Basic Alarm Clearing Procedures

Alarm Clearing Procedures
Document ID: 999-DOC000005-E Release: Standard Release Version: 1.1
www.tejasnetworks.com
Copyright Notice
Copyright 2000-2016. Tejas Networks Ltd. All rights reserved. No part of this book or manual may be
reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying,
recording, or by any information storage and retrieval system, without the express written permission from
Tejas Networks Ltd.
Warning and Disclaimer
While every effort has been made to make this document as complete and as accurate as possible, Tejas
Networks does not accept any responsibility for poorly designed or malfunctioning networks. The information
provided in this document is on an as is basis and is subject to change without prior notice. The author,
Tejas Networks, shall have neither liability nor responsibility to any person or entity with respect to any loss or
damage arising from the information contained in this document or from the use of equipment or software
that might accompany it. The opinions expressed in this document are not necessarily those of Tejas Networks.
Trademark Acknowledgments
All terms mentioned in this book that are known trademarks or service marks have been appropriately
capitalized. All trademarks duly acknowledged. Tejas Networks cannot attest to the accuracy of third-party
information. Use of a term in this document should not be regarded as affecting the validity of any trademark
or service mark.
Technical Support Information
Tejas customers can contact Tejas Support Center (TSC) 24x7x365 for any assistance through helpline, fax or
email.
- Phone(s): +91 80 41719090/91/92/93/94/95
- Email: support@tejasnetworks.com
- Skype: tscsupport123
- Web: www.tejasnetworks.com
Revision History
Version Date Modifications Made
1.0 30 August 2013 Standard Release
1.1 3 May 2016 Addition of MPLS and CEM related alarms

Your Feedback is valuable to us!
Your opinion is of great value and will help us improve the quality of our product documentation and offer
better services to you. Please take few moments to provide us your opinion of this document. Send your
comments to docs@tejasnetworks.com
Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of

Detail, Organization, Appearance)
Good Fair Average Poor Bad N/A

Your evaluation of this Intelligibility: (Language, Vocabulary, Readability and Clarity, Technical Accuracy,
document Content)
Accessibility: (Contents, Index, Headings, Numbering, Glossary)
Improve the Make it more Improve the

overview/introduction concise/brief Contents
Add more step-by-step Improve the organization Add more

Your suggestions for procedures/ tutorials troubleshooting
improving this information
document
Include more figures Make it less technical Add more examples
Add more/better quick Add more detail Improve the index

reference aids
Other Suggestions:
If you wish to be contacted regarding your comments, please provide your contact details:
Name: Company:
Postcode: Address:
Telephone: Email:
Table of Contents
Using This Guide 13
Who This Guide Is For ............................................................................................................... 13
What This Guide Covers ............................................................................................................. 13
What You Should Already Know .............................................................................................. 13
Safety Signs Conventions ............................................................................................................ 14
Typographical Conventions ........................................................................................................ 15
Mouse Operation Conventions .................................................................................................. 15
Chapter Organization................................................................................................................... 16
Using Tejas Product Documentation ........................................................................................ 16
Alerts 17
Card Inserted ................................................................................................................................. 19
Configuration File Not Found.................................................................................................... 19
Database Commit Complete ....................................................................................................... 20
Database Commit Failure ............................................................................................................ 20
Database Restore Completed...................................................................................................... 21
Database Save Completed ........................................................................................................... 21
Protection Switch Complete ....................................................................................................... 22
Software Download Completed ................................................................................................. 23
System Reboot .............................................................................................................................. 23
Upgrade Cancel Started ............................................................................................................... 24
Upgrade Cancel Passed ................................................................................................................ 24
Upgrade Cancel Release Started ................................................................................................. 25
Upgrade Cancel Release Passed .................................................................................................. 25
Upgrade Check Started ................................................................................................................ 26
Upgrade Check Passed ................................................................................................................. 26
Upgrade Check Failed .................................................................................................................. 27
Upgrade Check Failed - Failed Checksum Validation............................................................. 27
Upgrade Check Failed - NE Already Running Release........................................................... 28
Upgrade Check Failed - Release Does Not Exist on NE ....................................................... 29
Upgrade Check Failed - Upgrade to Release Not Supported ................................................ 29
Upgrade Commit Started ............................................................................................................. 30
Upgrade Commit Passed ............................................................................................................. 30
Upgrade Delete Release Failed ................................................................................................... 31
Upgrade Delete Release Passed .................................................................................................. 31
Upgrade Delete Release Started.................................................................................................. 32
iv
Upgrade Deliver Release Started ................................................................................................ 32
Upgrade Deliver Release Passed................................................................................................. 33
Upgrade Deliver Release Failed .................................................................................................. 33
Upgrade Deliver Release Failed - Cannot Reach Release Server........................................... 34
Upgrade Deliver Release Failed - FTP Protocol Error ........................................................... 35
Upgrade Deliver Release Failed - Insufficient Disk Space for Release ................................ 36
Upgrade Invoke Started ............................................................................................................... 36
Upgrade Invoke Passed ............................................................................................................... 37
Upgrade Invoke Failed................................................................................................................. 37
User Authentication Succeeded .................................................................................................. 38
User Logged Out .......................................................................................................................... 38
Card Protection Alarms 39

Lockout of protection - Trap ID:648 ........................................................................................ 39
Forced Switch to work card - Trap ID:649 .............................................................................. 40
Manual Switch to work card - Trap ID:650 .............................................................................. 41
Forced Switch to protect card - Trap ID:651 ........................................................................... 42
Manual Switch to protect card - Trap ID:652 .......................................................................... 43
Card Lockout From Protection - Trap ID:653 ........................................................................ 44
Equipment Alarms 45
Bad checksum on configuration file - Trap ID:7 ..................................................................... 47
Bus Error - Trap ID:22 ................................................................................................................ 48
Card jacked out - Trap ID:152 ................................................................................................... 49
Card mismatch - Trap ID:153 .................................................................................................... 50
Card missing or removed - Trap ID:11 ..................................................................................... 51
Card not supported in this slot - Trap ID:676 ......................................................................... 52
Card Unusable - Trap ID:618 ..................................................................................................... 53
Circuit Pack Below Baseline - Trap ID:615 .............................................................................. 54
Cold Restart Required: FPGA Changed - Trap ID:614.......................................................... 55
Connectivity Check Failed - Trap ID:658 ................................................................................. 56
Config Downloading - Trap ID:23 ............................................................................................ 57
Config out of sync - Trap ID:20 ................................................................................................ 58
Database is corrupted/improper - Trap ID:861 ...................................................................... 59
Database Restore Failed - Trap ID:579..................................................................................... 60
Database Save Failed - Trap ID:547 .......................................................................................... 61
DCN Failure - Trap ID:473 ........................................................................................................ 62
Derive Voltage High - Trap ID:201........................................................................................... 63
Derived Voltage Low - Trap ID:369 ......................................................................................... 64
Documentation Version Mismatch / Invalid with Software Version - Trap ID:595......... 65
EEPROM Failure - Trap ID:17 ................................................................................................. 66
External Alarm Occurred - Trap ID:224 .................................................................................. 67
Factory Defaults Restored - Trap ID:682 ................................................................................. 68
v
Fan Failed - Trap ID:434 ............................................................................................................. 69
File System Almost Full - Trap ID:12 ....................................................................................... 70
FPGA Load Failure - Trap ID:18 .............................................................................................. 71
Hardware Failure - Trap ID:13 ................................................................................................... 72
Improper Card Jackin - Trap ID:695 ......................................................................................... 73
Input Voltage High on PSU Card - Trap ID:370 .................................................................... 74
Input Voltage Low On PSU Card - Trap ID:371 .................................................................... 75
Intercard Communication Failure - Trap ID:378 .................................................................... 76
Intercard Suspected - Trap ID:607 ............................................................................................ 77
Laser Failure - Trap ID:24........................................................................................................... 78
LAN Port Down - Trap ID:384 ................................................................................................. 79
Laser Temperature High Threshold Crossed - Trap ID:429 ................................................. 80
Laser temperature low threshold crossed - Trap ID:430........................................................ 81
Laser Supply Voltage High Threshold Crossed - Trap ID:431 ............................................. 82
Laser supply voltage low threshold crossed - Trap ID:432 .................................................... 83
Memory usage exceeded threshold - Trap ID:116 .................................................................. 84
Onboard voltage generation lower threshold crossed - Trap ID:470 ................................... 85
Onboard voltage generation upper threshold crossed - Trap ID:471 .................................. 86
Program Fault, Software Failure - Trap ID:15 ......................................................................... 87
Port Mirroring Active - Trap ID:688 ......................................................................................... 87
Provisioning Disabled -FileSystem Full - Trap ID:542........................................................... 88
Redundant pair communication failure - Trap ID:21 ............................................................. 89
Routing table near capacity - Trap ID:685 ................................................................................ 90
SFP Mismatch - Trap ID:359 ..................................................................................................... 91
SFP missing or removed - Trap ID:489 .................................................................................... 92
SFP Failure - Trap ID:490 ........................................................................................................... 93
SFP Unknown - Trap ID:491 ..................................................................................................... 94
Software Committing - Trap ID:32 ........................................................................................... 95
Software Downloading ................................................................................................................ 96
Software Download Failed - Trap ID:311 ................................................................................ 97
Switch to Protecting Card - Trap ID:387 .................................................................................. 98
Switched off/No Input Voltage - Trap ID:388 ....................................................................... 99
SW version mismatch - Trap ID:19 ......................................................................................... 100
Telecom Bus Allocation conflict - Trap ID:746 .................................................................... 101
Uploading Config - Trap ID:117.............................................................................................. 102
Work Fan Failed - Trap ID:608................................................................................................ 103
Facility Alarms 105

Alarm Indication Signal (AIS) on STM/OCn Port - Trap ID:30 ....................................... 107
Alarm Indication Signal (AIS) on AU/STS - Trap ID:352 .................................................. 108
Alarm Indication Signal (AIS) on TU/VT - Trap ID:362 .................................................... 109
Alarm Indication Signal (Terminating) - Trap ID:487 .......................................................... 111
Alarm Indication Signal on Port_PDH - Trap ID:540 ......................................................... 112
vi
Alarm Indication Signal Generated on Port_PDH - Trap ID:767 ..................................... 113
ALS Triggered - Laser Is Shutdown - Trap ID:25 ................................................................. 114
APS PDU Not Received - Trap ID:667 .................................................................................. 115
APS/MSP Channel mismatch failure - Trap ID:315 ............................................................ 116
APS/MSP Mode mismatch failure - Trap ID:314 ................................................................. 117
APS/MSP Protect Switch Byte failure - Trap ID:316 .......................................................... 118
APS/MSP Far End Protect Line Failure - Trap ID:317....................................................... 119
Auto Negotiation Failed - Trap ID:516 .................................................................................. 120
SFP Auto Provision Mismatch - Trap ID:360 ....................................................................... 121
BER Threshold exceeded for Signal Degrade - Trap ID:381 .............................................. 122
BER Threshold exceeded on Section for Signal Degrade - Trap ID:480 .......................... 123
BER Threshold exceeded on Far End Line for Signal Degrade - Trap ID:482 ............... 124
BER Threshold Exceeded for Signal Failure (B1) - Trap ID:115 ....................................... 125
BER Threshold Exceeded for Signal Failure (B2) - Trap ID:115 ....................................... 126
BER Threshold Exceeded on Section for Signal Failure - Trap ID:479 ............................ 127
BER Threshold Exceeded on Far End Line for Signal Failure - Trap ID:481 ................. 128
Communication Link Failure - Trap ID:598 .......................................................................... 129
Connectivity Check Failed - Trap ID:658 ............................................................................... 130
Excessive Error on AU/STS - Trap ID:390 .......................................................................... 131
Excessive Error on TU/VT - Trap ID:391 ............................................................................ 132
Excessive Error Ratio (Ethernet Port) - Trap ID:518 .......................................................... 133
Excessive Error Ratio (VCG Port) - Trap ID:495 ................................................................ 134
Far End Client Signal Failure - Trap ID:409 .......................................................................... 135
Far End Excessive Error on AU/STS - Trap ID:484........................................................... 136
Far End Excessive Error on TU/VT - Trap ID:486 ............................................................ 137
Far End Protection Line Failure - Trap ID:444 ..................................................................... 138
Far End Signal Degrade on AU/STS - Trap ID:483 ............................................................ 139
Far End Signal Degrade on TU/VT - Trap ID:485 .............................................................. 140
Firmware version mismatch/invalid with software version - Trap ID:594 ....................... 141
Forced Switch Active ................................................................................................................. 142
Group Identifier Mismatch-LCAS - Trap ID:610 ................................................................. 144
Out of Frame (OOF) - Trap ID:29 ......................................................................................... 145
Laser Bias current lower threshold crossed - Trap ID:394 .................................................. 146
Laser Bias Voltage Upper Threshold Crossed - Trap ID:395.............................................. 147
LCAS Mode Mismatch - Trap ID:405..................................................................................... 148
Line/MS DCC Link Failure - Trap ID:597 ............................................................................ 149
Link Down On Ethernet - Trap ID:305 ................................................................................. 150
Link Down on VCG - Trap ID:493 ........................................................................................ 151
Link Integrity ON - Trap ID:402 ............................................................................................. 152
Lockout Active - Trap ID: ........................................................................................................ 153
Loopback Active-Facility - Trap ID:377 ................................................................................. 154
Loopback Active-Terminal - Trap ID:361.............................................................................. 155
Loss of Frame (LOF) - Trap ID:28 ......................................................................................... 157
vii
Loss of Frame Delineation - Trap ID:410 .............................................................................. 158
Loss of Frame on Port_PDH - Trap ID:541 ......................................................................... 159
Loss of Multiframe on AU/STS - Trap ID:104 ..................................................................... 160
Loss of Multiframe on Port_PDH - Trap ID:536 ................................................................. 161
Loss of Pointer on AU/STS - Trap ID:354 ........................................................................... 162
Loss of Pointer on TU/VT - Trap ID:364 ............................................................................. 163
Loss of Signal on STM/OC Port - Trap ID:27 ..................................................................... 164
Loss Of Signal on PDH port - Trap ID:202 .......................................................................... 165
Loss of VCAT Multiframe - Trap ID:50 ................................................................................ 166
Manual Switch Active................................................................................................................. 167
Manual Switch Fail ..................................................................................................................... 169
NTP Server Unreachable - Trap ID:535 ................................................................................. 170
Path Label Mismatch on AU/STS - Trap ID:357 ................................................................. 171
Path Label Mismatch on TU/VT - Trap ID:367 ................................................................... 172
Protection Switch Active ........................................................................................................... 173
Protection Switching is Incomplete - Trap ID:669 ............................................................... 174
Protection Channel Match Fail - Trap ID:442 ....................................................................... 175
Protection mode mismatch - Trap ID:441 ............................................................................. 176
Protection Switch Byte Fail - Trap ID:443 ............................................................................. 177
Received Power Lower Threshold Crossed - Trap ID:400 .................................................. 178
Received Power upper threshold crossed - Trap ID:401 ..................................................... 179
Remote Alarm Indication(RAI) - Trap ID:538 ...................................................................... 180
Remote Defect Indication (RDI) on STM/OCn Port - Trap ID:31 .................................. 181
Remote Defect Indication (RDI) on AU/STS - Trap ID:353 ............................................. 182
Remote Defect Indication (RDI) on TU/VT - Trap ID:363 .............................................. 183
Remote Defect Indication (Terminating) - Trap ID:488 ...................................................... 184
Rx Partial Loss of Capacity - LCAS - Trap ID:407 ............................................................... 185
Rx Total Loss of Capacity - LCAS - Trap ID:411 ................................................................. 186
Section/RS DCC Link Failure - Trap ID:596 ........................................................................ 187
Secondary Reference Out of Range - Trap ID:412 ............................................................... 188
SFP Auto Provision Mismatch - Trap ID:360 ....................................................................... 189
Signal Degrade on AU/STS - Trap ID:358 ............................................................................ 190
Signal Degrade on TU/VT - Trap ID:368.............................................................................. 192
Signal Degrade on Ethernet Port - Trap ID:519 ................................................................... 193
Signal Degrade on VCG - Trap ID:496 .................................................................................. 194
Signal Label Unequipped on AU/STS - Trap ID:355 .......................................................... 196
Signal Label Unequipped on TU/VT - Trap ID:365 ............................................................ 197
System clock in internal mode - Trap ID:97 .......................................................................... 198
Timing reference failed - Trap ID:241 .................................................................................... 199
Trace Identifier Mismatch on STM/OCn Port - Trap ID:52 .............................................. 201
Trace Identifier Mismatch on AU/STS - Trap ID:356......................................................... 203
Trace Identifier Mismatch on TU/VT - Trap ID:366 .......................................................... 205
Transmitted Power Lower Threshold Crossed - Trap ID:392 ............................................ 206
viii
Transmitted Power Upper Threshold Crossed - Trap ID:393 ............................................ 207
Tx Partial Loss of Capacity - LCAS - Trap ID:497 ............................................................... 208
Tx Total Loss Of Capacity-LCAS - Trap ID:406 .................................................................. 209
User Payload Mismatch - Trap ID:498 ................................................................................... 210
Upgrade load passed - Trap ID:566 ......................................................................................... 211
User Authentication Failed - Trap ID:320 .............................................................................. 212
Loss of Frames - Trap ID:740 .................................................................................................. 213
Late Frames - Trap ID:741 ....................................................................................................... 214
Malformed Frames - Trap ID:742 ........................................................................................... 215
Jitter Buffer Overrun - Trap ID:743 ........................................................................................ 216
FarEnd IWF failure - Trap ID:744 .......................................................................................... 217
FarEnd TDM Failure Trap ID:745 .......................................................................................... 218
Jitter Buffer Underrun Trap ID:749 ........................................................................................ 219
MS-SPRing/BLSR Alarms 221

Invalid K Byte - Trap ID:673 ................................................................................................... 222
Invalid K Byte East - Trap ID:626 .......................................................................................... 223
Invalid K Byte West - Trap ID:627 ......................................................................................... 224
Manual Switch Active on East - Trap ID:632 ........................................................................ 225
Manual Switch Active On West - Trap ID:634 ...................................................................... 226
Ring Switch Active - Trap ID:672............................................................................................ 227
Ring Switch East - Trap ID:423 ............................................................................................... 228
Ring Switch West - Trap ID:424 .............................................................................................. 229
Security Alarms 231

All Radius Servers are Unavailable - Trap ID:647 ................................................................. 231
Primary Radius Server Unavailable - Trap ID:645 ................................................................ 232
Secondary Radius Servers Unavailable - Trap ID:646 .......................................................... 233
L2 Alarms 235
CBG Member Not Deskewable - Trap ID:894 ..................................................................... 236
CCM Interval Mismatch - Trap ID:663 .................................................................................. 237
FDB Limited Reached - Trap ID:686 ..................................................................................... 238
Forced Down Link Integrity - Trap ID:517 ........................................................................ 239
Group Label Mismatch on CBG Member - Trap ID:897 .................................................... 240
Loop Detected - Trap ID:664 .................................................................................................. 241
Loss of Connectivity on CBG Member - Trap ID:895 ........................................................ 242
Loss of Signal on Ethernet port - Trap ID:611 ..................................................................... 243
Multiple RPL Owners Configured - Trap ID:660 ................................................................. 244
No RPL Owner Configured - Trap ID:659 ............................................................................ 245
PacketTrunk OperStatus Down - Trap ID:694 ..................................................................... 246
Partial Loss of Capacity on CBG - Trap ID:893 ................................................................... 247
RDI on CBG Member - Trap ID:896 ..................................................................................... 248
ix
Remote and Local IP Match - Trap ID:693 ........................................................................... 249
Remote Defect Indication - Trap ID:662 ............................................................................... 250
Total Loss of Capacity on CBG - Trap ID:892 ..................................................................... 251
Unexpected MAID - Trap ID:661 ........................................................................................... 252
Unexpected MEPID - Trap ID:665......................................................................................... 253
Unexpected MD Level - Trap ID:666 ..................................................................................... 254
EMS Alarms 255

Alarms from the Anonymous Node - Trap ID:105 .............................................................. 257
Amplifier Not Reachable - Trap ID:111 ................................................................................. 258
Audit Log Size Exceeded - Trap ID: ....................................................................................... 259
Audit Log Size Exceeded - Trap ID:134 ................................................................................. 260
Audit Log Size Exceeded - Trap ID:135 ................................................................................. 261
Audit Log Archive Size Exceeded - Trap ID:136 .................................................................. 262
CPU is Fully Loaded - Trap ID:128 ........................................................................................ 265
CPU Utilization Exceeded - Trap ID:127 ............................................................................... 266
CPU Utilization Is High - Trap ID:126................................................................................... 267
Disk Usage Almost Full - Trap ID:125 ................................................................................... 268
Disk Usage Exceeded - Trap ID:124 ....................................................................................... 269
Disk Usage is High - Trap ID:133 ........................................................................................... 270
EMS Backup Fail Alarm - Trap ID:8002 ................................................................................ 271
EMS License is going to expire - Trap ID:132 ...................................................................... 272
EVC Degrade - Trap ID:119 .................................................................................................... 273
EVC Failure ................................................................................................................................. 274
Farend Client Signal Degrade - Trap ID:121 ......................................................................... 275
Farend Client Signal Failure - Trap ID:122 ............................................................................ 276
Historical Alarm Data out of Sync - Trap ID:110 ................................................................. 276
HistAlarms size exceeded - Trap ID:139 ................................................................................ 277
HistAlarms size exceeded - Trap ID:141 ................................................................................ 278
HistAlarms Archive size exceeded - Trap ID:142 ................................................................. 279
Memory Usage Exceeded - Trap ID:123 ................................................................................ 282
Maximum Alarm Count exceeded - Trap ID:129 .................................................................. 283
No Connectivity to Slave - Trap ID:107 ................................................................................. 284
Node Alarm Out of Sync - Trap ID:112................................................................................. 285
Node Config out of Sync - Trap ID:106 ................................................................................. 286
Node Not Reachable - Trap ID:100 ........................................................................................ 287
Node Router ID changed - Trap ID:145 ................................................................................ 288
Node Upload Completed - Trap ID:102 ................................................................................ 289
Node Upload Failed - Trap ID:103 ......................................................................................... 290
x
Node Upload Started - Trap ID:101........................................................................................ 291
One Way Communication from Node to Server - Trap ID:114 ......................................... 292
One Way Communication from Server to Node - Trap ID:113 ......................................... 293
Total NodeWeight About to Exceed the Licensed Value .................................................... 294
Total Number of Nodes About to Exceed the Licensed Value - Trap ID:131 ................ 295
Trunk Oper Down - Trap ID:389............................................................................................ 296
NMS Alarms 297

Path failed .................................................................................................................................... 298
Circuit is unprotected ................................................................................................................. 299
Traffic Loss.................................................................................................................................. 300
EMS is not reachable ................................................................................................................. 301
Disk Usage alarm ........................................................................................................................ 302
Slave not reachable ..................................................................................................................... 303
Slave DB not reachable .............................................................................................................. 304
Loop Back Alarm........................................................................................................................ 305
All Managed Element Unavailable Alarm ............................................................................... 306
Bandwidth over-provisioned..................................................................................................... 307
QoS Mis-configuration .............................................................................................................. 308
Undiscovered/Incomplete entities found in QoS Domain.................................................. 309
Restart Procedures 311

Cold Restart Required: FPGA changed - Trap ID:614......................................................... 311
Module Replacement Procedures 313

Ethernet Interface Card Replacement ..................................................................................... 313
Fan Filter Replacement .............................................................................................................. 314
Fan Module Replacement .......................................................................................................... 315
Power Supply Unit Replacement.............................................................................................. 316
SFP Pluggable Module Replacement ....................................................................................... 317
Glossary of Terms 319

Index 325
xi
List of Tables
Table 1: Safety Sign Convention..................................................................................................... 14
Table 2: Typographical Conventions ............................................................................................. 15
Table 3: Mouse Operation ............................................................................................................... 15
xii
Chapter 1
Using This Guide

This section describes who should read this guide, how it is organized, and what conventions are
used in the document.
IN THIS CHAPTER
Who This Guide Is For ..................................................................................13
What This Guide Covers ................................................................................13
What You Should Already Know .................................................................13
Safety Signs Conventions ...............................................................................14
Typographical Conventions ...........................................................................15
Mouse Operation Conventions .....................................................................15
Chapter Organization .....................................................................................16
Using Tejas Product Documentation ...........................................................16
Who This Guide Is For

This document is intended for technician and maintenance engineers who are responsible for the
day-to-day operation of the system.
What This Guide Covers

This document contains details of alarms and procedures for clearing them. This revision of the
document is a super set of all the earlier versions of document.
What You Should Already Know

Before you read this guide you need to be comfortable working with:
Networking and SDH concepts.
Basic understanding of Tejas Networks products.
None of these topics are covered in this guide. For information about these topics, refer to their
separate user documentation.
13
Alarm Clearing Procedures Document ID: 999-DOC000005-E
Safety Signs Conventions

To prevent personal injury, equipment damage, and service interruptions, you must follow all
precautionary messages given in the document in addition to all the local safety standards
required by your company. The following symbols inserted in the document at various places
represent important situations.
Table 1: Safety Sign Convention
Symbols Meaning Represents

Caution Situations that could result in equipment damage or loss of
data.
Danger Situation that could cause bodily injury. Failure to observe

this precaution may result in personal injury, death, or
equipment damage.
Hot Surface Situation that could result in bodily burns.
Optical Safety Staring directly into the optical connector output beam may
cause irreparable damage to your eyes and even leading to
loss of eye sight.
Electric Shock Risk Failure to observe this precaution may result in personal
injury, death, or equipment damage.
Static Discharge Handle the equipment wearing a grounding wrist strap to

Warning discharge the static buildup. Failure to observe this
precaution may result in equipment damage.
Rotating Part Keep fingers, screwdrivers, and other objects away from the
openings in the fan tray assembly. The fans might still be
turning when you remove the fan assembly from the chassis.
14
Chapter 1 Using This Guide
Typographical Conventions
Before you start using this guide, it is important to understand the terms and typographical
conventions used in the document. The following kinds of formatting in the text identify special
information.
Table 2: Typographical Conventions
Formatting Convention Type of Information
Procedures Step-by-step procedures. You can follow these instructions to

complete a specific task.
Special Bold Items you must select, such as menu options, command buttons,
or items in a list.
Emphasis Use to emphasize the importance of a point or for variable
expressions such as parameters.
CAPITALS Names of keys on the keyboard, for example, SHIFT, CTRL, or

ALT.
KEY+KEY Key combinations for which the user must press and hold down
one key and then press another, for example, CTRL+P, or
ALT+F4.
Means reader take note. Notes contain helpful suggestions or
NOTE: references to materials not contained in this manual.
Mouse Operation Conventions

Table 3: Mouse Operation
Convention Description
Click Refers to pressing and releasing a mouse button to select a screen object.
Double-click Refers to pressing and releasing a mouse button twice in succession while the
cursor is positioned over an object on-screen.
Drag Refers to the function of the mouse by which an element on the screen of a
monitor is moved with the cursor, while holding down the mouse button and
moving the mouse.
Right-click Refers to pressing the right button on a two-button mouse.
Wheel button Refers to the third (middle) button on the mouse.
15
Chapter Organization
This document is organized as follows:
Chapter Scope
Alerts on page 17 This chapter describes the Alerts supported on the node.
Card Protection Alarms on page This chapter describes Card Protection alarms raised on the node and
39 the procedure to clear them.
Equipment Alarms on page 45 This chapter describes Equipment alarms raised on the node and the
procedure to clear them.
Facility Alarms on page 105 This chapter describes Facility alarms raised on the node and the
MS-SPRing/BLSR Alarms on This chapter describes MSSP alarms raised on the node and the
page 221 procedure to clear them. The alarm clearing procedures are based on
MS-SPRing/BLSR protection.
Security Alarms on page 231 This chapter describes Security alarms raised on the node and the
L2 Alarms on page 235 This chapter describes L2 alarms raised on the node and the
EMS Alarms on page 255 This chapter describes EMS alarms raised on Element Management
System and the procedure to clear them.
NMS Alarms on page 297 This chapter describes NMS alarms raised on Network Management
System and the procedure to clear them.
Restart Procedures on page 311 This chapter describes the restart procedures on the node.
Module Replacement Procedures This chapter covers the replacement procedures for different modules
on page 313 in a node.
Using Tejas Product Documentation

The following Tejas product documentation set helps you use the range of Tejas products:
The Hardware Description Guide document explains hardware configuration, functions,
capabilities, limitations, and physical characteristics of the product.
The Installation and Commissioning Guide document provides information on installing the
product and to initially configuring it to the point of verifying its proper operation in the
network.
The User Interface Guide introduces and orients service providers to the content, function, and
organization of the services user interface that support the nodes.
16
Chapter 2
Alerts
Alerts are events reported which may not require any direct action. These alerts are raised for
information purpose only. Alerts are displayed in the Event History preview pane.
17
IN THIS CHAPTER
Card Inserted ....................................................................................................19
Configuration File Not Found ......................................................................19
Database Commit Complete .........................................................................20
Database Commit Failure...............................................................................20
Database Restore Completed ........................................................................21
Database Save Completed ..............................................................................21
Protection Switch Complete ..........................................................................22
Software Download Completed ....................................................................23
System Reboot .................................................................................................23
Upgrade Cancel Started ..................................................................................24
Upgrade Cancel Passed...................................................................................24
Upgrade Cancel Release Started ....................................................................25
Upgrade Cancel Release Passed ....................................................................25
Upgrade Check Started ...................................................................................26
Upgrade Check Passed ...................................................................................26
Upgrade Check Failed.....................................................................................27
Upgrade Check Failed - Failed Checksum Validation ...............................27
Upgrade Check Failed - NE Already Running Release .............................28
Upgrade Check Failed - Release Does Not Exist on NE .........................29
Upgrade Check Failed - Upgrade to Release Not Supported...................29
Upgrade Commit Started ...............................................................................30
Upgrade Commit Passed ................................................................................30
Upgrade Delete Release Failed ......................................................................31
Upgrade Delete Release Passed.....................................................................31
Upgrade Delete Release Started ....................................................................32
Upgrade Deliver Release Started ...................................................................32
Upgrade Deliver Release Passed ...................................................................33
Upgrade Deliver Release Failed ....................................................................33
Upgrade Deliver Release Failed - Cannot Reach Release Server .............34
Upgrade Deliver Release Failed - FTP Protocol Error .............................35
Upgrade Deliver Release Failed - Insufficient Disk Space for Release...36
Upgrade Invoke Started..................................................................................36
Upgrade Invoke Passed ..................................................................................37
Upgrade Invoke Failed ...................................................................................37
User Authentication Succeeded ....................................................................38
User Logged Out .............................................................................................38
18
Chapter 2 Alerts
Card Inserted
This procedure provides information on the 'Card Inserted' alert.
Cause
This alert is raised when a valid card is inserted into an un-provisioned slot.
Impact
This alert is non-service affecting. This alert is raised for information purpose only.
Objects Affected
Cards
Clearing Procedure
No action is required.
Configuration File Not Found

This procedure provides information on the 'Configuration file not found' alert.
Cause
This alert is raised if the configuration database file is not found during the boot up process of
the node.
Severity
Minor
Objects Affected
Card
Impact
The node will come up in SLAT (initialization) mode on reboot. This alert is raised for
information purpose only.
Clearing Procedure
1. Log-in into the node WUI (Web User Interface) at the default view level with appropriate
user access privileges.
2. Restore the configuration back-up.
19
Database Commit Complete

This procedure provides information on the 'Database commit complete' alert.
Cause
This alert is raised when database commit on the node is completed.
Objects Affected
Card
Impact
Database commit is service affecting.
Clearing Procedure
Database Commit Failure

This procedure provides information on the 'Database Commit Failure' alert.
Cause
This alert is raised when database commit on the node has failed due to difference in MAC
Address, IP Address or node name.
Objects Affected
Card
Impact
Non-service affecting. This alert is raised for information purpose only.
Clearing Procedure
No action is required. This alert is cleared after next successful database commit operation.
20
Chapter 2 Alerts
Database Restore Completed

This procedure provides information on the 'Database Restore Completed' alert.
Cause
This alert is raised when the restoration of the node configuration from remote or local machine
is successful.
Objects Affected
Card
Impact
Non-service affecting. This alert is raised for information purpose only.
Clearing Procedure
No action is required to clear this alert.
Database Save Completed

