BTI7800 Series Alarm and Troubleshooting Guide

Transcription

1 BTI7800 Series Alarm and Troubleshooting Guide Juniper Networks, Inc Innovation Way Sunnyvale, CA USA Part Number: Document Version: Published: Type: tel: BT8A78PD November 2016 STANDARD product release Copyright 2016 Juniper Networks, Inc. ALL RIGHTS RESERVED.

2

3 Contents Preface viii 1.0 Fault monitoring on the BTI Fault reporting Maintenance signaling Alarms and conditions 2-1 AirFilterAbsence Clearing an AirFilterAbsence alarm AIS L Clearing an AIS-L condition APR Clearing an APR alarm (PRE port) Clearing an APR alarm (terminal amplifier port) APSD Clearing an APSD alarm (DOL port) Clearing an APSD alarm (terminal amplifier line port) BDI Clearing a BDI condition ContComS Clearing a ContComS alarm DiskHighUsage EnvCurrentHighTh Clearing an EnvCurrentHighTh alarm EnvCurrentLowTh Clearing an EnvCurrentLowTh alarm EnvTempHighTh Product Release STANDARD iii

4 Contents Clearing an EnvTempHighTh alarm EnvTempLowTh Clearing an EnvTempLowTh condition EnvVoltHighTh Clearing an EnvVoltHighTh alarm EnvVoltLowTh Clearing an EnvVoltLowTh alarm EqptComm Clearing an EqptComm alarm EqptDgrd Clearing an EqptDgrd alarm EqptFail Clearing an EqptFail alarm EqptMism Clearing an EqptMism alarm EqptMiss Clearing an EqptMiss alarm FanSpeedLowTh Clearing a FanSpeedLowTh alarm FECI Clearing a FECI alarm (DOL port) Clearing a FECI alarm (terminal amplifier OSC) FEIM Clearing a FEIM alarm (DOL port) Clearing a FEIM alarm (terminal amplifier OSC) FirmUpgrdInProg FirmUpgrdFail Clearing a FirmUpgrdFail alarm FirmUpgrdReqd Forced HighBer Clearing a HighBer alarm InvUnknown Clearing an InvUnknown alarm LaserFail Clearing a LaserFail alarm LaserTempHighTh Clearing a LaserTempHighTh alarm LaserTempLowTh Clearing a LaserTempLowTh alarm LCK Clearing an LCK alarm LF Clearing an LF condition Lockout LOF Clearing an LOF alarm iv BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

5 Contents LoLightRx Clearing a LoLightRx alarm (DOL entity) Clearing a LoLightRx alarm (wavelength protection port) Clearing a LoLightRx alarm (terminal amplifier port) LoLightTx Clearing a LoLightTx alarm LOM Clearing an LOM alarm LOS Clearing an LOS alarm LoSpecRx Clearing a LoSpecRx alarm LoSync Clearing a LoSync alarm LPBK MemHighUsage ModTempHighTh Clearing a ModTempHighTh alarm ModTempLowTh Clearing a ModTempLowTh alarm ModTempShutdown Clearing ModTempShutdown alarm MS-AIS Clearing an MS-AIS condition MS-RDI Clearing an MS-RDI condition NonCoLocatedController Clearing a NonCoLocatedController alarm ObrHt Clearing an ObrHt alarm OchAis Clearing an OchAis condition OchOci Clearing an OchOci condition OchUeq Clearing an OchUeq alarm OCI Clearing an OCI alarm ODU-AIS Clearing an ODU-AIS condition OmsAis Clearing an OmsAis condition OneCableDisconnected Clearing a OneCableDisconnected alarm OprHighTh Clearing an OprHighTh alarm OprLowTh Product Release STANDARD v

6 Contents Clearing an OprLowTh alarm OptHighTh Clearing an OptHighTh alarm OptLowTh Clearing an OptLowTh alarm OTU-AIS PartitionFault Clearing a ParitionFault alarm PosRxHigh Clearing a PosRxHigh alarm PosRxLow Clearing a PosRxLow alarm PosTxHigh Clearing a PosTxHigh alarm PosTxLow Clearing a PosTxLow alarm PowerAbsent Clearing a PowerAbsent alarm PRBS PyldMism Clearing a PyldMism alarm RDI-L Clearing an RDI-L condition RF Clearing an RF condition ScmNmiDown Clearing an ScmNmiDown alarm scmnonmconn Clearing an scmnonmconn alarm SD Clearing an SD alarm TIM Clearing a TIM alarm TlossRxHt Clearing a TlossRxHt alarm TlossRxLt Clearing a TlossRxLt alarm UPGRD Fault masking 3-1 Equipment fault hierarchy Environment fault hierarchy Common fault hierarchy - OTN and CBR ports OTN interface fault hierarchy Ethernet interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy vi BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

7 Contents DOL port fault hierarchy DOL OSC fault hierarchy DOL OMS fault hierarchy DOL OCH fault hierarchy Terminal amplifier port fault hierarchy Alarm thresholds 4-1 Environment thresholds Temperature thresholds - equipment and traffic modules Temperature thresholds - MSA transceivers Fan-speed thresholds Output-current thresholds Voltage thresholds DOL thresholds DOL OSC power alarm thresholds DOL OMS power alarm thresholds DOL OCH power alarm thresholds DOL port power alarm thresholds DOL Rx-loss alarm thresholds Appendix A: BTI7800 Series equipment and modules A-1 Appendix B: BTI7800 Series transceivers B-1 Appendix C: BTI7800 Series module and BIC LED behavior C-1 Product Release STANDARD vii

8 Preface Preface This preface explains who should read this guide, related documentation, documentation conventions, how to obtain documentation, and how to obtain technical support. Audience This guide is primarily intended for site planners, planning engineers, and network operation center (NOC) staff. BTI7800 Series Documentation The following guides are provided in the BTI7800 documentation suite. BTI7800 Series Command Line Reference Guide BTI7800 Series Hardware Overview and Installation Guide BTI7800 Series Software Configuration Guide BTI7800 Series Alarm and Troubleshooting Guide BTI7800 Series Release s Obtaining documentation To obtain the most current version of all Juniper Networks technical documentation, see the product documentation page on the Juniper Networks website at techpubs/. If the information in the latest release notes differs from the information in the documentation, follow the product Release s. Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC. JTAC policies - For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at en.pdf. Product warranties - For product warranty information, visit warranty/. viii BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

9 Preface JTAC hours of operation - The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: Search for known bugs: Find product documentation: Find solutions and answer questions using our Knowledge Base: Download the latest versions of software and review release notes: customers/csc/software/ Search technical bulletins for relevant hardware and software notifications: kb.juniper.net/infocenter/ Join and participate in the Juniper Networks Community Forum: company/communities/ Open a case online in the CSC Case Management tool: To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone. Use the Case Management tool in the CSC at Call JTAC ( toll-free in the USA, Canada, and Mexico). For international or direct-dial options in countries without toll-free numbers, see End User License Agreement The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at cm/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. Documentation conventions Convention Means reader take note. s contain helpful suggestions or background information. Means reader be careful. Equipment damage or loss of data can result from your actions. Product Release STANDARD ix

10 Preface Convention Caution Means reader be careful. Harm to yourself or others can result from your actions. Warning Invisible laser radiation can be emitted from the aperture ports of amplifier circuit packs when no fiber cable is connected. Avoid exposure and do not stare into open apertures to avoid permanent eye damage. Laser Warning x BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

11 Preface Caution USE OF CONTROLS OR ADJUSTMENTS OR PERFORMANCE OF PROCEDURES OTHER THAN THOSE SPECIFIED IN THIS GUIDE MAY RESULT IN HAZARDOUS RADIATION EXPOSURE. Product Release STANDARD xi

12 Preface Copyright 2016 Juniper Networks, Inc. ALL RIGHTS RESERVED. This product is the property of Juniper Networks, Inc. and its licensors, and is protected by copyright. Any reproduction in whole or in part is strictly prohibited. Juniper, Juniper Networks, BTI, BTI SYSTEMS, packetvx, pronx, and The Network You Need are trademarks or registered trademarks of Juniper Networks, Inc. and/or its subsidiaries in the U.S. and/or other countries. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Copyright BTI Systems, Inc. All rights reserved. xii BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

13 C H A P T E R Fault monitoring on the BTI7800 Fault monitoring is enabled by default for all managed entities and is conducted at the physical layer, covering optical signals and channel-specific transceiver faults, and at the protocol layer with specific fault points defined for all supported protocols. Monitoring is also conducted on supporting BTI7800 equipment, including the various sensors located throughout the chassis and on the modules. You can enable or disable the reporting of a fault. When reporting is enabled and fault masking does not occur, the fault is reported as either an alarm (alarmed) or a condition (not alarmed). An alarm generates a notification as the fault becomes active. A condition does not generate a notification and is typically used to report lower-severity faults. For more information about fault masking, see Chapter 3, Fault masking. You can also configure whether a fault is an alarm or a condition and change its default severity. For more information, see the description of the conditions settings CLI command in the BTI7800 Command Line Reference Guide. This section covers the following topics: Fault reporting Maintenance signaling For detailed information about BTI7800 alarms and conditions, including alarm-clearing procedures, see Chapter 2, Alarms and conditions. Product Release STANDARD 1-1

14 Fault monitoring on the BTI7800 Fault reporting When reporting is enabled for a fault that becomes active on a managed entity, the reporting behavior of that fault depends on the administrative status (enabled or disabled) of the entity, as described in Table 1-1. Table 1-1 Entity administrative status and fault reporting Status Enabled Disabled Fault-Reporting Behavior When a fault with critical, major, or minor severity (see Table 1-2) becomes active, it is reported with an alarm notification. When the fault is no longer active, a condition-clear alarm is generated. Polling retrieves active faults on enabled entities. The CLI command show conditions retrieves a list of all active faults (both alarms and conditions), and the command show alarms retrieves a list of all active alarms. When a fault with critical, major, or minor severity either becomes active or is cleared, no reporting is provided. Polling results retrieved with either show conditions or show alarms do not include any active faults (alarms or conditions) on disabled entities. To retrieve alarms and conditions, use the show alarms and show conditions CLI commands, respectively. For both alarms and conditions, the information retrieved shows the name of the entity affected, the fault code, the time the fault was reported, the fault severity, the impact on service, and the name of the fault in plain language. Figure 1-1 Alarm information retrieved using the CLI Fault severity Each fault is associated with one of the default severity types listed in the following table. Table 1-2 Fault severities Severity Critical Major Minor Not alarmed Not reported A failure that is likely causing serious loss or interruption of traffic. A failure that could potentially lead to loss or interruption of traffic. A failure that does not significantly affect traffic. A fault that results in a standing condition, not an alarm. A non-alarmed fault that is discovered only when standing conditions are polled. 1-2 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

15 Fault monitoring on the BTI7800 Notifications for raise and clear events are never generated for faults with Not Reported (NR) severity, and active occurrences can be discovered only when the active conditions list is polled. Impact on service In addition to fault severity, reporting indicates whether a fault impacts service (service-affecting true) or not (service-affecting false). Depending on the entity type, the operational status of the entity is reported as down when a fault is service-affecting. Product Release STANDARD 1-3

16 Fault monitoring on the BTI7800 Maintenance signaling When normal traffic cannot be transmitted from a port, for example, when a received signal is in a failed state or when a port is administratively disabled and traffic is disrupted, the BTI7800 Series will usually forward a maintenance signal from the transmit port to indicate to the downstream node that a local outage exists. For all interface protocols, the default maintenance signal (Table 1-3) enables the receiving node to conclude that the link to the adjacent upstream node is intact. Table 1-3 Default maintenance signals - interface protocols Protocol Default Maintenance Signal OTN OTU ODU-AIS OTN ODU ODU-AIS Ethernet LF OC192, WAN PHY over OC192 AIS L STM64, WAN PHY over STM64 MS-AIS 1-4 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

