R17.0 DTN and DTN-X Alarm and Trouble Clearing Guide

Infinera DTN and DTN-X
Alarm and Trouble Clearing Guide
Release 17.0
Version 001
Document ID 1900-001796
Infinera Corporation
140 Caspian Court
Sunnyvale, California 94089
www.infinera.com
- Please refer to the Infinera Customer Web Portal for the most recent version of this document. -
Copyright
Copyright © 2017 Infinera Corporation. All right reserved.
This Manual is the property of Infinera Corporation and is confidential. No part of this Manual may be reproduced for any purposes
or transmitted in any form to any third party without the express written consent of Infinera.
Infinera makes no warranties or representations, expressed or implied, of any kind relative to the information or any portion thereof
contained in this Manual or its adaptation or use, and assumes no responsibility or liability of any kind, including, but not limited to,
indirect, special, consequential or incidental damages, (1) for any errors or inaccuracies contained in the information or (2) arising
from the adaptation or use of the information or any portion thereof including any application of software referenced or utilized in the
Manual. The information in this Manual is subject to change without notice.
Trademarks
Infinera, Infinera Intelligent Transport Networks, IQ NOS, FlexILS, DTN-X, DTN, ATN, FastSMP, FlexCoherent, What the Network
Will Be, iWDM, Enlighten and logos that contain Infinera are trademarks or registered trademarks of Infinera Corporation in the
United States and other countries.
All other trademarks in this Manual are the property of their respective owners.
Infinera DTN-X, DTN, FlexILS, Cloud Xpress, XT, and ATN Regulatory Compliance
FCC Class A
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not
cause harmful interference, and (2) this device must accept any interference received, including interference that may cause
undesired operation. Modifying the equipment without Infinera's written authorization may result in the equipment no longer
complying with FCC requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC
regulations, and you may be required to correct any interference to radio or television communications at your own expense.
DOC Class A
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus as set out in the
interference-causing equipment standard titled “Digital Apparatus," ICES-003 of the Department of Communications.
Cet appareil numérique respecte les limites de bruits radioélectriques applicables aux appareils numériques de Classe A prescrites
dans la norme sur le matériel brouilleur: "Appareils Numériques," NMB-003 édictée par le Ministère des Communications.
Class A
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a domestic environment, radio
interference may occur, in which case, the user may be required to take corrective actions.
Warning
This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be
required to take adequate measures.
FDA
This product complies with the DHHS Rules 21CFR 1040.10 and 1040.11, except for deviations pursuant to Laser Notice No. 50,
dated June 24, 2007.
Contents
About this Document......................................................................................................................................i
Objective....................................................................................................................................................................i
Audience....................................................................................................................................................................i
Document Organization.............................................................................................................................................i
Documents for Release 17.0.................................................................................................................................... ii
Conventions..............................................................................................................................................................v
Technical Assistance............................................................................................................................................... vi
Documentation Feedback....................................................................................................................................... vii
Chapter 1: Alarms......................................................................................................................................1-1
Alarm Overview.....................................................................................................................................................1-2
Alarm Description and Clearing Procedures......................................................................................................... 1-5
Chapter 2: Alarm Masking Hierarchy.........................................................................................................2-1
Chapter 3: Events......................................................................................................................................3-1
Event Overview..................................................................................................................................................... 3-2
Event Description.................................................................................................................................................. 3-6
Appendix A: Alarm Index...........................................................................................................A-1
iv Contents
Alarm and Trouble Clearing Guide Release 17.0 V001 Infinera Corporation
Infinera Proprietary and Confidential

List of Tables
Table 1-1 Alarm Categories.............................................................................................................................1-2
Table 1-2 Alarm Detailed Conditions.............................................................................................................1 -45
Table 1-3 List of detail conditions for AGC-NF using BMM headend node.................................................. 1-302
Table 1-4 List of detail conditions for AGC-NF using FRM headend node...................................................1-306
Table 2-1 Alarm Masking Hierarchy................................................................................................................ 2-1
Table 3-1 Event Categories............................................................................................................................. 3-2
Table 3-2 Alphabetical Admin Events Index.................................................................................................... 3-2
Table 3-3 Alphabetical Security Events Index................................................................................................. 3-3
Table 3-4 Alphabetical Audit Events Index...................................................................................................... 3-4
Infinera Corporation Alarm and Trouble Clearing Guide Release 17.0 V001

vi List of Tables

About this Document
This document provides an overview of the Fault Management inventories and Alarm Manager. It also
provides the procedures to perform diagnostic tests on network elements.
Objective
This guide describes the Infinera Graphical Node manager (GNM) client user interface. It also provides
procedures to use the GNM to perform Fault Management and Diagnostics functions on the
network elements.
Audience
The primary audience for this guide includes network operation personnel and administrators responsible
for maintaining network elements and provisioning services using InfineraGNM. This guide assumes that
the reader is familiar with the following topics and products:
■ Microsoft Windows 2000
■ Microsoft Windows XP and Microsoft Windows Vista
■ Web browsers such as Internet Explorer and Mozilla
■ Internet and networking terminology and concepts
■ Optical networking
Document Organization
The following table describes each chapter in this guide:

ii Documents for Release 17.0
Chapter Number: Title Descriptio

Alarms Describes the alarms raised by the network element and
the corrective procedures to perform to clear the alarms.
Alarm Masking Hierarchy Describes the alarm masking hierarchy, in which a
network element masks (suppresses) reporting of higher
layer failures associated with the same root cause as a
higher priority, lower layer, failure.
Events Describes the events raised by the network element and
the conditions under which each of the events are
raised.
Documents for Release 17.0

The following documents are available for the Intelligent Transport Network™ systems:
Document Name Document ID Description

DTN and DTN-X Site Preparation and Hardware Installation Guide Portfolio
XTC Site Preparation and 1900-001773 Describes the procedures for initial installation of the XTC at any
Hardware Installation Guide given site. Includes procedures for site preparation and site
testing, system cabling, safety procedures and hand-over to
provisioning activities.
XT Site Preparation and 1900-001774 Describes the procedures for initial installation of the XT chassis
Hardware Installation Guide at any given site. Includes procedures for site preparation and
site testing, system cabling, safety procedures and hand-over to
Line Systems Site Preparation 1900-001775 Describes the procedures for initial installation of the Line
and Hardware Installation Systems at any given site. Includes procedures for site
Guide preparation and site testing, system cabling, safety procedures
and hand-over to provisioning activities.
DTC/MTC Site Preparation 1900-001776 Describes the procedures for initial installation of the DTC/MTC
and Hardware Installation at any given site. Includes procedures for site preparation and
Guide site testing, system cabling, safety procedures and hand-over to
Passive Equipment Site 1900-001777 Describes the procedures for initial installation of the Passive
Preparation and Hardware Equipment at any given site. Includes procedures for site
Installation Guide preparation and site testing, system cabling, safety procedures
and hand-over to provisioning activities.
DTN and DTN-X Hardware Description Guide Portfolio

About this Document iii

XT Hardware Description 1900-001778 Provides the hardware description of the XT chassis which
Guide includes the description of chassis, common modules and circuit
packs. It provides hardware block diagrams, functional
descriptions, mechanical and electrical specifications for each
module.
XTC Hardware Description 1900-001779 Provides the hardware description of the XTC which includes the
Guide description of chassis, common modules and circuit packs. It
provides hardware block diagrams, functional descriptions,
mechanical and electrical specifications for each module.
Line Systems Hardware 1900-001780 Provides the hardware description of the Line Systems which
Description Guide includes the description of chassis, common modules and circuit
module.
DTC/MTC Hardware 1900-001781 Provides the hardware description of the DTC/MTC which
Description Guide includes the description of chassis, common modules and circuit
module.
Passive Equipment Hardware 1900-001782 Provides the hardware description of the Passive Equipment
Description Guide which includes the description of chassis, common modules and
circuit packs. It provides hardware block diagrams, functional
module.
DTN and DTN-X Task Oriented Procedures Guide Portfolio
XTC Task Oriented 1900-001783 Provides the routine task oriented procedures used in support of
Procedures Guide the XTC.
XT Task Oriented Procedures 1900-001784 Provides the routine task oriented procedures used in support of
Guide the XT chassis.
Line Systems Task Oriented 1900-001785 Provides the routine task oriented procedures used in support of
Procedures Guide the Line Systems.
DTC/MTC Task Oriented 1900-001786 Provides the routine task oriented procedures used in support of
Procedures Guide the DTC/MTC.
DTN and DTN-X Turn-up and Test Guide Portfolio
DTN-X Turn-up and Test 1900-001787 Describes procedures for turning up, commissioning and testing
Guide the installed DTN-X network element. Includes the description of
circuit activation and end-end system testing procedures.
DTN Turn-up and Test Guide 1900-001788 Describes procedures for turning up, commissioning and testing
the installed DTN network element. Includes the description of

iv Documents for Release 17.0

FlexILS ROADM Turn-up and 1900-001789 Describes procedures for turning up, commissioning and testing
Test Guide the installed FlexILS and FlexROADM network elements.
Includes the description of circuit activation and end-end system
testing procedures.
Optical Amplifier Turn-up and 1900-001790 Describes procedures for turning up, commissioning and testing
Test Guide the installed OTC-based Optical Amplifier network elements.
Includes the description of circuit activation and end-end system
testing procedures.
XT Turn-up and Test Guide 1900-001791 Describes procedures for turning up, commissioning and testing
the installed XT network element. Includes the description of
Optical Line Amplifier Turn-up 1900-001792 Describes procedures for turning up, commissioning and testing
and Test Guide the installed MTC-9/MTC-6 based Optical Line Amplifier network
elements. Includes the description of circuit activation and end-
end system testing procedures.
DTN and DTN-X Reference Guides Portfolio
SNMP Agent Reference Guide 1900-001793 Describes the Simple Network Management Protocol (SNMP)
Agent for network elements. It provides detailed instructions to
configure and operate the SNMP Agent from the network
element.
DTN and DTN-X System 1900-001794 Provides an overview of the Intelligent Transport Network and its
Description Guide principal elements, including the network elements. Includes a
description of the IQ Network Operating System and an overview
of the management interfaces for products.
NETCONF Agent Reference 1900-001795 Describes the Network Configuration (NETCONF) Agent.
Guide
DTN and DTN-X Alarm and 1900-001796 Describes the alarms raised by the network elements and the
Trouble Clearing Guide corrective procedures to perform to clear the alarms. It also
describes about Event Log.
DTN and DTN-X User Guides Portfolio
GNM Overview Guide 1900-001797 Describes the Graphical Node Manager user interface. It also
describes the new features, the hardware and software
requirements required to launch the GNM. It also provides
procedures to install and upgrade the software and database on
the network elements.
GNM Fault Management and 1900-001798 Describes the Fault Management inventories and Alarm
Diagnostics Guide Manager. It also provides the procedures to perform diagnostic
tests on network elements.
GNM Configuration 1900-001799 Describes the procedures to use the GNM to configure the
Management Guide network elements and the network topology. It also provides a
description on the Equipment Manager and Facility Manager.

About this Document v

GNM Performance 1900-001800 Describes the procedures to use GNM to view performance
Management Guide monitoring (PM) data and modify PM thresholds for network
elements. It also provides the PM parameters details reported by
the network elements.
GNM Security Management 1900-001801 Describes the procedures to perform security and access
Guide management tasks such as creating, deleting and managing user
accounts on the network elements.
GNM Service Provisioning 1900-001802 Describes the procedures to provision cross-connects,
Guide subnetwork connections (SNCs) and protected services on
network elements. It includes a description of the various
inventory managers displayed in the GNM.
CLI User Guide 1900-001803 Describes Command Line Interface (CLI) for the MTC-6/MTC-9
based FlexROADM and Optical Line Amplifier network elements.
It includes the description of the supported CLI commands and
the procedures for the commonly performed OAM&P functions.
DTN and DTN-X TL1 User 1900-001804 Describes the TL1 interface supported by the DTN-X, ILS, DTN,
Guide XT and Optical Line Amplifier network elements. It includes the
description of the supported TL1 commands and the procedures
for the commonly performed OAM&P functions.
Acronyms
Acronyms 1900-001806 Lists the acronyms used in documentation.
Conventions
The table below lists the conventions used in this guide.
Convention Item Example

bold default font Menu command paths Select Fault Management-> Alarm
Manager
Button names Click Apply
User interface labels Click Summary panel
Window/dialog box titles In the Dial-Up Networking window
courier font User-entered text In the Label enter EastBMM

Command output Database restore from local or remote
machine?

vi Technical Assistance
Convention Item Example

Directory path /DNA/EMS
Note: If the directory path or

command is spanning across two
lines, copy the directory path or
command to notepad and execute
in editor.
default font, italic Document titles Refer to the CLI User Guide
Default font Icon names Click Node icon
Window names not in the user interface In the DNA Main View
Helpful suggestions
Note: Note: The window is refreshed only
after making all the changes.
Technical Assistance
Customer Support for Infinera products is available, 24 hours a day, 7 days a week (24x7). For
information or assistance with Infinera products, please contact the Infinera Technical Assistance Center
(TAC) using any of the methods listed below:
■ Email: [email protected]
■ Telephone:
□ Direct within United States: 1-408-572-5288
□ Outside North America: +1-408-572-5288
□ Toll-free within United States: +1-877-INF-5288 (+1-877-463-5288)
□ Toll-free within Germany/France/Benelux/United Kingdom: 00-800-4634-6372
□ Toll-free within Japan: 010-800-4634-6372
■ Infinera corporate website: http://www.infinera.com
■ Infinera Customer Web Portal: https://support.infinera.com

About this Document vii
Please see the Infinera Customer Web Portal to view technical support policies and procedures, to
download software updates and product documentation, or to create/update incident reports and
RMA requests.
Documentation Feedback
Infinera strives to constantly improve the quality of its products and documentation. Please submit
comments or suggestions regarding Infinera Technical Product Documentation using any of the following
methods:
■ Submit a service request using the Infinera Customer Web Portal
■ Send email to: [email protected]
■ Send mail to the following address:
Attention: Infinera Technical Documentation and Technical Training
Infinera Corporation
140 Caspian Court
Sunnyvale, CA 94089
When submitting comments, please include the following information:
■ Document name and document ID written on the document cover page
■ Document release number and version written on the document cover page
■ Page number(s) in the document on which there are comments

viii Documentation Feedback

CHAPTER 1
Alarms
The DTN, DTN-X, FlexROADM and Optical Line Amplifier network elements report alarm conditions
through local alarm indicators. This chapter describes the alarms reported by the network elements and
the corrective procedures to be performed to clear the alarms in the following sections:
Alarm Overview on page 1-2
Alarm Description and Clearing Procedures on page 1-5

1-2 Alarm Overview
Alarm Overview
The following section describes the alarm attributes and provides pointers to alarms in the following
sections:
Alarm Attributes on page 1-2
Alarm Configuration on page 1-3
Alarm Severity on page 1-2
Alarm Attributes
Alarms are reported with sufficient information so that users can take corrective actions. The following
sections describe some of the important attributes which are reported with each alarm.
Alarm Categories
Each alarm is assigned an alarm category as described in Alarm Categories.
Table 1-1 Alarm Categories

Alarm Category Description
“Communication Alarms“ Communication alarms are associated with faults which impact the communication
between modules within the network element and between network elements. For
example: No Communication with OSC Neighbor, OLOS on OSC channel.
“Environmental Alarms“ Environmental alarms are caused by the change in the state of the environmental
alarm input contact.
“Equipment Alarms“ Equipment alarms are associated with hardware faults. For example: Equipment
Failure, Equipment Unreachable
“Facility Alarms“ Facility alarms are associated with line and tributary facilities, and incoming signal.
For example: OLOS, LOS, AIS, BDI
“Software Processing Alarms“ Software processing alarms are associated with software processing errors. For
example, Software Upgrade has Failed, Persistence space less than 2%-critical
Alarm Severity
The alarm severity indicates the level of degradation that the alarm causes to the services provided. The
following are the severities displayed:
■ Critical (CR) alarms generally indicate severe, service-affecting trouble that needs immediate
correction
■ Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network
■ Minor (MN) alarms are used for troubles that do not have a serious effect on service to customers
or for troubles in circuits that are not essential to the network element operation

Alarms 1-3
■ Warning (WN) alarms are used to provide information regarding special precautions
■ Unreachable (UR) events are raised by the DNA when the DNA server is not able to establish a
session with the network element
Service Code
Telcordia standard service codes: Service-Affecting (SA) and Non-Service Affecting (NSA) are supported.
■ SA fault is one which actually or potentially interrupts the customer traffic through the system or the
network. A fault is defined to be SA if the fault affects a hardware or software entity in the data
plane and the affected hardware or software entity is administratively enabled
■ NSA fault is one which does not or cannot interrupt the customer traffic through the system or the
network
Probable Cause
This is a descriptive string that gives the probable cause of the problem corresponding to the generated
alarm. The probable cause is displayed as an alarm condition by the management interface.
Alarm Configuration
Users can customize the alarm reporting as described in the following sections. Refer to the DNA, GNM
user guides and/or DTN and DTN-X TL1 User Guide for details on using the management interfaces
( GNM).
Alarm Severity Profile Setting

The Alarm Severity Profile Setting (ASPS) feature allows users to modify the default severity of an alarm
type per managed object entity basis. The severity cannot be modified per managed object instance
basis. For example, when the severity of Loss of Signal (OLOS) of an Optical Carrier Group (OCG)
termination point is modified, the new severity is applied to the subsequent generation of alarm and to the
OLOS alarm reported by all instances of the OCG termination point. Users can modify the default severity
according to their fault-handling strategies. The ASPS is provisioned through the management interfaces
(GNM).
Alarm Reporting Control

The Alarm Reporting Control (ARC) feature allows users to silence a managed object instance that is
administratively unlocked, but which is being serviced or is awaiting valid signal flow. A typical example is
a tributary port in administrative in-service state or administrative unlocked state that is awaiting
interconnection to client equipment. In such cases, users would like the alarms inhibited on this resource,
as it is not yet providing service to the clients. Although the managed object instance may be detecting
alarms such as OLOS, they are not transmitted to any client, or reported to the management interfaces
(GNM).
The inhibited alarms do not change the status indicators, such as LEDs, audio, and visual indicators.
Inhibited alarms are logged in the Event Log and are viewable via the TL1 interface. The ARC is
provisioned through the management interfaces (GNM). Users can enable the ARC per managed object

1-4 Alarm Overview
instance basis. When ARC is applied to a managed object instance it is propagated to all the dependent
managed objects also. For example, when alarm reporting is inhibited for the chassis object instance,
alarm reporting is inhibited for all the circuit pack object instances within that chassis. The alarms are
inhibited for the duration the user has enabled the ARC. On disabling ARC, the standing alarm conditions,
which were inhibited due to ARC, are reported to the management interfaces (GNM).

Alarms 1-5
Alarm Description and Clearing Procedures

Alarms are listed according to the category. The description and common procedures that are frequently
used when troubleshooting, accompany each alarm. Alarms are described in the following sections:
“Facility Alarms“
“Communication Alarms“
“Software Processing Alarms“
“Equipment Alarms“
“Environmental Alarms“
“Threshold Crossing Alerts“
Note: Unless specifically noted otherwise, all references to the “line module” will refer to either the
DLM, XLM, OLM, ADLM, AXLM, and/or SLM interchangeably. All references to the “LM- 80” will refer
to the ADLM-80, AXLM-80, and/or SLM-80 interchangeably.
Note: All references to the "IMM" will refer to both IMM and IMM-B.
Facility Alarms
Facility alarms are associated with the line and tributary facilities, and any incoming signal. For example:
OLOS, LOS, AIS, and BDI. By default, the appropriate chassis level LED is illuminated when facility
alarms are raised.

1-6 Alarm Description and Clearing Procedures
FAC0004
AIS-DTP
Alarm Indication Signal - DTP
■ Alarm Type - Facility

■ Severity - Not Reported
■ SA/NSA - SA (Service-Affecting)
■ Applicable Facilities - DTPCTP
■ Detailed Conditions - Alarm Indication Signal
■ Direction - Receive
Description and Causes

This alarm is generated by the Trib DTF Path termination point.
This alarm is generated when the line module (DLM/XLM/ADLM/AXLM/SLM) in the upstream network
element detect a Loss of Frame (LOF) for the corresponding Optical Channel (OCh) on its receive path.
The upstream network element sends an AIS-DTP maintenance signal to this network element which is in
the downstream direction. Failure is declared when this defect persists for 2.5 +/- 0.5 seconds.
This alarm is most likely caused by:
■ A problem in the upstream network element or the network
Clearing Procedure
■ Identify if the problem is in some digital network element upstream of this network element

Alarms 1-7
FAC0006
BDI
Backward Defect Indication - Payload

■ SA/NSA - SA (Service Affecting)
■ Applicable Facilities - DLM Optical Channel, Digital Channel,OLDPSCH
■ Detailed Conditions - Backward Defect Indication
Description and Causes (BDI on Channel CTP)

This alarm is generated by the channel termination point (OCHCTP) on the line module.
This alarm is generated when the downstream DTN detects a channel fault condition on the channel and
transmits BDI maintenance signal to this upstream DTN.
This alarm is most likely caused when:
■ The BDI maintenance signal on the digital channel persists for more than 2.5 seconds
Description and Causes (BDI on DCHCTP)

This alarm is generated by the digital termination point (DCHCTP) on the TAM-2-10GT.
This alarm is generated when the downstream TAM-2-10GT detects a AIS condition on the digital
channel and transmits BDI maintenance signal to this upstream TAM-2-10GT.
■ The BDI channel maintenance signal persists for more than 2.5 seconds
Description and Causes (BDI on OLDPSCH)
This alarm is generated by the OLDP termination point (OLDP SCH) on the line module.
This alarm is generated when the downstream DTN-X detects a channel fault condition on the channel
and transmits BDI maintenance signal to this upstream DTN-X.
■ The BDI maintenance signal on the digital channel persists for more than 2.5 seconds
Clearing Procedure
■ Check for faults between this node and the downstream node, and clear them. Faults can be
Optical Loss Of Signal (OLOS) or LOF

FAC0019
LPBKFACILITY
Facility Loopback Enabled

■ Severity - Warning (user customizable)
■ SA/NSA - NSA (Non-Service Affecting)
■ Applicable Facilities - Digital Channel, GFPTP, GbE Client, ODUk Client/CTP, Clear Channel,
OTUCLIENTCTP, SDH, ODUki CTP, GFP Client, SONET, Fiber Channel Client, DTF Path

This alarm is generated by the network element.
This alarm is generated when a facility loopback is enabled on the Line DTF path and/or Client Trib
termination point for the SONET, SDH, GbE, 10G DTF, 1GFC/2GFC/8GFC/10GFC, OTU, ODUki and
ODUi clients.
Clearing Procedure
■ Release the facility loopback at the corresponding termination point

Alarms 1-9
FAC0020
LPBKTERM
Terminal Loopback Enabled

■ Applicable Facilities - Fiber Channel Client, GFPTP, SONET, Clear Channel, ODUk Client/CTP,
GbE Client, SDH, OTUCLIENTCTP, Digital Channel, DTF Path, GFP Client, XTOCGPTP,
XTSCGPTP

This alarm is generated when a terminal loopback is enabled on the Line/Trib DTF path and/or Client Trib
termination points for the SONET, SDH, GbE, 10G DTF, 1GFC/2GFC/8GFC/10GFC, OTU and ODUk
clients.
Clearing Procedure
■ Release the terminal loopback at the corresponding termination point

FAC0021
LOF
Loss Of Frame

■ Severity - Critical
■ Applicable Facilities - LMOCHPTP, Digital Channel, DLM Optical Channel
■ Detailed Conditions - Loss of Frame

This alarm is generated by the channel termination point on the line module and/or LM-80 and termination
point on the TAM-2-10GT and TIM-5-10GM/GX.
This alarm is generated when the line module and/or LM-80 is unable to lock on to the frame of the
incoming channel.
This alarm is generated when the TAM-2-10GT is unable to lock on to the frame of the incoming tributary
side DTP signal coming from the interconnected far end TAM-2-10GT and TIM-5-10GM/GX.
■ Noisy received signal
■ Very low optical power received (OPR)
■ Hardware faults in the channel data path of the line module and/or LM-80s in this network element
Clearing Procedure
Note: If any one of the below steps clears the alarm then the clearing procedure is complete.
1. Verify that the OPR is within the valid range.

2. Check for equipment failure alarms reported by the line module and/or LM-80s in the upstream digital
network element.
3. Check for equipment failure alarms reported by the line module and/or LM-80s in this network
element.
4. Cold reset the TAM.

Alarms 1-11
FAC0022
LOS
Loss Of Signal

■ Applicable Facilities - XT-500S OChCTP, XT-500F CarrierCTP

This alarm is generated by the XTOChCTP or XTCarrierCTP.
This alarm is generated by Loss of Rx Acquisition.
Clearing Procedure
■ This alarm is cleared when Rx Acquisition is successful.

FAC0024
OLOS
Optical Loss of Signal - Payload

■ Applicable Facilities - GAM OCG Port, BMM OCG Port, Band Port, XTOCGPTP, XTSCGPTP,
TribPTP

This alarm is generated by the OCG on the BMM and/or GAM.
This alarm is generated when the Optical Power received (OPR) (received from the line module) on this
OCG is equal to or below the pre-defined threshold.
■ For a BMM OCG OLOS
□ Failure in connection (dirty, bent or cut fiber) between the line module and the BMM
□ Cold reset or administratively locked line module or GAM
□ Hardware failure in the line module or the GAM in this network element
□ Failure of the optical receiver in the BMM
□ Incomplete BMM and line module Auto-discovery
□ Provisioned OCG configured, but the fibers not connected between expressed BMM
OCGPTPs
□ Provisioned OCG configured on the expressed BMM OCGPTPs on the local node, but
Auto-discovery between the line module and the BMM not complete
■ For a GAM OCG OLOS
□ Failure in connection (dirty, bent or cut fiber) between the line module and the GAM
□ Cold reset, or administratively locked line module
□ Hardware failure of line module in this network element
□ Incomplete Auto-discovery between a line module and GAM
□ Provisioned OCG configured, but the fibers not connected between the line module and the
GAM OCGPTP
Clearing Procedure for a BMM OCGPTP OLOS

Alarms 1-13
1. Check the connectivity between the line module and the BMM and expressed BMM OCGPTPs.
2. Check for the equipment failure alarms reported by the line module.
3. Check for the equipment failure alarms reported by the BMM.
4. Check the Auto-discovery state on the node between the BMM and line module.
Clearing Procedure for a GAM OCGPTP OLOS
1. Check the connectivity between the line module and the GAM OCG.
3. Check the Auto-discovery state on the node between the line module and the GAM.

FAC0028
LOMF
Loss of Multi-frame

■ Applicable Facilities - OTU Client CTP
■ Direction- Receive

This alarm is generated by the OTU Client CTP on TIM-5-10GM/GX.
This alarm is generated when the OTUk layer's Multi-frame Alignment Signal overhead is in a persistent
out-of-multiframe state for at least 3 ms as a part of a multi-frame alignment procedure. This alarm is
most likely caused by:
■ Hardware defect on the equipment (local/remote)
■ A problem in the network
Clearing Procedure
1. Ensure proper connectivity.

2. Check for symptoms of a hardware defect such as equipment fault conditions and historical
performance statistics for the OTUk layer.

Alarms 1-15
FAC0030
PRBS-GEN
PRBS Generation Activated

■ Severity - Warning
■ Applicable Facilities - DLM Optical Channel, DTF Path

This alarm is raised when a PRBS pattern is enabled. This alarm can be generated by any of the
following objects: channel termination point, OTUk client CTP, Trib DTF Path, SONET Client Trib
termination point, or the SDH Client Trib termination point.
Clearing Procedure
■ Disable the PRBS generation on the termination point or port that raised the alarm

FAC0032
PRBS-OOS
PRBS Out of Sync

■ Severity - Major (user customizable)
■ Applicable Facilities - DTF Path, DLM Optical Channel
■ Detailed Conditions- PRBS-OUT-OF-SYNC

This alarm is generated when the line module detects that the received PRBS pattern is out of synch on
the Optical Channel, DCH Client termination point, OTUk client CTP, Trib DTF Path termination point,
SONET Client Trib termination point, or the SDH Client Trib Termination point.
Clearing Procedure
1. Check and ensure that the PRBS was setup correctly.

2. Check and ensure that any SNC on the affected termination point was setup correctly.

Alarms 1-17
FAC0059
PWR-ADJUST-INCOMPLETE
Power Adjustment Incomplete

■ Severity - Major
■ Applicable Facilities - LMOCHPTP, DLM OCG Port, BMM OCG Port, OLM OCG Port, CMM OCG
Port, OFXSCGPTP, XTOCGPTP, XTSCGPTP
■ Detailed Conditions - PWR-ADJUST-TIMEOUT

This alarm is generated by the OCGPTP on the line module and BMM, or between the CMM and the
BMM.
On a line module and BMM OCGPTP, this alarm is generated when the Photonic Integrated Circuit (PIC)
on a line module is unable to complete the power adjustment between the LM OCGPTP and the
BMMOCGPTP.
On a CMM and BMM OCGPTP, this alarm is generated when the CMM is unable to complete the power
adjustment between the CMM OCGPTP and the BMM OCGPTP.
■ Dirty connectors
■ A pinched BMM patch cable
■ Failure of optical components on the line module
■ Failure of optical components on the CMM
Clearing Procedure
1. Check the state of the line module OCGPTP and each of its channels, at this network element and the
far-end digital network element (this failure may be service-affecting, but not necessarily).
Note: If the OCG or any of its channels is healthy and passing traffic, extra care must be taken in
executing the following steps, since these steps might inadvertently affect that traffic.
2. Inspect line module OCG OPT PM and BMM OCG OPR PM to determine the loss between the line
module and BMM, or between the CMM and the BMM.
3. Check for a pinched fiber.
4. Check for dirty connectors and clean the connectors.

5. Replace the fiber between the BMM and the line module, or between the CMM and the BMM.
7. Check for equipment failure alarms reported by the CMM.

Alarms 1-19
FAC0060
OLOS
Optical Loss Of Signal - OSC
■ Alarm Type - Communication

■ Severity - Critical (user customizable)
■ Applicable Facilities - OSCCTP

This alarm is generated by the OSCCTP on TIM-5-10GM/GX, TIM-1-100GE, TIM-1-40GE, TIM-1-100G,
TIM-1-40G.
This alarm is generated if the OAM is configured as booster or OAM/ORM is configured as per-amp has
OSC pin loss.
This alarm is generated when the OSC optical patch cord between the two OAMs/ORMs or between an
OAM and ORM fails.
■ Loosely connected optical patch cord
■ Bent or damaged optical patch cord
Clearing Procedure
1. If the optical patch cord is loosely connected, re-connect the optical patch cord.
2. Replace the optical patch cord.

FAC0063
BDI-DTP
Backward Defect Indication-DTP

■ Applicable Facilities - DTFCTP

This alarm is generated by the Trib DTF Path termination point on the TAM, DICM.
This alarm is caused when:
■ The BDI-DTP maintenance signal persists for more than 2.5 seconds
Clearing Procedure
■ Check for faults between this node and a downstream DTN and clear them. Faults can be OLOS,
LOF, or AIS-DTP

Alarms 1-21
FAC0064
LOF
Loss Of Frame

■ Severity - Critical/Warning
■ SA/NSA - NSA (Non Service-Affecting)
■ Applicable Facilities - DTFCTP
■ Detailed Conditions - LOF

This alarm is generated by the DTF Path termination point on the line module and TAM, DICM.
This alarm is generated when the line module and the TAM are unable to lock on to the frame of the
incoming channel.
■ Hardware faults in the DTF path of the line module/TAM/DICM in upstream network element
■ Hardware faults in the DTF path of the line module/TAM/DICM in this network element
Clearing Procedure
1. Check for the equipment failure alarms reported by the line module/TAM/DICM in the upstream
network element.
2. Check for the equipment failure alarms reported by the line module/TAM/DICM in this network
element. If any, replace the line module/TAM/DICM.
3. Cold reset the TAM.

FAC0065
LOF
Loss Of Frame

■ Applicable Facilities - OTUki Section CTP, OTUCni Section CTP, OTUCLIENTCTP, SDH, SONET
■ Detailed Conditions - LOF

This alarm is generated by the SONET and SDH client port, and OTU client termination points on
TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G.
This alarm is generated when the SONET and SDH ports or the OTU termination points are unable to
lock on to the incoming signal frame from the client equipment.
This alarm is generated when the downstream interface is unable to lock on to the frame of the incoming
optical signal for the SONET/SDH/OTU clients.
■ A defective upstream transmitter
■ Degradation of a fiber connection
■ Incorrect frame format from the client equipment
■ Bent or dirty fiber connection between the Trib port and the client equipment
■ Low optical power received
Clearing Procedure
1. Check that the client equipment is sending the SONET/SDH/OTU frame format that is expected by this
network element port.
2. Check the fiber connection between the Trib port and the client equipment.
3. Ensure the optical power received is within documented parameters.

Alarms 1-23
FAC0067
LOS
Loss Of Signal

■ Applicable Facilities - OTUki Section CTP, OTUCni Section CTP, Clear Channel, OTUCLIENTCTP,
Digital Channel, Fiber Channel Client, GbE Client, SDH, SONET, OCHCTP, CarrierCTP

This alarm is generated by the client termination point on the TOM, TIM-1-100GE, TIM-1-40GE. This
alarm is reported in the receive direction.
This alarm is generated when the TAM Clock and Data Recovery (CDR) unit has detected the Loss of
Lock defect for 2.5 seconds. Loss of lock defect = inability to lock for 100 microseconds.
■ Low OPR at the client facility
■ Client facility sending an unexpected signal framing
■ Client facility sending an unexpected data rate
■ Transmitter failure in the client equipment
Note: For client ports configured for 1.25G Clear Channel services, users must verify that the
incoming signal is 1.25GCC data rate. Ports configured for 1.25GCC services will not report a
client LOS alarm when a signal of a higher rate is received on the port.
Clearing Procedure
1. Check OPR on the trib port.

2. Ensure that the received signal framing is correct.
3. Ensure data rates are correct.
4. Check for equipment failure alarms reported by the TOM.
5. Check for failures in the client equipment.

FAC0068
OLOS
Optical Loss Of Signal
■ Alarm Type - Facility/Communication

■ SA/NSA - SA (Service-Affecting)/NSA (Non-Service Affecting)
■ Applicable Facilities - IDLERPTP, OSCTCTP, DSEPTP, FSMSCGPTP, FRMSCGPTP, OSCPTP,
FLEXCARRIERCTP, EXPNSCGPTP, OFXSCGPTP, Mid Stage Port, BASESCGPTP, OSAPTP,
SCHCTP
■ Detailed Conditions - OLOS

This alarm is generated by the Dispersion Compensation Module (DCM) port on the
BMM/OAM/ORM/DSE that provides the mid-stage DCM access, or by the CMM OCG port.
This alarm is generated when the BMM/OAM/ORM/DSE detects loss of receive optical power from the
DCM, or when the CMM detects loss of receive optical power from the BMM.
■ A fiber cut, a loose connector or a dirty fiber between the DCM and the BMM/OAM/ORM/DSE
■ A fiber cut, a loose connector or a dirty fiber between the CMM and the BMM
Clearing Procedure
1. Check the connectivity of the fiber between the BMM/OAM/ORM/DSE and the DCM port, or between
the CMM and the BMM.
2. Clean and reconnect the fiber between the BMM/OAM/ORM/DSE and the DCM port, or between the
CMM and the BMM.
3. Replace the fiber between the BMM/OAM/ORM/DSE and the DCM port, or between the CMM and the
BMM.

Alarms 1-25
FAC0073
TIM-DTP
Trace Identifier Mismatch

■ Applicable Facilities - DTF Path
■ Detailed Conditions - TIM

This alarm is generated by the Trib DTF Path termination point in the TAM and Line DTF Path termination
point on the line module.
This alarm is generated when the expected trace message does not match the received trace message
from the upstream DTN.
This alarm is generated when the transmitted DTF Path TTI from the ingress network element does not
match the expected DTF Path TTI at the egress network element.
■ Mis-configuration of transmit DTF Path TTI in the ingress network element or expected DTF Path
TTI in the egress network element
■ Mis-connection between the line module, or TEM and BMM in the upstream network element or in
this network element
■ Mis-connection between the network elements
Clearing Procedure
1. Check the transmit configuration in the upstream network element and the expected TTI in this
network element. If there is a mismatch, correct the configuration.
2. Ensure the fiber connection between the line module, TEM and BMM in the upstream network element
or in this network element is correct.

FAC0074
PLM
Payload Label Mismatch

■ SA/NSA - NSA
■ Applicable Facilities - DTF Path

This alarm is generated on the Trib DTF Path.
The criterion for alarm reporting is based on the mismatch between the provisioned cross-connect
payload in the source node and the destination node.
If the source cross-connect payload is SONET and destination cross-connect payload is something other
than SONET i.e. SDH, CLEAR CHANNEL, GbE LAN then Payload Mismatch will be reported in both the
source and destination nodes.
■ Different payloads provisioned manually at the either end of the circuit utilizing matching line side or
channel resources
Clearing Procedure
■ Manually restore the client Trib termination point payload type to that of its service type. This
requires the user to delete the cross-connect and rebuild the cross-connect in either of the nodes
(source node or destination node) to match the same payload

Alarms 1-27
FAC0075
OLOS
Optical Loss of Signal

■ Detailed Conditions - RX-OLOS

This alarm is generated by the line port on the BMM/OAM/ORM/RAM/SCM/OPSMPTP/DSE.
This alarm is generated when the BMM/OAM/ORM/RAM/SCM/DSE loses all of the receive optical power
for all expected bands and the Optical Supervisory Channel (OSC).
■ A loose, bent or broken fiber connector at a patch panel, or inside a
BMM/OAM/ORM/RAM/SCM/DSE in the local network element or the upstream network element
■ Physically severed fiber between local network element and the upstream network element
Clearing Procedure
1. Check fiber connectivity on the line port of the BMM/OAM/ORM/RAM/SCM/DSE on both ends of the
span.
2. Check for equipment failure at the upstream network element.

FAC0083
OLOS
Optical Loss Of Signal - Payload

■ Applicable Facilities - DLM OCG Port, OLM OCG Port, CMMOCHPTP, CMM OCG Port,
LMOCHPTP

This alarm is generated by the line module OCG port.
This alarm is generated when the optical power received is below the expected threshold for the OCG.
■ The BMM OCG-line module OCG fiber is removed/missing on local end or far end
■ The OTS OLOS/C-Band OLOS/DCF OLOS or when all 10 channels in the line module have an
LOF condition
■ Failure of the optical components on a BMM
■ Failure of the optical components on a line module
■ A BMM OCG OPR-OOR-HIGH Alarm present in the upstream BMM when the upstream network
element has Optical Express connectivity between BMM OCGs
■ A MIS-CONN Alarm present in the upstream BMM when the upstream network element has Optical
Express connectivity between BMM OCGs
■ Auto-discovery at the far end line module is not complete
■ The far end line module is locked or removed
Clearing Procedure
1. Check for the connectivity between the BMM and the line module.
2. Check for equipment alarms on the line module on the network element and the upstream digital
network element (that is, at the upstream line module).
3. Check for the equipment alarms on the BMM.
4. Check for an OPR-OOR-HIGH alarm on the upstream expressed OCGs.

Alarms 1-29
FAC0084
AIS-L
Alarm Indication Signal - Line

■ Detailed Conditions - AIS
■ Applicable Facilities - SONET

This alarm is generated by the downstream SONET client termination point on the TAM.
This alarm is generated when the client equipment in the upstream direction detects a LOS or LOF.
■ A problem in the SONET client network
■ AIS received from the client network
Clearing Procedure
1. Ensure proper fiber connectivity between the TOM and the SONET equipment.
2. Check for problems in the SONET client network.
3. Check for problems in the network.

FAC0085
AIS-MS
Alarm Indication Signal - MS

■ Applicable Facilities - SDH

This alarm is generated by the downstream SDH client termination point on the TAM and
TIM-5-10GM/GX.
This alarm is generated when the client equipment in the upstream direction detects a LOS or LOF in its
receive direction.
■ A problem in the SDH client network
Clearing Procedure
1. Ensure proper fiber connectivity between the TOM and the SDH equipment.
2. Check for problems in the SDH client network.

Alarms 1-31
FAC0086
TIM-S

■ Applicable Facilities - SDH, SONET, OLDPSCH, SCH

This alarm is generated by the SONET/SDH client port on TIM-5-10GM/GX.
This alarm is generated when the expected trace message does not match the trace message received
from the client equipment.
■ Incorrect configuration of the expected or transmit trace messages
■ Improper connectivity between the SONET/SDH client equipment and the Trib port
Clearing Procedure
1. Check the SONET/SDH J0 transmit configuration in the client equipment and the expected J0 in this
2. Check the connectivity between the client equipment and this network element.

FAC0088
OLOS
Optical Loss of Signal - Payload


This alarm is generated by the Band CTP on the BMM, OAM, TIM-5-10GM/GX, TIM-1-100GE,
TIM-1-40GE, TIM-1-100G, TIM-1-40G, FMMCSCGPTP, BASESCGPTP, EXPNSCGPTP,
FMMCSCGPTP, FMMFSCGPTP, FBMSCGPTP, FRMSCGPTP, OFXSCGPTP, ORM and RAM.
This alarm is generated when the BMM/OAM/ORM/RAM detects loss of all receive optical power for the C
band, while the OSC continues to have incoming optical power.
■ Hardware failures in the upstream network element or connection faults in the C band data path
■ Automatic Laser Shutdown (ALS) conditioning on the OTS link by an upstream network element
Clearing Procedure
1. Ensure proper fiber connectivity from the DCM port on the BMM/OAM/ORM/RAM.
2. Check for hardware failure(s) in the upstream network element.
3. Inspect all the line connections to the BMM on the upstream DTN.

Alarms 1-33
FAC0095
OPR-OORH
OPR Out of Range - High

■ Detailed Conditions - OPR too high

This alarm is generated by the Band layer on the BMM,OAM, ORM, RAM, OLM OCG Port ,GAM
OCGPTP, XTOCGPTP, XTSCGPTP or SCHCTP
This alarm is generated when Infinera’s Automated Gain Control (AGC)-based computed target gain is
equal to or greater than the Infinera defined threshold.
■ A fiber crimp between the upstream network element and this network element
■ BMM/OAM/ORM/RAM/GAM failure
■ Improper configuration of the link or too much attenuation
■ Misconfigured/damaged DCM at the upstream network element
Clearing Procedure
1. Ensure that there is proper attenuation between the upstream network element and this network
element.
2. Check for misconfigured DCM at the upstream network element or improper configuration of the link.
3. Check for equipment failure alarms reported by the BMM/OAM/ORM/RAM/GAM.
4. Check for a faulty photodiode/optical power monitor. To check if the photodiode is faulty remove the
fiber and check if the power value displayed changes. If the value changes, the photodiode is not
faulty. If the value remains the same, the photodiode is faulty. If the photodiode is faulty replace it.

FAC0096
OPR-OORL
OPR Out of Range - Low

■ Detailed Conditions - OPR too low

This alarm is generated by the Band layer on the BMM, OAM, ORM, RAM, OLM OCG Port, GAM
OCGPTP, XTOCGPTP, XTSCGPTP or SCHCTP
equal to or less than the defined threshold.
■ Power loss upstream
Clearing Procedure
element.
3. Check for the equipment failure alarms reported by the BMM/OAM/ORM/RAM/GAM.
4. Check for a faulty photodiode/optical power monitor and. To check if the photodiode is faulty remove
the fiber and check if the power value displayed changes. If the value changes, the photodiode is not

Alarms 1-35
FAC0097
OPR-OORH
■ TCC Type - Facility

■ Severity - Minor
■ Detailed Conditions - OPR too high

This threshold crossing condition (TCC) is generated by the Trib Port.
This TCC is generated when the optical power received is equal to or greater than the defined threshold.
■ The input power received is too high
■ Faulty receiver on the TOM
Clearing Procedure
1. Ensure there is proper attenuation between the client equipment and the TOM.
2. Check the client equipment for faults.
3. Check for the equipment failure alarms reported by the TOM.

FAC0098
OPR-OORL
■ TCC Type - Facility

■ Detailed Conditions - OPR too low

This threshold crossing condition (TCC) is generated by the Trib Port.
This TCC is generated when the optical power received is equal to or lower than the defined threshold.
■ The signal from the client equipment is too low
■ There is a crimped fiber between the client equipment and the TOM
Clearing Procedure
1. Ensure the fiber is not crimped.

2. Check the client equipment for faults.

Alarms 1-37
FAC0102
OPT-OORL
OPT Out Of Range - Low

■ Detailed Conditions - OPT-OORL

This alarm is generated by the optical channel termination point on the line module.
Optical power transmitted (OPT) must constantly be equal to or above (below) the High (Low) threshold
for 3 ms. Failure is declared when this defect persists for 2.5 +/- 0.5 secs. The thresholds are pre-defined
and are not user configurable.
Clearing Procedure
1. Ensure that the line module-BMM association is correct.

2. Ensure that Auto-discovery has been successfully completed.
3. Clean and reconnect the fiber between the line module and the BMM.

FAC0105
TIM-DTS

■ Detailed Conditions - TIM-S, DCHCTP-TTI-SECTION-TRACE-MISMATCH
Description and Causes (TIM-S)

This alarm is generated by the channel termination point in the line module.
This alarm is generated when the transmitted DTF Section TTI from the ingress network element does not
match the expected DTF Section TTI at the egress network element.
This alarm is also generated when the transmitted digital channel (DCH) CTP TTI from the ingress
network element does not match the expected DCH CTP TTI at the egress network element.
■ Mis-configuration of transmit DTF Section TTI in the ingress network element or expected DTF
Section TTI in the egress network element
■ Mis-configuration of transmit DCH CTP TTI in the ingress network element or expected DCH CTP
TTI in the egress network element
Description and Causes (DCHCTP-TTI-SECTION-TRACE-MISMATCH)

This alarm is generated by the digital channel termination point in the TAM-2-10GT.
This alarm is generated when the received DCHCTP TTI does not match the expected DCHCTP TTI.
■ Mis-configuration of fiber connection between the TAM-2-10GT cards installed in the customer side
network and provider side network of L1 OPN application
Clearing Procedure (TIM-S)
1. Check the DTS transmit configuration in the upstream network element and the expected TTI in this
2. Check the connectivity between the line module and BMM from the upstream network element and in
this network element.
3. Check the connectivity between the network elements.

Alarms 1-39
Clearing Procedure (DCHCTP-TTI-SECTION-TRACE-MISMATCH)
■ Check the fiber connectivity between the TAM-2-10GT installed in the customer side network and
provide side network of L1 OPN application

FAC0107
RFI-L
Remote Failure Indication - Line

■ Detailed Conditions - RDI

This alarm is generated by the SONET client termination point on the TAM and TIM-5-10GM/GX.
This alarm is generated when a RDI-L maintenance alarm is received for greater than 2.5 seconds.
Clearing Procedure
■ Check for a failure downstream of this network element (toward the client equipment).

Alarms 1-41
FAC0108
RFI-MS
Remote Failure Indication - Multiplex Section

■ Detailed Conditions - RDI

This alarm is generated by the SDH client termination point on the TAM and TIM-5-10GM/GX.
This alarm is generated when a RDI-MS maintenance signal is received for more than 2.5 seconds.
Clearing Procedure
■ Check for failure downstream of this network element (toward the client equipment)

FAC0109
OLOS
Optical Loss Of Signal


This alarm is generated by the Trib port on the TOM, TIM-5-10GM/GX, TIM-1-100GE, TIM-1-40GE,
TIM-1-100G,TIM-1-40G.
This alarm is generated when the received optical power is below the receiver sensitivity.
■ A physically severed fiber between the Trib port and the client equipment
■ A faulty transmitter in the client equipment
Clearing Procedure
1. Check the fiber connectivity between the Trib port and the client equipment.
2. Check for equipment failures in the client equipment.

Alarms 1-43
FAC0110
ADTIMEOUT
Auto-discovery Timed Out

■ Applicable Facilities - BMM OCG Port, DLM OCG Port, CMM OCG Port, FSMSCGPTP,
FRMSCGPTP, FMMFSCGPTP, LMOCHPTP, OLM OCG Port, FBMSCGPTP, OFXSCGPTP,
FMMCSCGPTP, XTOCGPTP, XTSCGPTP
■ Detailed Conditions - AUTODISC-TIMEOUT

This alarm is generated by the OCGPTP on the line module or BMM OCGPTP (OUT port), in case of an
optical express connection. In the case of a CMM to BMM interconnection, this alarm is generated by
OCGPTP on the CMM. In the case of an LM OCH to CMM interconnection, this alarm is generated by the
LMOCHPTP on the LM-80.
This alarm is generated when autodiscovery does not complete within the specified time.
■ CRC check failure
■ Failure of the optical components on the line module and/or LM-80
■ Failure of the optical components on the CMM
■ Failure of the 40G transponder on the LM-80
■ Dirty fiber between the BMM and the line module and/or between BMM OCGPTPs
■ Dirty fiber between the CMM and the BMM
■ Dirty fiber between the LM-80 and the CMM
Clearing Procedure
1. Perform the Auto-discovery operation manually from any of the management interfaces.
2. Clean or replace the fiber.
3. Check for the equipment failure alarms reported by the line module and/or LM-80.
4. Ensure that the OCGs of same type are connected together appropriately. In the case of a CMM to
BMM interconnection, ensure that the OCGs of same type are connected together appropriately.

5. Ensure that the connected OCG matches with the provisioned OCG.
6. Ensure there is a proper association between the line module OCG and the BMM and the BMM
OCGPTPs. In the case of a CMM to BMM interconnection, ensure this is a proper association between
the CMM OCG and the BMM OCG.

Alarms 1-45
FAC0112
MIS-CONN
Inter-module Mis-connection

■ Applicable Facilities - GAM OCG Port, Band Port, BMM OCG Port, Span, C-Band, CMMOCHPTP,
DSEPTP, FRMSCGPTP, FBMSCGPTP, FMMFSCGPTP, OFXSCGPTP, FSMSCGPTP,
FMMCSCGPTP, OPSMPTP
■ Detailed Conditions - LINK-MISMATCH
Table 1-2 Alarm Detailed Conditions

Detailed Condition Description
PeerNotFound Discovered AID is not valid
NotUserExpectedAssociation Own port is already provisioned to some other port
OwnCardDetected Discovered port is on its own card
PeerAlreadyAssociated Discovered port has already been provisioned to some other port
IncompatiblePorts Discovered card/port-type is not compatible with this card/port-
type
UnsupportedPeerTpType Discovered port-type is unknown
PreProvisioningMandatory Pre-provisioning is mandatory to successfully complete
AutoDiscovery
LosClearedWithoutAutoDiscoveredAssociation LOS is cleared without any Discovered port
AnotherPortIsAlreadyAssociatedToTheSameFru Same FRUs have already been associated via another set of
ports
OwnPortConfigInvalid Port configuration on own port is not correct (eg. Port that has
detected the AID is configured as ASEIdler
OwnEqptConfigInvalid Own equipment configuration is not compatible with the detected
port equipment (eg. If AOFx is connected to FRM equipment in
SLTE mode)

This alarm is generated by the OCG port on the BMM or OCH port on the CMM.
This alarm is generated when the line module type does not match the connected OCG port on the BMM,
that is, the provisioned OCG type does not match the discovered OCG type. For example, DLM/XLM-1-
C1 is connected to OCG 3 port on the BMM, instead of connecting to OCG 1 port.

This alarm is also generated when the LM-80 OCH does not match the connected OCH port on the CMM,
that is, the provisioned OCH type does not match the discovered OCH type. For example
AXLM-80-T1-C5 port 1 is configured for OCH 1 and connected to OCH 2 on the CMM, instead of
connecting to OCH 1.
This alarm is most likely caused:
■ When a BMM is connected to another BMM of the same type (both are either 40 or 80 channel) but
the max channel configuration is different in each (for example, one BMM is set to 40 channels and
the other is set to10 channels)
■ By mis-connection of the fibers between the line module and the BMM
■ By mis-connection of the fibers between the LM-80 and CMM
■ Installing the wrong line module type
■ Mismatch between the provisioned OCG type and discovered OCG type
■ When a mis-connection is created in GAMOCGPTP, for example when a GAM receives a signal
from a different line module when compared to the provisioned line module
■ When the BMM2-8-CH3-MS and BMM2H-4-R3-MS cards receive some valid power in the BAND
CTP and if the association is not completed with Expansion BMM2
■ When BMM2-8-CEH3 and BMM2H-4-B3 expansion cards receive some valid power in the BAND
CTP and if the association is not completed with the Base BMM2
■ When a BMM2-8-CH3-MS (Base BMM2) is configured for 160 channels and the Neighbor BMM
has not been configured.
This alarm can also be generated by the Band layer on a BMM, OAM, ORM or RAM. It is most
likely caused:
■ When the configured channel numbers on BMMs installed at either end of the span do not match.
This alarm can also be generated by the network element on the DSE PTP. It is most likely caused
when:
■ The DSE PTP detects a signal with a power level above the OLOS threshold value and if this DSE
PTP is not provisioned to a corresponding ORM (or OAM/BMM) DCF PTP
Clearing Procedure
1. Ensure that the provisioned OCG type and discovered OCG type are the same.
2. Ensure that the correct line module OCG (in slot and chassis) is connected to the appropriate BMM
OCGPTP.
3. Check if the configured number of channels match in the BMMs installed on either end of the span.

Alarms 1-47
4. If the alarm is raised on the DSE PTP, ensure that the provisioning of the DSE PTP is done
appropriately.
5. If the alarm is raised on the CMMOCHPTP, ensure that the OCH ports of the LM-80 and CMM are
provisioned for the correct (same) channel.

FAC0114
OPR-OORL

■ Applicable Facilities - BMMOCG, GAMOCG, CMMOCH
■ In the case of a BMM OCG:

□ This alarm is generated by the OCGPTP on the BMM
□ This alarm is generated when the OPR is below the pre-defined threshold value
■ In the case of a GAM OCG:
□ The alarm is generated by the OCGPTP on the GAM (Trib side)
■ In the case of a CMM OCH:
□ The alarm is generated by the OCHPTP on the CMM (OCH side)
In the case of a BMM OCG, this alarm is most likely caused by:
■ Failure in the fiber connection (dirty or bent) between the line module and the BMM
■ Failure in the fiber connection (dirty or bent) between the line module and the GAM OCG
■ Fault in the line module
■ Fault in the BMM
■ Power received by the BMM OCGPTP is not within specifications
In the case of a GAM OCG, this alarm is most likes caused by:
■ Failure in the fiber connection (dirty or bent) between the line module and the GAM OCG
■ Fault in the GAM
■ Power received by the GAM OCGPTP is not within specifications
In the case of a CMM OCH, this alarm is most likes caused by:
■ Failure in the fiber connection (dirty or bent) between the LM-80 and the CMM OCH
■ Fault in the LM-80

Alarms 1-49
■ Fault in the CMM

■ Power received by the CMM OCHPTP is not within specifications
Note: During OPR-OORL condition even if the alarm is raised correctly, the received power in
management interface is shown as -55dBm.
Clearing Procedure
In the case of a BMM OCG:

1. Check for hardware failures in the line module and the BMM.
2. Check the fiber connectivity between the line module and the BMM.
3. Remove, inspect, clean and re-insert the fiber between the line module and the BMM.
4. Check the power received by the BMM OCGPTP. Ensure attenuation between the express OCGs
does not exceed Infinera specifications (22dB).
In the case of a GAM OCG:
5. Check the fiber connectivity between the line module and the GAM.
6. Remove, inspect, clean and re-insert the fiber between the line module and the GAM.
7. Check for hardware failures in the line module and the GAM.
In the case of a CMM OCH:
8. Check the fiber connectivity between the LM-80 and the CMM.
9. Remove, inspect, clean and re-insert the fiber between the LM-80 and the CMM.
10. Check for hardware failures in the LM-80 and the CMM.

FAC0115
OPR-OOR-H

■ Applicable Facilities - BMMOCG, GAMOCG, CMMOCH

This alarm is generated by the OCGPTP on the BMM and the GAM, or between the LM-80 and CMM.
This alarm is generated when the OPR is above the pre-defined threshold value.
■ Fault in the LM-80
■ Fault in the BMM
■ Fault in the GAM
■ Fault in the CMM
■ Power received by the BMM OCGPTP exceeds the specified values
■ Power received by the GAM OCGPTP exceeds the specified values
■ Power received by the CMM OCHPTP exceeds the specified values
Clearing Procedure
In the case of a BMM OCG:
1. Check for hardware failures in the line module and the BMM.
2. Check the fiber connectivity between the line module and the BMM.
3. Remove, inspect, clean and re-insert the fiber between the line module and the BMM.
4. Check the power received by the BMM OCGPTP. Ensure attenuation between the express OCGs
does not exceed Infinera specifications (22dB).
In the case of a GAM OCG:
5. Check the fiber connectivity between the line module and the GAM.
6. Remove, inspect, clean and re-insert the fiber between the line module and the GAM.
7. Check for hardware failures in the line module and the GAM.
In the case of a CMM OCH:

Alarms 1-51
8. Check the fiber connectivity between the LM-80 and the CMM.
9. Remove, inspect, clean and re-insert the fiber between the LM-80 and the CMM.
10. Check for hardware failures in the LM-80 and the CMM.

FAC0116
OPR-OORL


This alarm is generated by the DCM port on a BMM/OAM/ORM with a DCM port.
This alarm is generated when the OPR is less than the pre-defined threshold value.
■ Improper fiber connection between the DCM and the DCM ports on the BMM/OAM/ORM
Clearing Procedure
1. Check the fiber connectivity between the DCM port on the BMM/OAM/ORM and the DCM.
2. If no DCM is present, ensure the fiber loop is present on the DCM port on the BMM/OAM/ORM.

Alarms 1-53
FAC0117
POST-FEC-BER-SF
Post-FEC BER-based Signal Failure

■ Detailed Conditions - SIGNAL-FAILURE-LINE, SIGNAL-FAILURE

This alarm is generated by the DTPCTP, OCHCTP, CarrierCTP and the channel termination point.
This alarm is generated when the bit error rate (BER) as measured by DTP BIP-8 field exceeds the
predefined threshold value of 1E-5.
If it is part of a protection or an unprotected restorable scheme, the alarm is raised with a severity of Minor
and non-service affecting. However, if the BER exceeds the predefined threshold on an unprotected
circuit, the alarm is raised with severity as Critical and service-affecting.
The severity and service-affecting fields of this alarm are based on the protection switch state. If the DTP
has a failure and a successful protection switch is performed or if the failure was associated with the non-
active PU (thus no protection switch was done/needed), the alarm’s severity is Minor and is non-service
affecting.
Clearing Procedure
1. Check the OPR to the line module OCGPTP.

2. Check for problems in the affect channel’s digital span.

FAC0118
DE-ENCAP-LOS
De-encapsulated Loss of Signal

■ Applicable Facilities - Clear Channel, SubClient, GbE Client, Fiber Channel Client, SDH,
OTUCLIENTCTP, SONET

This alarm is generated by the client CTP of TIM-1-100GE, TIM-1-40GE.
This alarm is generated when the upstream network element receives optical power below the receiver
sensitivity.
Clearing Procedure

Alarms 1-55
FAC0119
DE-ENCAP-LOF
De-encapsulated Loss of Frame

■ Applicable Facilities - SubClient, SDH, OTUCLIENTCTP, SONET

This alarm is generated by the SONET/SDH/OTU client port on TIM-5-10GM/GX.
This defect/failure is declared on the de-encapsulated client signal recovered from the network side--the
extracted DTP payload. A de-encap SEF/LOF defect is raised when the condition persists for 3ms. A de-
encap SEF/LOF defect is declared when the incoming signal has a minimum of four consecutive errored
framing patterns.
■ Incorrect frame format from client equipment
■ Low received optical power
Clearing Procedure
1. Check that the client equipment is sending the SONET/SDH/OTU frame format that is expected by this
network element port.
3. Ensure the OPR on the Trib port is within documented threshold.

FAC0120
DE-ENCAP-LOSYNC
De-encapsulated Loss Of Sync

■ Applicable Facilities - GbE Client, Fiber Channel Client
■ Detailed Conditions - DE-ENCAP-LOSYNC

This alarm is generated by the GbE Trib CTP on TIM-5-10GM/GX, TIM-1-100GE, TIM-1-40GE and the
FCClient CTP.
This alarm is generated when the upstream network element detects a LOSYNC.
■ Client equipment sending the wrong signal format
■ Equipment fault
Clearing Procedure
1. Ensure that the correct signal format is being received.

3. Check for equipment failures at the upstream network element.

Alarms 1-57
FAC0121
DE-ENCAP-AIS-L
De-encapsulated Alarm Indication Signal - Line

■ Detailed Conditions - DE-ENCAP-PL-AIS
■ Applicable Facilities - Sonet Client CTP, SubClient

This alarm is generated by the downstream client termination point on the TAM.
This alarm is generated on the de-encapsulated client signal recovered from the network. This alarm is
raised when the upstream network element receives an AIS-L from the client equipment.
■ A problem in the client network
Clearing Procedure
1. Check for problems in the client network.


FAC0122
DE-ENCAP-AIS-MS
De-encapsulated Alarm Indication Signal - MS

■ Applicable Facilities - SDH Client CTP, Sub Client

This alarm is generated by the downstream SDH CTP on the TAM and TIM-5-10GM/GX.
raised when the upstream network element receives a AIS-MS alarm from the client equipment.
■ A problem in the SDH client network
■ AIS-MS received from the client network
Clearing Procedure
1. Check for problems in the SDH client network.


Alarms 1-59
FAC0123
TRIB-TESTSIG-GEN
Test Signal Generation Activated, toward Client

■ Applicable Facilities - GbE Client, Fiber Channel Client

This alarm is generated by the 1GbE (TAM-8-1G), 1GFC/2GFC/8GFC client (TAM-8-2.5GM), 10GFC
client (TAM-2-10GM), TIM-5-10GM/GX, TIM-1-100GE and TIM-1-40GE.
This alarm is generated when the trib test signal generation is enabled (toward the client) for this
termination point.
Clearing Procedure
■ Manually clear the trib test signal generation (toward the client)

FAC0125
LINE-TESTSIG-GEN
Test Signal Generation Activated, toward Network


This alarm is generated by the 1GbE (TAM-8-1G), 1GFC/2GFC/8GFC client (TAM-8-2.5GM), 10GFC
client (TAM-2-10GM), TIM-5-10GM/GX, TIM-1-100GE and TIM-1-40GE.
This alarm is generated when the line test signal generation is enabled (toward the Infinera network) for
this termination point.
Clearing Procedure
■ Manually clear the line test signal generation (toward the Infinera network)

Alarms 1-61
FAC0127
TRIB-TESTSIG-OOS
Test Signal Out of Sync, from Client

■ Detailed Conditions - TRIB-TESTSIG-OOS

This alarm is generated by the 1GbE (TAM-8-1G) and TIM-5-10GM/GX.
This alarm is generated when the system has detected that the trib test signal received from the client is
out of sync.
Clearing Procedure
1. Ensure the trib test signal pattern has been properly configured.
2. The alarm will clear when the system detects that the received trib test signal pattern from the client is
in synch.

FAC0128
LINE-TESTSIG-OOS
Test Signal Out of Sync, from Network

■ Detailed Conditions - LINE-TESTSIG-OOS

This alarm is generated by the 1GbE (TAM-8-1G) and TIM-5-10GM/GX.
This alarm is generated when the system has detected that the line test signal received from the Infinera
network is out of sync.
Clearing Procedure
1. Ensure the line test signal pattern has been properly configured.
2. The alarm will clear when the system detects that the received line test signal pattern from the Infinera
network is in synch.

Alarms 1-63
FAC0129
LOSYNC
Loss of Sync

■ Applicable Facilities - Fiber Channel Client, GbE Client
■ Detailed Conditions - LOSYNC

This alarm is generated by the 1GbE (TAM-8-1G), 10GbE client trib termination point (TAM-2-10GR),
1GFC/2GFC/8GFC client (TAM-8-2.5GM), 10GFC client (TAM-2-10GM), 40GbE client (TAM-1-40GE/
TAM-1-40GR), 100GbE client (TAM-1-100GE/TAM-1-100GR), TIM-5-10GM/GX, TIM-1-40GE and
TIM-1-100GE.
This alarm is generated when a Loss Of Sync is detected from the client signal.
■ Physically severed fiber between local network element and the upstream network element
Clearing Procedure

FAC0222
TRIB-PRBS-GEN
Trib PRBS Generation Activated, toward Client

■ Applicable Facilities - Digital Channel, GFP Client, SDH, SONET

This alarm is generated when a TRIB PRBS generation is applied on the digital channel (DCh)
termination point, SONET client trib termination point, the SDH client trib termination point, Fiber Channel
CTP, OTU CTP or ODUKT CTP.
Clearing Procedure
■ Disable the PRBS generation on the digital channel termination point, SONET client trib termination
point, the SDH client trib termination point, Fiber Channel client termination point, OTU client
termination point or ODUKT Client termination point

Alarms 1-65
FAC0223
LINE-PRBS-GEN
PRBS Generation Activated, toward network

■ Applicable Facilities - SONET, GFP Client, Digital Channel, SDH

This alarm is generated when the line module has detected that PRBS generation is activated on the
digital channel termination, SONET client trib termination point, the SDH client trib termination point, the
Fiber Channel client termination point, ODUKT client termination point or OTU client termination point.
Clearing Procedure
1. Check whether PRBS generation is activated in the far end client equipment.
2. Check whether PRBS monitoring is activated in the near end client equipment.
3. Check the SNC setup.

FAC0224
TRIB-PRBS-OOS
Trib PRBS Out of Sync from Client

■ Applicable Facilities - GFP Client, Digital Channel, SONET, SDH

This alarm is generated when the line module detects that the received TRIB PRBS pattern is out of
synch on the digital channel termination point, SONET client trib termination point, the SDH client trib
termination point, Fiber Channel client termination point, ODUKT client termination point or OTU client
termination point.
Clearing Procedure

Alarms 1-67
FAC0225
LINE-PRBS-OOS
PRBS out of sync, from network

■ Applicable Facilities - GFP Client, SDH, SONET, Digital Channel

This alarm is generated when a PRBS pattern is applied on the SONET Client Trib termination point, the
SDH Client Trib termination point, Fiber Channel client termination point, ODUKT Client termination point
or OTU Client termination point.
Clearing Procedure

FAC0226
LOA
Loss of Alignment

■ Severity - Critical/Major
■ SA/NSA - SA
■ Applicable Facilities - GbE Client, VCG, SDH and SONET for TIM_1-40GM

This alarm is raised when the system has detected one or more of the constituent members of virtual
concatenation group (VCG) or GigE Client CTP of TIM-1-100GE and TIM-1-40GE are out of alignment.
■ One or more of the members of the VCG or GigE Client CTP are not able to achieve performance
threshold for the skew limit budget (skew limit is 5.7 microseconds)
Clearing Procedure
■ Ensure all members of the VCG or GigE Client CTP are able to achieve performance threshold for
the skew limit budget.

Alarms 1-69
FAC0227
OL-OORH
OCG Loss Out of Range - High

■ Severity - Minor (user customizable)
■ SA/NSA - NSA
■ Applicable Facilities - OLM OCG Port, BMM OCG Port, CMM OCG Port, DLM OCG Port, GAM
OCG Port, XTOCGPTP, XTSCGPTP
■ Direction - Transmit
■ In cases where a GAM is not used:

□ That is, when the DLM/XLMs are connected to BMMs only, this alarm will be raised when the
optical loss difference between OCGOPT on the line module (DLM/XLM) and the respective
BMM OCGOPR is greater than 1.5dB
□ That is, when the ADLM/AXLMs in Gen 2 operating mode are connected to BMM2s only, this
alarm will be raised when the optical loss difference between OCGOPT on the line module
(ADLM/AXLM) and the respective BMM2 OCGOPR is greater than 1.5dB
■ In cases where a GAM is used (that is, when DLM/XLMs are connected to BMM2s via GAMs) this
alarm will be raised on:
□ The OCGPTP on the DLM/XLMs when the optical loss difference between DLM/XLM
OCGOPT and the GAM Trib OCGOPR is greater than 1.5dB
□ The GAM OCGPTP when the optical loss difference between GAM Line OCGOPT and
BMM2 OCGOPR is greater than 1.5dB
■ This alarm is raised on a BMM2 OCGPTP when the optical loss difference between the BMM2
OCGPTP and BMM2 OCGPTP optical express is greater than 3dB. However, it will not be raised
on the BMM2 OCGPTP for which only ASE is present
■ This alarm is raised when the fiber patch loss between the BMM2/BMM2P OCGPTP to GAM
OCGPTP and between the GAM OCGPTP to the ADLM/AXLM OCGPTP is greater than the
Infinera defined threshold values (1.5dB) for each of these segments
■ In the case of an LM-80 to CMM or CMM to BMM interconnection, this alarm is raised when the
optical loss difference between the LM-80 and CMM or between the CMM and BMM exceeds the
pre-defined threshold value:
□ 1.5dB between LM-80 OCH and CMM OCH
□ 1.5dB between CMM OCG and BMM OCG (Gen 2/2P)
□ 18.0dB (15.0dB attenuator pad + 3.0dB) between CMM OCG and BMM OCG (Gen 1)

■ When a GAM is not used:

□ Failure in the fiber connection (dirty or bent fiber) between the line module and a BMM
■ When a GAM is used:
□ Failure in the fiber connection (dirty or bent fiber) between the line module and a GAM Trib
OCGPTP
□ Failure in the fiber connection (dirty or bent fiber) between the GAM OCGPTP and a BMM
OCGPTP
■ When an LM-80 and CMM are used:
□ Failure in the fiber connection (dirty or bent fiber) between the LM-80 and the CMM
□ Failure in the fiber connection (dirty or bent fiber) between the CMM and the BMM
■ When AOLx/AOLx2 is connected to BMM2:
□ Failure in the fiber connection (dirty or bent fiber) between the OLM and BMM2
□ Failure in the fiber connection (dirty or bent fiber) between BMM2 and OLM
Clearing Procedure
1. Ensure fiber is fully connected.

2. Inspect, clean and re-insert the fiber.
3. Replace bad fiber.

Alarms 1-71
FAC0228
ADMIN-MAINT
Administrative Maintenance

■ Severity - Not Reported (User Provisionable)
■ SA/NSA - NSA
■ Applicable Facilities - Optical Channel, Digital Channel, GFP Client, IDLERCHANNELCTP, OTUki
Section CTP, OTUCni Section CTP, FLEXCARRIERCTP, FBMSCGPTP, SONET, DTF Path,
CARRIERCTP, DLM Optical Channel, IDLERPTP, Clear Channel, ODUk Client/CTP, TRIBPTP,
SubClient, ODUki CTP, SDH, OTUCLIENTCTP, ODUkT, VCG, GbE Client, Fiber Channel Client,
PXM, OCHPTP, XTOCGPTP, XTSCGPTP, SCHCTP, CarrierCTP, TribCTP, Digital Wrapper CTP

This alarm is raised when the user has administratively put any of the applicable facilities into
maintenance state by using the management interface command.
Clearing Procedure
■ This alarm is cleared by unlocking the managed object using the management interface command

FAC0229
ADMIN-LOCK
Administrative Locked
■ Alarm Type - Facility / Communication

■ SA/NSA - SA/NSA
■ Applicable Facilities - GMPLS_CONTROL_CHANNEL, FRMSCGPTP, FBMSCGPTP,
FMMFSCGPTP, OLM OCG Port, ODUk Client/CTP, LMOCHPTP, DLM OCG Port, ODUki CTP,
TRIBPTP, FLEXCARRIERCTP, OSCTCTP, Optical Channel, SELECTOR, CMMOCHPTP, DLM
Optical Channel, DTF Path, BMM OCG Port, CMM OCG Port, SA, Band Port, SCHCTP,
IDLERCHANNELCTP, OFXSCGPTP, OSC, IDLERPTP, EXPNSCGPTP, FMMCSCGPTP,
FSMSCGPTP, PXM, XTOCGPTP, OCHCTP, XTSCGPTP, SCHCTP, CarrierCTP, TribPTP

This alarm is raised when the user has administratively put any of the applicable facilities into the locked
state by using the management interface command.
Clearing Procedure
■ This alarm is cleared by unlocking the managed object using the management interface command

Alarms 1-73
FAC0230
PWRLOOP-DISABLED
Power Control Loop Disabled

■ SA/NSA - NSA
■ Applicable Facilities - SCGPTP, OCGPTP, FBMSCGPTP, FMMFSCGPTP, FRMSCGPTP,
XTOCGPTP

This Alarm is raised when the OCG/SCG Power Control Loop feature is disabled by means of the
management interface.
Clearing Procedure
■ Enable the OCG/SCG Power Control Loop feature by using the management interface command

FAC0231
ALS-DISABLED
Automatic Laser Shutdown Disabled

■ SA/NSA - NSA
■ Applicable Facilities - BAND CTP

This alarm is raised when the user has disabled the ALS feature by using the management interface
command.
Clearing Procedure
1. Enable the ALS feature by using the management interface command.
2. The alarm will clear once the ALS-disabled timer has expired (the timer is user configurable).
3. The BMM/OAM/ORM/RAM has been made to do a warm reset.

Alarms 1-75
FAC0280
OPR-OORL

■ Applicable Facilities - FLEXCARRIERCTP, FSMSCGPTP, OFXSCGPTP, OSCTCTP, OSAPTP,
FRMSCGPTP, FMMCSCGPTP, OPSMPTP, XTSCGPTP

This alarm is generated by the RAM modules (RAM-1, RAM-2-OR, REM-2), DCF PTP and/or DSE (OSA
PTP).
In case of RAM modules, this alarm is generated when the received OSC optical power falls below a
predefined Infinerathreshold. It is most likely caused by:
■ Fault in the fiber connection between the BMM Line OUT port, and the RAM-1 or RAM-2-OR
BMM/OAM IN port
■ Fault in the fiber connection between the RAM-2-OR LINE OUT port and the REM-2's RAM-2-OR
IN port
In case of a DCF PTP, this alarm is generated if the mid-stage optical power received by the DCF
PTP falls below a predefined Threshold.
In case of a DSE (OSA PTP), this alarm is generated if the OSC optical power received by the DSE
(OSA PTP) falls below a predefined Threshold.
Clearing Procedure
1. Check the fiber connections.
2. Check the power received by the OSC port on the RAM module generating the alarm.
3. Compare to the OSC transmit power levels from the connected BMM or OAM, or in the case of the
REM-2, the OSCT OPT power of the attached RAM-2-OR.
4. In case of this alarm reported on DCF PTP, check for dirty fiber connector, fiber crimp, or other
unexpected attenuation on DCF/DCM and take appropriate actions to rectify the fault in the connector
or fiber.

FAC0281
OPR-OORH

■ Applicable Facilities - FLEXCARRIERCTP, FSMSCGPTP, OSCTCTP, OFXSCGPTP,
FRMSCGPTP, FMMCSCGPTP, OPSMPTP, XTSCGPTP

This alarm is generated by the RAM modules: RAM-1, RAM-2-OR, and/or REM-2.
This alarm is generated when the received OSC optical power falls above a predefined Infinera threshold.
■ Incorrect fiber connection between the BMM Line OUT port, and the RAM-1 or RAM-2-OR
BMM/OAM IN port
■ Incorrect fiber connection between the RAM-2-OR LINE OUT port and the REM-2's RAM-2-OR IN
port
Clearing Procedure

Alarms 1-77
FAC0282
OPT-OORL
OPT Out of Range - Low

■ Applicable Facilities - SCHCTP, CARRIERCTP, OSCTCTP, LMOCHPTP, FRMSCGPTP,
OFXSCGPTP, FSMSCGPTP, FMMCSCGPTP

This alarm is generated when the transmitted OSC optical power falls below a predefined threshold.
■ Fault in the fiber connection between the BMM Line OUT port and the RAM-1's BMM/OAM IN port
IN port
■ Failure in the OSC regeneration circuitry of the RAM-2-OR module
Clearing Procedure

FAC0283
OPT-OORH
OPT Out of Range - High
■ Alarm Type - Facility / Communication

■ Applicable Facilities - SCHCTP, OSCTCTP, FMMCSCGPTP, FRMSCGPTP, FSMSCGPTP,
OFXSCGPTP

This alarm is generated when the transmitted OSC optical power falls above a predefined threshold.
■ Fault in the fiber connection between the BMM Line OUT port and the RAM-1's BMM/OAM IN port
IN port
■ Failure in the OSC regeneration circuitry of the RAM-2-OR module
Clearing Procedure

Alarms 1-79
FAC0292
BDI-DTP
Backward Defect Indication DTP


This alarm is generated by the Trib DTF Path termination point on the TAM and TIM-5-10GM/GX.
This alarm is caused when:
■ The transmit BDI-DTP maintenance signal is received for more than 2.5 seconds
Clearing Procedure
■ Check for faults between this node and a downstream DTN. Faults can be OLOS, LOF, or AIS-DTP

FAC0293
AIS-DTP
Alarm Indication Signal DTP


This alarm is generated by the Trib DTF path on a TAM-2-10GT and TIM-5-10GM/GX.
This alarm is generated when the line module in the upstream network element detects a Loss of Frame
(LOF) for the corresponding Optical Channel (OCh) on its receive path and sends an AIS-DTP
maintenance signal to this network element which is in the downstream direction. Failure is declared
when this defect persists for 2.5 +/- 0.5 seconds.
■ A problem in upstream network element or the network
Clearing Procedure
■ Identify if the problem is in some digital network element upstream of this network element.

Alarms 1-81
FAC0294
TIM-DTP
Trace Identifier Mismatch DTP


This alarm is generated by the Trib DTF path on a TAM-2-10GT when the expected trace message does
not match the received trace message from the upstream DTN.
This alarm is generated when the transmitted DTF Path TTI from the ingress network element does not
match the expected DTF Path TTI at the egress network element.
■ Hardware faults in the DTF path of the TAM-2-10GT in upstream network element
■ Hardware faults in the DTF path of the TAM-2-10GT in this network element
Clearing Procedure
1. Check for the equipment failure alarms reported by the TAM-2-10GT in the upstream network element.
2. Check for the equipment failure alarms reported by the TAM-2-10GT in this network element. If any,
replace the line module/TAM/TOM.

FAC0295
POST-FEC-BER-SF
Post-FEC BER-based Signal Failure DTP

■ Detailed Conditions - SIGNAL-FAILURE-LINE, SIGNAL-FAILURE

This alarm is generated by the Trib DTF path on a TAM-2-10GT when the bit error rate (BER) as
measured by DTP BIP-8 field exceeds the predefined threshold value of 1E-5.
If it is part of a protection scheme, the alarm is raised with a severity as Minor and non-service affecting.
However, if the BER exceeds the factory default on the working line, the alarm is raised with severity as
Critical and service-affecting.
The severity and service-affecting fields of this alarm are based on the protection switch state. If the DTP
has a failure and a successful protection switch is performed or if the failure was associated with the non-
active PU (thus no protection switch was done/needed), the alarm’s severity is Minor and is non-service
affecting.
Clearing Procedure
1. Check the input power level to the line module.

2. Check for problems in this channel’s digital span.

Alarms 1-83
FAC0296
LOF-DTP
Loss of Frame DTP


This alarm is generated by the Trib DTF path on a TAM-2-10GT and TIM-5-10GM/GX.
■ Incorrect frame format from the client equipment
■ Low received optical power
Clearing Procedure
1. Check for the equipment failure alarms reported by the TAM-2-10GT in the upstream network element.
2. Check for the equipment failure alarms reported by the TAM-2-10GT in this network element. If any,
replace the TAM-2-10GT.

FAC0297
OPR-OORL

■ Applicable Facility - DLM OCG PTP, OLM OCG PTP

This alarm is generated by the DLM OCG PTP.
equal to or less than the Infinera defined threshold.
Note: During OPR-OORL condition even if the alarm is raised correctly, the received power in
management interface is shown as -55dBm.
Clearing Procedure
element.
3. Check for the equipment failure alarms reported by the BMM/OAM/ORM/RAM/GAM.
4. Check for a faulty photodiode/optical power monitor and. To check if the photodiode is faulty remove
the fiber and check if the power value displayed changes. If the value changes, the photodiode is not

Alarms 1-85
FAC0298
OPR-OORH

■ Detailed Conditions - OPR-OORH
■ Applicable Facility - DLM OCG PTP, OLM OCG PTP

The network element supports the OPR-OORH facility alarm on the ADLM/AXLM/SLM OCGPTP when
the corresponding Infineraset threshold for this alarm is crossed.
■ Fault in the line module (ADLM/AXLM/SLM)
■ Fault in the BMM2
■ Power received by the OCG (ADLM/AXLM/SLM) is exceeding the specifications
■ Power control loop is disabled on the BMM2
Clearing Procedure
1. Check for hardware failures in the ADLM/AXLM/SLM and BMM2.

2. Ensure the OCG power control loop on the BMM2 is enabled.

FAC0299
CONNECTIVITYFAIL
Connectivity Verification Failed

■ Detailed Conditions - CONNECTIVITYFAIL

This alarm is generated by the digital channel termination point (DchCTP) as a result of connectivity
failure in the provider network. This alarm is cleared when the connectivity is restored in the provider
network.
For this mechanism to work effectively, Connectivity verification must be enabled on the DchCTP at the
Customer Edge (CE) devices and disabled at the Provider Edge (PE) devices.
When a fault in the provider network is detected, then the DchCTP at the Customer Edge(CE) device will
raise the Connectivity Verification fail alarm. This alarm will also be reported by the DchCTP at the
Customer Edge (CE) device when bandwidth is not provisioned in the Provider Edge device.
Clearing Procedure
■ Rectifying the fault in the provider network would clear this alarm

Alarms 1-87
FAC0300
OL-OORH
Optical Loss Out of Range - High

■ Detailed Conditions - OL-OORH
■ Applicable facilities - DSEPTP, Span, FRMSCGPTP, OFXSCGPTP, FSMSCGPTP,
FMMCSCGPTP, FBMSCGPTP, FMMFSCGPTP, FRMSCGPTP, XTSCGPTP

This alarm is raised when the total (combined) optical loss of the two fibers connecting the mid-stage
client card (ORM, OAM, BMM) to the DSE exceeds threshold value. The threshold supported is 1.5dB.
The alarm is also raised during the following condition:
■ OL-OORH alarm is applicable between ORM-CXH1 and booster amp. Threshold supported is
1.5dB
■ Faulty optical attenuator
■ Pinched fiber
■ Fiber not fully connected
Clearing Procedure
1. Replace the faulty optical attenuator.

2. Ensure the fiber is fully connected.
3. Replace the fiber.

FAC0301
OL-OORH
Band Loss Out of Range - High

■ Detailed Conditions - OL-OORH

This alarm is generated by the Band layer on the BMM2E when the set threshold is crossed.
The optical loss on the fiber from BMM2E to base BMM2 exceeds the threshold-optical loss which is the
difference between the measured power launched from the BMM2E (approximately 1.5dB) towards the
base BMM2, and the measured received power on the base BMM2 expansion port.
Clearing Procedure
1. Clean the faulty fiber.

2. Ensure the fiber is fully connected.
3. Replace the fiber.

Alarms 1-89
FAC0302
OCG-MSMT
OCG Mismatch

■ Applicable Circuit Pack - ADLM/AXLM/SLM
■ Applicable Facilities - DLMOCG PTP, OLM OCG Port, XTOCGPTP
■ Detailed Conditions - OCG Mismatch

This alarm is generated when there is a mismatch between the provisioned OCG number in the MCM
database and the installed OCG number on the line module (the last known OCG number to which the
line module was tuned to).
Clearing Procedure
1. Modify the tunableOcgNumber attribute to match that (OCG number) of the installed line module.
2. Re-provision the OCG number of the line module to match the current value of the
tunableOcgNumber. Do one of the following:
■ In GNM, launch the corresponding properties window. In the Tunable tab, select the Apply OCG
Number check-box without editing the Provisioned OCG Number field. Click Apply
■ In TL1, execute the command, ed-eqpt retaining the same value for PROVOCG

FAC0311
AIS-OTU
Alarm Indication Signal - OTU


This alarm is generated by the OTU client CTP and OTUki Section CTP / OTUCni Section CTP on
TIM-5-10GM/GX.
Clearing Procedure


Alarms 1-91
FAC0312
BDI-OTU
Backward Defect Indication - OTU

■ Severity - Critical/Not Reported
■ Applicable Facilities - OTU Client CTP, OTUKiSectionCTP, OTUCniSectionCTP

This alarm is generated by the OTU Client termination point on the GM TAM(TAM-2-10GM or
TAM-8-2.5GM), TIM-5-10GM/GX, TIM-1-100G, TIM-1-40G and OLM.
Clearing Procedure

2. Check for problems in the OTU client network.

FAC0313
TX-TIM

■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, OTU Client CTP, OTUki CTP, SCH CTP

This alarm is generated by the ODU and OTU Client termination points on TIM-5-10GM/GX, TIM-1-100G
and TIM-1-40G.
This alarm is generated by the ODU client termination point on a GM TAM (TAM-2-10GM or
TAM-8-2.5GM) and OLM when the expected trace message does not match the received trace message
from the upstream DTN.
Clearing Procedure
■ TIM monitoring mode is off or there is no mismatch with the expected value of SAPI (DAPI/SAPI-
DAPI)

Alarms 1-93
FAC0314
DE-ENCAP-AIS-OTU
De-encapsulated Alarm Indication Signal - OTU

■ Severity - Not reported (user customizable)

This alarm is generated by the OTU Client termination point.
raised when the upstream network element receives an AIS from the client equipment.
Clearing Procedure


FAC0315
DE-ENCAP-BDI-OTU
De-encapsulated Backward Defect Indication - OTU


raised when the upstream network element receives an AIS from the client equipment.
Clearing Procedure


Alarms 1-95
FAC0317
SD
Signal Degraded

■ Applicable Facilities - OTUki Section CTP on TIM-5-10GM/GX, ODUki Path CTP, ODUk Client/
Path

This alarm is generated when the current BER value exceeds the predefined threshold value.
■ Improper autodiscovery attenuation level
■ Improper input power level to the line module
Clearing Procedure


FAC0318
AIS-ODU
Alarm Indication Signal - ODU

■ Applicable Facilities - ODUk Client CTP, ODUki Client CTP, ODUkT Client CTP

This alarm is generated by the ODUk Client termination point on TIM-5-10GM/GX,TIM-1-100G and
TIM-1-40G.
Clearing Procedure


Alarms 1-97
FAC0319
BDI-ODU
Backward Defect Indication - ODU

■ Severity - Not Reported (user customizable)
■ Applicable Facilities - ODUk Client CTP, ODUki Client CTP, ODUkT Client CTP

This alarm is generated by the network element on TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G.
Clearing Procedure


FAC0320
OCI-ODU
Open Connection Indication - ODU

■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, ODUkT Client CTP

This alarm is generated by ODU Client CTP, ODUi Client CTP, ODUkT Client CTP on TIM-5-10GM/GX,
TIM-1-100G and TIM-1-40G.
The alarm is generated when the ODU client in the upstream node has not been cross-connected.
■ Unprovisioned or deleted cross-connect on the upstream equipment
Clearing Procedure


Alarms 1-99
FAC0321
LCK-ODU
Locked Indication - ODU

■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, ODUkT Client CTP
Note: For detailed information about alarm type, severity, SA/NSA and direction for each
managed object of this alarm, refer to Table “Default Alarm Settings for each MO Type“.

This alarm is generated by ODU Client CTP, ODUi Client CTP, ODUkT Client CTP on TIM-5-10GM/GX,
The alarm is generated when the user has administratively locked the ODU entity.
Clearing Procedure


FAC0322
DE-ENCAP-AIS-ODU
De-encapsulated Alarm Indication Signal - ODU

■ Applicable Facilities - ODU Client CTP, ODUi Client CTP

This alarm is raised when the client equipment receives an AIS from the upstream network element.
■ A problem in the client network before the signal enters the Infinera network
■ AIS received from the client network at Infinera equipment ingress
Clearing Procedure


Alarms 1-101
FAC0323
DE-ENCAP-BDI-ODU
De-encapsulated Backward Defect Indication - ODU


This alarm is raised at a downstream node when an upstream node signals a signal failure in its receive
direction towards the downstream node.
■ A unidrectional fault between a pair of nodes
■ A BDI received from a client network
Clearing Procedure


FAC0324
DE-ENCAP-OCI-ODU
De-encapsulated Open Connection Indication - ODU


This alarm is raised when the upstream network element receives an OCI from the client equipment.
■ A problem in the missing or deleted cross-connection on that client facility
■ OCI received from the client network
Clearing Procedure


Alarms 1-103
FAC0325
DE-ENCAP-LCK-ODU
De-encapsulated Locked Indication - ODU


raised when the upstream network element receives an LCK from the client equipment.
■ A problem in the ODU client that has been administratively locked
■ LCK received from the client network
Clearing Procedure


FAC0332
RX-TIM
Receive Trace Identifier Mismatch

■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, ODUkT Client CTP, OTU Client CTP,
OTUki CTP, OTUCni CTP, SCH CTP, Digital Wrapper CTP

This alarm is generated by the ODUk Client termination point and the OTU Client termination point on
TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G when the terminal side receives TTI which does not match
the expected TTI.
Clearing Procedure
1. Ensure TIM monitoring mode is enabled.
2. Ensure TTI is configured correctly on both end points with the expected SAPI (SAPI/DAPI).

Alarms 1-105
FAC0335
LTC
Loss of Tandem Connection
■ Alarm - Facility
■ Severity - Event (user customizable)
■ Applicable Facilities - ODUkT Client CTP

This alarm is generated against specific/separate TCM object instances after the detection of the Loss of
Tandem Connection. This is caused when one side of a tandem connection facility is provisioned for
monitoring and does not receive an 'in use' signal on that tandem layer.
Clearing Procedure
■ Make sure that the TCM signal being transmitted by the Client side

FAC0361
MIS-CONN
Inter-module mis-connection

■ Applicable Facilities - TRIBPTP

This alarm is generated when the provisioned neighbor and the discovered neighbor do not match. This
alarm is valid only for TAM-2-10GT.
Clearing Procedure
One of the following steps can be used to clear the alarm condition:
■ Ensure that the fiber connection is correct
■ Change the provisioned neighbor

Alarms 1-107
FAC0364
FAC-PRBS-GEN
Facility PRBS generation activated

■ Applicable Facilities: ODUk Client/CTP, ODUki CTP, OTUCLIENTCTP

This alarm is generated when the PRBS generation is enabled in the receive direction.
Clearing Procedure
■ Disable the PRBS generation in the receive direction

FAC0365
TERM-PRBS-GEN
Terminal PRBS generation activated

■ Applicable Facilities - ODUk Client/CTP, OTUCLIENTCTP, ODUki CTP

This alarm is generated by OTU Client termination point when the PRBS generation is enabled in the
transmit direction.
Clearing Procedure
■ Disable PRBS generation in the transmit direction

Alarms 1-109
FAC0366
FAC-PRBS-OOS
Facility PRBS out of Sync

■ Applicable Facilities: ODUki CTP, ODUk Client/CTP, OTUCLIENTCTP

This alarm is generated by the ODUki CTP, ODUk Client/CTP, OTUCLIENTCTP on TIM-5-10GM/GX,
This alarm is generated when the line module has detected that the received PRBS pattern is out of
synch on the OTU Client termination point.
Clearing Procedure
1. Ensure that the PRBS setup is correct.

2. Ensure that any SNC associated with the two endpoints is setup correctly.

FAC0367
TERM-PRBS-OOS
Terminal PRBS Out of Sync

■ Applicable Facilities - ODUki CTP, ODUk Client/CTP, OTUCLIENTCTP

This alarm is generated by the ODUki CTP, ODUk Client/CTP, OTUCLIENTCTP on TIM-5-10GM/GX,
This alarm is generated when the line module has detected that the transmitted PRBS pattern is out of
synch with the OTU Client Termination Point.
Clearing Procedure
1. Ensure that the PRBS setup is correct.

2. Ensure that any SNC associated with the two endpoints is setup correctly.

Alarms 1-111
FAC0369
LS-ACTIVE
Laser Shutdown Active - ALS

■ Applicable Facilities - OTSPTP, TribPTP

This alarm is generated when the ALS condition is active. This is raised against the network element on
its OTSPTP whose transmit EDFA is shutdown down for eye safety. It implies that the system has
detected a condition on the line that is unsafe in the transmit direction for this EDFA, such as a uni-
directional or bi-direction fiber break.
Clearing Procedure
■ Check for faults between this node and the downstream node. Faults can be Optical Loss Of Signal
(OLOS) or LOF

FAC0370
LS-ACTIVE
Laser Shutdown Active

■ Applicable Facilities - TRIBPTP

This alarm is raised when the user has enabled the ALS feature by using the management interface
command.
Clearing Procedure
■ Check for faults between this node and the downstream node. Faults can be Optical Loss Of Signal
(OLOS) or LOF

Alarms 1-113
FAC0371
CFGMSMT
Configuration Mismatch

■ Applicable Facilities - OAM

The adjacent OAM operating mode is not configured to SLTE-MODE1.
Clearing Procedure
■ Make sure both the OAMs in the OTC have the same operating mode

FAC0372
OCH-MSMT
Optical Channel (OCH) Mismatch

■ Applicable Facilities - LMOCHPTP, CMMOCHPTP

This alarm is raised when the modulation format is different for the peer LM-80 channels at the other end
of the link. Specifically, this alarm is raised when there is a mismatch between the provisioned OCH
wavelength in the MCM database and the installed OCG wavelength for the LM-80’s optical channel port
(for example, the last known OCH wavelength to which the LM-80’s OCH port was tuned (if any)).
Clearing Procedure
1. Ensure that the modulation type matches the LM-80 OCH at the other end of the TE link.
2. Change the provisioned OCGx (x=1-16), OCHy (y=1-10), and modulation (QPSK, BPSK) values to
match the installed OCGx, OCHy, and modulation values or apply the currently provisioned values (for
OCGx, OCHy, and modulation) to the LM-80

Alarms 1-115
FAC0373
OL-OORH
OCH Loss Out of Range - High

■ Applicable Facilities - LMOCHPTP

This alarm is generated by LMOCHPTP.
This alarm is raised when the fiber loss or patch cable loss between LMOCHPTP Tx port and
CMMOCHPTP Rx port is out of range.
Clearing Procedure
If any one of the below steps clears the alarm then the clearing procedure is complete.
1. Ensure fiber is fully connected.
2. Inspect, clean and re-insert the fiber.
3. Replace bad fiber.

FAC0375
LOLM
Loss of Lane Marker Lock

■ Applicable Facilities - Gigabit Ethernet client CTP

This alarm is generated by the Gigabit Ethernet client CTP of TIM-1-100GE, TIM-1-40GE.
This alarm is raised when the system has detected that any of the physical coding sublayer (PCS) lanes
(4 for 40 GbE interfaces and/or 20 for 100 GbE interfaces) have not achieved an alignment marker lock
state (valid alignment markers received) in four consecutive iterations of receiving 16384 blocks of 66 bits
each while in a block sync lock state. The LOLM alarm is a composite alarm and is not available for
alignment marker lock on individual PCS lanes.
■ TOM equipment receiver intermittent failure
■ Faulty transmitter in the client equipment
Clearing Procedure

2. Check for alarms on the client equipment.

Alarms 1-117
FAC0376
DE-ENCAP-LOLM
De-Encapsulated Loss of Lane Marker

■ Applicable Facilities - GIGE ClientCTP

This alarm is generated by the GIGE Client Termination point of TIM-1-100GE, TIM-1-40GE.
This alarm is raised when a PCS alignment marker lock process operates independently on each PCS
lane. Each alignment marker lock process looks for two valid alignment markers 16384 66b blocks apart
to gain alignment marker lock. Once in lock, a PCS lane will go out of alignment marker lock if four
markers are received in a row that do not match the alignment marker that the PCS lane is currently
locked to.
Clearing Procedure


FAC0377
PLM
Payload Label Mismatch


This alarm is generated on the Client Trib at the ODU layer.
This alarm is raised when there is a mismatch between the provisioned cross-connect payload in the
source node and the destination node.
If the source cross-connect payload is ODU and destination cross-connect payload is something other
than ODU i.e. SONET, SDH, CLEAR CHANNEL, GbE LAN then Payload Mismatch will be reported in
both the source and destination nodes.
■ Different payloads provisioned manually at the either end of the circuit utilizing matching line side or
channel resources
Clearing Procedure
■ Manually restore the client Trib termination point payload type to that of its service type.
This requires the user to delete the cross-connect and rebuild the cross-connect in either of the
nodes (source node or destination node) to match the same payload.

Alarms 1-119
FAC0378
RF
Remote Fault

■ Severity - NR (User Customizable)
■ Applicable Facilities - GigE Client Trib Termination Point
Note: This alarm is raised on network elements running version R6.0.6, R8.0 and R8.1.3.

This alarm is reported by the GigE Client Trib Termination Port on TIM-5-10GM/GX, TIM-1-100GE,
TIM-1-40GE.
This alarm is raised when a remote fault is received at the ingress network element. This alarm is most
likely caused by:
Clearing Procedure


FAC0379
LF
Local Fault


This alarm is reported by the GigE Client Trib Termination Port on TIM-5-10GM/GX, TIM-1-100GE,
TIM-1-40GE.
This alarm is raised when a local fault is received at the ingress network element. This alarm is most likely
caused by:
Clearing Procedure


Alarms 1-121
FAC0380
DE-ENCAP-LF
DeEncap Local Fault


This alarm is generated by the GigE Client Trib Termination Port on TIM-5-10GM/GX, TIM-1-100GE,
TIM-1-40GE.
raised when the upstream network element receives an LF from the client equipment. This alarm is most
likely caused by:
Clearing Procedure
■ Check for problems in the client network.

FAC0381
DE-ENCAP-RF
DeEncap Remote Fault


This alarm is generated by the GigE Client Trib Termination Port on TIM-5-10GM/GX, TIM-1-100GE,
TIM-1-40GE.
This alarm is generated on the d-encapsulated client signal recovered from the network. This alarm is
raised when the upstream network element receives an RF from the client equipment. This alarm is most
likely caused by:
Clearing Procedure

Alarms 1-123
FAC0384
LFD
Loss of Frame Delineation

■ Applicable Facilities - GFP Client CTP

This alarm is generated by GFP Client termination point. This alarm is raised due to loss of GFP framing.
Clearing Procedure
■ Ensure the GFP provisioning at both ends of connection are compatible.

FAC0385
CSF
Client Signal Failure

■ Severity - Major / Not Reported
■ Applicable Facilities - GFP Client, ODUk Client/CTP, ODUki Client/CTP, OLDPSCH
■ Direction - Transmit, Receive (OLDPSCH)

This alarm is generated by the ODUk Client/CTP, ODUki Client/CTP on TIM-5-10GM/GX, TIM-1-100G,
OLDPSCH and TIM-1-40G.
This alarm condition originates from the ODUk TP which adapts the client signal (SONET/SDH/GbE/SCH)
into an ODUk frame.
Clearing Procedure
■ Clear the far-end client signal failure condition.

■ For OLDPSCH, ensure that client signal is present at circuit head-end node.

Alarms 1-125
FAC0386
UPI-MSMT
UPI Mismatch

■ Applicable Facilities - GFP Client CTP

This alarm is generated by the GFP Client termination point.
This alarm is raised when the received User Payload ID does not match with the user-provisioned
expected User Payload ID, during encapsulation mode.
Clearing Procedure

FAC0387
EXI-MSMT
EXI Mismatch

■ Applicable Facilities - GFP Client Termination Point

This alarm is generated by the GFP Client Termination Point
This alarm is raised when the received Extension Header ID does not match the user-provisioned
expected Extension Header ID.
Clearing Procedure

Alarms 1-127
FAC0388
MSIM
Multiplex Structure Identifier Mismatch

■ Applicable Facilities - ODUki CTP, ODUk Client/CTP

This alarm is generated by the ODUk Client Termination Port.
This alarm is generated when the detected/received TPN value on relevant TSs (the supporting OPU
tributary slots) for the ODUk does not match the expected TPN value (if TPN value matching is user-
enabled via setting of Expected TPN), or the detected/received ODTU-Type (or Occupied Not-Occupied
Indication) does not match the expected ODTU-Type (or expected Occupied | Not-Occupied Indication)
(pertaining to the ODUk’s type), or because the same TPN value is not detected on all TSs for the ODUk.
Clearing Procedure
1. Correct the (local) expected TPN value on desired TSs and/or the (local) expected ODU-Type.
2. Correct the (remote/far-end) transmitted TPN value on desired TSs and/or the (remote/far-end)
transmitted ODU-Type.

FAC0389
AIS-ODU
Alarm Indication Signal - ODU

■ Applicable Facilities - ODUi Client CTP, ODUk Client TP

This alarm is generated by the ODUk Client termination point on TIM-5-10GM/GX, TIM-1-100G and
TIM-1-40G.
■ AIS transmitted from the client network
Clearing Procedure
■ Ensure proper connectivity.
■ Check for problems in the network.

Alarms 1-129
FAC0390
BDI-ODU
Backward Defect Indication - ODU

■ Applicable Facilities - ODUi Client CTP, ODUk Client TP

■ A BDI transmitted from a client network
Clearing Procedure
■ Ensure proper connectivity.

FAC0391
OCI-ODU
Open Connection Indication - ODU

■ Applicable Facilities - ODUi Client CTP, ODUk

This alarm is generated by ODUi Client CTP, ODUk on TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G.
This alarm is raised when the upstream network element receives an OCI from the client equipment.
■ A problem in the missing or deleted cross-connection on that client facility
■ OCI transmitted from the client network
Clearing Procedure

Alarms 1-131
FAC0392
LCK-ODU
Locked Indication - ODU

■ Applicable Facilities - ODUi Client CTP, ODUk

■ AIS transmitted from the client network
Clearing Procedure

FAC0394
RX-EDFA-SPLIM
RX EDFA Input Power Exceeded its limit

■ SA/NSA - NSA (Non - Service Affecting)
■ Applicable Facilities - DLM OCG PTP, OFX,SCGPTP, OLM OCG PTP, XTOCGPTP, XTSCGPTP

This alarm is generated by the DLM OCG PTP, OFXSCGPTP and OLM OCG PTP.
This alarm is raised when the RX EDFA input power (Pin) exceeds its high threshold.
Clearing Procedure
■ Check for auto clearence as the system automatically adjusts the RX EDFA gain
■ Check for a manual adjustments to cause RX EPDA gain or Pin fall below its high threshold

Alarms 1-133
FAC0396
REM-MOD-MSMT
Remote Equipment OCH Modulation Mismatch

■ Applicable Facilities - OCHCTP

This alarm is generated by the OCHCTP.
This alarm is raised when the remote equipment OCH has different modulation format than the local end.
Clearing Procedure
Re-provision local or remote OCHCTP(s) such that they have same modulation format including lane
shuffling and channel grouping mode configuration.

FAC0397
OSC-MIS-CONN
OSC Inter-module misconnection

■ Applicable Facilities - OSCCTP

This alarm is generated by the OSCCTP.
This alarm is raised with a detection of light on the receive interface of OSC port on the pre-amplifier
when the pre-amp is connected to a BMM2C. The OSC Rx port of a pre-amplifier connected to the
receive port of the BMM2C is not expected to be connected. Only the Tx port of the pre-amplifier is to be
connected to the OSC port of the BMM2C.
Clearing Procedure
Remove the connected fiber on the receive interface of the OSC port.

Alarms 1-135
FAC0398
DE-ENCAP-LOA
De-Encapsulated Loss of Alignment

■ Applicable Facilities - GbE Client CTP

This alarm is generated by the GbE Client CTP.
This alarm is raised when the system has detected one or more of the constituent members of virtual
concatenation group (VCG) or GigE Client CTP of TIM-1-100GE and TIM-1-40GE are out of alignment.
One or more of the members of the VCG or GigE Client CTP are not able to achieve performance
threshold for the skew limit budget (skew limit is 5.7 microseconds)
Clearing Procedure
Ensure all members of the VCG or GigE Client CTP are able to achieve performance threshold for the
skew limit budget.

FAC0399
LOFLOM
Loss of Frame or Loss of Multi-frame

■ SA/NSA - SA
■ Applicable Facilities - ODUki

This alarm is generated by the ODUKi on TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G.
This alarm is generated when the TIM-5-10GM/GX is unable to lock on to the frames of the ODUk and
ODUki CTPs signal received from the far end.
■ Hardware faults in the channel data path of the ODUki in this network element
Clearing Procedure

2. Check for equipment failure alarms reported by the ODUki in the upstream digital network element.
3. Check for equipment failure alarms reported by the ODUki in this network element.

Alarms 1-137
FAC0400
LOFLOM
Loss of Frame or Loss of Multiframe

■ SA/NSA - SA
■ Applicable Facilities - ODUk Client CTP

This alarm is generated by the ODUk Client CTP on the TIM-5-10GM/GX.
This alarm is generated when the TIM-5-10GM/GX is unable to lock on to the frames of the ODUk Client
CTP signal in transmit direction.
■ Hardware faults in the channel data path of the ODUk Client CTP in this network element
Clearing Procedure

2. Check for equipment failure alarms reported by the ODUk Client CTP in the upstream digital network
element.
3. Check for equipment failure alarms reported by the ODUk Client CTP in this network element.

FAC0401
CSF
Client Signal Failure

■ Severity - Major / Not Reported
■ Applicable Facilities - ODUk client, ODUk CTP, ODUki Client, ODUki CTP

This alarm is generated by the ODUk Client/CTP, ODUki Client/CTP on TIM-5-10GM/GX, TIM-1-100G
and TIM-1-40G.
This alarm is raised due to the loss of Client Signal at ingress into the network.
Clearing Procedure
■ Clear the far-end client signal failure condition.

Alarms 1-139
FAC0402
SD
Signal Degraded

■ Applicable Facilities - ODUk Client, OTU Client on TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G

This alarm is generated when the current BER value exceeds the predefined threshold value.
Clearing Procedure


FAC0407
LOMF
Loss of Multi-frame


This alarm is generated by the OTU Client CTP on TIM-5-10GM/GX, TIM-1-100G and TIM-1-40G.
This alarm is generated when the OTU layer's Multi-frame Alignment Signal overhead is in a persistent
out-of-multi-frame state for at least 3 mili seconds as a part of a multi-frame alignment procedure. This
alarm is most likely caused by:
■ Hardware defect on the equipment (local/remote)
■ A problem in the network
Clearing Procedure

2. Check for symptoms of a hardware defect such as equipment fault conditions and historical
performance statistics for the OTU layer.

Alarms 1-141
FAC0408
LOFLANE
Loss of Frame - Logical Lane

■ Applicable Facilities - OTU3, OTU3e1, OTU3e2 and OTU4 Client CTP

This alarm is generated by the OTU3, OTU3e1, OTU3e2 and OTU4 Client CTP.
■ Hardware faults in the channel data path of the line module and/or LM-80s in this network element
Clearing Procedure

2. Check for equipment failure alarms reported by the line module and/or LM-80s in the upstream digital
network element.
3. Check for equipment failure alarms reported by the line module and/or LM-80s in this network
element.

FAC0409
LOOMFI
Loss of OPU Multi-Frame Identifier

■ Applicable Facilities - ODU4 Client CTP

This alarm is raised by the TIM-1-100GX when the OPU4 Multi-frame Identifier overhead (OH) received is
not in sync and contiguously increments for consecutive 3 ms.
This alarm is most likely caused by
■ A noisy received signal
■ The third party Customer Premise Equipment (CPE) connected to TIM-1-100GX is not generating a
stable OPU4 Multi-frame Identifier overhead (OH).
Clearing Procedure
This fault is cleared if TIM-1-100GX receives OPU-4 OMFI OH in sync (contiguous increments) for two
frames
1. Ensure the channel is noise free

2. Ensure the third party Customer Premise Equipment (CPE) is generating a stable OPU4 Multi-frame
Identifier overhead (OH).
3. Contact the Technical Assistance Center (TAC). See for contact details.

Alarms 1-143
FAC0410
LOL
Loss of Lane Alignment

■ Applicable Facilities - OTU3, OTU3e1, OTU3e2 and OTU4 Client CTP

This alarm is generated by the OTU3, OTU3e1, OTU3e2 and OTU4 Client CTP.
This alarm is raised when the system has detected one or more of the constituent members OTU Client
CTP are out of alignment.
Clearing Procedure
■ Ensure all OTU Client CTP are able to achieve performance threshold for the skew limit budget.

FAC0417
AIS-ODU-iPATH
Alarm Indication Signal -ODU-IPATH

■ Applicable Facilities - ODU

This alarm is generated by the line side of ODU on TIM-5-10GM/GX.
■ In case of a problem in the Infinera network
■ In case of switching between restorable and revertive-restorable SNC's
Clearing Procedure

2. Check for problems in Infinera network.

Alarms 1-145
FAC0418
BDI-ODU-iPATH
Backward Defect Indication - ODU-IPATH

■ Applicable Facilities - ODU

This alarm is generated by the line side of ODU.
■ In case of a problem in the Infinera network
■ In case of switching between restorable and revertive-restorable SNC's
Clearing Procedure


FAC0419
REM-PORT-FEC-MSMT
Remote Eqpt FEC Type Mismatch

■ Applicable Facilities - OLM2 OCG Port, OFXSCGPTP, OLM OCG Port, XTOCGPTP, XTSCGPTP

This alarm is generated by the OLM2 OCG Port, OFXSCGPTP, OLM OCG Port.
This alarm is generated when the remote line module has a different FEC type as compared with the local
line module.
Clearing Procedure
1. Re-connect line modules with the same FEC type on both ends.

Alarms 1-147
FAC0420
REM-PORT-ENCODING-MODE-MSMT
Remote Eqpt Encoding Mode Mismatch

■ Applicable Facilities - OCGPTP, XTOCGPTP, XTSCGPTP, OFXSCGPTP

This alarm is generated by the OCGPTP.
This alarm is generated when the encoding mode on the remote end PTP is different than the local.
Clearing Procedure
■ Re-configure local or remote OCGPTP such that the encoding modes on remote and local ends
match.

FAC0421
PMD-OORH
PMD Out of Range High

■ Applicable Facilities - OCHCTP, CarrierCTP

This alarm is generated by the OCHCTP.
This alarm is generated when the measured Polarization Mode Dispersion (PMD) value for optical carrier
crosses above the user defined threshold.
Clearing Procedure
■ This alarm is cleared when the measured PMD value for optical carrier crosses below the user
defined threshold.

Alarms 1-149
FAC0422
PRE-FEC-Q-SIGNAL-DEGRADE (PRE-FEC-BER-SIGNAL-DEGRADE)
Pre-FEC-Q value Out of range low

■ Applicable Facilities - OCHCTP, CarrierCTP

This alarm is generated by the OCHCTP on AOLM/AOLX/SOLM/SOLX/AOLM2/AOLX2/SOLM2/SOLX2.
This alarm is generated when at least one of the following conditions is attained:
■ the measured Pre-FEC-Q value for optical carrier goes below the user defined threshold.
■ the measured Pre-FEC-BER value for optical carrier exceeds the user defined threshold.
Clearing Procedure
■ This alarm is cleared automatically when the measured Pre-FEC-Q value for the optical carrier
crosses the user defined threshold.
■ This alarm is cleared by configuring a PreFecQSigDegThreshold value that is below the
measured Pre-FEC-Q value.

FAC0423
REM-SCH-PARAMETERS-MSMT
Remote Equipment SCH parameter Mismatch

■ Applicable Facilities - SCHCTP

This alarm is generated by the SCHCTP.
This alarm is generated due to more parameters included for Remote Equipment SCH like Super-
Channel Number, Modulation, Encoding Mode, CarrierGroupMode, OTNContainerRepresentation than
the local.
Clearing Procedure
Re-configure the same parameters on both local and remote SCH CTPs such that they have same set of
parameters like Super-Channel Number, Modulation, Encoding Mode, CarrierGroupMode,
OTNContainerRepresentation.

Alarms 1-151
FAC0424
MISCON
Client Equipment Misconnection


This alarm is generated by the SCHCTP.
This alarm is raised when one or more of the following conditions are met.
■ Channel-plan-type in O-XCONN is not supported by provisioned/pre-provisioned AOLM/AOFM
■ Super Channel for O-XCONN is not supported by connected LM (outside the tunable range of LM)
■ Super Channel chosen for O-XCONN is supported by LM but the specific provisioned super
channel on LM does not match with the O-XCONN super channel
■ When the modulation of the LM is not the same as indicated by the OEL.
■ When the spectrum type provisioned on the LM is different than the one indicated by the OEL.
■ When the equipment type+reach (indicated by the CTYPE) mismatches with the provisioned LM
FRU and the CTYPE is not provisioned with the compatible CTYPE list.
Clearing Procedure
The alarm is cleared by matching the properties between AOFM and the O-XCONN provisioning.

FAC0425
OPT-TOO-LOW
Super Channel Optical Power Transmitted Too Low

■ Applicable Facilities - FRM Line side SCHCTP
■ Location - Near End

This alarm is generated by the FRM Line side SCHCTP.
When DAMP determines the carrier count as 0 for the super channels and triggers to 2.5/10 sec, this
alarm is raised as the DAMP marks super channels as inactive.
Clearing Procedure
■ This alarm is cleared when DAMP determines the super channel as active.

Alarms 1-153
FAC0426
FDI-P
Forward Defect Indication - Payload

■ Applicable Facilities - OLDPSCH

This alarm is generated by the OLDPSCH.
This alarm is reported when the upstream node detects OPT-TOO-LOW (Tx) on SCHCTP due to a
datapath failure.
Clearing Procedure
■ Ensure that the upstream node clears OPT-TOO-LOW (Tx) on SCHCTP and is functioning
properly.

FAC0427
FDI-O
Forward Defect Indication - Overhead


This alarm is raised when FDI-O bit is set under OSC failure scenarios by peer node.
Clearing Procedure
■ Ensure that the upstream OSC is functioning properly.

Alarms 1-155
FAC0428
OCI
Open Connection Indication


This alarm is raised when there is no SCH XCON configured on the peer node.
Clearing Procedure
■ Ensure that the XCON is configured properly at upstream node(s).

FAC0429
BDI-O
Backward Defect Indication - Overhead

■ Applicable Facilities - OTSPTP, Band CTP

This alarm is generated by the OTSPTP and Band CTP.
This alarm is reported when there is a OSC failure in the downstream direction.
Clearing Procedure
■ Ensure OSC is received properly on the far end node.

Alarms 1-157
FAC0430
PMI
Payload Missing Indication

■ Applicable Facilities - OTSPTP, Band CTP

This alarm is generated by the OTSPTP and Band CTP.
OTS-PMI: This alarm is generated by IAM (OTS) when the band signal is absent and can be raised due
to one of the following reasons:
■ Super channel cross-connects are not present
■ Failures in FRM
■ Fiber cut between FRM-IAM in add-drop nodes or IAM-IAM in Optical Amplifiers
■ FRM is locked
■ IAM is under Automatic Laser Shutdown (ALS) condition
OMS-PMI: This alarm is generated by IAM (OMS) when there are no super channel cross-connects
present.
Clearing Procedure
■ This alarm is cleared in both OTS and OMS layers when the above mentioned causes are fixed
appropriately.

FAC0431
MUX-OPR-OORL
OPR in the Mux direction Out of Range - Low

■ Applicable Facilities - FRM Line side SCH CTP

This alarm is generated by the FRM Line side SCH CTP.
This alarm is raised when the OPM received or detected in the mux direction, is below the Infinera
defined threshold.
Clearing Procedure
1. When the OPM detects input power within normal operating range.
2. Ensure proper fiber connectivity with upstream equipment.

Alarms 1-159
FAC0432
IDLER-SEPARATION-OOR
Idler Channel Separation Out of Range

■ Applicable Facilities - SCM-2

This alarm is generated by the SCM-2.
This alarm is raised when the offset difference between both the idlers on the SCM-2 is less than 10 GHz.
This can happen under either of the following conditions:
■ Hardware degrade-Provisioned idler channel offsets do not match with hardware read values and
are drifting towards each other.
■ Provisioning error-The SCM-2 was provisioned with defaults or values on the idlers that are not
conformant to the 10 GHz separation. This can happen only over an NE upgrade.
Clearing Procedure
1. Ensure that the Idler Channel Numbers should be the same and the Idler frequency offset difference
between the two idler CTPs is at least 10 GHz.
2. Lock and unlock any Idler CTP.

FAC0433
SBS-OFF
SBS Suppression Not Enabled

■ Applicable Facilities - SCM IDLERPTP

This alarm is generated by the SCM IDLERPTP.
This alarm is raised in either of the below mentioned conditions:
■ SBS Mode is set to OFF
■ SBS Mode is ON and the SBS frequency width is set to 0 GHz
Clearing Procedure
1. Ensure that SBS Mode is set to ON.

2. Ensure that the SBS frequency width set to a value other than 0.
Note: This procedure can be performed only by field engineer and hence contact the Technical
Assistance Center (TAC). See for contact details.

Alarms 1-161
FAC0434
INSUFFICIENT-OUTPUT-PWR
Insufficient Output Power

■ Applicable Facilities - IAM BANDCTP

This alarm is generated by the IAM BANDCTP.
This alarm is raised when the desired Target Output Power is not achieved.
Clearing Procedure
1. Ensure that the Target Line Output Power is met.

2. Ensure that Input power is within the operating range.

FAC0435
OOS-AU
Service State Out Of Service-Autonomous

■ Applicable Facilities - GbE Client CTP

This Alarm is generated by the GbE Client CTP if:
■ The Service State Out-of-Service flag is enabled to report OOS-AU alarms and
■ Service state of the GbE client CTP transitions to Out-of-Service (OOS-AU) state or the client CTP
is already in OOS-AU state.
Clearing Procedure
1. Ensure the GbE Client CTP transitions to In Service state to clear this alarm.
2. Disable the Service State Out-of-Service flag to disable reporting and clear this alarm.

Alarms 1-163
FAC0436
ODUkPE-LAT-FAC-OORH
Facility ODUk Path Latency Out of Range - High


This alarm is generated when the facility ODUk Path latency is greater than the Infinera defined
threshold.
Clearing Procedure
1. Ensure service latency is within the specified threshold by adjusting the fiber length or threshold
values.
■ Change Latency Mode from Initiator to Responder or Disabled.
■ Delete the ODUk service.

FAC0437
ODUkPE-LAT-FAC-OORL
Facility ODUk Path Latency Out of Range - Low


This alarm is generated when the facility ODUk Path latency is lesser than the Infinera defined threshold.
Clearing Procedure
values.
■ Delete the ODUk service

Alarms 1-165
FAC0438
ODUkPE-LAT-TERM-OORH
Terminal ODUk Path Latency Out of Range - High


This alarm is generated when the terminal ODUk Path latency is greater than the Infinera defined
threshold.
Clearing Procedure
values.

FAC0439
ODUkPE-LAT-TERM-OORL
Terminal ODUk Path Latency Out of Range - Low


This alarm is generated when the terminal ODUk Path latency is lesser than the Infinera defined
threshold.
Clearing Procedure
values.

Alarms 1-167
FAC0440
ODUkPS-LAT-FAC-OORH
Facility ODUk Path Segment Latency Out of Range - High


This alarm is generated when the facility ODUk Path Segment latency is greater than the Infineradefined
threshold.
Clearing Procedure
values.

FAC0441
ODUkPS-LAT-FAC-OORL
Facility ODUk Path Segment Latency Out of Range - Low


This alarm is generated when the facility ODUk Path Segment latency is lesser than the Infinera defined
threshold.
Clearing Procedure
values.

Alarms 1-169
FAC0442
ODUkPS-LAT-TERM-OORH
Terminal ODUk Path Segment Latency Out of Range - High


This alarm is generated when the terminal ODUk Path Segment latency is greater than the Infinera
defined threshold.
Clearing Procedure
values.

FAC0443
ODUkPS-LAT-TERM-OORL
Terminal ODUk Path Segment Latency Out of Range - Low


This alarm is generated when the terminal ODUk Path Segment latency is lesser than the Infinera defined
threshold.
Clearing Procedure
values.

Alarms 1-171
FAC0445
LINK-DOWN
Loss of Ethernet Link

■ Applicable facilities - Ethernet Interface

This alarm is generated due to loss of Ethernet link occurring in the following conditions:
■ During an existing Tributary PTP OLOS condition
■ When the fiber connection is pulled out
■ During an existing equipment fault condition on the TOM
Clearing Procedure
1. When the Ethernet link is up again.

2. Check fiber connectivity and peer transmitter.

FAC0446
FAC-PRBS-PLM
Facility PRBS Payload Mismatch


This alarm is generated on HO-ODUk and LO-ODUj corresponding to a TIM-1-100GX in the following
cases:
■ If PRBS-MON is enabled, the Payload Type (PT(PSI[0])) of the ODUk/ODUj is expected to be
0XFE. This alarm is raised if the overhead value is not 0XFE.
■ If the peer network element does not source a valid PRBS signal
Clearing Procedure
1. Ensure the peer network element is sourcing a valid PRBS signal and the Payload Type (PT) byte
(PSI[0]) value is 0xFE.
2. If this problem persists, contact the Technical Assistance Center (TAC). See for contact details.

Alarms 1-173
FAC0447
TERM-PRBS-PLM
Facility PRBS Payload Mismatch


This alarm is generated on LO-ODUj corresponding to a TIM-1-100GX in the following cases:
■ If PRBS-MON is enabled, the Payload Type (PT(PSI[0])) of the ODUj is expected to be 0XFE. This
alarm is raised if the overhead value is not 0XFE.
■ If the peer network element does not source a valid PRBS signal
Clearing Procedure
1. Ensure the peer network element is sourcing a valid PRBS signal and the value of Payload Type (PT)
byte (PSI[0]) is 0xFE.

FAC0448
OCG-TYPE-MSMT
OCG Type Mismatch

■ Applicable Facilities - BMM OCG PTP

This alarm is generated when:
■ The system detects that one of the head-end BMM OCG in an L0 OPN application is configured in
Open Automated mode, while the tail-end BMM OCG is configured in Normal or Manual Mode
Clearing Procedure
Note:
■ Configure the same OCG Type on the head-end and tail-end BMM OCGs.

Alarms 1-175
FAC0449
OPR-TOO-LOW
Optical Power Received Too Low

■ SA/NSA - SA (Non-Service Affecting)

■ Optical power received in the Mux direction is too low for supporting the service.
Clearing Procedure
■ Check and clean the Fiber patch connection and upstream module operation.

FAC0450
OPR-TOO-HIGH
Optical Power Received Too High


■ Optical power received in the mux direction is too high for supporting the service.
Clearing Procedure
■ Check and clean the Fiber patch connection and upstream module operation.

Alarms 1-177
FAC0452
CCM-LOC
CCM Loss of Continuity

■ Applicable Facilities - MEP

This alarm is generated on MEP.
This alarm is generated if the MEP entity does not receive CCM PDUs from the peer MEP for K (3.25 <=
K <= 3.5) times the CCM interval.
Clearing Procedure
■ This alarm is cleared when at least one valid CCM message is received from remote MEP.
■ Associated RMEP(s) which are the cause of this alarm are manually deleted

FAC0453
CCM-UNEXP-LEVEL
CCM Unexpected MD Level


This alarm is generated by MEP.
This alarm is generated if the MEP entity receives CCM PDUs from the remote MEP with an MD Level
which is lesser than its own MD Level.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 CCM PDUs with invalid MD Level in K * received CCM
Period (where 3.25 <= K <= 3.5)

Alarms 1-179
FAC0454
CCM-MISMERGE
CCM Mismerge


This alarm is generated if the MEP entity receives CCM PDUs from the remote MEP with correct MD
Level but invalid MAID.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 CCM PDUs with correct MD Level and invalid MAID in
K * received CCM Period (where 3.25 <= K <= 3.5)

FAC0455
CCM-UNEXP-MEP
CCM Unexpected MEP


Level and MAID but unexpected MEPID or Remote MEP's ID is same as receiving MEP's ID.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 CCM PDUs with correct MD Level, MAID Level and
unexpected MEPID in K * received CCM Period (where 3.25 <= K <= 3.5)

Alarms 1-181
FAC0456
CCM-UNEXP-PERIOD
CCM Unexpected Period


Level, MAID and MEP ID but invalid transmission period.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 CCM PDUs with correct MD Level, MAID, MEPID and
invalid ransmission period in K * received CCM Period (where 3.25 <= K <= 3.5)

FAC0457
CCM-UNEXP-PRIO
CCM Unexpected Priority


Level, MAID and MEP ID but invalid Priority.
Clearing Procedure
■ Verify connectivity and remote MEP's CCM Priority.

Alarms 1-183
FAC0458
CCM-REM-MAC-ERR
CCM Remote MAC Error


Level, MAID, MEP ID and time period but Port or Interface Status indicating Service affecting fault on the
Remote MEP end.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 CCM PDUs with correct MD Level, MAID, MEPID,
Period and Port-Status-TLV or Interface-Status-TLV not indicating any remote faults in K * received
CCM Period (where 3.25 <= K <= 3.5)

FAC0459
ETH-RDI
Remote Defect Indication


Level, MAID, MEP ID and time period but with RDI bit set.
Clearing Procedure
■ This alarm is cleared when MEP receives valid CCM PDU with RDI bit unset.

Alarms 1-185
FAC0460
ETH-AIS
Alarm Indication Signal


This alarm is generated if the MEP entity receives AIS PDU(s) with the same MD Level and VLAN
Configuration as per the local MEP.
Clearing Procedure
■ This alarm is cleared when MEP receives 0 AIS PDUs in K * received AIS Period (where 3.25 <= K
<= 3.5)

FAC0461
VSI-FAIL
VSI Failure

■ Applicable Facilities - VSI

This alarm is generated by the VSI.
In a VPWS or VLAN Crossconnect VSI, this alarm is generated at the VSI when any of the supporting
have any fault or are operationally out of service due to any reason. In a VPLS VSI, this alarm is
generated on the VSI when all ACs and PWs endpoints associated with the VPLS VSI have fault or
operationally out of service due to any reason.
Clearing Procedure
■ Correct all reasons for endpoints being out of service.

Alarms 1-187
FAC0462
VSI-PARTIAL-FAIL
VPLS VSI

■ SA/NSA - NSA (Non service-Affecting)
■ Detailed Conditions - VSI-PARTIAL-FAIL
■ Direction - NA

This alarm is generated by the VSI when even a single endpoint associated with the VPLS VSI has a fault
or is operationally out of service due to any reason.
Clearing Procedure
■ Correct all reasons for endpoints being out of service.

FAC0463
MAC-FLAP
MAC Flap condition detected

■ Applicable Facilities - ACs, PWs

This alarm is generated on ACs and/or PWs.
This alarm is generated when the count of MAC Addresses being learned on different interfaces (i.e, ACs
and PWs) exceeds the configured threshold within the configured duration.
Clearing Procedure
■ Rectify any misconfiguration causing the MAC Flap, admin-lock the flapping interface(s) and re-
enable the interface(s).

Alarms 1-189
FAC0465
VSI-MAC-LIM-DNL-DNF
VSI MAC Limit Exceeded


This alarm is generated when the number of learned MAC addresses reaches the configured limit for the
VPLS VSI.
Clearing Procedure
■ The alarm is cleared when the number of learned MAC addresses either falls below the configured
limit for the VPLS VSI or the user configures a new value which is greater than the current number
of learned MAC addresses.

FAC0466
TIM-SCH
SCH TTI Mismatch

■ Applicable Facilities - XTSCGPTP

This alarm is raised on the XTSCGPTP
This alarm is generated when Expected SCH TTI and Received TTI from far-end SCH do not match.
Clearing Procedure
■ Rectify the TTI string at the remote-end to send TTI matching the expected value
■ Disable TTI by setting Expected TTI to “None”

Alarms 1-191
FAC0467
IntraSchCarrierRipple
Intra Super Channel Carrier Ripple

■ Applicable Facilities - Line SCHCTP
This alarm is generated when the carrier power difference cannot be compensated by the WSS in the
FRM.
This alarm is generated at the FRM-9D, FRM-4D and FRM-20X system ports (SCHPTP on FRM-9D/
FRM-4D/FRM-20X)in native mode.
Clearing Procedure
■ This alarm is cleared when Intra Superchannel Carrier ripple value is lesser than the Intra
Superchannel Carrier ripple threshold plus hysteresis.

FAC0468
ETH Client Signal Failure
Ethernet Client Signal Failure


This alarm is reported against MEP entity if it receives any ETH-CSF PDU.
Clearing Procedure
■ Verify upstream connectivity of the client

■ This alarm is cleared when MEP receives 0 CSF PDUs in K * received CSF Period (where 3.25<=
K <= 3.5) or it receives an ETH-CSF with C-DCI CSF type.

Alarms 1-193
FAC0469
OLDP VERSION MISMATCH

Version Mismatch With upstream/downstream Node
■ Applicable Facilities - OTSPTP
This alarm is generated if the peer span OSC OLDP version does not match with the local OLDP version
configured by software.
Note: This alarm is seen on upgrading to IQ NOS Release 16.2
Clearing Procedures
This alarm is cleared when Peer Span OSC OLDP version matches the local OLDP version configured by
software.
Note: During an outstanding OLDP Version mismatch condition, any release below IQ NOS R16.2
that communicates with a R16.2 Peer OSC, receives an invalid signal from the IQ NOS R16.2 node
leading to clearing of all outstanding OLDP alarms. This issue exists until the upgrade to IQ NOS
R16.2, when the OLDP version is also upgraded .

FAC0471
TIM-OCG
OCG TTI Mismatch

■ Applicable Facilities - XTOCGPTP

This alarm is generated by the XTOCGPTP.
This alarm is generated when the OCG TTI Received from far-end OCG termination point does not match
the expected TTI.
Clearing Procedure
■ Rectify TTI string at the remote-end to send TTI matching the expected value
■ Disable TTI by setting Expected TTI to "None"

Alarms 1-195
FAC0472
REACH-LTH-EX
Reach Lower threshold Exceeded

■ SA/NSA -NSA
■ Applicable Facilities - OCG

This alarm is a raised when the actual span is at 90% of the Infinera recommended threshold.
Clearing Procedure
■ Reduce the Span between the OCGs.

■ Contact the Technical Assistance Center.

FAC0473
REACH-UTH-EX
Reach Upper Threshold Exceeded

■ SA/NSA -SA
■ Applicable Facilities - OCG, XTOCGPTP, XTSCGPTP

This alarm is raised when the optical reach between the OCGs exceeds the Infinera recommended
threshold. The traffic is likely affected on the client ends affecting the service.
Clearing Procedure
■ Reduce the Span between the OCGs.

■ Contact Technical Assistance Center.

Alarms 1-197
PROT0003
LOCKOUTOFPR
Lockout of Protection

■ Applicable Facilities - SNGLTAMDSNCPPG, TRIBPTPYCABLEPG, Local SNC, Remote SNC,
Cross-connect, XOSNCPG

This alarm is generated in the following:
■ Single TAM Digital SNCP
■ Dual TAM Digital SNCP
■ SNCs and cross-connects that are part of a Shared Mesh Protection Group (SMPG)
This alarm is generated when a lockout of protection command has been executed for this
protection group (PG). Traffic cannot be switched to the protection unit until the lockout is cleared.
Clearing Procedure
■ Manually clear the lockout of protection request

PROT0004
LOCKOUTOFWK
Lockout of Working

■ Applicable Facilities - SNGLTAMDSNCPPG, TRIBPTPYCABLEPG, Local SNC, Remote SNC,
Cross-connect, XOSNCPG

This alarm is generated in the following:
■ Single TAM Digital SNCP
■ Dual TAM Digital SNCP
■ SNCs and cross-connects that are part of a Shared Mesh Protection Group (SMPG)
This alarm is generated when a lockout of the working command has been executed for this PG.
■ In case of Single TAM DSNCP and Dual TAM DSNCP, the traffic cannot be switched back to the
working line until the lockout is cleared.
■ In case of SNCs and cross-connects that are part of a Shared Mesh Protection Group (SMPG),
traffic cannot be switched to any line until the lockout is cleared.
Clearing Procedure
■ Manually clear the lockout request

Alarms 1-199
PROT0005
PROT-UNIT-ACTIVE
Protection Unit Active

■ Applicable Facilities - TRIBPTPYCABLEPG, SNGLTAMDSNCPPG, XOSNCPG

This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP.
This alarm is generated when the traffic is on the protection unit.
Clearing Procedure
■ Ensure that the working unit is fault free, then manually switch the traffic back to the working unit.
PROT0006
WKSWPR
Switched to Protection


This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP to indicate that, an
automatic switch to protection has been completed.
Clearing Procedure
■ Ensure that the working unit is fault free, then manually switch the traffic back to the working unit

PROT0007
MANWKSWPR
Manual Switch to Protection


This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP to indicate that a
manual switch to protection has been initiated by the user.
Clearing Procedure
■ Ensure that the working unit is fault free, then manually switch the traffic back to the working unit

Alarms 1-201
PROT0008
WKSWBK
Switched to Working


This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP to indicate that a switch
to working has been completed.
Clearing Procedure
■ None. To initiate a switch to protection, ensure that the protection unit is fault free, then manually
switch the traffic to the protection unit

PROT0009
MANWKSWBK
Manual Switch to Working


This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP to indicate that a
manual switch to working has been initiated by the user.
Clearing Procedure
■ None. To initiate a manual switch to protection, ensure that the protection unit is fault free, then
manually switch the traffic to the protection unit

Alarms 1-203
PROT0010
WTR
Wait to Revert


This alarm is generated in Single TAM Digital SNCP and Dual TAM Digital SNCP.
This alarm is generated when a wait to revert (WTR) is triggered on a revertive protection group (PG) for
this Digital SNCP.
Clearing Procedure
■ None.

PROT0011
FRCDWKSWPR
Forced Switch to Protection

■ Applicable Facilities - SMPG

This alarm is generated on Shared Mesh Protection Group (SMPG).
This alarm is generated when traffic switches from a healthy work path to protect path.s
Clearing Procedure
■ None.
PROT0012
FRCDWKSWBK
Forced Switch to Working

■ Applicable Facilities - SMPG

This alarm is generated on Shared Mesh Protection Group (SMPG).
This alarm is generated when traffic switches back from a protect path to a healthy work path.
Clearing Procedure
■ None. To initiate a forced switch to protection, ensure that the protection unit is fault free, then
forcefully switch the traffic to the protection unit.
Communication Alarms
Communication alarms are associated with faults which impact the communication between the modules
within the network element and between network elements. For example: No Communication with OSC
Neighbor and GMPLS neighbor down.

Alarms 1-205
COM0008
NTP-SERVER-LOSS
Configured NTP Server(s) Unreachable or of Low Quality


This alarm is generated by the network element object on the Node Controller chassis AID.
This alarm is generated when
■ At least one NTP instance is configured and the network element has not synchronized with any of
the configured NTP servers
■ Synch is achieved but with a server whose clock quality has fallen below stratum 5 level
The network element polls the NTP server every 16 seconds and performs an NTP synchronization
status check every 192 seconds. Upon configuration of a new NTP server, this timer is reset.
During each status check up to four retries are attempted. After four failed retries this alarm is
raised. However, the alarm is cleared once synchronization is detected.
The chassis level LED is not lit when this alarm is raised. However, this behavior can be changed
using the Alarm Severity Assignment Profile Settings window in GNM.
Clearing Procedure
1. Check the NTP servers configured and the connectivity between the network element and NTP server.
2. All configured NTP instances are disabled.
3. All the configured NTP instances are Administratively Locked
4. Any one of the configured NTP instances becomes operationally enabled again and starts providing
valid timing to the network element.

COM0012
DCN-ENET-LOLINK-CTRLRA
DCN Loss of Enet Link from Controller A


This alarm is generated by the XCM/MCM/IMM/OMM on the network element object.
This alarm is generated when the XCM in XTC-4 and XTC-10, MCM in slot 7A or OMM in slot 1A is
unable to communicate with the external network through the DCN link.
■ Failure of the DCN port on the MCMOMM/XCM
■ Failure of the Ethernet cable connected to the DCN port
Clearing Procedure
1. Check the Ethernet cable connectivity to the DCN A port.

2. Replace the Ethernet cable.
3. If the link is fine and the alarm persists, check for equipment alarms on the XCM/MCM/IMM/OMM.

Alarms 1-207
COM0013
DCN-ENET-LOLINK-CTRLRB
DCN Loss of Enet Link from Controller B


This alarm is generated by the XCM/MCM/IMM/OMM on the network element object.
This alarm is generated when the XCM in XTC-4 and XTC-10, MCM in slot 7B or the OMM in slot 1B is
unable to communicate with the external network through the DCN link.
■ Failure of the DCN port on the XCM/MCM/IMM/OMM
■ Failure of the Ethernet cable connected DCN port
Clearing Procedure
1. Check the Ethernet cable connectivity to the DCN B port.


COM0014
AUX-ENET-LOLINK-CTRLRA
AUX Loss of Enet Link from Controller A


This alarm is generated by the AUX port on the network element object.
This alarm is generated when the XCM in XTC-4 and XTC-10, MCM in slot 7A or the OMM is slot 1A is
unable to communicate with the external network through the AUX link.
■ Improper AUX port configuration
■ Failure in the AUX link
Clearing Procedure
1. Check the Ethernet cable connectivity to the AUX A port.


Alarms 1-209
COM0015
AUX-ENET-LOLINK-CTRLRB
AUX Loss of Enet Link from Controller B


This alarm is generated by the AUX port on the network element object.
This alarm is generated when the XCM in XTC-4 and XTC-10, MCM in slot 7B or the OMM in slot 1B is
unable to communicate with the external network through the AUX link.
■ Improper AUX port configuration
■ Failure in the AUX link
Clearing Procedure
1. Check the Ethernet cable connectivity to the DCN A port.


COM0017
NCT1-ENET-LOLINK-CTRLRA
NCT1 Loss of Enet Link from Controller A


This alarm is generated by the Nodal Control and Timing (NCT) port.
This alarm is generated when the chassis has detected a NCT Ethernet loss of link. By default, this alarm
is reported if the Ethernet cables are not connected to any other chassis.
■ Removal of Ethernet cable from slot NCT1 A
■ Faulty Ethernet cable
■ Removal of MCM from slot 7A of a chassis that has a Ethernet cable connected to this NCT port
■ Faulty XCM/MCM/IMM/OMM
Clearing Procedure
1. Check the Ethernet cable connectivity to the NCT1 A port.

3. Check for equipment alarms on the MCM.

Alarms 1-211
COM0018
NCT1-ENET-LOLINK-CTRLRB
NCT1 Loss of Enet Link from Controller B


This alarm is generated on the NCT port.
■ Removal of Ethernet cable from slot NCT1 B
■ Removal of MCM from slot 7B of a chassis that has a Ethernet cable connected to this NCT port
Clearing Procedure
1. Check the Ethernet cable connectivity to the NCT1 B port.

3. Check for equipment alarms on the MCM in slot 7B.

COM0019
NCT2-ENET-LOLINK-CTRLRA
NCT2 Loss of Enet Link from Controller A


■ Removal of Ethernet cable from slot NCT2 A
■ Removal of MCM from slot 7A of a chassis that has a Ethernet cable connected to this NCT port
Clearing Procedure
1. Check the Ethernet cable connectivity to the NCT2 A port.

3. Check for equipment alarms on the MCM in slot 7A.

Alarms 1-213
COM0020
NCT2-ENET-LOLINK-CTRLRB
NCT2 Loss of Enet Link from Controller B


■ Removal of Ethernet cable from slot NCT2 B
■ Removal of MCM from slot 7B of a chassis that has a Ethernet cable connected to this NCT port
Clearing Procedure
1. Check the Ethernet cable connectivity to the NCT2 B port.

3. Check for equipment alarms on the MCM in slot 7B.

COM0027
NW-MISCONFIG-DUP-MENAME
Node with Duplicate Name Found in Routing Domain


This alarm is generated by the network elements.
This alarm is generated when this network element detects another network element with the same name
within the same signaling domain.
■ Mis-configuration
Clearing Procedure
■ Change the name of the network elements in conflict so that each network element has a unique
name

Alarms 1-215
COM0028
NW-MISCONFIG-DUP-RID
Node with Duplicate Generalized Multi Protocol Label Switching (GMPLS) Router ID Found in Routing Domain


This alarm is generated by the network element when it detects that this network element shares the
same GMPLS Router ID as some other network element(s) within the GMPLS routing domain.
Clearing Procedure
■ Reconfigure one of the network elements in conflict, to give unique router IDs in the GMPLS routing
domain

COM0029
NW-MISCONFIG-DUP-NBR
Neighbors’ Router ID in Conflict with Each Other


This alarm is generated by the network element when it has detected that two (or more) neighbors in the
GMPLS routing domain share the same router ID.
Clearing Procedure
■ Reconfigure the network elements in conflict, to give unique router IDs in the signaling domain
Note: The alarm is cleared one hour after the router ID is reconfigured.

Alarms 1-217
COM0030
GCC-GMPLS-NBR-DOWN/GMPLS-NBR-DOWN
GMPLS Neighbor Adjacency Lost


This alarm is generated by the OSC along which the neighbor’s adjacency is lost.
This alarm is generated when this network element loses control path to the adjacent network element.
■ Invalid IP configuration between the network element and it’s neighbor
■ Reboot of the XCM/MCM/IMM/OMM of the adjacent network element
Clearing Procedure
1. Provision a valid IP address between the network element and the neighbor.
2. Ensure GMPLS signaling is enabled on both ends of the link.

COM0031
OSC-IPADDR-SUBNET-MISMATCH
Neighbor OSC IP Address in Different Subnet


This alarm is generated by the OSC along which the neighbor is found to be in a different subnet.
This alarm is generated when the discovered remote OSC IP address is in a different subnet.
■ Incorrect fiber connection between the adjacent network elements
■ IP address configuration is invalid
Clearing Procedure
1. Ensure the current network element and the neighbor are in the same subnet.
3. Check with the network administrator to ensure the configuration is valid.

Alarms 1-219
COM0032
GCC-IPADDR-DUPLICATE/OSC-IPADDR-DUPLICATE
Node with Duplicate OSC/GCC IP Address Found in Routing Domain


This alarm is generated by the network element when it has detected that it shares the OSC IP Address
or the GCC IP Address with two (or more) network elements within the same GMPLS signaling domain.
This alarm could take up to one hour to be raised.
This alarm is caused by:
■ Mis-configuration of OSC IP Address or the GCC IP Address for a network element within the
GMPLS signaling domain in case of OSC-IPADDR-DUPLICATE or GCC-IPADDR-DUPLICATE
respectively
Clearing Procedure
■ Reconfigure the network elements to have a unique OSC IP Address or the GCC IP Address within
a single GMPLS signaling domain in case of OSC-IPADDR-DUPLICATE or GCC-IPADDR-
DUPLICATE respectively

COM0033
NBRS-OSC-IPADDR-IN-CONFLICT/NBRS-GCC-IPADDR-IN-CONFLICT
Neighbors’ OSC/GCC IP Address in Conflict with Each Other


This alarm is generated by the network element when it has detected that two (or more) network
elements within the same GMPLS signaling domain share the same OSC IP address.
Or
This alarm is generated by the network element when it has detected that two (or more) network
elements within the same GMPLS signaling domain share the same GMPLS Control Channel IP address.
Clearing Procedure
■ In case of NBRS-OSC-IPADDR-IN-CONFLICT alarm, reconfigure the network elements to have a

unique OSC IP address within a single GMPLS signaling domain
■ In case of NBRS-GCC-IPADDR-IN-CONFLICT alarm, reconfigure the network elements to have a
unique OSC IP address within a single GMPLS signaling domain

Alarms 1-221
COM0034
INTER-OAM-MIS-CONN
Inter-OAM or ORM mis-connection

■ Detailed Conditions - TX-OSC-OLOS

This alarm is generated by the OSC layer on the OAM/ORM.
This alarm is generated when the OSC optical patch cord between the two OAMs/ORMs or between and
OAM and ORM fails.
■ Loosely connected optical patch cord
■ Bent or damaged optical patch cord
Clearing Procedure
1. If the optical patch cord is loosely connected, re-connect the optical patch cord.
2. Replace the optical patch cord.

COM0035
LOC
Loss of Communication - OSC

■ Detailed Conditions - LOSS-OF-COMM

This alarm is generated by the OSC layer on the BMM/OAM/ORM.
This alarm is generated when the control path between the upstream network element and this network
element has failed.
■ Low OSC receive power
■ OSC digital transmitter failure in the upstream network element
■ OSC receives LOF due to laser transmitter failure in the upstream network element
■ Span Loss out of range
Clearing Procedure
1. Check the OPR on this port.

2. Ensure the span loss for this span is within range.
3. Check for the equipment failure in the BMM/OAM/ORM/RAM in the upstream network element.

Alarms 1-223
COM0038
SNCFAIL
Signaled SNC Failure


This alarm is generated by the remote and local SNC termination point.
This alarm is generated by the SNC termination point when it has detected any of the following failures
(regardless of whether these failures are configured to be reported or masked):
■ On the associated Trib DTF Path supporting this SNC:
□ AIS
□ BDI
□ POST-FEC-BER
■ On the associated client or trib side termination point supporting this SNC:
□ Trib OLOS
□ Client LOS
□ Client LOF
□ Client AIS-L
□ Client RFI
The chassis level LED is not lit by default when this alarm is raised. However, this behavior
can be changed using the Alarm Severity Assignment Profile Settings window in GNM.
Clearing Procedure
■ This alarm is cleared when the low-level failures are cleared

COM0039
SNCSETUPFAIL
Signaled SNC Setup Failure


This alarm is generated by the local SNC.
This alarm is generated when the user has configured an SNC but the network element failed to setup.
■ Lack of resources (for example, bandwidth) in the network
Clearing Procedure
1. Ensure that sufficient resources are available throughout the network to allow setup of this SNC.
2. Check the destination endpoint for proper configuration, and service type.
3. If using routing constraints, ensure the route is valid.

Alarms 1-225
COM0040
TXFR-PRI-FAIL
File Transfer Failed - Primary server


This alarm is generated when the FTP/SCP transfer of a file to the primary FTP/SCP server fails.
■ Incorrect FTP/SCP server IP address
■ Incorrect user name / password
■ Unavailable disk space
■ Failure in connectivity to the server
Clearing Procedure
1. Ensure the primary FTP/SCP server’s IP address is correct.

2. Check firewall and router settings.
3. Ensure the user name/password used to access the primary server is correct.
4. Check the disk space available on the primary server.

COM0041
TXFR-PRI-FAIL-SNA
File Transfer Failed - Secondary not configured


This alarm is generated when the FTP/SCP transfer of a file to the primary FTP/SCP server fails and the
secondary FTP/SCP server is not configured.
Clearing Procedure
1. Ensure the primary FTP/SCP server IP addresses is correct.

3. Ensure the user name/password used to access the primary server is correct.
4. Configure a secondary server.

Alarms 1-227
COM0042
TXFRSFAIL
File Transfer Failed - Primary and Secondary Servers


This alarm is generated when the FTP/SCP transfer of a file to the primary and secondary FTP/SCP
servers fail.
■ Failure in connectivity to the servers
Clearing Procedure
1. Ensure the primary and secondary FTP/SCP server’s IP addresses are correct.
3. Ensure the user name/password used to access both FTP/SCP servers are correct.
4. Ensure there is enough disk space available on one the FTP/SCP server.
5. Check connectivity to the servers.

COM0044
GCC-GMPLS-CONFIG-MISMATCH/GMPLS-CONFIG-MSMT
GMPLS neighbors' configuration do not match


This alarm is generated by the OSC along which there is a mismatch between the local value and
received value of the Hello interval/Dead interval. This indicates that the OSPF adjacency is not up.
This alarm is cleared when the GMPLS routing detects two consecutive mismatch-free OSPF Hello
messages.
■ Mismatch configuration of Hello Interval/Dead Interval between this node and it’s direct neighbor
Clearing Procedure
■ Ensure the Hello Interval and Dead Interval at each affected network element are the same (both
ends of a given link must have the same Hello Interval value and both ends must have the same
Dead Interval value)

Alarms 1-229
COM0045
GRE-TUNNEL-ADDRESS-MISMATCH
GRE Tunnel address do not match at Local and Remote End


This communications alarm is raised on the GMPLS Control Channel if the GRE Tunnel Remote IP
Address discovered by the GMPLS Control Channel does not match with the GRE Tunnel Remote IP
Address that is configured on the GRE Tunnel which is associated with the GMPLS Control Channel.
■ Associated GRE Tunnel Remote Address <tunnel_remote_ip_address> does not match Discovered
GRE Tunnel Remote Address <discovered_remote_ip_address>
Clearing Procedure
■ Ensure that the Associated GRE Tunnel Remote Address <tunnel_remote_ip_address> and
Discovered Remote Address <discovered_remote_ip_address> match. This can be achieved by
doing one any of the following:
□ By configuring GRE Tunnel Remote IP address at the local end to the same value as the
GRE Tunnel Local IP address configured at the remote end
□ By configuring GRE Tunnel Local IP address at the remote end to the same value as the
GRE Tunnel Remote IP address configured at the local end

COM0048
RSTRPATHACT
Restoration Path Active


It will be generated when restorable or revertive SNC switches from the working path to the restored path.
Clearing Procedure
■ This alarm will be cleared when the SNC switches from the restored path to the working path

Alarms 1-231
COM0049
IGCCFAIL
General Communication Channel - Line Side IGCC Failure

■ Severity - Major/Minor

This alarm is generated by the IGCC.
This alarm is generated when none of the XGCC0-VCAT channels are in-service.
Clearing Procedure
■ This alarm is cleared by clearing the individual datapath related fault conditions.

COM0050
TXFR-SEC-FAIL
File Transfer to Secondary FTP Server Failed


In situations where simultaneous upload of a file to both primary and secondary FTP/SCP servers is
enabled, this alarm is generated when the FTP/SCP transfer of a file to the primary FTP/SCP server is
successful, but fails on the secondary FTP/SCP server.
■ Incorrect Secondary FTP/SCP server IP address
Clearing Procedure
1. Ensure the secondary FTP/SCP server IP addresses is correct.

3. Ensure the user name/password used to access the secondary FTP/SCP server is correct.

Alarms 1-233
COM0052
NTP-SERVER-UNAVAILABLE
Configured NTP Server(s) is Unavailable
■ Alarm Type - Equipment

Description
This alarm is generated on the NTP server due to any of the following:
■ Loss of connectivity to the NTP server
■ Quality of the clock source falls below Stratum 5 level
■ NTP status (ServerStatus) is one of these values
□ REJECT
□ FALSE-TICK
□ OUTLYER
□ EXCESS
Clearing Procedure
1. Delete the affected NTP instance configuration

2. Ensure connectivity is restored with the NTP server
3. Ensure the clock quality improves to Stratum 5 level (at a minimum)
Note: Performing a warm or cold reboot may temporarily clear the alarm (until the next cycle of
NTP synchronization takes place).
Note: This alarm can be suppressed by placing the NTP in Locked or Maintenance admin state.
COM0053
GCCFAIL
General Communication Channel-Link Failure


■ Applicable Facilities - GCC

This alarm is generated by GCC Link failure.
This alarm is generated if supporting equipment cannot support Trib GCC (Ex. non CR TIMs inserted in
place of CR TIM after Trib GCC was created on CR-TIM).
Clearing Procedure
■ Check the datapath and correct any issues, including GccInterOp Mode
■ Check the supporting equipment can support GCC or not

Alarms 1-235
COM0071
PEER-UNREACHABLE
Unable to reach the IKE Peer

This alarm is generated on the IKE peer.

This alarm is generated when the IGCC interface is unable to establish IKE session with the peer.
■ IGCC (control channel) interface used to communicate with the Peer IKE instance being
disconnected.
■ Peer IKE instance not reachable
Clearing Procedure
Note: Note: If any one of the below steps clears the alarm then the clearing procedure is complete
1. Check for IGCC faults or underlying OCG/SCH faults

2. Restore IGCC interface to successfully establish session with the IKE Peer

COM0072
PEER-AUTHENTICATION-FAIL
IKE Peer Authentication Failed

■ SA/NSA - NSA (Non Service- Affecting) or SA (Service Affecting) depending on the global policy
configuration

■ If the IKE authentication with the peer fails
■ If the IKE peer is unreachable
■ If the IKE peer X.509 certificate is invalid
Clearing Procedure
1. Check if there are any acitve PEER-UNREACHABLE, REKEY-SA-FAIL, ENCR-CONFIG-MSMT

IGCCFAIL alarms on the system.
2. Check if the IKE peer X.509 certificate is valid

Alarms 1-237
COM0073
REKEY-SA-FAIL
Failed to Re-key the SA

■ SA/NSA - NSA (Non Service- Affecting) or SA (Service Affecting) depending on the global policy
configuration

This alarm is generated on the SecY MO , if the MACsec child security association (SA) re-key fails. This
alarm is generated on the IKEPeer MO, if the IKE SA re-key fails.
■ IKE Session with Peer is down due to IGCC interface Faults or the Peer IKE process is down
■ IKE Deamon Failure or Software issues
Clearing Procedure
1. Check for fault in IGCC interface or underlying OCG/SCH faults

2. Restore IGCC interface to successfully establish session with the IKE Peer

COM0074
IKE-MIS-CONFIG
IKE configuration mismatch


This alarm is raised on the IKE Peer MO, if the mismatch is IKE related. This alarm is raised on the SecY
Ctrl MO, if the mismatch is MACsec data path encryption related.
This alarm is raised when IKE detects a mismatch between the near-end and far-end peers related to
either IKE or data path encryption attributes, which inhibits the proper functioning of encryption related
functions.
Note: The detailed condition of the alarms displays the specific attribute which is mismatching.
Clearing Procedure
1. Check whether the IKE configurations and the data path encryption attributes between near-end and
far-end match. For example, cipher suite, authentication schemes, expect peer X.509 certificates.
2. If there is a mismatch, configure the appropriate values.
Software Processing Alarms

Software processing alarms are associated with the software processing errors. For example, Software
Upgrade has Failed, and Persistence space less than 2%-critical. The chassis level LED is not illuminated
when software processing alarms are raised.

Alarms 1-239
SWP0006
DBRESTOREFAIL
DB Restore Failure
■ Alarm Type - Software Processing


This alarm is generated during a user initiated database restore operation and the network element did
not execute this successfully.
■ The database to be restored was determined to be 'incoherent' (for example, failed its Error Check
(for example, Checksum))
■ There was insufficient non-volatile memory to store the database. This is generated after the
system has re-initialized with the previous database
Clearing Procedure
1. If there is insufficient space in the persistent memory, clear the persistent memory and retry.
2. Down the correct database image and perform database restoration again.

SWP0018
SWUPGRDFAIL
Software Upgrade Failure, flash space problem or corrupt SW


This alarm is generated when a user initiated software upgrade operation has failed.
■ Corrupted software image
■ Insufficient space in persistent memory
Clearing Procedure
1. If there is insufficient space in the persistent memory, clear the persistent memory and retry.
2. Download the correct software image and perform software upgrade again.
3. If even after downloading a new copy of the software image this problem persists, contact the
Technical Assistance Center (TAC). See for contact details.

Alarms 1-241
SWP0019
SWUPGRDFAIL-BOOTUP
Software Upgrade Failure, when loading new software


This alarm is generated when a user initiated software loading operation has failed during reboot.
■ Corrupted new software image
■ Software image not loading
Clearing Procedure
■ Delete the software load and download another copy of the image

SWP0023
AUPFAIL
Creation of Upload File Failure


This alarm is generated when the network element failed to create a backup file (e.g. database). A
backup could have been initiated manually by the user or by the network element that has been
configured for a scheduled backup.
■ Insufficient memory in the persistent storage on the XCM/MCM/IMM/OMM
Clearing Procedure
1. Check the available persistence space in the XCM/MCM/IMM/OMM.

2. Delete unused software and database images on the network element.

Alarms 1-243
SWP0027
DBRESTOREFAIL-RBT
DB Restore Failure, Controller Reboot


This alarm is generated when the database restore operation fails due to a reboot.
This alarm is caused by:
■ Explicit reboot of the XCM/MCM/IMM/OMM card when the database restore was in progress
Clearing Procedure
■ Attempt another database restore

SWP0030
SWINSTALLFAIL
Software Installation Failure


This alarm is generated by the network element when a software installation procedure did not complete
successfully. The system has reverted to its previous software image (which in this case is the image
loaded from manufacturing).
■ Corrupted new software image
■ Unable to load the image
Clearing Procedure
1. Check the persistence space.

2. Delete the software load and download another copy of the image.

Alarms 1-245
SWP0031
BKUPMEM-LOW
Available Non-volatile Memory Space is Low


This alarm is generated when the persistent storage used on the XCM/MCM/IMM/OMM is below 16% of
total non-volatile space.
■ Too many software images or database images downloaded to the XCM/MCM/IMM/OMM.
Clearing Procedure
■ Delete the excess database and software images

SWP0032
BKUPMEM-VERYLOW
Available Non-volatile Memory Space is Very Low


This alarm is generated when the persistent storage on the XCM/MCM/IMM/OMM is below 4% of total
non-volatile space.
■ Too many software images or database images downloaded to the XCM/MCM/IMM/OMM.
Clearing Procedure
■ Delete the excess database and software images

Alarms 1-247
SWP0036
MISCONFIG-IP-ADDR
IP Address Conflict on NE
■ Alarm Type - Software Processing / Communication


This alarm is generated by the network element when there is an IP address conflict on the network.
Clearing Procedure
1. Reconfigure the IP address on the network element.
2. Check with the network administrator to ensure the IP address is valid.

SWP0037
ADSRUP
Software Upgrade has Failed, Controller Reboot


This alarm is generated when user initiated software loading operation has failed during reboot.
■ XCM/MCM/IMM/OMM reboot during software upgrade
Clearing Procedure
■ Attempt another upgrade of the XCM/MCM/IMM/OMM.

Alarms 1-249
SWP0039
SHELFDB-CORRUPT
Shelf database corruption detected while Upgrade


This alarm is generated by the Chassis.
This alarm is raised when the shelf chassis database is corrupted.
Clearing Procedure
■ Revert to the old software and database.

SWP0040
LIC-ASSIGN-MISMATCH
License Assignment Mismatch

■ Applicable facilities - AOLM-B, AOLX-B, AOLM2-B, AOLX2-B, SOLM2-B, SOLX2-B, XTOCGPTP,
XTSCGPTP

This alarm is generated by AOLM-B, AOLX-B, AOLM2-B, AOLX2-B, SOLM2-B, SOLX2-B, XTOCGPTP,
and XTSCGPTP.
This alarm is generated when there is a mismatch between the serial number of the FRU associated with
the license and the serial number of the physically inserted FRU. This can happen when a FRU is
inserted in place of another FRU which had licenses activated on it.
Clearing Procedure
The user needs to perform a Re-assign operation from the License Manager in DNA to associate the
serial number of the currently provisioned FRU with the licenses associated with the FRU slot.

Alarms 1-251
SWP0041
LIC-INSUFFICIENCY
License Insufficiency

■ Applicable facilities - AOLM-B, AOLX-B, XTOCGPTP, XTSCGPTP

This alarm is generated by AOLM-B, AOLX-B, XTOCGPTP, XTSCGPTP.
This alarm is generated when the licensed FRU has services provisioned beyond the default licensed
capacity. This alarm is raised only during upgrade and is visible until a reboot is performed. Once this
alarm is cleared, it will not be raised again.
Clearing Procedure
■ Activate appropriate licenses on the provisioned equipment until the bandwidth accrued from the
licenses can support the services provisioned.
■ Change the modulation of channel from modulation type with insufficient license to modulation type
having excess license, provided the modulation type on both the ends match with each other.
Note: This alarm is also cleared if the services on the modulation type that has insufficient
licenses are deleted.

SWP0042
LIC-MF-MISMATCH
License Modulation Format Mismatch

■ Applicable facilities - AOLM-B, AOLX-B, AOLM2-B, AOLX2-B, SOLM2-B, SOLX2-B

This alarm is generated by AOLM-B, AOLX-B, AOLM2-B, AOLX2-B, SOLM2-B, SOLX2-B.
This alarm is raised when there is a mismatch in the licenses provisioned and the carrier modulation
formats due to a change of modulation format on a carrier pair from BPSK to QPSK or vice versa by the
user when services are provisioned against the carrier.
Clearing Procedure
■ Add licenses to support the modulation format as applicable.

■ Change the modulation of channel from modulation type with insufficient license to modulation type
having excess license, provided the modulation type on both the ends match with each other.
Note: This alarm is also cleared if the services on the modulation type that has insufficient
licenses are deleted.

Alarms 1-253
SWP0043
LIC-NW-AUDIT-MISM
License Network Audit Mismatch


This alarm is generated on network elements.
This alarm is triggered by DNA when there is a mismatch between the DNA and the network element with
respect to a license(s).This condition can occur after a database restore which may not reflect the current
provisioned status of the network element, leading to a mismatch.
Note: This alarm is neither affected by Alarm Reporting Control (ARC) nor Administrative Lock /
Administrative Maintenance alarms.
Clearing Procedure
■ Resolve the conflicting licenses by deleting the licenses or services or a combination of both from
DNA.
Note: If any node containing line modules with activated licenses (in an audit mismatched
state) becomes unreachable after the LIC-NW-AUDIT-MISM alarm is raised, the NCT
connectivity to the chassis must be re-established and the chassis must be reachable before
any licensing operation can be done to resolve the conflicts

SWP0044
ENCMODE-CHANGE-PENDING
Encoding Mode Changing Pending Cold Reset

■ Applicable facilities - AOLX2, AOLM2, SOLX2, SOLM2, AOFX, AOFM, XTOCGPTP, XTSCGPTP

This alarm is generated by AOLX2, AOLM2, SOLX2, SOLM2, AOFX, AOFM equipments.
This alarm is raised when the encoding mode is changed to a value other than the installed encoding
mode and the cold reset is pending.
Clearing Procedure
■ Cold reset/Power cycle the FRU.

■ Change the encoding mode to the installed encoding mode.

Alarms 1-255
SWP0045
SCH-MSMT
Super-Channel Provisioned and Installed values do not match

■ Applicable facilities - SCHCTP

This alarm is generated by SCHCTP.
This alarm is generated when there is a mismatch between the provisioned and installed super channel
values of the AOFX/AOFM-500.
Clearing Procedure
This alarm is cleared when the provisioned and installed super channel values match.

SWP0046
MIGR-FAIL
Migration of DB to DTN-X failed

■ Applicable facilities - Chassis

This alarm is generated by chassis.
This alarm is raised due to the failure of migration of database from the system being migrated (original
database) to the new node controller. It could be because of a corrupted database or because of steps
missed during migration procedure. This alarm is raised on the node controller of the XTC chassis that
would be the node controller for the migrated system.
Clearing Procedure
1. A subsequent successful migration of the original database to the new node controller.
2. Fresh installation of the database on the XTC chassis.
3. Repeat the migration procedure after verifying that all the steps have been followed including the the
pre-requisite of the original database being in a migration enabled state. Verify that the backup of the
database being migrated was taken after enabling this state.
4. If the failure persists, revert the migration procedure and start from a fresh install of the XTC chassis
and initiate a migration of the original database again.
5. If failure continues to persist, contact the Technical Assistance Center (TAC). See for contact details.

Alarms 1-257
SWP0047
PREPUPGRDFAIL
Prepare for upgrade failed

■ SA/NSA - NSA (Non-service Affecting)
■ Applicable facilities - Node

This alarm is generated by the node when pre-upgrade check fails on one or more controller chassis of a
node.
Clearing Procedure
1. Perform the PrepareForUpgrade action to re-initiate the pre-upgrade check and clear the alarm.
2. If failure continues to persist, contact the Technical Assistance Center (TAC). See for contact details.

SWP0048
CAC-UNAVAIL
Supporting Transport Layer is not Provisioned

■ SA/NSA - NSA (Non-service Affecting)
■ Applicable facilities - Network Interface

This alarm is generated when the supporting ODU CTP/ODU Flexi CTP is not provisioned or is deleted
after Network interface is provisioned.
Clearing Procedure
■ Re-provision the supporting ODU/ODUFlexi CTP by creating an OTN SNC or cross-connect.

Alarms 1-259
SWP0049
CAC-FAIL
Supporting Transport Layer has lesser capacity

■ Applicable facilities - Network Interface, Ethernet Interface

This alarm is generated when supporting ODU CTP/ODU Flexi CTP is re-provisioned with lesser capacity
than the bandwidth committed by network interface and ethernet interface Connection Admission Control
(CAC).
Clearing Procedure
■ Re-provision the supporting ODU/ODUFlexi CTP by creating an OTN SNC or cross-connect with
the correct bandwidth.

SWP0050
LIC-TYPE-MISMATCH
License Type Mismatch

■ Applicable facilities - AOFX-500B, AOFM-500B , SOFX-500B, SOFM-500B, AOLM-500B,
AOLX-500B, AOLM2-500B, AOLX2-500B, SOLM2-500B, SOLX2-500B

This alarm is generated when there is a mismatch between the FRU type in the activated license on an IB
FRU and the installed IB FRU in the slot.
Clearing Procedure
■ Re-assign operation on the existing license to have a matching installed type in the license
information.
■ Ensure to rebrand the license as applicable to the installed FRU.

Alarms 1-261
SWP0051
COLD-RESET-PENDING
OtnContainer Change Pending Cold Reset

■ Applicable facilities - AOFX-500B, AOFM-500B , SOFX-500B, SOFM-500B, AOLM-500B,
AOLX-500B, AOLM2-500B, AOLX2-500B, SOLM2-500B, SOLX2-500B

This alarm is generated when the OTN container type is changed and cold reset it pending.
Clearing Procedure
■ Cold reset/Power Cycle the FRU

SWP0052
REM-FECOH-RATIO-MSMT
Fec Overhead Ratio Changing Pending Cold Reset

■ Applicable facilities - XTSCGPTP

This alarm is generated when remote equipment has different FEC overhead ratio configured than the
local.
Clearing Procedure
■ Re-provision both remote and local ends to have same FEC overhead ratio.
Equipment Alarms
Equipment alarms are associated with the hardware faults like Equipment Failure and Equipment
Unreachable. Equipment Alarms can also be associated with alarms such as Equipment Mismatch. The
chassis level LED is illuminated when equipment alarms are raised. For equipment alarms, this behavior
cannot be changed using the Alarm Severity Assignment Profile Settings window in GNM.

Alarms 1-263
EQP0000
BRKROPEN48V
Breaker Open 48V

■ Detailed Conditions - BREAKER-OPEN

This alarm is generated when the breaker is open and there is no supply of power to the PEM/FeedPTP.
■ Circuit breaker trip
Clearing Procedure
1. Check the breaker connectivity.
2. Turn breaker to the on position.

EQP0008
EQPTFAIL
Equipment Failure

■ Severity - Critical/Major/Minor
■ SA/NSA - SA/NSA
■ Applicable Circuit Packs - BMM, Chassis, CMM, DLM, DSE, Fan, FBM, GAM, IOSHELF, MCM,
OAM, OLM, OLX, OMM, ORM, OTM, OTXM, PEM, OPSM, RAM, TAM, DICM, TEM, TIM, XICM,
TOM, TSM, XCM, XCMH, XLM, XM, IRM, FMMC, FRM, FSE, AOFX, IAM, FSM, IMM,
AOFM,PXM , XMM, FMMF250
■ Detailed Conditions - BMM_RED_PLC_POWER_SUPPLY_FAILURE,
BMM_BLUE_PLC_POWER_SUPPLY_FAILURE, BMM_RED_PLC_FAULT,
BMM_BLUE_PLC_FAULT, BPOST_FAIL, BPOSTFAILED, RX-EDFA-POWER-SUPPLY-FAILURE,
TX-EDFA-POWER-SUPPLY-FAILURE, RX-EDFA-ACCESS-FAIL, TX-EDFA-ACCESS-FAIL, DSP-
FAULT, CONTROL-BPOSTFAILED, DSP-COMMFAILED, CARDFAULT, FPGA-LOAD-FAILED,
IDLER_LASER-DEGRADE, IDLER_LASER_FAIL, INVALID-EEPROM, UNSUPPORTED-HW,
COMM-FAILED, PATH-FAILED, TX-FAULT, TEC-FAULT, WAVELENGTH-LOSS-OF-LOCK,
TEMPSHUTDOWN, TX-BIAS-EXTREME-OOR-HIGH, TX-BIAS-EXTREME-OOR-LOW, OPT-
EXTREME-OOR-HIGH, OPT-EXTREME-OOR-LOW, VCC-EXTREME-OOR-HIGH, VCC-
LEXTREME-OOR-LOW, FAULTED, FAN1-SPEED-OUT-OF-RANGE, FAN2SPEED-OUT-OF-
RANGE, FAN3-SPEED-OUT-OF-RANGE, PUMP-CURRENT, PUMP-VOLT, PUMP-BREAKER,
PUMP-FAILURE, ALS-PILOT-LASER-FAIL

This alarm is generated by the active XCM/MCM/XCMH/IMM/OMM on the reporting circuit pack or fan or
PEM.
This alarm is generated when a hardware component on the reporting circuit pack/fan/PEM has failed. If
the alarm is raised on any of the circuit packs, the alarm severity is critical and is service affecting. If the
alarm is raised on the XCM, fan or PEM, the alarm severity is major and is non-service affecting.
This alarm is most likely caused by a device failure.
Clearing Procedure
Note: Always ensure that the collected debug information is sent to Technical Assistance Center
(TAC).
1. Upload the debug information to an FTP server.

2. Check the detailed condition information.

Alarms 1-265
3. Warm-reset the circuit pack (wherever applicable) on which the alarm is reported.
4. Verify that the reset is complete and error free.

EQP0009
EQPT-PARTFAIL
Equipment Partial Failure

■ Severity - Critical/Major
■ SA/NSA - SA/NSA
■ Applicable Circuit Packs - BMM, CMM, DLM, DSE, FAN, FBM, FMMF250, GAM, MCM, OAM,
OLM, OMM, ORM, OTM, OTM, OTXM, OPSM, PEM, RAM, SCM, TAM, DICM,TIM, XICM, TOM,
TSM, XCM, OXM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80, SLM-80, REM, FRM, IMM,
FSM, BMM, AOFM, IAM, AOFX, IRM, XCMH, FMMC, FSE, PXM, XMM
■ Detailed Conditions - BACK-REFLECTION-AUTO-MUTE, GAM_DSP_COM_FAIL,
GAM_DSP_FAIL, GAM_DSP_INIT_FAIL, GAM_TX_EDFA_PUMP_EOL, VOA-ATTN-OOR, OSC-
LASER-FAIL, OSC-LASER-DEGRADE, OSC-APD-CUR-LIMIT, MCMA-ETHERNET-LINK-DOWN,
MCMB-ETHERNET-LINK-DOWN

This alarm is generated by the active XCM/MCM/XCMH/IMM/OMM on the reporting circuit pack or the
fan.
This alarm is generated when a few hardware components of the reporting circuit pack fail or the fan. If
the alarm is raised on any of the circuit pack, the severity of the alarm is critical and is service affecting. If
the alarm is raised on the fan, alarm severity is major and is non-service affecting.
This alarm is most likely caused by a device failure.
Clearing Procedure
(TAC).

3. Warm reset the circuit pack on which the alarm is reported.

Alarms 1-267
EQP0010
EQPTMSMT
Equipment Type Mismatch

■ Applicable Circuit Packs - BMM, Chassis, CMM, DLM, DSE, FAN, FBM, FMMF250, GAM, MCM,
OAM, OLM,OLX, OMM, ORM, OTM, OTXM, OPSM, PEM, RAM, SCM, TAM, DICM,TIM, XICM,
TOM, TSM, XCM, OXM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80, SLM-80, REM, IRM,
FMMC, FRM, IAM, AOFX, AOFM, IMM, FSM,PXM

This alarm is generated by the active XCM/MCM/IMM/OMM on the reporting circuit pack.
This alarm is generated when a circuit pack is inserted in the slot that has been provisioned for a different
type of circuit pack. In case of ILS3 cards, this alarm is generated when a circuit pack is inserted into a
different slot other than the pre-provisioned slot.
Clearing Procedure
1. If the slot has been improperly configured, delete the provisioned configuration of the slot. This allows
the reporting circuit pack to automatically come into service.
2. Edit the provisioned card type to be the same as the installed type.
3. If an incorrect circuit pack has been inserted, install the correct circuit pack in the correct slot.

EQP0012
IMPROPRMVL
Equipment Improper Removal

■ Severity - Critical/Major/Minor
■ SA/NSA - SA/NSA
OLM, OMM, ORM, OTM, OTM, OTXM, OPSM, PEM, RAM, SCM, TAM, DICM, TIM, XICM, TOM,
TSM, XCM, XCMH, OXM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80, SLM-80, REM, IRM,
IMM, FRM, AOFM, IAM, FSM, FMMC, AOFX, FSE,PXM

This alarm is generated by the active XCM/MCM/XCMH/IMM/OMM in the chassis on any of the circuit
packs, fan or PEM.
This alarm is generated when the circuit pack, fan or PEM is removed from the slot without changing the
administrative state to Maintenance or Locked. If the alarm is raised on any of the circuit packs, the
severity of the alarm is critical and is service affecting. If the alarm is raised on the fan or PEM, alarm
severity is major and is non-service affecting.
Clearing Procedure
■ Insert the circuit pack into the slot from where it was removed, or using the GUI delete the
configured module from the database

Alarms 1-269
EQP0013
EQPTCPUR
Equipment’s Control Plane is Unreachable

■ Applicable Circuit Packs - BMM, Chassis, XCMH, CMM, DLM, DSE, FBM, FMMF250, MCM, OAM,
OLM, OMM, ORM, OTM, OTXM, PEM, OPSM, RAM, SCM, XCM, XLM, ADLM, AXLM, SLM,
ADLM-80, AXLM-80, SLM-80, REM, AOFX, IMM, FMMC, FSM, AOFM, IRM, IAM, FRM,PXM

This alarm is generated by the active XCM/XCMH/MCM/IMM/OMM on the reporting circuit pack.
This alarm is generated when the XCM/MCM/XCMH/IMM/OMM cannot communicate with the reporting
circuit pack and is not able to exchange control plane messages.
■ Rebooting or faulty circuit pack
■ Bent pin in the backplane
Clearing Procedure
(TAC).

3. Warm reset the circuit pack on which the alarm is reported.

EQP0015
DBMSMT
Database Mismatch

■ Applicable Circuit Packs - BMM, CMM, DLM, DSE, FBM, FMMF250, OAM, OLM, ORM, OTM,
RAM, SCM, OLX, XLM, OPSM, OTXM, TEM, MCM, OMM, IAM, AOFM, FRM, AOFX, FMMC,
FSM, IRM

This alarm is raised when the serial number of the active/stand-by XCM/MCM/IMM/OMM stored on the
line card does not match the serial number of the active/standby XCM/MCM/IMM/OMM installed in the
chassis. The Additional Text field in GNM displays the serial numbers.
Clearing Procedure
1. Download and install the correct database from the FTP server to the existing XCM/MCM/IMM/OMM
installed in the chassis.
2. Replace the correct XCM/MCM/IMM/OMM into the chassis, that is, the XCM/MCM/IMM/OMM that
matches the serial number present on the line cards.
3. Force synchronize the line cards with the database on the active XCM/MCM/IMM/OMM.

Alarms 1-271
EQP0021
EQPTCPRESET
Equipment's Control Plane is Warm-resetting

■ SA/NSA - NSA (Non-Service-Affecting)
■ Applicable Circuit Packs - BMM, CMM, DLM, DSE, FBM, FMMF250, MCM, OAM, OLM, OMM,
ORM, OTM, OTXM, OPSM, RAM, SCM, XCM, XCMH, XLM, ADLM, AXLM, SLM, ADLM-80,
AXLM-80, SLM-80, TEM, FMMC, FRM, IAM, AOFM, FSM, IRM, IMM, AOFX

This alarm is generated by the managed object.
This alarm is generated when the control plane has been warm reset.
Clearing Procedure
■ This alarm will clear once the applicable circuit pack has completed the warm reset.

EQP0024
PWROV
Power over voltage

■ Applicable Circuit Packs - PEM
This alarm is generated by the PEM.

This alarm is raised on Feed PTP when input voltage exceeds the configured threshold.
Clearing Procedure
■ Ensure the input voltage on PEM is normal and below the set threshold level.
■ Replace the PEM equipment if found faulty.

Alarms 1-273
EQP0025
PWRUV
Power under voltage

■ Applicable Circuit Packs - PEM

This alarm is generated by the PEM object.
This alarm is raised on feed PTP when input voltage drops below the configured threshold level.
Clearing Procedure
■ Ensure the input voltage on PEM resumes to normal and with in the set voltage threshold range.
■ Check for the PEM module and replace the PEM equipment if found faulty.

EQP0028
TEMP-OORH-TXPIC-SHUTDOWN
Tx PIC Temperature Out of Range - High - Auto Shutdown

■ Detailed Conditions - TXPIC-TEMPSHUTDOWN, TXPIC-CASE-TEMPSHUTDOWN

This alarm is generated by DLM, OLM, OLX, and XLM.
This alarm is generated when the Tx PIC temperature exceeds the predefined threshold value.
Clearing Procedure
(TAC).

3. Ensure that ambient temperature is sufficiently low.
4. Check that system fans are working properly.

Alarms 1-275
EQP0029
TEMP-OORH-RXPIC-SHUTDOWN
Rx PIC Temperature Out Of Range High - Auto Shutdown

■ Detailed Conditions - RXPIC-TEMPSHUTDOWN, RXPIC-CASE-TEMPSHUTDOWN

This alarm is generated by DLM, OLM, OPSM, OTXM, OLX, and XLM.
This alarm is generated when the Rx PIC temperature exceeds the predefined threshold value.
Clearing Procedure
(TAC).

3. Ensure that ambient temperature is sufficiently low.
4. Check that the system fans are working properly.

EQP0034
AMBIENT-TEMP-OORH
Ambient (inlet) Temperature Out of Range - High


This alarm is generated by the chassis when the ambient temperature (detected upon inlet to this chassis
by at least one circuit pack) is greater than or equal to the pre-defined high-inlet-temperature onset
threshold and has remained above it for 2.5 +/- 0.5 seconds. The network element does not automatically
power down any circuit pack as a result of reaching this threshold.
Clearing Procedure
■ Ensure that the environmental issues are corrected

Alarms 1-277
EQP0036
TEMP-OORH
Temperature Out Of Range - High

■ SA/NSA - NSA(Non-Service Affecting)
■ Applicable Circuit Packs - MCM, OPSM, BMM, CMM, DLM/ADLM/ADLM-80, XLM/AXLM/AXLM-80,
SLM/SLM-80, FBM, FMMF250, GAM, OMM, OAM, ORM, OTXM, RAM, DSE, OLM, OTM, PEM,
SCM, TSM, XCM, XCMH, OXM, TEM, IRM, AOFM, IAM, FSM, AOFX, FRM, IMM, FMMC, XMM
■ Detailed Conditions - GAM_TX_EDFA_PUMP_TEMP_XTR, TEMPSHUTDOWN, TX-EDFA-CASE-
TEMP, TXPIC-OVERTEMP, RXPIC-OVERTEMP, TXPIC-CASE-OVERTEMP, RXPIC-CASE-
OVERTEMP, WAVELOCKER-OVERTEMP, VOA-OVERTEMP

This alarm is generated when the temperature of this circuit pack is greater than the predefined threshold
value in spite of the ambient temperature being within range.
This is due to some combination of system fan problem or Thermo-Electric Cooler (TEC) failure on the
module.
Clearing Procedure
1. Ensure that the air filter is clean.

2. Ensure that the system fans are functioning properly.

EQP0043
PWR48VFAIL
Power 48V Failure

■ Detailed Conditions - POWER-FAIL

This alarm is generated by the active XCM/MCM/IMM/OMM on the PEM object.
This alarm is generated when the PEM is unable to detect power and breaker is closed.
■ Faulty / severed power wires coming into the PEM
Clearing Procedure
1. Check cabling coming into the PEM.

2. Check the power distribution system feeding the PEM.

Alarms 1-279
EQP0044
EQPTDEGRADE
Equipment Degradation

■ Applicable Circuit Packs - BMM, Chassis, CMM, DLM, DSE, FAN, FBM, FMMF250, GAM, IOShelf,
MCM, OAM, OLM, OMM, ORM, OTM, OTXM, OPSM, PEM, RAM, REM, SCM, TAM, DICM, TIM,
XICM, TEM, TOM, TSM, XCM, XCMH, OXM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80,
SLM-80, IRM, AOFX, FRM, FSE, FSM, IMM, IAM, AOFM, FMMC, XMM
■ Detailed Conditions - BPOST_FAIL, GAM_TX_EDFA_GAIN_ERROR,
GAM_TX_EDFA_CASE_TEMP_OOR, GAM_TX_EDFA_CASE_TEMP_XTR,
GAM_TX_EDFA_PUMP_TEMP_OOR, IDLER_LASER-DEGRADE, IDLER_LASER_FAIL,
BMM_RED_PLC_HEATSINK_TEMP, BMM_BLUE_PLC_HEATSINK_TEMP,
BMM_RED_PLC_ACCESS_FAIL, BMM_BLUE_PLC_ACCESS_FAIL, RX-EDFA-PUMP-TEMP, RX-
EDFA-PUMP-EOL, TX-EDFA-PUMP-TEMP, TX-EDFA-PUMP-EOL, RX-EDFA-TEC-CURRENT,
TX-EDFA-TEC-CURRENT, CTRLMOD-DEGRADED, OCH1-DEGRADED, OCH2-DEGRADED,
OCH3-DEGRADED, OCH4-DEGRADED, OCH5-DEGRADED, OCH6-DEGRADED, OCH7-
DEGRADED, OCH8-DEGRADED, OCH9-DEGRADED, OCH10-DEGRADED, SINGLE-FUSE,
ALS-PILOT-LASER-DEGRADE, PUMP-EOL, PUMP-LAUNCH-POWER, PUMP-TEMP, PUMP-
TEMPSHUTDOWN, ALS-PILOT-LASER-VOLTAGE-DEVIATION, OSC-VOLTAGE-DEVIATION,
TEC-CURRENT, MSA-FAULT, STATUSBUS-FAIL, TX/RX-EDFA-SPLIM, RX-EDFA-STAGE-
POWER-LIM.
Note: BMM2 module reports EQPTDEGRADE alarm with detailed condition text as “RX-EDFA-
STAGE-POWER-LIM”, when Q NOS R9.0.x is upgraded to R10.0.X or R11.0.X .

This alarm is generated by the active XCM/MCM/XCMH/IMM/OMM on the applicable circuit packs or fan
or PEM.
This alarm is generated when the service offered by the circuit pack is degrading. The circuit pack will
continue to be functional for some more time before it completely goes out-of-service.
Clearing Procedure
(TAC).
1. Upload the debug information to an FTP server (if applicable).



Alarms 1-281
EQP0045
Maintenance Required - contact Infinera customer support

■ Applicable Circuit Packs - DLM, TEM, and XLM

This alarm is raised on the circuit packs when a communication failure alarm is present on the circuit
pack.
Clearing Procedure
Contact Technical Assistance Center.

EQP0046
EQPT-PROT-FAIL-SLOT-n
Equipment Protection Control Bus Failure with Slot n

■ Applicable Circuit Packs - line module (DLM, OLM, XLM, ADLM, AXLM, and/or SLM), LM-80
(ADLM-80, AXLM-80, and/or SLM-80), and/or TEM
■ Detailed Conditions - PROTBUS-TO-SLOT3-FAILED, PROTBUS-TO-SLOT4-FAILED, PROTBUS-
TO-SLOT5-FAILED, PROTBUS-TO-SLOT6-FAILED

This alarm is generated by the line module, LM-80, and/or TEM.
This alarm is generated when there is an internal system fault that affects the line module, LM-80, and/or
TEM. After this alarm is raised no further protection switch will occur for a Digital SNCP on this slot. All
external requests will be rejected with error indication ‘protection switching operationally disabled’.
■ The problem is either on one of the slots or line module, LM-80, and/or TEM
Clearing Procedure
(TAC).


Alarms 1-283
EQP0047
INSUFFICIENT-GAIN
Insufficient Gain

■ Applicable Circuit Packs - BMM, CMM, OAM, ORM, IAM, IRM, FMMC, FSM, FRM
■ Detailed Conditions - RX-EDFA-LOSS-OF-GAIN, TX-EDFA-LOSS-OF-GAIN

This alarm is generated by the BMM/CMM/OAM/ORM/IAM/IRM/FSM/FRM.
This alarm is generated when the EDFA device cannot achieve the target gain.
■ EDFA hardware degradation
■ Too much loss on the DCM port
Clearing Procedure
(TAC).
1. Check the connectivity of the fiber coming in/out of the DCM port.

EQP0048
UNKNOWNFW
Unknown Firmware Present

OLM, OMM, ORM, OTM, PEM, OTXM, OPSM, RAM, SCM, TAM, DICM, TIM, XICM, TEM, TOM,
TSM, XCM, OXM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80, SLM-80, REM, FMMC, FRM,
AOFX, FSE, FSM, IAM, IRM, AOFM, PXM
■ Detailed Conditions - BMM-FIRMWARE-UNKNOWN, UNKNOWN-BASE-FW, UNKNOWN-LINE-
FW

This alarm is generated by the BMM, CMM, DLM, XLM, ADLM, AXLM, SLM, ADLM-80, AXLM-80,
SLM-80, TAM, DICM, GAM, OAM, OTXM, ORM, SCM, DSE, RAM, and/or REM.
This alarm is generated when the firmware version is incompatible with the software version currently
installed.
■ A rollback of software version is performed after software upgrade and the firmware version is not
compatible with the older software version. Software revision operation does not automatically
revert firmware
Clearing Procedure
■ Upgrade the version of software or revert the firmware by cold reboot

Alarms 1-285
EQP0050
BRAND-MSMT
Brand Mismatch


This alarm is generated by the OMM, IMM, MCM, XCMH and XCM.
This alarm is raised when an OMM, IMM, MCM, XCMH and XCM, which was commissioned earlier in a
different chassis is inserted into another chassis.
Clearing Procedure
1. Right click the MCM and select Make Standby.

2. Perform the procedure to re-sync all line cards to the IMM/XCM/XCMH/MCM/OMM.
3. Cold reboot each module.

EQP0051
INITFAIL
Initialization Failure


This alarm is generated by the standby IMM/XCM/XCMH/MCM/OMM.
This alarm is generated when the IMM/XCM/MCM/OMM has failed to intialize as standby.
This alarm is most likely caused when :
■ The IMM/XCM/XCMH/MCM/OMM has failed to intialize the database
Clearing Procedure
1. Pull out the IMM/XCM/XCMH/MCM/OMM partially and re-insert it. Refer to the DTC/MTC Task
Oriented Procedures Guide.
2. If re-inserting the IMM/XCM/XCMH/MCM/OMM does not solve the problem, contact the Technical

Alarms 1-287
EQP0052
OLDREV-CTRLR
Older Revision Controller present in invalid configuration

■ Applicable Managed Type - MCM/XCM/IMM/XCMH

This alarm is generated by MCM/XCM/IMM when more than 32 line cards are pre-provisioned or
installed, and the active MCM is MCM-B.
Note: The OLDREV-CTRLR alarm is raised by the management interfaces (GNM) on nodes with an
MCM-B node controller when the node is provisioned with 32 line modules, although the maximum
number of line modules supported for an MCM-B node controller is 48. The OLDREV-CTRLR alarm
has no functional impact and this discrepancy will be resolved in a future IQ NOS software release.
Clearing Procedure
1. Replace MCM of the Node Controller with MCM-C.

2. Remove some of the line cards to make their count less than or equal to 32.

EQP0054
OSC-COMM-FAIL-CTRLRA
CP to Controller A Internal OSC Ethernet Link Failure

■ Applicable Circuit Packs - BMM, OAM, RAM, ORM, IAM, IRM, FRM
■ Detailed Conditions - OSC-A-LINK-DOWN

This alarm is generated by the MCM in slot 7A or the OMM in slot 1A on the BMM/OAM/RAM/ORM/IAM/
IRM.
This alarm is generated when the OSC control link from the BMM/OAM and the MCM in slot 7A or the
OMM in slot 1A has failed.
■ A bent pin in the backplane
■ Faulty BMM/OAM/RAM/ORM/IAM/IRM
■ Faulty MCM/OMM/IMM
Clearing Procedure
(TAC).


Alarms 1-289
EQP0055
OSC-COMM-FAIL-CTRLRB
CP to Controller B Internal OSC Ethernet Link Failure

■ Severity - Major, not user customizable
■ Applicable Circuit Packs - BMM, OAM, ORM, RAM, IAM, IRM, FRM
■ Detailed Conditions - OSC-B-LINK-DOWN

This alarm is generated by the MCM in slot 7B or the OMM in slot 1B on the BMM/OAM.
This alarm is generated when the OSC control link from the BMM/OAM/ORM/RAM/IAM/IRM and the
MCM in slot 7B/OMM/IMM in slot 1B has failed.
■ Removal of MCM/OMM/IMM
■ Faulty MCM/OMM/IMM
■ Faulty BMM/OAM/ORM/RAM/IAM/IRM
Clearing Procedure
(TAC).

2. Check the detailed description information.

EQP0056
CTRL-COMM-FAIL-CTRLRA
CP to Controller A Internal Comm Failure

■ Applicable Circuit Packs - BMM, CMM, line module (DLM, XLM, ADLM, AXLM, and/or SLM), LM-80
(ADLM-80, AXLM-80, and/or SLM-80), DSE, FBM, FMMF250, MCM, OAM, OLM, OMM, ORM,
OTM, RAM, OTXM, OPSM, SCM, TSM, XCM, OXM, TEM, REM, FMMC, FRM, AOFX, AOFM,
FSM, IAM, IRM, PXM
■ Detailed Conditions - CARD-A-LINK-DOWN

This alarm is generated by the XCM/MCM/OMM/IMM in slot 7A or the OMM in slot 1A for this BMM/CMM/
line module/
LM-80/TEM/OAM/ORM/RAM/REM/SCM/DSE.
This alarm is generated when the Ethernet control link between the BMM/CMM/line module/
LM-80/TEM/OAM/ORM/RAM/REM/SCM/DSE/FRM/AOFX/AOFM/FMMC/FSM/IAM/IRM and the MCM in
slot 7A or the OMM in slot 1A or IMM has failed.
■ Faulty Ethernet transmitter on the BMM/CMM/line module/
LM-80/TEM/OAM/ORM/RAM/REM/SCM/DSE/FRM/AOFX/AOFM/FMMC/FSM/IAM/IRM as on the
XCM/MCM/OMM/IMM
■ Bent pin in the backplane connecting BMM/CMM/line module/LM-80/TEM and MCM in slot 7A or
OAM/ORM/RAM/REM/SCM/DSE/FRM/AOFX/AOFM/FMMC/FSM/IAM/IRM, IMM and OMM in slot
1A
Clearing Procedure
(TAC).


Alarms 1-291
EQP0057
CTRL-COMM-FAIL-CTRLRB
CP to Controller B Internal Comm Failure

■ Severity - Major, not user customizable
■ Applicable Circuit Packs - BMM, CMM, line module (DLM, XLM, ADLM, AXLM, and/or SLM), LM-80
(ADLM-80, AXLM-80, and/or SLM-80), DSE, FBM, FMMF250, OPSM, MCM, OAM, OLM, OMM,
ORM, OTM, OTXM, RAM, SCM, TSM, XCM, OXM, TEM, REM, IRM, AOFM, FRM, FSM, FMMC,
AOFX, IAM, PXM
■ Detailed Conditions - CARD-B-LINK-DOWN

This alarm is generated by the MCM in slot 7B or the OMM in slot 1B for this BMM/CMM/line module/
LM-80/TEM/OAM/ORM/RAM/REM/SCM/DSE.
This alarm is generated when the Ethernet control link between the BMM/CMM/line module/
LM-80/TEM/OAM/ORM/RAM/REM/SCM/DSE and the MCM in slot 7B or the OMM in slot 1B has failed.
■ Faulty Ethernet transmitter on the BMM/CMM/line module/LM-80/TEM/OAM/RAM/REM/SCM/DSE
as on the XCM/MCM/OMM/IMM
■ Bent pin in the backplane connecting BMM/CMM/line module/LM-80/TEM and MCM in slot 7B or
OAM/ORM/RAM/REM/SCM/DSE and OMM in slot 1B
Clearing Procedure
(TAC).


EQP0058
PEER-CTRLR-COMM-FAIL
Internal Ethernet Link Failure to Peer Controller Module

■ SA/NSA - NSA
■ Applicable Circuit Packs - MCM, OMM, XCM, IMM, XCMH

This alarm is generated by the active IMM, MCM, OMM, XCHM and XCM. This alarm is generated when
there is a loss of internal Ethernet-layer communication between the MCMs/OMMs. Loss of
communication between MCMs: MCM in slot 7A and MCM in slot 7B. Loss of communication between
OMMs: OMM in slot 1A and OMM in slot 1B.
■ Faulty Ethernet transmitter on the BMM/line module/TEM/OAM
■ Bent pin in the backplane connecting BMM/line module/TEM and MCM in slot 7B
■ Bent pin in the backplane connecting OAM and OMM in slot 1B
■ Removal of MCM in slot 7B
■ Removal of OMM in slot 1B
■ Faulty MCM
■ Faulty OMM
■ Reboot of the XCM/MCM/IMM/OMM (for example warm or cold reboot, XCM/MCM/IMM/OMM
switchover, software upgrade, and/or database restore)
Clearing Procedure
(TAC).
1. Upload the debug information to an FTP server (if applicable).


Alarms 1-293
EQP0059
EQPPER1
Air Filter Replacement Required

■ Severity - Minor (User Provisionable)
■ SA/NSA - NSA
■ Applicable Circuit Packs - Air Filter

This alarm is raised when the air filter needs to be replaced.
Clearing Procedure
1. Reset the Declaration Offset Policy.
2. Set a new alarm declaration date and time.
3. When the value of the parameter Alarm Status is changed to Disabled.
4. When the alarm reporting is inhibited using “Alarm Reporting Control” (ARC).
Note: The conditional description (air filter replacement) is user configurable.

EQP0060
EQPPER2
User Configured Probable Cause

■ SA/NSA - NSA

This alarm is raised when the alarm condition is reached.
Clearing Procedure
1. When the parameter Declaration Offset Policy is reset or a new alarm declaration date and time is set.

Alarms 1-295
EQP0061
EQPPER3
Air Filter Replacement Required

■ SA/NSA - NSA

This alarm is raised when the alarm condition is reached.
Clearing Procedure
1. When the parameter Declaration Offset Policy is reset or a new alarm declaration date and time is set.

EQP0062
ADMIN-MAINT
Administrative Maintenance

■ SA/NSA - NSA
■ Applicable Circuit Packs - Chassis, BMM, CMM, DLM, FBM, FMMF250, XLM, ADLM, AXLM, SLM,
ADLM-80, AXLM-80, SLM-80, OPSM, OTXM, TEM, TAM, DICM, TIM, XICM, TOM, GAM, OMM,
OAM, ORM, RAM, REM, SCM, DSE, FAN, MCM, OLM, OMM, OTM, PEM, TSM, XCM, OXM,
FSM, FRM, AOFM, FSE, AOFX, IAM, IRM, FMMC, XMM, XTOCGPTP , OCHPTP, XTSCGPTP ,
SCHCTP , CARRIERCTP , TRIBPTP

This alarm is raised when the user has administratively put the managed object into maintenance state by
using the management interface command.
Clearing Procedure
■ This alarm is cleared by Unlocking the managed object by using the management interface
command

Alarms 1-297
EQP0063
ADMIN-LOCK
Administrative Locked

■ SA/NSA - NSA
■ Applicable Circuit Packs - Chassis, MCM, BMM, CMM, DLM, FBM, FMMF250, XLM, ADLM, AXLM,
SLM, ADLM-80, AXLM-80, SLM-80, TEM, TAM, DICM, TIM, XICM, TOM, GAM, OMM, OAM,
ORM, RAM, REM, SCM, DSE, FAN, MCM, OLM, OTXM, XCMH, OMM, OTM, PEM, TSM, XCM,
OXM, IMM, FSM, OPSM, AOFM, FMMC, FSE, IAM, IRM, ORM, OLX, AOFX, FRM, XCMH

This alarm is raised when the user has administratively put the managed object into locked state by using
the management interface command.
Clearing Procedure
■ This alarm is cleared by Unlocking the managed object by using the management interface
command

EQP0064
PWRDRAW
Power Draw / Chassis power draw exceeds configured maximum value

■ SA/NSA - NSA
■ Applicable Circuit Packs - Chassis

This alarm is raised when the chassis power draw exceeds the configured maximum value as set in the
attribute configuredMaxPowerDraw.
This alarm is cleared when the chassis power draw drops below the value set in the attribute
configuredMaxPowerDraw.
Clearing Procedure
1. Change the attribute configuredMaxPowerDraw to a higher value.

2. If this alarm is raised after installing a circuit pack, perform the following:
a. Remove the circuit pack from the system (ensure that the circuit pack has been deleted from the
database if provisioned).
b. Change the attribute configuredMaxPowerDraw to a higher value.
c. Install the circuit pack into the system.
d. Verify that the alarm is clear.
3. If this alarm is raised unexpectedly and no circuit packs were recently installed, contact the Technical

Alarms 1-299
EQP0065
TEMP-OORL
Temperature Out of Range - Low

■ Applicable Circuit Packs - DLM, GAM, OLM, OTM, TEM, AOFM, XLM, AOFX, OLX

This alarm is generated when the temperature of this circuit pack is lower than the Infinera predefined
threshold value in spite of the ambient temperature being within range.
This is due to some combination of system fan problem or Thermo-Electric Cooler (TEC) failure on the
module.
Clearing Procedure
1. Ensure that the air filter is clean.

2. Ensure that the system fans are functioning properly.

EQP0066
EXCHAN
Excessive Channels

■ SA/NSA - SA
■ Applicable Circuit Packs - BMM (all BMM types)

This alarm indicates an excessive channel count alarm condition and is raised when the number of BMM
OCGs provisioned (either auto-provisioned or pre-provisioned) on a BMM exceeds the OCG equivalent
value configured for numberOfChannels attribute.
Clearing Procedure
■ This alarm is cleared when the number of BMM OCGs provisioned (either auto-provisioned or pre-
provisioned) on a BMM is equal to or less than the OCG equivalent value configured for
numberOfChannels attribute

Alarms 1-301
EQP0068
PWRCTRL
Power control initiated - maximum allowed fan speed reduced

■ Applicable Circuit Pack - Chassis
■ Detailed Conditions - SYSTEM-POWER-CONTROL-FAN-SPEED-REDUCED

This alarm is generated when the chassis power control action is initiated and maximum allowed fan
speed is reduced.
Clearing Procedure
This alarm is cleared on disabling the power control (power reduction) algorithm. Do any of the following
to clear this alarm:
1. Disable the chassis power control algorithm by setting the “ChassisPwrCtrl” attribute on the chassis to
‘Disabled’.
2. Change the chassis configuration such that the power consumption on the chassis is within the worst-
case limit set, that is remove or delete or un-provisioned equipment as appropriate to reduce the
chassis power consumption.

EQP0069
AGC-NF
AGC not Functioning

■ Applicable Circuit Packs - BMM, FRM
Description
This alarm is generated by the BMM/FRM head node.
This alarm is generated when Infinera’s Automated Gain Control (AGC) is not functioning or there is a
downstream loss of signal (after soaking the AGC failure condition in the network element for 2 hours).
List of detail conditions for AGC-NF using BMM headend node - lists all the detailed conditions of AGC-
NF alarm using BMM headend node.
List of detail conditions for AGC-NF using FRM headend node - lists all the detailed conditions of AGC-NF
alarm using FRM headend node.
Table 1-3 List of detail conditions for AGC-NF using BMM headend node
Sl.No Current AGC abort additional Detailed explanation Probable root cause
text (New)
1 AGC Link Discovery Timeout ADAPT is unable to discover the 1. OSC failure in downstream
entire link end to end ( BMM to node
BMM) 2. OSC crossover cable is not
connected properly
3. One/more intermediate
OAM/ORM is unreachable
OAM/ORM is rebooting
5. Improper association (pre-
amp to BMM)
2 Automatic Gain Control (AGC) ADAPT is disabled in the user User initiated configuration
is Disabled interface disabled AGC from user
interface

Alarms 1-303
Table 1-3 List of detail conditions for AGC-NF using BMM headend node (continued)
text (New)
3 Headend OCG Channel Num is ADAPT is unable to get add/drop, 1. Frequent power fluctuation in
Unknown for OCGs < list of express OCG information for one/ previous link with optical express
OCG's> more OCG's associated with the configuration
Head End BMM 2. One/more LM/peer
BMM/CMM card is unreachable/
warm rebooting
3. Chassis housing one/more
LM/peer BMM is unreachable
4. OCG OOR-H/L present in any
of the discovered add/drop
BMMOCGPTP
5. OCG OOR-H/L present in any
of the discovered optical express
BMMOCGPTP in Gen2 FRU's
6. OCG OOR-H present in any
of the optical express
BMMOCGPTP in Gen1 FRU's
7. Extender BMM card in
unreachable/warm rebooting
8. Chassis housing extender
BMM card is unreachable
9. High patch loss in extender to
base BMM card
10. Equipment degradation for of
the Head End BMM due to R|b
PLC Access Failure, CMM
Access Failure
4 Headend Local Signal Ratio ADAPT encountered error while Link parameters are out of range
Calc Error signal ratio calculation
5 Node Id: <xx>, Hop Id: <yy>, ADAPT gain commit failed Link parameters are out of range
Phase Id: <zz>: Gain Commit
Failed
6 Node Id: <xx>, Hop Id: <yy>, ADAPT is taking longer time to Unknown error encountered
Phase Id: <zz>: Gain Calc calculate gain in any FRU
Timeout
Phase Id: <zz>: Gain Commit commit gain in any FRU
Timeout
Phase Id: <zz>: Ack-timer return ADAPT status in any FRU
Expired

text (New)
9 Node Id: <xx>, Hop Id: <yy>, ADAPT is unable to get 1. Raman card unreachable
Phase Id: <zz>, Abort Commit: information of the associated 2. Raman card is not in service
Associated Raman Card Not Raman card 3. Chassis housing Raman is
Ready unreachable.
4. Link parameters are out of
range
10 Node Id: <xx>, Hop Id: <yy>, ADAPT is unable to get 1. Raman card unreachable
Phase Id: <zz>, Abort Commit: information of the associated far 2. Raman card is not in service
Far end Tx Raman card not end Raman card 3. Chassis housing Raman is
ready unreachable.
4. Link parameters are out of
range
11 Node Id: <xx>, Hop Id: <yy>, Head End Tx EDFA is shutdown 1. Head End BMM is in locked
Phase Id: <zz>, Abort Commit: state
Head end Tx EDFA Disabled 2. Head End BMM is disabled
due to ALS
12 Node Id: <xx>, Hop Id: <yy>, Any downstream OAM/ORM or 1. Any upstream card is in
Phase Id: <zz>, Abort Commit: TE-BMM is in LOL state locked state
Rx EDFA is in LOL 2. Span loss too high
3. DCF OLOS in upstream
OAM/ORM
4. High DCF loss in upstream
OAM/ORM
13 Node Id: <xx>, Hop Id: <yy>, Any downstream OAM/ORM or 1. TE BMM is locked
Phase Id: <zz>, Abort Commit: TE-BMM is in disable state 2. EDFA disabled due to ALS
Rx EDFA is disabled
14 Node Id: <xx>, Hop Id: <yy>, Any downstream Raman FRU is in 1. Raman card is in locked state
Phase Id: <zz>, Abort Commit: disable state 2. Raman pumps are disabled
RAMAN pumps are disabled due to ALS
15 Node Id: <xx>, Hop Id: <yy>, One/more Rx fiber type is set as User configured Tx fiber type as
Phase Id: <zz>, Abort Commit: unknown unknown to the upstream node
Rx fiber type is unknown
16 Node Id: <xx>, Hop Id: <yy>, One/more Tx fiber type is set as User configured Tx fiber type as
Phase Id: <zz>, Abort Commit: unknown unknown to the current node
Tx fiber type is unknown
17 Node Id: <xx>, Hop Id: <yy>, ADAPT getting invalid signal ratio Link parameter are out of range
Phase Id: <zz>, Abort Commit: from previous node
Invalid previous signal-ratio
18 Node Id: <xx>, Hop Id: <yy>, ADAPT is not doing gain commit Link is not doing gain commit
Phase Id: <zz>, Abort Commit: due to AGC-NF in previous link
AGC is not doing gain commit

Alarms 1-305
text (New)
19 Node Id: <xx>, Hop Id: <yy>, One/more DSP component of the 1. EDFA DSP access fail alarm
Phase Id: <zz>, Abort Commit: downstream OAM/ORM/BMM is in in the node
DSP access failure access failed state 2. RAMAN DSP access fail in
the node
3. Hw fault
20 Node Id: <xx>, Hop Id: <yy>, SLTE_Mode_1 is enabled in the 1. SLTE Mode 1 is enabled in
Phase Id: <zz>, Abort Commit: BMM any BMM2 in link
SLTE_Mode_1 is enabled in the 2. SLTE Mode 1 is enabled in
link any OAM-CXH1-MS in link
21 Node Id: <xx>, Hop Id: <yy>, Third Party Amplifier mode is 1. Third Party Amplifier mode is
Phase Id: <zz>, Abort Commit: enabled in the BMM enabled in any BMM in link
Third Party Amplifier mode is 2.Third Party Amplifier mode is
enabled in the link enabled in any OAM-CXH1-MS
in link
22 Node Id: <xx>, Hop Id: <yy>, Static mode is enabled in one/ 1. Static mode is enabled in any
Phase Id: <zz>, Abort Commit: more down stream FRUs ORM-CXH1, ORM-CXH1-
Static mode enabled in the link LL,ORM-CXH1-MS-LL in link
2. Static mode is enabled in any
OAM-CXH1 in link
23 Node Id: <xx>, Hop Id: <yy>, DSE Communication Failed 1. DSE is warm/cold rebooting
Phase Id: <zz>, DSE Status: 2. Chassis housing DSE is
Comms failed unreachable
3. Pre-provisioned DSE is
present
24 Node Id: <xx>, Hop Id: <yy>, DSE control loop is not running 1. DSE in faulted state
Phase Id: <zz>, DSE Status: 2. Invalid mode is configured in
CtrlLoop Not Run DSE (SLTE Mode 1 in native
automated link etc.)
3. DSE control loop is disabled
4. High loss in fiber connecting
the OSA in port of DSE
5. Connection ports are unclean
6. Alarm OSAPTP LOL or
OSAPTP OPROORL is present
in the DSE
7. High patch loss between
OAM/ORM/BMM and DSE
8. Any upstream band level
faults for which channel power is
low

Table 1-4 List of detail conditions for AGC-NF using FRM headend node
text (New)
1 DAMP LinkDisc timeout ADAPT is unable to discover the 1. OSC failure in downstream
entire link end to end ( FRM to node
FRM) 2. OSC crossover cable is not
connected properly
IAM/IRM is unreachable
IAM/IRM is rebooting
5. Improper association
(between AMP'S and/or FRM's)
6. Incomplete/mismatch IPSEC
configuration
2 Automatic Gain Control (AGC) ADAPT is disabled in the user User initiated configuration
is Disabled interface disabled AGC from user
interface
3 Headend SCH Slice count is ADAPT is unable to get add/drop, 1. Frequent power fluctuation in
Unknown express SCH information for one/ previous link with optical express
more SCH's associated with the configuration
HE FRM 2. Frequent power fluctuation
between LM/FSM with FRM in
ADD/DROP configuration
3. One/more LM/peer FRM/FSM
card is unreachable/warm
rebooting
4. Chassis housing one/more
LM/peer FRM/FSM is
unreachable
5. SCH OPT-OOR-H/L present
in any of the SCH of HE FRM
6. SCH OPR-OOR-L present in
any of the SCH of HE FRM
7. Equipment degradation for of
the associate LM/FSM due to
DSP Access Failure
4 Node Id: <xx>, Phase Id: <zz>: ADAPT gain commit failed Link parameters are out of range
GAIN_COMMIT_FAILED
5 Node Id: <xx>, Phase Id: <zz>: ADAPT is taking longer time to Unknown error encountered
GainCalc timeout calculate gain in any FRU
6 Node Id: <xx>, Phase Id: <zz>: ADAPT is taking longer time to Unknown error encountered
Commit timeout commit gain in any FRU
7 AckTimer expired ADAPT is taking longer time to Unknown error encountered
return ADAPT status in any FRU

Alarms 1-307
Table 1-4 List of detail conditions for AGC-NF using FRM headend node (continued)
text (New)
8 Node Id: <xx>, Phase Id: <zz>, HE Tx EDFA is shutdown 1. HE FRM is in locked state
Abort Commit: 2. HE FRM is disabled due to
HEAD_TX_EDFA_DISABLED ALS
9 Node Id: <xx>, Phase Id: <zz>, Any downstream IAM/IRM or TE- 1. Any upstream card is in
Abort Commit: EDFA_LOL FRM is in LOL state locked state
2. Span loss too high
10 Node Id: <xx>, Phase Id: <zz>, Any downstream IAM/IRM or TE- 1. TE FRM is locked
Abort Commit: FRM is in disable state 2. EDFA disabled due to ALS
EDFA_DISABLED
11 Node Id: <xx>, Phase Id: <zz>, One/more Rx fiber type is set as 1. User configured Tx fiber type
Abort Commit: unknown as unknown to the upstream
RX_FIBER_TYPE_UNKNOWN node
12 Node Id: <xx>, Phase Id: <zz>, One/more Tx fiber type is set as 1. User configured Tx fiber type
Abort Commit: unknown as unknown to the current node
TX_FIBER_TYPE_UNKNOWN
13 Node Id: <xx>, Phase Id: <zz>, ADAPT is not doing gain commit Link is not doing gain commit
Abort Commit: AGC is not due to AGC-NF in previous link
doing gain commit
14 Node Id: <xx>, Phase Id: <zz>, one/more DSP component of the 1. FRE DSP access fail alarm in
Abort Commit: downstream IAM/IRM/FMM/FSM the associated FRU
DSP_ACCESS_FAIL is in access failed state 2. FRW DSP access fail alarm in
the associated FRU
3. EDFA|RAMAN DSP access
fail alarm in the associated FRU
4. Hw fault
Note: The AGC-NF alarm with any condition mentioned above in Table 5-5 and Table 5-6 can be
cleared by clearing at least one of the probable root causes provided. For more information refer to
the detailed condition on the Span Properties window.
Clearing Procedure
1. Manually enable the AGC.

2. If this problem persists, contact the Technical Assistance Center (TAC).

EQP0070
NO-CTRLR-MODULE-REDUNDANCY
Redundant Controller Module not Physically Present

Description
This alarm is generated by the chassis when there is no redundant IMM/MCM/OMM/XCM physically
installed in the DTC/MTC/XTC.
Clearing Procedure
1. Install a redundant IMM/MCM/OMM/XCM in the DTC/MTC/XTC.


Alarms 1-309
EQP0071
INCOMPATIBLE-DSE
Incompatible DSE

■ Applicable Circuit Packs - DSE
Description
This alarm is generated when an older version DSE containing an unsupported modulation format signal
is detected in a link requiring baud rates higher than 11.1Gbps.
Clearing Procedure
1. Install a known compatible DSE (with revised OPM calibration) in the DTC/MTC/XTC.
2. If this problem persists, contact the Technical Assistance Center (TAC).

EQP0072
TEMP-OORH-DEVICE-AUTOSHUTDOWN
Temperature Out Of Range High-Device Auto Shutdown

■ Applicable Circuit Packs - DLM, XLM, TEM
Description
This alarm is generated by the DLM, XLM, TEM.
This alarm is generated when the temperature of this circuit pack is greater (or lesser) than the
predefined threshold value. Allowing the device to function at the same temperature will result in damage
and hence will be powered down.
This alarm is most likely caused due to a combination of ambient temperature and system fan problem.
Clearing Procedure
(TAC).
1. Ensure that ambient temperature is within expected range.

3. Ensure the air filter is clean.

Alarms 1-311
EQP0073
SPECTRUM-NOT-ATTAINED
DSE Output Spectrum not Attained

■ Applicable Circuit Packs - DSE
Description
This alarm is generated by the DSE.
After an equalization event trigger, if the DSE is not converged within 3 cycles, this alarm will be
generated. The alarm is applicable irrespective of whether the DSE is operating in Native Automated or
SLTE mode and will continue to be reported as long as the condition exists and will be cleared only after
a successful equalization event.
Clearing Procedure
1. Ensure that the per-channel and/or per-OCG offsets for the head-end node are set properly.
2. Ensure that the channel map changes for the head-end/express node are set properly.
3. Ensure that the power difference between adjacent channels provided in the power profile for the DSE
does not exceed 3dB.
4. If a change was recently made to the relative power profile for the DSE, re-adjust the power profile
settings.

EQP0074
SWITCH-FABRIC-FAIL
Switch Fabric Fail

Description
This alarm is generated by the chassis.
This alarm is raised against the chassis when there are less than 8 active OXMs in a XTC-10 or 4 active
OXMs in a XTC-4 chassis.
Clearing Procedure
■ Ensure minimum number of 8 active switch modules are present in the chassis for XTC-10.
■ Ensure minimum number of 4 active switch modules are present in the chassis for XTC-4.

Alarms 1-313
EQP0075
SWITCH-PROTECTION-UNAVAILABLE
Switch Fabric Protection Unavailable

■ SA/NSA - NSA (Non - Service Affecting)
Description
This alarm is raised when there are no redundant switch modules available in a standby state for a
switchover.
Clearing Procedure
1. Insert at least one standby switch module which can be switched in case of failure on any of the active
XM.
2. Change the OXM status Lock to Unlock state.

EQP0077
TIMING-SOURCE-MISMATCH
Timing Source Mismatch

Description
This alarm is raised when there is a mismatch of actual timing source latched on the equipment (OLM,
OTM, switch module, TSM and XCM slots) against the evaluated acting timing source of the system.
This alarm is raised on a periodic audit of the timing sources or on every equipment failure or removal.
Clearing Procedure
■ Use the correlation of internal status of the timing sources, the equipment status and CSTS
commands to switch the source or locking of specific timing sources to effect a timing source
switch.

Alarms 1-315
EQP0078
TSM-UNAVAILABLE
Timing And Synchronization Module Unavailable

Description
This alarm is raised if chassis has no TSM FRU available as active clock source.
Clearing Procedure
1. Insert a TSM module into a TSM slot.

2. Check for at least one TSM ready to go active and not faulted.

EQP0079
TSM-NON-REDUNDANT
Timing And Synchronization Module not redundant

Description
This alarm is raised when a chassis has TSMs in a non-redundant configuration.
Clearing Procedure
1. Insert a redundant TSM into the XTC- 10 chassis.

2. Insert or unlock a redundant TSM.

Alarms 1-317
EQP0080
PWR-PROT-FAIL
Chassis power protection failed

■ SA/NSA - NSA (Non Service Affecting)
Description
This alarm is raised when the system does not have power redundancy, where the number of active
feeds on groupA and groupB are not equal.
Note: There are 3 Power Entry Modules in each the group (A and B) in XTC 10 and 2 Power Entry
Modules in each group (A and B) in XTC-4. Each module has 2 feeds.
Clearing Procedure
■ Insert the active feeds into group A and group B.

EQP0081
REM-CHNL-PLAN-MSMT
Remote Equipment Channel Plan Mismatch

■ Applicable Circuit Packs - OLX, OLM, AOFX, AOFM
Description
This alarm is generated by the OLX, OLM, AOFX, AOFM.
This alarm is raised when the remote line card has different channel plan than the local line card.
Clearing Procedure
1. Insert same channel plan on both line cards (local and remote)
2. Re-provision local or remote such that they have same channel plan.

Alarms 1-319
EQP0082
PWRCTRL-INIT
Power Control: System needed power is more than available power

Description
This alarm is generated when there is no enough input power (from PEM/Feed) to power up all FRU's
installed in the chassis, or when the input power is less than the minimum recommended power (which is
4558W for XTC-10 and 2389W for XTC-4).
Clearing Procedure
■ Insert (or Add) more PEM’s/FEED’s.

EQP0083
LOCKED-SOURCE-ACTIVE
Locked Sync Source Active

Description
This alarm is raised when a timing source that has been locked has been selected as the active timing
source for the system. This alarm is seen when the system in the absence of any other timing source,
uses a locked timing source as the active timing source overriding the administrative state.
Clearing Procedure
Contact the Technical Assistance Center (TAC). See for contact details.

Alarms 1-321
EQP0084
EQPTCOMFAIL
Equipment Communication Fail

■ Applicable Circuit Packs - FMMC, FBM, FMMF250, OPSM, OXM, OTXM, XCM, XCMH, OTM,
OLM, OLX, FAN, PEM, AOFM, FRM, IMM, AOFX, FSM, TIM
Description
This alarm is generated by the OXM, XCM, OTM, OLM, OLX, OTXM, TSM, FAN, PEM, AOFMAOFM,
FRM, IMM, AOFX, TIM, FSE, FSM.
This alarm is generated because of the communication failure between the XCM and the different slot
entities (cards). This alarm can also be raised due to hardware failures or malfunction.In case of PEM,
this alarm is raised due to the failure of all 48V inputs.
Clearing Procedure
1. Initiate a warm reset of the card (if supported)

2. Cold reboot of card
3. Card reset
4. If the condition does not go away, it is an indication of a hardware failure and the card needs to be
returned back to Infinera via a RMA procedure.

EQP0085
LOCKED-SWITCH-ACTIVE
Locked Switch Module Active

■ Applicable Circuit Packs - OXM
Description
This alarm is generated by the OXM.
This alarm is generated when an administratively locked switch module has a redundancy status of
"Active".
■ A conflict between provisioned information (Locked/Unlocked) and switch redundancy status
information (Active/Standby).
Clearing Procedure
■ Unlock the admin status of the noted switch modules from the management interface
■ Issue a manual switch on this switch module.

Alarms 1-323
EQP0086
MODEMSMT
Operating Mode Mismatch

■ Applicable Circuit Packs - GAM-1
Description
This alarm is generated by the GAM-1.
This alarm is generated when there is a mismatch between the provisioned operating mode and the
installed operating mode.
Clearing Procedure
■ Take steps such that provisioned operating mode matches the installed operating mode.

EQP0087
DEGRADED-CONFIG
Degraded Configuration

■ Applicable Circuit Packs - TOM-10G-SFPP-IR2, TOM-10G-SFPP-LR2
Description
This alarm is generated by TOM-10G-SFPP-IR2 and TOM-10G-SFPP-LR2.
This alarm is generated when a 2 Port 10G TIM D-SNCP is provisioned on an DTN-X node configuration
that does not support sub-50ms switching time. Note that only the TOMs with the CLEI WOTRCUPLAA
and WOTRCURLAA for TOM-10G-SFPP-IR2 and TOM-10G-SFPP-LR2 respectively are affected.
Clearing Procedure
Contact the Technical Assistance Center (TAC). See for contact details.

Alarms 1-325
EQP0088
INIT
Initialization Under Progress

■ Applicable facilities - BMM, DLM, DSE, Fan, FBM, FMMF250, OAM, OLM, OLX, OMM, OTM,
ORM, TAM, DICM, TIM, XICM, TEM, TOM, OPSM, OTXM, XCMH, TSM, XLM, OXM, AOLx2,
SOLx2, GAM, CMM, Chassis, MCM, XCM, PEM, SCM, RAM, IRM, FSE, IAM, FSM, FRM, IMM,
AOFM, AOFX, PXM
Description
This alarm is generated by BMM, DLM, DSE, Fan, OAM, OLM, OLX, OMM, OTM, ORM, TAM, DICM,
TIM, XICM, TEM, TOM, TSM, XLM, XCMH, OXM, AOLx2, SOLx2, GAM, CMM, Chassis, MCM, XCM,
PEM, SCM, RAM, IRM, FSE, IAM, FSM, FRM, IMM, AOFM, AOFX.
This alarm is generated when an equipment is placed back in a slot and the equipment improper removal
alarm is cleared before the equipment is completely up.
Clearing Procedure
None
It is cleared automatically when the card is fully operational/in -service.

EQP0089
FLASH-FAIL
Flash Device Failed

■ Applicable facilities - FMMC, IMM, IOSHELF
Description
This alarm is generated by FMMC, IMM and IOSHELF.
This alarm is generated when a write operation to the flash device on IOSHELF panel fails.
Clearing Procedure
1. Replace the IO Panel.

Alarms 1-327
EQP0090
GLNA
Ground Lug Not Available

■ Applicable Equipment - PEM

This alarm is generated when the NE detects that a DC PEM is inserted into the XT chassis which does
not support ground lug.
Clearing Procedure
1. Replace DC-PEM with AC-PEM

2. Replace XT Chassis with a chassis which supports ground lug.

EQP0091
AGC-PF
AGC Partially Functioning

■ Applicable facilities - FRM
Description
This alarm is generated by FRM.
This alarm is generated when ADAPT’s Link Discovery State Machine in unable to complete LD within an
OSG specified time interval.
Clearing Procedure
1. Ensure ADAPT LD can discover ADAPT link from HeadEnd to TailEnd.

2. Check OSC connectivity from Head End to Tail End Node and any associated fiber connectivity.

Alarms 1-329
EQP0092
PWR-FAIL
Main Power failure

■ Applicable facilities - PEM
Description
This alarm is generated on the AC PEM’s feed input.
This alarm is generated when the PEM is unable to detect power and breaker is closed. This alarm is
most likely caused by:
■ Faulty/severed power wires coming into the PEM.
Clearing Procedure
1. Check cabling coming into the PEM.

2. Check the power distribution system feeding the PEM.

EQP0093
PEM-TYPE-MISM
PEM Type Mismatch

■ Applicable facilities - PEM
Description
This alarm is generated by PEM.
This alarm is generated when PEM types mismatch within a group.
Clearing Procedure
1. Replace the mismatched PEM type with the same type PEM.

Alarms 1-331
EQP0094
FREQ_PROV_PENDING
User has not provisioned the Frequency

■ Applicable facilities - TOM
Description
This alarm is generated by TOM.
This alarm is generated when the user has not provisioned the tunable frequency on the TOM.
Clearing Procedure
1. Provision the tunable frequency on the TOM with a valid value within the XTM range.

EQP0096
NODE-CONFIG-CHANGED
Node Config Changed

■ Applicable Facilities - IMM, MCM

This alarm is raised if LTS or RSTP Bypass flag is set in Syspvt or Syscfg file. Node checks for these
flags during booting. If either of these flags is set, then the alarm is raised.
Clearing Procedure
To clear the alarm, check which of the flags is set. Remove the flag and reboot the node to clear the
alarm.

Alarms 1-333
EQP0097
EQPT-USB-MISCONN
EQPT USB Misonnection

■ Applicable Facilities - FBM

This alarm is generated by the FBM.
This alarm is raised when the serial number of FBM provisioned on a MTC-6/MTC-9 chassis is detected
on another MTC-6/MTC-9 chassis on the same node due to USB misconnection.
Clearing Procedure
■ Ensure that USB connection of the FBM is connected to the correct extension shelf of MTC-6/
MTC-9 chassis that is provisioned.
■ Disassociate the serial number of the FBM provisioned on the original chassis.

EQP0098
EQPT-USB-NOACCESS-WARNING
Access to USB ports will be lost when module becomes active

■ Applicable Facilities - XTMM, XCMH, IMM, MCM, OMM, XMM, XCM

This alarm is generated by the XTMM, XCMH, IMM, MCM, OMM, XMM, XCM.
This alarm is raised when IMM-A/IMM-B is standby in slot 8 of MTC-9 OR when IMM-A is standby in slot
9.
Clearing Procedure
■ Remove IMM-A/IMM-B from slot 8

■ Rreplace IMM-A with IMM-B in slot 9.

Alarms 1-335
EQP0099
EQPT-USB-NOACCESS
No access to USB ports on IO-PANEL

■ Applicable Facilities - XMM, IMM, MCM, XCM, OMM, XTMM, XCMH

This alarm is generated by the XMM, IMM, MCM, XCM, OMM, XTMM, XCMH.
This alarm is raised when controller card on slot 8 is active or IMM-A in slot 9 is active.
Clearing Procedure
■ Remove IMM-A/IMM-B from slot 8

■ Replace IMM-A with IMM-B in slot 9.

EQP0100
SW-INIT-FAIL
Software Initialization Failure

■ Applicable Facilities - FBM

This alarm is generated by the FBM.
This alarm is raised when software fails to initialize even after 5 restarts within an hour.
Clearing Procedure
■ None

Alarms 1-337
EQP0101
EQPT-USB-POWER-RESET
Equipment is USB power-resetting

■ Applicable Facilities - XM, XLM, XCMH, OAM, OTDM, CMM, IAM, IMM, DSE, OLM, OTM, FBM,
TSM, OTXM, OLX, SCM, MCM, TEM, XCM, RAM, FMMC, DLM, OPSM, BMM, OMM, FRM,
OFM-500, IRM, ORM, OFX-500, FMMF250, XMM, XTMM, FSM, PXM

This alarm is generated by the XM, XLM, XCMH, OAM, OTDM, CMM, IAM, IMM, DSE, OLM, OTM, FBM,
TSM, OTXM, OLX, SCM, MCM, TEM, XCM, RAM, FMMC, DLM, OPSM, BMM, OMM, FRM, OFM-500,
IRM, ORM, OFX-500, FMMF250, XMM, XTMM, FSM, PXM.
This alarm is raised when the USB has been power reset.
Clearing Procedure
■ This alarm is cleared once the applicable circuit pack has reset the power.
Environmental Alarms
Environmental alarms are caused by the change in the state of the environmental alarm input contact.

ENV00(01-16)
PTIN-1 through PTIN-16
Alarm Contact Closure Input 1 through 16
■ Alarm Type - Environmental

■ Severity - Info, not user customizable

There are 16 different input contacts that the user can define to detect various environmental changes.
This alarm is generated when there is a change in the state of an input contact.

Alarms 1-339
ENV0029
TEMP-OOR-DEVICE-SHUTDOWN
Temperature Out Of Range - Device Auto Shutdown
■ Alarm Type - Environmental/Equipment

■ SA/NSA - SA(Service Affecting)
■ Detailed Conditions - RX-EDFA-EXTREME-CASE-TEMP, TX-EDFA-EXTREME-CASE-TEMP,
FRM-FRW-MODULE-SHUTDOWN-TEMP-ORR.

This alarm is raised by the IAM, TSM, OLM, CMM, IRM, OAM, FMMC, FSM, FRM, FSE, GAM, ORM,
OLX, BMM, RAM, OFM-500, OFX-500, OTM, XCM, OXM, and/or REM. This alarm is generated when the
temperature of this circuit pack is greater (or lesser) than the predefined threshold value. Allowing the
device to function at the same temperature will result in damage and hence will be powered down.
This alarm is most likely caused due to a combination of ambient temperature and system fan problem.
Clearing Procedure
Note: Always ensure that the collected debug information is sent to Technical Assistance Center.
1. Ensure that ambient temperature is within expected range.

3. Ensure the air filter is clean.
6. Contact the Technical Assistance Center.
Threshold Crossing Alerts

The network elements performs thresholding on some of the optical PM parameters by utilizing user
configurable high and low threshold values. A threshold crossing alert is reported when the measured
value is above the high threshold or below the low threshold values.

FAC0061
SL-OORH
Span Loss Out of Range - High

■ Detailed Conditions - SPAN-LOSS-HIGH

This alarm is generated by the OAM/BMM/ORM/RAM.
This alarm is generated when the actual span loss exceeds the user defined high span loss threshold.
■ Misconfigured or damaged DCM at the upstream network element
■ BMM/OAM/ORM/RAM failure
■ Improper configuration of the link or span
Clearing Procedure
1. Check the received optical power on this port.

2. Check fiber connectivity on the OAM/BMM/ORM/RAM line port.
3. Ensure the DCM is properly connected.

Alarms 1-341
FAC0062
SL-OORL
Span Loss Out of Range - Low

■ Detailed Conditions - SPAN-LOSS-LOW

This alarm is generated by the OAM/BMM/ORM/RAM.
This alarm is generated when the actual span loss is below the user defined low span loss threshold.
■ Misconfigured or damaged DCM at the upstream network element
■ BMM/OAM/RAM failure
■ Improper configuration of the link or span
Clearing Procedure
1. Check the received optical power on this port.

2. Check fiber connectivity on the OAM/BMM/ORM/RAM line port.
3. Ensure the DCM is properly connected.

FAC0106
PRE-FEC-BER-SD
Pre-FEC BER-based Signal Degrade

■ Applicable Facilities - DCHCTP, OCHCTP
■ Detailed Conditions - PRE-FEC-BER-SD
Description and Causes (PRE-FEC-BER-SD on OCHCTP)

This alarm is generated when the BER prior to the FEC exceeds the predefined threshold value.
Description and Causes (PRE-FEC-BER-SD on DCHCTP)
This alarm is generated when the BER prior to the FEC exceeds the pre-defined threshold value.
Clearing Procedure
1. Check the input power level to the line module.

2. Check for impediment in this channel’s digital span.

Alarms 1-343
FAC0261
TXOCTETS15MINEV
Tx Octets,15-Minutes, Tx TCA
■ TCAA15 - Facility
■ Severity - Event (User provisionable)

This TCA is generated by the PMGigE Client Trib Termination Port and FC Client Termination Point.
This TCA is generated when the number of octets of data received exceeds the number set for a 15-
minute period.
Clearing Procedure
■ A 15-minute TCA is cleared when the subsequent 15-minute interval passes with the threshold not
reached or crossed for that managed object

FAC0130
DTSCV15MINEV
Code Violations, 15-Minutes, Rx TCA

This threshold crossing alert (TCA) is generated by the DTS.
This TCA is generated when the number of code violations received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
■ Faulty transmitter on the client equipment
Clearing Procedure
1. Inspect fiber and ensure it is not pinched in a fiber tray.

2. Clean the fiber.
3. Ensure the fiber is fully connected at both ends

Alarms 1-345
FAC0131
DTSCVDAYEV
Code Violations, 24-Hours, Rx TCA

This TCA is generated by the DTS.
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.
3. Ensure the fiber is fully connected at both ends

FAC0132
DTSES15MINEV
Errored Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of errored seconds received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.
3. Ensure the fiber is fully connected at both ends.

Alarms 1-347
FAC0133
DTPESDAYEV
Errored Seconds, 24-Hours, Rx TCA

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0134
DTSSES15MINEV
Severely Errored Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of severely errored seconds received exceeds the number set
for a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-349
FAC0135
DTSSESDAYEV
Severely Errored Seconds, 24-Hours, Rx TCA

for a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0136
DTPCV15MINEV

This threshold crossing alert (TCA) is generated by the DTPCTP.
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-351
FAC0137
DTPCVDAYEV

This TCA is generated by the DTPCTP.
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0138
DTPES15MINEV

minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-353
FAC0139
DTPESDAYEV

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0140
DTPUAS15MINEV
Unavailable Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of unavailable seconds received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-355
FAC0141
DTPUASDAYEV
Unavailable Seconds, 24-Hours, Rx TCA

This TCA is generated when the number of unavailable seconds received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0142
DTPSES15MINEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-357
FAC0143
DTPSESDAYEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0144
RXBE15MINEV
Block Errors, 15-Minutes, Rx TCA

This threshold crossing alert (TCA) is generated by the SDH Client Trib Termination Point.
This TCA is generated when the number of background errors received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-359
FAC0145
RXBEDAYEV
Block Errors, 24-Hours, Rx TCA

This TCA is generated by the SDH Client Trib Termination Port.
This TCA is generated when the number of background errors received exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0146
RXES15MINEV

minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-361
FAC0147
RXESDAYEV

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0148
RXSES15MINEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-363
FAC0149
RXSESDAYEV
■ TCAA24- Facility

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0150
RXOFS15MINEV
Out of Frame Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of out of frame seconds received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-365
FAC0151
RXOFSDAYEV
Out of Frame Seconds, 24-Hours, Rx TCA

This TCA is generated when the number of out of frame seconds received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0152
RXLOSS15MINEV
LOS seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of loss of signal seconds received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-367
FAC0153
RXLOSSDAYEV
LOS seconds, 24-Hours, Rx TCA

This TCA is generated when the number of loss of signal seconds received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0154
TXBE15MINEV
Block Errors, 15-Minutes, Tx TCA

This threshold crossing alert (TCA) is generated by the SDH Client Trib Termination Point.
This TCA is generated when the number of background errors transmitted exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
■ Faulty receiver on the client equipment
■ Faulty transmitter on the TOM
Clearing Procedure

2. Clean the fiber.

Alarms 1-369
FAC0155
TXBEDAYEV
Block Errors, 24-Hours, Tx TCA

This TCA is generated when the number of background errors transmitted exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0156
TXES15MINEV
Errored Seconds, 15-Minutes, Tx TCA

This TCA is generated by the SONET/SDH Client Trib Termination Port.
This TCA is generated when the number of errored seconds transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-371
FAC0157
TXESDAYEV
Errored Seconds, 24-Hours, Tx TCA

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0158
TXSES15MINEV
Severely Errored Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of severely errored seconds transmitted exceeds the number set
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-373
FAC0159
TXSESDAYEV
Severely Errored Seconds, 24-Hours, Tx TCA

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0160
TXOFS15MINEV
Out of Frame Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of out of frame seconds transmitted exceeds the number set for
a 15-minute period.
■ Facility is not connected to an SDH client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an SDH signal.

3. Clean the fiber.

Alarms 1-375
FAC0161
TXOFSDAYEV
Out of Frame Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of out of frame seconds transmitted exceeds the number set for
a 24-hour period.
■ Facility is not connected to an SDH client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an SDH signal.

3. Clean the fiber.

FAC0162
RXCV15MINEV

This threshold crossing alert (TCA) is generated by the SONET Client Trib Termination Point.
This TCA is generated when the number of code violations errors received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-377
FAC0163
RXCVDAYEV

This TCA is generated by the SONET Client Trib Termination Port.
This TCA is generated when the number of code violation errors received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0164
RXES15MINEV

minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-379
FAC0165
RXESDAYEV

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0166
RXSES15MINEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-381
FAC0167
RXSESDAYEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0168
RXSEFS15MINEV
Severely Errored Frame Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of severely errored frame seconds received exceeds the
number set for a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-383
FAC0169
RXSEFSDAYEV
Severely Errored Frame Seconds, 24-Hours, Rx TCA

number set for a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0170
TXCV15MINEV
Code Violations, 15-Minutes, Tx TCA

This threshold crossing alert (TCA) is generated by the SONET Client Trib Termination Point.
This TCA is generated when the number of code violations transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-385
FAC0171
TXCVDAYEV
Code Violations, 24-Hours, Tx TCA

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0172
TXSES15MINEV
Severely Errored Frame Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of severely errored framed seconds transmitted exceeds the
■ Facility is not connected to a SONET client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an SONET signal.

3. Clean the fiber.

Alarms 1-387
FAC0173
TXSESDAYEV
Severely Errored Frame Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of severely errored framed seconds received exceeds the
■ Facility is not connected to a SONET client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an SONET signal.

3. Clean the fiber.

FAC0174
RXPCSICG15MINEV
PCS Invalid Code Group, 15-Minutes, Rx TCA

1GFC/2GFC/8GFC client (TAM-8-2.5GM) and 10GFC client (TAM-2-10GM).
This TCA is generated when the number of PCS Invalid Code Group received exceeds the number set for
a 15-minute period.
■ Facility is not connected to a GigE client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an Ethernet signal.

3. Clean the fiber.

Alarms 1-389
FAC0175
RXPCSES15MINEV
PCS Errored Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of PCS errored framed seconds received exceeds the number
set for a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0176
RXPCSSES15MINEV
PCS Severely Errored Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of PCS severely errored framed seconds received exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-391
FAC0177
RXPCSSESS15MINEV
PCS Severely Errored Sync Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of PCS severely errored sync seconds received exceeds the
■ Facility is not connected to an GigE client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0178
RXPCSICGDAYEV
PCS Invalid Code Group, 24-Hours, Rx TCA

This TCA is generated when the number of PCS Invalid Code Group received exceeds the number set for
a 24-hour period.
■ Facility is not connected to a valid client signal
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is a valid signal.

3. Clean the fiber.

Alarms 1-393
FAC0179
RXPCSESDAYEV

This TCA is generated when the number of PCS severely errored seconds received exceeds the number
set for a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0180
RXPCSSESDAYEV
PCS Severely Errored Seconds, 24-Hours, Rx TCA

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-395
FAC0181
RXPCSSESSDAYEV
PCS Severely Errored Sync Seconds, 24-Hours, Rx TCA

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0182
RXMACJS15MINEV
MAC Jabber Seconds 15-Minutes Rx TCA

This alarm is generated by the 1GbE (TAM-8-1G) and 10GbE client trib termination point (TAM-2-10GR).
This TCA is generated when the number of MAC Jabber seconds received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-397
FAC0183
RXMACSES15MINEV
MAC Severely Errored Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC severely errored seconds received exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0184
RXMACERROCTET15MINEV
MAC Error Octets, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC error octets received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-399
FAC0185
RXMACJABBER15MINEV
MAC Jabber, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC jabbers received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0186
RXMACFRAGMENT15MINEV
MAC Fragment, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC fragments received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure
1. Ensure client signal is an GigE signal.

3. Clean the fiber.

Alarms 1-401
FAC0187
RXMACCRCALIGNED15MINEV
MAC CRC Aligned, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC CRC aligned received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0188
RXMACUNDERSIZED15MINEV
MAC Undersized, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC undersized packet errors received exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-403
FAC0189
RXMACOVERSIZE15MINEV
MAC OverSized, 15-Minutes, Rx TCA

This TCA is generated when the number of MAC oversized packet errors received exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0190
RXMACJSDAYEV
MAC Jabber Seconds 24-Hours Rx TCA

This TCA is generated when the number of MAC jabber seconds received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-405
FAC0191
RXMACSESDAYEV
MAC Severely Errored Seconds, 24-Hours, Rx TCA

This TCA is generated when the number of MAC severely errored seconds received exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0192
RXMACERROCTETDAYEV
MAC Error Octets, 24-Hours, Rx TCA

This TCA is generated when the number of MAC error octets received exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-407
FAC0193
RXMACJABBERDAYEV
MAC Jabber, 24-Hours, Rx TCA

This TCA is generated when the number of MAC jabbers received exceeds the number set for a 24-hour
period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0194
RXMACFRAGMENTDAYEV
MAC Fragment, 24-Hours, Rx TCA

This TCA is generated when the number of MAC fragment packets received exceeds the number set for
a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-409
FAC0195
RXMACCRCALIGNEDDAYEV
MAC CRC Aligned, 24-Hours, Rx TCA

This TCA is generated when the number of MAC CRC aligned errors received exceeds the number set
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0196
RXMACUNDERSIZEDDAYEV
MAC Undersized, 24-Hours, Rx TCA

This TCA is generated when the number of MAC undersized packet errors exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-411
FAC0197
RXMACOVERSIZEDAYEV
MAC OverSized, 24-Hours, Rx TCA

This TCA is generated when the number of MAC oversized packet errors received exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0198
TXPCSICG15MINEV
PCS Invalid Code Group, 15-Minutes, Tx TCA

This TCA is generated when the number of PCS invalid code group received exceeds the number set for
a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-413
FAC0199
TXPCSES15MINEV
PCS Errored Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of PCS errored seconds received exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0200
TXPCSSES15MINEV
PCS Severely Errored Seconds, 15-Minutes, Tx TCA

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-415
FAC0201
TXPCSSESS15MINEV
PCS Severely Errored Sync Seconds, 15-Minutes, Tx TCA

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0202
TXPCSICGDAYEV
PCS Invalid Code Group, 24-Hours, Tx TCA

This TCA is generated when the number of PCS invalid code groups received exceeds the number set for
a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-417
FAC0203
TXPCSESDAYEV
PCS Errored Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of PCS errored seconds received exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0204
TXPCSSESDAYEV
PCS Severely Errored Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of PCS severely errored seconds transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-419
FAC0205
TXPCSSESSDAYEV
PCS Severely Errored Sync Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of PCS severely errored sync seconds transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0206
TXMACJS15MINEV
MAC Jabber Seconds 15-Minutes Tx TCA

This TCA is generated when the number of MAC jabber seconds transmitted exceeds the number set for
a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-421
FAC0207
TXMACSES15MINEV
MAC Severely Errored Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC severely errored seconds transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0208
TXMACERROCTET15MINEV
MAC Error Octets, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC error octets transmitted exceeds the number set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-423
FAC0209
TXMACJABBER15MINEV
MAC Jabber, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC jabbers transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0210
TXMACFRAGMENT15MINEV
MAC Fragment, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC fragment packets transmitted exceeds the number set
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-425
FAC0211
TXMACCRCALIGNED15MINEV
MAC CRC Aligned, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC CRC aligned packet errors transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0212
TXMACUNDERSIZED15MINEV
MAC Undersized, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC undersized packet errors transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-427
FAC0213
TXMACOVERSIZE15MINEV
MAC OverSized, 15-Minutes, Tx TCA

This TCA is generated when the number of MAC oversized packet errors transmitted exceeds the number
set for a period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0214
TXMACJSDAYEV
MAC Jabber Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of MAC jabber seconds transmitted exceeds the number set for
a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-429
FAC0215
TXMACSESDAYEV
MAC Severely Errored Seconds, 24-Hours, Tx TCA

This TCA is generated when the number of MAC severely errored seconds transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0216
TXMACERROCTETDAYEV
MAC Error Octets, 24-Hours, Tx TCA

This TCA is generated when the number of MAC error octets transmitted exceeds the number set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-431
FAC0217
TXMACJABBERDAYEV
MAC Jabber, 24-Hours, Tx TCA

This TCA is generated when the number of MAC jabbers transmitted exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0218
TXMACFRAGMENTDAYEV
MAC Fragment, 24-Hours, Tx TCA

This TCA is generated when the number of MAC fragments transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-433
FAC0219
TXMACCRCALIGNEDDAYEV
MAC CRC Aligned, 24-Hours, Tx TCA

This TCA is generated when the number of MAC CRC aligned packet errors transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0220
TXMACUNDERSIZEDDAYEV
MAC Undersized, 24-Hours, Tx TCA

This TCA is generated when the number of MAC undersized packet errors transmitted exceeds the
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-435
FAC0221
TXMACOVERSIZEDAYEV
MAC OverSized, 24-Hours, Tx TCA

This TCA is generated when the number of MAC oversized packet errors transmitted exceeds the number
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0232
RXSIZE64_15MINEV
Rx 64 byte size packets,15-Minutes, Rx TCA

This TCA is generated by the Gigabit Ethernet Client Trib Termination Port.
This TCA is generated when the total number of packets (including bad packets) received that were 64
octets in length (excluding framing bits but including FCS octets) exceeds the number set for a 15-minute
period.
Clearing Procedure

Alarms 1-437
FAC0233
RXSIZE65TO127_15MINEV
Rx 65 to 127 byte size packets,15-Minutes, Rx TCA

This TCA is generated when the total number of packets (including bad packets) received that were
between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets) exceeds
the number set for a 15-minute period.
Clearing Procedure
■ A 15-minute TCA is cleared when a subsequent 15-minute interval passes with the threshold not

FAC0234

Clearing Procedure

Alarms 1-439
FAC0235

Clearing Procedure

FAC0236

between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets)
exceeds the number set for a 15-minute period.
Clearing Procedure

Alarms 1-441
FAC0237

Clearing Procedure

FAC0238
RXSIZE1519TOJUMBO_15MINEV
Rx 1519 to Jumbo size packets,15-Minutes, Rx TCA

between 1519 and Jumbo octets in length inclusive (excluding framing bits but including FCS octets)
Clearing Procedure

Alarms 1-443
FAC0239
RXOCTETS15MINEV
Rx Octets,15-Minutes, Rx TCA

This TCA is generated by the Gigabit Ethernet Client Trib Termination Port and FC Client Termination
Point.
This TCA is generated when the number of octets of data received exceeds the number set for a 15-
minute period.
Clearing Procedure

FAC0240
RXBROADCASTPKTS15MINEV
Rx Broadcast packets,15-Minutes, Rx TCA

This TCA is generated when the total number of good packets received that were directed to the
broadcast address received exceeds the number set for a 15-minute period.
Clearing Procedure

Alarms 1-445
FAC0241
RXMULTICASTPKTS15MINEV
Rx Multicast packets,15-Minutes, Rx TCA

This TCA is generated when the total number of good packets received that were directed to a multicast
address exceeds the number set for a 15-minute period.
Clearing Procedure

FAC0242
RXINPAUSEFRAMES15MINEV
Rx In Pause Frames,15-Minutes, Rx TCA

This TCA is generated when the number of MAC Control frames on this interface with an opcode
indicating the PAUSE operation exceeds the number set for a 15-minute period.
Clearing Procedure

Alarms 1-447
FAC0243
RXSIZE64_DAYEV
Rx 64 byte size packets,24-Hours, Rx TCA

octets in length (excluding framing bits but including FCS octets) exceeds the number set for a 24-hour
period.
Clearing Procedure
■ A 24-hour TCA is cleared when the subsequent 24-hour interval passes with the threshold not

FAC0244
RXSIZE65TO127_DAYEV
Rx 65 to 127 byte size packets,24-Hours, Rx TCA

the number set for a 24-hour period.
Clearing Procedure

Alarms 1-449
FAC0245
RXSIZE128TO255_DAYEV

Clearing Procedure

FAC0246

Clearing Procedure

Alarms 1-451
FAC0247

exceeds the number set for a 24-hour period.
Clearing Procedure

FAC0248

Clearing Procedure

Alarms 1-453
FAC0249
RXSIZE1519TOJUMBO_DAYEV
Rx 1519 to Jumbo size packets,24-Hours, Rx TCA

Clearing Procedure

FAC0250
RXOCTETSDAYEV
Rx Octets,24-Hours, Rx TCA

This TCA is generated by the Gigabit Ethernet Client Trib Termination Port and FC Client Termination
Point.
This TCA is generated when the number of octets of data received exceeds the number set for a 24-hour
period.
Clearing Procedure

Alarms 1-455
FAC0251
RXBROADCASTPKTSDAYEV
Rx Broadcast packets,24-Hours, Rx TCA

broadcast address received exceeds the number set for a 24-hour period.
Clearing Procedure

FAC0252
RXMULTICASTPKTSDAYEV
Rx Multicast packets,24-Hours, Rx TCA

address exceeds the number set for a 24-hour period.
Clearing Procedure

Alarms 1-457
FAC0253
RXINPAUSEFRAMESDAYEV
Rx In Pause Frames,24-Hours, Rx TCA

indicating the PAUSE operation exceeds the number set for a 24-hour period.
Clearing Procedure

FAC0254
TXSIZE64_15MINEV
Tx 64 byte size packets,15-Minutes, Tx TCA

octets in length (excluding framing bits but including FCS octets) exceeds the number set for a 15-minute
period.
Clearing Procedure

Alarms 1-459
FAC0255
TXSIZE65TO127_15MINEV
Tx 65 to 127 byte size packets,15-Minutes, Tx TCA

Clearing Procedure

FAC0256

Clearing Procedure

Alarms 1-461
FAC0257

Clearing Procedure

FAC0258

Clearing Procedure

Alarms 1-463
FAC0259

Clearing Procedure

FAC0260
TXSIZE1519TOJUMBO_15MINEV
Tx 1519 to Jumbo size packets,15-Minutes, Tx TCA

Clearing Procedure

Alarms 1-465
FAC0262
TXBROADCASTPKTS15MINEV
Tx Broadcast packets,15-Minutes, Tx TCA

broadcast address received exceeds the number set for a 15-minute period.
Clearing Procedure

FAC0263
TXMULTICASTPKTS15MINEV
Tx Multicast packets,15-Minutes, Tx TCA

This TCA is generated by the GigE Client Trib Termination Port.
address exceeds the number set for a 15-minute period.
Clearing Procedure

Alarms 1-467
FAC0264
TXOUTPAUSEFRAMES15MINEV
Tx Out Pause Frames,15-Minutes, Tx TCA

indicating the PAUSE operation exceeds the number set for a 15-minute period.
Clearing Procedure

FAC0265
TXSIZE64_DAYEV
Tx 64 byte size packets,24-Hours, Tx TCA

This TCA is generated when the total number of packets (including bad packets) transmitted that were 64
octets in length (excluding framing bits but including FCS octets) exceeds the number set for a 24-hour
period.
Clearing Procedure

Alarms 1-469
FAC0266
TXSIZE65TO127_DAYEV
Tx 65 to 127 byte size packets,24-Hours, Tx TCA

Clearing Procedure

FAC0267
TXSIZE128TO255_DAYEV

Clearing Procedure

Alarms 1-471
FAC0268

Clearing Procedure

FAC0269

Clearing Procedure

Alarms 1-473
FAC0270

Clearing Procedure

FAC0271
TXSIZE1519TOJUMBO_DAYEV
Tx 1519 to Jumbo size packets,24-Hours, Tx TCA

Clearing Procedure

Alarms 1-475
FAC0272
TXOCTETSDAYEV
Tx Octets,24-Hours, Tx TCA
■ SA/NSA - NSA

This TCA is generated when the number of octets of data transmitted exceeds the number set for a 24-
hour period.
Clearing Procedure

FAC0273
TXBROADCASTPKTSDAYEV
Tx Broadcast packets,24-Hours, Tx TCA

This TCA is generated when the total number of good packets transmitted that were directed to the
broadcast address received exceeds the number set for a 24-hour period.
Clearing Procedure

Alarms 1-477
FAC0274
TXMULTICASTPKTSDAYEV
Tx Multicast packets,24-Hours, Tx TCA

This TCA is generated when the total number of good packets transmitted that were directed to a
multicast address exceeds the number set for a 24-hour period.
Clearing Procedure

FAC0275
TXOUTPAUSEFRAMESDAYEV
Tx Out Pause Frames,24-Hours, Tx TCA

indicating the PAUSE operation exceeds the number set for a 24-hour period.
Clearing Procedure

Alarms 1-479
FAC0276
RXPACKETS15MINEV
Rx Packets,15-Minutes, Rx TCA

This TCA is generated when the number of packets received exceeds the number set for a 15-minute
period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0277
RXPACKETSDAYEV
Rx Packets,24-Hours, Rx TCA

This TCA is generated when the number of packets received exceeds the number set for a 24-hour
period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-481
FAC0278
TXPACKETS15MINEV
Tx Packets,15-Minutes, Tx TCA

This TCA is generated when the number of packets transmitted exceeds the number set for a 15-minute
period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

FAC0279
TXPACKETSDAYEV
Tx Packets,24-Hours, Tx TCA

This TCA is generated when the number of packets transmitted exceeds the number set for a 24-hour
period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

3. Clean the fiber.

Alarms 1-483
FAC0284
DTPTXCV15MINEV
Code Violations, 15-Minutes, Tx TCA

This threshold crossing alert (TCA) is generated by the Trib DTF path of a TAM-2-10GT and represents
the error in the line side (Tx direction).
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0285
DTPTXCVDAYEV
Code Violations, 24-Hours, Tx TCA

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-485
FAC0286
DTPTXES15MINEV
Errored Seconds, 15-Minutes, Tx TCA

minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0287
DTPTXESDAYEV
Errored Seconds, 24-Hours, Tx TCA

hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-487
FAC0288
DTPTXUAS15MINEV
Unavailable Seconds, 15-Minutes, Tx TCA

This TCA is generated when the number of unavailable seconds transmitted exceeds the number set for
a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0289
DTPTXUASDAYEV
Unavailable Seconds, 24-Hours, Tx TCA

a 24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-489
FAC0290
DTPTXSES15MINEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0291
DTPTXSESDAYEV

■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-491
FAC0303
■ Applicable Facilities - Gigabit Ethernet Client CTP

This TCA is generated by the Gigabit Ethernet Client Termination Point.
between 1024 and 1522 octets in inclusive length exceeds the threshold value set for a 15-minute period.
Clearing Procedure
reached or crossed for that network element.

FAC0304
RXSIZE1523TOJUMBO_15MINEV
Rx 1523 to Jumbo size packets,15-Minutes, Rx TCA

This TCA is generated when the total number of packets (including bad packets) received that were 1523,
or more, octets exceeds the threshold value set for a 15-minute period.
Clearing Procedure
■ A 15-minute TCA is cleared when a subsequent 15-minute hour interval passes with the threshold
not reached or crossed for that managed object

Alarms 1-493
FAC0305

between 1024 and 1522 octets exceeds the threshold value set for a 24-hour period.
Clearing Procedure
■ A 24-hour TCA is cleared when a subsequent 24-hour interval passes with the threshold not

FAC0306
RXSIZE1523TOJUMBO_DAYEV
Rx 1523 to Jumbo size packets,24-Hours, Rx TCA

or more octets exceeds the threshold value set for a 24-hour minute period.
Clearing Procedure

Alarms 1-495
FAC0307

This TCA is generated when the total number of packets (including bad packets) transmitted that were
between 1024 and 1522 octets exceeds the threshold value set for a 15-minute period.
Clearing Procedure

FAC0308
TXSIZE1523TOJUMBO_15MINEV
Tx 1523 to Jumbo size packets,15-Minutes, Tx TCA

1523 or more octets exceeds the threshold value set for a 15-minute period.
Clearing Procedure

Alarms 1-497
FAC0309

between 1024 and 1522 octets exceeds the threshold value set for a 24-hour period.
Clearing Procedure
reached or crossed for that managed object.

FAC0310
TXSIZE1523TOJUMBO_DAYEV
Tx 1523 to Jumbo size packets, 24-Hours, Tx TCA

1523 or more octets exceeds the threshold value set for a 24-hour period.
Clearing Procedure

Alarms 1-499
FAC0326
TXUAS15MINEV
Unavailable Seconds, 15-Minutes, Tx TCA
■ Severity - Event (User Customizable)
■ Applicable Facilities - SDH client CTP

This TCA is generated by the network element on the SDH client termination point..
a 15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0327
TXUASDAYEV
Unavailable Seconds, 24-Hours, Tx TCA

This TCA is generated by the network element on the SDH client termination point.
This TCA is generated when the number of unavailable seconds transmitted exceeds the threshold
seconds set for a 24-hour period.By default, this alert is disabled.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-501
FAC0328
RXUAS15MINEV
Unavailable Seconds, 15-Minutes, Rx TCA

This TCA is generated when the number of unavailable seconds received exceeds the threshold value
■ Dirty fiber
■ Pinched fiber
■ Faulty receiver on the TAM, DICM
Clearing Procedure

2. Clean the fiber.
5. Check for the equipment failure alarms reported by the TAM, DICM.

FAC0329
RXUASDAYEV
Unavailable Seconds, 24-Hours, RX TCA

This TCA is generated when the number of unavailable seconds received exceeds the threshold value
■ Dirty fiber
■ Pinched fiber
■ Faulty receiver on the TAM, DICM
Clearing Procedure

2. Clean the fiber.
5. Check for the equipment failure alarms reported by the TAM, DICM.

Alarms 1-503
FAC0337
RXERROREDOCTETS15MINEV
Errored Octets, 15-Minutes, Rx TCA

This alarm is generated by the 1GFC/2GFC/8GFC/10GFC Client Trib Termination Port.
This TCA is generated when the number of errored octets received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0338
RXERROREDOCTETSDAYEV
Errored Octets, 24-Hours, Rx TCA

This TCA is generated when the number of errored octets received exceeds the threshold value set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-505
FAC0339
TXERROREDOCTETS15MINEV
Errored Octets, 15-Minutes, Tx TCA

This TCA is generated when the number of errored octets transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0340
TXERROREDOCTETSDAYEV
Errored Octets, 24-Hours, Tx TCA

This TCA is generated when the number of errored octets transmitted exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-507
FAC0341
RXFCSESS15MINEV

This TCA is generated by the 1GFC/2GFC/8GFC/10GFC Client Trib Termination Port.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0342
RXFCSESDAYEV

This TCA is generated by 1GFC/2GFC/8GFC/10GFC Client Trib Termination Port.
This TCA is generated when the number of Fiber Channel Severely Errored Seconds received exceeds
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-509
FAC0343
TXFCSES15MINEV

This TCA is generated by the 1GFC/2GFC/8GFC/10GFC Client Trib Termination Port.
This TCA is generated when the number of Fiber Channel Severely Errored Seconds transmitted
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0344
TXFCSESDAYEV

This TCA is generated by the 1GFC/2GFC/8GFC/10GFC Client Trib Termination Point.
This TCA is generated when the number of Fiber Channel Severely Errored Seconds transmitted
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-511
FAC0345
RXFRAMES15MINEV
Frames, 15-Minutes, Rx TCA

This TCA is generated when the number of frames received exceeds the number set for a 15-minute
period.
Clearing Procedure
■ Increase the threshold value set for this event to considerable value

FAC0346
RXFRAMESDAYEV
Frames, 24-Hours, Rx TCA

This TCA is generated when the number of frames received exceeds the number set for a 24-hour period.
Clearing Procedure

Alarms 1-513
FAC0347
TXFRAMES15MINEV
Frames, 15-Minutes, Tx TCA

This TCA is generated when the number of frames transmitted exceeds the number set for a 15-minute
period.
Clearing Procedure

FAC0348
TXFRAMESDAYEV
Frames, 24-Hours, Tx TCA

This TCA is generated when the number of frames transmitted exceeds the number set for a 24-hour
period.
Clearing Procedure

Alarms 1-515
FAC0349
RXERROREDFRAMES15MINEV
Errored Frames, 15-Minutes, Rx TCA

This TCA is generated when the number of errored frames received exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0350
RXERROREDFRAMESDAYEV
Errored Frames, 24-Hours, Rx TCA

This TCA is generated when the number of errored frames received exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-517
FAC0351
TXERROREDFRAMES15MINEV
Errored Frames, 15-Minutes, Tx TCA

This TCA is generated when the number of errored frames transmitted exceeds the number set for a 15-
minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0352
TXERROREDFRAMESDAYEV
Errored Frames, 24-Hours, Tx TCA

This TCA is generated when the number of errored frames transmitted exceeds the number set for a 24-
hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-519
FAC0353
RXEB15MINEV
Errored Blocks, 15-Minutes, Rx TCA
OTUki CTP

This TCA is generated by the network element.
This TCA is generated when the number of errored blocks received exceeds the threshold value set for a
15-minute period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0354
RXEBDAYEV
Errored Blocks, 24-Hours, Rx TCA
OTUki CTP

This TCA is generated when the number of errored blocks received exceeds the threshold value set for a
24-hour period.
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-521
FAC0355
RXDS15MINEV
Defect Seconds, 15-Minutes, Rx TCA
■ Severity - Event (User customizable)
OTUki CTP

This TCA is generated when the number of defect seconds received exceeds the threshold value set for a
15-minute period.
Clearing Procedure
■ The 15-minute TCA is cleared when a subsequent 15-minute interval passes with the threshold not

FAC0356
RXDSDAYEV
Defect Seconds, 24-Hours, Rx TCA
OTUki CTP

24-hour period.
Clearing Procedure
■ The 24-hour TCA is cleared when a subsequent 24-hour interval passes with the threshold not

Alarms 1-523
FAC0357
TXEB15MINEV
Errored Blocks, 15-Minutes, Tx TCA
■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, OTU Client CTP, OTUki CTP

This TCA is generated when the number of errored blocks transmitted exceeds the threshold value set for
a 15-minute period.
Clearing Procedure

FAC0358
TXEBDAYEV
Errored Blocks, 24-Hours, Tx TCA

This TCA is generated when the number of errored blocks transmitted exceeds the threshold value set for
a 24-hour period.
Clearing Procedure

Alarms 1-525
FAC0359
TXDS15MINEV
Defect Seconds, 15-Minutes, Tx TCA

15-minute period.
Clearing Procedure

FAC0360
TXDSDAYEV
Defects Seconds, 24-Hours, Tx TCA
■ SA/NSA - SA (Service-Affecting), OTUki CTP

24-hour period.
Clearing Procedure

Alarms 1-527
FAC0362
RXBEI15MINEV
Backward Error Indication Counts, 15-Minutes, Rx TCA
■ Applicable Facilities - ODUk Client CTP, OTUKi CTP

This TCA is generated when the number of Backward Error Indication received exceeds the threshold
value for a 15-minute period.
Clearing Procedure
■ The 15-minute TCA is cleared when a subsequent 15-minute interval passes without the Backward
Error Indication count for that network element reaching or exceeding the threshold value

FAC0363
RXBEIDAYEV
Backward Error Indication Counts, 24-Hours, Rx TCA
■ Applicable Facilities - ODUkT Client CTP, OTUKi CTP

value for the 24-hour period.
Clearing Procedure
■ The 24-hour TCA is cleared when a subsequent 24-hour interval passes without the Backward
Error Indication count for that network element reaching or exceeding the threshold value

Alarms 1-529
FAC0382
TXBEI15MINEV
Transmit Backward Error Indication Counts, 15-Minutes, Tx TCA
■ Severity - Event

value for a 15-minute period.
Clearing Procedure
The 15-minute TCA is cleared when a subsequent 15-minute interval passes without the Backward Error
Indication count for that network element reaching or exceeding the threshold value.

FAC0383
TXBEIDAYEV
Transmit Backward Error Indication Counts, 24-Hours, Tx TCA

This TCA is generated when the number of Backward Error Indication received from network side
exceeds the threshold value for the 24-hour period.
Clearing Procedure
The 24-hour TCA is cleared when a subsequent 24-hour interval passes without the Backward Error
Indication count for that network element reaching or exceeding the threshold value.

Alarms 1-531
FAC0403
RXDSF15MINEV
Defect Seconds, 15-Minutes, Rx TCA
■ Severity - Event
■ Applicable Facilities - ODUkT, ODUki CTP, OTUCLIENTCTP, ODUk Client, OTUki Section CTP

This TCA is generated when the number of defect seconds received on the far end exceeds the threshold
value set for a 15-minute period.
Clearing Procedure
The 15-minute TCA is cleared when a subsequent 15-minute interval passes with the threshold not

FAC0404
RXDSFDAYEV
Defect Seconds, 24-Hours, Rx TCA
■ Applicable Facilities - ODUki CTP, OTUCLIENTCTP, ODUk Client, OTUki Section CTP, ODUkT

value set for a 24-hour period.
Clearing Procedure

Alarms 1-533
FAC0405
TXDSF15MINEV
Defect Seconds, 15-Minutes, Tx TCA
■ Applicable Facilities - OTUCLIENTCTP, ODUk Client CTP, ODU Client CTP

Clearing Procedure

FAC0406
TXDSFDAYEV
Defect Seconds, 24-Hours, Tx TCA
■ Applicable Facilities - OTUCLIENTCTP, ODUk Client

Clearing Procedure

Alarms 1-535
FAC0412
RXEBF15MINEV
Errored Blocks, 15-Minutes, Rx TCA
■ Applicable Facilities - ODU Client CTP, ODUi Client CTP, OTU Client CTP, OTUKi CTP

This TCA is generated when the number of errored blocks received on the far end exceeds the threshold
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

FAC0413
RXEBFDAYEV
Errored Blocks, 24-Hours, Rx TCA
■ Applicable Facilities - ODUk Client, OTU Client CTP, ODUki CTP, OTUki Section CTP

This TCA is generated by the network element. on the far end
This TCA is generated when the number of errored blocks received on the far end exceeds the threshold
■ Dirty fiber
■ Pinched fiber
Clearing Procedure

2. Clean the fiber.

Alarms 1-537
FAC0414
TXEBF15MINEV
Errored Blocks, 15-Minutes, Tx TCA
■ Applicable Facilities - OTU Client CTP, ODUk Client

This TCA is generated when the number of errored blocks transmitted on the far end exceeds the
threshold value set for a 15-minute period.
Clearing Procedure

FAC0415
TXEBFDAYEV
Errored Blocks, 24-Hours, Tx TCA
■ Applicable Facilities - OTU Client CTP, ODUk Client/CTP

This TCA is generated when the number of errored blocks transmitted on the far end exceeds the
threshold value set for a 15-minute period.
Clearing Procedure

CHAPTER 2
Alarm Masking Hierarchy
IQ NOS provides an alarm masking feature, in which a network element masks (suppresses) reporting of
higher layer failures associated with the same root cause as a higher priority, lower layer, failure. Table
2-1: Alarm Masking Hierarchy on page 2-1 documents the alarm masking hierarchy in tabular format.
Note that Table 2-1: Alarm Masking Hierarchy on page 2-1 lists the alarm masking hierarchy in tabular
format and uses the following conventions:
■ In the ‘Masked Alarm(s)’ column, an italicized alarm indicates the alarm masks additional lower
layer failure alarms
■ In the ‘Masking Alarm(s)’ column, an italicized alarm indicates the alarm is masked by higher layer
failure alarms
For a complete description of each alarm, refer to Alarm Description and Clearing Procedures on
page 1-5.
Table 2-1 Alarm Masking Hierarchy

Alarm Type Masked Alarm(s) Masking Alarm(s)
ADMIN-LOCK (on base card) C-Band OLOS None
ADMIN-LOCK (on ORM-CXH1-MS/ OTS/C-Band/OSC facility alarms OTS/C-Band/OSC alarms due to
ORM-CXH1) OLOS on C-Band
ADMIN-LOCK on BMM2P OTS/C-Band/OSC facility alarms on
OAM booster amp

2-2
Table 2-1 Alarm Masking Hierarchy (continued)

AIS - DTP (Tributary-side)a DE-ENCAP-LOS Client CTPa, TIM - LOF - DTP (Tributary-side)a
DTP (Trib side)a, POST-FEC-BER-
SF DTP (Trib side)a
AIS - La TIM - Sa LOS Client CTP, LOF Client CTPa
AIS - MSa TIM - Sa LOS Client CTP, LOF Client CTPa
AIS-ODUk (Trib Side) TIM - ODUk, PLM - ODUk LOS Client CTP, LOF Client CTP
AIS-ODUkT (Trib Side) TIM-ODUkT LOS Client CTP, LOF Client CTP
AIS-ODUki (Trib Side) TIM-ODUki (Trib), PLM-ODUki (Trib) LOS Client CTP, LOF Client CTP
AIS-ODUkiT (Trib Side) TIM-ODUkiT LOS Client CTP, LOF Client CTP
AIS-ODUki (Line Side) TIM-ODUki (Line), PLM-ODUki (Line) LOS OTUki CTP (Line Side), LOF
OTUki CTP (Line Side)
AIS-ODUkiT (Line Side) TIM-ODUkiT LOS OTUki CTP (Line Side), LOF
OTUki CTP (Line Side)
AIS-OTUk (Trib Side) TIM-OTUk LOS OTUk Client CTP, LOF OTUk
Client CTP
AIS-OTUki (Line Side) TIM-OTUki LOS OTUki CTP (Line Side), LOF
OTU CTP (Line Side)
AMBIENT TEMP OORH (Chassis) TEMP OORH (Any slot/module) None
BANDCTP OLOS (IAM/IRM) None (IAM/IRM/FRM) BANDPTP OLOS
BANDCTP OLOS (FRM) None (FRM) SCGPTP OLOS
BANDCTP OLOS (FRM) None FSE Line SCGPTP OLOS
BANDCTP OLOS (FRM) None FSM Line SCGPTP OLOS
BANDPTP OLOS (FRM) None OFX SCGPTP OLOS
BDI-ODUk (Trib Side) None LOS Client CTP, LOF Client CTP,
AIS-ODUk, LTC-ODUk, OCI-ODUk,
LCK-ODUk, TIM-ODUk if TimActDis
is false
BDI-ODUkT (Trib Side) None LOS Client CTP, LOF Client CTP,
AIS-ODUkT, LTC-ODUkT, OCI-
ODUkT, LCK-ODUkT, TIM-ODUkT
BDI-ODUki (Trib Side) LOS Client CTP, LOF Client CTP,
AIS-ODUki, LTC-ODUki, OCI-ODUki,
LCK-ODUki, TIM-ODUki
BDI-ODUkiT (Trib Side) None LOS Client CTP, LOF Client CTP,
AIS-ODUkiT, LTC-ODUkiT, OCI-
ODUkiT, LCK-ODUkiT, TIM-ODUkiT

Alarm Masking Hierarchy 2-3

BDI-ODUki (Line Side) None LOS OTUki CTP (Line Side), LOF
OTUki CTP (Line Side), AIS-ODUki
(Line), LTC-ODUki (Line), OCI-ODUki
(Line), LCK-ODUki (Line), TIM-ODUki
(Line)
BDI-ODUkiT (Line Side) None LOS OTUkiT CTP (Line Side), LOF
OTUkiT CTP (Line Side), AIS-
ODUkiT (Line), LTC-ODUkiT (Line),
OCI-ODUkiT (Line), LCK-ODUkiT
(Line), TIM-ODUkiT (Line)
BDI-OTUk (Trib Side) None LOS OTUk Client CTP, LOF OTUk
Client CTP, AIS-OTUk, TIM-OTUk
BDI-OTUki (Line Side) None LOS OTUki CTP (Line Side), LOF
OTUki CTP (Line Side), AIS-OTUki,
TIM-OTUki
BDI-P None OSC-OLOS, OCH-FDI-O, OMS-FDI-
O, TIM (if TimActDis is supported and
set to False)
CAC-UNAVAIL None EQPTFAIL
CAC-FAIL None EQPTFAIL
CCM-LOC None Supporting Interface is
administratively or operationally
down. OR Received ETH-AIS PDU
and AIS based suppression is
enabled. OR CCM Is Disabled on the
MEP OR Any other higher severity
Alarm which is present at the same
time OR CCM-MISMERGE, CCM-
UNEXP-LEVEL, CCM-UNEXP-MEP,
CCM-UNEXP-PERIOD, CCM-
UNEXP-PRIO
CCM-MISMERGE None Supporting Interface is
down. OR CCM Is Disabled on the
time.

2-4

CCM-REM-MAC-ERR None Supporting Interface is
CCM-UNEXP-PERIOD, CCM-
UNEXP-PRIO, CCM-LOC
CCM-UNEXP-LEVEL None Supporting Interface is
time OR CCM-MISMERGE
CCM-UNEXP-MEP None Supporting Interface is
UNEXP-LEVEL
CCM-UNEXP-PERIOD None Supporting Interface is
time. OR CCM-MISMERGE, CCM-
UNEXP-LEVEL, CCM-UNEXP-MEP
CCM-UNEXP-PRIO None Supporting Interface is
CCM-UNEXP-PERIOD
CONNECTIVITYFAIL Trib Alarms on DchCTP OLOS (DchCTP)
CONNECTIVITYFAIL Trib Alarms on OTUki CTP OLOS OChCTP
CSF OSC-OLOS, OCH-FDI-O, OMS-FDI-
O, OCH-FDI-P
CTRL-COMM-FAIL-CTRLRA/B (For None IMPROPRMVL (For given controller),
any controller) IMPROPRMVL (For peer controller)


DB-MSMT (For any module) None IMPROPRMVL (For given module)
DE-ENCAP-AIS-L Any Tx/Rx TCA alarm - Client CTP DE-ENCAP-LOS-Client CTP, DE-
ENCAP-LOF-Client CTPa
DE-ENCAP-AIS-MS Any Tx/Rx TCA alarm - Client CTP DE-ENCAP-LOS-Client CTP, DE-
DE-ENCAP-AIS-ODU Any Tx/Rx TCA alarm - Client CTP DE-ENCAP-LOS-Client CTP, DE-
DE-ENCAP-AIS-OTUk (Trib Side Any Tx TCA alarm - Client CTP DE-ENCAP-LOS-OTUk Client CTP,
Only) DE-ENCAP-LOF-OTUk Client CTPa
DE-ENCAP-BDI-ODU Any Tx TCA alarm - Client CTP DE-ENCAP-LOS-Client CTP, DE-
DE-ENCAP-BDI-OTUk (Trib Side Any Tx TCA alarm - Client CTP DE-ENCAP-LOSOTUk Client CTP,
Only) DEENCAP-LOF-OTUk Client CTPa
DE-ENCAP-BER-SF(SONET/SDH None DE-ENCAP LOF Client CTP
Client CTP)
DE-ENCAP-LF Ethernet DE-ENCAP LOSYNC
DE-ENCAP-LOF Client CTPa None DE-ENCAP-LOS Client CTPa
DE-ENCAP-LOS Client CTP DE-ENCAP-LOF Client CTP AIS - DTP (Tributary-side)a
DE-ENCAP-LOSYNC Any Tx TCA alarm - Client CTP DE-ENCAP-LOS Client CTPa
DE-ENCAP-RF Ethernet DE-ENCAP LOSYNC
DE-ENCAP-LOA Any Tx TCA alarm - Client CTP DE-ENCAP-LOS Client CTPa, DE-
ENCAP-LOLM
DE-ENCAP-LOLM Any Tx TCA alarm - Client CTP, DE- DE-ENCAP-LOS Client CTPa, DE-
ENCAPLOA ENCAP-LOSYNC
ETH-AIS None Supporting Interface is
down. OR Any other higher severity
time.
ETH-RDI None Supporting Interface is
administratively or operationally down
OR CCM-LOC OR CCM Is Disabled
on the MEP OR Any other higher
severity Alarm which is present at the
same time.
ETH-CSF None Supporting Interface is
or Or any other higher severity Alarm
which is present at the same time.

2-6

EQPTCPUR (Any module)(1) EQPTFAIL(2) IMPROPRMVLc
EQPTCPUR - Chassis None Chassis admin-lock, chassis admin-
maint
EQPTCPUR - BMM/OAMb OPR OORH - Banda, SL OORL - None
Banda, OLOS OTSa, OPR OORH -
BMM OCGa, OLOS - OCG (BMM)
EQPTCPUR - DLM/XLMb OLOS OCG (DLM/XLM)a, EQPTFAIL None
- TAM, IMPROPRMVL - TAM
EQPTCPUR - AOLMb OLOS OCG (AOLM)a, EQPTFAIL - None
TIM, IMPROPRMVL - TIM
EQPTCPUR - GAM OLOS OCG (GAM), EQPTFAIL - None
GAM
EQPTDEGRADE (Any module) None EQPTFAIL
EQPTCOMFAIL None EQPTFAIL
EQPTFAIL (Any module) EQPT-PARTFAILc, IMPROPRMVLc, EQPTCPURc
EQPTDEGRADEc, INSUFFICIENT-
GAINc, UNKNOWNFWc
EQPT FAIL (ADLM/AXLM) OCG-MSMT, other Equipment Alarms None
on the ADLM/AXLM
EQPT FAIL (AOLM) OCG-MSMT, other Equipment Alarms None
on the AOLM
EQPTFAIL - BMM/OAM OPR OORH - Banda, SL OORL - IMPROPRMVLc, EQPTCPURc
BMM OCGa, OLOS - OCG (BMM),
OCG MSMT
EQPTFAIL - DLM/XLM OLOS OCG (DLM/XLM)a, OLOS - IMPROPRMVLc, EQPTCPURc
OCG (BMM), EQPTFAIL - TAM,
IMPROPRMVL - TAM
EQPTFAIL - AOLM OLOS OCG (AOLM)a, OLOS - OCG IMPROPRMVLc,
(BMM), EQPTFAIL - TIM, EQPTCPURc
IMPROPRMVL - TIM
EQPTFAIL - GAM OLOS OCG (GAM), OLOS - OCG IMPROPRMVLc, EQPTCPURc
(GAM), EQPTFAIL - GAM,
IMPROPRMVL - GAM
EQPTFAIL - LM-80 None OCh-MSMT, EQPTCPUR, EQPTFAIL
EQPTFAIL - RAM OLOS OTS (RAM) IMPROPRMVLc, EQPTCPURc
EQPTFAIL - TIM EQPTFAIL - TOM, IMPROPRMVL - EQPTFAIL - AOLM, IMPROPRMVL -
TOM AOLM, EQPTCPUR -AOLM


EQPTFAIL - TAM EQPTFAIL - TOM, IMPROPRMVL - EQPTFAIL - DLM/XLM,
TOM IMPROPRMVL - DLM/XLM,
EQPTCPUR - DLM/XLM
EQPTFAIL - TOM OLOS Trib PTPa, LOF - DTP EQPTFAIL - TAM, IMPROPRMVL -
(Tributary-Side)a TAM
EQPTFAIL - TOM OLOS Trib PTPa, LINK-DOWN, CAC- EQPTFAIL - TIM, IMPROPRMVL -
UNAVAIL, CAC-FAIL TIM
EQPTMSMT (Any module) None ADMIN-LOCK, IMPROPRMVLc
EQPT-PARTFAIL (Any module) None EQPTFAILc
EQPT-PROT-FAIL-SLOT-n (Any None IMPROPRMVLc
module)
ETH-CSF None Supporting Interface is
or any other higher severity alarm is
present at the same time.
EXI-MSMT None ODUk ClientCTP, SONET ClientCTP,
SDH ClientCTP
FAC-PRBS-PLM FAC-PRBS-OOS
FLASH-FAIL None ADMIN-LOCK (chassis), EQPTFAIL,
IMPROPRMVL
FREQ_PROV_PENDING All TOM Equipment alarms
FDI-P OSC-OLOS, OMS-FDI-O, OCH-FDI-
O
FDI-O OSC-OLOS
GFP-LFD Alarms on FCClientCTP, Alarms on LOS ClientCTP (ODU), LOF
GbeClientCtp ClientCTP (ODU)
GFP-CSF (far end) DE-ENCAP-LOS, DE-ENCAP- Server layer Alarms such as Alarms
LOSYNC on ODU Client CTP
GFP-UPI-MSMT Alarms on contained object - Server layer Alarms such as Alarms
FCClientCTP, GbeClientCTP on ODU Client CTP
GFP-EXI-MSMT Alarms on contained object - Server layer Alarms such as Alarms
FCClientCTP, GbeClientCTP on / ODU Client CTP
GLNA None IMPROPRMVL
GMPLS CONFIG MSMTa None LOC OSCa
GMPLS NBR Downa None LOC OSCa
GRE-TUNNEL-ADDRESS-MSMT None GMPLS-NBR-DOWN

2-8

IGCCFAIL EQPT-FAIL, EQPT-IMPROPRMVL,
EQPT-CPUR, IGCC-ADMIN-LOCK,
OCGPTP-OLOS/ SCGPTP-OLOS,
REM-PORT-FEC-MSMT, REM-
PORT-ENCODING-MODE-MSMT,
REM-SCH-PARAMETERS-MSMT,
IMPROPRMVL (Any module) EQPTCPUR c, EQPTFAILc, None
EQPTMSMTc, DB-MSMTc,
UNKNOWNFWc, TEMP-OORHc,
OLDREV-CTRLRc, TEMP-{OOR-
DEVICE, OORH-PIC}-SHUTDOWNc,
OSC-COMM-FAIL-CTRLRA/Bc,
(3),PEER-CTRLR-COMM-FAILc,d,
CTRL-COMM-FAIL-CTRLRA/Bc,d,
EQPT-PROT-FAIL-SLOT-nc,d
IMPROPRMVL - BMM/OAM OPR OORH - Banda, SL OORL - None
BMM OCGa, OLOS - OCG (BMM)
IMPROPRMVL - DLM/XLM OLOS OCG (DLM/XLM)a, OLOS - None
OCG (BMM), EQPTFAIL - TAM,
IMPROPRMVL - TAM
IMPROPRMVL - AOLM OLOS OCG (AOLM)a, OLOS - OCG None
(BMM), EQPTFAIL - TIM,
IMPROPRMVL - TIM
IMPROPRMVL - GAM EQPTFAIL - TOM, IMPROPRMVL - EQPTFAIL - DLM/XLM,
GAM IMPROPRMVL - DLM/XLM,
EQPTCPUR - DLM/XLM
IMPROPRMVL - RAM OLOS OTSa None
IMPROPRMVL - TAM EQPTFAIL - TOM, IMPROPRMVL - EQPTFAIL - DLM/XLM,
TOM IMPROPRMVL - DLM/XLM,
EQPTCPUR - DLM/XLM
IMPROPRMVL - TIM EQPTFAIL - TOM, IMPROPRMVL - EQPTFAIL - AOLM, IMPROPRMVL -
TOM AOLM, EQPTCPUR - AOLM
IMPROPRMVL - TOM OLOS Trib PTP, LOF - DTP (Trib- EQPTFAIL - TAM, IMPROPRMVL -
Sidea TAM
IMPROPRMVL - TOM OLOS Trib PTP, Dlos ClientCTP, EQPTFAIL - TIM, IMPROPRMVL -
LOF Client CTP TIM
INSUFFICIENT-GAIN (Any module) None EQPTFAILc
IntraSchCarrierRipple None SCHCTP alarms : OLOS, OPT-
OORL, OPT-OORH, MUX-OORL
LIC-MF-MISMATCH None License Insufficiency


LOA None LOS, LOSYNC, LOLM
LFD None ODUk Client CTP, SONET Client
CTP, SDH Client CTP
LOF/LOMF None Server layer alarms (OTUk, ODUk
(HO-ODUk))
LOFLANE None LOS
LOLM None LOS, LOSYNC
LCK-ODUk (Trib Side) TIM-ODUk, PLM-ODUk LOS Client CTP, LOF Client CTP
LCK-ODUkT (Trib Side) TIM-ODUkT (Trib) LOS Client CTP, LOF Client CTP
LTC-ODUkT (Trib Side) TIM-ODUkT LOS Client CTP, LOF Client CTP
LCK-ODUki (Trib Side) TIM-ODUki (Trib), PLM-ODUki (Trib) LOS Client CTP, LOF Client CTP
LCK-ODUkiT (Trib Side) TIM-ODUkiT (Trib) LOS Client CTP, LOF Client CTP
LTC-ODUkiT (Trib Side) TIM-ODUkT LOS Client CTP, LOFClient CTP
LCK-ODUki (Line Side) TIM-ODUki (Line), PLM-ODUki (Line) LOS OTUki Client CTP, OTUki LOF
Client CTP
LCK-ODUkiT (Line Side) TIM-ODUkiT (Line) LOS OTUki Client CTP, OTUki LOF
Client CTP
LTC-ODUkiT (Line Side) TIM-ODUkiT LOS OTUkiT CTP (Line Side), LOF
OTUkiT CTP (Line Side)
LOA Client CTP (TIM-1-40GE and ODUk (Trib Side) alarms LOLM, EQPTFAIL, IMPROPRMVL,
TIM-1-100GE) EQPTCPUSR OTM or TIM
LOLM Client CTP (TIM-1-40GE and LOA LOSYNC, EQPTFAIL,
TIM-1-100GE) IMPROPRMVL, EQPTCPUSR OTM
or TIM
LOSYNC Client CTP (TIM-1-40GE LOLM DLOS/OLOS, EQPTFAIL,
and TIM-1-100GE) IMPROPRMVL, EQPTCPUSR OTM
or TIM
LOA-VCG Client CTP (TIM-1-40GE ODUk (Trib Side) alarms EQPTFAIL, IMPROPRMVL,
and TIM-1-100GE) EQPTCPUSR OTM or TIM
LF Ethernet LOS, Ethernet LOSYNC
LINK-DOWN LOLM TribPTP OLOS, TOM EQPTFAIL
LOC OSC GMPLS NBR Down, GMPLS OLOS OTS
CONFIG MSMTa, OSC-IPADDR-
SUBNET-MISMATCHa

2-10

LOF - Channel LOF - DTP (Tributary-side)a, PRE- OLOS OCG (DLM/XLM)a
FEC-BER-SD Channela, POST-FEC-
BER-SF Channela, TIM - DTP (Line-
side)a, TIM - DTSa
LOF - OTUki (Line Side)a BER-SD- OTUki (Line Side)a , TIM- LOS OTUki (Line Side)a ADMIN-
OTUki MAIN-OTUki, EQPTFAIL-AOLM,
IMPRPRRMVLAOLM, EQPTCPUSR-
AOLM
LOF - OTUk (Line Side)a BER-SD- OTUk (Line Side)a , TIM- LOS OTUk (Line Side)a ADMIN-
OTUk MAIN-OTUki, EQPTFAIL-AOLM,
IMPRPRRMVLAOLM, EQPTCPUSR-
AOLM
LOF - Client CTPa RFI - L Client CTP, RFI - MS Client LOS - Client CTPa
CTP, AIS - L Client CTP, AIS - MS
Client CTP
LOF - DTP (Tributary-Side)a AIS - DTP (Tributary-side)a LOF Channela, EQPTFAIL - TOM,
IMPROPRMVL - TOM
LOOMFI Client layer TP alarms (such as LO- Server (OTUk) layer alarms, ODUkP
ODUj or ODUjT alarms) layer failure alarms (such as AIS,
OCI, LCK)
LOS (on Optical Clear Channel None EQPTFAIL, IMPROPRML
interfaces)
LOS - Client CTPa LOF - Client CTPa OLOS Trib PTPa
LOS - OTUki (Line Side)a LOF - OTUki (Line Side)a OPT-OORL-OChCTP, MOD-MSMT-
OchCTP
LOS (XT-500S OChCTP/XT500F LOS on Carrier/OChCTP shall mask XT-500S OCGPTP/XT-500F
CarrierCTP) other Carrier/OchCTP facility alarms SCGPTP OLOS
like Pre/Post FEC SD/SF, PMD
related alarms.
OLOS (DchCTP) CONNECTIVITYFAIL TribPTP OLOS
LOS - OSCTa None OLOS OTSa
LOSYNC LOF - Client CTPa OLOS Trib PTPa
LS-ACTIVE EQPTFAIL, IMPROPRMVL, ALS-
DISABLED
MAC-FLAP None EQPTFAIL
MIS-CONN (Band PTP, None EQPTFAIL
CMMOchPTP, GAM OCG)
MIS-CONN None GAM OCG, Band PTP
MIS-CONN Banda None OLOS OTSa


MOD-MSMT OLOS-OChCTP OTUki layer alarms
MSIM None ODUk PLM
OCG-MSMT (ADLM/AXLM) OL-OORH, PWR-ADJUST- EQPT FAIL (ADLM/AXLM)
INCOMPLETE
OCG-MSMT (ADLM/AXLM OCG EQPTFAIL (ADLM/AXLM
PTP)
OCG-MSMT (AOLM) OL-OORH, PWRADJUST- EQPT FAIL (AOLM)
INCOMPLETE
OCG-MSMT (AOLM OCG PTP) None EQPTFAIL (AOLM)
OCG-TYPE-MSMT None ADMIN-LOCK
OCI-ODUk (Trib Side) TIM-ODUk, PLM-ODUk LOS, LOF Client CTPs
OCI-ODUkT (Trib Side) TIM-ODUkT (Trib) LOS, LOF Client CTPs
OCI-ODUki (Trib Side) TIM-ODUki (Trib), PLM-ODUki (Trib) LOS, LOF Client CTPs
OCI-ODUkiT (Trib Side) TIM-ODUkiT (Trib) LOS, LOF Client CTPs
OCI-ODUki (Line Side) TIM-ODUki (Line), PLM-ODUki (Line) LOS, LOF OTUki (Line Side)
OCI-ODUkiT (Line Side) TIM-ODUkiT LOS, LOF OTUki (Line Side)
OCI OSC-OLOS, OCH-FDI-O, OMS-FDI-
O
ODUk-CSF (@ FAR END Trib Side) DE-ENCAP-LOS, DE-ENCAP- ODUk AIS
LOSYNC
ODUk-MSIM (Trib Side) ODUk-PLM
(Trib Side)
ODUk-PLM (Trib Side) ODUk-MSIM ODUk-AIS, ODUk-LCK, ODUk-OCI,
Server layer (Client CTP alarms)
ODUki-CSF (@ FAR END Trib Side) DE-ENCAP-LOS, DE-ENCAP- ODUki AIS (Trib)
LOSYNC
ODUki-MSIM (Trib Side) ODUki-PLM (Trib Side)
ODUki-PLM (Trib Side) ODUk-MSIM ODUki-AIS, ODUki-LCK, ODUki-OCI,
Server layer (Client CTP alarms)
ODUki-MSIM (Line Side) ODUki-PLM (Trib Side)
ODUki-PLM (Line Side) ODUki-MSIM ODUki-AIS (Line), ODUki-LCK (Line),
ODUki-OCI (Line), Server layer
(OTUki CTP alarms)
OCh-MSMT (LM-80) None OPT-OORL
OCI-ODU LOS, LOF

2-12

OLDP VERSION MISMATCH None OSC-OLOS, IAM/IRM EQPT-FAIL
OLDREV-CTRLR (Any controller) None IMPROPRMVLc
OL-OORH (on C-Band CTP of OPR-OORL (only on express OLOS (on C-Band CTP of BMM2-8-
BMM2-8-CH3-MS/BMM2H-4-R3-MS) OCGPTP on BMM2-8-CH3-MS/ CH3-MS/BMM2H-4-R3-MS)
BMM2H-4-R3-MS)
OL-OORH (BMM2P OTS PTP) None EQPTFAIL, IMPROPRMVL, ADMIN-
LOCK
OL-OORH (on OTS-PTP on ORM- None ADMIN-LOCK, EQPTFAIL of
CXH1-MS/ORM-CXH1) BMM2P, IMPROPRMVL of BMM2P
OLOS (BMM2-8CH3-MS) None OTS-OLOS, Associated DLMOCG
PTP OLOS, Band CTP OLOS on
Extender Card, DSE PTP and OSA
PTP OLOS if associated with a DSE
OLOS (on C-Band CTP of BMM2-8- OL-OORH (on respective C-Band Nonee.
CH3-MS/BMM2H-4-R3-MS) CTP of BMM2-8-CEH3/BMM2H-4-B3)
OLOS Banda OPR OORL - Banda, SL OORH - OLOS OTSa
Banda, OLOS - DCF
OLOS Band (ORM) OLOS-DSE, OLOS-OSA (DSE) OLOS OTS
OLOS - DCF OLOS OCG (DLM/XLM)a,(4), OPR OLOS Banda
OORL - DCF, OPR-OORL-DCF,
OLOS-OSA (DSE)
OLOS (DCF PTP on base card) C-Band OLOS None
OLOS-DSE OLOS - DCF (ORM), OL-OORH-DSE OLOS Band (ORM)
OLOS OCG (BMM) OPR OORL - OCG (BMM) EQPTFAIL - BMM/OAM/GAM/DLM/
XLM, IMPROPRMVL -
BMM/OAM/DLM/XLM, EQPTCPUR -
BMM/OAM/DLM/XLM
OLOS OCG (DLM/XLM)e LOF Channela OLOS - DCF, EQPTFAIL, C Band
OLOS, OTS OLOS, OTS OLOS,
IMPROPRMVL - DLM/XLM,
EQPTCPUR - DLM/XLM
OLOS OCG (AOLM) OLOS OLOS - DCF, EQPTFAIL, C Band
OLOS, OTS OLOS, IMPROPRMVL -
AOLM, EQPTCPUR - AOLM
OLOS-OChCTP (AOLM) MOD-MSMT OChCTP OLOS - OCG (AOLM),
IMPROPRMVL -AOLM, EQPTCPUR
-AOLM
OLOS OCG (GAM) OPR OORL - OCG (GAM) EQPTFAIL - GAM, IMPROPRMVL -
GAM, EQPTCPUR - GAM


OLOS OCh (LM-80) None LOF - DTP (Tributary-side), PRE-
FECBER-SD Channel,
POSTFECBER-SF Channel, TIM -
DTP Line-side), TIM - DTS
OLOS-OSA OPR-OORL-OSA OLOS OTS
OLOS (OSC CTP on BMM2P) ADMIN-LOCK
OLOS OTSa MIS-CONN Banda, OLOS Banda, EQPTFAIL - BMM/OAM,
LOC - OSCa, LOS-OSCT (RAM), IMPROPRMVL - BMM/OAM,
OLOS-DSE, OLOS-OSA EQPTCPUR - BMM/OAM
OLOS OTS (BMM2-8-CH3-MS/ OLOS (on respective C-Band CTPs None(5)
BMM2H-4-R3-MS) of BMM2-8-CEH3/BMM2H-4-B3)
OLOS (OTS on ORM-CXH1-MS/ Facility alarms of OTS/C-Band/OSC None
ORM-CXH1)
OLOS Triba LOS - Client CTPa EQPTFAIL - TOM, IMPROPRMVL -
TOM
OLOS SCG PTP None (OFX,FSE,FSM) EQPTFAIL,
IMPROPRMVL, EQPTCPUR
OL-OORH EQPTFAIL, IMPROPRMVL,
EQPTCPUR
OPR OORH - Banda None EQPTFAIL - BMM/OAM,
IMPROPRMVL - BMM/OAM,
EQPTCPUR - BMM/OAM
OPR OORH - OCG (BMM)a None EQPTFAIL - BMM/OAM,
EQPTCPUR - BMM/OAM
OPR OORH - OCG (GAM)a None EQPTFAIL - GAM, IMPROPRMVL -
GAM, EQPTCPUR - GAM
OPR OORL - Banda None OLOS - Banda
OPR OORL - DCF None OLOS - DCF
OPR OORL - OCG (BMM) None OLOS - OCG (BMM), OL-OORH (on
C-BAND CTP of BMM2-8-CEH3/
BMM2H-4-B3)(6)
OPR OORL - OCG (GAM) None OLOS - OCG (GAM)
OSC-COMM-FAIL-CTRLRA/B (Any None IMPROPRMVLc,d
controller)
OSC-IPADDR-SUBNET- None LOC - OSCa
MISMATCHa
OTSPTP OLOS (IAM/IRM) None (IAM/IRM/FRM) BANDPTP OLOS

2-14

OTSPTP ALS (IAM/IRM) None (IAM/IRM/FRM) BANDPTP OLOS
PEER-CTRLR-COMM-FAIL (Any None IMPROPRMVLc,d
controller)
PLM - DTP (Trib side)a None TIM - DTP (Trib side)c,d
POST-FEC-BER-SF Channela PRE-FEC_BER-SD Channela, POST- LOF - Channela
FEC-BER-SF DTP (Tributary-side)a
POST-FEC-BER-SF DTP (Trib side) None AIS - DTP (Tributary-side)a, POST-
FEC-BER-SF Channela
PRE-FEC-BER-SD Channel None LOF - Channela
PWR48VFAIL None EQPTFAIL (PEM), IMPROPRMVL
(PEM)
PWRCTRL-INIT None ADMIN-LOCK (Chassis), ADMIN-
MAINT (Chassis)
BRKROPEN48V PWR48VFAIL EQPTFAIL (PEM), IMPROPRMVL
(PEM),
PWRUV None EQPTFAIL (PEM), IMPROPRMVL
(PEM), PWR48VFAIL (PEM)
PWROV None EQPTFAIL (PEM), IMPROPRMVL
(PEM), PWR48VFAIL (PEM)
PWR-PROT-FAIL None Chassis Admin Lock, Chassis
admin Main
RF Ethernet LOS, Ethernet LOSYNC
RFI - L (Client CTP)a None LOF - Client CTPa
RFI - MS (Client CTP)a None LOF - Client CTPa
RX-TIM AIS-ODU, AIS-OTU on Client CTP
RX-TIM-ODUk (Trib Side) AIS-ODUk (Trib), LCK-ODUk (Trib),
OCI-ODUk (Trib),
RX-TIM-ODUkT (Trib Side) AIS-ODUkT (Trib), LTC-ODUkT
(Trib), OCI-ODUkT (Trib),
RX-TIM-ODUki (Trib Side) AIS-ODUki (Trib), LCK-ODUki (Trib),
OCI-ODUki (Trib),
RX-TIM-ODUkiT (Trib Side) AIS-ODUkiT (Trib), LTC-ODUkiT
(Trib), OCI-ODUkiT (Trib),
RX-TIM-OTUk (Trib Side) AIS-OTUk (Trib Side)
RX-TIM-ODUki (Line Side) AIS-ODUki (Line), LCK-ODUki (Line),
OCI-ODUki (Line),


RX-TIM-ODUkiT (Line Side) AIS-ODUkiT (Line), LTC-ODUkiT
(Line), OCI-ODUkiT (Line)
RX-TIM-OTUki (Line Side) None AIS-OTUki (Line Side)
SCGPTP OLOS (FSM Line Side) None OFX SCGPTP OLOS
SCGPTP OLOS (FSE Line Side) None OFX SCGPTP OLOS
BASESCGPTP OLOS (FSM) None OFX SCGPTP OLOS
SL-OORH - Banda None OLOS Banda
SL-OORL - Banda None EQPTFAIL - BMM/OAM,
EQPTCPUR - BMM/OAM
SWITCH-FABRIC-FAIL None ADMIN-LOCK, ADMIN-MAINT
SWITCH-PROTECTION- SWITCH-FABRIC-FAIL ADMIN-LOCK, ADMIN-MAINT,
UNAVAILABLE SWITCH-FABRIC-FAIL
TEMP-OOR-DEVICE-SHUTDOWN None IMPROPRMVLc
(Any module)
TEMP-OORH (Any module) None AMBIENT TEMP OORH(7) ,
IMPROPRMVLc
TEMP OORH-PIC-SHUTDOWN None IMPROPRMVLc
(Any module/slot)
TERM-PRBS-PLM TERM-PRBS-OOS
TIM-SCH None OLOS. EQPT-FAIL, IMPROPRMVL
TSM-UNAVAILABLE None ADMIN-LOCK, ADMIN-MAINT
TSM-NON-REDUNDANT None ADMIN-LOCK, ADMIN-MAINT, TSM-
UNAVAILABLE
TIM - Channela None LOF Channela
TIM - DTP (Line side)a None LOF Channela
TIM - DTP (Trib side)a PLM - DTP (Trib side)a AIS - DTP (Trib side)a
TIM-OCG None OLOS
TIM - S None AIS - L Client CTP a, AIS - MS Client
CTPa
TIMING-SOURCE-MISMATCH None None
TX-TIM-ODUk (Trib) None AIS-ODUk (Trib), LCK-ODUk (Trib),
OCI-ODUk (Trib)
TX-TIM-ODUkT (Trib) None AIS-ODUkT (Trib), LTC-ODUkT
(Trib), OCI-ODUkT (Trib)

2-16

TX-TIM-ODUki (Trib) None AIS-ODUki (Trib), LCK-ODUki (Trib),
OCI-ODUki (Trib)
TX-TIM-ODUkiT (Trib) None AIS-ODUkiT (Trib), LTC-ODUkiT
(Trib), OCI-ODUkiT (Trib)
TX-TIM AIS-ODU, AIS-OTU on Client CTP
UPI-MSMT None ODUk ClientCTP, SONET ClientCTP,
SDH ClientCTP
UNKNOWNFW (Any module) None IMPROPRMVLc, EQPTFAILc
VSI-FAIL None EQPT-FAIL, EQPT-IMPROPRMVL
OR Supporting entity is
adminstratively down
VSI-MAC-LIM-DNL-DNF None EQPT-FAIL, OR Supporting entity is
VSI-PARTIAL-FAIL None EQPT-FAIL, EQPT-IMPROPRMVL,
OR Supporting entity is
(1) EQPTCPUR alarm only masks failures below it (in hierarchy) on supported termination points contained in the
module, and not on termination points contained in downstream modules. Further, the EQPTCPUR alarm only
masks higher layer alarms in the cold-reset case.
(2) For the specific module associated with the masking/masked alarm.
(3) For the associated module’s peer module, if the peer exists.
(4) The OLOS OCG (DLM/XLM) alarm is not masked by the IMPROPRMVL - BMM/OAM or EQPTFAIL - BMM/OAM
alarms. This is true, even though a direct path may be traced from the OLOS OCG (DLM/XLM) alarm to the latter
alarms in the alarm masking hierarchy.
(5) OL-OORH and OLOS (on C-Band CTP) is masked on the extender card unless the peer Band PTP association
exists.
(6) OL-OORH (on C-BAND CTP of BMM2-8-CEH3/BMM2H-4-B3) masks OPR-OORL on OCGPTP (on express
OCGs only) of the same card. This alarm does not mask OPR-OORL/H on an add/drop OCGPTP and OPR-OORH
on express OCGPTPs.
(7) For associated chassis.
None of the license alarms can be suppressed/masked by any other alarms.

Note:

CHAPTER 3
Events
The DTN, DTN-X, FlexROADM and Optical Line Amplifier (referred to as the network element) network
elements report events that indicate an informational condition that does not require troubleshooting.
This chapter describes the events reported by the network element and the conditions under which the
events are reported in the following sections:
Event Overview on page 3-2
Event Description on page 3-6

3-2 Event Overview
Event Overview
The following section describes the event categories and provides pointers to events in the following
sections:
■ Event Category on page 3-2
■ Alphabetical Event Index on page 3-2
Event Category
Each event is assigned an event category as described in Event Categories.
Table 3-1 Event Categories

Event Category Description
Admin Events on page 3- Administrative events are internal communication events between network elements
6 and management clients such as GNM. These events are used to communicate the
event queue status and processor activities (reboot, switchover, active).
#unique_2637 Audit events are records of user actions that modify the state of any of the managed
objects within the network element. Only those user initiated operations that modify the
network element are audit logged. Any monitoring or Read-only operations are not
audit logged.
Security Events on page 3- Security events are generated when there are security violations in the managed
19 network element.
Alphabetical Event Index

Alphabetical Admin Events Index gives the name and page number of the admin events listed
alphabetically, with the corresponding message text and the source object on which the events are
raised.
Table 3-2 Alphabetical Admin Events Index

Alarm Indication Signal - DTP Automatic Switch to Protection Automatically Reverted Back to
Working
Backward Defect Indication - DTP BMM DAMP Status Update Circuit Pack Operationally Ready
Circuit Pack Plug-In Circuit Pack UnPlug Command Completed Successfully
on Expansion Chassis
Database restore in progress DB Rebranding was done DLM ID Already Provisioned to Other
BMM OCG
GAM OCG DLM ID Already DLM ID Not Found DLM ID Not Found
Provisioned to Other GAM OCG

Events 3-3
Table 3-2 Alphabetical Admin Events Index (continued)

DLM OCG Time Out on Auto DSE Output Spectrum Achieved Expected Span Loss Change
Discovery
File Transfer Failed File Transfer Failed Because of File transfer partially succeeded
MCM/Controller Card Reboot
File Transferred Process Started File transferred successfully Install Failed
Install in Progress...Unpacking the Install: Done Unpacking the Tar Invalid DLM ID CRC fail
Tar File File...Rebooting...
LM OCH ID Already Provisioned to LM OCH ID Not Found Local Backup Done
Other CMM OCH
Local Backup Failed Because of Make Standby Completed Manual Switch to Protection
Reboot
Manual Switch to Protection Failed Manual Switch to Working Migrate Completed Successfully
Database Migrate Failed MSA firmware upgrade completed MSA firmware upgrade in progress
successfully
NC System is Active Now Restore Completed Successfully Revert Failed
“PrepareUpgrade Completed “Prepare For Upgrade error“
Successfully“
Revert in Progress Revert: Done Unpacking the Tar Scheduled Transfer Request
File...Rebooting... Dropped
Software Install Failed Because of Software Revert Failed Because of Software Uncompress Failed
Reboot Reboot Because of Reboot
Switched to Protection Switched to Working Time Set Backward by More than 10
Secs
Time Set Forward by More than 10 Transfer Request Dropped Uncompress Completed
Secs
Uncompress Failed Uncompress in progress Upgrade Completed
Upgrade Completed Successfully Upgrade in Progress...Unpacking the Wait to Revert Cancel
Tar File
Alphabetical Security Events Index gives the name and page number of the security events listed
raised.
Table 3-3 Alphabetical Security Events Index

Intrusion Detected Reserved Session Limit Reached
Session Limit Reached
TACACS-CONNECT-INIT
TACACS-CONNECT-SUCCESS TACACS-CONNECT-FAIL

3-4 Event Overview
Alphabetical Audit Events Index gives the name and page number of the Audit events listed
raised.
Table 3-4 Alphabetical Audit Events Index

AC MAC Limit Exceeded AddPu Failed
AddPu Successful ApplyAlarmOffsetDays Failed
ApplyAlarmOffsetDays Successful ApplyOcg Failed
ApplyOcg Successful ApplyOch Failed
ApplyOch Successful CancSCMigrate Failed
CancSCMigrate Successful ClearLockout Failed
ClearLockout Successful Compress Failed
Compress Successful Creation Failed
Creation Successful Delete Failed
Delete Successful ForceSync Failed
ForceSync Successful InactivityAuthetication Failed
InactivityAuthetication Successful Install Failed
Install Successful InstallWithEmptyDB Failed
InstallWithEmptyDB Successful LocalBackup Failed
LocalBackup Successful Login Failed
Login Successful Logout Failed
Logout Successful MakeStandBy Failed
MakeStandBy Successful Manual Switch Failed
Manual Switch Successful MigrateSC Failed
MigrateSC Successful NCMigrate Failed
NCMigrate Successful PasswordChange Failed
PasswordChange Successful PasswordReset Failed
PasswordReset Successful PLck Failed
PLck Successful ReleaseDynamicConnections Failed
ReleaseDynamicConnections Successful RemPu Failed
RemPu Successful ResetCard Failed
ResetCard Successful ResetRx Fail
ResetRx Successful Restore Failed
Restore Successful Revert Failed

Events 3-5
Table 3-4 Alphabetical Audit Events Index (continued)

Revert Successful SessionTermination Failed
SessionTermination Successful StartAutoDiscovery Failed
StartAutoDiscovery Successful Update Failed
Update Successful Upgrade Failed
Upgrade Successful VSI MAC Limit Exceeded
WLck Failed WLck Successful

3-6 Event Description
Event Description
Events are listed according to their category. The description and the causes for the generation of each of
the events accompany each event.
The events are described in the following sections:
Admin Events on page 3-6
Security Events on page 3-19
#unique_2637
Admin Events
Administrative events are internal communication events between network elements and management
clients such as GNM. These events are used to communicate the event queue status and processor
activities (reboot, switchover, active). The following section provides the description and cause for the
generation of Admin events.
Alarm Indication Signal - DTP

Access Type - Admin
This message is generated when the attribute dataplane transparency is set on DCH and an AIS
condition is present on either receive or transmit direction.
Automatic Switch to Protection

Access Type - Admin
This message is generated by:
■ Digital SNCP or
■ Network element to indicate that a automatic switch to protection has been complete on a Shared
Mesh Protection Group.
This message is generated when:
■ The Digital SNCP is switched from working to protection
■ Traffic switches from automatically from work path to protect path of a Shared Mesh Protection
Group
■ Traffic switches from one protect path to another protect path due to failure or user operation.(in
case of SMPG)
Automatically Reverted Back to Working

Access Type - Admin
This message is generated by the Digital SNCP.

Events 3-7

■ The Digital SNCP is switched back from protection to working. The Digital SNCP waits for the wait
to revert time (specified by the user) for the digital SNCP to switch from protection to working if the
working remains fault free for this time.
Backward Defect Indication - DTP

Access Type - Admin
This message is generated when the attribute dataplanetransparency is set on DCH and a BDI condition
is present on either the receive or transmit direction.
BMM DAMP Status Update

Access Type - Admin
This message is generated by the active BMM to report the DAMP status.
■ The BMM is improperly provisioned.
Circuit Pack Operationally Ready

Access Type - Admin
This message is generated by the active BMM, CMM, OAM, ORM, RAM, SCM, DSE, line module (DLM/
XLM/ADLM/AXLM/SLM), LM-80 (ADLM-80/AXLM-80/SLM-80), TEM, GAM, TAM, and/or TOM equipment
when the operational state of a circuit pack changes from disabled (non-operational) to enabled
(operational).
Starting in Release 10.0, a circuit pack operationally ready (CPOR) event is generated even if the
administrative state of a circuit pack is set to Lock or Maintenance. However, for any installed child cards,
a CPOR event is generated only after the parent card is administratively set to Unlock. Additionally, a
management module (XCM) reset and/or switchover will no longer generate a CPOR event.
■ Any of the line module/LM-80s and/or TEMs are cold reset
■ The administrative state of a circuit pack is set to Unlock causing the operational state to transition
from disabled to enabled. CPOR events are generated for all child cards that transition to enabled.
Refer to the following examples:
□ Example 1—a pre-provisioned circuit pack is administratively set to Lock and a circuit pack is
physically inserted (the operational state of the circuit pack transitions to enabled generating
a CPOR event for the circuit pack). The circuit pack is then administratively set to Unlock
causing CPOR events to be generated for all installed child cards that transition to enabled.
□ Example 2—a failed circuit pack is administratively set to Lock and subsequently replaced
(the operational state of the circuit pack transitions to enabled generating a CPOR event for
the circuit pack). The circuit pack is then administratively set to Unlock causing CPOR events
to be generated for all installed child cards that transition to enabled.

Circuit Pack Plug-In

Access Type - Admin
This message is generated by the system when the circuit pack is plugged in.
■ Circuit pack is plugged in.
Circuit Pack UnPlug

Access Type - Admin
This message is generated by the system when the circuit pack is unplugged.
■ The Circuit pack is unplugged.
Command Completed Successfully on Expansion Chassis

Access Type - Admin
This message is generated by the system when Prepare/Revert migration operation is issued, and
command completes successfully on SC.
■ The command is run and completed successfully on the expansion chassis.
Database Migrate Failed

Access Type - Admin
This message is generated by the network element to indicate the failure in migrating the database.
■ The migration of the database is failed.
Database restore in progress

Access Type - Admin
This message is generated by the system when the database restore is in progress.
■ The database restore is in progress.
DB Rebranding was done

Access Type - Admin
This message is generated by the system when the database rebranding is already done.
■ The database rebranding is already done.

Events 3-9
DLM ID Already Provisioned to Other BMM OCG

Access Type - Admin
This message is generated by the active MCM to report that a request for Auto-discovery is dropped
when the BMM OCG reports a DLM ID which is already provisioned to some other BMM.
■ The DLM ID is improperly provisioned to the BMM.
DLM ID Not Found

Access Type - Admin
when the BMM OCG reports a non-existent DLM ID (that passes the CRC check) that is not known to the
MCM during Auto-discovery.
■ A DLM from some other network element is plugged in
■ An unreachable DLM (DLM is not communicating with the MCM) is in Auto-discovery mode
DLM OCG Time Out on Auto Discovery

Access Type - Admin
This message is generated by the DLM when the OCG is timed out on auto discovery.
■ The DLM OCG is timed out on auto discovery.
DSE Output Spectrum Achieved

Access Type - Admin
This message is generated by the DSE to report that the output spectrum has been achieved following a
successful equalization attempt where spectrum convergence has been obtained.
■ The DSE output spectrum has been successfully achieved.
Expected Span Loss Change

Access Type - Admin
This message is generated by the network element to indicate an update to the Expected Span Loss
(ESL) values. The updated ESL high and low thresholds, as well as the previous values for ESL high and
low thresholds are indicated.
■ The Expected Span Loss values have been updated.

File Transfer Failed

Access Type - Admin
This message is generated by the network element to report unsuccessful completion of a file transfer.
■ The process of file transfer to or from the network element has failed / abruptly ended.
File Transfer Failed Because of MCM/Controller Card Reboot

Access Type - Admin
This message is generated by the network element to report unsuccessful completion of a file transfer.
■ The XCM is rebooted while file transfer is in progress.
File transfer partially succeeded

Access Type - Admin
This message is generated by the network element to report partial completion of a file transfer.
■ The file is partially transferred.
File Transferred Process Started

Access Type - Admin
This message is generated by the network element to report that a file transfer has started.
■ A request for file transfer is accepted and file transfer to or from the network element is in progress.
File transferred successfully

Access Type - Admin
This message is generated by the network element to report successful completion of a file transfer.
■ The desired set of files have been successfully transferred to or from the network element.
FRM DAMP Status Update

Access Type - Admin
This message is generated by the active FRM to report the DAMP status.
■ The FRM is improperly provisioned.

Events 3-11
GAM OCG DLM ID Already Provisioned to Other GAM OCG

Access Type - Admin
when the GAM OCG reports a DLM ID which is already provisioned to some other GAM.
■ The DLM ID is improperly provisioned to the BMM.
Install Failed
Access Type - Admin
This message is generated by the XCM circuit pack to report the failure of a software install process.
■ The software image corresponding to the software version does not get installed or
■ A fresh database is not created.
Install in Progress...Unpacking the Tar File

Access Type - Admin
This message is generated by the XCM circuit pack to report the progress of a software install process.
■ The software image corresponding to the software version is being installed.
Install: Done Unpacking the Tar File...Rebooting...

Access Type - Admin
This message is generated by the XCM circuit pack to report the progress of a software install process.
■ The software image corresponding to the software version is being installed.
Invalid DLM ID CRC fail

Access Type - Admin
This message is generated by the circuit pack to report the invalid DLM ID.
■ Circuit pack reports invalid DLM ID.
License Activated
Access Type - Admin
This message is generated to report that the license is activated.

■ The license is activated.
License Deactivated
Access Type - Admin
This message is generated to report that the license is deactivated.
■ The license is deactivated.
License Reassigned
A+ccess Type - Admin This message is generated to report that the license is reassigned.
■ The license is reassigned.
LM OCH ID Already Provisioned to Other CMM OCH

Access Type - Admin
when the CMM OCH reports an LM OCH ID which is already provisioned to some other CMM.
■ The LM OCH ID is improperly provisioned to the CMM.
LM OCH ID Not Found

Access Type - Admin
when the CMM OCH reports a non-existent LM OCH ID (that passes the CRC check) that is not known to
the MCM during Auto-discovery.
■ An LM-80 from some other network element is plugged in
■ An unreachable LM-80 (LM-80 is not communicating with the MCM) is in Auto-discovery mode
Local Backup Done

Access Type - Admin
This message is generated by the MCM circuit pack to report that the local backup of the database is
complete.
■ The local backup of the network element database is successfully complete

Events 3-13
Local Backup Failed Because of Reboot

Access Type - Admin
This message is generated by the MCM circuit pack to report that the local backup of the database failed
because the MCM circuit pack was rebooted.
This message will be raised on the object if the MCM circuit pack is rebooted while a local backup of the
database is being performed.
Make Standby Completed

Access Type - Admin
This message is generated by the network element to complete the standby process.
■ The user standby action is not complete.
Manual Switch to Protection

Access Type - Admin
This message is generated by the network element to indicate that a manual switch to protection has
been complete along with source and destination of switch as part of the details.
■ The user completes a switch from working to protection from one of the management interfaces.
Manual Switch to Protection Failed

Access Type - Admin
This message is generated by the network element to indicate that a manual switch to protection has
failed.
■ The user initiates a switch from working to protection from one of the management interfaces but
the switch fails to initiate.
Manual Switch to Working

Access Type - Admin
This message is generated by the network element to indicate that a manual switch from protection back
to working has been initiated.
■ The user initiates a switch from protection back to working from one of the management interfaces.
Migrate Completed Successfully

Access Type - Admin

This message is generated by the network element to indicate the successful completion of migration.
■ The migration is completed successfully.
MSA firmware upgrade completed successfully

Access Type - Admin
This message is generated by the network element to indicate the sucessful completion of MSA firmware
upgrade.
■ The MSA firmware upgrade is completed sucessfully.
MSA firmware upgrade in progress

Access Type - Admin
This message is generated by the network element to indicate that the MSA firmware upgrade is in
progress.
■ The MSA firmware upgrade is in progress.
NC System is Active Now

Access Type - Admin
This message is generated by the network element to indicate that the system is ready now.
■ The XCM is rebooted
■ The system comes up
OPM SCAN Completed

Access Type - Admin
This event is raised by the network element.
This event is raised when FRM OPM scan is completed.
PrepareUpgrade Completed Successfully

Access Type - Admin
This is raised on the node, when the user action prepare for upgrade is successfully completed.
■ Prepare to upgrade procedure is completed successfully.

Events 3-15
Prepare For Upgrade error

Access Type - Admin
This is raised on the chassis to notify failure of the prepare to upgrade procedure on the individual shelf.
■ Prepare to upgrade procedure fails on the shelf.
Restore Completed Successfully

Access Type - Admin
This message is generated by the MCM circuit pack to report that the restoration of the database is
complete.
■ The database restoration process is complete.
Revert Failed
Access Type - Admin
This message is generated by the XCM circuit pack to report the failure of a software revert process.
■ The software fails to revert to an older version or
■ The corresponding older database is not picked up
Revert in Progress
Access Type - Admin
This message is generated by the XCM circuit pack to report the progress of a software revert process.
■ The software of the network element is being reverted to an older version from the current version
Revert: Done Unpacking the Tar File...Rebooting...

Access Type - Admin
This message is generated by the XCM circuit pack to report the progress of a software revert process.
■ The software of the network element is being reverted to an older version from the current version.
Scheduled Transfer Request Dropped

Access Type - Admin
This message is generated by the network element to indicate that the scheduled file transfer has been
dropped.


■ A scheduled backup is initiated when a manual file transfer is in progress.
SNC WTR Started

Access Type - Admin
This message will be raised on the object when a SNC wait to revert is started.
SNC WTR Canceled

Access Type - Admin
This message will be raised on the object when a SNC wait to revert is canceled.
Software Install Failed Because of Reboot

Access Type - Admin
This message will be raised on the object if the MCM circuit pack is rebooted while software is being
installed.
Software Revert Failed Because of Reboot

Access Type - Admin
This message is raised on the object if the MCM circuit pack is rebooted while software revert is in
progress.
Software Uncompress Failed Because of Reboot

Access Type - Admin
This message will be raised on the object if the MCM circuit pack is rebooted while software is being
uncompressed.
Switched to Protection
Access Type - Admin
This message is generated when the active timing source for the chassis is switched from one TSM/XCM
to another.
■ The active timing source for the chassis is switched from one TSM/XCM to another.
Switched to Working
Access Type - Admin
This message is generated by the network element to indicate that a switch from protection back to
working has been completed.

Events 3-17
■ A switch to working has been completed.

OR
This message is generated by the network element to indicate that a automatic switch to work has been
complete on a Shared Mesh Protection Group.
■ Traffic switches from protect path to work path of a Shared Mesh Protection Group due to
automatic or manual reversion
■ Manual or forced switch is released in revertive mode.
Time Set Backward by More than 10 Secs

Access Type - Admin
This message is generated by the network element.
■ The network element time is set backward by more than 10 seconds.
Time Set Forward by More than 10 Secs

Access Type - Admin
This message is generated by the network element.
■ The network element time is set forward by more than 10 seconds.
Transfer Request Dropped

Access Type - Admin
This message is generated by the network element to indicate that the file transfer has been dropped.
■ A backup is initiated when a manual file transfer is in progress.
Uncompress Completed
Access Type - Admin
This message is generated by the XCM circuit pack to report the successful completion of a software
uncompress process.
■ The newer software has completed the uncompress process.
Uncompress Failed
Access Type - Admin

This message is generated by the XCM circuit pack to report the failure of a software uncompress
process.
■ The newer software has failed to complete the uncompress process.
Uncompress in progress
Access Type - Admin
This message is generated by the XCM circuit pack to report that the software uncompress process is in
progress.
■ The newer software is in progress to complete the uncompress process.
Upgrade Completed
Access Type - Admin
upgrade process.
■ The network element has been upgraded to a newer software version
■ The current version of the database has been migrated to the newer version
Upgrade Completed Successfully

Access Type - Admin
upgrade process.
■ The network element has been upgraded to a newer software version
■ The current version of the database has been migrated to the newer version
Upgrade in Progress...Unpacking the Tar File

Access Type - Admin
This message is generated by the XCM circuit pack to report the progress of an upgrade.
■ The software of the network element is being upgraded from the current version to a newer version

Events 3-19
Wait to Revert Cancel

Access Type - Admin
This event is generated by the network element to report when a wait to revert (WTR) is stopped or
canceled as a result of a fault condition on the protection unit.
This event is generated when:
■ A WTR has been stopped or canceled.
Security Events
Security events are generated when there are security violations in the managed network element. This
section provides description and causes for Security events.
Intrusion Detected
Access Type - Security
This message is generated by the network element to report a system intrusion or security violation in the
network element.
■ A user tries to log on to the system more than three times with invalid password.
Reserved Session Limit Reached

This message is generated by the network element to report that the maximum number of permissible
sessions have been used.
■ All the permissible 30 sessions have been used and no more users can log in.
Session Limit Reached

This message is generated by the network element to report that the maximum number of permissible
sessions for a non security administrator have been used.
■ All the permissible 28 sessions have been used and no more user other than the security
administrator can log in.
TACACS-CONNECT-INIT

This message is generated by the network element when the system attempts to establish a connection
with the configured TACACS+ servers.
TACACS-CONNECT-SUCCESS
This message is generated by the network element when the system successfully connects with the
configured TACACS+ servers.
TACACS-CONNECT-FAIL
This message is generated by the network element when the system fais to connect with the configured
TACACS+ servers.

APPENDIX A:
Alarm Index
Table Default Alarm Settings for each Managed Object (AID) Type the alarms for each of the AID types
(i.e., managed objects types) on the DTN, DTN-X, XT, FlexROADM, Optical Amplifier and Optical Line
Amplifier. The table lists the managed object types supported for ASPS, as well as the alarm ID, condition
type, default severity level (Sev.), service affecting or not service affecting type (SA/ NSA), location (Loc.),
direction (Dir.), and whether the alarm has an associated chassis-level LED.
Table List of Threshold Crossing Alerts for FlexROADM, DTN-X, DTN, XT, and Optical Amplifiers lists the
threshold crossing alerts (TCAs) for each of the managed object types on DTN, DTN-X, XT, FlexROADM,
and Optical Amplifier.
Alarms
Default Alarm Settings for each Managed Object (AID) Type
Applies to Object Alarm Probable Cause Severity Type Locati Directi Affects
Unique Id on on Chassis
LED
AC FAC0464 AC MAC Limit Major Non‐ LocNA DirNA TRUE
Reached (MJ) Servi
ce
Affec
ting
FAC0463 MAC flap Major Non‐ LocNA DirNA TRUE
condition (MJ) Servi
detected ce
Affec
ting
Band Port FAC0300 Optical Loss Out Minor Non‐ NearE Trans TRUE
of Range ‐ High (MN) Servi nd mit
ce
Affec
ting
FAC0112 Inter‐module Major Non‐ NearE Receiv TRUE
mis‐connection (MJ) Servi nd e

A-2 Alarm Index
ce
Affec
ting
EQP0063 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
FAC0024 Optical Loss Of Critical Servi NearE Receiv TRUE
Signal ‐ Payload (CR) ce nd e
Affec
ting
Maintenance Reported Servi
(NR) ce
Affec
ting
BASESCGPTP FAC0088 Optical Loss Of Critical Servi NearE Receiv TRUE
Affec
ting
BMM EQP0062 Administrative Not Non‐ LocNA DirNA FALSE
(NR) ce
Affec
ting
EQP0063 Administrative Not Servi LocNA DirNA FALSE
Lock Reported ce
(NR) Affec
ting
EQP0008 Equipment Critical Servi LocNA DirNA TRUE
failure (CR) ce
Affec
ting
EQP0066 Excessive Major Servi LocNA DirNA TRUE
Channels (MJ) ce
Affec
ting
EQP0036 Temperature out Major Non‐ LocNA DirNA TRUE
of range (MJ) Servi
ce
Affec
ting
ENV0029 Temperature Out Critical Servi LocNA DirNA TRUE
Of Range ‐ device (CR) ce
auto shutdown Affec
ting
Alarm and Trouble Clearing Guide Release 17.0 V0.1 Infinera Corporation

Alarm Index A-3
EQP0057 CP to Controller Major Non‐ LocNA DirNA TRUE

B internal comm (MJ) Servi
failure ce
Affec
ting
EQP0015 Database Major Non‐ LocNA DirNA TRUE
Mismatch (MJ) Servi
ce
Affec
ting
A internal OSC (MJ) Servi
Ethernet link ce
failure Affec
ting
EQP0010 Equipment type Major Non‐ LocNA DirNA TRUE
mismatch (MJ) Servi
ce
Affec
ting
EQP0069 AGC not Minor Non‐ LocNA DirNA TRUE
functioning (MN) Servi
ce
Affec
ting
EQP0044 Equipment Major Non‐ LocNA DirNA TRUE
degradation (MJ) Servi
ce
Affec
ting
EQP0101 Equipment is USB Minor Non‐ LocNA DirNA TRUE
power‐resetting (MN) Servi
ce
Affec
ting
EQP0048 Unknown Major Non‐ LocNA DirNA TRUE
Firmware (MJ) Servi
present ce
Affec
ting
EQP0047 Insufficient gain Major Non‐ LocNA DirNA TRUE
(MJ) Servi
ce
Affec
ting
EQP0088 Initialization Warning Non‐ LocNA DirNA TRUE
Under Progress (WN) Servi
Infinera Corporation Alarm and Trouble Clearing Guide Release 17.0 V0.1

A-4 Alarm Index
ce
Affec
ting
A internal comm (MJ) Servi
failure ce
Affec
ting
B internal OSC (MJ) Servi
Ethernet link ce
failure Affec
ting
EQP0021 Equipment's Minor Non‐ LocNA DirNA TRUE
control plane is (MN) Servi
warm‐resetting ce
Affec
ting
improper (CR) ce
removal Affec
ting
partial failure (CR) ce
Affec
ting
EQP0013 Equipment's Major Non‐ LocNA DirNA TRUE
control plane is (MJ) Servi
unreachable ce
Affec
ting
BMM OCG Port FAC0230 Power Control Major Non‐ NearE Trans TRUE
Loop Disabled (MJ) Servi nd mit
ce
Affec
ting
Affec
ting
FAC0115 OPR Out of Minor Non‐ NearE Receiv TRUE
Range ‐ High (MN) Servi nd e
ce
Affec
ting

Alarm Index A-5
FAC0229 Administrative Not Servi LocNA DirNA FALSE

Lock Reported ce
(NR) Affec
ting
FAC0448 OCG Type Warning Non‐ NearE Receiv FALSE
Mismatch (WN) Servi nd e
ce
Affec
ting
FAC0227 OCG Loss Out of Minor Non‐ LocNA Trans TRUE
Range ‐ High (MN) Servi mit
ce
Affec
ting
FAC0059 Power Major Non‐ LocNA Trans TRUE
adjustment (MJ) Servi mit
incomplete ce
Affec
ting
FAC0112 Inter‐module Major Non‐ LocNA DirNA TRUE
mis‐connection (MJ) Servi
ce
Affec
ting
Range ‐ Low (MN) Servi nd e
ce
Affec
ting
FAC0110 Auto discovery Critical Servi LocNA Trans TRUE
timed out (CR) ce mit
Affec
ting
CARRIERCTP FAC0229 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
FAC0421 PMD Out of Minor Non‐ NearE Receiv TRUE
Range High (MN) Servi nd e
ce
Affec
ting
FAC0033 Rx Backward Not Servi FarEnd Receiv TRUE
Defect Indication Reported ce e
(NR) Affec
ting

A-6 Alarm Index
FAC0117 Post‐FEC BER‐ Critical Servi NearE Receiv TRUE

based Signal (CR) ce nd e
Failure Affec
ting
FAC0228 Administrative Not Non‐ LocNA DirNA FALSE
(NR) ce
Affec
ting
FAC0422 Pre‐FEC‐Q value Minor Non‐ NearE Receiv TRUE
Out of range low (MN) Servi nd e
ce
Affec
ting
FAC0021 Loss Of Frame Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
FAC0022 Loss Of Signal Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
FAC0282 OPT Out of Minor Non‐ NearE Trans TRUE
Range ‐ Low (MN) Servi nd mit
ce
Affec
ting
C‐Band FAC0426 Forward Defect Not Servi NearE Receiv TRUE
Indication ‐ Reported ce nd e
Payload (NR) Affec
ting
FAC0427 Forward Defect Not Non‐ NearE Receiv TRUE
Indication ‐ Reported Servi nd e
Overhead (NR) ce
Affec
ting
FAC0231 Automatic Laser Major Non‐ NearE Trans TRUE
Shutdown (MJ) Servi nd mit
Disabled ce
Affec
ting
FAC0062 Span Loss Out of Minor Non‐ NearE Receiv TRUE
ce
Affec
ting

Alarm Index A-7
FAC0095 OPR Out of Major Non‐ NearE Receiv TRUE

Range ‐ High (MJ) Servi nd e
ce
Affec
ting
(NR) ce
Affec
ting
FAC0006 Backward Defect Not Servi FarEnd Receiv TRUE
Indication ‐ Reported ce e
Payload (NR) Affec
ting
FAC0429 Backward Defect Not Non‐ FarEnd Receiv TRUE
Indication ‐ Reported Servi e
Overhead (NR) ce
Affec
ting
ce
Affec
ting
FAC0282 OPT Out of Warning Non‐ NearE Trans TRUE
Range ‐ Low (WN) Servi nd mit
ce
Affec
ting
FAC0283 OPT Out of Warning Non‐ NearE Trans TRUE
Range ‐ High (WN) Servi nd mit
ce
Affec
ting
FAC0301 BAND Loss Out of Major Non‐ NearE Trans TRUE
Range ‐ High (MJ) Servi nd mit
ce
Affec
ting
FAC0096 OPR Out of Major Non‐ NearE Receiv TRUE
Range ‐ Low (MJ) Servi nd e
ce
Affec
ting
FAC0430 Payload Missing Not Non‐ NearE Receiv TRUE
Indication Reported Servi nd e
(NR) ce

A-8 Alarm Index
Affec
ting
FAC0444 Insufficient Minor Non‐ NearE Trans TRUE
Output Power (MN) Servi nd mit
ce
Affec
ting
Affec
ting
FAC0061 Span Loss Out of Minor Non‐ NearE Receiv TRUE
ce
Affec
ting
Chassis EQP0082 Power Minor Non‐ LocNA DirNA TRUE
Control:System (MN) Servi
needed power is ce
more than Affec
available power ting
EQP0093 Mismatch of PEM Minor Non‐ LocNA DirNA TRUE
types within a (MN) Servi
group ce
Affec
ting
EQP0064 Chassis power Minor Non‐ LocNA DirNA TRUE
draw exceeds (MN) Servi
configured ce
maximum value Affec
ting
EQP0013 Equipment's Critical Servi LocNA DirNA TRUE
control plane is (CR) ce
unreachable Affec
ting
EQP0093 Registration Major Non‐ LocNA DirNA TRUE
RequiredMJ (MJ) Servi
ce
Affec
ting
ce
Affec
ting
EQP0080 Chassis power Warning Non‐ LocNA DirNA TRUE
protection failed (WN) Servi

Alarm Index A-9
ce
Affec
ting
EQP0070 Redundant Not Non‐ LocNA DirNA TRUE
controller Reported Servi
module not (NR) ce
physically Affec
present ting
EQP0096 NODE CONFIG Minor Servi LocNA DirNA TRUE
CHANGED (MN) ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
Affec
ting
failure (CR) ce
Affec
ting
EQP0079 Timing And Not Non‐ LocNA DirNA TRUE
Synchronization Reported Servi
Module not (NR) ce
redundant Affec
ting
EQP0068 Power control Major Non‐ LocNA DirNA TRUE
initiated ‐ (MJ) Servi
maximum ce
allowed fan Affec
speed reduced ting
EQP0083 Locked Sync Critical Servi LocNA DirNA FALSE
Source Active (CR) ce
Affec
ting
EQP0077 Timing Source Major Servi LocNA DirNA TRUE
Mismatch (MJ) ce
Affec
ting
EQP0078 Timing And Warning Non‐ LocNA DirNA TRUE
Synchronization (WN) Servi
Module ce
Unavailable Affec
ting

A-10 Alarm Index
EQP0034 Ambient (inlet) Major Non‐ LocNA DirNA TRUE

temperature Out (MJ) Servi
of Range ‐ High ce
Affec
ting
EQP0010 Equipment type Critical Non‐ LocNA DirNA TRUE
mismatch (CR) Servi
ce
Affec
ting
EQP0075 Switch Fabric Warning Non‐ LocNA DirNA TRUE
Protection (WN) Servi
Unavailable ce
Affec
ting
EQP0091 Registration Critical Servi LocNA DirNA TRUE
Expired (CR) ce
Affec
ting
(NR) ce
Affec
ting
EQP0074 Switch Fabric Fail Critical Servi LocNA DirNA TRUE
(CR) ce
Affec
ting
EQP0092 Registration Minor Non‐ LocNA DirNA TRUE
Required (MN) Servi
ce
Affec
ting
EQP0102 Power Over Minor Non‐ LocNA DirNA TRUE
Current (MN) Servi
ce
Affec
ting
EQP0024 Power over Minor Non‐ LocNA DirNA TRUE
voltage (MN) Servi
ce
Affec
ting
EQP0025 Power under Minor Non‐ LocNA DirNA TRUE
voltage (MN) Servi
ce

Alarm Index A-11
Affec
ting
EQP0084 Equipment Major Servi LocNA DirNA TRUE
Communication (MJ) ce
Fail Affec
ting
auto shutdown Affec
ting
EQP0051 Initialization Major Servi LocNA DirNA TRUE
failure (MJ) ce
Affec
ting
Clear Channel FAC0228 Administrative Not Non‐ LocNA DirNA FALSE
(NR) ce
Affec
ting
FAC0118 De‐encapsulated Not Servi NearE Trans FALSE
Loss of Signal Reported ce nd mit
(NR) Affec
ting
(CR) ce nd e
Affec
ting
FAC0020 Terminal Warning Non‐ NearE DirNA TRUE
loopback enabled (WN) Servi nd
ce
Affec
ting
FAC0019 Facility loopback Warning Non‐ NearE DirNA TRUE
enabled (WN) Servi nd
ce
Affec
ting
CMM EQP0015 Database Major Non‐ LocNA DirNA TRUE
Mismatch (MJ) Servi
ce
Affec
ting
auto shutdown Affec
ting

A-12 Alarm Index

Affec
ting
Lock Reported ce
(NR) Affec
ting
ce
Affec
ting
warm‐resetting ce
Affec
ting
ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
failure ce
Affec
ting
failure (CR) ce
Affec
ting
(NR) ce
Affec
ting
improper (CR) ce
removal Affec
ting

Alarm Index A-13

ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
failure ce
Affec
ting
unreachable ce
Affec
ting
(MJ) Servi
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
CMM OCG Port FAC0227 OCG Loss Out of Minor Non‐ LocNA Trans TRUE
ce
Affec
ting
FAC0083 Optical Loss Of Critical Servi LocNA Receiv TRUE
Signal ‐ Payload (CR) ce e
Affec
ting
Lock Reported ce
(NR) Affec
ting
incomplete ce

A-14 Alarm Index
Affec
ting
Affec
ting
CMMOCHPTP FAC0112 Inter‐module Major Non‐ LocNA DirNA TRUE
ce
Affec
ting
FAC0230 Power Control Major Non‐ NearE Trans TRUE
ce
Affec
ting
FAC0114 OPR Out of Major Servi LocNA Receiv TRUE
Range ‐ Low (MJ) ce e
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
FAC0115 OPR Out of Major Servi LocNA Receiv TRUE
Range ‐ High (MJ) ce e
Affec
ting
FAC0372 OCH Mismatch Major Non‐ LocNA DirNA TRUE
(MJ) Servi
ce
Affec
ting
Signal ‐ Payload (CR) ce e
Affec
ting
Digital Channel FAC0117 Post‐FEC BER‐ Critical Servi NearE Receiv TRUE
Failure Affec
ting
FAC0299 Connectivity Major Servi NearE Receiv TRUE
Verification (MJ) ce nd e
Failed Affec
ting

Alarm Index A-15
FAC0019 Facility loopback Warning

Non‐ NearE DirNA TRUE
enabled (WN)
Servi nd
ce
Affec
ting
ce
Affec
ting
(CR) ce nd e
Affec
ting
(CR) ce nd e
Affec
ting
Payload (NR) Affec
ting
FAC0225 PRBS out of sync, Major Servi NearE DirNA TRUE
from network (MJ) ce nd
Affec
ting
FAC0223 PRBS generation Warning Servi NearE DirNA TRUE
activated, toward (WN) ce nd
network Affec
ting
client Affec
ting
from client (MJ) ce nd
Affec
ting
(NR) ce
Affec
ting
FAC0106 Pre‐FEC BER‐ Minor Non‐ NearE Receiv TRUE
based Signal (MN) Servi nd e
Degrade ce

A-16 Alarm Index
Affec
ting
FAC0105 Trace Identifier Major Non‐ NearE Receiv TRUE
Mismatch (MJ) Servi nd e
ce
Affec
ting
DigitalSNCP‐1‐port PROT0005 Protection Unit Not Non‐ LocNA DirNA TRUE
Active Reported Servi
(NR) ce
Affec
ting
PROT0004 Lockout of Minor Non‐ NearE Receiv TRUE
working (MN) Servi nd e
ce
Affec
ting
protection (MN) Servi nd e
ce
Affec
ting
DigitalSNCP‐2‐Port PROT0004 Lockout of Minor Non‐ NearE Receiv TRUE
working (MN) Servi nd e
ce
Affec
ting
PROT0005 Protection Unit Not Non‐ LocNA DirNA TRUE
Active Reported Servi
(NR) ce
Affec
ting
protection (MN) Servi nd e
ce
Affec
ting
DIGITALWRAPPERCTP FAC0332 Trace Identifier Major Non‐ NearE Receiv TRUE
ce
Affec
ting
(NR) ce
Affec
ting

Alarm Index A-17
DLM EQP0056 CP to Controller Major Non‐ LocNA DirNA TRUE

failure ce
Affec
ting
protection (MJ) Servi
control bus ce
failure with slot 6 Affec
ting
control bus ce
ting
control bus ce
ting
control bus ce
ting
unreachable ce
Affec
ting
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
EQP0072 Temperature Out Critical Servi LocNA DirNA TRUE
Of Range High‐ (CR) ce

A-18 Alarm Index
Device auto Affec

shutdown ting
EQP0028 Tx PIC Critical Servi LocNA DirNA TRUE
temperature Out (CR) ce
Of Range High ‐ Affec
auto shutdown ting
EQP0045 Maintenance Minor Non‐ LocNA DirNA TRUE
required ‐ (MN) Servi
Contact Technical ce
Assistance Center Affec
ting
ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
(NR) ce
Affec
ting
improper (CR) ce
removal Affec
ting
warm‐resetting ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
EQP0029 Rx PIC Critical Servi LocNA DirNA TRUE
temperature Out (CR) ce

Alarm Index A-19
Of Range High ‐ Affec

auto shutdown ting
Affec
ting
of range ‐ Low (MJ) Servi
ce
Affec
ting
failure ce
Affec
ting
failure (CR) ce
Affec
ting
ce
Affec
ting
DLM OCG Port FAC0110 Auto discovery Critical Servi LocNA Trans TRUE
Affec
ting
FAC0227 OCG Loss Out of Minor Non‐ LocNA Trans TRUE
ce
Affec
ting
FAC0420 Remote Eqpt Major Servi FarEnd DirNA TRUE
Encoding Mode (MJ) ce
Mismatch Affec
ting
ce
Affec
ting
FAC0302 OCG Mismatch Major Non‐ LocNA DirNA TRUE
(MJ) Servi
ce

A-20 Alarm Index
Affec
ting
FAC0394 RX EDFA Input Major Non‐ NearE Receiv TRUE
Power Exceeded (MJ) Servi nd e
its limit ce
Affec
ting
incomplete ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
FAC0419 Remote Eqpt FEC Major Servi FarEnd DirNA TRUE
Type Mismatch (MJ) ce
Affec
ting
Affec
ting
ce
Affec
ting
ce
Affec
ting
DLM Optical Channel FAC0021 Loss Of Frame Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
Failure Affec
ting
FAC0032 PRBS out of sync Major Servi NearE DirNA TRUE
(MJ) ce nd
Affec
ting

Alarm Index A-21

activated (WN) ce nd
Affec
ting
ce
Affec
ting
FAC0105 Trace Identifier Major Non‐ NearE Receiv TRUE
ce
Affec
ting
(NR) ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
FAC0106 Pre‐FEC BER‐ Minor Non‐ NearE Receiv TRUE
based Signal (MN) Servi nd e
Degrade ce
Affec
ting
Payload (NR) Affec
ting
DSE EQP0008 Equipment Critical Servi LocNA DirNA TRUE
failure (CR) ce
Affec
ting
EQP0071 Incompatible DSE Critical Servi LocNA DirNA TRUE
(CR) ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting

A-22 Alarm Index

warm‐resetting ce
Affec
ting
ce
Affec
ting
ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
unreachable ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
Affec
ting
ce
Affec
ting
(NR) ce

Alarm Index A-23
Affec
ting
EQP0073 DSE Output Minor Non‐ NearE Trans TRUE
Spectrum Not (MN) Servi nd mit
Attained ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
failure ce
Affec
ting
improper (CR) ce
removal Affec
ting
failure ce
Affec
ting
DSEPTP FAC0112 Inter‐module Major Non‐ LocNA DirNA TRUE
ce
Affec
ting
FAC0300 Optical Loss Out Minor Non‐ LocNA Receiv TRUE
of Range ‐ High (MN) Servi e
ce
Affec
ting
Signal (CR) ce e
Affec
ting
DTF Path FAC0073 Trace Identifier Major Non‐ NearE Receiv TRUE
ce
Affec
ting
FAC0293 Alarm Indication Not Servi NearE Trans TRUE
Signal‐ DTP Reported ce nd mit
(NR)

A-24 Alarm Index
Affec
ting
Indication ‐ DTP Reported ce e
(NR) Affec
ting
(NR) ce
Affec
ting
FAC0004 Alarm Indication Not Servi NearE Receiv TRUE
Signal ‐ DTP Reported ce nd e
(NR) Affec
ting
FAC0294 Trace Identifier Major Non‐ NearE Trans TRUE
Mismatch (MJ) Servi nd mit
ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
FAC0292 Backward Defect Not Servi FarEnd Trans TRUE
Indication‐ DTP Reported ce mit
(NR) Affec
ting
ce
Affec
ting
activated (WN) ce nd
Affec
ting
Failure Affec
ting
FAC0032 PRBS out of sync Major Servi NearE DirNA TRUE
(MJ) ce nd
Affec
ting

Alarm Index A-25
FAC0074 Payload label Major Non‐ NearE Receiv TRUE

ce
Affec
ting
FAC0296 Loss Of Frame Warning Non‐ NearE Trans TRUE
(WN) Servi nd mit
ce
Affec
ting
FAC0295 Post‐FEC BER‐ Critical Servi NearE Trans TRUE
based Signal (CR) ce nd mit
Failure Affec
ting
ce
Affec
ting
(CR) ce nd e
Affec
ting
ETHINTF FAC0019 Facility loopback Warning Non‐ NearE DirNA TRUE
ce
Affec
ting
ce
Affec
ting
Affec
ting
network Affec
ting
SWP0049 Supporting Critical Servi LocNA DirNA TRUE
Transport Layer (CR) ce
has lesser Affec
capacity ting

A-26 Alarm Index

client Affec
ting
(NR) ce
Affec
ting
Affec
ting
FAC0445 Loss of Ethernet Critical Servi NearE Receiv TRUE
Link (CR) ce nd e
Affec
ting
EXPNPTP FAC0228 Administrative Not Non‐ LocNA DirNA FALSE
(NR) ce
Affec
ting
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
ce
Affec
ting
EXPNSCGPTP FAC0229 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
Affec
ting
Fan EQP0009 Equipment Major Non‐ LocNA DirNA TRUE
partial failure (MJ) Servi

Alarm Index A-27
ce
Affec
ting
failure (MJ) Servi
ce
Affec
ting
Fail Affec
ting
improper (MJ) ce
removal Affec
ting
FBM EQP0084 Equipment Major Servi LocNA DirNA TRUE
Fail Affec
ting
failure ce
Affec
ting
(NR) ce
Affec
ting
failure (CR) ce
Affec
ting
ce
Affec
ting
EQP0100 Software Major Non‐ LocNA DirNA TRUE
Initialization (MJ) Servi
Failure ce
Affec
ting
of range (MJ) Servi
ce

A-28 Alarm Index
Affec
ting
warm‐resetting ce
Affec
ting
EQP0097 EQPT USB Major Non‐ LocNA DirNA TRUE
Misonnection (MJ) Servi
ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
failure ce
Affec
ting
ce
Affec
ting
Affec
ting
ce
Affec
ting
improper (CR) ce
removal Affec
ting

Alarm Index A-29

unreachable ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
FBMSCGPTP FAC0229 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
ce
Affec
ting
(NR) ce
Affec
ting
FAC0300 Optical Loss Out Minor Non‐ NearE Trans TRUE
ce
Affec
ting
Affec
ting
Affec
ting
ce
Affec
ting

A-30 Alarm Index
FEEDPTP EQP0000 Breaker open MinorNon‐ LocNA DirNA TRUE

48V (MN) Servi
ce
Affec
ting
EQP0043 Power 48V Minor Non‐ LocNA DirNA TRUE
failure (MN) Servi
ce
Affec
ting
EQP0024 Power over Minor Non‐ LocNA DirNA TRUE
voltage (MN) Servi
ce
Affec
ting
EQP0025 Power under Minor Non‐ LocNA DirNA TRUE
voltage (MN) Servi
ce
Affec
ting
Fibre Channel Client FAC0067 Loss Of Signal Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
FAC0128 Test signal out of Major Servi NearE DirNA TRUE
sync, from (MJ) ce nd
network Affec
ting
FAC0125 Test signal Warning Servi NearE DirNA TRUE
generation (WN) ce nd
activated, toward Affec
network ting
client ting
Loss Of Sync Reported ce nd mit
(NR) Affec
ting
(NR) Affec
ting
ce

Alarm Index A-31
Affec
ting
ce
Affec
ting
(NR) ce
Affec
ting
FAC0129 Loss of Sync Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
sync, from client (MJ) ce nd
Affec
ting
FLEXCARRIERCTP FAC0229 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
(NR) ce
Affec
ting
Signal (CR) ce nd e
Affec
ting
ce
Affec
ting
ce
Affec
ting
FMMC EQP0063 Administrative Not Servi LocNA DirNA FALSE
Lock Reported ce
(NR)

A-32 Alarm Index
Affec
ting
unreachable ce
Affec
ting
auto shutdown Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
ce
Affec
ting
(MJ) Servi
ce
Affec
ting
improper (CR) ce
removal Affec
ting
failure ce
Affec
ting
Fail Affec
ting
ce
Affec
ting
ce

Alarm Index A-33
Affec
ting
of range (MJ) Servi
ce
Affec
ting
failure (CR) ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
warm‐resetting ce
Affec
ting
(NR) ce
Affec
ting
Affec
ting
failure ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
FMMCSCGPTP FAC0230 Power Control Major Non‐ NearE Trans TRUE
ce
Affec
ting

A-34 Alarm Index
ce
Affec
ting
ce
Affec
ting
Affec
ting
ce
Affec
ting
Range ‐ High (MN) Servi nd mit
ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
ce
Affec
ting
Affec
ting
ce
Affec
ting
FMMF250 EQP0101 Equipment is USB Minor Non‐ LocNA DirNA TRUE
ce
Affec
ting

Alarm Index A-35

Mismatch (MJ) Servi
ce
Affec
ting
Affec
ting
Lock Reported ce
(NR) Affec
ting
improper (CR) ce
removal Affec
ting
ce
Affec
ting
failure ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
failure (CR) ce
Affec
ting
unreachable ce
Affec
ting
warm‐resetting ce
Affec
ting

A-36 Alarm Index

Firmware (MJ) Servi
present ce
Affec
ting
(NR) ce
Affec
ting
Fail Affec
ting
failure ce
Affec
ting
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
FMMFSCGPTP FAC0229 Administrative Not Non‐ LocNA DirNA FALSE
Lock Reported Servi
(NR) ce
Affec
ting
Affec
ting
ce
Affec
ting
ce

Alarm Index A-37
Affec
ting
Affec
ting
ce
Affec
ting
FRM EQP0084 Equipment Major Servi LocNA DirNA TRUE
Fail Affec
ting
(NR) ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
EQP0091 AGC Partially Warning Non‐ LocNA DirNA TRUE
Functioning (WN) Servi
ce
Affec
ting
EQP0069 AGC not Minor Non‐ LocNA DirNA TRUE
functioning (MN) Servi
ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
ce

A-38 Alarm Index
Affec
ting
warm‐resetting ce
Affec
ting
failure ce
Affec
ting
auto shutdown Affec
ting
A internal OSC (MJ) Servi
Ethernet link ce
failure Affec
ting
failure ce
Affec
ting
ce
Affec
ting
ce
Affec
ting
failure (CR) ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting

Alarm Index A-39

improper (CR) ce
removal Affec
ting
Ethernet link ce
failure Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
Affec
ting
unreachable ce
Affec
ting
(MJ) Servi
ce
Affec
ting
FRMSCGPTP FAC0110 Auto discovery Critical Servi LocNA Trans TRUE
Affec
ting
ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
Affec
ting

A-40 Alarm Index

ce
Affec
ting
ce
Affec
ting
FSE EQP0008 Equipment Critical Servi LocNA DirNA TRUE
failure (CR) ce
Affec
ting
improper (CR) ce
removal Affec
ting
of range (MJ) Servi
ce
Affec
ting
ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
EQP0047 Insufficient gain Major Non‐ LocNA Trans TRUE
(MJ) Servi mit
ce
Affec
ting
Affec
ting

Alarm Index A-41

auto shutdown Affec
ting
(NR) ce
Affec
ting
FSM EQP0009 Equipment Critical Servi LocNA DirNA TRUE
Affec
ting
unreachable ce
Affec
ting
ce
Affec
ting
improper (CR) ce
removal Affec
ting
of range (MJ) Servi
ce
Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
ce
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting

A-42 Alarm Index

warm‐resetting ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
EQP0047 Insufficient gain Major Non‐ LocNA Trans TRUE
(MJ) Servi mit
ce
Affec
ting
failure ce
Affec
ting
Fail Affec
ting
ce
Affec
ting
failure (CR) ce
Affec
ting
failure ce
Affec
ting
(NR) ce
Affec
ting
auto shutdown Affec
ting

Alarm Index A-43

Lock Reported ce
(NR) Affec
ting
FSMSCGPTP FAC0110 Auto discovery Critical Servi LocNA Trans TRUE
Affec
ting
ce
Affec
ting
ce
Affec
ting
Lock Reported Servi
(NR) ce
Affec
ting
ce
Affec
ting
Affec
ting
GAM EQP0048 Unknown Major Non‐ LocNA DirNA TRUE
Firmware (MJ) Servi
present ce
Affec
ting
ce
Affec
ting
(NR) ce
Affec
ting

A-44 Alarm Index

auto shutdown Affec
ting
mismatch (MJ) Servi
ce
Affec
ting
improper (CR) ce
removal Affec
ting
Affec
ting
Lock Reported ce
(NR) Affec
ting
failure (CR) ce
Affec
ting
EQP0086 Operating Mode Major Non‐ LocNA DirNA TRUE
Mismatch (MJ) Servi
ce
Affec
ting
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
of range ‐ Low (MJ) Servi
ce
Affec
ting
GAM OCG Port FAC0227 OCG Loss Out of Minor Non‐ LocNA Trans TRUE

Alarm Index A-45
ce
Affec
ting
FAC0112 Inter‐module Major Non‐ LocNA DirNA TRUE
ce
Affec
ting
Affec
ting
ce
Affec
ting
ce
Affec
ting
GbE Client FAC0380 DeEncap Local Not Servi NearE Trans TRUE
Fault Reported ce nd mit
(NR) Affec
ting
FAC0398 De‐Encapsulated Major Servi NearE Trans TRUE
Loss of Alignment (MJ) ce nd mit
Affec
ting
(NR) Affec
ting
FAC0379 Local Fault Not Servi NearE Receiv TRUE
Reported ce nd e
(NR) Affec
ting
network ting
sync, from client (MJ) ce nd
Affec
ting

A-46 Alarm Index

(NR) ce
Affec
ting
FAC0375 Loss of Lane Major Servi NearE Receiv TRUE
Marker (MJ) ce nd e
Affec
ting
ce
Affec
ting
sync, from (MJ) ce nd
network Affec
ting
ce
Affec
ting
FAC0378 Remote Fault Not Servi FarEnd Receiv TRUE
Reported ce e
(NR) Affec
ting
FAC0376 De‐Encapsulated Major Servi NearE Trans TRUE
Loss of Lane (MJ) ce nd mit
Marker Affec
ting
client ting
FAC0381 DeEncap Remote Not Servi FarEnd Trans TRUE
Fault Reported ce mit
(NR) Affec
ting
FAC0129 Loss of Sync Critical Servi NearE Receiv TRUE
(CR) ce nd e
Affec
ting
FAC0120 De‐encapsulated Not Servi NearE Trans TRUE
Loss Of Sync Reported ce nd mit
(NR) Affec
ting

Alarm Index A-47

(CR) ce nd e
Affec
ting
FAC0226 Loss of Alignment Major Servi NearE Receiv TRUE
(MJ) ce nd e
Affec
ting
FAC0435 Service State Critical Servi NearE DirNA FALSE
OOS‐AU (CR) ce nd
Affec
ting
GCC COM0053 General Minor Non‐ LocNA DirNA TRUE
Communication (MN) Servi
Channel ‐ Link ce
Failure Affec
ting
GFP Client FAC0019 Facility loopback Warning Non‐ NearE DirNA TRUE
ce
Affec
ting
client Affec
ting
Affec
ting
FAC0387 EXI Mismatch Major Servi NearE Receiv TRUE
(MJ) ce nd e
Affec
ting
FAC0384 Loss of Frame Major Servi NearE Receiv TRUE
Delineation (MJ) ce nd e
Affec
ting
FAC0386 UPI Mismatch Major Servi NearE Receiv TRUE
(MJ) ce nd e
Affec
ting
network Affec
ting

A-48 Alarm Index

ce
Affec
ting
Affec
ting
FAC0385 Client Signal Major Servi FarEnd Trans TRUE
Failure (MJ) ce mit
Affec
ting
(NR) ce
Affec
ting
GFPTP FAC0228 Administrative Not Non‐ LocNA DirNA FALSE
(NR) ce
Affec
ting
FAC0387 EXI Mismatch Major Servi NearE Receiv TRUE
(MJ) ce nd e
Affec
ting
network Affec
ting
FAC0385 Client Signal Major Servi FarEnd Trans TRUE
Failure (MJ) ce mit
Affec
ting
Affec
ting
FAC0384 Loss of Frame Major Servi NearE Receiv TRUE
Delineation (MJ) ce nd e
Affec
ting
Affec
ting

Alarm Index A-49

client Affec
ting
FAC0386 UPI Mismatch Major Servi NearE Receiv TRUE
(MJ) ce nd e
Affec
ting
ce
Affec
ting
ce
Affec
ting
GMPLS_CONTROL_CHANNEL COM0030 GMPLS neighbor Major Non‐ LocNA DirNA TRUE
adjacency lost (MJ) Servi
ce
Affec
ting
COM0033 Neighbors' GCC Minor Non‐ LocNA DirNA TRUE
IP Address in (MN) Servi
conflict with each ce
other Affec
ting
COM0031 Neighbor GCC IP Major Non‐ LocNA DirNA TRUE
address in (MJ) Servi
different subnet ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
COM0032 Node with Major Non‐ LocNA DirNA TRUE
duplicate GCC IP (MJ) Servi
address found in ce
routing domain Affec
ting
COM0044 GMPLS Major Non‐ LocNA DirNA TRUE
neighbors' (MJ) Servi
configuration do ce
not match Affec
ting

A-50 Alarm Index
COM0045 GRE Tunnel Major Non‐ LocNA DirNA TRUE

address do not (MJ) Servi
match at Local ce
and Remote End Affec
ting
GRE SWP0036 IP address Critical Servi LocNA DirNA TRUE
conflict on NE (CR) ce
Affec
ting
IAM EQP0088 Initialization Warning Non‐ LocNA DirNA TRUE
ce
Affec
ting
ce
Affec
ting
auto shutdown Affec
ting
Ethernet link ce
failure Affec
ting
failure ce
Affec
ting
Mismatch (MJ) Servi
ce
Affec
ting
Affec
ting
Firmware (MJ) Servi
present ce
Affec
ting

Alarm Index A-51

failure ce
Affec
ting
failure (CR) ce
Affec
ting
(MJ) Servi
ce
Affec
ting
of range (MJ) Servi
ce
Affec
ting
Lock Reported ce
(NR) Affec
ting
(NR) ce
Affec
ting
EQP0021

R17.0 DTN and DTN-X Alarm and Trouble Clearing Guide

Uploaded by

Copyright:

Available Formats

R17.0 DTN and DTN-X Alarm and Trouble Clearing Guide

Uploaded by

Document Information

Original Title

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

R17.0 DTN and DTN-X Alarm and Trouble Clearing Guide

Uploaded by

Copyright:

Available Formats

Infinera DTN and DTN-X

Alarm and Trouble Clearing Guide

Chapter 2: Alarm Masking Hierarchy.........................................................................................................2-1

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Chapter Number: Title Descriptio

Documents for Release 17.0

Document Name Document ID Description

Infinera Proprietary and Confidential

Document Name Document ID Description

Infinera Proprietary and Confidential

Document Name Document ID Description

Infinera Proprietary and Confidential

Document Name Document ID Description

Convention Item Example

courier font User-entered text In the Label enter EastBMM

Infinera Proprietary and Confidential

Convention Item Example

Note: If the directory path or

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Table 1-1 Alarm Categories

Infinera Proprietary and Confidential

Alarm Severity Profile Setting

Alarm Reporting Control

Infinera Proprietary and Confidential

Infinera Proprietary and Confidential

Alarm Description and Clearing Procedures

Infinera Proprietary and Confidential

Alarm Indication Signal - DTP

■ Alarm Type - Facility

Description and Causes

Infinera Proprietary and Confidential

Backward Defect Indication - Payload

■ Alarm Type - Facility

Description and Causes (BDI on Channel CTP)

Description and Causes (BDI on DCHCTP)

Infinera Proprietary and Confidential

Facility Loopback Enabled

■ Alarm Type - Facility

Description and Causes

■ Release the facility loopback at the corresponding termination point

Infinera Proprietary and Confidential

Terminal Loopback Enabled

■ Alarm Type - Facility

Description and Causes

■ Release the terminal loopback at the corresponding termination point

Infinera Proprietary and Confidential

■ Alarm Type - Facility

Description and Causes

1. Verify that the OPR is within the valid range.

Infinera Proprietary and Confidential

■ Alarm Type - Facility

Description and Causes

■ This alarm is cleared when Rx Acquisition is successful.