This procedure provides information on the 'Database Save Completed' alert.
Cause
This alert is raised when back-up operation of node configuration is successful.
Objects Affected
Card
Impact
The impact of this alert is non-service affecting. This alert is raised for information purpose only.
Clearing Procedure
No action is necessary.
21
Protection Switch Complete

This procedure provides information on the 'Protection Switch Active' alert.
Cause
The alert is raised when traffic switches from work to protect channel on a revertive mode. In
case of a bidirectional or an automatic switch, this alert is raised for any of the following reasons:
a local signal fail
signal degrade
loss of frame
AIS
Object affected
STM/OCn Port
Impact
The impact of this alert is that traffic is carried in the protect path.
Clearing procedure
To clear this alert,
1. Log-in to the node WUI (Web User Interface) at the default view level with appropriate user
access privileges.
2. Determine if there are any Signal fail or Signal degrade alarm present. Use appropriate
procedure to clear the reported alert.
If alarm persists, contact your next level of support.
22
Chapter 2 Alerts
Software Download Completed

This procedure provides information on the 'Software Download Completed' alert.
Cause
This alert is raised after the completion of software download operation. This alarm is a
consequence of software download operation performed on the node.
Objects Affected
Card
Impact
Non-traffic affecting.
Clearing Procedure
System Reboot
This procedure provides information on the 'System Reboot' alert.
Cause
This alert is raised when the node initializes after a reboot. The reboot could be a result of a user-
initiated operation or of a software fault. This is an event, transient condition.
Object affected
Node
Impact
The impact of this alert are:
operations like protection switching and performance data collection will not be available for
some time.
alarms will be reported only after the software and management connectivity has been fully
set-up.
the management connectivity for the downstream node will be affected for some time.
Clearing Procedure
No action is required. This alert will be automatically cleared by the node after the initialization is
complete.
23
Upgrade Cancel Started

This procedure provides information on the 'Upgrade Cancel Started' alert.
Cause
This alert is raised when canceling the software upgrade process on the node.
Objects Affected
Node
Impact
The impact of this alert is non-service affecting. The node will go for a non-service affecting
restart if this alert is raised after 'Upgrade Invoke Passed on page 37' alert. Other node will not
restart.
Clearing Procedure
No action is required. This alert is raised for information purpose only.
Upgrade Cancel Passed

This procedure provides information on the 'Upgrade Cancel Passed' alert.
Cause
This alert is raised when software upgrade process for the node is canceled successfully.
Objects Affected
Node
Impact
The impact of this alert is non-service affecting.
Clearing Procedure
24
Chapter 2 Alerts
Upgrade Cancel Release Started

This procedure provides information on the 'Upgrade Cancel Release Started' alert.
Cause
This alert is raised to indicate upgrade cancel operation has started on the node.
Objects Affected
Node
Impact
Clearing Procedure
Upgrade Cancel Release Passed

This procedure provides information on the 'Upgrade Cancel Release Passed' alert.
Cause
This alert is raised when the upgrade process is canceled before the upgrade commit step is
completed on the node.
Objects Affected
Node
Impact
The impact of the alarm is non-service affecting.
Clearing Procedure
25
Upgrade Check Started

This procedure provides information on the 'Upgrade Check Started' alert.
Cause
This alert is raised when checking for prerequisites for software upgrade is initialized on the
node.
Objects Affected
Node
Impact
This alert is raised for information purpose only and does not affect the traffic.
Clearing Procedure
No action necessary.
Upgrade Check Passed

This procedure provides information on the 'Upgrade Check Passed' alert.
Cause
This alert is raised when checking for prerequisites for software upgrade is completed on the
node.
Objects Affected
Node
Impact
This alert is raised for information purpose only and does not affect the traffic.
Clearing Procedure
No action necessary.
26
Chapter 2 Alerts
Upgrade Check Failed

This procedure provides information on the 'Upgrade Check Failed' alert.
Cause
This alert is raised when checking for prerequisites for software upgrade is failed on the node.
Objects Affected
Node
Impact
Clearing Procedure
1. Log-in to the node WUI at the default view level with appropriate user access privileges.
Ensure that the release server has the correct software version.
2. Perform upgrade operation on a release, different from the release which is running on the
node.
Upgrade Check Failed - Failed Checksum Validation

This procedure provides information on the 'Upgrade Check Failed - Failed Checksum Validation'
alert.
Cause
This alert is raised when checking for prerequisites for software upgrade is failed on node as
downloaded software is corrupted. The node displays "Check upgrade failed on release" message
in the Software download preview pane.
Objects Affected
Node
Impact
Clearing Procedure
27
2. Cancel the current upgrade and perform upgrade operation.
Upgrade Check Failed - NE Already Running Release

This procedure provides information on the 'Upgrade Check Failed - NE Already Running Release'
alert.
Cause
This alert is raised when checking for prerequisites for software upgrade is failed as the node is
already running on the downloaded software.
Objects Affected
Node
Impact
The impact of the alert is non-service affecting.
Clearing Procedure
3. Ensure that deliver release operation is successful.
28
Chapter 2 Alerts
Upgrade Check Failed - Release Does Not Exist on NE

This procedure provides information on the 'Upgrade Check Failed - Release Does Not Exist On NE'
alert.
Cause
This alert is raised software upgrade is failed as the software release bundle does not exists on the
node.
Objects Affected
Node
Impact
Clearing Procedure
1. Log-in to the node WUI (Web User Interface) at the default view level with appropriate user
access privileges.
Upgrade Check Failed - Upgrade to Release Not

Supported
This procedure provides information on the 'Upgrade Check Failed - Upgrade To Release Not
Supported' alert.
Cause
This alert is raised when upgrade to the new software is not supported.
Objects Affected
Node
Impact
Clearing Procedure
29
2. Ensure that the new Software version to be upgraded is a supported upgrade path.
NOTE: Software versions are incremental. Upgrading to higher versions is allowed while
downgrading is not supported.
Upgrade Commit Started

This procedure provides information on the 'Upgrade Commit Started' alert.
Cause
This alert is raised when committing the software on the node is started.
Objects Affected
Node
Impact
The node does not go for a reboot. This alert is raised for information purpose only and does not
affect the service.
Clearing Procedure
Upgrade Commit Passed

This procedure provides information on the 'Upgrade Commit Passed' alert.
Cause
This alert is raised when committing the software on the node is completed.
Objects Affected
Node
Impact
Clearing Procedure
No action is necessary. This alert is raised for information purpose only.
30
Chapter 2 Alerts
Upgrade Delete Release Failed

This procedure provides information on the 'Upgrade Delete Release Failed' alert.
Cause
This alert is raised to indicate that delete release operation has failed.
Objects Affected
Node
Impact
Clearing Procedure
Contact your next level of support.
Upgrade Delete Release Passed

This procedure provides information on the 'Upgrade Delete Release Passed' alert.
Cause
This alert is raised to indicate that delete release operation has passed.
Objects Affected
Node
Impact
Clearing Procedure
No action is necessary. This alert is raised for information purposes only.
31
Upgrade Delete Release Started

This procedure provides information on the 'Upgrade Delete Release Started' alert.
Cause
This alert is raised to indicate that delete release operation has started.
Objects Affected
Node
Impact
Clearing Procedure
Upgrade Deliver Release Started

This procedure provides information on the 'Upgrade Deliver Release Started' alert.
Cause
This alert is raised when transfer of software release starts while upgrading the software on node.
Objects Affected
Node
Impact
Clearing Procedure
No action is required. This alert is raised for information purposes only.
32
Chapter 2 Alerts
Upgrade Deliver Release Passed

This procedure provides information on the 'Upgrade Deliver Release Passed' alert.
Cause
This alert is raised when transfer of software on node is completed.
Objects Affected
Node
Impact
Clearing Procedure
Upgrade Deliver Release Failed

This procedure provides information on the 'Upgrade Deliver Release Failed' alert.
Cause
This alert is raised when the transfer of software to the node fails due to certain errors in the
transmission.
Objects Affected
Node
Impact
Clearing Procedure
2. Correct the transmission errors which causes the software download to fail.
33
Upgrade Deliver Release Failed - Cannot Reach Release

Server
This procedure provides information on the 'Upgrade Deliver Release Failed - Cannot Reach Release
Server' alert.
Cause
This alert is raised when the transfer of the software onto the node fails as the node cannot
connect to the release server.
Objects Affected
Node
Impact
Clearing Procedure
2. Check for connectivity between the node and the release server.
34
Chapter 2 Alerts
Upgrade Deliver Release Failed - FTP Protocol Error

This procedure provides information on the 'Upgrade Deliver Release Failed - FTP Protocol Error'
alert.
Cause
This alert is raised when upgrading the software on node is failed due to FTP timeout errors,
wrong user name, wrong password, wrong directory path or incorrect file name.
Objects Affected
Node
Impact
Clearing Procedure
2. Check for FTP timeout errors, wrong user name, wrong password, wrong directory path or
incorrect file name. Rectify the same.
35
Upgrade Deliver Release Failed - Insufficient Disk Space

for Release
This procedure provides information on the 'Upgrade Deliver Release Failed - Insufficient Disk Space
For Release' alert.
Cause
This alert is raised when upgrading the software on node is failed due to insufficient disk space.
Objects Affected
Node
Impact
Clearing Procedure
2. Cancel the upgrade. Contact your next level of support.
Upgrade Invoke Started

This procedure provides information on the 'Upgrade Invoke Started' alert.
Cause
This alert is raised when untarring and installation of the software package is started for the node.
Objects Affected
Node
Impact
The node goes for a restart. This alert is raised for information purpose only and does not affect
the service.
Clearing Procedure
36
Chapter 2 Alerts
Upgrade Invoke Passed

This procedure provides information on the 'Upgrade Invoke Passed' alert.
Cause
This alert is raised while invoking the software on the node. The software package is unpacked
and installed on the node.
Objects Affected
Node
Impact
the service.
Clearing Procedure
Upgrade Invoke Failed

This procedure provides information on the 'Upgrade Invoke Failed' alert.
Cause
This alert is raised when invoking of the software on the node is failed.
Objects Affected
Node
Impact
the service.
Clearing Procedure
37
User Authentication Succeeded

This procedure provides information on the 'User Authentication Succeeded' alert.
Cause
This alert is raised when TL1 session is logged in successfully.
Objects Affected
Node
Impact
TL1 session will be available for provisioning and retrieval commands (as per the user privilege
level). It is an event in transient condition.
Clearing Procedure
User Logged Out

This procedure provides information on the 'User Logged Out' alert.
Cause
This alert is raised when a previously opened TL1 session is terminated.
Objects Affected
Node
Impact
This impact of this alert is non-service affecting.
Clearing Procedure
38
Chapter 3
Card Protection Alarms

This chapter describes Card Protection alarms and the clearing procedures on the node.
IN THIS CHAPTER
Lockout of protection - Trap ID:648...........................................................39
Forced Switch to work card - Trap ID:649 .................................................40
Manual Switch to work card - Trap ID:650 ................................................41
Forced Switch to protect card - Trap ID:651 .............................................42
Manual Switch to protect card - Trap ID:652 ............................................43
Card Lockout From Protection - Trap ID:653 ..........................................44
Lockout of protection - Trap ID:648

Use this procedure to clear the 'Lockout of protection' alarm.
Cause
This alarm is raised when the user issues a lockout of protection external command on the
protect (protecting) card.
Severity
Minor
Object Affected
Card Protection Group
Impact
Card protection for all the Work (Protected) cards becomes unavailable. This alarm is service
affecting if the work card fails.
Clearing Procedure
To clear this alarm, check for the 'Card Lockout of Protection' alarm and apply Clear command.
If the alarm persists, contact your next level of support.
39
Forced Switch to work card - Trap ID:649

Use this procedure to clear the 'Forced Switch to work card' alarm.
Cause
This alarm is raised when user issues Forced Switch to work external command.
Severity
Minor
Object Affected
Objects Affected
This alarm is applicable only for protecting card, non-revertive protection and when the
protection is active. This alarm is not applicable for 1:N as 1:N is only for revertive mode of
operation.
Impact
Service affecting, if the Work (Protected) card is out of service
Traffic affecting, if the traffic is on protect card
Clearing Procedure
To clear this alarm, apply the forced switch to work command.
40
Chapter 3 Card Protection Alarms
Manual Switch to work card - Trap ID:650

Use this procedure to clear the 'Manual Switch to work card' alarm.
Cause
This alarm is raised when user issuing Manual Switch to work external command.
Severity
Minor
Object affected
Impact
Traffic affecting, if the traffic is on protect card.
Clearing Procedure
To clear this alarm, apply the Clear or Lockout or Forced Switch commands. Failure of any card
involved in work group also clears this alarm.
41
Forced Switch to protect card - Trap ID:651

Use this procedure to clear the 'Forced Switch to protect card' alarm.
Cause
This alarm is raised when User issues Forced Switch to protect external command.
Severity
Minor
Object Affected
Card
Impact
Services will be impacted if the protecting card is failed.
Clearing Procedure
To clear this alarm, apply the forced switch to protect command.
42
Chapter 3 Card Protection Alarms
Manual Switch to protect card - Trap ID:652

Use this procedure to clear the 'Manual Switch to protect card' alarm. A failure on the protect card
(after issuing this command) will clear this command and the active traffic will be carried on the
work card.
Cause
This alarm is raised when the user issues Manual Switch to Protect external command.
Severity
Minor
Object affected
Card
Impact
The impact of this alarm will be service affecting.
Clearing Procedure
To clear this alarm, apply the Clear or Lockout or Forced Switch commands. Failure of any card
involved in Protection group also clears this alarm.
43
Card Lockout From Protection - Trap ID:653

Use this procedure to clear the 'Card Lockout from protection' alarm.
Cause
This alarm is raised when user issues a Lockout from protection on the card.
Severity
Minor
Object Affected
Card
Impact
Non service affecting.
Clearing Procedure
To clear this alarm, apply the Clear of Lockout command. If the alarm still persists, contact your
next level of support.
44
Chapter 4
Equipment Alarms
This chapter describes Equipment alarms raised on the node and the procedure to clear them.
45
IN THIS CHAPTER
Bad checksum on configuration file - Trap ID:7..................................................................................... 47

Bus Error - Trap ID:22............................................................................................................................... 48
Card jacked out - Trap ID:152................................................................................................................... 49
Card mismatch - Trap ID:153.................................................................................................................... 50
Card missing or removed - Trap ID:11 .................................................................................................... 51
Card not supported in this slot - Trap ID:676 ......................................................................................... 52
Card Unusable - Trap ID:618 .................................................................................................................... 53
Circuit Pack Below Baseline - Trap ID:615.............................................................................................. 54
Cold Restart Required: FPGA Changed - Trap ID:614.......................................................................... 55
Connectivity Check Failed - Trap ID:658 ................................................................................................ 56
Config Downloading - Trap ID:23 ........................................................................................................... 57
Config out of sync - Trap ID:20................................................................................................................ 58
Database is corrupted/improper - Trap ID:861 ...................................................................................... 59
Database Restore Failed - Trap ID:579 .................................................................................................... 60
Database Save Failed - Trap ID:547 ......................................................................................................... 61
DCN Failure - Trap ID:473 ....................................................................................................................... 62
Derive Voltage High - Trap ID:201 .......................................................................................................... 63
Derived Voltage Low - Trap ID:369......................................................................................................... 64
Documentation Version Mismatch / Invalid with Software Version - Trap ID:595 .......................... 65
EEPROM Failure - Trap ID:17................................................................................................................. 66
External Alarm Occurred - Trap ID:224 .................................................................................................. 67
Factory Defaults Restored - Trap ID:682 ................................................................................................ 68
Fan Failed - Trap ID:434............................................................................................................................ 69
File System Almost Full - Trap ID:12....................................................................................................... 70
FPGA Load Failure - Trap ID:18 ............................................................................................................. 71
Hardware Failure - Trap ID:13 .................................................................................................................. 72
Improper Card Jackin - Trap ID:695 ........................................................................................................ 73
Input Voltage High on PSU Card - Trap ID:370 .................................................................................... 74
Input Voltage Low On PSU Card - Trap ID:371 .................................................................................... 75
Intercard Communication Failure - Trap ID:378 .................................................................................... 76
Intercard Suspected - Trap ID:607............................................................................................................ 77
Laser Failure - Trap ID:24.......................................................................................................................... 78
LAN Port Down - Trap ID:384 ................................................................................................................ 79
Laser Temperature High Threshold Crossed - Trap ID:429.................................................................. 80
Laser temperature low threshold crossed - Trap ID:430 ........................................................................ 81
Laser Supply Voltage High Threshold Crossed - Trap ID:431.............................................................. 82
Laser supply voltage low threshold crossed - Trap ID:432 .................................................................... 83
Memory usage exceeded threshold - Trap ID:116 .................................................................................. 84
Onboard voltage generation lower threshold crossed - Trap ID:470 ................................................... 85
Onboard voltage generation upper threshold crossed - Trap ID:471 ................................................... 86
Program Fault, Software Failure - Trap ID:15......................................................................................... 87
Port Mirroring Active - Trap ID:688 ........................................................................................................ 87
Provisioning Disabled -FileSystem Full - Trap ID:542 ........................................................................... 88
Redundant pair communication failure - Trap ID:21 ............................................................................. 89
Routing table near capacity - Trap ID:685 ............................................................................................... 90
SFP Mismatch - Trap ID:359..................................................................................................................... 91
SFP missing or removed - Trap ID:489 ................................................................................................... 92
SFP Failure - Trap ID:490.......................................................................................................................... 93
SFP Unknown - Trap ID:491 .................................................................................................................... 94
Software Committing - Trap ID:32........................................................................................................... 95
Software Downloading ............................................................................................................................... 96
Software Download Failed - Trap ID:311................................................................................................ 97
Switch to Protecting Card - Trap ID:387 ................................................................................................. 98
Switched off/No Input Voltage - Trap ID:388 ....................................................................................... 99
SW version mismatch - Trap ID:19 ........................................................................................................ 100
Telecom Bus Allocation conflict - Trap ID:746 .................................................................................... 101
46
Uploading Config - Trap ID:117 ............................................................................................................. 102
Work Fan Failed - Trap ID:608 ............................................................................................................... 103
Chapter 4 Equipment Alarms
Bad checksum on configuration file - Trap ID:7

Use this procedure to clear the 'Bad checksum on configuration file' alarm.
Cause
This alarm is raised when the configuration file is modified or corrupt. This is due to improper
shutdown/restart of the node software.
Severity
Major
Object affected
Card
Impact
Traffic will be disrupted and will not be able to write to the configuration file.
Clearing Procedure
To clear this alarm,
1. Restore the configuration file.
2. Reboot the node.
If the alarm persists, contact the next level of support.
47
Bus Error - Trap ID:22

Use this procedure to clear the 'Bus Error' alarm.
Cause
This alarm is raised when the I2C device failed.
Severity
Minor
Object affected
Card
Impact
Traffic will be disrupted.
Clearing Procedure
1. Remove the faulty card.
2. Insert the new card.
If the alarm persists, contact next level of support.
48
Card jacked out - Trap ID:152

Use this procedure to clear the 'Card jacked out' alarm.
Cause
This alarm is raised when the card is jacked out.
Severity
Major
Object affected
Shelf
Impact
Card will not be functional and traffic will be disrupted.
Clearing Procedure
To clear this alarm, jack-in the card. If the alarm persists, contact next level of support.
49
Card mismatch - Trap ID:153

Use this procedure to clear the 'Card mismatch' alarm.
Cause
This alarm is raised when a slot is provisioned for a specific card and a different card is inserted.
Severity
Major
Object Affected
Card
Impact
The impact of this alarm is as follows:
The inserted (mismatched) card is not recognized by the node software and is not
provisionable.
The card that is configured initially in the inventory can be used for management operations
(for example, port and/or cross connection configuration) but the provisioning changes are
not reflected on the hardware and traffic will be down on any provisioned interfaces.
Clearing Procedure
1. Determine the slot against which the alarm is raised.
2. For the same type of cards, remove the card against which the alarm is raised and then go to
step 6.
3. For different type of cards, 'Card mismatch' alarm is cleared by deleting the card. To delete a
card,
4. Remove the card from the node and delete cross-connects relevant to that card.
5. Delete the card by using Delete Cards link on the Node Inventory preview pane.
6. The 'Card mismatch' alarm is cleared and the 'Card missing or removed see "Card missing
or removed - Trap ID:11" on page 51' alarm is raised.
7. Install the correct card in the slot. The 'Card missing or removed' alarm is cleared.
50
Card missing or removed - Trap ID:11

Use this procedure to clear the 'Card missing or removed' alarm.
Cause
This alarm is raised in following instances:
when a slot is provisioned for a specific card and it is not present in the corresponding slot
when card is not inserted securely to engage the backplane
when the control card backplane connectors are faulty
when the backplane is faulty
Severity
Major
Object Affected
Card
Impact
This alarm is traffic affecting.
Clearing Procedure
This alarm is cleared when the appropriate card is installed securely in the slot. To clear this
alarm, perform the steps given below:
1. If the card is missing from the provisioned slot, insert the card in the appropriate slot.
2. Verify that the card is inserted securely to engage the backplane.
3. Replace the faulty card.
If the problem persists, contact your next level of support.
51
Card not supported in this slot - Trap ID:676

Use this procedure to clear the 'Card not supported in this slot' alarm.
Cause
This alarm is raised after software upgrade, if the card present in the config is not supported any
longer by the upgraded software.
Severity
Critical
Object affected
Card
Impact
Card will not be functional.
Clearing Procedure
1. Remove the incorrect old card.
2. Delete the cross-connects associated with the old card.
3. Delete the image of the old card.
4. Insert the new card.
52
Card Unusable - Trap ID:618

Use this procedure to clear the 'Card Unusable' alarm.
Cause
This alarm is raised when:
A tributary protected card is installed without the corresponding IO panel being present in
the chassis.
On the protect card there is no tributary protection group provisioned in the node.
Severity
Major
Object affected
Card
Impact
Work card will not be usable unless an IO panel is installed and in case of protect card, it will not
be usable until it is added to some protection group.
Clearing Procedure
1. Insert the appropriate IO panel required.
2. Check if the alarm is cleared.
3. If alarm persists, create a tributary protection group in the allocated slot.
4. Check if the alarm is cleared. If the alarm persists, contact next level of support.
53
Circuit Pack Below Baseline - Trap ID:615

Use this procedure to clear the 'Circuit Pack Below Baseline' alarm.
Cause
This alarm is raised when the card has an older version of the CPLD, which is not supported by
the CPLD version of the base card.
Severity
Major
Object Affected
Card
Impact
Clearing Procedure
1. Determine the card against which the alarm is raised.
2. Check the CPLD version of the card.
3. Remove the card against which alarm is raised.
4. Check if the alarm is present. If the alarm persists, contact your next level of support, else
move to step 5.
5. Change the CPLD version of the card against which alarm occurred to the version supported
by the CPLD version of the base card.
6. Insert the card and check if the alarm is present.
54
Cold Restart Required: FPGA Changed - Trap ID:614

Use this procedure to clear the 'Cold Restart Required: FPGA Changed' alarm.
Cause
This alarm is raised during card initialization, if the FPGA version in the current software load is
higher than FPGA version on the card.
Severity
Major
Object affected
Card
Impact
Traffic might be disrupted.
Clearing Procedure
To clear this alarm, cold reboot the card. If the alarm persists, contact next level of support.
55
Connectivity Check Failed - Trap ID:658

Use this procedure to clear the 'Connectivity check failed' alarm.
Cause
This alarm is raised when a MEP receives no CCM frames from a peer MEP (MEP ID=i) during
an interval equal to 3 times the CCM transmission period.
Severity
Critical
Object Affected
MEP
Impact
Non-traffic affecting
Clearing Procedure
1. Check whether MEP is configured on the remote end or not.
2. Check the link status of the member ports of VLAN, on which MEP is created.
3. Alarm is cleared when MEP receives three frame in three consecutive CCM periods.
56
Config Downloading - Trap ID:23

Use this procedure to clear the 'Config Downloading' alarm.
Cause
This alarm is raised when the command to download config is executed.
Severity
Minor
Object affected
Card
Impact
No impact
Clearing Procedure
1. Wait for the config to be downloaded completely.
2. Reboot the card.
57
Config out of sync - Trap ID:20

Use this procedure to clear the 'Config out of sync' alarm.
Cause
This alarm is raised when the config file on the two control cards are not in sync.
Severity
Minor
Object affected
Card
Impact
Clearing Procedure
To clear this alarm, update the config files on the control cards to be the same.
58
Database is corrupted/improper - Trap ID:861

Use this procedure to clear the 'Database is corrupted/improper' alarm.
Cause
This alarm is raised when the network element detects a corrupted configuration file while
rebooting or booting the element. This occurs when the checksum calculated on restart does not
match the checksum stored previous to the restart.
Severity
Major
Objects Affected
Node
Impact
The impact of this alarm is traffic affecting.
Clearing Procedure
To clear this alarm, perform warm reset to the network element
59
Database Restore Failed - Trap ID:579

Use this procedure to clear the 'Database Restore Failed' alarm.
Cause
This alarm is raised when download of configuration database of node has failed.
Severity
Major
Objects Affected
Card
Impact
Non-service affecting
Clearing Procedure
2. Restore the network element configuration data successfully.
60
Database Save Failed - Trap ID:547

Use this procedure to clear the 'Database Save Failed' alarm.
Cause
This alarm is raised when back-up operation of node configuration is failed.
Severity
Major
Object Affected
Card
Impact
The impact of this alarm is non-service affecting.
Clearing Procedure
2. Take the successful backup of the node configuration.
61
DCN Failure - Trap ID:473

Use this procedure to clear the 'DCN Failure' alarm.
Cause
The alarm is raised on the port where IBC is provisioned. This alarm is raised when the in-band
communication (IBC) or embedded communication channel (ECC) interface is not receiving the
packets from the far end node because of:
higher priority alarm such as Loss of Signal, Loss of Frame, AIS on the STM/OC port
existing on the interface
mismatch in the ECC byte selection between the interfaces at the near end and the far end
nodes
when there is a DCN protocol mismatch existing between the near end and far end nodes
Severity
Major
Object Affected
Network Interface
Impact
The impacts of this alarm are as follows:
Loss of management connectivity over IBC on unprotected paths
Temporary loss of management connectivity over IBC on the protected paths
Clearing Procedure
1. Check if there is mismatch in the ECC byte selected on the interfaces, both at the near end
and far end nodes.
2. Correct the mismatch, if detected. If the alarm persists, go to step 3.
3. Check for higher priority alarms raised on the STM/OC interface.
4. Perform appropriate procedure to clear the alarms if any. If the alarm persists, go to step 5.
5. Correct the mismatch in DCN protocol at near and far end by ensuring that protocol selected
at both ends on the communicating interface is same.
6. Check if the alarm cleared.
62
Derive Voltage High - Trap ID:201

Use this procedure to clear the 'Derived Voltage High' alarm.
Cause
This alarm is raised when the onboard voltage has crossed the upper threshold. This could be
due to:
faulty power supply unit
faulty backplane
Severity
Major
Object Affected
Card_PSU
Impact
The impact of this alarm may or may not be traffic affecting depending on the overload voltage
level.
Clearing Procedure
2. Replace the faulty card. If the alarm persists, replace the PSU.
3. Check if the alarm cleared. If the alarm persists, contact your next level of support.
63
Derived Voltage Low - Trap ID:369

Use this procedure to clear the 'Derived Voltage Low' alarm.
Cause
This alarm is raised when the onboard voltage has gone below the lower threshold. This could be
due to:
faulty backplane
Severity
Major
Object Affected
Card_PSU
Impact
The impact of this alarm may or may not be traffic affecting depending on the underload voltage
level.
Clearing Procedure
2. Replace the faulty card. If the alarm persists, replace the PSU.
3. Check if the alarm cleared. If the alarm persists, contact your next level of support.
64
Documentation Version Mismatch / Invalid with Software

Version - Trap ID:595
Use this procedure to clear the 'Documentation version mismatch/invalid with the software version' alarm.
Cause
This alarm is raised when the current documentation version of node is not supported by
running software.
Severity Level
Minor
Object Affected
Card
Impact
The impact of this alarm is that documentation displayed on the node may not be accurate.
Clearing Procedure
1. Upgrade the documentation of the node to correct documentation version.
2. Check for the 'Documentation version mismatch/invalid with the software version' alarm on local node.
3. Check if alarm is cleared. If the alarm persists, contact your next level of support.
65
EEPROM Failure - Trap ID:17

Use this procedure to clear the 'EEPROM Failure' alarm.
Cause
This alarm is raised when the serial EPROM could not be read.
Severity
Major
Object affected
Card
Impact
Card will not come up or the traffic will be disrupted.
Clearing Procedure
1. Remove the faulty EEPROM.
2. Replace with a readable EPROM.
66
External Alarm Occurred - Trap ID:224

Use this procedure to clear the 'External Alarm occurred' alarm.
Cause
This alarm is raised when the external alarm is triggered.
Severity
Critical
Object Affected
External alarm
Impact
The impact of this alarm is dependent on the cause of the external alarm.
Clearing Procedure
1. Check for the cause of the external alarm.
2. Rectify the cause of the external alarm. If the alarm persists, contact your next level of
support.
67
Factory Defaults Restored - Trap ID:682

Use this procedure to clear the 'Factory Defaults Restored' alarm.
Cause
This alarm is raised when you perform a restore factory defaults operation.
Severity
Minor
Object affected
Node
Impact
The objects with previous configuration will be deleted. The traffic will be disrupted.
Clearing Procedure
To clear this alarm, restart the node.
68
Fan Failed - Trap ID:434

Use this procedure to clear the 'Fan Failed' alarm.
Cause
This alarm is raised when the fan module is not operational. This could be because of:
clogged air filter
malfunctioning of the fan module
Node supports normal functioning on single fan failure. 'Fan Failed' alarm is raised if at least one
fan failure is detected.
Severity
Critical
Object Affected
Card
Impact
The impact of this alarm is overheating of the node, which may affect some of the functionalities
of the node.
Clearing Procedure
To clear this alarm, replace the air filter and/or the fan module. If the alarm persists, contact your
69
File System Almost Full - Trap ID:12

Use this procedure to clear the 'File system almost full' alarm.
Cause
the free space available is less than 10% of the total disk space.
disk checking program has detected bad blocks and these blocks may have been marked
unusable, thus reducing effective disk space.
Severity
Minor
Object Affected
Card
Impact
The impacts of this alarm are:
non-service affecting
configuration changes and alarm history may be lost
any new configuration changes added will not be updated/reflected
new alarms may not be reliably reported
Clearing Procedure
1. Check the disk memory usage.
2. Remove the unwanted files from the disk.
3. Launch the network element user interface session. If the alarm persists, contact your next
level of support.
70
FPGA Load Failure - Trap ID:18

Use this procedure to clear the 'FPGA Load Failure' alarm.
Cause
This alarm is raised when the FPGA on card could not be loaded.
Severity
Major
Object affected
Card
Impact
Clearing Procedure
To clear this alarm, upgrade with the correct FPGA on the card. If the alarm persists, contact
71
Hardware Failure - Trap ID:13

Use this procedure to clear the 'Hardware Failure' alarm.
Cause
This alarm is raised in following instances:
when there is a hardware problem with the card
when the backplane is faulty
Severity
Major
Object Affected
Card
Impact
Clearing Procedure
This alarm is cleared when the appropriate card is installed securely in the slot. To clear this
alarm,
2. Replace the faulty card. If the alarm persists, contact your next level of support.
72
Improper Card Jackin - Trap ID:695

Use this procedure to clear the 'Improper Card Jackin' alarm.
Cause
This alarm is raised when the ejector supported cards have ejectors in unlock state or the card
jackin is not proper.
Severity
Major
Object affected
Card
Impact
Card will not be functional. Traffic will be disrupted.
Clearing Procedure
1. Jack-out the card.
2. Jack-in the card properly.
3. Push the ejectors to lock state.
73
Input Voltage High on PSU Card - Trap ID:370