17 C H A P T E R Alarms and conditions This section provides detailed information about fault points monitored on the BTI7800, including procedures for clearing alarms raised against entities in the system. Table 2-1 BTI7800 alarms and conditions Code Entities Affected Default Severity Service Affecting AirFilterAbsence (Air Filter Absent) BTI7814 chassis Major No (false) AIS L (Alarm Indication Signal - Line, SONET) APR (Automatic Power Reduction) DOL ports SONET interfaces Not alarmed Yes (true) Terminal amplifier client ports Terminal amplifier DCM ports APSD (Automatic Power Shutdown) DOL ports Terminal amplifier line ports Critical Critical Yes (true) Yes (true) BDI (Backward Defect Indication, OTN) OTN OTU interfaces Not alarmed No (false) ContComS (Control Communications Failure, Span Section) DOL optical service channels Terminal amplifier Optical Supervisory Channels Major Yes (true) Product Release STANDARD 2-1

18 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting DiskHighUsage (Disk High Usage) Management modules EnvCurrentHighTh (Current Above High Temperature) EnvCurrentLowTh (Current Below Low Temperature) EnvTempHighTh (Environment Temperature Above High Threshold) EnvTempLowTh (Environment Temperature Above Low Threshold) EnvVoltHighTh (Environment Voltage Above High Threshold) EnvVoltLowTh (Environment Voltage Below Low Threshold) EqptComm (Equipment Management Communications Failure) Traffic modules Major No (false) AC PEM Major Yes (true) AC PEM Major Yes (true) PEMs Fan modules Management modules Traffic modules PEMs Fan modules Management modules Traffic modules AC PEMs Traffic modules AC PEMs Traffic modules EqptDgrd (Equipment Degrade) UFM modules Major Not alarmed Major Major Yes (true) Yes (true) Yes (true) Yes (true) Traffic modules Major Depends on cause of alarm BIC modules EqptFail (Equipment Failure) Equipment Management modules Traffic modules Pluggable transceivers EqptMism (Equipment Mismatch) Equipment Management modules Traffic modules Pluggable transceivers Major Critical Critical Yes (true) Yes (true) Yes (true) 2-2 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

19 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting EqptMiss (Equipment Missing) Equipment FanSpeedLowTh (Fan Speed Below Threshold) FECI (Far-End Node Configuration Mismatch) FEIM (Far-End Node Identification Mismatch) FirmUpgrdInProg (Automatic Shelf Management Firmware Upgrade in Progress) FirmUpgrdFail (Shelf Management Firmware Upgrade Failed) FirmUpgrdReqd (Firmware Upgrade Required) Forced (Forced Protection Switch Active) Management modules Traffic modules Pluggable transceivers Critical Yes (true) Fan module Major Yes (true) DOL ports Terminal amplifier Optical Supervisory Channels DOL ports Terminal amplifier Optical Supervisory Channels Major Major Yes (true) Yes (true) Management modules Not alarmed No (false) Management modules Major No (false) Management modules Major No (false) Wavelength protection ports Not alarmed No (false) HighBer (High Bit-Error Rate) Ethernet interfaces Major No (false) InvUnknown (Inventory Unknown) Pluggable transceivers Major No (false) LaserFail (Laser Fail) OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels Critical Yes (true) Product Release STANDARD 2-3

20 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting LaserTempHighTh (Laser Temperature Above High Temperature Threshold) LaserTempLowTh (Laser Temperature Below Low Temperature Threshold) OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels Major Major No (false) No (false) LCK (Locked, ODU) OTN ODU interfaces Critical Yes (true) LF (Local Fault) Ethernet interfaces Not alarmed No (false) Lockout (Lockout of Protection) Wavelength protection ports LOF (Loss of Frame) OTN OTU interfaces SONET/SDH interfaces LoLightRx (Loss of Light, Receive) DOL PRE ports DOL optical service channels DOL optical multiplex sections DOL optical channels Wavelength protection ports Terminal amplifier ports Not alarmed Critical Critical No (false) Yes (true) Yes (true) LoLightTx (Loss of Light, Transmit) DOL optical channels Major Yes (true) LOM (Loss of Multiframe) OTN OTU interfaces Critical Yes (true) 2-4 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

21 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting LOS (Loss of Signal) OTN OTU interfaces LoSpecRx (Loss out of Specification, Receive) Ethernet interfaces SONET/SDH interfaces Wavelength channels Critical Yes (true) DOL ports Critical Yes (true) LoSync (Loss of Synchronization) Ethernet interfaces Critical Yes (true) LPBK (Loopback Operated) OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces MemHighUsage (Memory High Usage) Management modules ModTempHighTh (Module Temperature Above High Threshold) ModTempLowTh (Module Temperature Below Low Threshold) ModTempShutdown (Module Temperature Shutdown) MS-AIS (Multiplex Section Alarm Indication Signal, SDH) MS-RDI (Multiplex Section Remote Defect Indication, SDH) NonCoLocatedController (Controllers are in Different Chassis) ObrHt (Optical Backreflection High Threshold Exceeded) Traffic modules OTN OTU4 line interfaces OTN OTU4 line interfaces OTN OTU4 line interfaces Not alarmed Major Major Major Critical No (false) No (false) No (false) No (false) Yes (true) SDH interfaces Not alarmed Yes (true) SDH interfaces Not alarmed No (false) BTI7814 chassis BTI7802 chassis Terminal amplifier Optical Supervisory channels Critical Minor Yes (true) Yes (true) OchAis (Alarm Indication Signal, OCH) DOL optical channels Not alarmed Yes (true) OchOci (Open Connection Indication, OCH) DOL optical channels Critical Yes (true) OchUeq (OCH Unequipped) DOL optical channels Critical Yes (true) OCI (Open Connection Indication, ODU) OTN ODU interfaces Critical Yes (true) ODU-AIS (ODU Alarm Indication Signal) OTN interfaces Not alarmed Yes (true) OmsAis (Alarm Indication Signal, OMS) OneCableDisconnected (One Multi- Chassis Cable Disconnected) DOL optical multiplex sections BTI7814 chassis BTI7802 chassis Not alarmed Major Yes (true) Yes (true) Product Release STANDARD 2-5

22 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting OprHighTh (Optical Power Received Above High Threshold) OprLowTh (Optical Power Received Below Low Threshold) OptHighTh (Optical Power Transmitted Above High Threshold) OptLowTh (Optical Power Transmitted Below Low Threshold) OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Wavelength channels Major Major Major Major No (false) No (false) No (false) No (false) OTU-AIS (OTU Alarm Indication Signal) OTN OTU interfaces Not alarmed Yes (false) PartitionFault (Disk Partition Fault Detected) PosRxHigh (Receive Power Out of Specification, High) PosRxLow (Receive Power Out of Specification, Low) PosTxHigh (Transmit Power Out of Specification, High) PosTxLow (Transmit Power Out of Specification, Low) Management modules Traffic modules Major No (false) DOL optical channels Minor Yes (true) DOL optical multiplex sections DOL optical channels Major Yes (true) DOL optical channels Critical Yes (true) DOL optical channels Critical Yes (true) PowerAbsent (No Power Available) PEM Critical Yes (true) PRBS (PRBS Test Activated) OTN OTU interfaces Ethernet interfaces SONET/SDH interfaces Not alarmed No (false) PyldMism (Payload Mismatch) OTN ODU interfaces Critical Yes (true) RDI-L (Remote Defect Indication, Line) SONET interfaces Not alarmed No (false) 2-6 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

23 Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting RF (Remote Fault) Ethernet interfaces Not alarmed No (false) ScmNmiDown (System Controller Management Interface Down) scmnonmconn (No Network Management Connectivity on SCM) SD (Signal Degrade) OTN OTU interfaces Management modules Major Yes (true) Management modules Critical Yes (true) SONET/SDH interfaces TIM (Trace Identifier Mismatch) OTN OTU interfaces TlossRxHt (Loss Above High Threshold, Receive) TlossRxLt (Loss Below Low Threshold, Receive) SONET/SDH interfaces Terminal amplifier line ports Terminal amplifier line ports UPGRD (Upgrade in Progress) Management modules Traffic modules Minor Critical Minor Minor Minor No (false) Yes (true) Yes (true) Yes (true) Yes (true) Product Release STANDARD 2-7

24 AirFilterAbsence Table 2-2 Alarm details Parameter Code /Cause AirFilterAbsence Air Filter Absent: The air filter required for operation of the chassis has not been detected in the chassis. Entities Affected BTI7800 chassis (see Table 2-3). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy This alarm is supported on the BTI7814 chassis only. Major. No (false). See Clearing an AirFilterAbsence alarm. Table 2-3 BTI7800 chassis Equipment Indicator Status chassis:<1 2> BTI See equipment specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing an AirFilterAbsence alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before installing equipment in the chassis. Step 1 Confirm whether an air filter is present in the chassis. If an air filter is present, go to Step 2. If an air filter is not present, go to Step 3. Step 2 Ensure that the air filter is properly seated in the chassis, and then go to Step 4. Step 3 Step 4 Install an air filter in the chassis. Check for alarms on the chassis. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. 2-8 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

25 AIS L Table 2-4 Condition details Parameter Code ais-l Alarm Indication Signal Line (AIS-L), SONET: The local interface has received an AIS-L signal from the NE at the far end of the fiber, indicating that no SONET signal is being transmitted upstream of (and toward) the local NE. See also Maintenance signaling. Entities Affected SONET (OC192, WAN PHY OC192) interfaces (see Table 2-5). Default Severity Not alarmed. Service Affecting Yes (true). Condition Clearing See Clearing an AIS-L condition. Related Fault Hierarchy See OC192, WAN PHY over OC192 interface fault hierarchy. Table 2-5 SONET (OC192, WAN PHY OC192) interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanoc192:<chassis>/<slot>/<subslot>/<port> Clearing an AIS-L condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms upstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-9