Use this procedure to clear the 'Input Voltage High on PSU Card' alarm.
Cause
This alarm is raised when the input voltage on PSU exceeds the provisioned voltage high
threshold.
Severity
Major
Object Affected
Card_PSU
Impact
The impact of this alarm may or may not be traffic affecting, depending on the overload voltage
level. A further increase in the input voltage level may result tripping of the PSU and the node
will switched off automatically.
Clearing Procedure
1. Measure the input voltage of the node with a voltmeter.
2. Reduce the input voltage to -48V, the ideal input voltage for PSU such that the input voltage
to the PSU is well within the normal operating voltage range.
74
Input Voltage Low On PSU Card - Trap ID:371

Use this procedure to clear the 'Input Voltage Low on PSU Card' alarm.
Cause
This alarm is raised when the input voltage on PSU falls below the provisioned voltage low
threshold. The optimum input voltage to the PSU is -48V. The normal operating voltage ranging
from -42V to -56V keeps the network element functional.
Severity
Major
Object Affected
Card_PSU
Impact
The impact of this alarm may or may not be traffic affecting, depending on the overload voltage
level. A further decrease in the input voltage level may result tripping of the PSU and the
network element will be switched off automatically.
Clearing Procedure
1. Measure the input voltage of the network element with a voltmeter
2. Increase the input voltage to -48V, the ideal input voltage for PSU. Such that the input
voltage to the PSU is well within the normal operating voltage range.
75
Intercard Communication Failure - Trap ID:378

Use this procedure to clear the 'Inter Card Communication failure' alarm.
Cause
This alarm is raised when the processor card is not able to establish connection with the standby
card or the intelligent line cards on the Node. This may be due to the rebooting of the other card.
Severity
Minor
Object Affected
Card
Impact
This alarm is usually not traffic affecting but may result in traffic outage if protection switch is
initiated when this alarm is present on the line cards.
Clearing Procedure
1. Check whether the card on which the alarm is present is inserted properly in the slot.
2. If not, insert the card properly into the slot.
3. Give a warm restart to the Node. If the alarm persists, contact your next level of support.
76
Intercard Suspected - Trap ID:607

Use this procedure to clear the 'Intercard Suspected' alarm.
Cause
This alarm is raised when any of the processor card, Tributary card or the backplane is faulty. For
faults which cannot be localized to a particular card, 'Intercard Suspected' alarm will be raised on
both the cards: the card on which the failure is reported and the card that generated the failed
signal.
Severity
Major
Object Affected
Card
Impact
The impact of this alarm may be traffic affecting.
Clearing Procedure
1. Check for the alarm on the faulty card.
2. Replace the faulty card. If the alarm persists, contact your next level of support.
77
Laser Failure - Trap ID:24

Use this procedure to clear the 'Laser Failure' alarm.
Cause
This alarm is raised when SFP/XFP is faulty.
Severity
Major
Object Affected
Port
Impact
Clearing Procedure
To clear this alarm, replace the SFP/XFP.
78
LAN Port Down - Trap ID:384

Use this procedure to clear the 'LAN Port Down' alarm.
Cause
LAN Ethernet port is down
Ethernet cable is disconnected
Ethernet cable is defective
Ethernet port on the Ethernet hub, router or switch is down or defective
Severity
Major
Object Affected
Network Interface
Impact
If the node is configured as a gateway node, there will be a loss of management connectivity from
this node and all nodes managed through this gateway will be unmanageable.
Clearing Procedure
1. Check that the LAN cable is connected correctly to the node.
2. Check that the LAN cable is connected correctly to the Ethernet hub/transceiver.
3. If persists, replace the LAN cable.
4. If persists, check that the port on the Ethernet router or switch is enabled and correctly
provisioned.
5. Check if the alarm is cleared. If the alarm still persists, contact your next level of support.
79
Laser Temperature High Threshold Crossed - Trap ID:429

Use this procedure to clear 'Laser temperature high threshold crossed' alarm.
Cause
This alarm is raised when SFP is faulty or Fan module is not working, and the temperature of
node itself is too high, it crosses laser temperature high threshold limit (lower temperature limit is
-42C and high temperature 125C).
Severity Level
Major
Object Affected
Port
Impact
Clearing Procedure
1. Ensure that environmental temperature is within the operating range of the node.
2. Check for the 'Laser temperature high threshold' alarm.
If the alarm clears, the procedure is complete.
If the alarm persists, replace the SFP/XFP. Check for the 'Laser temperature high
threshold' alarm.
80
Laser temperature low threshold crossed - Trap ID:430

Use this procedure to clear the 'Laser temperature low threshold crossed' alarm.
Cause
This alarm is raised when SFP/XFP is faulty or temperature of the node itself is too low so that
it is crossing the lower operational limits of SFP/XFP working.
Severity
Major
Object Affected
Port
Impact
Impact of this alarm is traffic affecting.
Clearing Procedure
1. Ensure that environmental temperature is within the operating range of the node.
2. Check for the 'Laser temperature low threshold' alarm.
If the alarm persists, replace the SFP/XFP. Check for the 'Laser temperature low
threshold' alarm.
81
Laser Supply Voltage High Threshold Crossed - Trap

ID:431
Use this procedure to clear the 'Laser supply voltage high threshold crossed' alarm.
Cause
This alarm is raised when the supplied voltage to SFP/XFP module from the on board power
supply of the card is higher than high threshold limits.
Severity
Major
Object Affected
Port
Impact
The SFP/XFP transmit power may get affected or lead to SFP/XFP failure. The optical receiver
on remote system might be damaged, which will affect the traffic.
Clearing Procedure
1. Check if 'Laser supply voltage high threshold crossed' alarm exists on the cards.
2. If the alarm is reported, clear the alarm by replacing the PSU.
3. Check for the 'Laser supply voltage high threshold' alarm again. If the alarm persists, contact your
82
Laser supply voltage low threshold crossed - Trap ID:432

Use this procedure to clear the 'Laser supply voltage low threshold' alarm.
Cause
This alarm is raised when the supplied voltage to SFP/XFP module from the on board power
supply of the card is lower than low threshold limits.
Severity Level
Major
Object Affected
Port
Impact
The SFP/XFP transmit power may get affected leading to SFP/XFP failure. LOS may be raised
on the remote system, which is traffic affecting.
Clearing Procedure
1. Check if 'Laser supply voltage low threshold' alarm exists on the cards.
2. If the alarm is reported, clear the alarm by replacing the PSU.
3. Check for the 'Laser supply voltage low threshold' alarm again. If the alarm persists, contact your
83
Memory usage exceeded threshold - Trap ID:116

Use this procedure to clear the 'Memory Usage exceeded threshold' alarm.
Cause
This alarm is raised when the physical memory (RAM) usage exceeds 90% of the available
capacity.
Severity
Minor
Object affected
Card
Impact
Impacts of this alarm are:
non-service affecting
any new configuration changes will not be updated/reflected
performance data will not be updated
Clearing Procedure
This alarm will be cleared when memory usage falls below the threshold limit of 90% of the
available capacity.

1. Perform a non-service disruptive reset (warm reboot) on the node.
2. Launch the network element user interface session after the restart. If the alarm persists,
contact your next level of support.
84
Onboard voltage generation lower threshold crossed - Trap

ID:470
Use this procedure to clear the 'Onboard Voltage Generation lower threshold crossed' alarm.
Cause
This alarm is raised when the onboard voltage has crossed the lower threshold. This could be due
to:
faulty card
faulty backplane
Severity
Major
Object affected
Card
Impact
The impact of this alarm may or may not be traffic affecting, depending on the underload voltage
level.
Clearing Procedure
1. Determine the card against which the alarm is raised and replace the faulty card
2. Replace the PSU
85
Onboard voltage generation upper threshold crossed - Trap

ID:471
Use this procedure to clear the 'Onboard voltage generation upper threshold crossed' alarm.
Cause
This alarm is raised when the onboard voltage has crossed the upper threshold. This could be
due to:
faulty card
faulty backplane
Severity
Major
Object affected
Card
Impact
Depending on the overload voltage level, the impact of this alarm may or may not be traffic
affecting.
Clearing Procedure
2. Replace the faulty card.
3. If the alarm persists, replace the PSU. If the alarm persists, contact your next level of support.
86
Program Fault, Software Failure - Trap ID:15

Use this procedure to clear 'Program Fault, Software Failure' alarm.
Cause
This alarm is raised when software is unable to open the devices to access.
Severity
Major
Object affected
Card
Impact
Card will not work properly.
Clearing Procedure
Reboot the card on which the 'Program Fault, Software Failure' alarm is raised. If the alarm persists,
Port Mirroring Active - Trap ID:688

Use this procedure to clear the 'Port Mirroring Active' alarm.
Cause
Port Mirroring Session is created.
Severity
Minor
Object affected
Data Port
Impact
The impact of this alarm is traffic affecting. Traffic from the source port will be mirrored on the
destination port.
Procedure
1. Check the Port Mirroring Alarm.
87
2. Delete the port mirroring session.

3. Alarm will get cleared once port mirroring session is deleted. If the alarm persists, contact the
Provisioning Disabled -FileSystem Full - Trap ID:542

Use this procedure to clear the 'Provisioning Disabled -File System Full' alarm.
Cause
This alarm is raised when the file space on disk is very low.
Severity
Critical
Object affected
Card
Impact
Provisioning is disabled since it can lead to configuration file being deleted or getting corrupt.
Clearing Procedure
To clear this alarm, free some space on disk by deleting unnecessary files.
If the problem persists, contact your next level of support.
88
Redundant pair communication failure - Trap ID:21

Use this procedure to clear the 'Redundant pair communication failure' alarm.
Cause
This alarm is raised when the redundant card is unable to communicate with the primary card.
Severity
Minor
Object affected
Card
Impact
Clearing Procedure
To clear this alarm, check if the primary card is active.
89
Routing table near capacity - Trap ID:685

Use this procedure to clear the 'Routing table near capacity' alarm.
Cause
This alarm is raised when the 'routing database' is high. The calculation of the alarm is dependent
on the number of routes present in the system.
Severity
Major
Object affected
Node
Impact
The impact of this alarm is non-traffic affecting.
Clearing Procedure
1. Plan the subnet and flood lesser routes to the node.
2. Check the routing table in OSPF through the node.
3. Reduce the number of routes being advertised to the node.
90
SFP Mismatch - Trap ID:359

Use this procedure to clear the 'SFP Mismatch' alarm.
Cause
This alarm is raised when there is a mismatch in the SFP rate, reach, and wavelength of the
inserted SFP/XFP and the expected SFP/XFP.
Severity
Critical
Object affected
SFP
Impact
This alarm is traffic affecting only if there is a line rate or wavelength mismatch. Traffic will be
down until you replace the SFP.
Clearing Procedure
1. Determine the SFP/XFP port against which the alarm is raised.
2. Remove the SFP/XFP.
3. Either insert an SFP with the SFP rate, reach, and wavelength as originally provisioned SFP
or insert a new SFP that is supported for the Tejas node
4. SFP mismatch alarm can also be cleared by deleting the SFP.
91
SFP missing or removed - Trap ID:489

Use this procedure to clear the 'SFP Missing or Removed' alarm.
Cause
This alarm is raised when the SFP/XFP pluggable is not in the slot.
Severity
Critical
Object affected
SFP
Impact
This alarm is traffic affecting. Traffic will be down until you replace the SFP/XFP.
Clearing Procedure
1. Insert the appropriate SFP/XFP in the allocated slot.
2. This alarm can also be cleared by deleting the SFP/XFP.
92
SFP Failure - Trap ID:490

Use this procedure to clear the 'SFP Failure' alarm.
Cause
This alarm is raised when a Small Form-factor Pluggable (SFP/XFP) optical transceiver module
provisioned on a card fails.
Severity
Critical
Object affected
SFP
Impact
Clearing Procedure
1. Identify the card and SFP/XFP port raising the alarm.
2. Replace the SFP/XFP optical transceiver module you identified.
93
SFP Unknown - Trap ID:491

Use this procedure to clear the 'SFP Unknown' alarm.
Cause
This alarm is raised when the SFP pluggable is from a non approved vendor.
Severity
Critical
Object affected
SFP
Impact
Clearing Procedure
1. Unplug the unapproved SFP.
2. Delete the entry of SFP.
3. Plug-in any approved SFP.
94
Software Committing - Trap ID:32

Use this procedure to clear the 'Software Committing' alarm.
Cause
This alarm is raised when the command to commit the software is executed.
Severity
Minor
Object affected
Card
Impact
Clearing Procedure
1. Wait for the software commit to be completed.
2. Reboot the card.
95
Software Downloading
This procedure provides information on the 'Software Downloading' alarm.
Cause
This alarm is raised in the event of an on going software download operation.
Severity
Minor
Object affected
Card
Impact
The impact of this alarm is that the management operations of the nodes using the same DCC
path may be slowed down.
Clearing Procedure
No action is necessary. This alarm is cleared automatically when the software download
operation is complete.
96
Software Download Failed - Trap ID:311

Use this procedure to clear the 'Software Download failed' alarm.
Cause
This alert is raised when the file transfer protocol (FTP) for the software download from the
server fails. The FTP failure could be because of :
IP connectivity problems to the server
user authentication failure
access restrictions on the specified location
FTP timed out
low disk space
Severity
Minor
Object affected
Card
Impact
Clearing Procedure
To clear this alarm, ensure that:
the IP connectivity to the server is correct
the software load file is present on the server
you have a valid User Name and Password and the appropriate access privilege
the node has enough disk space to download the software
97
Switch to Protecting Card - Trap ID:387

Use this procedure to clear the 'Switch to protecting card' alarm.
Cause
This alarm is raised when a fault is detected on protected card.
Severity
Minor
Object Affected
Impact
Services will be impacted if the protecting card is failed.
Clearing Procedure
This alarm is cleared when the traffic switches to protecting card.

1. Determine the protected card against which the alarm is raised.
2. Rectify the issues with the protected card.
98
Switched off/No Input Voltage - Trap ID:388

Use this procedure to clear the 'Switched off/No Input Voltage' alarm.
Cause
This alarm is raised when the redundant PSU card is present in the slot but no power is fed to it.
Severity
Major
Object affected
Card_PSU
Impact
None
Clearing Procedure
To clear this alarm, feed power to redundant PSU card or suppress the alarm using alarm-filtering
method.
To provision Alarm Filter,

1. In the WUI, click Faults > Alarm Filters in the navigation pane.
2. Click on Provision a new alarm filter and change the following field values:
For Alarm Class, select the value as 'Card'.
For Type, select the PSU/PFU on which alarm is coming.
For Alarm, select 'All'.
For Name, enter a user defined name.
3. Click on Create button.
99
SW version mismatch - Trap ID:19

Use this procedure to clear the 'SW version mismatch' alarm.
Cause
This alarm is raised when the node has software version that is not compatible with the hardware.
Severity
Minor
Object affected
Card
Impact
Clearing Procedure
1. Install the correct version of the software for the node.
2. Reboot the node.
100
Telecom Bus Allocation conflict - Trap ID:746

Use this procedure to clear the 'Telecombus Allocation conflict' alarm.
Cause
This alarm is raised whenever any telecom bus allocation errors are detected.
Severity
Critical
Object affected
Card
Impact
Clearing Procedure
1. Delete all the faulty cross-connects.
2. Reboot the node.
101
Uploading Config - Trap ID:117

Use this procedure to clear the 'Uploading Config' alarm.
Cause
This alarm is raised when the configuration backup operation is in progress.
Severity
Warning
Object affected
Card
Impact
No impact
Clearing Procedure
To clear this alarm, wait for the configuration backup to be completed.
102
Work Fan Failed - Trap ID:608

Use this procedure to clear the 'Work Fan Failed' alarm.
Cause
This alarm is raised when the work fan on the card has failed.
Severity
Major
Object affected
Card
Impact
No impact if only one of the work fan fails. The network element will shutdown if multiple fans
fail.
Clearing Procedure
1. Remove the work fan from the card.
2. Replace the work fan on the card with a new fan.
103
Chapter 5
Facility Alarms
This chapter describes Facility alarms raised on Tejas Node and procedure to clear them.
105
IN THIS CHAPTER
Alarm Indication Signal (AIS) on STM/OCn Port - Trap ID:30 ........................................................ 107
Alarm Indication Signal (AIS) on AU/STS - Trap ID:352 .................................................................. 108
Alarm Alarm
Clearing Indication Signal
Procedures (AIS) on TU/VT
Document ID: - Trap ID:362 .................................................................... 109
999-DOC000005-E
Alarm Indication Signal (Terminating) - Trap ID:487 .......................................................................... 111
Alarm Indication Signal on Port_PDH - Trap ID:540 ......................................................................... 112
Alarm Indication Signal Generated on Port_PDH - Trap ID:767 ...................................................... 113
ALS Triggered - Laser Is Shutdown - Trap ID:25................................................................................. 114
APS PDU Not Received - Trap ID:667 ................................................................................................. 115
APS/MSP Channel mismatch failure - Trap ID:315 ............................................................................ 116
APS/MSP Mode mismatch failure - Trap ID:314................................................................................. 117
APS/MSP Protect Switch Byte failure - Trap ID:316........................................................................... 118
APS/MSP Far End Protect Line Failure - Trap ID:317....................................................................... 119
Auto Negotiation Failed - Trap ID:516 .................................................................................................. 120
SFP Auto Provision Mismatch - Trap ID:360 ....................................................................................... 121
BER Threshold exceeded for Signal Degrade - Trap ID:381 .............................................................. 122
BER Threshold exceeded on Section for Signal Degrade - Trap ID:480 ........................................... 123
BER Threshold exceeded on Far End Line for Signal Degrade - Trap ID:482 ................................ 124
BER Threshold Exceeded for Signal Failure (B1) - Trap ID:115 ....................................................... 125
BER Threshold Exceeded for Signal Failure (B2) - Trap ID:115 ....................................................... 126
BER Threshold Exceeded on Section for Signal Failure - Trap ID:479............................................. 127
BER Threshold Exceeded on Far End Line for Signal Failure - Trap ID:481 .................................. 128
Communication Link Failure - Trap ID:598 .......................................................................................... 129
Connectivity Check Failed - Trap ID:658 .............................................................................................. 130
Excessive Error on AU/STS - Trap ID:390 .......................................................................................... 131
Excessive Error on TU/VT - Trap ID:391............................................................................................ 132
Excessive Error Ratio (Ethernet Port) - Trap ID:518 .......................................................................... 133
Excessive Error Ratio (VCG Port) - Trap ID:495 ................................................................................ 134
Far End Client Signal Failure - Trap ID:409 .......................................................................................... 135
Far End Excessive Error on AU/STS - Trap ID:484........................................................................... 136
Far End Excessive Error on TU/VT - Trap ID:486 ............................................................................ 137
Far End Protection Line Failure - Trap ID:444 .................................................................................... 138
Far End Signal Degrade on AU/STS - Trap ID:483 ............................................................................ 139
Far End Signal Degrade on TU/VT - Trap ID:485 .............................................................................. 140
Firmware version mismatch/invalid with software version - Trap ID:594 ........................................ 141
Forced Switch Active ................................................................................................................................ 142
Group Identifier Mismatch-LCAS - Trap ID:610 ................................................................................. 144
Out of Frame (OOF) - Trap ID:29 ......................................................................................................... 145
Laser Bias current lower threshold crossed - Trap ID:394................................................................... 146
Laser Bias Voltage Upper Threshold Crossed - Trap ID:395 .............................................................. 147
LCAS Mode Mismatch - Trap ID:405 .................................................................................................... 148
Line/MS DCC Link Failure - Trap ID:597 ............................................................................................ 149
Link Down On Ethernet - Trap ID:305................................................................................................. 150
Link Down on VCG - Trap ID:493 ........................................................................................................ 151
Link Integrity ON - Trap ID:402 ............................................................................................................ 152
Lockout Active - Trap ID: ....................................................................................................................... 153
Loopback Active-Facility - Trap ID:377 ................................................................................................ 154
Loopback Active-Terminal - Trap ID:361 ............................................................................................. 155
Loss of Frame (LOF) - Trap ID:28......................................................................................................... 157
Loss of Frame Delineation - Trap ID:410 ............................................................................................. 158
Loss of Frame on Port_PDH - Trap ID:541 ......................................................................................... 159
Loss of Multiframe on AU/STS - Trap ID:104 .................................................................................... 160
Loss of Multiframe on Port_PDH - Trap ID:536 ................................................................................. 161
Loss of Pointer on AU/STS - Trap ID:354 ........................................................................................... 162
Loss of Pointer on TU/VT - Trap ID:364 ............................................................................................ 163
Loss of Signal on STM/OC Port - Trap ID:27 ..................................................................................... 164
Loss Of Signal on PDH port - Trap ID:202 .......................................................................................... 165
Loss of VCAT Multiframe - Trap ID:50 ................................................................................................ 166
Manual Switch Active ............................................................................................................................... 167
Manual Switch Fail .................................................................................................................................... 169
NTP Server Unreachable - Trap ID:535 ................................................................................................ 170
Path Label Mismatch on AU/STS - Trap ID:357 ................................................................................. 171
Path Label Mismatch on TU/VT - Trap ID:367................................................................................... 172
Protection Switch Active .......................................................................................................................... 173
106
Protection Switching is Incomplete - Trap ID:669 ............................................................................... 174
Protection Channel Match Fail - Trap ID:442 ....................................................................................... 175
Protection mode mismatch - Trap ID:441 ............................................................................................. 176
Protection Switch Byte Fail - Trap ID:443 ............................................................................................. 177
Received Power Lower Threshold Crossed - Trap ID:400 .................................................................. 178
Chapter 5 Facility Alarms
Alarm Indication Signal (AIS) on STM/OCn Port - Trap

ID:30
Use this procedure to clear the 'Alarm Indication Signal' alarm on STM/OCn Port.
Cause
The Alarm Indication Signal (AIS) is detected in the K2 byte in the multiplexer section overhead
indicating a failure at the far end node. The Alarm Indication Signal on STM/OCn Port is
generated in the downstream nodes.
NOTE: AIS on STM/OCn Port is not intentionally generated by the network element,
however the alarm is reported at the local network element as a consequence of an AIS on the
STM/OCn port existing at the far end network element.
Severity
Critical
Object Affected
STM/OC Port
Impact
traffic affecting on unprotected paths
temporary traffic hit if path is switched to the protect path
AIS on AU/STS/TU/VT propagated downstream depending on the level of cross
connections provisioned
RDI on STM/OCn port propagated upstream
Clearing Procedure
1. Use the network connection information to identify the transmit and receive ends of the
alarm signal.
2. Log in to the network element at the transmit end.
3. Retrieve all active alarms from the transmit end
4. Look for alarm message for the STM/OCn port connected to the local network element. If
there is LoS at regenerator level there will be AIS on STM/OCn port
5. Clear the alarm using the appropriate procedures
107
Alarm Indication Signal (AIS) on AU/STS - Trap ID:352

Use this procedure to clear the 'Alarm Indication Signal' alarm on AU/STS.
Cause
This alarm is raised when a higher priority alarm such as Loss of Signal, Loss of Frame, MS-AIS,
AU/STS-LOP exists on an upstream neighboring node having AU level cross-connects on the
same path.
Severity
Major
Object Affected
AU/STS
Impact
temporary traffic hit if path is switched to the protecting aggregate
AIS on AU/STS propagated downstream depending on AU/STS level cross-connects
provisioned
RDI propagated upstream
Clearing Procedure
1. Retrieve all active alarms from the local node.
2. Verify if there are alarms of higher order. Clear alarms of higher order on the hierarchy first
using the appropriate procedures.
3. Check if 'AIS' alarm on AU/STS is cleared at the local node.
If AIS is cleared, the procedure is complete.
If AIS persists, go to step 4.
alarm signal.
5. Log-in to the node at the transmit end.
6. Retrieve all active alarms from the transmit end.
108
9. Log into each of the pass-through nodes and retrieve the active alarms.
If AIS persists, contact your next level of support.
Alarm Indication Signal (AIS) on TU/VT - Trap ID:362

Use this procedure to clear the 'Alarm Indication Signal' alarm on TU/VT.
Cause
This alarm is raised on TU/VT when a higher priority alarm such as Loss of Signal, Loss of
Frame, AIS on STM/OCn port/AU/STS/TU/VT, TIM (with TIM action set to downstream
AIS) or Signal label mismatch (with Signal label mismatch action set to downstream AIS) exists
on an upstream neighboring node.
Severity
Major
Object Affected
TU/VT
Impact
AIS on TU/VT or PDH port propagated downstream depending on the level of cross
RDI on TU/VT propagated upstream
Clearing Procedure
109
2. Verify if there are alarms of higher order. Clear alarms of higher order (Loss of Signal, Loss
of frame, AU-LOP, AU-AIS, TU-LOP) on the hierarchy first using the appropriate
procedures.
3. Check if 'AIS' alarm on TU/VT is cleared at the near end.
alarm signal.
8. Check if 'AIS' alarm on TU/VT is cleared at the local node.
9. Log into each of the pass-through nodes and retrieve the active alarms.
11. Check if 'AIS' alarm on TU/VT is cleared at the local node.
If alarm is cleared, the procedure is complete.
110
Alarm Indication Signal (Terminating) - Trap ID:487

Use this procedure to clear the 'Alarm Indication Signal (Terminating)' alarm.
Cause
This alarm is raised in the following scenarios.
When there is a higher priority alarm such as Loss of Signal, Loss of Frame, AIS on VT, TIM
(with TIM action set to downstream AIS), Signal label mismatch (with Signal label mismatch
action set to downstream AIS) exists on an upstream neighboring node.
On receiving a signal label as Unequipped on the lower or higher order path and the
consequent action on receiving Unequipped is set to downstream AIS.
Severity
Major
Object Affected
TU/VT
Impact
AIS on TU/VT or PDH port propagated downstream depending on the level of cross
RDI on TU/VT propogated upstream
Clearing Procedure
2. Clear alarms of higher order on the hierarchy first using the appropriate procedures.
3. Check if the alarm is cleared at the near end.
If the alarm is cleared, the procedure is complete.
If the alarm persists, go to step 4
alarm signal.
7. Clear alarms of higher order on the hierarchy first using the appropriate procedures.
111
8. Clear the TIM or PLM alarm on TU/VT at the far end network element with appropriate
procedure. If the alarm persists, go to step 9.
9. Check if the 'Alarm Indication Signal (Terminating)' alarm is cleared at the local node
10. Log into each of the pass-through network elements and retrieve the active alarms
12. Check if the alarm is cleared at the local node.
Alarm Indication Signal on Port_PDH - Trap ID:540

Use this procedure to clear 'Alarm Indication Signal' alarm on Port_PDH.
Cause
incoming Port_PDH signal has AIS
STM/OC traffic is not present (if any fault condition is present in SDH/SONET side then
AIS will be reported on Port_PDH).
Severity
Major
Object Affected
Port_PDH
Impact
Due to this alarm, E1/DS1 traffic will be down.
Clearing Procedure
1. Check the incoming E1/DS1 signal with a tester.
If AIS condition is detected, perform the necessary steps to rectify the condition
on the source signal. Go to step 3.
If AIS condition is not detected, trace and verify that the proper cable is
connected to the E1/DS1 service interface. Go to step 3.
2. Check if 'AIS' alarm on E1/DS1 port is cleared at the local node.
112
Alarm Indication Signal Generated on Port_PDH - Trap

ID:767
Use this procedure to clear the 'Alarm Indication Signal Generated on Port' alarm on Port_PDH
Cause
This alarm is raised when there is LoS on Port_PDH.
Severity
Major
Object Affected
Port_PDH
Impact
Due to this alarm, E1/DS1 traffic will be down.
Clearing Procedure
1. Check for the faulty E1/DS1 port and also the incoming E1/DS1 signal with a tester.
2. If AIS generated on port condition is detected, do one of the following:
Perform the necessary steps to rectify the condition on the source signal
Trace and verify that the proper cable is connected to the E1/DS1 service
interface
3. Check if 'AIS' alarm on E1/DS1 port is cleared at the local node.
113
ALS Triggered - Laser Is Shutdown - Trap ID:25

Use this procedure to clear the 'ALS Triggered - Laser is shutdown' alarm.
Cause
This alarm is raised when there is 'Loss of Signal' alarm on a port on which ALS is enabled.
Severity
Major
Object Affected
Port
Impact
The impact of this alarm is that traffic through the respective port gets affected.
Clearing Procedure
1. Check for 'Loss of Signal' alarm on near end node.
If the alarm is reported, clear the alarm with appropriate procedures and then go
to step 3.
If the alarm is not reported, contact your next level of support.
2. Check if the 'ALS Triggered - Laser is shutdown' alarm is cleared at the local node.
114
APS PDU Not Received - Trap ID:667

Use this procedure to clear the 'APS PDU Not Received' alarm on a tunnel group.
Cause
This alarm is raised when APS PDU is not received on the protect tunnel of a protected tunnel
group.
Severity
Critical
Object Affected
Protection Group
Impact
Protection switching cannot be performed on a protected tunnel group if work path goes
down, causing traffic to be hit.
It could also detect mis-configuration, if incorrect parameters were specified during tunnel
creation.
Clearing Procedure
1. Check if any CCM alarm is present on protect tunnel.
2. Verify if far end tunnel group is in protected mode. If not, delete existing tunnel group and
create new protected tunnel group at far end.
3. Verify if far end protect tunnel is created. If not, create protect tunnel and wait for 10
seconds to get the alarm cleared.
115
APS/MSP Channel mismatch failure - Trap ID:315

Use this procedure to clear the 'APS/MSP Channel mismatch failure' alarm.
Cause
This alarm is raised when the channel number in the received K2 byte is different from that in
the transmitted K1 byte. This can happen due to improper fiber connections. This alarm is
applicable only if the node is in APS/MSP configuration.
Severity
Minor
Object Affected
APS/MSP Group
Impact
This alarm is not traffic affecting.
Clearing Procedure
To clear the alarm, ensure that fiber connections are done properly.
116
APS/MSP Mode mismatch failure - Trap ID:314

Use this procedure to clear the 'APS/MSP Mode mismatch failure' alarm.
Cause
This alarm is raised when one of the node is configured for bidirectional APS/MSP and the other
node is in unidirectional APS/MSP.
Severity
Minor
Object Affected
APS/MSP Group
Impact
Impact of this alarm is non-service affecting.
Procedure
1. Check the APS/MSP configuration on far end node.
If APS/MSP is configured, go to step 3.
If APS/MSP is not configured, configure APS/MSP in the far end node. Go to
step 4.
2. Ensure that in the far end node and in the near end node, APS/MSP configuration is same,
either bidirectional or unidirectional.
3. Check for the 'APS/MSP Mode mismatch failure' alarm.
If the alarm persists. contact next level of support.
117
APS/MSP Protect Switch Byte failure - Trap ID:316

Use this procedure to clear the 'APS/MSP Protect Switch Byte failure' alarm.
Cause
This alarm is raised when one or more of the following conditions are present in the received K-
bytes:
inconsistent K-bytes
an invalid, unused, or inappropriate K-byte code
an invalid or unused channel number
A loss of K-byte continuity between far end and near end nodes may cause this alarm.
NOTE: This alarm is applicable only if the node is in MSP/APS configuration.
Severity
Minor
Object Affected
APS/MSP Group
Impact
Impact of this alarm is non-service affecting.
Procedure
To clear the alarm,
1. Check for the LOS/AIS alarms on the protect port.
If alarm is reported, clear the alarms by following the respective trouble clearing
procedure. Go to step 3.
If alarm is not reported, go to step 2.
2. Check the status of the cards and replace any failed card
3. Check for the 'APS/MSP Protect Switch Byte failure' alarm.
118
APS/MSP Far End Protect Line Failure - Trap ID:317

Use this procedure to clear the 'APS/MSP Far End Protection Line failure' alarm.
Cause
This alarm is raised when the K-byte receives protection line signal failure.
Severity
Minor
Object Affected
APS/MSP Group
Impact
The impact of this alarm is non-service affecting.
Clearing Procedure
1. Check the far end alarms on the protection line.
2. Perform the appropriate procedure to clear the alarm at the far end.
119
Auto Negotiation Failed - Trap ID:516

Use this procedure to clear the 'Auto Negotiation Failed' alarm.
Cause
This alarm is raised when the auto negotiation is enabled on the interface and the auto
negotiation protocol could not be completed due to a time-out. The probable cause could be
auto negotiation being enabled at the local node and disabled at the client equipment.
Severity
Critical
Object Affected
Ethernet Port
Impact
traffic affecting
associated cross connection status down
associated links down
Clearing Procedure
To clear the alarm,
1. Check if the auto negotiation feature is required on the link
If required, enable auto negotiation on both the client Ethernet interface and local
node Ethernet interface. Go to step 2
If not required, disable auto negotiation on both the client Ethernet interface and
local node Ethernet interface. Go to step .
2. Check if the 'Auto Negotiation Failed' alarm is cleared at the local node.
120
SFP Auto Provision Mismatch - Trap ID:360

Use this procedure to clear the 'SFP Auto Provision Mismatch' alarm.
Cause
This alarm is raised when there is a mismatch in the port capacity and the laser capacity of the
SFP/XFP.
Severity
Critical
Object affected
SFP/XFP
Impact
Applies to
This alarm is applicable to STM/OCn port.
Clearing Procedure
1. Make sure that there is no traffic through the node and then remove the SFP/XFP.
2. Delete the SFP/XFP object.
3. Insert a new SFP/XFP with the laser capacity same as the port capacity.
4. Check if the 'SFP Auto Provision Mismatch' alarm is cleared at the local node.
121
BER Threshold exceeded for Signal Degrade - Trap ID:381

Use this procedure to clear the 'BER Threshold exceeded for Signal Degrade' alarm.
Cause
This alarm is raised on STM/OC port when the bit error ratio (BER) exceeds the set signal
degrade (B2) threshold.
The probable causes for this alarm are:

faulty fiber or dirty fiber connector
faulty transmitter at far end node
faulty receiver at local node
faulty local node
Severity
Major
Objects Affected
STM/OC port
Impact
operation status of the associated cross connections degraded
traffic on the respective interface is in error
temporary traffic hit if path switched to protecting one in case of protected cross connections
Clearing Procedure
1. If the route is protected, ensure that the traffic is switched to the other aggregate port.
2. Clear the fiber bend (if any) and reconnect the fiber properly.
3. Clean the optical fiber.
4. Check if the received power lies in the optimum range. If the received optical power is within
the specified range, contact your next level of support.
5. Ensure that there are no damaged fiber connectors or fiber cuts of any kind.
6. Replace the SFP. If the alarm persists, contact your next level of support.
122
BER Threshold exceeded on Section for Signal Degrade -

Trap ID:480
Use this procedure to clear the 'BER Threshold exceeded on Section for Signal Degrade' alarm.
Cause
This alarm is raised on STM/OCn port when the bit error ratio (BER) exceeds the set signal
degrade (B1) threshold.

faulty local node
Severity
Major
Objects Affected
STM/OC Port
Impact
Clearing Procedure
the specified range, contact your next level of support.
5. Ensure that there are no damaged fiber connectors or fiber cuts of any kind.
123
BER Threshold exceeded on Far End Line for Signal

Degrade - Trap ID:482
Use this procedure to clear the 'BER Threshold exceeded on Far End Line for Signal Degrade' alarm.
Cause
This alarm is raised on STM/OCn port when the bit error ratio (BER) exceeds the set signal
degrade (B2) threshold. The probable causes for this alarm are:
faulty fiber (uncleaned fiber or fiber bend)
faulty receiver
Severity
Major
Objects Affected
STM/OCn Port
Impact
Clearing Procedure
the specified range, contact your next level of support
5. Ensure that there are no damaged fiber connectors or fiber cuts of any kind
124
BER Threshold Exceeded for Signal Failure (B1) - Trap

ID:115
Use this procedure to clear the 'BER Threshold exceeded for Signal Failure' (B1) alarm.
Cause
This alarm is raised on STM/OCn ports when the bit error ratio (BER) exceeds the set signal
failure (B1) threshold.
The probable causes of this alarm are:

faulty local node
Severity
Major
Object Affected
STM/OCn Port
Impact
Clearing Procedure
1. Ensure that the traffic is switched to the other aggregate port if the route is protected.
2. Clear the fiber bend (if any) and reconnect the fiber properly. Check for 'BER Threshold
Exceeded for Signal Failure (B1)' alarm.
4. If the received power lies in the optimum range, contact your next level of support or else go
to step 6.
5. Check if the transmitted power at the far end network element lies in the optimum range.
125
6. It indicates that SFP is faulty. Replace the SFP at the far end node. If the alarm persists,
BER Threshold Exceeded for Signal Failure (B2) - Trap

ID:115
Use this procedure to clear the 'BER Threshold Exceeded Signal Failure' (B2) alarm.
Cause

faulty local node
Severity
Major
Object Affected
STM/OCn port
Impact
Clearing Procedure
to step 6.
126
BER Threshold Exceeded on Section for Signal Failure -

Trap ID:479
Use this procedure to clear the 'BER Threshold Exceeded on Section for Signal Failure' (B1) alarm.
Cause

faulty local node
Severity
Major
Object Affected
STM/OCn Port
Impact
Clearing Procedure
Exceeded on Section for Signal Failure' alarm.
127
to step 6.
BER Threshold Exceeded on Far End Line for Signal

Failure - Trap ID:481
Use this procedure to clear the 'BER Threshold Exceeded on Far End Line for Signal Failure' alarm.
Cause
This alarm is raised on STM/OC ports when the bit error ratio (BER) exceeds the set signal

faulty receiver
Severity
Major
Object Affected
STM/OCn port
Impact
Clearing Procedure
128
to step 6.
6. It indicates that SFP is faulty. Replace the SFP at the far end network element. If the alarm
persists, contact your next level of support.
Communication Link Failure - Trap ID:598

Use this procedure to clear the 'Communication Link Failure' alarm.
Cause
This alarm is raised when the DCC communication has failed on F2, F3, F2F3, E1, or VC12
management channels. This failure may be due to:
Loss of signal or excessive errors on the optical link
Loss of signal or excessive errors on the E1 port, in case of E1 management
DCC not enabled or enabled on a different set of bytes or channels at the remote node
Remote end node is either faulty or in rebooting stage
There is a DCN Layer 2 protocol and parameters mismatch between near and far end nodes.
For example, near is provisioned for L2 protocol as 'PPP, HDLC Framing' and far end
provisioned as 'Standard PPP, RFC 1661'
NOTE: This failure may be a temporary problem due to the instability of the optical link or
remote node and would be corrected when the fault is repaired.
Severity
Major
Object Affected
Network Interface
Impact
This alarm is not traffic affecting, but may cause loss of management connectivity to the nodes
whose connectivity to the gateway goes through this link, if there is no DCC redundancy.
Clearing Procedure
1. Check for the fiber connectivity by sending trace identifier (J0 byte).
2. Verify the type of management channel being used in the network element. If the
management channel type is E1 then ensure that Admin status is up for the E1 port.
129
3. Ensure that same management channel is used for communication in the neighboring nodes.
4. Check for 'Communication Link Failure' on node. If the alarm persists, contact your next
level of support.
Connectivity Check Failed - Trap ID:658

Use this procedure to clear 'Connectivity Check Failed' alarm.
Cause
A MEP does not receive CCM frames from a peer MEP for an interval equal to 3 times the CCM
transmission period.
Severity
Critical
Object Affected
MEP
Clearing Procedure
1. Check whether the physical connectivity and Maintenance Association (MA) Domain is
proper on both sides.
2. Trigger a Loop back Message (LBM) to the remote MEP.
3. If there is no response, trigger a Link Trace Message (LTM) to the remote MEP to isolate the
fault.
4. At the remote end, check if all the associated entities have been enabled. If the alarm persists,
130
Excessive Error on AU/STS - Trap ID:390

Use this procedure to clear the 'Excessive Error' alarm on AU/STS.
Cause
This alarm is raised on AU/STS, when the bit error ratio (BER) of the VC-4 path BIP-8 error
rate exceeds the set signal fail (B3) threshold.
The probable causes are:

Severity
Major
Object Affected
AU/STS
Impact
operation status of the associated cross connections goes down
Clearing Procedure
2. Clear the fiber bend (if any) and reconnect the fiber properly. Check for 'Excessive Error on
AU (B3)' alarm.
4. Check if the received power lies in the optimum range. If not, it indicates that SFP is faulty.
Replace the SFP.
5. Check if the transmitted power at the far end network element lies in the optimum range. If
not, it indicates that SFP is faulty.
6. Replace the SFP at the far end node.
131
Excessive Error on TU/VT - Trap ID:391

Use this procedure to clear the 'Excessive Error' alarm on TU/VT.
Cause
This alarm is raised on TU/VT, when the BER of the BIP-2 (VC-12) or BIP-8 (VC-3) error rate
exceeds the set signal fail (V5) threshold.

faulty local node
Severity
Major
Object Affected
TU/VT
Impact
Clearing Procedure
2. Clear the fiber bend (if any) and reconnect the fiber properly. Check for 'Excessive Error on
TU (V5)' alarm.
4. Check if the received power lies in the optimum range. If not, it indicates that SFP is faulty.
Replace the SFP.
132
Excessive Error Ratio (Ethernet Port) - Trap ID:518

Use this procedure to clear the 'Excessive Error Ratio' alarm.
Cause
This alarm is raised on Ethernet ports when more than 1% of the total frames received at the
Ethernet port per second are errored for three consecutive seconds.
This is caused due to:

Faulty optical cable
Frames being received that are shorter than the minimum supported frame size of 64 bytes,
or frames being received which are longer than the MTU size which is provisioned on the
Ethernet port
Severity
Major
Object Affected
Ethernet port
Impact
operational status of the associated unprotected cross connections down
traffic on the respective interface in error
Clearing Procedure
1. Ensure that the Ethernet cable is connected properly.
2. Check if 'Excessive error ratio' alarm on Ethernet port is cleared at the near end node.
133
Excessive Error Ratio (VCG Port) - Trap ID:495

Use this procedure to clear the 'Excessive Error Ratio' alarm.
Cause
This alarm is raised on VCG ports when more than 1% of the total frames received at the VCG
port per second are errored for three consecutive seconds.
This may be due to:

faulty fiber or dirty connector
faulty receiver at local end node
Severity
Major
Object Affected
VCG
Impact
Clearing Procedure
1. Determine the port on which alarm is raised. Clear the fiber bend (if any) and reconnect the
fiber properly for that port.
2. Check for 'Excessive Error Ratio' alarm.
If the alarm persists, go to step 3.
4. Check if the 'Excessive Error Ratio' alarm is cleared at the local node.
5. Check if the received power lies in the optimum range.
If the received optical power is within the specified range, contact your next level
of support.
134
If the received optical power is not in the specified range, it indicates that
SFP/XFP is faulty. Replace the SFP/XFP.
6. Enable ALS at both ends of the optical fiber, if you have disabled the same while verifying
the Rx power.
7. Check if the 'Excessive Error Ratio' alarm is cleared at the local node.
If the alarm still persists, contact your next level of support.
Risk of laser radiation exposure: Before verifying the Receiver (Rx) power, disable ALS at
both ends of the optical fiber.
Far End Client Signal Failure - Trap ID:409

Use this procedure to clear the 'Far End Client Signal Failure' alarm.
Cause
This alarm is reported at the local node when the far end node detects a client signal failure
condition.
Severity
Major
Object Affected
VCG
Impact
The impact of this alarm is link down at the client end, which is traffic affecting
Clearing Procedure
1. Check the far end node for any alarms for the Ethernet port that could cause the reporting of
this alarm
2. If cause of this alarm detected, perform the appropriate procedure to clear the alarm at the
far end
135
Far End Excessive Error on AU/STS - Trap ID:484

Use this procedure to clear the 'Far End Excessive Error' alarm.
Cause
This alarm is raised on AU/STS, when the bit error ratio (BER) of the higher order path exceeds
the set Signal Fail BER threshold (B3).

faulty receiver
Severity
Major
Object Affected
AU/STS
Impact
temporary traffic hit if path switched to protecting one in case of protected cross
connections or MSP/APS protection scheme
Clearing Procedure
To clear the alarm,
1. If the route is protected, ensure that the traffic is switched to the protecting AU/STS
2. Clear the fiber bend (if any) and reconnect the fiber properly
3. Check for 'Far End Excessive Error' alarm
4. If alarm persists, clean the optical fiber
5. Check if the 'Far End Excessive Error' alarm is cleared.
6. If alarm persists, check if the received power lies in the optimum range. If the received
optical power is not in the specified range. Replace the SFP
7. Enable ALS at both ends of the optical fiber, if you have disabled it while verifying the Rx
power
8. Check if 'Far End Excessive Error' alarm is cleared
136
Far End Excessive Error on TU/VT - Trap ID:486

Use this procedure to clear the 'Far End Excessive Error' alarm.
Cause
This alarm is raised on the TU/VT object when the bit error ratio (BER) of the lower order path
exceeds the set Signal Fail BER threshold (V5).

faulty receiver
Severity
Major
Object Affected
TU/VT
Impact
connections or MSP/APS protection scheme
Clearing Procedure
To clear the alarm,
1. If the route is protected, ensure that the traffic is switched to the protecting AU/STS
3. Check for 'Far End Excessive Error' alarm
4. If the alarm persists, clean the optical fiber
5. Check if the 'Far End Excessive Error' alarm is cleared
6. If the alarm persists , check if the received power lies in the optimum range. If the received
optical power is not in the specified range. Replace the SFP
137
7. Enable ALS at both ends of the optical fiber, if you have disabled it while verifying the Rx
power
8. Check if 'Far End Excessive Error' alarm is cleared
Far End Protection Line Failure - Trap ID:444

Use this procedure to clear the 'Far End Protection Line Fail' alarm.
Cause
This alarm is raised when the K-byte receives protection line signal failure.
Severity
Major
Object Affected
STM/OCn port
Impact
Non-service affecting.
Clearing Procedure
1. Check the far end alarms on the protection line
2. Perform the appropriate procedure to clear the alarm at the far end node
138
Far End Signal Degrade on AU/STS - Trap ID:483

Use this procedure to clear the 'Far End Signal Degrade on AU/STS' alarm
Cause
This alarm is raised when the bit error ratio (BER) of the AU/STS path BIP-8 error rate exceeds
the set signal degrade threshold. The probable causes are:
faulty receiver
Severity
Major
Object affected
AU/STS
Impact
Clearing Procedure
1. If the path is protected, ensure that the traffic is switched to the other aggregate port
3. Clean the optical fiber
4. Check if the received power lies in the optimum range. If yes, contact your next level of
support
6. Check if the alarm is cleared at the local node. If not, it indicates that SFP is faulty. Replace
the SFP
139
Far End Signal Degrade on TU/VT - Trap ID:485

Use this procedure to clear the 'Far End Signal Degrade on TU/VT' alarm
Cause
This alarm is raised when the bit error ratio (BER) of the TU/VT path BIP-8 error rate exceeds
the set signal degrade threshold. The probable causes are:
faulty receiver
Severity
Major
Object affected
TU/VT
Impact
Clearing Procedure
1. If the path is protected, ensure that the traffic is switched to the other aggregate port
3. Clean the optical fiber
4. Check if the received power lies in the optimum range. If yes, contact your next level of
support
6. Check if the alarm is cleared at the local network element. If not, it indicates that SFP is
faulty. Replace the SFP
140
Firmware version mismatch/invalid with software version -

Trap ID:594
Use this procedure to clear the 'Firmware Version Mismatch/invalid With Software Version'
alarm.
Cause
This alarm is raised when the current firmware version of the network element is not supported
by the running software.
Severity
Minor
Object Affected
Card
Impact
The impact of this alarm is that some of the features may not be fully functional.
Clearing Procedure
1. Upgrade the correct firmware version which is compatible with the existing software
2. Check for 'Firmware Version Mismatch/invalid With Software Version' alarm at the near end
141
Forced Switch Active

Use this procedure to clear the 'Forced Switch Active' alarm.
Cause
This alarm is raised on both work and protect channel depending on whether the Force Switch is
applied to Work or Protect. This alarm will be raised on
a STM/OCn port, AU/STS, TU/VT, port PDH when User Forced Switch is applied on the
port
AU/STS, TU/VT when User Forced Switch is applied on the corresponding AU/STS port
any STM/OCn ports (if provisioned as part of a 1+1 MSP/APS), AU/STS and TU/VT (if
the STM/OCn port provisioned in SNCP/UPSR mode)
Impact
Traffic will switch to the path to which it is forced to.
Since Signal Fail or Equipment fail on protect is of higher priority, when Forced Switch is applied
to Work, the traffic switches back to work.
In MSP/APS, Signal Fail on protect has high priority than Force Switch, so Force Switch to
protect will not be allowed to occur.
Severity
Minor
Objects Affected
STM/OCn port - Trap ID:437
Port_PDH - Trap ID:447
AU/STS - Trap ID:453
TU/VT - Trap ID:459
Clearing Procedure
To clear this alarm on STM/OCn port,
1. Click Protection in the Navigation menu. Click MSP/APS groups link. The MSP/APS
groups page is displayed.
2. Click on the desired port under the Name field. The Protection provisioning page is
displayed.
3. Click Release and then click Confirm request. A success message is displayed.
4. If 'Forced Switch Active' alarm on STM port persists at the near end, contact your next
level of support
142
To clear this alarm on AU/STS,

1. Click Protection in the Navigation menu. Click Connections link. The Connections
protection request page is displayed.
2. Select the connection for protection request. Click Release. The Connections protection
request confirm page is displayed.
3. Click Confirm request. A success message is displayed.
4. If 'Forced Switch Active' alarm on AU persists at the near end, contact your next level of
support.
To clear this alarm on TU/VT,
1. Click Protection in the Navigation menu and then click Connections link. The Connections
4. If 'Forced Switch Active' alarm persists, contact your next level of support.
To clear this alarm on PDH port,
1. Click Protection in the Navigation menu and then click PDH port link. The Connections
4. If 'Forced Switch Active' alarm persists, contact your next level of support.
143
Group Identifier Mismatch-LCAS - Trap ID:610

Use this procedure to clear the 'Group Identifier Mismatch' alarm.
Cause
This alarm is raised when the VCG members are incorrectly mapped, i.e. VCG members on one
end are mapped to members of two different VCGs on the remote end.
Severity
Major
Object Affected
VCG
Impact
Impact of this alarm is that no traffic is transmitted from the interface.
Applies to
Ethernet cards
Clearing Procedure
1. Ensure that both the far end and near end network elements have the same numbers of VCs
provisioned
2. Create the same number of cross-connects on both the near and far end node. Also, check
the time slots used for the VCG associations are the same at both the near and far end node
3. Check for the alarms on all the VCG ports
4. Check if the alarm is cleared at the local node
5. Delete the wrongly connected cross connects
144
Out of Frame (OOF) - Trap ID:29

Use this procedure to clear the 'Out of Frame on STM/OCn Port' alarm.
Cause
This alarm is raised when the node detects a severely errored framing generated when the
incoming signal has a minimum of five consecutive errored framing patterns. This could be
because of the following reasons:
excessive attenuation
dirty optical fibers
dirty connectors
improper connector seating
excessive optical power received from the far end
mismatch in the capabilities (For example, STM4/16/64 line rate fiber inserted in STM1
receiver)
Severity
Critical
Object Affected
STM/OCn port
Impact
temporary traffic hit on the protected paths if the paths switched to aggregate containing the
alarm
Clearing Procedure
1. Identify the STM/OC port raising the alarm
2. Use an up-to-date fiber connection information to identify the transmit and receive sites of
the alarm signal
3. Retrieve all alarms at the transmit end. Clear any alarms of higher order by following the
appropriate procedure. Check for the 'Out of Frame' alarm on local node
4. Check the Rx power of the receiver to make sure it is above the Rx sensitivity
5. Ensure that received power at the local node is within the optimum range
6. Make sure the optical fibers are properly seated in the SFP
145
7. If the Rx attenuation is not adjustable, check the transmit power at the far end. If the
transmit power is within the Tx specification, the optical attenuation in between the two sites
is too high, the optical fiber connections are dirty or the optical fiber is damaged. Use the
appropriate company procedure to clean the optical fibers and connectors
8. Ensure that interfaces connected to each other are of same capacity
9. Ensure that there is no excessive bend on fibers. Check for the 'Loss of Frame' alarm on local
node
Laser Bias current lower threshold crossed - Trap ID:394

Use this procedure to clear the 'Laser Bias current lower threshold crossed' alarm.
Cause
This alarm is raised when the laser bias current goes below the lower threshold of the bias current
for the SFP type. This may happen when transmitter is degraded.
Severity
Major
Object Affected
Port
Impact
Clearing Procedure
This alarm will be cleared when the laser bias current is higher than the specified lower threshold
value. To clear this alarm, replace the SFP.
The alarm is raised when the SFP is freshly jacked in or the port is made admin up. Wait for
about a minute, it may get cleared by itself.
146
Laser Bias Voltage Upper Threshold Crossed - Trap ID:395

Use this procedure to clear the 'Laser Bias current upper threshold crossed' alarm.
Cause
This alarm is raised when the laser bias current crosses the upper threshold of the bias voltage for
the SFP type. This may happen when:
the temperature is high
transmitter has degraded
Severity
Major
Object Affected
Port
Impact
Clearing Procedure
The alarm will be cleared when the laser bias current comes below the specified upper threshold
value for that SFP. To clear this alarm, replace the SFP.
147
LCAS Mode Mismatch - Trap ID:405

Use this procedure to clear the 'LCAS Mode Mismatch' alarm.
Cause
This alarm is raised on a LCAS enabled VCG if it is detected that LCAS on remote VCG is
disabled.
Severity
Minor
Object Affected
VCG
Impact
Clearing Procedure
1. Check if LCAS mode is enabled for the corresponding VCG at the far end network element.
If LCAS mode is enabled, contact your next level of support, else goto Step 2.
2. Delete all the cross-connects associated to the VCG
3. Enable the LCAS mode
4. Create cross-connects as provisioned earlier
148
Line/MS DCC Link Failure - Trap ID:597

Use this procedure to clear the 'Line/MS DCC Link Failure' alarm.
Cause
This alarm is raised when DCC_M bytes are used on the DCC communication and either of the
following condition exists.
There is LOS/LOF/MS-AIS/Excessive error/Signal degrade alarm on the optical link
DCC byte is not provisioned on far end
DCC byte provisioned at far end is other than DCC_M
There is a DCN Layer 2 protocol and parameters mismatch between near and far end
network elements. For example, near is provisioned for L2 protocol as "PPP, HDLC
Framing" and far end provisioned as 'Standard PPP, RFC 1661' near end network element is
faulty
Far end node is faulty
This may be a temporary problem due to the instability of the optical link or remote node and
would be corrected when the fault is repaired.
Severity
Major
Object Affected
Network Interface
Impact
This alarm is non-traffic affecting and may result in the loss of management connectivity to the
nodes whose connectivity to the gateway goes through this link, if there is no Line/DCC
redundancy.
Clearing Procedure
1. Check for the LOS/LOF/MS-AIS/Excessive error/Signal degrade alarms on the optical
interface on which 'Line/MS DCC Link Failure' alarm is raised
2. Clear the reported alarm by following the respective trouble clearing procedure or else
contact your next level of support
3. Check for 'Line/MS DCC Link Failure' alarm on node
4. Check at the far end network element whether DCC byte is provisioned as DCC_M. If DCC
byte provisioned at far end node is other than DCC_M, provision it to DCC_M
149
Link Down On Ethernet - Trap ID:305

Use this procedure to clear the 'Link Down on Ethernet' alarm.
Cause
This alarm is raised in the following scenarios:
There is a faulty connection and/or there is a signal fail at client Ethernet source with link
integrity enabled at the local network element
There is a path break between the local network element and the client Ethernet source due
to missing or wrong cross-connections.
Auto negotiation failed between the network element and the client
Severity
Major
Object Affected
Data Port
Impact
This alarm is traffic affecting and may cause associated link to go down at the far end network
elements when Link Integrity enabled
Clearing Procedure
1. Check for the alarm on local VCG port. If the alarm is present, go to step 3
2. Ensure that local Ethernet port is admin up
3. Check if the alarm is present on local node
4. Ensure that auto negotiation is enabled on the local node
5. Check for the VCG related alarms on the local node Ethernet port
150
Link Down on VCG - Trap ID:493

Use this procedure to clear the 'Link Down On VCG' alarm.
Cause
This alarm is raised when there is a complete failure of VCG in at least one direction. This alarm
is reported as a consequence of any of the VCG related alarms such as:
Loss of Frame Delineation (LFD) on page 158
Total loss of capacity-Tx (TLCT) on page 209
Total Loss Of Capacity-Rx (TLCR) on page 186
Severity
Critical
Object Affected
VCG
Impact
Clearing Procedure
1. Check the local and far end network element for any VCG related alarms that could cause the
reporting of the 'Link down' alarm. If cause of Link down on VCG alarm is not detected,
contact your next level of support
2. Perform the appropriate procedure to clear the alarm at the far end. Check if the alarm is
cleared at the local network element
3. Ensure that the VC connections are provisioned correctly for the VCG at the local, pass-
through and far end network elements with the correct mapping structure
4. Ensure that matching time slots are provisioned on all the far end and pass-through network
elements. If the connections are provisioned correctly, contact your next level of support
5. Check if the 'Link Down On Ethernet on page 150' alarm is cleared at the local node
151
Link Integrity ON - Trap ID:402

Use this procedure to clear the 'Link Integrity ON' alarm.
Cause
This alarm is a consequent action on an Ethernet interface whenever the Link Integrity feature is
enabled on that interface and an error has occurred on the VCG.
Severity
Major
Object Affected
Ethernet port
Impact
Clearing Procedure
1. Check if the Link integrity option in enabled for the Ethernet port of the local node. If Link
integrity is disabled, contact your next level of support.
2. Check for the admin status of Ethernet port of far end node. If admin status is up, go to step
4.
3. Ensure that port is admin up. Check if the alarm is present on local node. If the alarm
persists, go to step 4.
4. Check if Link down/Auto negotiation failure alarm present on Ethernet port of far end node.
If any of these alarms exist, perform the appropriate procedure to clear the alarm at the far
end.
5. Check for the VCG related alarms on the associated local end network element's Ethernet
port.
If any alarm persists, contact your next level of support.
152
Lockout Active - Trap ID:

Use this procedure to clear the 'Lockout Active' alarm.
Cause
This alarm is raised when a lockout of protection is initiated on an STM/OCn or PDH ports.
Severity
Minor
Object Affected
TU/VT - Trap ID:458
Impact
The impact of this alarm can be service affecting if the working channel or port failed. This alarm
would be non-service affecting only if traffic is on the work path when the alarm is raised.
Clearing Procedure
1. After completion of maintenance, click Protection in the navigation menu.
2. Click Connections. Select the connection ID on which the alarm is present and click on
release button.
If any alarm persists, contact your next level of support.
153
Loopback Active-Facility - Trap ID:377

Use this procedure to clear the 'Loopback Active-Facility' alarm.
Cause
This alarm is raised when the interface is placed in facility loopback mode through explicit user
command.
Severity
Minor
Object Affected
Interface
Impact
Due to this alarm, the port will be out of service when facility loopback is active as downstream
AIS will be inserted as a result of facility loopback. The loopback has to be removed for the
network element to carry the live traffic. Downstream AIS is not inserted on applying facility
loopback on DS3 and E3 traffic streams.
Clearing Procedure
1. select Maintenance in the Navigation menu and click Loop-Back. A list of loopback for
STM/OCn, PDH, Ethernet ports is displayed
1. Choose STM/OCn. The corresponding STM/OCn loopback page is displayed
2. Select the STM/OCn port on which the alarm is raised. The corresponding Port
maintenance page is displayed
3. Choose Normal Operation for the LoopBack Mode and click Submit. Click Accept Valid
Modifications. The 'Loopback Active-facility' alarm clears
To clear loopback active-facility on PDH ports,

1. Choose PDH. The PDH port loopback page is displayed.
2. Select the E1/E3/DS1/DS3 port on which the alarm is raised. Corresponding Port
maintenance page is displayed.
3. Choose Normal Operation for the LoopBack Mode and click Submit. Click Accept Valid
Modifications. The 'Loopback Active-facility' alarm clears.
154
To clear loopback active-facility on Ethernet ports,

1. Choose Ethernet. The Ethernet ports loopback page is displayed.
2. Select the Ethernet port on which the alarm is raised. The corresponding Port maintenance
page is displayed.
3. Choose Normal Operation for the LoopBack Mode and click Submit.
4. Click Accept Valid Modifications. The Loopback active-facility alarm is cleared.
Loopback Active-Terminal - Trap ID:361

Use this procedure to clear the 'Loopback Active-Terminal' alarm.
Cause
This alarm is raised when the interface is placed in terminal loopback mode through explicit user
command.
Severity
Minor
Object Affected
Interface
Impact
The impact of this alarm is that the port will be out of service when the loopback is active. The
loopback has to be released in order for the port to carry live traffic.
Clearing Procedure
To clear this alarm, select Maintenance in the Navigation menu and click Loop-Back. A list of
loopback for STM/OCn, PDH/DS1/DS3 and Ethernet ports is displayed.
To clear loopback active-terminal on STM/OCn ports,

1. Choose STM/OCn. The STM/OCn port loopback page is displayed
2. Select the STM/OCn port on which the alarm is raised. Corresponding Port maintenance
page is displayed
3. Choose Normal Operation for the LoopBack Mode and click Submit
4. Click Accept Valid Modifications. The 'Loopback Active-terminal' alarm is cleared
155
To clear loopback active-terminal on PDH ports,

1. Choose PDH. The PDH ports loopback page is displayed
2. Select the E1/E3/DS1/DS3 port on which the alarm is raised. Corresponding Port
maintenance page is displayed
4. Click Accept Valid Modifications. The 'Loopback Active-terminal' alarm clears
To clear loopback active-terminal on Ethernet ports,

1. Choose Ethernet. The Ethernet ports loopback page is displayed
2. Select the Ethernet port on which the alarm is raised. Corresponding Port maintenance page
is displayed
4. Click Accept Valid Modifications. The 'Loopback Active-terminal' alarm clears
156
Loss of Frame (LOF) - Trap ID:28

Use this procedure to clear the 'Loss of Frame' alarm on STM/OCn port.
Cause
This alarm is raised when the node detects a severely errored framing generated when the
incoming signal has a minimum of twenty four consecutive errored framing patterns. This could
be because of the following reasons:
excessive attenuation
dirty optical fibers
dirty connectors
improper connector seating
excessive optical power received from the far end
mismatch in the capabilities (For example, STM-4/16/64 line rate fiber inserted in STM-1
receiver)
Severity
Critical
Object Affected
STM/OCn Port
Impact
alarm
Clearing Procedure
1. Identify the STM/OCn port raising the alarm.
2. Use an up-to-date fiber connection information to identify the transmit and receive sites of
the alarm signal.
3. Retrieve all alarms at the transmit end. Clear any alarms of higher order by following the
appropriate procedure. Check for the 'Loss of Frame' alarm on local node.
4. Check the Rx power of the receiver to make sure it is above the Rx sensitivity
5. Ensure that received power at the local node is within the optimum range.
6. Make sure the optical fibers are properly seated in the SFP.
157
7. If the Rx attenuation is not adjustable, check the transmit power at the far end.
8. If the transmit power is within the Tx specification, the optical attenuation in between the
two sites is too high, the optical fiber connections are dirty or the optical fiber is damaged.
Use the appropriate procedure to clean the optical fibers and connectors.
9. Ensure that interfaces connected to each other are of same capacity
10. Ensure that there is no excessive bend on fibers.
11. Check for the 'Loss Of Frame' alarm on local node. If the alarm persists, contact your next
level of support.
Loss of Frame Delineation - Trap ID:410

Use this procedure to clear the 'Loss of Frame Delineation' alarm.
Cause
This alarm is raised when there is a:
mismatch in the number of channels configured in non-LCAS mode at the local and far end
node
mismatch in the framing type
LFD alarm is valid only if VCG is in GFP framing mode. Unprovisioned VCs in VCG may lead
to 'Loss of Frame Delineation' alarm on local network element.
Severity
Critical
Object Affected
VCG
Impact
Clearing Procedure
1. Check if the far end node is having VCG configured for GFP protocol
2. Check for the number of channels configured at the local and far end node
3. Make sure to provision the same number of channels on both the far end and the local node
4. Check for any signal degrade alarm on the TUs used in the VCG of corresponding Ethernet
port
158
Loss of Frame on Port_PDH - Trap ID:541