26 APR Table 2-6 Alarm details Parameter Code apr Entities Affected DOL ports (see Table 2-7). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Automatic Power Reduction: For safety reasons, the local port has automatically reduced laser power. For more information about APR, see the BTI7800 Series Software Configuration Guide. Terminal amplifier client and DCM ports (see Table 2-8). A fiber cut has been detected. Critical. Yes (true). See: Clearing an APR alarm (PRE port) Clearing an APR alarm (terminal amplifier port) See: DOL port fault hierarchy Terminal amplifier port fault hierarchy Table 2-7 DOL ports port:<chassis>/<slot>/1/pre PRE Fault LED, PRE port On Table 2-8 Terminal amplifier ports client:<chassis>/<slot>/1/<portnum> AMP1 Fault LED, DCM port On dcm:<chassis>/<slot>/1/<portnum> Fault LED, C1 port Clearing an APR alarm (PRE port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for a LoLightRx alarm on the host module's PRE In port. Inspect the fiber at the following locations, and ensure that the fiber is intact, thoroughly clean, and correctly connected: 2-10 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

27 Between the PRE module's Out port and the host module's PRE In port. Between the host module's PRE Out port and the PRE module's In port. Step 3 Check for alarms on the PRE port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Clearing an APR alarm (terminal amplifier port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Do one of the following: If the alarm is raised against the client Out port, retrieve statistics for the port to view the values of the APR optical backreflection and Optical power transmitted counters. show statistics current client:identifier If the alarm is raised against the DCM Out port, check for a LoLightRx alarm on the DCM In port. Step 2 Step 3 Inspect the fiber, and ensure that it is intact, thoroughly clean, and correctly connected. Check for alarms on the terminal amplifier line port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-11

28 APSD Table 2-9 Alarm details Parameter Code apsd Automatic Power Shutdown: The local port has automatically shut down its laser because either the optical power received has dropped below the Loss of Light, Receive threshold or APSD has been triggered on the NE at the far end of the fiber. For more information about APSD, see the BTI7800 Series Software Configuration Guide. Entities Affected DOL ports (see Table 2-10). Terminal amplifier line ports (see Table 2-11). Possible Causes The fiber connection is poor. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy There is a problem with the fiber. There is a problem at the far-end transmitter. Critical. Yes (true). See: Clearing an APSD alarm (DOL port) Clearing an APSD alarm (terminal amplifier line port) See: DOL port fault hierarchy Terminal amplifier port fault hierarchy Table 2-10 DOL ports port:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On port:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-11 Terminal amplifier line ports line:<chassis>/<slot>/1/<portnum> AMP1 Fault LED, Line port On 2-12 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

29 Clearing an APSD alarm (DOL port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Check for and clear the following alarms and conditions: LoLightRx raised against the DOL OSC and the DOL OMS ContComS raised against the DOL OSC OmsAis raised against the DOL OMS Check for alarms on the DOL port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Check for and clear an APSD alarm on the NE at the far-end of the fiber. Check for alarms on the local DOL port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Clearing an APSD alarm (terminal amplifier line port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Check whether an LoLightRx alarm has been raised against the input amplifier Optical Supervisory Channel on the line port, and clear the alarm if it exists. Check for alarms on the terminal amplifier line port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Check for and clear an APSD alarm on the far-end NE. Check for alarms on the local terminal amplifier line port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-13

30 BDI Table 2-12 Condition details Parameter Code /Cause bdi Backward Defect Indication, OTN: The local interface has received a BDI signal from the NE at the far end of the fiber, indicating that no OTN OTU signal is being transmitted downstream of (and away from) the local NE. (See also Maintenance signaling.) Entities Affected OTN OTU interfaces (see Table 2-13). Default Severity Not alarmed. Service Affecting No (false). Condition Clearing See Clearing a BDI condition. Related Fault Hierarchy See OTN interface fault hierarchy. Table 2-13 OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Clearing a BDI condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms downstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

31 ContComS Table 2-14 Alarm details Parameter Code Possible Cause contcoms Control Communications Failure, Span Section: Control communications with the NE at either end of the span section have failed. There are alarms on the far-end OSC. Entities Affected DOL optical service channels (see Table 2-15). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Terminal amplifier Optical Supervisory Channels (see Table 2-16). Major. Yes (true). See Clearing a ContComS alarm. See: DOL OSC fault hierarchy Terminal amplifier port fault hierarchy Table 2-15 DOL optical service channels (OSCs) osc:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On osc:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-16 Terminal amplifier Optical Supervisory Channels (OSCs) osc:<chassis>/<slot>/1/<portnum>.<oscnum> AMP1 Product Release STANDARD 2-15

32 Clearing a ContComS alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Check for and clear alarms on OSC entities at both the local and far-end NEs. Check the far-end NE for conditions indicating a module reset. Check for alarms on the local OSC. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

33 DiskHighUsage Table 2-17 Alarm details Parameter Code diskhighusage Disk High Usage. Entities Affected Management and traffic modules (see Table 2-18). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. No (false). This alarm indicates that disk usage on the module has exceeded 90%. For information about clearing this alarm, contact your next level of support. Table 2-18 Management and traffic modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS4 Product Release STANDARD 2-17

34 EnvCurrentHighTh Table 2-19 Alarm details Parameter Code /Cause envcurrenthighth Entities Affected Equipment (see Table 2-20). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Current Above High Threshold: The output current at the AC power entry module (PEM) is above the high-current threshold. For information, see Output-current thresholds. Major. Yes (true). See Clearing an EnvCurrentHighTh alarm. See Environment fault hierarchy. Table 2-20 Equipment Equipment Indicator Status pem:<chassis>/<slot> AC PEM See the PEM specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing an EnvCurrentHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment. Step 1 Step 2 Step 3 Step 4 Retrieve environment information to view output-current readings for the PEM: show environment current Reseat the PEM. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Replace the PEM. Check for alarms on the PEM. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

35 EnvCurrentLowTh Table 2-21 Alarm details Parameter Code /Cause envcurrentlowth Entities Affected Equipment (see Table 2-22). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Current Below Low Threshold: The output current at the AC power entry module (PEM) is below the low-current threshold. For information, see Output-current thresholds. Major. Yes (true). See Clearing an EnvCurrentLowTh alarm. See Environment fault hierarchy. Table 2-22 Equipment Equipment Indicator Status pem:<chassis>/<slot> AC PEM See the PEM specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing an EnvCurrentLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment. Step 1 Step 2 Step 3 Step 4 Retrieve environment information to view current readings for the PEM: show environment current Reseat the PEM. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Replace the PEM. Check for alarms on the PEM. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-19

36 EnvTempHighTh Table 2-23 Alarm details Parameter Code /Cause envtemphighth Environment Temperature Above High Threshold: The temperature at the equipment or module has exceeded the high temperature threshold. For information, see Temperature thresholds - equipment and traffic modules. Entities Affected Equipment (see Table 2-24). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Management and traffic modules (see Table 2-25). Major. Yes (true). See Clearing an EnvTempHighTh alarm. See Environment fault hierarchy. Table 2-24 Equipment Equipment Indicator Status pem:<chassis>/<slot> PEM See equipment specifications in the fan:<chassis>/<slot> Cooling module BTI7800 Series Hardware Overview and Installation Guide. Table 2-25 Management and traffic modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. bic:<chassis>/<slot>/<subslot> BIC roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

37 Clearing an EnvTempHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module or to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment or traffic modules. Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Retrieve environment information to view the temperature reading for the equipment or traffic module: show environment temperature Check for and clear a FanSpeedLowTh alarm on each cooling module installed in the chassis. Check for alarms on the affected equipment or traffic module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 4. Ensure that the ambient temperature is within the specified range for chassis operation. For information, see the BTI7800 Series Hardware Overview and Installation Guide. Check for alarms on the affected equipment or traffic module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 6. Do the following: If the alarm is raised against equipment, reseat the equipment. If the alarm is raised against a traffic module, perform a warm reboot of the module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 8. Replace the equipment or module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-21

38 EnvTempLowTh Table 2-26 Condition details Parameter Code /Cause envtemplowth Environment Temperature Above Low Threshold: The temperature at the equipment or module is higher than the temperature at the low end of the hightemperature threshold range. For information, see Temperature thresholds - equipment and traffic modules. Entities Affected Equipment (see Table 2-27). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Management and traffic modules (see Table 2-28). Not alarmed. Yes (true). See Clearing an EnvTempLowTh condition. See Environment fault hierarchy. Table 2-27 Equipment Equipment Indicator Status pem:<chassis>/<slot> PEM fan:<chassis>/<slot> Cooling module Table 2-28 Management and traffic modules cmm:<chassis>/<slot> CMM ufm:<chassis>/<slot> UFM bic:<chassis>/<slot>/<subslot> BIC roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

39 Clearing an EnvTempLowTh condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module or to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment or traffic modules. Step 1 Step 2 Step 3 Step 4 Step 5 Retrieve environment information to view the temperature reading for the equipment or traffic module: show environment temperature Ensure that the ambient temperature is within the specified range for chassis operation. For information, see the BTI7800 Series Hardware Overview and Installation Guide. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 4. Do the following: If the alarm is raised against equipment, reseat the equipment. If the alarm is raised against a traffic module, perform a warm reboot of the module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-23

40 EnvVoltHighTh Table 2-29 Alarm details Parameter Code /Cause envvolthighth Environment Voltage Above High Threshold: The voltage on the equipment (PEM) or module exceeds the high-voltage threshold. For information, see Voltage thresholds. Caution Continued operation might cause equipment damage. Entities Affected Equipment (see Table 2-30). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Traffic modules (see Table 2-31). Major. Yes (true). See Clearing an EnvVoltHighTh alarm. See Environment fault hierarchy. Table 2-30 Equipment Equipment Indicator Status pem:<chassis>/<slot> AC PEM See the PEM specifications in the BTI7800 Series Hardware Overview and Installation Guide. Table 2-31 Traffic modules ufm:<chassis>/<slot> UFM See Appendix C, BTI7800 Series amp:<chassis>/<slot> AMP1 module and BIC LED behavior. wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

41 Clearing an EnvVoltHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module or to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment or traffic modules. Step 1 Step 2 Step 3 Step 4 Step 5 Retrieve environment information to view voltage readings for the equipment or traffic module: show environment voltage Do the following: If the alarm is raised against equipment, reseat the equipment. If the alarm is raised against a traffic module, perform a warm reboot of the module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 4. Replace the equipment or module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-25

42 EnvVoltLowTh Table 2-32 Alarm details Parameter Code /Cause envvoltlowth Environment Voltage Above High Threshold: The voltage on the equipment (PEM) or module is below the low-voltage threshold. For information, see Voltage thresholds. Caution Continued operation might cause equipment damage. Entities Affected Equipment (see Table 2-33). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Traffic modules (see Table 2-34). Major. Yes (true). See Clearing an EnvVoltLowTh alarm. See Environment fault hierarchy. Table 2-33 Equipment Equipment Indicator Status pem:<chassis>/<slot> AC PEM See the PEM specifications in the BTI7800 Series Hardware Overview and Installation Guide. Table 2-34 Traffic modules ufm:<chassis>/<slot> UFM See Appendix C, BTI7800 Series amp:<chassis>/<slot> AMP1 module and BIC LED behavior. wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

43 Clearing an EnvVoltLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module or to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment or traffic modules. Step 1 Step 2 Step 3 Step 4 Step 5 Retrieve environment information to view voltage readings for the equipment or traffic module: show environment voltage Do the following: If the alarm is raised against equipment, reseat the equipment. If the alarm is raised against a traffic module, perform a warm reboot of the module. Check for alarms on the equipment or module: If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 4. Replace the equipment or module. Check for alarms on the equipment or module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-27

44 EqptComm Table 2-35 Alarm details Parameter Code /Cause eqptcomm Equipment Management Communications Failure: The CMM is not able to communicate with the equipment. Entities Affected Traffic modules (see Table 2-36). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. Depends on reason alarm has been raised. See Clearing an EqptComm alarm. See Equipment fault hierarchy. Table 2-36 Traffic modules ufm:<chassis>/<slot> UFM See Appendix C, BTI7800 Series roadm:<chassis>/<slot> ROADM2 module and BIC LED behavior. ila:<chassis>/<slot> ILA wps:<chassis>/<slot> WPS4 amp:<chassis>/<slot> AMP1 Clearing an EqptComm alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting an active CMM. Step 1 Step 2 Perform a warm reboot of the active CMM, and then check for alarms on the affected module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 2. Perform a cold reboot of the active CMM, and then check for alarms on the affected module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

45 EqptDgrd Table 2-37 Alarm details Parameter Code eqptdgrd /Cause Equipment Degrade: Initialization of a module has failed. Entities Affected Traffic modules (see Table 2-38). Default Severity Major. Service Affecting Yes (true). Alarm Clearing See Clearing an EqptDgrd alarm. Related Fault Hierarchy See Equipment fault hierarchy. Table 2-38 Traffic modules ufm:<chassis>/<slot> UFM See Appendix C, BTI7800 Series module bic:<chassis>/<slot>/<subslot> 1x CFP BIC or and BIC LED behavior. 12x SFP+ BIC Clearing an EqptDgrd alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before either rebooting or changing the administrative status of equipment. Step 1 Step 2 Do the following: For a UFM module, perform a cold reboot of the module. For a BIC module, administratively disable the module, and then administratively enable it. Check for alarms on the module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-29

46 EqptFail Table 2-39 Alarm details. Parameter Code /Cause eqptfail Equipment Failure: A hardware self-test has detected faulty equipment. Entities Affected Equipment (see Table 2-40). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Table 2-40 Equipment Management and traffic modules (see Table 2-41). Pluggable transceivers (see Table 2-41). Critical. Yes (true). See Clearing an EqptFail alarm. See Equipment fault hierarchy. Equipment Indicator Status cap:<chassis>/<slot> CAP See equipment specifications in the fan:<chassis>/<slot> Cooling module BTI7800 Series Hardware Overview and Installation Guide. esl:<chassis>/<slot> ESL pem:<chassis>/<slot> PEM Table 2-41 Management and traffic modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. bic:<chassis>/<slot>/<subslot> BIC roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

47 Table 2-42 Pluggable transceivers <transceiver-type>:<chassis>/<slot>/<subslot>/ <port> where transceiver-type corresponds to the type of transceiver installed in the port; for example, cfp or sfpplus. Transceiver Indicator Status CFP, SFP+ Fail LED, CFP or SFP+ client port on BIC pre:<chassis>/<slot> PRE Fail LED, PRE port On Clearing an EqptFail alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment. Step 1 Step 2 Step 3 Step 4 Reseat the equipment (equipment, traffic module, or pluggable transceiver). Check for alarms. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Replace the equipment. Check for alarms on the equipment. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-31

48 EqptMism Table 2-43 Alarm details Parameter Code /Cause eqptmism Equipment Mismatch: The installed equipment does not match the equipment provisioned for the slot or subslot. Entities Affected Equipment (see Table 2-44). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Traffic modules (see Table 2-45). Pluggable transceivers (see Table 2-46). Critical. Yes (true). See Clearing an EqptMism alarm. See Equipment fault hierarchy. Table 2-44 Equipment Equipment Indicator Status fan:<chassis>/<slot> Cooling module See equipment specifications in the esl:<chassis>/<slot> ESL BTI7800 Series Hardware Overview and Installation Guide. pem:<chassis>/<slot> PEM Table 2-45 Traffic modules ufm:<chassis>/<slot> UFM See Appendix C, BTI7800 Series bic:<chassis>/<slot>/<subslot> BIC module and BIC LED behavior. roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

49 Table 2-46 Pluggable transceivers <transceiver-type>:<chassis>/<slot>/<subslot>/ <port> where transceiver-type corresponds to the type of transceiver installed in the port; for example, cfp or sfpplus. Transceiver Indicator Status CFP, SFP+ Fail LED, CFP or SFP+ client port on BIC On Clearing an EqptMism alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing equipment. Step 1 Step 2 Step 3 Retrieve equipment-provisioning information: show equipment Do one of the following: Modify the provisioned settings so that they match those of the installed equipment (equipment, traffic module, or pluggable transceiver). For information, see the BTI7800 Software Configuration Guide. Replace the equipment with equipment that matches the provisioned settings. Check for alarms on the equipment. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-33

50 EqptMiss Table 2-47 Alarm details Parameter Code /Cause eqptmiss Equipment Missing: Provisioned equipment is not physically present in a slot or subslot. Entities Affected Equipment (see Table 2-48). Default Severity Service Affecting Alarm clearing Related Fault Hierarchy Management and traffic modules (see Table 2-49). Pluggable transceivers (see Table 2-50). Critical. Yes (true). See Clearing an EqptMiss alarm. See Equipment fault hierarchy. Table 2-48 Equipment Equipment Indicator Status fan:<chassis>/<slot> Cooling module esl:<chassis>/<slot> ESL pem:<chassis>/<slot> PEM Table 2-49 Management and traffic modules cmm:<chassis>/<slot> CMM ufm:<chassis>/<slot> UFM bic:<chassis>/<slot>/<subslot> BIC roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

51 Table 2-50 Pluggable transceivers <transceiver-type>:<chassis>/<slot>/<subslot>/ <port> where transceiver-type corresponds to the type of transceiver installed in the port; for example, cfp or sfpplus. Transceiver Indicator Status CFP, SFP+ pre:<chassis>/<slot> PRE Clearing an EqptMiss alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Refer to the BTI7800 Series Hardware Overview and Installation Guide before installing equipment. Step 1 Step 2 Retrieve inventory and provisioned-equipment information: show inventory show equipment Confirm whether the equipment (equipment, traffic module, or pluggable transceiver) is present in the slot or subslot. If the equipment is present in the slot or subslot, go to Step 3. If the equipment is not present in the slot or subslot, go to Step 4. Step 3 Ensure that the equipment is properly seated in the slot or subslot, and then go to Step 5. Step 4 Step 5 Install the missing equipment, ensuring that its attributes match the attributes of the equipment provisioned for the slot or subslot. For information, see the BTI7800 Hardware Overview and Installation Guide. Check for alarms on the equipment. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-35

52 FanSpeedLowTh Table 2-51 Alarm details Parameter Code fanspeedlowth Entities Affected Equipment (see Table 2-52). Fan Speed Below Threshold: The fan speed of the cooling module is below the low threshold. For information, see Fan-speed thresholds. Possible Cause The cooling module is faulty. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The power entry module is faulty. Major. Yes (true). See Clearing a FanSpeedLowTh alarm. Table 2-52 Equipment Equipment Indicator Status fan:<chassis>/<slot> Cooling module See cooling module specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing a FanSpeedLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before reseating (removing and reinstalling) or replacing equipment. Step 1 Retrieve fan-speed information for the cooling modules installed in the chassis: show environment fanspeed Step 2 Ensure that the ambient temperature is within the specified range for chassis operation. See the BTI7800 Series Hardware Overview and Installation Guide for information about environmental site requirements. Step 3 Check for and clear alarms raised against each PEM, and then check for alarms on the cooling module. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

53 Step 4 Step 5 Reseat the cooling module, and then check for alarms. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 5. Replace the cooling module, and then check for alarms. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-37

54 FECI Table 2-53 Alarm details Parameter Code /Cause feci Far-End Node Configuration ID Mismatch: Either the configuration of the DOL fiberconnection is not supported or the expected far-end degree and group values provisioned on a terminal amplifier Optical Supervisory Channel do not match the actual (far-end) degree and group values. Entities Affected DOL ports (see Table 2-54). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Terminal amplifier Optical Supervisory Channels (see Table 2-55). Major. Yes (true). See: Clearing a FECI alarm (DOL port) Clearing a FECI alarm (terminal amplifier OSC) See: DOL port fault hierarchy Terminal amplifier port fault hierarchy Table 2-54 DOL ports port:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On port:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-55 Terminal amplifier Optical Supervisory Channels (OSCs) osc:<chassis>/<slot>/1/<portnum>.<oscnum> AMP BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

55 Clearing a FECI alarm (DOL port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve DOL fiber-connection information to identify the unsupported fiber-connection configuration: show dol fiber-conn Delete the unsupported fiber connection, and reprovision the fiber connection using a supported configuration. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the DOL port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Clearing a FECI alarm (terminal amplifier OSC) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve information for the OSC: show amp Compare the values of the following pairs of attributes: Expected Far-end Degree/Actual Far-end Degree Expected Far-end Group/Actual Far-end Group Delete the OSC at either the local or far-end NE, and reprovision the OSC so that the expected and actual degree and/or group values are the same. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the OSC. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-39

56 FEIM Table 2-56 Alarm details Parameter Code /Cause feim Far-End Node Identification Mismatch: Either the provisioned endpoints of a DOL fiber connection do not match the actual endpoints or the expected far-end system information provisioned on a terminal amplifier Optical Supervisory Channel does not match the actual (far-end) system information Entities Affected DOL ports (see Table 2-57). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Terminal amplifier Optical Supervisory Channels (see Table 2-58). Major. Yes (true). See: Clearing a FEIM alarm (DOL port) Clearing a FEIM alarm (terminal amplifier OSC) See: DOL port fault hierarchy Terminal amplifier port fault hierarchy Table 2-57 DOL ports port:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On port:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-58 Terminal amplifier Optical Supervisory Channels (OSCs) osc:<chassis>/<slot>/1/<portnum>.<oscnum> AMP BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

57 Clearing a FEIM alarm (DOL port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve DOL fiber-connection information to determine whether the provisioned endpoints or the actual endpoints of the fiber connection are incorrect: show dol fiber-conn Delete the incorrect fiber connection, and reprovision the fiber-connection so that the mismatch is resolved. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the DOL port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Clearing a FEIM alarm (terminal amplifier OSC) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve information for the OSC: show amp Compare the values of the following pairs of attributes: Expected Far-end System ID/Actual Far-end System ID Expected Far-end IP Address/Actual Far-end IP Address Delete the OSC at either the local or far-end NE, and reprovision the OSC so that the expected and actual system ID and/or IP address values are the same. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the OSC. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-41

58 FirmUpgrdInProg Table 2-59 Condition details Parameter Code /Cause firmupgrdinprog Automatic Shelf Management Firmware Upgrade in Progress: A shelf management (SHMM) firmware upgrade is in progress. Entities Affected Management modules (see Table 2-60) Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. No (false). This condition clears when the firmware is successfully upgraded. For information, see the BTI7800 Series Software Configuration Guide. Table 2-60 Management modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series module and BIC LED behavior BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

59 FirmUpgrdFail Table 2-61 Alarm details Parameter Code /Cause firmupgrdfail Shelf Management Firmware Upgrade Failed: A shelf management (SHMM) firmware upgrade (manual or automatic) has failed. Entities Affected Management modules (see Table 2-62). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. No (false). See Clearing a FirmUpgrdFail alarm. Table 2-62 Management modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series module and BIC LED behavior. Clearing a FirmUpgrdFail alarm Step 1 Step 2 Reattempt the firmware upgrade. For information, see the BTI7800 Series Hardware Overview and Installation Guide. Check for alarms on the CMM. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-43

60 FirmUpgrdReqd Table 2-63 Alarm details Parameter Code /Cause firmupgrdreqd Firmware Upgrade Required: The version of firmware running on the Chassis Management Module (CMM) does not match the version of the Shelf Management (SHMM) firmware. Entities Affected Management modules (see Table 2-64). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. No (false). This alarm clears when the firmware is successfully upgraded. For information, see the BTI7800 Series Software Configuration Guide. Table 2-64 Management modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series module and BIC LED behavior BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

61 Forced Table 2-65 Condition details Parameter Code /Cause forced Forced Protection Switch Active: The operator has forced a protection switch. Entities Affected Wavelength protection ports (see Table 2-66). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. No (false). This condition clears when the protection switch is released. For information, see the BTI7800 Series Software Configuration Guide. Table 2-66 Wavelength protection ports wpsport:<chassis>/<slot>/l<n> where n is in the range of 1A to 4A or 1B to 4B. WPS4 Product Release STANDARD 2-45

62 HighBer Table 2-67 Alarm details Parameter Code highber High Bit-Error Rate: The local port has detected a bit-error rate in the received signal that is 10-4 or greater. Entities Affected Ethernet interfaces (see Table 2-68). Possible Causes Either the fiber link or the optical connection is degraded. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy There is excessive attenuation of the signal, causing high a signal-to-noise ratio. Major. No (false). See Clearing a HighBer alarm. See Ethernet interface fault hierarchy. Table 2-68 Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port 2-46 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

63 Clearing a HighBer alarm Step 1 Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Retrieve detailed information for the interface to determine whether the value of the Optical Power Rx counter is within the range indicated by the Optical Power Received Minimum Threshold and Optical Power Received Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Step 4 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Ensure that no unintentional attenuation has been added to the fiber. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-47

64 InvUnknown Table 2-69 Alarm details Parameter Code invunknown /Cause Inventory Unknown: The installed pluggable transceiver is not readable. Entities Affected Pluggable transceivers (see Table 2-70). Default Severity Major. Service Affecting No (false). Alarm Clearing See Clearing an InvUnknown alarm. Related Fault Hierarchy Table 2-70 Pluggable transceivers <transceiver-type>:<chassis>/<slot>/<subslot>/ <port> where transceiver-type corresponds to the type of transceiver installed in the port; for example, cfp or sfpplus. Transceiver Indicator Status CFP, SFP+ Fail LED, 100GE or 10GE port On Clearing an InvUnknown alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing a transceiver. Step 1 Step 2 Replace the unknown transceiver with a readable transceiver. For information about supported transceivers, see Appendix B, BTI7800 Series transceivers. Check for alarms on the port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

65 LaserFail Table 2-71 Alarm details Parameter Code laserfail /Cause Laser Fail: The transmit laser of the transceiver has failed. Entities Affected OTN OTU interfaces (see Table 2-72). Ethernet interfaces (see Table 2-73). SONET/SDH interfaces (see Table 2-74). Wavelength channels (see Table 2-75). Default Severity Critical. Service Affecting Yes (true). Alarm Clearing See Clearing a LaserFail alarm. Related Fault Hierarchy See Common fault hierarchy - OTN and CBR ports. Table 2-72 OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table 2-73 Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table 2-74 SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-49

66 Table 2-75 Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing a LaserFail alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module or to the BTI7800 Series Hardware Overview and Installation Guide replacing a traffic module or transceiver. Step 1 Step 2 Step 3 Step 4 Perform a cold reboot: If the alarm is raised against a line-port interface provisioned on an integrated MSA transceiver, reboot the UFM that contains the integrated MSA. If the alarm is raised against a client-port interface provisioned on a pluggable transceiver installed in a BIC, reboot the UFM in which the BIC is installed. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, go to Step 3. Replace the either the UFM or the pluggable transceiver: If the alarm is raised against a line-port interface provisioned on an integrated MSA transceiver, replace the UFM. If the alarm is raised against a client-port interface provisioned on a pluggable transceiver, replace the pluggable transceiver. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

67 LaserTempHighTh Table 2-76 Alarm details Parameter Code lasertemphighth Laser Temperature Above High Temperature Threshold: The transmit laser temperature has exceeded the high temperature threshold. Entities Affected OTN OTU interfaces (see Table 2-77). Possible Causes Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-78). SONET/SDH interfaces (see Table 2-79). Wavelength channels (see Table 2-80). The transmit laser is malfunctioning. Major. No (false). See Clearing a LaserTempHighTh alarm. See Common fault hierarchy - OTN and CBR ports. Table 2-77 OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table 2-78 Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table 2-79 SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-51

68 Table 2-80 Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing a LaserTempHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing a traffic module or a transceiver. Step 1 Step 2 Step 3 Optionally, retrieve detailed information for the interface to view the Laser Temperature and Laser Temperature Max. Threshold values: show interface name:identifier detail Replace either the pluggable transceiver installed in the port or, if the alarm is raised against an interface provisioned on an integrated MSA, the UFM. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

69 LaserTempLowTh Table 2-81 Alarm details Parameter Code lasertemplowth Laser Temperature Below Low Temperature Threshold: The transmit laser temperature has fallen below the low temperature threshold. Entities Affected OTN OTU interfaces (see Table 2-82). Possible Causes Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-83). SONET/SDH interfaces (see Table 2-84). Wavelength channels (see Table 2-85). The transmit laser is malfunctioning. Major. No (false). See Clearing a LaserTempLowTh alarm. See Chapter 3, Fault masking. Table 2-82 OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table 2-83 Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table 2-84 SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-53

70 Table 2-85 Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing a LaserTempLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing a traffic module or a transceiver. Step 1 Step 2 Step 3 Optionally, retrieve detailed information for the interface to view the Laser Temperature and Laser Temperature Min. Threshold values: show interface name:identifier detail Replace either the pluggable transceiver installed in the port or, if the alarm is raised against a line-port interface provisioned on an integrated MSA, the UFM. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

71 LCK Table 2-86 Alarm details Parameter Code lck Locked, ODU: The local interface has received an ODU-LCK signal from the NE at the far end of the fiber, indicating that the connection at the transmitting interface is locked. Entities Affected OTN ODU interfaces (see Table 2-87). Possible Causes Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The transmitting OTN OTU interface at an upstream NE is either administratively disabled or in loopback mode. Critical. Yes (true). See Clearing an LCK alarm. See OTN interface fault hierarchy. Table 2-87 OTN ODU interfaces odu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port odu2:<chassis>/<slot>/<subslot>/<port.subinterface> odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Product Release STANDARD 2-55

72 Clearing an LCK alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve data for the transmitting OTU interface at the upstream NE to determine whether it is either administratively disabled (Admin State = disabled) or in loopback mode (Loopback = loopback) show interface name:identifier Do one of the following, referring to the BTI7800 Series Software Configuration Guide for more information: If the transmitting interface is administratively disabled, enable the interface. If the transmitting interface is in loopback mode, release the loopback. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

73 LF Table 2-88 Condition details Parameter Code lf Local Fault: The local interface has received a local-fault signal from the NE at the far end of the fiber, indicating that no Ethernet signal is being transmitted upstream of (and toward) the local NE. (See also Maintenance signaling.) Entities Affected Ethernet interfaces (see Table 2-89). Default Severity Not alarmed. Service Affecting No (false). Condition Clearing See Clearing an LF condition. Related Fault Hierarchy See Ethernet interface fault hierarchy. Table 2-89 Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC 12x SFP+ BIC Clearing an LF condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms upstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-57

74 Lockout Table 2-90 Condition details Parameter Code /Cause lockout Lockout of Protection: The operator has locked out a line port for protection. Entities Affected Wavelength protection ports (see Table 2-91). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. No (false). This condition clears when the protection switch is released. For information, see the BTI7800 Series Software Configuration Guide. Table 2-91 Wavelength protection ports wpsport:<chassis>/<slot>/l<n> where n is in the range of 1A to 4A or 1B to 4B. WPS BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

75 LOF Table 2-92 Alarm details Parameter Code lof Loss of Frame: Either the frame-alignment process is in the out-of-frame (OOF) state or a severely-errored-frame defect is present on an incoming signal. Entities Affected OTN OTU interfaces (see Table 2-93). SONET/SDH interfaces (see Table 2-94). Possible Causes Either the fiber link or the optical connection is severely degraded. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The far-end optical transmitter is faulty. Critical. Yes (true). See Clearing an LOF alarm. See: Common fault hierarchy - OTN and CBR ports OTN interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy Table 2-93 OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table 2-94 SONET /SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-59

76 Clearing an LOF alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Check for and clear all alarms raised against the far-end optical transmitter. Check for alarms on the local interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

77 LoLightRx Table 2-95 Alarm details Parameter Code /Cause lolightrx Loss of Light, Receive: The optical power received has dropped below the loss-oflight threshold. Entities Affected DOL PRE Ports (see Table 2-96). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy DOL optical service channels (see Table 2-97). DOL optical multiplex sections (see Table 2-98). DOL optical channels (see Table 2-99). Wavelength protection ports (see Table 2-100). Terminal amplifier ports (see Table 2-101). Critical. Yes (true). See: Clearing a LoLightRx alarm (DOL entity) Clearing a LoLightRx alarm (wavelength protection port) Clearing a LoLightRx alarm (terminal amplifier port) See: DOL port fault hierarchy DOL OSC fault hierarchy DOL OMS fault hierarchy DOL OCH fault hierarchy Terminal amplifier port fault hierarchy For wavelength protection ports, this alarm is not masked by any other alarm. Table 2-96 DOL PRE ports port:<chassis>/<slot>/0/pre PRE Fault LED, PRE port On port:<chassis>/<slot>/1/pre Product Release STANDARD 2-61

78 Table 2-97 DOL optical service channels (OSCs) osc:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On osc:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-98 DOL optical multiplex sections (OMSs) oms:<chassis>/<slot>/0/l1<> ROADM2 or ILA Fault LED, L1 port On oms:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Table 2-99 DOL optical channels (OCHs) och:<chassis>/<slot>/0/c<n>/<channel> where the range of n depends on the module and channel is an alphanumeric string. ROADM2 Table Wavelength protection ports wpsport:<chassis>/<slot>/l<n> where n is in the range of 1A to 4A or 1B to 4B. WPS4 Fault LED, Line<n> port On Table Terminal amplifier ports osc:<chassis>/<slot>/1/<portnum>.<oscnum> AMP1 line:<chassis>/<slot>/1/<portnum> Fault LED, Line port On dcm:<chassis>/<slot>/1/<portnum> Fault LED, DCM port client:<chassis>/<slot>/1/<portnum> Fault LED, C1 port 2-62 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

79 Clearing a LoLightRx alarm (DOL entity) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. In some ROADM network topologies with ILAs deployed, amplified spontaneous emissions (ASE) might accumulate sufficiently to cause this alarm to clear on provisioned but unoccupied optical channels. (The ASE will not be high enough to affect optical performance, however.) Step 1 Step 2 Retrieve statistics for the affected entity to view the value of the Optical power received counter: show statistics current name:identifier Do the following: If the alarm is raised against a PRE port, refer to DOL port power alarm thresholds, and then go to Step 3. If the alarm is raised against a DOL OSC, DOL OMS, or DOL OCH, refer to DOL OSC power alarm thresholds, DOL OMS power alarm thresholds, or DOL OCH power alarm thresholds, and then go to Step 4. Step 3 Check for and resolve any of the following problems, and then go to Step 5: The span fiber or patch panel fiber is cut or disconnected or has excessive loss. The amplifier transmitting into the patch fiber has shut down. There is excessive loss on each module that is connected to the alarmed port. There is excessive loss on upstream patch fibers. Step 4 Step 5 Check for and resolve any of the following problems: The far-end ROADM2 or ILA is not provisioned. The far-end DOL OMS, DOL OSC, or DOL OCH is administratively disabled. A fiber is either cut or disconnected. Check for alarms on the local DOL entity. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-63

80 Clearing a LoLightRx alarm (wavelength protection port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve information for the wavelength protection port to view the values of the received-loss-of-light threshold (LoLightRx Th) and the optical power received Opt.Pw.Rx counter: show protection wavelength port name:identifier Do the following: Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Check for and clear all alarms on the upstream NE. Check for alarms on the local port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Clearing a LoLightRx alarm (terminal amplifier port) Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve statistics for the port to view the value of the Optical power received counter: show statistics current name:identifier Check for and resolve any of the following problems: The span fiber or patch panel fiber is cut or disconnected or has excessive loss. The amplifier transmitting into the patch fiber has shut down. There is excessive loss on each module that is connected to the alarmed port. There is excessive loss on upstream patch fibers. The far-end port is administratively disabled. Check for alarms on the local port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

81 LoLightTx Table Alarm details Parameter Code /Cause lolighttx Loss of Light, Transmit: The optical power transmitted has dropped below the lossof-light threshold. Entities Affected DOL optical channels (see Table 2-103). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. Yes (true). See Clearing a LoLightTx alarm. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where the range of n depends on the module and channel is an alphanumeric string. ROADM2 Clearing a LoLightTx alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. In some ROADM network topologies with ILAs deployed, amplified spontaneous emissions (ASE) might accumulate sufficiently to cause this alarm to clear on provisioned but unoccupied optical channels. (The ASE will not be high enough to affect optical performance, however.) Step 1 Step 2 Step 3 Retrieve statistics for the DOL OCH to view the value of the Optical power received counter, and then refer to DOL OCH power alarm thresholds : show statistics current och:identifier Ensure that the upstream fiber connections are thoroughly clean and correctly connected. Check for alarms on the DOL optical channel. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-65

82 LOM Table Alarm details Parameter Code lom Loss of Multiframe: The multiframe alignment process is in the out-of-multiframe state. Entities Affected OTN OTU interfaces (see Table 2-105). Possible Causes Either the fiber link or the optical connection is degraded. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The far-end optical transmitter is faulty. Critical. Yes (true). See Clearing an LOM alarm. See OTN interface fault hierarchy. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Clearing an LOM alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Check for and clear all alarms on the far-end optical transmitter. Check for alarms on the local interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

83 LOS Table Alarm details Parameter Code los Loss of Signal: The local port has detected a loss of received signal power. Entities Affected OTN OTU interfaces (see Table 2-107). Ethernet interfaces (see Table 2-108). SONET/SDH interfaces (see Table 2-109). Wavelength channels (see Table 2-110). Possible Causes The fiber input is disconnected. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The far-end interface is not yet provisioned. The far-end transmit laser is disabled or has failed. Critical. Yes (true). See LOS. See: Common fault hierarchy - OTN and CBR ports OTN interface fault hierarchy Ethernet interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Product Release STANDARD 2-67

84 Table SONET /SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Table Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Monitoring and reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing an LOS alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Ensure that the light path on the optical line system, if it exists, is correctly provisioned and fault free. Check for and resolve the following problems: The far-end transmitter is disabled or has failed. The far-end interface is not provisioned. Check for alarms on the local interface If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

85 LoSpecRx Table Alarm details Parameter Code lospecrx Entities Affected DOL ports (see Table 2-112). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Loss out of Specification, Receive: The optical loss received is outside the specification range. Either the upstream fiber link or the optical connection is degraded. Critical. Yes (true). See Clearing a LoSpecRx alarm. See DOL port fault hierarchy. Table DOL ports port:<chassis>/<slot>/0/l1 ROADM2 or ILA Fault LED, L1 port On port:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Clearing a LoSpecRx alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve statistics for the DOL port to view the value of the Optical power loss in recv. direction counter, and then refer to DOL Rx-loss alarm thresholds : show statistics current port:identifier Ensure that the upstream fiber connections are intact, thoroughly clean, and correctly connected. Check for alarms on the DOL port. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-69

86 LoSync Table Alarm details Parameter Code losync Loss of Synchronization: The signal received on the local interface is sufficiently degraded that it cannot be synchronized. Entities Affected Ethernet interfaces (see Table 2-114). Possible Causes Either the fiber link or the optical connection is severely degraded. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The far-end optical transmitter is faulty. Critical. Yes (true). See Clearing a LoSync alarm. See Ethernet interface fault hierarchy. Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port 2-70 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

87 Clearing a LoSync alarm Step 1 Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Retrieve detailed information for the interface, and ensure that the value of the Optical Power Rx counter is within the range indicated by the Optical Power Received Minimum Threshold and Optical Power Received Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Step 4 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Check for and clear alarms on the far-end optical transmitter. Check for alarms on the local interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-71

88 LPBK Table Condition details Parameter Code /Cause lpbk Loopback Operated: A loopback test is active on the local port. Entities Affected OTN OTU interfaces (see Table 2-116). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-117). SONET/SDH interfaces (see Table 2-118). Not alarmed. (Default severity should not be changed.) No (false). This condition clears when the loopback is released. For information, see the BTI7800 Series Software Configuration Guide. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC 12x SFP+ BIC Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> 2-72 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

89 MemHighUsage Table Alarm details Parameter Code /Cause memhighusage Memory High Usage. Entities Affected Management and traffic modules (see Table 2-120). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Major. No (false). This alarm indicates that memory usage on the module has exceeded 90%. For information about clearing this alarm, contact your next level of support. Table Management and traffic modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS4 Product Release STANDARD 2-73

90 ModTempHighTh Table Alarm details Parameter Code modtemphighth Module Temperature Above High Threshold: The temperature of the MSA transceiver is above the high-temperature threshold. For information, see Temperature thresholds - MSA transceivers. Entities Affected OTN OTU interfaces (see Table 2-122). Possible Causes The ambient temperature is above the normal operating range of the chassis. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The output power of the MSA transceiver is excessive. Major. No (false). See Clearing a ModTempHighTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On 2-74 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

91 Clearing a ModTempHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Optionally retrieve statistics for the OTU4 interface to view the value of the Module temperature parameter: show statistics current otu4:identifier Check for and resolve any of the following problems: Either a cooling module is not present in the chassis or is present but is operationally down or administratively disabled. A FanSpeedLowTh alarm has been raised against a cooling module. An EnvTempHighTh alarm has been raised against the UFM. The ambient temperature is higher than the specified operating range for the chassis. For information, see the BTI7800 Series Hardware Overview and Installation Guide. Check for alarms on the interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-75

92 ModTempLowTh Table Alarm details Parameter Code modtemplowth Module Temperature Below Low Threshold: The temperature of the MSA transceiver is below low-temperature threshold. For information, see Temperature thresholds - MSA transceivers. Entities Affected OTN OTU interfaces (see Table 2-124). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The ambient temperature is lower than the normal operating range of the chassis. Major. No (false). See Clearing a ModTempLowTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On Clearing a ModTempLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Optionally retrieve statistics for the OTU4 interface to view the value of the Module temperature parameter: show statistics current otu4:identifier Retrieve environment information to view data on equipment temperature, and ensure that the ambient temperature is within the specified range for chassis operation. For information, see the BTI7800 Series Hardware Overview and Installation Guide. show environment Check for alarms on the interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

93 ModTempShutdown Table Alarm details Parameter Code modtempshutdown Module Temperature Shutdown: The temperature of the MSA transceiver has exceeded the high-temperature-shutdown threshold, causing the transmit laser to shut down. For information, see Temperature thresholds - MSA transceivers. Entities Affected OTN OTU interfaces (see Table on page 2-74). Possible Causes Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The ambient temperature is excessively higher than the normal operating range of the MSA transceiver. Critical. Yes (true). See Clearing ModTempShutdown alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On Product Release STANDARD 2-77

94 Clearing ModTempShutdown alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing a traffic module. Step 1 Step 2 Step 3 Step 4 Check for and resolve any of the following problems: Either a cooling module is not present in the chassis or is present but is operationally down or administratively disabled. A FanSpeedLowTh has been raised against a cooling module. The ambient temperature is higher than the specified operating range for the chassis. For information, see the BTI7800 Series Hardware Overview and Installation Guide. Check for alarms on the OTU4 interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, go to Step 3. Replace the UFM4. Check for alarms on the interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

95 MS-AIS Table Condition details Parameter Code /Cause ms-ais Multiplex Section Alarm Indication Signal, SDH: The local port has received an MS- AIS signal from the NE at the far end of the fiber, indicating that no SDH signal is being transmitted upstream of (and toward) the local NE. (See also Maintenance signaling.) Entities Affected SDH (STM64, WAN PHY STM64) interfaces (see Table 2-128). Default Severity Not alarmed. Service Affecting Yes (true). Condition Clearing See Clearing an MS-AIS condition. Related Fault Hierarchy See STM64, WAN PHY over STM64 interface fault hierarchy. Table SDH (STM64, WAN PHY STM64) interfaces stm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanstm64:<chassis>/<slot>/<subslot>/<port> Clearing an MS-AIS condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms on the upstream NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-79

96 MS-RDI Table Alarm details Parameter Code /Cause ms-rdi Multiplex Section Remote Defect Indication, SDH: The local interface has received an MS-RDI signal from the NE at the far end of the fiber, indicating that no SDH signal is being transmitted downstream of (and away from) the local NE. (See also Maintenance signaling.) Entities Affected SDH (STM64, WAN PHY STM64) interfaces (see Table 2-130). Default Severity Not alarmed. Service Affecting No (false). Alarm Clearing See Clearing an MS-RDI condition. Related Fault Hierarchy See STM64, WAN PHY over STM64 interface fault hierarchy. Table SDH (STM64, WAN PHY STM64) interfaces stm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanstm64:<chassis>/<slot>/<subslot>/<port> Clearing an MS-RDI condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms on the downstream NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

97 NonCoLocatedController Table Alarm details Parameter Code /Cause noncolocatedcontroller Entities Affected Equipment (see Table 2-132). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Controllers are in Different Chassis: The active CMMs in a multi-chassis configuration are not located in the same chassis. This alarm is supported on the BTI7814 and BTI7802 chassis only. Critical. Yes (true). See NonCoLocatedController. Table Equipment Equipment Indicator Status chassis:<1 2> BTI7814 or BTI7802 See equipment specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing a NonCoLocatedController alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve information for the hub and satellite chassis: show system chassis Ensure that multi-chassis system is correctly configured. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the chassis. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-81

98 ObrHt Table Alarm details Parameter Code obrht Optical Backreflection High Threshold Exceeded: The optical backreflection has exceeded the high threshold. The default administrative status of this alarm is disabled. Entities Affected Terminal amplifier Optical Supervisory Channels (see Table 2-134). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The fiber connection is poor. Minor. Yes (true). See Clearing an ObrHt alarm. See Terminal amplifier port fault hierarchy. Table Terminal amplifier Optical Supervisory Channels (OSCs) osc:<chassis>/<slot>/1/<portnum>.<oscnum> AMP1 Clearing an ObrHt alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Retrieve statistics for the entity to view the value of the Optical back reflected power counter: show statistics current name:identifier Retrieve statistics information from the running configuration file to view the threshold profile for the OSC: show running-config statistics Example bti7800# show running-config statistics threshold profile statistics threshold profile obrdis entitytype osc statistic opt-back-ref-ratio alarmhigh untimed enabled 2-82 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

99 dec64raisevalue dec64clearvalue -28.0! Step 3 Step 4 Step 5 Step 6 Ensure that the span fiber at the Line output port is intact, thoroughly clean, and correctly connected. Ensure that the fiber connectors are compatible. Ensure that any downstream fiber connections are thoroughly cleaned and correctly connected. Check for alarms on the OSC. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-83

100 OchAis Table Condition details Parameter Code ochais Alarm Indication Signal (AIS), OCH: The local NE has received an OCH-AIS signal from the far-end NE, indicating that no signal is being transmitted upstream of (and toward) the local NE. Entities Affected DOL optical channels (see Table 2-136). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. Yes (true). See Clearing an OchAis condition. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where n depends on the module and channel is an alphanumeric string. ROADM2 Clearing an OchAis condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Check for and clear all alarms upstream of the local NE. Check for excessive loss on the receive span fiber, and, if required, ensure that all upstream fibers are thoroughly cleaned and correctly connected. Ensure that all upstream fibers are thoroughly clean and correctly connected. Check for conditions on the DOL optical channel. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

101 OchOci Table Alarm details Parameter Code ochoci Open Connection Indication (OCI), OCH: The optical channel has received an OCH OCI signal from the NE at the far end of the fiber, indicating that there is a missing optical cross-connect on an upstream node. Entities Affected DOL optical channels (see Table 2-138). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Critical. Yes (true). See Clearing an OchOci condition. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. ROADM2 Clearing an OchOci condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 If required, retrieve cross-connect information for the upstream node: show dol och-xcon Do one of the following, referring to the BTI7800 Series Software Configuration Guide for information: Provision the missing cross-connect on the upstream node. Delete the cross-connect provisioned on the local DOL OCH. Check for conditions on the local DOL OCH. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-85

102 OchUeq Table Alarm details Parameter Code ochueq /Cause OCH Unequipped: The downstream optical channel is not provisioned. Entities Affected DOL optical channels (see Table 2-140). Default Severity Critical. Service Affecting Yes (true). Alarm Clearing See Clearing an OchUeq alarm. Related Fault Hierarchy See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. ROADM2 Clearing an OchUeq alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Provision the DOL OCH on the downstream node. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the local DOL OCH. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

103 OCI Table Alarm details Parameter Code /Cause oci Open Connection Indication, ODU: The local interface has received an ODU-OCI signal from the far-end NE, indicating that an optical cross-connect is not present on an upstream node. Entities Affected OTN ODU interfaces (see Table 2-142). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Critical. Yes (true). See Clearing an OCI alarm. See OTN interface fault hierarchy. Table OTN ODU interfaces odu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port odu2:<chassis>/<slot>/<subslot>/<port.subinterface> odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Clearing an OCI alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Provision the missing cross-connect. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-87

104 ODU-AIS Table Condition details Parameter Code /Cause odu-ais ODU Alarm Indication Signal: The local interface has received an ODU-AIS signal from the NE at the far end of the fiber, indicating that no OTN OTU or OTN ODU signal is being transmitted upstream of (and toward) the local NE. (See also Maintenance signaling.) Entities Affected OTN OTU interfaces (see Table 2-144). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy OTN ODU interfaces (see Table 2-145). Not alarmed. Yes (true). See Clearing an ODU-AIS condition. See OTN interface fault hierarchy. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Table OTN ODU interfaces odu4:<chassis>/<slot>/<subslot>/<port> UFM4 odu4:<chassis>/<slot>/<subslot>/<port> odu2:<chassis>/<slot>/<subslot>/<port.subinterface> odu2:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC 12x SFP+ BIC 2-88 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

105 Clearing an ODU-AIS condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms upstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-89

106 OmsAis Table Condition details Parameter Code OmsAis Alarm Indication Signal, OMS: The local NE has received an OMS-AIS signal from the far-end NE, indicating that no signal is being transmitted upstream of (and toward) the local NE. Entities Affected DOL optical multiplex sections (see Table 2-147). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. Yes (true). Clearing an OmsAis condition See DOL OMS fault hierarchy. Table DOL optical multiplex sections (OMSs) oms:<chassis>/<slot>/0/l1<> ROADM2 or ILA Fault LED, L1 port On oms:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Fault LED, C<n> port Clearing an OmsAis condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Check for and clear all alarms upstream of the local NE. Ensure that the far-end NE has at least one optical channel provisioned and crossconnected. Check for excessive loss on the receive span fiber, and, if required, ensure that all upstream fibers are intact, thoroughly clean, and correctly connected. Check for conditions on the DOL OMS. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

107 OneCableDisconnected Table Alarm/condition details Parameter Code /Cause onecabledisconnect Entities Affected Equipment (see Table 2-149). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy One Multi-Chassis Cable Disconnected: A cable that connects two CMMs in a multichassis configuration is not connected to a CMM. This alarm is supported on the BTI7814 and BTI7802 chassis only. Major. Yes (true). See Clearing a OneCableDisconnected alarm. Table Equipment Equipment Indicator Status chassis:<1 2> BTI7814 or BTI7802 See equipment specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing a OneCableDisconnected alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Inspect the cable connecting the CMMs, and ensure that it is intact and correctly connected. Check for alarms on the chassis. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-91

108 OprHighTh Table Alarm details Parameter Code oprhighth Optical Power Received Above High Threshold: The optical power received is above the high threshold. Entities Affected OTN OTU interfaces (see Table 2-151). Ethernet interfaces (see Table 2-152). SONET/SDH interfaces (see Table 2-153). Wavelength channels (see Table 2-154). Possible Causes There is inadequate attenuation on the optical connection to signal source. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The output power on the remote optical transmitter is too high. Major. No (false). See Clearing an OprHighTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> 2-92 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

109 Table SONET/SDH interfaces (Continued) wanstm64:<chassis>/<slot>/<subslot>/<port> Table Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing an OprHighTh alarm Step 1 Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Retrieve detailed information for the interface to determine whether the value of the Optical Power Rx counter is within the range indicated by the Optical Power Received Minimum Threshold and Optical Power Received Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Step 4 Step 5 Check for and clear alarms on the far-end optical transmitter. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, go to Step 4. Add an attenuation pad in the optical path. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-93

110 OprLowTh Table Alarm details Parameter Code oprlowth Optical Power Received Below Low Threshold: The optical power received is below the low threshold. Entities Affected OTN OTU interfaces (see Table 2-156). Ethernet interfaces (see Table 2-157). SONET/SDH interfaces (see Table 2-158). Wavelength channels (see Table 2-159). Possible Causes There is excessive attenuation on either the fiber link or the optical connection. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The far-end optical transmitter is faulty. Major. No (false). See Clearing an OprLowTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> 2-94 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

111 Table SONET/SDH interfaces (Continued) wanstm64:<chassis>/<slot>/<subslot>/<port> Table Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing an OprLowTh alarm Step 1 Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Retrieve detailed information for the interface to determine whether the value of the Optical Power Rx counter is within the range indicated by the Optical Power Received Minimum Threshold and Optical Power Received Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Step 4 Step 5 Check for and clear alarms on the far-end optical transmitter. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, go to Step 4. Inspect the fiber at the local port, and ensure that it is intact, thoroughly clean, and correctly connected to the port. Check for alarms on the local interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-95

112 OptHighTh Table Alarm details Parameter Code opthighth Optical Power Transmitted Above High Threshold: The optical power transmitted is above the high threshold. Entities Affected OTN OTU interfaces (see Table 2-161). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-162). SONET/SDH interfaces (see Table 2-163). Wavelength channels (see Table 2-164). The optical transmitter is faulty. Major. No (false). See Clearing an OptHighTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> 2-96 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

113 Table Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing an OptHighTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing equipment. Step 1 Retrieve detailed information for the interface to determine whether the value of the Optical Power Tx counter is within the range indicated by the Optical Power Transmitted Minimum Threshold and Optical Power Transmitted Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Replace either the pluggable transceiver installed in the port or, if the alarm is raised against an interface provisioned on an integrated MSA, the UFM. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-97

114 OptLowTh Table Alarm details Parameter Code optlowth Optical Power Transmitted Below Low Threshold: The optical power transmitted is below the low threshold. Entities Affected OTN OTU interfaces (see Table 2-166). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-167). SONET/SDH interfaces (see Table 2-168). Wavelength channels (see Table 2-169). The transmit laser is failing. Major. No (false). See Clearing an OptLowTh alarm. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC Fault LED, 100G port On 12x SFP+ BIC Fault LED, 10G port Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> 2-98 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

115 Table Wavelength channels channel:<chassis>/<slot>/<subslot>/ <port.channel> 1x CFP BIC 1 Fault LED, 100G port On 1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers. Clearing an OptLowTh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before replacing equipment. Step 1 Retrieve detailed information for the interface to determine whether the value of the Optical Power Tx counter is within the range indicated by the Optical Power Transmitted Minimum Threshold and Optical Power Transmitted Maximum Threshold values. show interface name:identifier detail For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Replace either the pluggable transceiver installed in the port or, if the alarm is raised against an interface provisioned on an integrated MSA, the UFM. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-99

116 OTU-AIS Table Condition details Parameter Code /Cause otu-ais OTU Alarm Indication Signal: The local interface has received an OTU-AIS signal from the NE at the far end of the fiber, indicating that no OTN OTU signal is being transmitted upstream of (and toward) the local NE. This signal is generated by non-bti7800 NEs only. Entities Affected OTN OTU interfaces (see Table 2-171). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Not alarmed. Yes (true). The condition will clear when the fault that resulted in the transmission of the OTU- AIS signal is resolved. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

117 PartitionFault Table Alarm details Parameter Code partitionfault /Cause Disk Partition Fault Detected. Entities Affected Management and traffic modules (see Table 2-173). Default Severity Major. Service Affecting No (false). Alarm Clearing See Clearing a ParitionFault alarm. Related Fault Hierarchy Table Management and traffic modules Modules Indicator Status cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS4 Clearing a ParitionFault alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Important Refer to the BTI7800 Series Software Configuration Guide before rebooting a traffic module. Step 1 Step 2 Perform a warm reboot of the module. Check for alarms on the module. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-101

118 PosRxHigh Table Alarm details Parameter Code /Cause posrxhigh Receive Power Out of Specification, High: The optical power received is above the specified range for operation. Entities Affected DOL optical channels (see Table 2-175). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Minor. Yes (true). See Clearing a PosRxHigh alarm. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where n depends on the module and channel is an alphanumeric string. ROADM2 Clearing a PosRxHigh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve PM statistics for the DOL OCH: show statistics current och:identifier Refer to DOL OCH power alarm thresholds to determine whether the optical power received is higher than the specified range for operation. If the optical power received is too high, add an attenuation pad in the optical path to bring the power down to a level within the specified range. Check for alarms on the DOL OCH. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

119 PosRxLow Table Alarm details Parameter Code posrxlow Receive Power Out of Specification, Low: The optical power received is below the specified range for operation. Entities Affected DOL optical multiplex sections (see Table 2-177). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy DOL optical channels (see Table 2-178). Major. Yes (true). See Clearing a PosRxHigh alarm. See: DOL OMS fault hierarchy DOL OCH fault hierarchy Table DOL optical multiplex sections (OMSs) oms:<chassis>/<slot>/0/l1<> ROADM2 or ILA oms:<chassis>/<slot>/0/c<n> where the range of n depends on the module. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where n depends on the module and channel is an alphanumeric string. ROADM2 Product Release STANDARD 2-103

120 Clearing a PosRxLow alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve statistics for the DOL entity: show statistics current name:identifier Refer to DOL OCH power alarm thresholds or DOL OMS power alarm thresholds to determine whether the optical power received for the entity is lower than the specified range for operation. If the optical power received is too low, do the following to bring the power up to a level within the range, retrieving statistics for the entity after each task: Clean the fibers connected to the affected ports. Change the patch cord fiber. Check the source of the entity to determine whether it is transmitting at an adequate level. Check the fibers and any attenuators in the path to ensure that no unintentional attenuation has been added to the path. Check for alarms on the DOL entity. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

121 PosTxHigh Table Alarm details Parameter Code /Cause postxhigh Transmit Power Out of Specification, High: The optical power transmitted is higher than the specified range for operation. Entities Affected DOL optical channels (see Table on page 2-106). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Critical. Yes (true). See Clearing a PosTxHigh alarm. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where n depends on the module and channel is an alphanumeric string. ROADM2 Clearing a PosTxHigh alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve statistics for the DOLOCH: show statistics current och:identifier Refer to DOL OCH power alarm thresholds to determine whether the optical power transmitted is out of the specified range for operation. If the optical power transmitted is too high, add an attenuation pad in the optical path to bring the power to a level within the range. Check for alarms on the DOL OCH. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-105

122 PosTxLow Table Alarm details Parameter Code /Cause postxlow Transmit Power Out of Specification, Low: The optical power transmitted is below the specified range for operation. Entities Affected DOL optical channels (see Table 2-182). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Critical. Yes (true). See Clearing a PosTxLow alarm. See DOL OCH fault hierarchy. Table DOL optical channels (OCHs) och:<chassis>/<slot>/0/l1/<channel> where channel is an alphanumeric string. och:<chassis>/<slot>/0/c<n>/<channel> where n depends on the module and channel is an alphanumeric string. ROADM2 Clearing a PosTxLow alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve statistics for the DOL OCH: show statistics current och:identifier Refer to DOL OCH power alarm thresholds to determine whether the optical power transmitted is lower than the range specified for operation. If the optical power transmitted is too low, ensure that the upstream fiber connections are intact, thoroughly clean, and correctly connected. Check for alarms on the DOL OCH. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

123 PowerAbsent Table Alarm details Parameter Code powerabsent No Power Available: No power is available to the power entry module (PEM). Caution Continued operation might cause equipment damage. Entities Affected Equipment (see Table 2-184). Possible Causes AC PEM: The input AC voltage is either less than 90 Vac or greater than 255 Vac, and the output DC voltage is either less than 40 Vdc or greater than 60 Vdc. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy DC PEM: The input and output DC voltages are either less than 40 Vdc or greater than 60 Vdc. Critical. Yes (true). See Clearing a PowerAbsent alarm. Table Equipment Equipment Indicator Status pem:<chassis>/<slot> PEM See the PEM specifications in the BTI7800 Series Hardware Overview and Installation Guide. Clearing a PowerAbsent alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Check the power distribution to the chassis: Ensure that each PEM is properly seated and the power connection to it is secure. Ensure that each external source DC power circuit breaker is on. Ensure that each the external power wires are delivering power correctly. Step 2 Check for alarms on the PEM. If the alarm clears, you have successfully completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-107

124 PRBS Table Condition details Parameter Code /Cause prbs PRBS Test Activated: A PRBS test is active on the local port. Entities Affected OTN OTU interfaces (see Table 2-186). Default Severity Service Affecting Condition Clearing Related Fault Hierarchy Ethernet interfaces (see Table 2-187). SONET/SDH interfaces (see Table 2-188). Not alarmed. (Default severity should not be changed.) No (false). This condition clears when PRBS-signal generation is turned off. For information, see the BTI7800 Series Software Configuration Guide. See Common fault hierarchy - OTN and CBR ports. Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC 12x SFP+ BIC Table SONET/SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

125 PyldMism Table Alarm details Parameter Code pyldmism Payload Mismatch: The payload type in the received signal is not the expected payload type. Entities Affected OTN ODU interfaces (see Table 2-190). Possible Cause Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The cross-connect configuration at the far-end NE does not match the crossconnect configuration at the local NE. Critical. Yes (true). See Clearing a PyldMism alarm. See OTN interface fault hierarchy. Table OTN ODU interfaces odu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port odu2:<chassis>/<slot>/<subslot>/<port.subinterface> odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Product Release STANDARD 2-109

126 Clearing a PyldMism alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Step 4 Retrieve interface data to compare the values of the Payload Type and Received Payload Type parameters. show interface name:identifier Retrieve cross-connect information for the local NE and the far-end NE to determine at which end the cross-connect is incorrectly provisioned. show cross-connect Delete the correct cross-connect, and reprovision it to resolve the mismatch. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the local interface. If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

127 RDI-L Table Condition details Parameter Code /Cause rdi-l Remote Defect Indication Line: The local interface has received an RDI-L signal from the NE at the far end of the fiber, indicating that no SONET signal is being transmitted downstream of (and away from) the local NE. (See also Maintenance signaling.) Entities Affected SONET (OC192, WAN PHY OC192) interfaces (see Table 2-192). Default Severity Not alarmed. Service Affecting No (false). Condition Clearing See Clearing an RDI-L condition. Related Fault Hierarchy See OC192, WAN PHY over OC192 interface fault hierarchy. Table SONET (OC192, WAN PHY OC192) interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC wanoc192:<chassis>/<slot>/<subslot>/<port> Clearing an RDI-L condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms downstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support. Product Release STANDARD 2-111

128 RF Table Condition details Parameter Code /Cause rf Remote Fault: The local interface has received a remote-fault signal from the NE at the far end of the fiber, indicating that no Ethernet signal is being transmitted downstream of (and away from) the local NE. (See also Maintenance signaling.) Entities Affected Ethernet interfaces (see Table 2-194). Default Severity Not alarmed. Service Affecting No (false). Condition Clearing See Clearing an RF condition. Related Fault Hierarchy See Ethernet interface fault hierarchy. Table Ethernet interfaces 100ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 10ge:<chassis>/<slot>/<subslot>/<port>/ <subport> 1x CFP BIC 12x SFP+ BIC Clearing an RF condition Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Check for and clear all alarms downstream of the local NE. Check for conditions on the local interface. If the condition clears, you have completed this procedure. If the condition does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

129 ScmNmiDown Table Alarm details Parameter Code /Cause scmnmidown System Controller Module (SCM) Interface Down: One of the SCMs in a dual-cmm system cannot connect to the management IP network. Entities Affected Management modules (see Table 2-196). Default Severity Service Affecting Major. Yes (true). Alarm Clearing See Clearing an ScmNmiDown alarm. Related Fault Hierarchy Table Management modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series module and BIC LED behavior. Clearing an ScmNmiDown alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Provision a static management IP address on the affected CMM. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the CMM. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-113

130 scmnonmconn Table Alarm details Parameter Code /Cause scmnonmconn No Network Management Connectivity on System Controller Module (SCM): In a dual-cmm system, neither SCM can connect to the management IP network. In a single-cmm system, the SCM cannot connect to the management IP network. Entities Affected Management modules (see Table 2-198). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Critical. Yes (true). See Clearing an scmnonmconn alarm. Table Management modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series module and BIC LED behavior. Clearing an scmnonmconn alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Provision a static management IP address on each affected CMM. For information, see the BTI7800 Series Software Configuration Guide. Check for alarms on the CMM. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

131 SD Table Alarm details Parameter Code sd Signal Degrade: The local port is in a signal-degrade state because of a number of errors in the received signal. Entities Affected OTN OTU interfaces (see Table 2-200). SONET/SDH interfaces (see Table 2-201). Possible Causes Either the fiber link or the optical connection is degraded. Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Excessive signal attenuation has resulted in a high signal-to-noise ratio. Minor. No (false). See Clearing an SD alarm. See: OTN interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table SONET /SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-115

132 Clearing an SD alarm Step 1 Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Reprieve statistics for the interface, and ensure that the optical power received and the optical signal-to-noise ratio are within specification: show statistics current name:identifier For detailed transceiver specifications, see Appendix B, BTI7800 Series transceivers. Step 2 Step 3 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and correctly connected to the port. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

133 TIM Table Alarm details Parameter Code tim Trace Identifier Mismatch: The received trace identifier is different from the expected trace identifier. Entities Affected OTN OTU interfaces (see Table 2-203). SONET/SDH interfaces (see Table 2-204). Possible Causes The optical fiber link is from the wrong source (misconnected). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy The expected trace identifier configured on the local interface is incorrect. The trace identifier configured on the remote interface is incorrect. Critical. Yes (true). See Clearing a TIM alarm. See: OTN interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy Table OTN OTU interfaces otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port Table SONET /SDH interfaces oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On wanoc192:<chassis>/<slot>/<subslot>/<port> stm64:<chassis>/<slot>/<subslot>/<port> wanstm64:<chassis>/<slot>/<subslot>/<port> Product Release STANDARD 2-117

134 Clearing a TIM alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Step 2 Step 3 Retrieve detailed interface data to view the values of the following attribute pairs: OTU interface: Trace Message Expected/Trace Message Received SONET/SDH interface: Expected Section Trace Message/Received Section Trace Message show interface name:identifier detail Based on the trace-message data, determine whether any of the following problems exist, and then resolve them: The optical fiber link is from the wrong source (misconnected). The expected trace identifier configured on the local interface is incorrect. The trace identifier configured on the remote interface is incorrect. Check for alarms on the interface. If the alarm clears, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

135 TlossRxHt Table Alarm details Parameter Code /Cause tlossrxht Loss Above High Threshold, Receive: The measured optical power loss in the receive fiber is above the high threshold. Entities Affected Terminal amplifier line ports (see Table 2-206). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Minor. Yes (true). See Clearing a TlossRxHt alarm. See Terminal amplifier port fault hierarchy. Table Terminal amplifier line ports line:<chassis>/<slot>/1/<portnum> AMP1 Fault LED, Line port On Clearing a TlossRxHt alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Optical power loss in recv. direction counter: show statistics current line:identifier For detailed AMP1 specifications, see the BTI7800 Series Hardware Overview and Installation Guide. Step 2 Step 3 Check for the following problems, and resolve them if they exist: There is excessive loss on the receive span fiber. The span length is excessive, resulting in loss that cannot be supported. There is excessive loss on upstream patch fibers. Check for alarms on the terminal amplifier line port: If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support. Product Release STANDARD 2-119

136 TlossRxLt Table Alarm/condition details Parameter Code /Cause tlossrxlt Loss Below Low Threshold, Receive: The measured optical power loss in the received fiber is below the low threshold. Entities Affected Terminal amplifier line ports (see Table 2-208). Default Severity Service Affecting Alarm Clearing Related Fault Hierarchy Minor. Yes (true). See Clearing a TlossRxLt alarm. See Terminal amplifier port fault hierarchy. Table Terminal amplifier line ports line:<chassis>/<slot>/1/<portnum> AMP1 Fault LED, Line port On Clearing a TlossRxLt alarm Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Optical power loss in recv. direction counter: show statistics current line:identifier For detailed AMP1 specifications, see the BTI7800 Series Hardware Overview and Installation Guide. Step 2 Step 3 Check the upstream fiber connections, and ensure that the fiber is intact, thoroughly clean, and properly connected. Check for alarms on the terminal amplifier line port: If the alarm has cleared, you have completed this procedure. If the alarm does not clear, contact your next level of support BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

137 UPGRD Table Alarm details Parameter Code upgrd /Cause Upgrade in Progress: A system software upgrade is in progress. Entities Affected Management and traffic modules (see Table 2-210). Default Severity Minor. Service Affecting Yes (true). Alarm Clearing This alarms clear when the system software upgrade is completed. Related Fault Hierarchy Table Management and traffic modules cmm:<chassis>/<slot> CMM See Appendix C, BTI7800 Series ufm:<chassis>/<slot> UFM module and BIC LED behavior. roadm:<chassis>/<slot> ROADM2 ila:<chassis>/<slot> ILA amp:<chassis>/<slot> AMP1 wps:<chassis>/<slot> WPS4 Product Release STANDARD 2-121

138 2-122 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

139 C H A P T E R Fault masking Fault masking occurs when a service-affecting alarm or condition raised against a monitored entity suppresses the reporting of other alarms or conditions that are raised against the same entity. A fault that masks another fault is in a higher position in the fault hierarchy for a monitored entity and indicates either a higher priority fault or a fault that more accurately identifies the source of a problem. This means that when a fault that masks other faults is cleared, each masked fault will be reported if it was not cleared by the resolution of the masking fault. The following sections list faults common to specific monitored entities and include faulthierarchy flow charts that illustrate the masking relationships among those faults. Equipment fault hierarchy Environment fault hierarchy Common fault hierarchy - OTN and CBR ports OTN interface fault hierarchy Ethernet interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy DOL port fault hierarchy DOL OSC fault hierarchy DOL OMS fault hierarchy DOL OCH fault hierarchy Terminal amplifier port fault hierarchy Product Release STANDARD 3-1

140 Fault masking Equipment fault hierarchy Table 3-1 Equipment fault hierarchy Alarms/Conditions EqptMiss EqptMism EqptComm EqptFail EqptDgrd Fault Hierarchy 3-2 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

141 Fault masking Environment fault hierarchy Table 3-2 Environment fault hierarchy Alarms/Conditions Equipment fault hierarchy EnvCurrentHighTh EnvCurrentLowTh EnvTempHighTh EnvTempLowTh EnvVoltHighTh EnvVoltLowTh Fault Hierarchy Product Release STANDARD 3-3

142 Fault masking Common fault hierarchy - OTN and CBR ports Table 3-3 Common fault hierarchy - OTN and CBR ports Alarms/Conditions Equipment fault hierarchy LOS LPBK PRBS LaserTempHighTh LaserTempLowTh LaserFail ModTempShutdown OptHighTh OprLowTh LOF Protocol Faults: OTN interface fault hierarchy Ethernet interface fault hierarchy OC192, WAN PHY over OC192 interface fault hierarchy STM64, WAN PHY over STM64 interface fault hierarchy OptHighTh OptLowTh ModTempHighTh ModTempLowTh Fault Hierarchy 3-4 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

143 Fault masking OTN interface fault hierarchy In the OTN fault hierarchy, a service-affecting fault raised against an OTN OTU interface will mask all faults raised against each OTU ODU interface it contains. Table 3-4 OTN interface fault hierarchy Alarms/Conditions Equipment fault hierarchy LOS LOF SD LOM BDI TIM ODU-AIS LCK OCI PyldMism Fault Hierarchy Product Release STANDARD 3-5

144 Fault masking Ethernet interface fault hierarchy Table 3-5 Ethernet interface fault summary Alarms/Conditions Equipment fault hierarchy LOS LoSync HighBer LF RF Fault Hierarchy 3-6 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

145 Fault masking OC192, WAN PHY over OC192 interface fault hierarchy Table 3-6 OC192, WAN PHY over OC192 interface fault summary Alarms/Conditions Fault Hierarchy Equipment fault hierarchy LOS LOF SD TIM AIS L RDI-L Product Release STANDARD 3-7

146 Fault masking STM64, WAN PHY over STM64 interface fault hierarchy Table 3-7 STM64, WAN PHY over STM64 interface fault summary Alarms/Conditions Fault Hierarchy Equipment fault hierarchy LOS LOF SD TIM MS-AIS MS-RDI 3-8 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

147 Fault masking DOL port fault hierarchy Table 3-8 DOL port fault summary Alarms/Conditions Equipment fault hierarchy APSD FECI FEIM LoSpecRx APR LoLightRx Fault Hierarchy Product Release STANDARD 3-9

148 Fault masking DOL OSC fault hierarchy Table 3-9 DOL OSC fault summary Alarms/Condition Equipment fault hierarchy ContComS LoLightRx Fault Hierarchy 3-10 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

149 Fault masking DOL OMS fault hierarchy Table 3-10 DOL OMS alarms summary Alarms/Conditions Equipment fault hierarchy OmsAis LoLightRx PosRxLow Fault Hierarchy Product Release STANDARD 3-11

150 Fault masking DOL OCH fault hierarchy Table 3-11 DOL OCH fault summary Alarms/Conditions Equipment fault hierarchy OchOci OchUeq PosTxHigh LoLightTx DOL OMS fault hierarchy PosTxLow PosRxHigh OchAis LoLightRx PosRxLow Fault Hierarchy 3-12 BTI7800 Series Alarm and Troubleshooting Guide Document Version 01

151 Fault masking Terminal amplifier port fault hierarchy Table 3-12 Terminal amplifier port fault summary Alarms/Conditions Equipment fault hierarchy APSD ContComS FECI FEIM ObrHt TlossRxHt TlossRxLt APR LoLightRx Fault Hierarchy Product Release STANDARD 3-13