Use this procedure to clear the 'Loss of Frame' alarm on PDH port.
Cause
This alarm is raised on PDH port when there is no proper incoming framed signal. This may be
due to faulty card.
Severity
Major
Object Affected
Port_PDH
Impact
This alarm is traffic affecting. If the port on which alarm is raised is nominated as clock source,
synchronization will be lost (applicable to E1 port only).
Note: Verify framing type between the client and the port, which should be same. This is
raised when you have a hardware loopback but no signal at the far end.
Clearing Procedure
1. Identify the E1/DS1/E3/DS3 port raising the alarm
2. Check the framing of incoming signal
3. Perform a facility loopback on that port. If the alarm clears, replace the card
4. Check for LOF alarm
159
Loss of Multiframe on AU/STS - Trap ID:104

Use this procedure to clear 'Loss of Multiframe' alarm.
Cause
the received multiframe number does not match the expected one
the network is misconfigured
an unprovisioned AU/STS is present on far end network element, which does not send any
VCAT overhead to the local node
Severity
Major
Object affected
AU/STS
Impact
This alarm is traffic affecting on the associated channel.
Clearing Procedure
1. Check for misconfiguration in the network
2. Reconfigure the connections to get the correct configuration
160
Loss of Multiframe on Port_PDH - Trap ID:536

Use this procedure to clear 'Loss of Multiframe' alarm.
Cause
there is an illegal multiframe sequence has been detected in the H4 byte
received payload is of higher order than the expected
faulty local network element
faulty far end network element
Severity
Major
Object Affected
Port_PDH
Impact
temporary traffic hit on the protected paths if the paths switched to aggregate containing
alarm
Clearing Procedure
1. Ensure that local node and far end nodet are provisioned for the same granularity. If there is
a mismatch, provision the local node accordingly
2. Perform a fiber loopback on the appropriate aggregate at the local node. If the alarm persists
at the local network element, contact your next level of support
3. Remove the loopback and ensure that the received Rx power is within range
161
Loss of Pointer on AU/STS - Trap ID:354

Use this procedure to clear the 'Loss Of Pointer on AU/STS' alarm.
Cause
This alarm is raised on AU/STS if an invalid AU/STS pointer value is received for the three
consecutive frames. This condition may arise when:
there exist a AU/STS mode mismatch between near end and far end network elements. For
example, if at near end AU/STS mode is AU4/STS-3 and far end mode is AU3/STS then
AU/STS-LOP will be raised on the second and third AU3/STS of far end equipment
there is any faulty circuit pack near or far end
if the cross-connect is present on one end and absent on the other
Severity
Major
Object Affected
AU/STS
Impact
alarm
Clearing Procedure
1. Compare the AU/STS mapping used at the far end network element and the local network
element. If there is any mismatch, use the appropriate provisioning procedure to set the
proper AU/STS mapping so that the far end and local network element uses the same
AU/STS mapping
2. Verify if the alarm on AU/STS is cleared at the local node
3. Ensure that respective cross connects and cards are properly provisioned in the neighboring
node
162
Loss of Pointer on TU/VT - Trap ID:364

Use this procedure to clear the 'Loss Of Pointer on TU/VT' alarm.
Cause
This alarm is received on the TU/VT when:
there is no cross-connect at the far end network element corresponding to this TU/VT
at the far end equipment the tributary circuit pack having PDH/Ethernet ports is not
inserted in the node
faulty circuit packs at near or far end
Severity
Major
Object Affected
TU/VT
Impact
alarm
Clearing Procedure
1. Compare the TU/VT mapping used at the far end network element and the local network
element. If there is any mismatch, use the appropriate provisioning procedure to set the
proper TU/VT mapping so that the far end and local network element uses the same TU/VT
mapping
2. Verify if the alarm on TU/VT is cleared at the local node
3. Ensure that respective cross connects and cards are properly provisioned in the neighboring
node
163
Loss of Signal on STM/OC Port - Trap ID:27

Use this procedure to clear the 'Loss of Signal on STM/OC port' alarm.
Cause
This alarm is raised on STM/OCn port when:
the received optical signal level drops below an implementation
determined threshold
Rx of SFP at the near end or Tx of the SFP at the far end is faulty
Severity
Critical
Object affected
STM/OCn port
Impact
traffic affecting
management connectivity will be lost on that interface
loss of synchronization if network element is locked to that port and the remaining clock
switching depends on the nomination of other clock
Clearing Procedure
1. Check if the received power lies in the optimum range at the local network element. If the
received optical power is within the specified range, contact the next level of support
2. Check if the corresponding far end port is admin up. Following appropriate procedures to get
the port in admin up condition
3. Clean the fibers and ensure that there are no fiber cuts
164
Loss Of Signal on PDH port - Trap ID:202

Use this procedure to clear the 'Loss of Signal on PDH port' alarm.
Cause
This alarm is raised on PDH ports, when:
the received signal level drops below an implementation determined threshold
faulty cables between client port and PDH port
faulty receivers
Severity
Critical
Object affected
Port_PDH
Impact
The impacts of this alarm on PDH ports are:
traffic affecting
DCN connectivity over E1 management channel will be lost if LOS is there on the E1 port
used for E1 management
loss of synchronization if the network element is locked to the E1 or DS1 port having LOS
alarm
Clearing Procedure
1. Check if the corresponding far end PDH port is admin up. If the far end port is not in admin
up condition, get the port in admin up condition by following appropriate procedure
2. Check the cable and ensure that there are no fiber cuts
165
Loss of VCAT Multiframe - Trap ID:50

Use this procedure to clear 'Loss of VCAT Multiframe' alarm.
Cause
This alarm is raised when
the received multiframe number does not match the expected one
the network is misconfigured
an unprovisioned TU/VT is present on far end network element, which does not send any
VCAT overhead to the local node
Severity
Critical
Object affected
TU/VT
Impact
This alarm is traffic affecting on the associated channel.
Clearing Procedure
1. Check for misconfiguration in the network. For example, a VC3 connection between two
nodes with VCAT enabled at the near-end and VCAT disabled at the far end
2. Reconfigure the connections to get the correct configuration
166
Manual Switch Active

Use this procedure to clear the 'Manual Switch Active' alarm.
Cause
This alarm is raised only against the work channel, when:
STM/OCn port belonging to an MSP/APS group if Manual switch is applied on it
AU/STS/TU/VT channel belonging to SNCP/UPSR pair if manual switch is applied on it
Any STM ports (if provisioned as part of a 1+1 MSP), AU and TU (if the STM/OCn port
provisioned in SNCP/UPSR mode)
Severity
Minor
Object affected
TU/VT - Trap ID:460
Impact
Due to this alarm, traffic will be switched to the STM/OCn port or the AU/STS/TU/VT
channel to which the manual switch is given. The traffic will stay in the manually switched port or
channel until again manually/forcefully switched away from this path or signal failure condition
occurs on this path. A traffic outrage of maximum 50 ms. will be experienced on successful
manual switching of traffic from one path to another.
Clearing Procedure
To clear Manual switch active on STM/OCn port,
1. Click Protection in the Navigation menu. Click MSP/APS groups link. The MSP/APS groups
page is displayed.
2. Click on the MSP/APS group under the Name field. The Protection Provisioning page is
displayed.
3. Click Release. The Connections protection request confirm page is displayed.
4. Click Confirm request. The Connections protection request result page is displayed with a
success message.
167
To clear Manual switch active on AU/STS,

1. Click Protection in the Navigation menu. Click Connections link. The Connections protection
request page is displayed.
3. Click Confirm request. The Connections protection request result page is displayed with a
success message.
To clear this alarm on TU/VT,

1. Click Protection in the Navigation menu and then click Connections link. The Connections
To clear this alarm on PDH port,

1. Click Protection in the Navigation menu and then click PDH port link. The Connections
168
Manual Switch Fail

Use this procedure to clear the 'Manual Switch Fail' alarm.
Cause
This alarm is raised when the last applied external command Manual switch on STM/OC,
AU/STS, and TU/VT has failed.
Severity
Warning
Impact
The Manual Switch command applied by the user is not completed by the network element and
is ignored.
Objects Affected
STM/OC, AU/STS, and TU/VT
Clearing Procedure
1. Log into the network element web user interface at the default view level with appropriate
user access privileges
2. Determine if there are any alarms present on the interface on which manual switch command
is applied. If no alarm is present, contact your next level of support
3. Use appropriate procedure to clear the alarm
4. Operate manual switch command again
169
NTP Server Unreachable - Trap ID:535

Use this procedure to clear the 'NTP Server Unreachable' alarm.
Cause
This alarm is raised when the node is not synchronized with the NTP server.
Severity
Minor
Object affected
Node
Impact
The impact of this alarm is node will not be synchronized with NTP server.
Clearing Procedure
1. Ensure that NTP server is provisioned properly
2. Ensure that NTP server is reachable from the node
3. Check if the alarm is cleared at the near end
170
Path Label Mismatch on AU/STS - Trap ID:357

Use this procedure to clear the 'Path label Mismatch' alarm.
Cause
This alarm is raised on AU/STS, when the received value of the signal label in the C2 byte does
not match with the expected signal label value. The probable causes for this alarm are:
incorrect connection setup
incorrect configuration setup
faulty local or far end network elements
Severity
Major
Object affected
AU/STS
Impact
If generation of downstream AIS on PLM is enabled using profiles, this alarm affects traffic in
the following ways:
protected traffic will switch to protect path with a hit of maximum 50 ms
unprotected traffic will go down
Clearing Procedure
1. Retrieve all active alarms on the network element. Clear all the higher alarms using
appropriate procedures
2. Check for appropriate fiber connections. Reconnect the fiber connections to get the right
configuration
3. Check if the values against the Signal Label and Received Signal Label fields match. If
mismatch is present, set the transmit same as the received signal label or set the transmit on
both the near end and far nodes the same.
Note: The expected signal label is same as the transmitted signal label. There is no field for
expected signal label.
171
Path Label Mismatch on TU/VT - Trap ID:367

Use this procedure to clear the 'Path label Mismatch' alarm.
Cause
This alarm is raised on TU/VT, when the received value of the signal label in the V5 byte does
not match with the expected signal label value. The probable causes for this alarm are:
incorrect configuration setup
faulty local or far end network elements
Severity
Major
Object affected
TU/VT
Impact
If generation of downstream AIS on PLM is enabled using profiles, this alarm affects traffic in
the following ways:
protected traffic will switch to protect path with a hit of maximum 50 ms
unprotected traffic will go down
Clearing Procedure
1. Retrieve all active alarms on the network element. Clear all the higher alarms using
appropriate procedures
2. Check for appropriate fiber connections. Reconnect the fiber connections to get the right
configuration
3. Check if the values against the Signal Label and Received Signal Label fields match. If
mismatch is present, set the transmit same as the received signal label or set the transmit on
both the near end and far nodes the same
Note: The expected signal label is same as the transmitted signal label. There is no field for
expected signal label.
172
Protection Switch Active

Use this procedure to clear the 'Protection Switch Active' alert.
Cause
The alert is raised when traffic is switched from work to protect channel in revertive mode. In
case of a bidirectional or an automatic switch, this alert is raised due to:
a local signal fail
signal degrade
loss of frame
AIS
Severity
Major
Object affected
STM/OC Port - Trap ID:439
TU/VT - Trap ID:461
Impact
The impact of this alert is that traffic is carried in the protect path.
Clearing Procedure
1. Log into the network element web user interface at the default view level with appropriate
user access privileges
2. Determine if there are any Signal fail or Signal degrade alarm present. Use appropriate
procedure to clear the reported alarm or contact your next level of support
173
Protection Switching is Incomplete - Trap ID:669

Use this procedure to clear 'Protection Switching Incomplete' alarm on a tunnel group.
Cause
This alarm is raised when,
Higher priority alarm 1 above is present (or)
Near end requested (selected) signal is different from far end bridged signal
Severity
Critical
Object Affected
Protection Group
Impact
Traffic will be affected on the tunnel group.
Clearing Procedure
To clear this alarm, check and clear higher priority alarm 1.
174
Protection Channel Match Fail - Trap ID:442

Use this procedure to clear the 'Protection Channel Match Fail' alarm.
Cause
This alarm is raised when the channel number in the received K2 byte is different from that in
the transmitted K1 byte. This can happen due to improper fiber connections. This alarm is
applicable only if the network element is in MSP/APS configuration when NE is in SONET
mode.
Severity
Minor
Object affected
STM/OCn port
Impact
Clearing Procedure
To clear this alarm, ensure that fiber connections are done properly.
175
Protection mode mismatch - Trap ID:441

Use this procedure to clear the 'Protection mode mismatch' alarm.
Cause
This alarm is raised when one of the network element is configured for bidirectional MSP and
the other network element is in unidirectional MSP.
Severity
Minor
Object Affected
STM/OCn port
Impact
Non service affecting
Clearing Procedure
NOTE: All cross-connects on MSP ports have to be deleted before editing the mode of the
group.
1. Check the MSP configuration on far end node
If MSP/APS is not configured

1. Configure MSP/APS in the far end network element
2. Ensure that in the far end network element, MSP/APS configuration is bidirectional
3. If MSP/APS is unidirectional, configure the far end network element to bidirectional MSP
4. Check for the 'Protection mode mismatch' alarm
If MSP/APS is configured
1. Ensure that in the far end network element, MSP/APS configuration is bidirectional
2. If MSP/APS is unidirectional, configure the far end network element to bidirectional MSP
3. Check for the 'Protection mode mismatch' alarm.
176
Protection Switch Byte Fail - Trap ID:443

Use this procedure to clear the 'Protection Switch Byte Fail' alarm.
Cause
This alarm is raised when one or more of the following conditions are present in the received K-
bytes:
inconsistent K-bytes
an invalid, unused, or inappropriate K-byte code
an invalid or unused channel number
A loss of K-byte continuity between far end and near end network elements may cause this
alarm.
Severity
Minor
Object affected
STM/OCn Port
Impact
Non service affecting
Clearing Procedure
To clear this alarm, check for the LOS and AIS alarms on the protect port.
If the LOS and AIS alarms persists:

1. Clear the alarms using the troubleshooting procedures
2. Check for the 'Protection switch byte fail' alarm if the LOS and AIS alarms are not reported
3. If the alarm persists, contact your next level of support
If the LOS and AIS alarms are not reported:

1. Check the status of the cards and replace any failed cards
2. Check for the Protection switch byte fail alarm if the LOS and AIS alarms are not reported
3. If the alarm persists, contact your next level of support
177
Note: If East port of one is connected to east of other node, similarly the West port then
Invalid k byte alarm is reported. Now issuing an exerciser command, the command is
successfully accepted. The result of 'failure of exerciser' is shown in the events history page.
The Invalid K Byte alarm is present but can be any where in the ring.
Received Power Lower Threshold Crossed - Trap ID:400

Use this procedure to clear the 'Received Power lower threshold crossed' alarm.
Cause
This alarm is raised when the received power drops below the lower threshold power for the SFP
type which is used in the network element. This alarm will be cleared when the received power is
more than the specified lower threshold value.
Severity
Major
Object affected
Port
Impact
The impact of this alarm may or may not be traffic affecting, depending on the lower received
power level.
Clearing Procedure
1. Check for the received power level. If the received power is low, check the fiber channel
2. Clean and replace the fiber
3. Replace the SFP on the far end node
If the alarm persists, contact your next level of support
178
Received Power upper threshold crossed - Trap ID:401

Use this procedure to clear the 'Received Power upper threshold crossed' alarm.
Cause
This alarm is raised when the received power crosses the upper threshold power for the SFP type
which is used in the network element. This can be due to:
higher transmitting power of the upstream network element
very little optical attenuation between the two network element
This alarm will be cleared when the received power is less than the specified upper threshold
value.
Severity
Major
Object affected
Port
Impact
The impact of this alarm may or may not be traffic affecting, depending on the upper received
power level.
Clearing Procedure
1. Check for the received power level. If it is higher, introduce proper attenuation.
2. If the alarm is not cleared, replace the SFP in the remote node.
179
Remote Alarm Indication(RAI) - Trap ID:538

Use this procedure to clear the 'Remote Alarm Indication' alarm.
Cause
This alarm is raised when the receive port of the local network element is receiving RAI from
remote PDH port
Severity
Major
Object affected
Port_PDH
Impact
Clearing Procedure
1. Check if any alarm exists on the remote PDH port, clear it with appropriate procedure
2. If the alarm exists, replace the card
If this alarm persists, contact your next level of support.
180
Remote Defect Indication (RDI) on STM/OCn Port - Trap

ID:31
Use this procedure to clear the 'Remote Defect Indication on STM/OCn Port' alarm.
Cause
This alarm is raised on STM/OCn port when the byte K2 has been set, indicating that the far end
network element has detected a fault in the regenerator section/section level or the multiplexer
section/line level.
This alarm is reported in case of an LOS, LOF on STM/OCn port, AIS on STM/OCn port,
TIM with downstream AIS enabled at remote STM/OCn port of network element.
Severity
Critical
Object affected
STM/OCn Port
Impact
Clearing Procedure
To clear the alarm,
1. Verify the transmitted and received traces at the STM port (J0 trace) on the far end node.
2. Determine the Rx and Tx directions at the local network element and determine the same on
the far end nodes.
3. Login to the far end network element and retrieve a list of alarms. If there are no additional
alarms, the equipment and facilities are in-service, then check the fiber else perform the
appropriate procedure to clear the alarms.
4. Retrieve the alarms at local node.
181
Remote Defect Indication (RDI) on AU/STS - Trap ID:353

Use this procedure to clear the 'Remote Defect Indication' alarm on AU/STS.
Cause
This alarm is raised on AU/STS when the fifth bit of the status byte (G1) is set in VC-4/STS-
3/VC-3/STS-1 path, indicating that the downstream node has detected a fault at the higher path
level.
This alarm is reported in case of AIS on AU/STS, TIM/PLM with downstream AIS enabled at
corresponding remote AU/STS where the higher order path is terminating.
Impact
The Impact of this alarm is not traffic affecting.
Severity
Major
Object affected
AU/STS
Clearing Procedure
the far end network elements
2. Login to the far end network element and retrieve a list of alarms
3. Perform the appropriate procedure to clear the alarms or ensure that the equipment and
facilities are in service
4. Retrieve the alarms at local network element. Check if the alarm is cleared at the local
network element
5. Verify the fiber connection at far end network element that connects to local network
element. Repair, clean and reconnect the fiber as required
6. Retrieve the alarms at local network element.
182
Remote Defect Indication (RDI) on TU/VT - Trap ID:363

Use this procedure to clear the 'Remote Defect Indication on TU/VT' alarm.
Cause
This alarm is raised on TU/VT when the fifth bit of the status byte (G1/V5 respectively) is set in
the VC-3/VC-12 path, indicating that the far end node has detected a fault at the lower path
level.
Severity
Major
Object affected
TU/VT
Impact
Clearing Procedure
the far end network elements.
2. Login to the far end network element and retrieve a list of alarms.
3. Perform the appropriate procedure to clear the additional alarms
4. Retrieve the alarms at local network element. Check if the alarm on TU/VT is cleared at the
local network element.
183
Remote Defect Indication (Terminating) - Trap ID:488

Use this procedure to clear the 'Remote Defect Indication on TU/VT' alarm.
Cause
This alarm is raised on TU/VT when the fifth bit of the status byte (G1/V5 respectively) is
set in VC-3/VC-12, indicating that the far end node has detected a fault at the lower path
level.
This alarm is reported in case of AIS on TU/VT, TIM/PLM with downstream AIS enabled
on corresponding remote end TU/VT where the lower order path is terminating.
Severity
Major
Object affected
TU/VT
Impact
Clearing Procedure
the far end network elements.
2. Login to the far end network element and retrieve a list of alarms.
3. Perform the appropriate procedure to clear the additional alarms.
4. Retrieve the alarms at local network element. Check if the alarm on TU/VT is cleared at the
local network element.
184
Rx Partial Loss of Capacity - LCAS - Trap ID:407

Use this procedure to clear the 'Rx Partial Loss of Capacity - LCAS' alarm.
Cause
This alarm is raised when there is at least one of the channels (not all) of VCG is unable to
receive data resulting in partial loss of capacity in the receiving direction.
Severity
Minor
Object affected
VCG
Impact
The impact of this alarm is partial loss of traffic on the VCG.
Clearing Procedure
1. Check for the number of VC/VT members provisioned at both near end and far end
network elements. If the number of VC/VT members in both network element are same, go
to step 3
2. Provision the VC/VT members in the near/far end network element so that number of
member in near and far network element are the same
3. Check if the 'Rx Partial Loss of Capacity - LCAS' alarm is cleared at the local network
element.
4. Check for the alarms on the TU/VT members of the VCG at near end and far end network
element. If any alarm on VCG is detected, clear those alarm with appropriate procedures
5. Ensure that LCAS provisioning settings are similar on corresponding TU/VT members
connected in a VCG group
6. Check if the 'Rx Partial Loss of Capacity - LCAS' alarm is cleared at the local network
element.
185
Rx Total Loss of Capacity - LCAS - Trap ID:411

Use this procedure to clear the 'Rx Total Loss of Capacity' alarm.
Cause
This alarm is valid in LCAS as well as non-LCAS modes of VCG. In LCAS mode, if all the added
receive channels are temporarily removed from the VCG due to fault, this alarm will be raised. In
Non-LCAS mode, any single receive channel of the VCG with a traffic affecting defect (such as
LOP, AIS, LOM, TIM/PLM) will cause the whole receive VCG to be down and hence total loss
of receive transport capacity.
Severity
Major
Object affected
VCG
Impact
This alarm is traffic affecting in the receive direction.
Clearing Procedure
1. Check if the corresponding VCG association at the far end network element is provisioned in
the transmit direction
2. Check for the alarms associated with the AU that could cause the reporting of this alarm. If
the cause of alarm is detected, perform the appropriate procedure to clear the alarm at the far
end
186
Section/RS DCC Link Failure - Trap ID:596

Use this procedure to clear the 'Section/RS DCC Link Failure' alarm.
Cause
This alarm is raised when DCC_R bytes are used on the DCC communication and one of the
following conditions exist:
there is an LOS/LOF/MS-AIS/Excessive error alarm on the optical link
DCC byte is not provisioned on far end
DCC byte provisioned at far end is other than DCC_R
if there is a mismatch in Layer 2 or OSPF parameters. For example, near is provisioned for
L2 protocol as "PPP, HDLC Framing" and far end is provisioned as "Standard PPP, RFC
1661".
near end node is faulty
far end node is faulty
Severity
Major
Object affected
Network Interface
Impact
The impact of this alarm is loss of management connectivity over IBC (Inband Communication).
Clearing Procedure
1. Check for the LOS/LOF/MS-AIS/Excessive error/Signal degrade alarm on the optical
interface on which 'Section/RS DCC Link Failure' alarm is raised.
If any alarm is reported, clear the alarm using appropriate clearing procedure. Go
to step 2.
If any alarm is not reported, contact your next level of support.
2. Check for the 'Section/RS DCC Link Failure' alarm on the node.
3. Check at the far end node whether DCC byte is provisioned as DCC_R.
187
If is provisioned other than DCC_R, provision it to DDC_R. Ensure that DCN

protocol provisioned at both Near and far end network elements are same. Go to
step 4.
If DCC byte provisioned at far end network element is same as that in the near
end node, contact your next level of support.
4. Check for 'Section/RS DCC Link Failure' alarm on node.
Secondary Reference Out of Range - Trap ID:412

Use this procedure to clear the 'Secondary Reference out of range' alarm.
Cause
This alarm is raised when secondary reference goes out of lock because of very high frequency
difference.
Severity
Major
Object affected
Synchronization
Impact
If primary fails synchronization does not work, secondary is out of reference.
Clearing Procedure
No action is required. It gets settled by itself after some time.
188
SFP Auto Provision Mismatch - Trap ID:360

Use this procedure to clear the 'SFP Auto Provision Mismatch' alarm.
Cause
This alarm is raised when there is a mismatch in the port capacity and the laser capacity of the
SFP/XFP.
Severity
Critical
Object affected
SFP/XFP
Impact
Applies to
This alarm is applicable to STM/OCn port.
Clearing Procedure
1. Make sure that there is no traffic through the node and then remove the SFP/XFP.
2. Delete the SFP/XFP object.
3. Insert a new SFP/XFP with the laser capacity same as the port capacity.
4. Check if the 'SFP Auto Provision Mismatch' alarm is cleared at the local node.
189
Signal Degrade on AU/STS - Trap ID:358

Use this procedure to clear the 'Signal Degrade' alarm on AU/STS.
Cause
This alarm is raised when the bit error ratio (BER) of the VC-4 path BIP-8 error rate exceeds the
set signal degrade threshold.

faulty local node
Severity
Major
Object affected
AU/STS
Impact
Clearing Procedure
1. If the path is protected, ensure that the traffic is switched to the other aggregate port.
fiber properly.
3. Check for 'Signal Degrade' alarm.
5. Check if the 'Signal Degrade' alarm is cleared at the local node.
190

of support.
If it is not in the specified range, it indicates that SFP/XFP is faulty. Replace the
SFP/XFP.
the Rx power.
8. Check if 'Signal Degrade' alarm on AU/STS is cleared at the local node.
191
Signal Degrade on TU/VT - Trap ID:368

Use this procedure to clear the 'Signal Degrade' alarm on TU/VT.
Cause
This alarm is raised when the BER of the BIP-2 (VC-12) or BIP-8 (VC-3) error rate exceeds the
set signal degrade threshold. The probable causes are:
faulty transmitter at far end network element
faulty receiver at local network element
NOTE: Upon a fiber re-insertion on the STM-N interface, 'Signal Degrade on TU' alarm may
be raised. The alarm will clear within a minute.
Severity
Major
Object affected
TU/VT
Impact
operation status of the associated unprotected cross connections degraded
traffic on the respective TU/VT in error
Clearing Procedure
1. If the path is protected, ensure that the traffic is switched to the other aggregate port.
fiber properly.
192

of support.
SFP/XFP.
the Rx power.
8. Check if 'Signal Degrade' alarm on TU/VT is cleared at the local node.
Signal Degrade on Ethernet Port - Trap ID:519

Use this procedure to clear the 'Signal Degrade' alarm on Ethernet Ports.
Cause
This alarm is raised on Ethernet ports when more than 1% of the total frames received at the
Ethernet port per second are errored for three consecutive seconds. The probable causes are:
faulty optical cable
received frame size is smaller/larger than the supported frame size
Severity
Minor
Object affected
Ethernet Port
Impact
This alarm is traffic affecting on unprotected paths.
Clearing Procedure
1. Ensure that the Ethernet cable is connected properly.
2. Ensure that the MTU size of the data is within the supported range.
3. Check if 'Signal degrade' alarm on Ethernet port is cleared at the local node.
193

Signal Degrade on VCG - Trap ID:496

Use this procedure to clear the 'Signal Degrade' alarm on VCG.
Cause
This alarm is raised on VCG ports when more than 1% of the total frames received at the VCG
port per second are errored for three consecutive seconds.

faulty transmitter at far end network element
faulty receiver at local network element
Severity
Minor
Object affected
VCG
Impact
operation status of the associated cross connections degraded, if the threshold is enabled on
the TU/VT
connections, if the threshold is enabled on the TU/VT
Clearing Procedure
fiber properly.
194

of support.
SFP/XFP.
the Rx power.
7. Check if 'Signal Degrade' alarm on VCG is cleared at the local node.
195
Signal Label Unequipped on AU/STS - Trap ID:355

Use this procedure to clear the 'Signal Label Unequipped' alarm on AU/STS.
Cause
This alarm is raised when the Received Signal Label of the corresponding AU/STS is
unequipped.

probable misconfiguration at the far end upstream network element
improper provisioning of corresponding cross-connection at one of the far end upstream
network element
improper fiber connections
Severity
Major
Object affected
AU/STS
Impact
The alarm is service affecting depending on the consequent action which is set on the particular
AU/STS over which the alarm is reported.
Clearing Procedure
1. Check the far end upstream node for AU/STS transmit Signal Label (Go to
Facilities>STM/OCn>AU/STS>Signal Label).
If the value of the Signal Label is unequipped, select the appropriate value against
the field. Go to step 2.
If the value of the Signal Label is any other valid value, contact your next level of
support.
2. Ensure that cross-connects are provisioned properly in that particular AU/STS.
3. Ensure proper fiber connections.
4. Check if the 'Signal Label Unequipped' alarm on AU/STS is cleared at the local node.
196
Signal Label Unequipped on TU/VT - Trap ID:365

Use this procedure to clear the 'Signal Label Unequipped' alarm on TU/VT.
Cause
This alarm is raised when the Received Signal Label of the corresponding TU/VT is unequipped.

a probable misconfiguration at the far end upstream network element
improper provisioning of corresponding cross-connection at one of the far end upstream
node
Severity
Major
Object affected
TU/VT
Impact
The alarm is service affecting depending on the consequent action which is set on the particular
TU/VT over which the alarm is reported.
Clearing Procedure
1. Ensure that the corresponding cross-connect is properly provisioned.
2. Check at the first upstream node for the 'Signal Label Unequipped' alarm on TU/VT.
If the alarm is reported, go to step 3.
If the alarm is not reported, check for the alarm in the consecutive upstream
node. Go to step 5.
3. Check for the provisioning of the corresponding cross-connect on upstream network
element.
If provisioning is correct, contact your next level of support.
If provisioning is incorrect, ensure correct provisioning of the cross connection.
Go to step 4.
4. Check if the 'Signal Label Unequipped' alarm on TU/VT is cleared at the local node.
197
System clock in internal mode - Trap ID:97

Use this procedure to clear the 'System clock in internal mode' alarm.
Cause
node is in holdover mode for last 24 hours
node has the nominated source as internal synchronization source
node is commissioned and does not have any timing source provisioned
If the nominated clock source is internal, this alarm will not clear. In certain platforms, the alarm
could be raised when the ppm offset crosses +/- 12 ppm only. High ppm offset may not be
considered as a hard failure condition on some platforms and this may not cause the alarm to
appear in that case.
Severity
Major
Object affected
Timing Manager
Impact
This alarm is not traffic affecting. The node synchronization is using the internal clock in free run
mode. It is an event in standing condition. While the alarm is active, the internal clock provides
stratum 3 (SONET)/G.813 option 1 (SDH) quality (4.6 ppm) timing.
Clearing Procedure
1. Check the nominated synchronization source
2. If the source is:
STM1/4/16/64/OC-3/12/48/192, ensure the proper optical fiber connectivity.
Then go to step 3.
E1/DS1, ensure that E1/DS1 cable is connected properly. Then go to step 3.
BITSIN- (clock) or BITSIN- (data), go to step 5.
NOTE: In SONET mode, both the BITS clocks are DS1 data clocks.
3. Check whether the nominated clock source port is Admin _down.

If it is Admin _down, provision it to Admin_up and go to step 6.
If it is Admin_up, go to step 4.
198
4. Check for 'Loss Of Signal','Signal Fail' and 'AIS' alarms on nominated clock source.
If the alarm exist, clear the alarm by using appropriate procedures and then go to
step 6.
If the alarm does not exist, contact the next level of support.
5. Ensure that external synchronization ESI cable is properly connected to ESI interface.
6. Check if 'System clock in internal mode' alarm is cleared at the local node.
If the alarm clears, you have completed the procedure.
Timing reference failed - Trap ID:241

Use this procedure to clear the 'Timing reference failed' alarm.
This alarm is raised on clock source nominated as timing reference.
Cause
there is a Signal fail condition on the nominated clock source
the ppm offset of the clock source is more than +/- 12 ppm
Severity
Major
Object affected
Timing Reference
Impact
The impact of this alarm is not traffic affecting. But system will go to holdover mode if there is
no other valid clock sources.
Procedure
1. Check the clock source on which the alarm is raised.
2. If the alarm is raised on:
STM1/4/16/64/OC-3/12/48/192, go to step 3.
E1/DS1, go to step 4.
BITSIN- (clock) or BITSIN- (data), go to step 5.
NOTE: In SONET mode, both the BITS clocks are DS1 data clocks.
199
3. Check for LOS, LOF, and MS-AIS alarm on STM ports.

If any of these alarms exist, use the appropriate procedure to clear it. Go to step
11.
If it does not exist, go to step 10.
4. Check for LOS, LOF, and AIS alarm on E1/DS1 ports.
If any of these alarms exist, use the appropriate procedure to clear it. Go to step
11.
If it does not exist, go to step 10.
5. Check the mode of the node.
If the node is in SDH mode, then go to step 6.
If the node is in SONET mode, then go to step 8.
6. Ensure that external synchronization interface cable is inserted properly in ESI RJ45
connector.
If the clock source is BITSIN- (clock), then go to step 10.
If the clock source is BITSIN- (data), then go to step 7.
7. Ensure that the data we are getting is in framed as PCM30/31 (with or without CRC). Go to
step 10.
PCM refers to pulse code modulation and CRC refers to cyclic redundancy code.
8. Ensure that external synchronization interface cable is inserted properly in ESI RJ45
connector.
9. Ensure that the data we are getting is in framed as ESF framing. Go to step 10.
10. Ensure that the ppm offset of the synchronization source is less than +/- 12ppm. Go to step
11.
11. Check if 'Timing reference failed' alarm is cleared at the local node.
NOTE: In certain platforms, the alarm could be raised when the ppm offset crosses +/- 12
ppm only. High ppm offset may not be considered as a hard failure condition on some
platforms and this may not cause the alarm to appear in that case.
200
Trace Identifier Mismatch on STM/OCn Port - Trap ID:52

Use this procedure to clear the 'Trace Identifier Mismatch' alarm on STM/OCn Port.
Cause
This alarm is raised when the received string of the trace byte (J0) does not match the expected
string.

incorrect settings during configuration (receive string or far end transmit string)
faulty local node
Severity
Major
Object affected
STM/OCn port
Impact
traffic affecting on unprotected paths depending on the value assigned to the TIM Action
field
operation status of the associated unprotected cross connections down
temporary traffic hit if paths switched to protecting one in case of protected cross
connections
AIS propagated downstream, and RDI propagated upstream when TIM Action field is set to
tim_downstream_ais
Clearing Procedure
1. Determine the object on which the alarm is raised.
2. Check if Rx J0 string is same as the Tx J0 string for that object at the far end node connected
to the same interface.
If strings are same, go to step 4.
If strings are different, then go to 3.
3. Check for the configurations of the node and fiber connectivity.
If fiber connections are incorrect, then reconnect to get the right configuration.
Go to step 4.
201
If fiber connections are correct, then go to step 4.

4. Reconnect the fiber connections to get the right configuration.
5. Ensure that the values against the Expected J0 and Received J0 fields match at the local node.
6. In case of a mismatch detected between the Transmit J0 at the far end node and Expected J0
at the local node, correct the same by changing the Expected J0 value.
NOTE: One byte trace length is supported at the RS level though it has to be numeric rather
than an alphabet.
7. Check if the 'Trace Identifier Mismatch' alarm is cleared at the local node.
202
Trace Identifier Mismatch on AU/STS - Trap ID:356

Use this procedure to clear the 'Trace Identifier Mismatch' alarm on AU/STS.
Cause
This alarm is raised on AU/STS when the received string of the higher order path trace byte (J1)
does not match the expected string.

settings incorrect during configuration (receive string or far end transmit string)
Severity
Major
Object affected
AU/STS
Impact
field
connections
tim_downstream_ais
Clearing Procedure
Go to step 4.
203

than an alphabet.
204
Trace Identifier Mismatch on TU/VT - Trap ID:366

Use this procedure to clear the 'Trace Identifier Mismatch' alarm on TU/VT.
Cause
This alarm is raised when the received string of the trace byte does not match the expected string.

settings incorrect during configuration (receive string or far end transmit string)
Severity
Major
Object affected
TU/VT
Impact
field
connections
tim_downstream_ais
Clearing Procedure
Go to step 4.
205

than an alphabet.
Transmitted Power Lower Threshold Crossed - Trap

ID:392
Use this procedure to clear the 'Transmitted Power lower threshold crossed' alarm.
Cause
This alarm is raised when the transmitted power drops below the lower threshold power for the
SFP/XFP transceiver which is used for the node. This alarm will be cleared when the transmitted
power is more than the specified lower threshold value. This alarm is also raised if ALS is enabled
on a port and LOS is present on Rx port.
Severity
Major
Object affected
Port
Impact
This alarm may affect traffic if the transmitted power level has crossed the lower threshold
considerably.
Clearing Procedure
1. This alarm indicates that SFP/XFP of the local network element is faulty. Replace the faulty
SFP/XFP with an equivalent one.
2. Check if the 'Transmitted Power lower threshold crossed' alarm is cleared at the local node.
206
Transmitted Power Upper Threshold Crossed - Trap

ID:393
Use this procedure to clear the 'Transmitted Power upper threshold crossed' alarm.
Cause
This alarm is raised when the transmitted power crosses above the upper threshold power for the
SFP/XFP type which is used for the network element. This alarm will be cleared when the
transmitted power is less than the specified upper threshold value.
Severity
Major
Object affected
Port
Impact
This alarm may affect traffic if the transmitted power level has crossed the upper threshold
considerably.
Clearing Procedure
1. This alarm indicates that SFP/XFP of the local network element is faulty. Replace the faulty
SFP/XFP with an equivalent one.
2. Check if the 'Transmitted Power upper threshold crossed' alarm is cleared at the local node.
207
Tx Partial Loss of Capacity - LCAS - Trap ID:497

Use this procedure to clear the 'Tx Partial Loss of Capacity - LCAS' alarm.
Cause
This alarm is raised when there is at least one of the channels (not all) of VCG is unable to
transmit data resulting in partial loss of capacity in the transmit direction.
Severity
Minor
Object affected
VCG
Impact
The impact of this alarm is partial loss of traffic on the VCG.
Clearing Procedure
1. Check if the corresponding VCG association at the local network element is provisioned in
the transmit direction.
2. Check for the alarms associated with the channels that could cause the reporting of this
alarm. Perform the appropriate procedure to clear the alarm at the far end.
3. Ensure that LCAS provisioning settings are similar on corresponding TU members
connected in a VCG group.
208
Tx Total Loss Of Capacity-LCAS - Trap ID:406

Use this procedure to clear the 'Tx Total Loss Of Capacity-LCAS' alarm.
Cause
This alarm is raised either when all the VC members of the near end network element are LCAS
removed from the VCG or all the VC members in the far end network element are alarmed
(LOP, AIS, LOM, Uneq, PLM) thus unable to carry traffic.
Severity
Major
Object affected
VCG
Impact
Due to this alarm, no traffic is transmitted from the VCG towards the SDH side resulting in total
loss of transmit capacity at the near end network element.
Clearing Procedure
1. Ensure that both the far end and near end network elements have the same number of VCs
provisioned.
2. Verify the TX status on the VC members on the local Network element. If the status is other
than Norm (add/idle), contact your next level of support.
3. Check for the alarms on all the VC members on the far end network element and clear them
using appropriate clearing procedures.
209
User Payload Mismatch - Trap ID:498

Use this procedure to clear the 'User Payload Mismatch' alarm.
Cause
This alarm is raised when the received user payload identifier (UPI) in the GFP frames does not
match the expected payload type. The probable cause is that the far end network element is
transmitting a payload that is not the same as the locally configured payload. For instance, local
port is configured to carry frame mapped Ethernet and the far end port is carrying frame mapped
PPP (point-to-point protocol).
Severity
Critical
Object affected
VCG
Impact
Clearing Procedure
1. Check the client payload (for example, frame mapped Ethernet, PPP, and transparent gigE)
that is sent over GFP on both ends of the network
2. Ensure that the payload at far end network element is same as that at the local network
element
210
Upgrade load passed - Trap ID:566

Use this procedure to know about the 'Upgrade load passed' alert.
Cause
This alert is raised when upgrading the software release bundle on node is started.
Severity
Warning
Objects Affected
MEP
Impact
The impact of this alert is non-service affecting. This alert is raised for information purposes
only.
Procedure
211
User Authentication Failed - Trap ID:320

Use this procedure to clear the 'User Authentication Failed' alarm.
Cause
an attempt to login into a TL1 session fails due to authentication.
the user gives wrong credentials while logging in from web UI also.
This may be due to incorrect entry of user name and/or password. This alarm is raised when the
user login is from TL1 interface.
Severity
Minor
Object Affected
Node
Impact
The TL1 session will remain unavailable for provisioning commands unless authentication
succeeds.
Clearing Procedure
No action is required. This alert is raised and cleared, and logged into the event.
NOTE: User Name and Password are case sensitive. While typing the User Name or Password
ensure that Caps Lock is disabled.
212
Loss of Frames - Trap ID:740

Use this procedure to clear the 'Loss of Frames' alarm on CESIWF.
Cause
This alarm is raised on CESIWF when:
there is fiber cut at NNI or Service disruption at the network elements involved.
if clock recovery mode (RTP) is different on both the sides.
Severity
Critical
Object Affected
CESIWF
Impact
alarm
The impact of this alarm on CESIWF is traffic affecting.
Clearing Procedure
To clear this alarm on CESIWF,
1. Identify the CESIWF port raising the alarm.
2. Ensure that the cause of disruption on NNI path like the link status of NNI, service label
CCM, IWF configuration parameters are corrected.
3. Check for the 'Loss of frame' alarm.
213
Late Frames - Trap ID:741

Use this procedure to clear the 'Late Frames' alarm.
Cause
This alarm is raised due to increased network delay or lower values of jitter buffer depth. This is a
threshold crossing alert alarm.
Severity
Critical
Object Affected
CESIWF
Impact
Impact of this alarm is bit errors and is traffic affecting.
Clearing Procedure
1. Check the Jitter Buffer Depth of the CESIWF provisioned on the card.
2. Check for the 'Late Frames' alarm.
If the alarm persists, check the network for any additional delay.
3. If the alarm still persists, contact your next level of support.
214
Malformed Frames - Trap ID:742

Use this procedure to clear the 'Malformed Frames' alarm.
Cause
there is configuration mismatch of payload type bit in Realtime Transport Protocol [RTP] or
payload length mismatch on the remote end
local hardware failure
Severity
Critical
Object Affected
CESIWF
Impact
The impacts of this alarm is traffic affecting.
Clearing Procedure
1. Ensure the remote node and local node are configured for the same payload and are carrying
the same data traffic.
2. Check for the 'Malformed Frames' alarm in the node.
If the alarm persists, ensure that there is no hardware fault.
215
Jitter Buffer Overrun - Trap ID:743

Use this procedure to clear the 'Jitter Buffer Overrun' alarm.
Cause
The transmit clock is either loopback clock or the system clock and selected clock rate does
not match the E1 source clock.
Clock recovery lock is achieved using differential clock recovery method, but the two ends of
circuit are not synchronized to the same PRC.
Adaptive clock recovery mode is used and the delay variations are very high and hence the
clock recovery process does not succeed.
Protection switching events.
Severity
Critical
Object Affected
CESIWF
Impact
The impact of this alarm is bit errors and is traffic affecting.
Clearing Procedure
1. Increase the Jitter Buffer Depth for the CESIWF provisioned.
2. Check for the 'Jitter Buffer Overrun' alarm.
If the alarm is not present, the procedure is complete.
If the alarm is present, check network path QOS and rectify for any congestion
issues.
216
FarEnd IWF failure - Trap ID:744

Use this procedure to clear the 'FarEnd IWF failure' alarm.
Cause
This alarm is raised when there is network (NNI) or IWF problem reported on Far End node.
Severity
Critical
Object Affected
CESIWF
Impact
Clearing Procedure
1. Check the link status of NNI and far end switch status for any alarms that could cause the
reporting of the 'FarEnd IWF failure' alarm at the local node.
If the cause is not detected, contact the next level of support.
If the cause is detected, perform the appropriate procedure to clear the alarm at
the far end. Go to step 3.
2. Check if 'Far End IWF failure' alarm is cleared at the near end.
217
FarEnd TDM Failure Trap ID:745

Use this procedure to clear the 'FarEnd TDM failure' alarm.
Cause
This alarm is raised when there is a problem on the PDH side on Far End node.
Severity
Critical
Object Affected
CESIWF
Impact
Clearing Procedure
1. Check the far end PDH connectivity status for any alarms that could cause the reporting of
the 'FarEnd TDM failure' alarm at the local node.
If cause is not detected, contact the next level of support.
If cause is detected, then perform the appropriate procedure to clear the alarm at
the far end. Go to step 3.
2. Check if 'FarEnd TDM failure' alarm is cleared at the near end.
218
Jitter Buffer Underrun Trap ID:749

Use this procedure to clear the 'Jitter Buffer Underrun' alarm.This is a threshold crossing alert alarm.
Cause
The transmit clock is either loopback clock or the system clock and selected clock rate does
not match the E1 source clock.
Clock recovery lock is achieved using differential clock recovery method, but the two ends of
circuit are not synchronized to the same PRC.
Adaptive clock recovery mode is used and the delay variations are very high and hence the
clock recovery process does not succeed.
Protection switching events.
Severity
Critical
Object Affected
CESIWF
Impact
The impact of this alarm is bit errors and is traffic affecting.
Clearing Procedure
1. Decrease the Jitter Buffer Depth for the CESIWF provisioned.
2. Check for the 'Jitter Buffer Underrun' alarm.
219
Chapter 6
MS-SPRing/BLSR Alarms
This chapter describes MSSP alarms raised on Tejas Network Element and procedure to clear
them. The alarm clearing procedures are based on MS-SPRing/BLSR protection.
IN THIS CHAPTER
Invalid K Byte - Trap ID:673 ..................................................................... 222
Invalid K Byte East - Trap ID:626 ............................................................ 223
Invalid K Byte West - Trap ID:627 ........................................................... 224
Manual Switch Active on East - Trap ID:632 ......................................... 225
Manual Switch Active On West - Trap ID:634 ....................................... 226
Ring Switch Active - Trap ID:672 ............................................................. 227
Ring Switch East - Trap ID:423 ................................................................. 228
Ring Switch West - Trap ID:424................................................................ 229
221
Invalid K Byte - Trap ID:673

Use this procedure to clear the 'Invalid K Byte' alarm.
Cause
This alarm is raised when one or more of the following conditions are present:
Faulty fiber connection
Mismatch between the given ring map and the actual ring topology
If east port of one is connected to east of other NE, similarly West port then Invalid k byte alarm
is reported. Now issuing an exerciser command, the command is successfully accepted. The
result of 'failure of exerciser' is shown in the events history page.
Severity
Major
Object Affected
STM/OCn Port
Impact
The impact of the alarm is traffic affecting.
Clearing Procedure
To clear this alarm, check the ring topology and ensure that they match the ring map provisioned
on the network elements for the MS-SPRing/BLSR configuration.
222
Chapter 6 MS-SPRing/BLSR Alarms
Invalid K Byte East - Trap ID:626

Use this procedure to clear the 'Invalid K Byte East' alarm.
Cause
Faulty fiber connection.
Mismatch between the given ring map and the actual ring topology.
Note: If East port of one is connected to east of other node, then Invalid k byte alarm is
reported. Now issuing an exerciser command, the command successfully is accepted. The
result of "failure of exerciser" is shown in the events history page.
Severity
Major
Object Affected
MS-SPRing/BLSR
Impact
Traffic affecting
Clearing Procedure
1. Check the ring topology and the fibre connections with the ring map.
2. Check if the 'Invalid K byte East' alarm is cleared.
223
Invalid K Byte West - Trap ID:627

Use this procedure to clear the 'Invalid K Byte West' alarm.
Cause
Faulty fiber connection
Mismatch between the given ring map and the actual ring topology
Note: If West port of one is connected to west of other node, then Invalid k byte alarm is
reported. Now issuing an exerciser command, the command successfully is accepted. The
result of 'failure of exerciser' is shown in the events history page.
Severity
Major
Object Affected
MS-SPRing/BLSR
Impact
Traffic affecting
Clearing Procedure
1. Check the ring topology and the fibre connections with the ring map.
2. Check if the 'Invalid K byte West' alarm is cleared.
224
Manual Switch Active on East - Trap ID:632

Use this procedure to clear the 'Manual switch active on East' alarm.
Cause
This alarm is raised on any STM/OCn ports belonging to an MSSPRing/BLSR group if Manual
switch is applied on it.
Severity Level
Minor
Object Affected
MS-SPRing/BLSR
Impact
Impact of this alarm is that the traffic will be switched to the STM/OCn port to which the
manual switch is issued. The traffic will stay in the manually switched port or channel until again
manually/forcefully switched away from this path or signal failure condition occurs on this path.
Clearing Procedure
To clear the alarm,
1. Click Protection in the Navigation menu. Click MSSP-Ring/BLSR link. The MS-SPRing page
is displayed.
2. Click on the desired MS-SPRing facility under the view field. The Protection Provisioning
page is displayed.
3. Click Clear on the side (East) on which Manual Switch was given (this can be found by
seeing the alarm Ring switch, being present on east or west). A success message is displayed.
4. Check if the 'Manual switch active on East' alarm on STM/OC port is cleared. If the alarm is
cleared, you have completed the procedure.
225
Manual Switch Active On West - Trap ID:634

Use this procedure to clear the 'Manual switch active on West' alarm.
Cause
This alarm is raised on any STM ports belonging to an MSSPRing/BLSR group if Manual switch
is applied on it.
Severity Level
Minor
Object Affected
MS-SPRing/BLSR
Impact
Impact of this alarm is that the traffic will be switched to the STM/OC port to which the manual
switch is given. The traffic will stay in the manually switched port or channel until again
manually/forcefully switched away from this path or signal failure condition occurs on this path.
Clearing Procedure
To clear the alarm,
1. Click Protection in the Navigation menu. Click MSSP-Ring link. The MS-SPRing page is
displayed.
2. Click on the desired MS-SPRing facility under the View field. The Protection Provisioning
page is displayed.
3. Click Clear on the side (West) on which Manual Switch was given (this can be found by
seeing the alarm Ring switch, being present on east or west). A success message is displayed.
4. Check if the 'Manual switch active on West' alarm on STM/OC port is cleared. If the alarm is
cleared, you have completed the procedure.
226
Ring Switch Active - Trap ID:672

Use this procedure to clear the 'Ring Switch Active' alarm.
Cause
External command like force or manual switch exists
There is loss of signal, excessive errors or signal degrade on the optical port of the facility
Card missing/ faulty card exists where the facility is provisioned
Port admin is down at the location where the facility is provisioned
Any of the above cause is present in the adjacent node connected through that facility.
Severity
Major
Object affected
STM/OCn Port
Impact
Clearing Procedure
To clear the alarm,
1. Check for Forced switch active/Manual switch/signal fail/card missing or other active alarms
present for the port/slot where the facility is provisioned.
2. Clear any active alarms by following respective trouble clearing procedures.
227
Ring Switch East - Trap ID:423

Use this procedure to clear the 'Ring Switch East' alarm.
Cause
Severity
Major
Object affected
MS-SPRing/BLSR
Impact
Clearing Procedure
To clear the alarm,
228
Ring Switch West - Trap ID:424

Use this procedure to clear the 'Ring Switch West' alarm.
Cause
Severity
Major
Object affected
MS-SPRing/BLSR
Impact
Clearing Procedure
To clear the alarm,
229
Chapter 7
Security Alarms
This chapter describes Security alarms raised on Tejas Network Element and procedure to clear
them.
IN THIS CHAPTER
All Radius Servers are Unavailable - Trap ID:647 .................................. 231
Primary Radius Server Unavailable - Trap ID:645 .................................. 232
Secondary Radius Servers Unavailable - Trap ID:646 ............................ 233
All Radius Servers are Unavailable - Trap ID:647

Use this procedure to clear the 'All Radius Servers are Unavailable' alarm.
Cause
This alarm is raised when the remote authentication request to all RADIUS servers expires after a
user-provisionable timeout and no response is received from any RADIUS server.
Severity
Major
Object Affected
Shelf
Impact
The impact of the alarm is non-traffic affecting.
Clearing Procedure
1. Verify RADIUS server is reachable from node. If not, provision at least one of the reachable
RADIUS Server from UI and start the server.
2. If the alarm persists, check if the one of the RADIUS server from UI has its secret key
matching as that of the server. If the secret key is not the same, then edit the same.
3. Check if the All Radius Servers are Unavailable alarm is still present on local node.
231
Primary Radius Server Unavailable - Trap ID:645

This procedure helps you clear the 'Primary Radius Server Unavailable' alarm.
Cause
This alarm is raised when
remote authentication request to the Primary RADIUS server expires after a user-
provisionable timeout and no response is received from the primary RADIUS server
DCN connectivity is lost between the network element and the RADIUS server
other parameters are incorrectly configured. For example, secret and vendor specific
attributes
Severity
Minor
Object affected
Radius
Impact
Non-traffic affecting. If no servers are reachable, the new management sessions (WUI, TL1)
based on centralized user accounts may not be possible. User account changes on the RADIUS
server may not be synchronized on the network element under this condition.
Procedure
1. Verify Primary RADIUS server is reachable from node. If not, provision a reachable Primary
radius server and start the server.
2. If the alarm persists, check if the Primary RADIUS server from UI has its secret key
matching as that of the server. If the secret key is not the same, then edit the same.
3. Check if the 'Primary RADIUS Server Unavailable' alarm is present on local node.
232
Chapter 7 Security Alarms
Secondary Radius Servers Unavailable - Trap ID:646

Use this procedure to clear the 'Secondary Radius Server Unavailable' alarm.
Cause
This alarm is raised when the remote authentication request to the secondary RADIUS server
expires after a user-provisionable timeout and no response is received from the secondary
RADIUS server.
Severity
Minor
Object affected
Radius
Impact
Clearing Procedure
1. Verify Secondary RADIUS server is reachable from node. If not, provision a reachable
Secondary radius server and start the server.
2. If alarm persists, check if the Secondary RADIUS server from UI has its secret key matching
as that of the server. If the secret key is not the same, then edit the same.
3. Check if the 'Secondary RADIUS Server Unavailable' alarm is present on local node.
233
Chapter 8
L2 Alarms
This chapter describes L2 alarms raised on Tejas Network Element and procedure to clear them.
IN THIS CHAPTER
CBG Member Not Deskewable - Trap ID:894 ....................................... 236
CCM Interval Mismatch - Trap ID:663 .................................................... 237
FDB Limited Reached - Trap ID:686 ....................................................... 238
Forced Down Link Integrity - Trap ID:517 ......................................... 239
Group Label Mismatch on CBG Member - Trap ID:897 ..................... 240
Loop Detected - Trap ID:664 .................................................................... 241
Loss of Connectivity on CBG Member - Trap ID:895.......................... 242
Loss of Signal on Ethernet port - Trap ID:611 ....................................... 243
Multiple RPL Owners Configured - Trap ID:660................................... 244
No RPL Owner Configured - Trap ID:659 ............................................. 245
PacketTrunk OperStatus Down - Trap ID:694 ....................................... 246
Partial Loss of Capacity on CBG - Trap ID:893 ..................................... 247
RDI on CBG Member - Trap ID:896....................................................... 248
Remote and Local IP Match - Trap ID:693 ............................................. 249
Remote Defect Indication - Trap ID:662 ................................................. 250
Total Loss of Capacity on CBG - Trap ID:892 ....................................... 251
Unexpected MAID - Trap ID:661............................................................. 252
Unexpected MEPID - Trap ID:665 .......................................................... 253
Unexpected MD Level - Trap ID:666....................................................... 254
235
CBG Member Not Deskewable - Trap ID:894

Use this procedure to clear the 'CBG Member Not Deskewable' alarm.
Cause
This alarm is raised when the bandwidth of the member link under question is less than 1/6th of
the highest capacity member in the group.
Severity
Critical
Object affected
Ethernet Port
Impact
Member link will not be considered as part of the CBG.
Clearing Procedure
This alarm clears when ratio of the maximum and minimum capacity members is less than 6.
236
Chapter 8 L2 Alarms
CCM Interval Mismatch - Trap ID:663

Use this procedure to clear the 'CCM Interval Mismatch' alarm.
Cause
This alarm is raised when MEP receives a CCM frame with valid MD Level and a valid MAID,
but at a CCM interval different than local end configured interval.
Severity
Critical
Object affected
MEPs against ports, PBT tunnels and services over PBT tunnels.
Impact
This alarm is traffic affecting only when the protection switching due to CFM does not happen in
case there is a mismatch between the CCM intervals.
Clearing Procedure
To clear the alarm,
1. Check the CCM interval configured across the Maintenance Association.
2. Check the CCM interval of the associated MEP on the end-point where the remote MEP is
configured.
NOTE: This alarm clears when a MEP receives three consecutive CCM frames with correct
MD Level, MAID and CCM interval. Check if the 'CCM Interval Mismatch' alarm is cleared.
237
FDB Limited Reached - Trap ID:686

Use this procedure to clear the 'FDB Limited Reached' alarm.
Cause
This alarm is raised when the number of learnt MAC address reaches the configured limit in a
service.
Severity
Critical
Object affected
EVC
Impact
No more entries will be learnt. Any traffic which has to be forwarded to unlearnt MAC address
will be broadcasted to all ports in the service. The network throughput will get affected.
Clearing Procedure
To clear the alarm, understand the number of MAC address required to be learnt and
appropriately adjust the FDB limit.
238
Chapter 8 L2 Alarms
Forced Down Link Integrity - Trap ID:517

Use this procedure to clear the 'Forced Down-Link Integrity' alarm.
Cause
This alarm is raised when Ethernet port is forced down to propagate the network side fault or the
remote client fault. Forced down - link Integrity can happen only if TLS is configured.
Severity
Major
Object affected
Ethernet Port
Impact
Ethernet port link will be down.
Clearing Procedure
To clear the alarm,
Identify the network or the remote client fault that caused the link integrity operation and
following the clearing procedures of the source of the fault.
239
Group Label Mismatch on CBG Member - Trap ID:897

Use this procedure to clear the 'Group Label Mismatch on CBG Member' alarm.
Cause
This alarm is raised when the group label of the peer member is not the same as configured
value. The probable cause of this alarm are:
mis-connection between between Modem links belonging to two different CBG groups
misconfiguration of CBG Group Label on the peer nodes
Severity
Critical
Object affected
Ethernet Port
Impact
The member link will not be usable in the group because of the mismatch.
Clearing Procedure
This alarm is cleared when the group label of the peer member is same as the configured value.
Check on both ends that members ports are part of the correct CBG.
240
Chapter 8 L2 Alarms
Loop Detected - Trap ID:664

Use this procedure to clear the 'Loop Detected' alarm.
Cause
MEP receives CCM frame with MEPID, MAID, CCM interval, MD level and MAC address
same as of its own MEP.
Severity
Critical
Object affected
MEP
Impact
The impact of this alarm is non-traffic affecting.
Clearing Procedure
To clear the alarm,
1. Check the loop detection alarm.
2. Remove the loop from the network.
3. Alarm is cleared when no such packets are received in three consecutive frames.
241
Loss of Connectivity on CBG Member - Trap ID:895

Use this procedure to clear the 'Loss of Connectivity on CBG Member' alarm.
Cause
This alarm is raised when connectivity check messages or data frames are not received for
duration of 2.5 seconds.
Severity
Critical
Object affected
Ethernet Port
Impact
The member port under question becomes unusable in CBG.
Clearing Procedure
This alarm is cleared when connectivity check messages or data frames are received for duration
of 10 seconds. Check for any faults on the member link and clear them.
242
Chapter 8 L2 Alarms
Loss of Signal on Ethernet port - Trap ID:611

Use this procedure to clear the 'Loss of Signal' alarm.
Cause
there is a fiber cut (or)
the received signal level drops below an implementation determined threshold
Severity
Critical
Object affected
Ethernet Port
Impact
The impact of this alarm on the Ethernet ports is traffic-affecting.
Clearing Procedure
To clear the alarm,
1. Determine if the cable is faulty and replace the cable.
2. Check if the Loss of Signal alarm on Ethernet port is cleared.
243
Multiple RPL Owners Configured - Trap ID:660

Use this procedure to clear the 'Multiple RPL Owners Configured' alarm.
Cause
This alarm is raised when multiple RPL ports are configured in the ringlet.
Severity
Critical
Object affected
Ringlet
Impact
ERP configured will not be usable.
Clearing Procedure
To clear the alarm,
1. Identify the correct RPL port in the ringlet.
2. Delete the configuration on other nodes where RPL is configured and re-create them without
RPL.
244
Chapter 8 L2 Alarms
No RPL Owner Configured - Trap ID:659

Use this procedure to clear the 'No RPL Owner Configured' alarm.
Cause
This alarm is raised when no RPL is configured on the ERP ringlet.
Severity
Critical
Object affected
Ringlet
Impact
ERP configured will not be usable.
Clearing Procedure
To clear the alarm,
1. Identify the RPL port in the ringlet.
2. Delete the ringlet configuration on the identified node and re-create the ringlet with RPL port
notified.
245
PacketTrunk OperStatus Down - Trap ID:694

Use this procedure to clear the 'PacketTrunk OperStatus Down' alarm.
Cause
This alarm is raised when an operational packet trunk goes down.
Severity
Minor
Object affected
Packet Trunk
Impact
The services created in NMS on the packet trunk may not get activated.
Clearing Procedure
To clear the alarm,
Check for any faults or mismatch in LLDP settings on both the ends of the packet trunk and
correct them. This alarm clears when the LLDP messages are received correctly and adjacency is
established.
246
Chapter 8 L2 Alarms
Partial Loss of Capacity on CBG - Trap ID:893

Use this procedure to clear the 'Partial Loss of Capacity on CBG' alarm.
Cause
This alarm is raised on the group whe some members are operationally down.
Severity
Minor
Object affected
Channel Bonding Group
Impact
The entire Channel Bonding Group capacity will not be used.
Clearing Procedure
To clear the alarm,
Check for any faults on individual members and correct them. The alarm clears when all the
members are operationally up.
247
RDI on CBG Member - Trap ID:896

Use this procedure to clear the 'RDI on CBG Member' alarm.
Cause
This alarm is raised when RDI indication is received and the condition persists for 2.5 seconds.
Severity
Critical
Object affected
Ethernet Port
Impact
Indicates that there is a problem on the far end member of the link.
Clearing Procedure
This alarm is cleared when RDI indication is not received and condition persists for 10 seconds.
Check for any faults on the far end of the member link.
248
Chapter 8 L2 Alarms
Remote and Local IP Match - Trap ID:693

Use this procedure to clear the 'Remote and Local IP Match' alarm.
Cause
This alarm is raised when the remote IP and local IP are same when packet trunk is dynamically
discovered.
Severity
Minor
Object affected
Packet Trunk
Impact
Indicates a mis-connection. This trunk cannot be used in NMS for service creation.
Clearing Procedure
To clear the alarm,
Check the physical connectivity and correct it. The alarm clears when correct connectivity is
made.
249
Remote Defect Indication - Trap ID:662

Use this procedure to clear the 'Remote Defect Indication' alarm.
Cause
This alarm is raised when received RDI bit on a MEP indicates a problem on the remote MEP.
Severity
Critical
Object affected
MEP
Impact
Indicates fault on the remote end. If not resolved, this may lead to traffic loss in case of another
fault.
Clearing Procedure
To clear the alarm,
1. Clear the fault existing on the remote end MEP.
2. Check the RMEP ID and MEP ID on both the ends and ensure correctness.
250
Chapter 8 L2 Alarms
Total Loss of Capacity on CBG - Trap ID:892

Use this procedure to clear the 'Total Loss of Capacity on CBG' alarm.
Cause
This alarm is raised when all members are operationally down.
Severity
Critical
Object affected
Channel Bonding Group
Impact
The Channel Bonding Group configured will not be usable.
Clearing Procedure
To clear the alarm,
1. Check each member link for any faults and clear them.
2. This alarm clears when any one of the members become operationally up.
251
Unexpected MAID - Trap ID:661

Use this procedure to clear 'Unexpected MAID' alarm on a tunnel group.
Cause
This alarm is raised when there is short Maintenance Association (MA) name mismatch on either
end of the Maintenance End Point (MEP).
Severity
Critical
Object affected
MEPs against ports, PBT tunnels and services over PBT tunnels
Impact
Clearing Procedure
This alarm is cleared when the short Maintenance Association (MA) name is same on both ends
of the MEP.
252
Chapter 8 L2 Alarms
Unexpected MEPID - Trap ID:665

Use this procedure to clear the 'Unexpected MEPID' alarm.
Cause
A MEP receives a CCM frame with correct MEG Level, correct MEG ID but with unexpected
MEPID.
Severity
Critical
Object affected
Impact
Procedure
To clear the alarm,
1. Check MEPID of remote MEP. MEPID of the remote MEP should be part of remote
MEPIDs of the local MEP.
2. Alarm is cleared when no mismatch in MEPID is detected in three consecutive frames.
253
Unexpected MD Level - Trap ID:666

Use this procedure to clear the 'Unexpected MD Level' alarm.
Cause
This alarm is raised on the group when there is misconfiguration or a leak in the CFM domains.
The MEP has detected CFM frames at a lower MD level.
Severity
Critical
Object affected
Impact
Traffic protected by the MEP will be down.
Clearing Procedure
To clear the alarm,
Identify the misconfiguration or the leak and correct it. The alarm clears when mis-configuration
or leak of CFM domains are corrected.
254
Chapter 9
EMS Alarms
This chapter describes alarms raised on Tejas Element Management Systems and procedure to
clear them.
255
IN THIS CHAPTER
Alarms from the Anonymous Node - Trap ID:105 ............................... 257
Amplifier Not Reachable - Trap ID:111 .................................................. 258
Audit Log Size Exceeded - Trap ID:......................................................... 259
Audit Log Size Exceeded - Trap ID:134 .................................................. 260
Audit Log Size Exceeded - Trap ID:135 .................................................. 261
Audit Log Archive Size Exceeded - Trap ID:136 ................................... 262
CPU is Fully Loaded - Trap ID:128 .......................................................... 265
CPU Utilization Exceeded - Trap ID:127 ................................................ 266
CPU Utilization Is High - Trap ID:126 .................................................... 267
Disk Usage Almost Full - Trap ID:125..................................................... 268
Disk Usage Exceeded - Trap ID:124 ........................................................ 269
Disk Usage is High - Trap ID:133 ............................................................. 270
EMS Backup Fail Alarm - Trap ID:8002.................................................. 271
EMS License is going to expire - Trap ID:132 ........................................ 272
EVC Degrade - Trap ID:119 ...................................................................... 273
EVC Failure ................................................................................................... 274
Farend Client Signal Degrade - Trap ID:121 ........................................... 275
Farend Client Signal Failure - Trap ID:122 .............................................. 276
Historical Alarm Data out of Sync - Trap ID:110 .................................. 276
HistAlarms size exceeded - Trap ID:139.................................................. 277
HistAlarms size exceeded - Trap ID:141.................................................. 278
HistAlarms Archive size exceeded - Trap ID:142................................... 279
Memory Usage Exceeded - Trap ID:123.................................................. 282
Maximum Alarm Count exceeded - Trap ID:129 ................................... 283
No Connectivity to Slave - Trap ID:107 .................................................. 284
Node Alarm Out of Sync - Trap ID:112 .................................................. 285
Node Config out of Sync - Trap ID:106 .................................................. 286
Node Not Reachable - Trap ID:100 ......................................................... 287
Node Router ID changed - Trap ID:145.................................................. 288
Node Upload Completed - Trap ID:102 .................................................. 289
Node Upload Failed - Trap ID:103 ........................................................... 290
Node Upload Started - Trap ID:101 ......................................................... 291
One Way Communication from Node to Server - Trap ID:114 .......... 292
One Way Communication from Server to Node - Trap ID:113 .......... 293
Total NodeWeight About to Exceed the Licensed Value ..................... 294
Total Number of Nodes About to Exceed the Licensed Value - Trap ID:131
......................................................................................................................... 295
Trunk Oper Down - Trap ID:389 ............................................................. 296
256
Chapter 9 EMS Alarms
Alarms from the Anonymous Node - Trap ID:105

Use this procedure to clear the 'Alarms from The Anonymous Node' alarm.
Cause
This alarm is raised by EMS when the node which is not added in EMS sends the SNMP traps to
EMS.
Severity
Warning
Impact
The impact of the alarm is non-EMS service affecting.
Clearing Procedure
To clear this alarm, remove trap destination from node manually.
257
Amplifier Not Reachable - Trap ID:111

Use this procedure to clear the 'Amplifier Not reachable' alarm.
Cause
This alarm is raised when amplifier is not reachable.
Severity
Warning
Object Affected
EMS and amplifier
Impact
Cannot provision amplifier
Clearing Procedure
It gets clear when connectivity to the node is restored.
258
Audit Log Size Exceeded - Trap ID:

Use this procedure to clear the 'Audit Log Size Exceeded' alarm.
Cause
This alarm is raised when the entries in AuditLog table exceeds the 50% of configured maximum
value.
Severity
Minor
Object Affected
EMS
Impact
The impact is that the new audit entries will not be entered.
Clearing Procedure
1. Click Administration > Data Management.
2. Configure Archiving in case of AuditLog and Purging in case of AuditLogArchive.
259
Audit Log Size Exceeded - Trap ID:134

Cause
value.
Severity
Major
Object Affected
EMS
Impact
Clearing Procedure
1. Click Administration > Data Management.
260
Audit Log Size Exceeded - Trap ID:135

Cause
value.
Severity
Critical
Object Affected
EMS
Impact
Clearing Procedure
1. Go to Administration > Data Management.
261
Audit Log Archive Size Exceeded - Trap ID:136

Use this procedure to clear the 'Audit Log Archive Size Exceeded' alarm.
Cause
This alarm is raised when the entries in AuditLog Archive table exceeds the 50% of configured
maximum value.
Severity
Minor
Object Affected
EMS
Impact
The impact of the alarm is that the data will not be archived beyond the count limit.
Clearing Procedure
To clear this alarm, User needs to purge the archived data manually.
262

Cause
maximum value.
Severity
Major
Object Affected
EMS
Impact
Clearing Procedure
263

Cause
maximum value.
Severity
Critical
Object Affected
EMS
Impact
Clearing Procedure
264
CPU is Fully Loaded - Trap ID:128

Use this procedure to clear the 'CPU Is Fully Loaded' alarm.
Cause
This alarm is raised when Server CPU usage exceeds critical threshold limit set in server as
properties file (default value 95%).
Severity
Critical
Object Affected
EMS application/EMS Server
Impact
The impact of the alarm is the application slow down
Clearing Procedure
The alarm is automatically cleared when task processing is less.
265
CPU Utilization Exceeded - Trap ID:127

Use this procedure to clear the 'CPU Utilization Exceeded' alarm.
Cause
This alarm is raised when Server CPU usage exceeds Major threshold limit set in server as
properties file (Default value 65%).
Severity
Major
Object Affected
EMS application/EMS Server
Impact
The impact of the alarm is the application slow down.
Clearing Procedure
The alarm will get automatically cleared when task processing is less.
266
CPU Utilization Is High - Trap ID:126

Use this procedure to clear the 'CPU Utilization Is High' alarm.
Cause
This alarm is raised when Server CPU usage exceeds Minor threshold limit set in server as
properties file (Default value 50%).
Severity
Minor
Object Affected
EMS Application
Impact
Application slow down
Clearing Procedure
This alarm will be cleared when unnecessary and non-ems process are terminated.
267
Disk Usage Almost Full - Trap ID:125

Use this procedure to clear the 'Disk Usage Almost Full' alarm.
Cause
This alarm is raised when the Hard Disk is 95% full.
Severity
Critical
Object Affected
EMS
Impact
Slow operations
Not able to store any more data
Clearing Procedure
1. Upgrade the disk or delete/remove unnecessary files from the disk partition.
2. It is automatically cleared when the Disk usage drops down below 90%.
268
Disk Usage Exceeded - Trap ID:124

Use this procedure to clear the 'Disk Usage Exceeded' alarm.
Cause
Severity
Major
Object Affected
EMS Application
EMS Server
Impact
Slow operations
Clearing Procedure
269
Disk Usage is High - Trap ID:133

Use this procedure to clear the 'Disk Usage is High' alarm.
Cause
Severity
Minor
Object Affected
EMS Application
EMS Server
Impact
Slow operations
Clearing Procedure
270
EMS Backup Fail Alarm - Trap ID:8002

Use this procedure to clear the 'EMS Backup Fail alarm'.
Cause
Disk is 100% full i.e. when there is not enough space for writing data on disk.
MySQL is corrupt or if some file is missing in the database.
FTP credentials are incorrect, like wrong username or password provided and unreachable
server.
Severity
Critical
Object Affected
EMS Server
Impact
The impact of this alarm is the failure of EMS Backup operation which the user will be notified
by raising the alarm along with the reason of failure.
Clearing Procedure
This alarm will be automatically cleared on the next successful backup.
While scheduling an EMS backup, following points must be considered:

Ensure that the path or directory mentioned for backup storage has enough free space.
Ensure that the FTP credentials of the Backup server (IP address, username, and password)
are correct and the remote server is accessible all time during the EMS backup activity.
271
EMS License is going to expire - Trap ID:132

Use this procedure to clear the 'EMS License is going to expire' alarm.
Cause
This alarm is raised the number of days (default value 30 days) before license expiry date.
Severity
Critical
Object Affected
EMS Application
Impact
Not able to run the application after the expiry date.
Clearing Procedure
To clear this alarm, buy the new license with new expiry or upgrade the existing license.
272
EVC Degrade - Trap ID:119

Use this procedure to clear the 'EVC Degrade' alarm.
Cause
This alarm is raised when traffic is affected on EVC.
Severity
Minor
Object Affected
EVC
Impact
EVC traffic degraded
Clearing Procedure
It gets clear when there are no alarms on EVC.
273
EVC Failure
Use this procedure to clear the 'EVC Down' alarm.
Cause
This alarm is raised when it fails to connect to EVC traffic.
Severity
Major
Object Affected
EVC
Impact
EVC traffic is down.
Clearing Procedure
It gets clear when there are no alarms on EVC.
274
Farend Client Signal Degrade - Trap ID:121

Use this procedure to clear the 'Farend Client Signal Degrade' alarm.
Cause
This alarm is raised when one of Ethernet or VCG has Signal Degrade alarm.
Severity
Minor
Object affected
EVC
Impact
Point-to-Point EVC is degraded.
Clearing Procedure
It gets clear when there is no alarms on Point-to-Point EVC.
275
Farend Client Signal Failure - Trap ID:122

Use this procedure to clear the 'Farend Client Signal Down' alarm.
Cause
This alarm is raised when one of Ethernet or VCG has Signal Failure alarm.
Severity
Major
Object affected
EVC
Impact
Point-to-Point EVC is down.
Clearing Procedure
It gets clear when no alarms on Point-to-Point EVC.
Historical Alarm Data out of Sync - Trap ID:110

Use this procedure to clear the 'Historical Alarm Data Out Of Sync' alarm.
Cause
This event is raised when node is unable to send the alarm history to EMS because it is either
been deleted or got corrupted on the node. This alarm indicates that EMS does not have
complete historical fault data of the node.
Severity
Warning
Impact
Clearing Procedure
276
HistAlarms size exceeded - Trap ID:139

Use this procedure to clear the 'HistAlarms size exceeded' alarm.
Cause
This alarm is raised when the entries in HistAlarm table exceeds the 50% of configured
maximum value.
Severity
Minor
Object Affected
EMS
Impact
Clearing Procedure
To clear this alarm, User needs to archive or purge the historical alarms data manually.
277
HistAlarms size exceeded - Trap ID:141

Use this procedure to clear the 'HistAlarms size exceeded' alarm.
Cause
This alarm is raised when the entries in HistAlarm table exceeds the 90% of configured
maximum value.
Severity
Critical
Object Affected
EMS
Impact
Clearing Procedure
To clear this alarm, User needs to archive or purge the historical alarms data manually.
278
HistAlarms Archive size exceeded - Trap ID:142

Use this procedure to clear the 'HistAlarms Archive size exceeded' alarm.
Cause
This alarm is raised when the entries in HistAlarm Archive table exceeds the 50% of configured
maximum value.
Severity
Minor
Object Affected
EMS
Impact
Clearing Procedure
To clear this alarm, User needs to purge the historical alarms archive data manually.
279

Cause
maximum value.
Severity
Major
Object Affected
EMS
Impact
Clearing Procedure
280

Cause
maximum value.
Severity
Critical
Object Affected
EMS
Impact
Clearing Procedure
281
Memory Usage Exceeded - Trap ID:123

Use this procedure to clear the 'Memory Usage Exceeded' alarm.
Cause
This alarm is raised when Physical Memory (RAM) usage exceeds the threshold limit set in server
as properties file (Default value 80%).
Severity
Critical
Object Affected
EMS
Impact
The impact of the alarm is the application will slow down.
Clearing Procedure
1. Terminate unnecessary and non-ems process.
2. If the alarm persists, upgrade the physical memory of the server if possible.
3. It is automatically cleared when the RAM usage drops down below 70%.
282
Maximum Alarm Count exceeded - Trap ID:129

Use this procedure to clear the 'Max Alarm Count exceeded' alarm.
Cause
This alarm is raised when total number of active alarms present in EMS exceeds the threshold
limit (Default value:10000 for Active alarms) set in server. The property can be set for specific
severity alarm values like ACTIVE ALARMS, CRITICAL, MAJOR, MINOR alarm. Types.of
alarm to monitor=ACTIVEALARMS.
Alarm count to be monitored
If ACTIVEALARMS: then it is for [Critical + major + minor]

If CRITICAL: then it is for [Critical + major + minor]
If MAJOR: then it is for [major + minor]
If MINOR: then it is only for [minor]
Severity
Critical
Object Affected
EMS Application
Impact
New alarms from network elements will not be reported in the EMS if max count is exceeded.
This will lead to service outage to customer and restoration of services will take longer time. May
cause Unreliable service from the provider.
Applies to
Server
Clearing Procedure
To clear this alarm, rectify the alarms in the network.
283
No Connectivity to Slave - Trap ID:107

Use this procedure to clear the 'No Connectivity To Slave' alarm.
Cause
This alarm is raised for the slave of a Hot standby EMS system. This alarm is raised when:
Slave becomes unreachable from the master due to network failure
Hot standby server is not running on the slave
Severity
Critical
Objected Affected
EMS
Impact
If there is a network failure between master server and slave server, then slave server cannot
switch over to master server. You cannot forcibly switch the slave to master.
Clearing Procedure
1. From the master server, check whether slave is reachable. If not, go to step 3.
2. Execute the following command in Command-Line Interpreter: /etc/init.d/ems status
3. Check whether Hot Standby is running on the slave server. If not, execute the following
command: /etc/init.d/ems start.
4. If alarm still persists in the master, contact your next level of support.
5. Restore the connectivity between master and slave.
284
Node Alarm Out of Sync - Trap ID:112

Use this procedure to clear the 'Node Alarm Out of Sync' alarm.
Cause
This alarm is raised when the node alarm count is not in-sync with EMS alarm count for that
node.
Severity
Warning
Object Affected
EMS
Impact
Non-traffic affecting
Clearing Procedure
Alarm gets cleared when the alarm count is in-sync with EMS alarm count. It can also be cleared
by force uploading alarms.
To forcefully upload the alarm to EMS, select the node and right click, select upload > alarm.
This will forcefully upload node alarm to EMS. When the count of alarms in node and EMS are
same, the alarm gets cleared.
285
Node Config out of Sync - Trap ID:106

Use this procedure to clear the 'Node Config Out of Sync' alarm.
Cause
This alarm is an indication that EMS database for that node may not be in sync with nodes
current configuration. This alarm is raised when:
SNMP agent on the node is not responding
Node load average is too high to respond to EMS getObjects/getChanges queries within
EMS timeout limit
Because of network congestion, SNMP packets (request from EMS or response from node)
may get dropped
Node is unreachable from EMS
Severity
Warning
Objected Affected
EMS
Impact
Node cannot be configured from EMS. Any configuration on the node can be done only after
this alarm is cleared.
Clearing Procedure
1. If 'Node not reachable alarm' is also there, see Node Not Reachable see "Node Not
Reachable - Trap ID:100" on page 287, then restore connectivity between EMS and node
and then force upload node from EMS. If force uploading of the node succeeds, proceed to
step 5.
2. Telnet to the node and issue 'netstat lun | grep 161' command. Verify the RecvQBuffer buffer
size of port 161. If the RecvQBuffer buffer size is zero, proceed to step 4
3. It indicates that SNMP agent on node is not working. Collect logs and stack trace of node
and reboot the node. It may be traffic affecting.
4. Telnet to the node and run uptime command to check the load average of the node. If it is
high, contact your next level of support.
286
Node Not Reachable - Trap ID:100

Use this procedure to clear the 'Node Not Reachable' alarm.
Cause
This alarm is an indication that there is no IP connectivity between EMS and this node. This
alarm is raised when EMS is not receiving alive messages from a node. This may be due to
following reasons:
Trap destination address of the EMS is not set on the node
Node is not reachable from EMS and/or EMS is not reachable from node
Due to some congestion, the network drops SNMP traps from a node
EMS machine firewall setting is high and so traps are not passed from lower layer of IP stack to
upper layers.
Severity
Warning
Object affected
EMS
Impact
This alarm is non-traffic affecting. Due to this alarm
EMS is not having the updated configuration details of the node
Node cannot be operated from EMS
Clearing Procedure
1. Check whether trap destination address of the EMS is set on the node.
2. Ping the node from EMS. If it fails, establish IP connectivity between node and EMS.
3. Ensure that EMS machine firewall settings are set to low.
4. Check node logs to find out if there has been some problem with sending traps.
287
Node Router ID changed - Trap ID:145

Use this procedure to clear the 'Node Router ID Changed' alarm.
Cause
This alarm is raised when the Router ID is changed at the node level.
Severity
Critical
Object affected
EMS
Impact
The impact of the alarm is that the node will be in unreachable state at EMS level.
Clearing Procedure
1. Delete the node from the Node Administration page of the EMS.
2. Readd the node with new Router ID.
3. Check if the alarm cleared.
288
Node Upload Completed - Trap ID:102

Use this procedure to clear the 'Node Upload Completed' alarm.
Cause
This event is raised when configuration details of the node is successfully uploaded to the EMS
through SNMP protocol. EMS database is now updated with latest configuration details of the
node.
Severity
Warning
Object affected
EMS
Impact
Clearing Procedure
No action is necessary. This event is raised for information purposes only.
289
Node Upload Failed - Trap ID:103

Use this procedure to clear the 'Node Upload Failed' alarm.
Cause
This alarm is raised when EMS failed to upload node configuration. This also results in raising of
'Node Config Out of Sync' alarm.
Severity
Warning
Object affected
EMS
Impact
Clearing Procedure
1. If Node Not Reachable alarm' is raised, see Node Not Reachable see "Node Not Reachable
- Trap ID:100" on page 287, then restore connectivity between EMS and node and then
force upload node from EMS. If alarm persists, contact your next level of support.
2. Telnet to the node and issue netstat lun | grep 161 command. Verify the RecvQBuffer
buffer size of port 161. If the buffer size is zero, proceed to step 4
3. If the SNMP agent on node is not working, collect logs, stack trace of node and reboot the
node. If the alarm persists, contact your next level of support
4. Check the load average of the node. If it is high, then try to bring it down and force upload
node from EMS
290
Node Upload Started - Trap ID:101

Use this procedure to clear the 'Node Upload Started' alarm.
Cause
This event occurs when EMS starts to upload the configuration details of the node. Especially
when it sends SNMP request to upload node configuration.
Severity
Warning
Object affected
EMS
Impact
Clearing Procedure
291
One Way Communication from Node to Server - Trap

ID:114
Use this procedure to clear the 'One Way Communication from Node to Server' alarm.
Cause
This alarm is raised when there is a one-way connectivity from the node to server. This occurs
when the EMS is able to receive the alive messages but the communication from the server to
node fails. This communication failure may occur due to the following reasons:
Firewall is blocking the outgoing packets from the EMS.
There is no available route from the server to the node.
A connection cannot be established to the web server port 20080
Severity
Warning
Object affected
EMS
Impact
The node page cannot be launched from the EMS. All the set operations on the node such as the
creation of cross connects shall fail.
Clearing Procedure
1. Ensure that firewall is not blocking the packets.
2. Ensure that there is a route available from the server to the node.
3. Make sure that a connection can be established to the 20080 web server port of the node.
This alarm shall be automatically cleared within two minutes of establishing a connection to the
20080 port of the node.
292
One Way Communication from Server to Node - Trap

ID:113
Use this procedure to clear the 'One Way Communication from Server to Node' alarm.
Cause
This alarm is raised when the EMS is unable to receive messages from the node but the node is
reachable from the server. This may be due to the following reasons:
Trap destination address of the EMS is not set on the node
The network drops SNMP traps from the node due to traffic congestion
Firewall is blocking the packets
There is no available route from the node to EMS
Severity
Warning
Object affected
EMS
Impact
EMS will not have the updated configuration and alarm details of the node.
Clearing Procedure
To clear the alarm,
1. Check whether the EMS machine IP is set on the list of the trap destination addresses on the
node.
2. Ensure that firewall settings are correct.
3. Check the node logs and verify whether node is able to send the packets.
4. Ensure that there is a route available from the node to the EMS.
Once the EMS is able to receive messages, then it will automatically clear the alarm.
293
Total NodeWeight About to Exceed the Licensed Value

Use this procedure to clear the 'Total NodeWeight About to Exceed the Licensed Value' alarm.
Cause
This alarm is raised when Number of STM/OCn equivalents enrolled in EMS exceeds the
threshold limit (80% by default) with respect to the entry provided in license file for 'Number of
STM/OCn equivalents'.
NOTE: The default values can be modified in server properties file. If values are modified,
EMS application should be restarted.
Severity
Critical
Object Affected
EMS application
Impact
Not able to add more STM/OCn equivalents.
Clearing Procedure
To clear this alarm, buy the license to support more number of nodes or delete some of the
nodes. If alarm persists, contact your next level of support.
294
Total Number of Nodes About to Exceed the Licensed

Value - Trap ID:131
Use this procedure to clear the 'Total Number of Nodes About to Exceed the Licensed Value' alarm.
Cause
This alarm is raised when Number of Nodes Uploaded in EMS exceeds the threshold limit (80%
by default) with respect to the entry provided in license file for 'Number of manageable nodes.
Severity
Critical
Object Affected
EMS Application
Impact
Not able to add more nodes
Clearing Procedure
To clear this alarm, buy the license to support more number of nodes or delete some of the
nodes.
295
Trunk Oper Down - Trap ID:389

Use this procedure to clear the 'Trunk Oper Down' alarm.
Cause
This alarm is raised when link status goes down on which trunk is present.
Severity
Minor
Object affected
Trunk
Impact
Link will be shown as down in EMS, but traffic will be up if port is up.
Clearing Procedure
Make the link up if it is down.
296
Chapter 10
NMS Alarms
This chapter describes alarms raised on Tejas Network Management Systems and procedure to
clear them.
IN THIS CHAPTER
Path failed ...................................................................................................... 298
Circuit is unprotected................................................................................... 299
Traffic Loss.................................................................................................... 300
EMS is not reachable ................................................................................... 301
Disk Usage alarm .......................................................................................... 302
Slave not reachable ....................................................................................... 303
Slave DB not reachable ............................................................................... 304
Loop Back Alarm ......................................................................................... 305
All Managed Element Unavailable Alarm ................................................ 306
Bandwidth over-provisioned ...................................................................... 307
QoS Mis-configuration ................................................................................ 308
Undiscovered/Incomplete entities found in QoS Domain ................... 309
297
Path failed
Use this procedure to clear the 'Path failed' alarm.
Cause
This alarm is raised when the work path is failed in a diamond service.
Severity
Minor
Object affected
NMS
Impact
The impact of the alarm is not service affecting.
Clearing Procedure
Identify the alarms on backup path and clear it.
298
Chapter 10 NMS Alarms
Circuit is unprotected
Use this procedure to clear the 'Circuit is unprotected' alarm.
Cause
This alarm is raised when the work and protect path is failed and there is only one work path
operating in the diamond service.
Severity
Major
Object affected
NMS
Impact
The impact of the alarm is not service affecting.
Clearing Procedure
Identify the alarms on work path or protect path and clear it.
299
Traffic Loss
Use this procedure to clear 'Traffic Loss' alarm.
Cause
This alarm is raised when all the paths are failed in a diamond service.
Severity
Critical
Object affected
NMS
Impact
Clearing Procedure
Identify the alarms on work path or protect path (any one of the path) and clear it.
300
EMS is not reachable

Use this procedure to clear the 'EMS is not reachable' alarm.
Cause
This alarm is raised when the communication between NMS and EMS is lost. This may be due to
following reasons:
Network failure
EMS not running
Authentication failure
EMS IP not reachable from NMS
Some congestion in the network or communication packet drops from EMS to NMS
Severity
Major
Object affected
NMS
Impact
This alarm is non-traffic affecting. Due to this alarm
NMS is not having the updated configuration details of the EMS
EMS cannot be operated from NMS
Clearing Procedure
To clear this alarm, identify the reason (network failure and/ authentication failure) for
communication loss between EMS and NMS and resolve accordingly.
301
Disk Usage alarm

Use this procedure to clear the 'Disk Usage alarm' alarm.
Cause
This alarm is raised when the Hard Disk Drive usage of any partition (/var, /home, /opt, /tmp)
is above 80%.
Severity
Critical
Object affected
NMS
Impact
Slow operations
Clearing Procedure
NOTE: Alarm status is updated after 12 hours.
302
Slave not reachable

Use this procedure to clear the 'Slave not reachable' alarm.
Cause
This alarm is raised for the slave of a Hot standby NMS system. This alarm is raised when:
Slave becomes unreachable from the master due to network failure
Hot standby server is not running on the slave
Severity
Critical
Object affected
NMS
Impact
If there is a network failure between master server and slave server, then slave server cannot
switch over to master server. You cannot forcibly switch the slave to master.
Clearing Procedure
To clear the alarm,
1. From the master server, check whether slave is reachable. If not, go to step 3.
2. Execute the following command in Command-Line Interpreter: /etc/init.d/nms status
3. Check whether Hot Standby is running on the slave server. If not, execute the following
command: /etc/init.d/nms start
303
Slave DB not reachable

Use this procedure to clear the 'Slave DB not reachable' alarm.
Cause
This alarm is raised for the slave of a Hot standby NMS system when slave DB server becomes
unreachable from the slave application server. This alarm is also observed if NMS is installed in
clustering mode.
Severity
Critical
Object affected
NMS
Impact
The impact of this alarm is that the slave machine goes into Standby Transition state. This results
in SLAVE machine becoming non-functional.
The Hot Standby feature will not work if this alarm is present.
Clearing Procedure
From the SLAVE application server, check whether the SLAVE DB server is reachable and
MySQL is running properly.
304
Loop Back Alarm

Use this procedure to clear the 'Loop Back' alarm.
Cause
This alarm is raised when the SNC circuit is placed in loopback mode through explicit user
command.
Severity
Critical
Object affected
Circuit
Impact
Due to this alarm, the circuit will be out of service when loopback is active. The loopback has to
be removed for the circuit to carry the live traffic.
Clearing Procedure
To clear the alarm,
1. Select the circuit on which the loopback is issued.
2. Remove the loopback.
305
All Managed Element Unavailable Alarm

Use this procedure to clear 'All Managed Element Unavailable' alarm.
Cause
This alarm is raised when the NMS and EMS are reachable but the nodes are unreachable.
Severity
Critical
Object affected
NMS
Impact
This alarm is non-traffic affecting. Due to this alarm:
NMS and EMS is not having the updated configuration details of the node
Node cannot be operated from EMS
Clearing Procedure
1. Check whether trap destination address of the EMS is set on the node.
2. Ping the node from EMS. If it fails, establish IP connectivity between node and EMS.
3. Ensure that EMS machine firewall settings are set to low.
4. Check node logs to find out if there has been some problem with sending traps.
306
Bandwidth over-provisioned
Use this procedure to clear the 'Bandwidth Over Provisioned' alarm.
Cause
This alarm is raised when the Bandwidth [per CoS (class of service) Queue] reserved on
Topological Links due to services riding over it exceeds the maximum limit for that particular
CoS.
Severity
Major
Object affected
NMS
Impact
Traffic on CoS Queue gets congested resulting in packet drops.
Services using CoS Value for which the Bandwidth Limit has exceeded on the TL won't be
provisioned from NMS.
Clearing Procedure
Delete the services using the CoS Value on their UNIs for which the Bandwidth Limit has
exceeded on the Topological Link.
307
QoS Mis-configuration
Use this procedure to clear 'QoS Misconfiguration' alarm.
Cause
This alarm is raised on ports of switches when non-compliant tunnels/services are provisioned
over switches which are in QoS Domain in NMS.
Severity
Major
Object affected
NMS
Impact
QoS cannot be guaranteed for packets sent through non-compliant services/tunnels.
Clearing Procedure
Delete the services and tunnels marked as Non-compliant and ride over QoS Domain switches.
308
Undiscovered/Incomplete entities found in QoS Domain

Use this procedure to clear the 'Undiscovered/Incomplete entities found in QoS Domain' alarm.
Cause
This alarm is raised when there are undiscovered objects such as MPLS Cross-connects or EVCs
present in QoS Domain Switches in NMS.
Severity
Major
Object affected
NMS
Impact
QoS cannot be guaranteed for packets sent through undiscovered objects (MPLS Cross-connects
and EVCs).
Clearing Procedure
To clear the alarm,
1. Trigger Service Discovery.
2. If the alarms are not cleared, then delete the undiscovered objects on QoS Domain Switches
from the node.
NOTE: The user can deactivate and delete undiscovered objects from NMS also.
309
Chapter 11
Restart Procedures
This chapter describes the restart procedures on the node.
IN THIS CHAPTER
Cold Restart Required: FPGA changed - Trap ID:614 .......................... 311
Cold Restart Required: FPGA changed - Trap ID:614

Use this procedure to Card level cold restart on the node.
Cause
This alarm is performed either when a new FPGA has to be programed as a part of new software
load or when the existing FPGA has to be reinitialized.
Severity Level
Major
Object Affected
Card
Impact
Affects the traffic of the card that is restarted.
Procedure
1. Log-in to the node. NE information preview pane is displayed.
2. Click Maintenance in the navigation pane.
3. Click Cold Reboot Cards. Cold Reboot Cards preview pane is displayed.
4. Select one card to be restarted. Click Submit.
5. Click Yes. Confirmation message is displayed that the card is successfully restarted.
NOTE: The DCN connectivity through the affected card will be hit and will be restored
within 1 to 2 minutes.
311
Chapter 12
Module Replacement Procedures

This chapter describes Module replacement procedures.
IN THIS CHAPTER
Ethernet Interface Card Replacement....................................................... 313
Fan Filter Replacement................................................................................ 314
Fan Module Replacement ........................................................................... 315
Power Supply Unit Replacement ............................................................... 316
SFP Pluggable Module Replacement......................................................... 317
Ethernet Interface Card Replacement

Use this procedure to replace the Ethernet Interface card.
Caution: Risk of damaging cards. Use electrostatic discharge protection to avoid

damaging cards.
Danger: Risk of damaging equipment. Do not use excessive force when removing or
inserting cards into the shelf.
Caution: Risk of traffic loss. Perform the procedure on one PSU at a time.
Replacement Procedure
1. Remove the interface connections from the card.
2. Unfasten the screws located at both the sides of card face plate using a Phillips (PH1)
screwdriver.
3. Operate the latches outwards to disengage the card from the backplane.
313
4. Slide out the card with the latches in open position along the guide ways.
Attention: User should wait 10 seconds between the removal of a card and its reinsertion.
5. Slide in the new card along the guide ways provided on the chassis with the latches in the
open position to engage them to the chassis groove.
6. Operate the two latches inwards simultaneously to engage the card to the backplane.
7. Fasten the screws located at both sides of card face plate using a Phillips (PH1) screwdriver.
8. Make the appropriate Ethernet interface connections and check for error free traffic flow.
9. Verify that no equipment related alarm is present against the card.
Fan Filter Replacement

Use this procedure to replace the fan filter replacement.
NOTE: During this procedure, there is no power or traffic disruption in the network element.
The user should try to minimize the duration for which no fan module is present in the
network element to avoid overheating of the network element which may affect some of the
functionalities of the network element.
1. Un-fasten the 4 M3 screws located at the top of the fan module using a Phillips (PH1)
screwdriver.
2. Remove the cover gently.
3. Remove the air filter from the slot.
4. Place the new air filter into the slot.
5. Fix the cover to the fan module.
6. Fasten the 4 M3 screws to the screw slot located on the top of the fan module using a
Phillips (PH1) screwdriver.
NOTE: Make sure the system is not running without a fan for long time.
314
Chapter 12 Module Replacement Procedures
Fan Module Replacement

Use this procedure to replace the fan module.
NOTE: During this procedure, there is no power or traffic disruption in the network element.
The user should try to minimize the duration for which no fan module is present in the
network element to avoid overheating of the network element which may affect some of the
functionalities of the network element.
1. Unfasten the captive screw located at bottom end of the face plate using a Phillips (PH1)
screwdriver.
2. Dis-engage the unit by pulling from the backplane connector and slide it out along the guide
way.
3. Slide in the new fan module along the guide ways provided on the chassis.
4. Fasten the screw located at bottom end of the face plate using a Phillips (PH1) screwdriver.
5. Ensure that no alarm is present against the fan module.
6. Ensure that there is no High temperature alarm for other circuit packs.
NOTE: Make sure the system is not running without a fan for long time. The fan tray unit
needs to be replaced if an alarm exists on the fan tray unit. Even the alarm exists on the Fan
tray unit, the system keeps working till the second fault occurs, if the Room temperature is
below 40 degree. So do not remove the Fan try unit till the replacement Unit is available and
the Fan tray replacement procedure should complete in 2 to 3 minutes.
315
Power Supply Unit Replacement

Use this procedure to replace the power supply unit of the node.

damaging cards.
inserting cards into the shelf.
Caution: Risk of traffic loss. Perform the procedure on one PSU at a time.
1. Ensure that the power cables from the PSU are labeled correctly.
2. Ensure that you are properly grounded to the node by an ESD protective wrist strap.
3. Turn off the power feeding the power supply to be replaced and then wait for 15 seconds for
the residual stored energy to discharge.
4. Verify that the LEDs on the PSU to be replaced are OFF, and that LEDs on the other PSU
are on.
5. Unfasten the phoenix DC plug connector screws using precision screw driver and then pull
the connector out of the PSU.
6. Unfasten the screw located at bottom end of the face plate using a Phillips screwdriver
(PH1).
7. Disengage the PSU from the backplane connector. Slide it out along the guide way by using
the puller.
8. Insert a new PSU into the slot of the node.
9. Fasten the screw located at bottom end of the face plate using a Phillips screwdriver (PH1).
10. Connect the phoenix DC plug connector and fasten the screws slotted precision screwdriver.
11. Turn on the power supply to the node.
12. Ensure that no alarm is present against the PSU.
13. Ensure that no voltage related alarm is present for other cards.
316
Chapter 12 Module Replacement Procedures
SFP Pluggable Module Replacement

Use this procedure to replace the small form factor pluggable (SFP) module on an optical
interface card.

damaging cards.
inserting SFP into the shelf.
1. Determine your next step.
If the protection mode is linear 1+1 MSP/APS then go to step 2.
If the protection mode is SNCP/UPSR then go to step 3.
2. Determine your next step.
If you want to replace the working SFP then perform a force switch to protection,
go to step 4.
If you want to replace the protect SFP then perform a lockout protection
switching, go to step 4.
3. Perform a manual switching to switch traffic away from the SFP that is to be replaced.
4. Disconnect the fiber-optic cable from the pluggable module.
Caution: Risk of static damage. Wear an anti-static wrist strap and foot straps to
protect the shelf and the equipment from static damage. Connect the wrist strap to an
available earth point.
5. Swing open the latch on the SFP module to the bottom to disengage the SFP module from
the port. Open the bail latch until it is perpendicular to the face of the SFP module from the
optical interface on the base chassis. Open the bail latch until it is perpendicular to the face of
the SFP module.
6. Use the bail latch to carefully pull the SFP module out of its cage on the optical interface.
Make sure you apply the extraction force in a direction parallel to the long dimension of the
SFP module.
7. Put the dust cap on the SFP and place it back into its ESD-protective packaging.
317
You have completed the removing of the pluggable module.

8. Remove the new pluggable module from its packaging.
9. Remove the dust cap from the new SFP/XFP.
CAUTION: Risk of static damage: Wear an antistatic wrist strap and foot straps to
protect the shelf and the equipment from static damage. Connect the wrist strap to an
available earth point.
10. Make sure that the latch on the SFP module is closed (folded back in the SFP module).
NOTE: If the latch is not closed when you insert the SFP module, the module can jam inside
the receptacle in the base chassis faceplate.
11. While holding the SFP module with the side where the electrical connections are exposed to
your left, slide the SFP module into one of the receptacles in the base chassis faceplate.
NOTE: The SFP module must slide easily into its receptacle until it locks into place. If it does
not slide easily, verify the orientation of the module.
12. Connect the fiber-optic cable to the pluggable module. Make sure that there is no alarm
against SFP modules.
13. Clear the lockout of protection/forced switch to protect/manual switch requests.
NOTE: Any unprotected traffic going through SFP being replaced will go down for the time
taken for SFP replacement.
318
Glossary of Terms
A B
AIS BLSR
Alarm Indication Signal(AIS) is a signal Bidirectional Line-Switched Ring (BLSR) is a
transmitted by an intermediate element of a protection switching scheme defined for
multi-node transport circuit that is part of a ring network. No dedicated source is
concatenated telecommunications system to required for protection and supports
alert the receiving end of the circuit that a improved switching time. BLSR switching
segment of the end-to-end link has failed at scheme is referred to as shared protection.
a logical or physical level, even if the system In the event of a link failure, the ring nodes
it is directly connected to is still working. adjacent to the failure reroute the traffic "the
Downstream intermediate elements of the long way" around the ring on the protection
transport circuit propagate the AIS to the fibers using the available protection capacity.
destination element.
C
APS CCM
Automatic Protection Switching (APS) schemes Continuity Check Messages (CCM) is an OAM
involve reserving a protection channel protocol data unit that provides service
(dedicated or shared) with the same capacity monitoring from one Maintenance End
as the channel or facility to be protected. Point (MEP) to another. The CCMs
exchanged between MEPs are analogous to
AU
a "heartbeat" message and can be configured
Administrative Unit (AU) is the information to be sent at in 7 standard intervals: 3.3ms,
structure which provides adaptation between 10ms, 100ms, 1s, 10s, 1 min, and 10 min.
the Higher-Order path layer and the
Multiplex Section layer. The Virtual CPLD
Container (VC) plus the pointers (H1, H2, Complex Programmable Logic Device (CPLD) are
H3 bytes) is called the Administrative Unit integrated circuits (ICs) or chips that
(AU). application designers configure to
implement digital hardware. CPLDs contain
several logic blocks, each of which includes
eight to sixteen macrocells. Each logic block
performs a specific function, hence all the
macrocells within a logic block are fully
connected. Depending upon the application,
however, logic blocks may or may not be
connected to one another.
319
D ERP
DCC Ethernet Ring Protection (ERP) is a mechanism
used for reliable switching and avoiding
Data Communication Channel (DCC) are the loops in a network without using spanning
bytes in SDH frame that enable OAM tree protocols. ERP is applicable to single or
communication between individual network multi-ring topology.
elements as well as inter network element
communication. EVC
DCN Ethernet Virtual Circuit (EVC) connects two
physical User-to-Network Interfaces (UNI)
Data Communication Network (DCN) is the such that the connection appears like a
SDH network that enables OAM virtual private line to the customer. Packets
communication between individual network received on one UNI are transported
elements as well as inter network element directly to the other corresponding UNI.
communication.
F
E
FPGA
ECC
Field Programmable Gate Array (FPGA) is a
Embedded Communication Channel (ECC) is a semiconductor device that can be configured
channel in SDH network that provides an by the customer or designer after
in-band management channel. The SDH manufacturing hence "field-programmable".
management system accesses the network
elements by using one of the FTP
communication channels built into the
section overhead of the STM frame. File Transfer Protocol (FTP) is a standard
network protocol used to transfer files from
EEPROM one host to another host over a TCP based
network, such as the Internet.
Electrically Erasable Programmable Read-Only
Memory (EEPROM) is user modifiable Read G
Only Memory (ROM) that can be erased
GFP
and reprogrammed (written to) repeatedly
through the application of higher than Generic Framing Procedure (GFP) is an
normal electrical voltage. encapsulation scheme for Ethernet over
SONET/SDH defined by ITU-T G.7041.
EMS GFP allows mapping of variable length,
Element Management System (EMS) is an higher-layer client signals over a transport
integrated management of network elements network like SDH/SONET.
across an intelligent optical network. EMS
collects and represents management data
from geographically dispersed network
elements on to a centralized database
(console) in a centralized Network
Operations Center (NOC).
320
Glossary of Terms
I LOS
IBC Loss of Signal (LOS) is an alarm raised on
STM/OCn ports when received signal level
In-Band Communication (IBC) is a channel in drops below an implementation determined
SDH network that allows for in-band threshold. LOS may be due to port admin
management including Operation, down at far end, fiber cuts, faulty fibers,
Administration, Maintenance and dusty fibers and faulty receiver.
Provisioning (OAM&P) functionality. IBC
management system accesses the network M
elements by using one of the
MAC
communication channels built into the
section overhead of the STM frame. Media Access Control (MAC) is a unique
identifier assigned to network interfaces for
communication on the physical network
segment. MAC addresses are used for
L numerous network technologies and most
LAN IEEE 802 network technologies, including
Ethernet. MAC address is 48 bits long. The
Local Area Network (LAN) refers to a group
MAC address is commonly written as a
of computers interconnected into a network
sequence of 12 hexadecimal digits.
so that the multiple users are able to
communicate, exchange information and MAID
share computer resources regardless of the
physical location of the resources. Maintenance Association Identifier (MAID) is a
unique name (identifier) for a Maintenance
LCAS Association. There are 2 parts of every
MAID: the Maintenance Domain (MD)
Link Capacity Adjustment Scheme (LCAS) is a
name and the Short Maintenance
method to dynamically increase or decrease
Association (MA) name. This way, even with
the bandwidth of virtual concatenated
same names in different domains, the MAID
containers. It allows on-demand increase or
is unique.
decrease of the bandwidth of the virtual
concatenated group in a hitless manner. This MD
brings bandwidth-on-demand capability for
data clients like Ethernet when mapped into Maintenance Domain (MD) is an administrative
TDM containers. domain for the purpose of managing and
administering a network. MDs are
LOF configured with names and levels, where the
eight levels range from 0 to 7. A hierarchal
Loss of Frame (LOF) This alarm is raised on
relationship exists between domains based
STM/OCn port, when the network element
on levels. The larger the domain, the higher
detects a severely errored frames generated
the level value.
involving a minimum of four consecutive
errored framing patterns.
321
MEP NTP
Maintenance End Points (MEP) is an actively Network Time Protocol (NTP) is a protocol that
managed CFM entity, associated with a is used to synchronize the time of different
specific port of a service instance, which can network element in a network. It also allows
generate and receive CFM protocol data the transfer and maintenance of time
units and track any responses. CFM assigns functions over distributed network.
MEPs to the edges of each domain. This
helps define the relationships between all O
entities from a maintenance perspective, to OC
allow each entity to monitor the layers under
its responsibility and easily localize Optical Carrier (OC) is a group of signal
problems. bandwidth in a Synchronous Optical
Network (SONET) with many defined
MSP levels. It is typically denoted as OC-n, where
n is the multiplexing factor of the basic rate
Multiplex Section Protection (MSP) is a port of 51.8 Mbps.
level protection supported on the STM
interfaces. MSP schemes involve reserving a OSPF
dedicated protection channel with the same
capacity as the work channel. A point to Open Shortest Path First (OSPF) is a dynamic
point topology where a high priority service routing protocol for use in Internet Protocol
line is protected using another service line (IP) networks. It is used to allow routers to
use MSP type of protection. dynamically learn routes from other routers
and to advertise routes to other routers.
MSPP OSPF selects the best routes by finding the
lowest cost paths to a destination.
Multi-Service Provisioning Platform (MSPP)
provides the functions of multiple network P
elements in a single platform. It supports
PDH
common interfaces such as E1/DS1,
E3/DS3 and data solutions including Plesiochronous Digital Hierarchy (PDH) is a
10/100/1000 Mbps Ethernet solutions with technology used in telecommunications
STM-n/OC-n optical transport bit rates. networks to transport large quantities of
data over digital transport equipment such as
N fibre optic and microwave radio systems. It
NMS is the conventional multiplexing technology
for network transmission systems.
Network Management System (NMS) provides
an integrated management of Element PSU
Management Systems (EMS) across an
intelligent optical network. NMS collects Power Supply Unit (PSU) is a device that
and represents management data from converts mains AC to low-voltage regulated
geographically dispersed EMSs on to a DC power.
centralized database.
322
Glossary of Terms
R T
RPL TU
Ring Protected Link (RPL) owner is a central Tributary Unit (TU) is an information
node in Ethernet ring protection switching structure which provides adaptation between
scheme which blocks one of the ports to the lower order path layer and the higher
ensure that there is no loop formed for the order path layer. It contains the virtual
Ethernet traffic. The link which gets blocked container and a tributary unit pointer.
is referred as RPL.
V
S VC
SDH
Virtual Container (VC) is a technique that
Synchronous Digital Hierarchy (SDH) is an allows SDH circuits to be grouped into
international standard for high speed arbitrarily sized bandwidth increments for
synchronous data transmission over more efficient transport of client protocols.
optical/electrical networks which can
transport digital signals in variable capacities. VCG
It is a synchronous system which intend to Virtual Concatenation Group (VCG) is a logical
provide a more flexible and simple network entity in which the VC channel bandwidth is
infrastructure. divided into smaller individual containers
and are grouped together to form a VCG.
VT
SFP
Virtual Tributary (VT) is a type of
Small Form-factor Pluggable (SFP) is a compact Synchronous Payload Envelope (SPE)
optical transceiver used in optical defined for a Synchronous Optical Network
communications for both (SONET). It is a structure used to carry sub
telecommunication and data rate payloads across a SONET transport
communications applications. It interfaces a network.
network device to a fiber optic cable.
SLAT
System Line-up And Test (SLAT) is the initial
state of the network element considered as
the factory default condition.
STM
Synchronous Transport Module (STM) is the
Synchronous Digital Hierarchy (SDH) ITU-
T fiber optic network transmission standard.
It is the basic building block of SDH.
STS
Synchronous Transport Signal (STS) is the basic
logical building block signal of SONET data
rate.
323
Index
316 118
A
AU 319
AIS 319 Audit Log Archive Size Exceeded - Trap ID
Alarm Indication Signal (AIS) on AU/STS - 136 262
Trap ID 137 263
352 108 138 264
Alarm Indication Signal (AIS) on STM/OCn Audit Log Size Exceeded - Trap ID
Port - Trap ID 134 260
30 107 135 261
Alarm Indication Signal (AIS) on TU/VT - Audit Log Size Exceeded - Trap ID: 259
Trap ID Auto Negotiation Failed - Trap ID
362 109 516 120
Alarm Indication Signal (Terminating) - Trap
B
ID
487 111 Bad checksum on configuration file - Trap ID
Alarm Indication Signal Generated on 7 47
Port_PDH - Trap ID Bandwidth over-provisioned 307
767 113 BER Threshold exceeded for Signal Degrade -
Alarm Indication Signal on Port_PDH - Trap Trap ID
ID 381 122
540 112 BER Threshold Exceeded for Signal Failure
Alarms from the Anonymous Node - Trap ID (B1) - Trap ID
105 257 115 125
Alerts 16, 17 BER Threshold Exceeded for Signal Failure
All Managed Element Unavailable Alarm 306 (B2) - Trap ID
All Radius Servers are Unavailable - Trap ID 115 126
647 231 BER Threshold exceeded on Far End Line for
ALS Triggered - Laser Is Shutdown - Trap ID Signal Degrade - Trap ID
25 114 482 124
Amplifier Not Reachable - Trap ID BER Threshold Exceeded on Far End Line
111 258 for Signal Failure - Trap ID
APS 319 481 128
APS PDU Not Received - Trap ID BER Threshold exceeded on Section for
667 115 Signal Degrade - Trap ID
APS/MSP Channel mismatch failure - Trap 480 123
ID BER Threshold Exceeded on Section for
315 116 Signal Failure - Trap ID
APS/MSP Far End Protect Line Failure - 479 127
Trap ID BLSR 319
317 119 Bus Error - Trap ID
APS/MSP Mode mismatch failure - Trap ID 22 48
314 117
C
APS/MSP Protect Switch Byte failure - Trap
ID Card Inserted 19
325
Card jacked out - Trap ID 579 60

152 49 Database Save Completed 21
Card Lockout From Protection - Trap ID Database Save Failed - Trap ID
653 44 547 61
Card mismatch - Trap ID DCC 320
153 50 DCN 320
Card missing or removed - Trap ID DCN Failure - Trap ID
11 50, 51 473 62
Card not supported in this slot - Trap ID Derive Voltage High - Trap ID
676 52 201 63
Card Protection Alarms 16, 39 Derived Voltage Low - Trap ID
Card Unusable - Trap ID 369 64
618 53 Disk Usage alarm 302
CBG Member Not Deskewable - Trap ID Disk Usage Almost Full - Trap ID
894 236 125 268
CCM 319 Disk Usage Exceeded - Trap ID
CCM Interval Mismatch - Trap ID 124 269
663 237 Disk Usage is High - Trap ID
Chapter Organization 16 133 270
Circuit is unprotected 299 Documentation Version Mismatch / Invalid
Circuit Pack Below Baseline - Trap ID with Software Version - Trap ID
615 54 595 65
Cold Restart Required
FPGA changed - Trap ID
E
614 311 ECC 320
EEPROM 320
FPGA Changed - Trap ID
EEPROM Failure - Trap ID
614 55 17 66
Communication Link Failure - Trap ID EMS 320
598 129 EMS Alarms 16, 255
Config Downloading - Trap ID EMS Backup Fail Alarm - Trap ID
23 57 8002 271
Config out of sync - Trap ID EMS is not reachable 301
20 58 EMS License is going to expire - Trap ID
Configuration File Not Found 19 132 272
Connectivity Check Failed - Trap ID Equipment Alarms 16, 45
658 56, 130 ERP 320
CPLD 319 Ethernet Interface Card Replacement 313
CPU is Fully Loaded - Trap ID EVC 320
128 265 EVC Degrade - Trap ID
CPU Utilization Exceeded - Trap ID 119 273
127 266 EVC Failure 274
CPU Utilization Is High - Trap ID Excessive Error on AU/STS - Trap ID
126 267 390 131
Excessive Error on TU/VT - Trap ID
D 391 132
Database Commit Complete 20 Excessive Error Ratio (Ethernet Port) - Trap
Database Commit Failure 20 ID
Database is corrupted/improper - Trap ID 518 133
861 59 Excessive Error Ratio (VCG Port) - Trap ID
Database Restore Completed 21 495 134
Database Restore Failed - Trap ID External Alarm Occurred - Trap ID
326
Index
224 67 G
F GFP 320
Facility Alarms 16, 105 Group Identifier Mismatch-LCAS - Trap ID
610 144
Factory Defaults Restored - Trap ID
682 68 Group Label Mismatch on CBG Member -
Fan Failed - Trap ID Trap ID
897 240
434 69
Fan Filter Replacement 314 H
Fan Module Replacement 315
Hardware Failure - Trap ID
Far End Client Signal Failure - Trap ID
13 72
409 135
HistAlarms Archive size exceeded - Trap ID
Far End Excessive Error on AU/STS - Trap
142 279
ID
143 280
484 136
144 281
Far End Excessive Error on TU/VT - Trap
HistAlarms size exceeded - Trap ID
ID 139 277
486 137
141 278
Far End Protection Line Failure - Trap ID
Historical Alarm Data out of Sync - Trap ID
444 138
110 276
Far End Signal Degrade on AU/STS - Trap
ID I
483 139
IBC 321
Far End Signal Degrade on TU/VT - Trap ID
Improper Card Jackin - Trap ID
485 140
695 73
Farend Client Signal Degrade - Trap ID
Input Voltage High on PSU Card - Trap ID
121 275
370 74
Farend Client Signal Failure - Trap ID
Input Voltage Low On PSU Card - Trap ID
122 276
371 75
FarEnd IWF failure - Trap ID
Intercard Communication Failure - Trap ID
744 217
378 76
FarEnd TDM Failure Trap ID
Intercard Suspected - Trap ID
745 218
607 77
FDB Limited Reached - Trap ID
Invalid K Byte - Trap ID
686 238
673 222
File System Almost Full - Trap ID
Invalid K Byte East - Trap ID
12 70
626 223
Firmware version mismatch/invalid with
Invalid K Byte West - Trap ID
software version - Trap ID 627 224
594 141
Forced Down Link Integrity - Trap ID J
517 239
Jitter Buffer Overrun - Trap ID
Forced Switch Active 142 743 216
Forced Switch to protect card - Trap ID Jitter Buffer Underrun Trap ID
651 42
749 219
Forced Switch to work card - Trap ID
649 40 L
FPGA 320 L2 Alarms 16, 235
FPGA Load Failure - Trap ID LAN 321
18 71
LAN Port Down - Trap ID
FTP 320
327
384 79 28 157
Laser Bias current lower threshold crossed - Loss of Frame Delineation - Trap ID
Trap ID 410 151, 158
394 146 Loss of Frame on Port_PDH - Trap ID
Laser Bias Voltage Upper Threshold Crossed - 541 159
Trap ID Loss of Frames - Trap ID
395 147 740 213
Laser Failure - Trap ID Loss of Multiframe on AU/STS - Trap ID
24 78 104 160
Laser Supply Voltage High Threshold Crossed Loss of Multiframe on Port_PDH - Trap ID
- Trap ID 536 161
431 82 Loss of Pointer on AU/STS - Trap ID
Laser supply voltage low threshold crossed - 354 162
Trap ID Loss of Pointer on TU/VT - Trap ID
432 83 364 163
Laser Temperature High Threshold Crossed - Loss of Signal on Ethernet port - Trap ID
Trap ID 611 243
429 80 Loss Of Signal on PDH port - Trap ID
Laser temperature low threshold crossed - 202 165
Trap ID Loss of Signal on STM/OC Port - Trap ID
430 81 27 164
Late Frames - Trap ID Loss of VCAT Multiframe - Trap ID
741 214 50 166
LCAS 321
M
LCAS Mode Mismatch - Trap ID
405 148 MAC 321
Line/MS DCC Link Failure - Trap ID MAID 321
597 149 Malformed Frames - Trap ID
Link Down On Ethernet - Trap ID 742 215
305 150, 151 Manual Switch Active 167
Link Down on VCG - Trap ID Manual Switch Active on East - Trap ID
493 151 632 225
Link Integrity ON - Trap ID Manual Switch Active On West - Trap ID
402 152 634 226
List of Tables xii Manual Switch Fail 169
Lockout Active - Trap ID: 153 Manual Switch to protect card - Trap ID
Lockout of protection - Trap ID 652 43
648 39 Manual Switch to work card - Trap ID
LOF 321 650 41
Loop Back Alarm 305 Maximum Alarm Count exceeded - Trap ID
Loop Detected - Trap ID 129 283
664 241 MD 321
Loopback Active-Facility - Trap ID Memory Usage Exceeded - Trap ID
377 154 123 282
Loopback Active-Terminal - Trap ID Memory usage exceeded threshold - Trap ID
361 155 116 84
LOS 321 MEP 322
Loss of Connectivity on CBG Member - Trap Module Replacement Procedures 16, 313
ID Mouse Operation Conventions 15
895 242 MSP 322
Loss of Frame (LOF) - Trap ID MSPP 322
MS-SPRing/BLSR Alarms 16, 221
328
Index
Multiple RPL Owners Configured - Trap ID Path Label Mismatch on AU/STS - Trap ID
660 244 357 171
Path Label Mismatch on TU/VT - Trap ID
N 367 172
NMS 322 PDH 322
NMS Alarms 16, 297 Port Mirroring Active - Trap ID
No Connectivity to Slave - Trap ID 688 87
107 284 Power Supply Unit Replacement 316
No RPL Owner Configured - Trap ID Primary Radius Server Unavailable - Trap ID
659 245 645 232
Node Alarm Out of Sync - Trap ID Program Fault, Software Failure - Trap ID
112 285 15 87
Node Config out of Sync - Trap ID Protection Channel Match Fail - Trap ID
106 286 442 175
Node Not Reachable - Trap ID Protection mode mismatch - Trap ID
100 286, 287, 290 441 176
Node Router ID changed - Trap ID Protection Switch Active 173
145 288 Protection Switch Byte Fail - Trap ID
Node Upload Completed - Trap ID 443 177
102 289 Protection Switch Complete 22
Node Upload Failed - Trap ID Protection Switching is Incomplete - Trap ID
103 290 669 174
Node Upload Started - Trap ID Provisioning Disabled -FileSystem Full - Trap
101 291 ID
NTP 322 542 88
NTP Server Unreachable - Trap ID PSU 322
535 170
Q
O
QoS Mis-configuration 308
OC 322
Onboard voltage generation lower threshold
R
crossed - Trap ID RDI on CBG Member - Trap ID
470 85 896 248
Onboard voltage generation upper threshold Received Power Lower Threshold Crossed -
crossed - Trap ID Trap ID
471 86 400 178
One Way Communication from Node to Received Power upper threshold crossed -
Server - Trap ID Trap ID
114 292 401 179
One Way Communication from Server to Redundant pair communication failure - Trap
Node - Trap ID ID
113 293 21 89
OSPF 322 Remote Alarm Indication(RAI) - Trap ID
Out of Frame (OOF) - Trap ID 538 180
29 145 Remote and Local IP Match - Trap ID
693 249
P
Remote Defect Indication - Trap ID
PacketTrunk OperStatus Down - Trap ID 662 250
694 246 Remote Defect Indication (RDI) on AU/STS
Partial Loss of Capacity on CBG - Trap ID - Trap ID
893 247
Path failed 298
329
353 182 519 193

Remote Defect Indication (RDI) on Signal Degrade on TU/VT - Trap ID
STM/OCn Port - Trap ID 368 192
31 181 Signal Degrade on VCG - Trap ID
Remote Defect Indication (RDI) on TU/VT - 496 194
Trap ID Signal Label Unequipped on AU/STS - Trap
363 183 ID
Remote Defect Indication (Terminating) - 355 196
Trap ID Signal Label Unequipped on TU/VT - Trap
488 184 ID
Restart Procedures 16, 311 365 197
Ring Switch Active - Trap ID SLAT 323
672 227 Slave DB not reachable 304
Ring Switch East - Trap ID Slave not reachable 303
423 228 Software Committing - Trap ID
Ring Switch West - Trap ID 32 95
424 229 Software Download Completed 23
Routing table near capacity - Trap ID Software Download Failed - Trap ID
685 90 311 97
RPL 323 Software Downloading 96
Rx Partial Loss of Capacity - LCAS - Trap ID STM 323
407 185 STS 323
Rx Total Loss of Capacity - LCAS - Trap ID SW version mismatch - Trap ID
411 151, 186 19 100
Switch to Protecting Card - Trap ID
S
387 98
Safety Signs Conventions 14 Switched off/No Input Voltage - Trap ID
SDH 323 388 99
Secondary Radius Servers Unavailable - Trap System clock in internal mode - Trap ID
ID 97 198
646 233 System Reboot 23
Secondary Reference Out of Range - Trap ID
412 188 T
Section/RS DCC Link Failure - Trap ID Telecom Bus Allocation conflict - Trap ID
596 187 746 101
Security Alarms 16, 231 Timing reference failed - Trap ID
SFP 323 241 199
SFP Auto Provision Mismatch - Trap ID Total Loss of Capacity on CBG - Trap ID
360 121, 189 892 251
SFP Failure - Trap ID Total NodeWeight About to Exceed the
490 93 Licensed Value 294
SFP Mismatch - Trap ID Total Number of Nodes About to Exceed the
359 91 Licensed Value - Trap ID
SFP missing or removed - Trap ID 131 295
489 92 Trace Identifier Mismatch on AU/STS - Trap
SFP Pluggable Module Replacement 317 ID
SFP Unknown - Trap ID 356 203
491 94 Trace Identifier Mismatch on STM/OCn Port
Signal Degrade on AU/STS - Trap ID - Trap ID
358 190 52 201
Signal Degrade on Ethernet Port - Trap ID Trace Identifier Mismatch on TU/VT - Trap
ID
330
Index
366 205 Upgrade Deliver Release Failed - Insufficient

Traffic Loss 300 Disk Space for Release 36
Transmitted Power Lower Threshold Crossed Upgrade Deliver Release Passed 33
- Trap ID Upgrade Deliver Release Started 32
392 206 Upgrade Invoke Failed 37
Transmitted Power Upper Threshold Crossed Upgrade Invoke Passed 24, 37
- Trap ID Upgrade Invoke Started 36
393 207 Upgrade load passed - Trap ID
Trunk Oper Down - Trap ID 566 211
389 296 Uploading Config - Trap ID
TU 323 117 102
Tx Partial Loss of Capacity - LCAS - Trap ID User Authentication Failed - Trap ID
497 208 320 212
Tx Total Loss Of Capacity-LCAS - Trap ID User Authentication Succeeded 38
406 151, 209 User Logged Out 38
Typographical Conventions 15 User Payload Mismatch - Trap ID
498 210
U
Using Tejas Product Documentation 16
Undiscovered/Incomplete entities found in Using This Guide 13
QoS Domain 309
Unexpected MAID - Trap ID V
661 252 VC 323
Unexpected MD Level - Trap ID VCG 323
666 254 VT 323
Unexpected MEPID - Trap ID
665 253 W
Upgrade Cancel Passed 24 What This Guide Covers 13
Upgrade Cancel Release Passed 25 What You Should Already Know 13
Upgrade Cancel Release Started 25 Who This Guide Is For 13
Upgrade Cancel Started 24 Work Fan Failed - Trap ID
Upgrade Check Failed 27 608 103
Upgrade Check Failed - Failed Checksum
Validation 27
Upgrade Check Failed - NE Already Running
Release 28
Upgrade Check Failed - Release Does Not
Exist on NE 29
Upgrade Check Failed - Upgrade to Release
Not Supported 29
Upgrade Check Passed 26
Upgrade Check Started 26
Upgrade Commit Passed 30
Upgrade Commit Started 30
Upgrade Delete Release Failed 31
Upgrade Delete Release Passed 31
Upgrade Delete Release Started 32
Upgrade Deliver Release Failed 33
Upgrade Deliver Release Failed - Cannot
Reach Release Server 34
Upgrade Deliver Release Failed - FTP
Protocol Error 35
331

Basic Alarm Clearing Procedures

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Basic Alarm Clearing Procedures

Uploaded by

Copyright:

Available Formats

Alarm Clearing Procedures

Document ID: 999-DOC000005-E Release: Standard Release Version: 1.1

Warning and Disclaimer

Technical Support Information

- Phone(s): +91 80 41719090/91/92/93/94/95

Version Date Modifications Made

1.0 30 August 2013 Standard Release

1.1 3 May 2016 Addition of MPLS and CEM related alarms

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of

Good Fair Average Poor Bad N/A

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)

Good Fair Average Poor Bad N/A

Improve the Make it more Improve the

Add more step-by-step Improve the organization Add more

Add more/better quick Add more detail Improve the index

Card Protection Alarms 39

Facility Alarms 105

MS-SPRing/BLSR Alarms 221

Security Alarms 231

EMS Alarms 255

NMS Alarms 297

Restart Procedures 311

Module Replacement Procedures 313

Glossary of Terms 319

Using This Guide

Who This Guide Is For

What This Guide Covers

What You Should Already Know

Safety Signs Conventions

Table 1: Safety Sign Convention

Symbols Meaning Represents

Danger Situation that could cause bodily injury. Failure to observe

Hot Surface Situation that could result in bodily burns.

Static Discharge Handle the equipment wearing a grounding wrist strap to

Table 2: Typographical Conventions

Formatting Convention Type of Information

Procedures Step-by-step procedures. You can follow these instructions to

CAPITALS Names of keys on the keyboard, for example, SHIFT, CTRL, or

Mouse Operation Conventions

Using Tejas Product Documentation

Configuration File Not Found

Database Commit Complete

Database Commit Failure

Database Restore Completed

Database Save Completed

Protection Switch Complete

Software Download Completed

Upgrade Cancel Started

Upgrade Cancel Passed

Upgrade Cancel Release Started

Upgrade Cancel Release Passed

Upgrade Check Started

Upgrade Check Passed

Upgrade Check Failed

Upgrade Check Failed - Failed Checksum Validation

2. Cancel the current upgrade and perform upgrade operation.

Upgrade Check Failed - NE Already Running Release

Upgrade Check Failed - Release Does Not Exist on NE

Upgrade Check Failed - Upgrade to Release Not

Upgrade Commit Started

Upgrade Commit Passed

Upgrade Delete Release Failed

Upgrade Delete Release Passed