BTI7800 Series Alarm and Troubleshooting Guide BTI7800 Series Alarm and Troubleshooting Guide –...

BTI7800 Series Alarm and Troubleshooting Guide

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, CA 94089 USA

tel: 408-745-2000

www.juniper.net

Part Number:Document Version:Published:Type:

BT8A78PD0021 01 November 2016 STANDARD

product release 2.1.1

Copyright © 2016 Juniper Networks, Inc. ALL RIGHTS RESERVED.

Contents

Preface viii

1.0 Fault monitoring on the BTI7800 1-1 Fault reporting .................................................................................................................................................................................... 1-2Maintenance signaling ....................................................................................................................................................................... 1-4

2.0 Alarms and conditions 2-1 AirFilterAbsence ................................................................................................................................................................................ 2-8

2.1.1 Clearing an AirFilterAbsence alarm .................................................................................................................................... 2-8AIS–L ................................................................................................................................................................................................. 2-9

2.2.1 Clearing an AIS-L condition ................................................................................................................................................ 2-9APR ................................................................................................................................................................................................. 2-10

2.3.1 Clearing an APR alarm (PRE port) ................................................................................................................................... 2-102.3.2 Clearing an APR alarm (terminal amplifier port) ............................................................................................................... 2-11

APSD ............................................................................................................................................................................................... 2-122.4.1 Clearing an APSD alarm (DOL port) ................................................................................................................................ 2-132.4.2 Clearing an APSD alarm (terminal amplifier line port) ...................................................................................................... 2-13

BDI ................................................................................................................................................................................................... 2-142.5.1 Clearing a BDI condition ................................................................................................................................................... 2-14

ContComS ....................................................................................................................................................................................... 2-152.6.1 Clearing a ContComS alarm ............................................................................................................................................. 2-16

DiskHighUsage ................................................................................................................................................................................ 2-17EnvCurrentHighTh ........................................................................................................................................................................... 2-18

2.8.1 Clearing an EnvCurrentHighTh alarm .............................................................................................................................. 2-18EnvCurrentLowTh ............................................................................................................................................................................ 2-19

2.9.1 Clearing an EnvCurrentLowTh alarm ............................................................................................................................... 2-19EnvTempHighTh .............................................................................................................................................................................. 2-20

Product Release 2.1.1 STANDARD iii

2.10.1 Clearing an EnvTempHighTh alarm ............................................................................................................................... 2-21EnvTempLowTh ............................................................................................................................................................................... 2-22

2.11.1 Clearing an EnvTempLowTh condition ........................................................................................................................... 2-23EnvVoltHighTh ................................................................................................................................................................................. 2-24

2.12.1 Clearing an EnvVoltHighTh alarm .................................................................................................................................. 2-25EnvVoltLowTh .................................................................................................................................................................................. 2-26

2.13.1 Clearing an EnvVoltLowTh alarm ................................................................................................................................... 2-27EqptComm ....................................................................................................................................................................................... 2-28

2.14.1 Clearing an EqptComm alarm ........................................................................................................................................ 2-28EqptDgrd .......................................................................................................................................................................................... 2-29

2.15.1 Clearing an EqptDgrd alarm ........................................................................................................................................... 2-29EqptFail ............................................................................................................................................................................................ 2-30

2.16.1 Clearing an EqptFail alarm ............................................................................................................................................. 2-31EqptMism ......................................................................................................................................................................................... 2-32

2.17.1 Clearing an EqptMism alarm .......................................................................................................................................... 2-33EqptMiss .......................................................................................................................................................................................... 2-34

2.18.1 Clearing an EqptMiss alarm ........................................................................................................................................... 2-35FanSpeedLowTh ............................................................................................................................................................................. 2-36

2.19.1 Clearing a FanSpeedLowTh alarm ................................................................................................................................. 2-36FECI ................................................................................................................................................................................................. 2-38

2.20.1 Clearing a FECI alarm (DOL port) .................................................................................................................................. 2-392.20.2 Clearing a FECI alarm (terminal amplifier OSC) ............................................................................................................ 2-39

FEIM ................................................................................................................................................................................................ 2-402.21.1 Clearing a FEIM alarm (DOL port) .................................................................................................................................. 2-412.21.2 Clearing a FEIM alarm (terminal amplifier OSC) ............................................................................................................ 2-41

FirmUpgrdInProg ............................................................................................................................................................................. 2-42FirmUpgrdFail .................................................................................................................................................................................. 2-43

2.23.1 Clearing a FirmUpgrdFail alarm ..................................................................................................................................... 2-43FirmUpgrdReqd ............................................................................................................................................................................... 2-44Forced .............................................................................................................................................................................................. 2-45HighBer ............................................................................................................................................................................................ 2-46

2.26.1 Clearing a HighBer alarm ............................................................................................................................................... 2-47InvUnknown ..................................................................................................................................................................................... 2-48

2.27.1 Clearing an InvUnknown alarm ...................................................................................................................................... 2-48LaserFail .......................................................................................................................................................................................... 2-49

2.28.1 Clearing a LaserFail alarm ............................................................................................................................................. 2-50LaserTempHighTh ........................................................................................................................................................................... 2-51

2.29.1 Clearing a LaserTempHighTh alarm .............................................................................................................................. 2-52LaserTempLowTh ............................................................................................................................................................................ 2-53

2.30.1 Clearing a LaserTempLowTh alarm ............................................................................................................................... 2-54LCK .................................................................................................................................................................................................. 2-55

2.31.1 Clearing an LCK alarm ................................................................................................................................................... 2-56LF ..................................................................................................................................................................................................... 2-57

2.32.1 Clearing an LF condition ................................................................................................................................................ 2-57Lockout ............................................................................................................................................................................................ 2-58LOF .................................................................................................................................................................................................. 2-59

2.34.1 Clearing an LOF alarm ................................................................................................................................................... 2-60

iv BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Contents

LoLightRx ......................................................................................................................................................................................... 2-612.35.1 Clearing a LoLightRx alarm (DOL entity) ........................................................................................................................ 2-632.35.2 Clearing a LoLightRx alarm (wavelength protection port) .............................................................................................. 2-642.35.3 Clearing a LoLightRx alarm (terminal amplifier port) ...................................................................................................... 2-64

LoLightTx ......................................................................................................................................................................................... 2-652.36.1 Clearing a LoLightTx alarm ............................................................................................................................................ 2-65

LOM ................................................................................................................................................................................................. 2-662.37.1 Clearing an LOM alarm .................................................................................................................................................. 2-66

LOS .................................................................................................................................................................................................. 2-672.38.1 Clearing an LOS alarm ................................................................................................................................................... 2-68

LoSpecRx ........................................................................................................................................................................................ 2-692.39.1 Clearing a LoSpecRx alarm ............................................................................................................................................ 2-69

LoSync ............................................................................................................................................................................................. 2-702.40.1 Clearing a LoSync alarm ................................................................................................................................................ 2-71

LPBK ................................................................................................................................................................................................ 2-72MemHighUsage ............................................................................................................................................................................... 2-73ModTempHighTh ............................................................................................................................................................................. 2-74

2.43.1 Clearing a ModTempHighTh alarm ................................................................................................................................ 2-75ModTempLowTh .............................................................................................................................................................................. 2-76

2.44.1 Clearing a ModTempLowTh alarm ................................................................................................................................. 2-76ModTempShutdown ......................................................................................................................................................................... 2-77

2.45.1 Clearing ModTempShutdown alarm ............................................................................................................................... 2-78MS-AIS ............................................................................................................................................................................................ 2-79

2.46.1 Clearing an MS-AIS condition ........................................................................................................................................ 2-79MS-RDI ............................................................................................................................................................................................ 2-80

2.47.1 Clearing an MS-RDI condition ........................................................................................................................................ 2-80NonCoLocatedController ................................................................................................................................................................. 2-81

2.48.1 Clearing a NonCoLocatedController alarm ..................................................................................................................... 2-81ObrHt ............................................................................................................................................................................................... 2-82

2.49.1 Clearing an ObrHt alarm ................................................................................................................................................. 2-82OchAis ............................................................................................................................................................................................. 2-84

2.50.1 Clearing an OchAis condition ......................................................................................................................................... 2-84OchOci ............................................................................................................................................................................................. 2-85

2.51.1 Clearing an OchOci condition ......................................................................................................................................... 2-85OchUeq ............................................................................................................................................................................................ 2-86

2.52.1 Clearing an OchUeq alarm ............................................................................................................................................. 2-86OCI .................................................................................................................................................................................................. 2-87

2.53.1 Clearing an OCI alarm .................................................................................................................................................... 2-87ODU-AIS .......................................................................................................................................................................................... 2-88

2.54.1 Clearing an ODU-AIS condition ...................................................................................................................................... 2-89OmsAis ............................................................................................................................................................................................ 2-90

2.55.1 Clearing an OmsAis condition ........................................................................................................................................ 2-90OneCableDisconnected ................................................................................................................................................................... 2-91

2.56.1 Clearing a OneCableDisconnected alarm ...................................................................................................................... 2-91OprHighTh ....................................................................................................................................................................................... 2-92

2.57.1 Clearing an OprHighTh alarm ......................................................................................................................................... 2-93OprLowTh ........................................................................................................................................................................................ 2-94

Product Release 2.1.1 STANDARD v

Contents

2.58.1 Clearing an OprLowTh alarm ......................................................................................................................................... 2-95OptHighTh ....................................................................................................................................................................................... 2-96

2.59.1 Clearing an OptHighTh alarm ......................................................................................................................................... 2-97OptLowTh ........................................................................................................................................................................................ 2-98

2.60.1 Clearing an OptLowTh alarm .......................................................................................................................................... 2-99OTU-AIS ........................................................................................................................................................................................ 2-100PartitionFault .................................................................................................................................................................................. 2-101

2.62.1 Clearing a ParitionFault alarm ...................................................................................................................................... 2-101PosRxHigh ..................................................................................................................................................................................... 2-102

2.63.1 Clearing a PosRxHigh alarm ........................................................................................................................................ 2-102PosRxLow ...................................................................................................................................................................................... 2-103

2.64.1 Clearing a PosRxLow alarm ......................................................................................................................................... 2-104PosTxHigh ..................................................................................................................................................................................... 2-105

2.65.1 Clearing a PosTxHigh alarm ......................................................................................................................................... 2-105PosTxLow ...................................................................................................................................................................................... 2-106

2.66.1 Clearing a PosTxLow alarm ......................................................................................................................................... 2-106PowerAbsent ................................................................................................................................................................................. 2-107

2.67.1 Clearing a PowerAbsent alarm ..................................................................................................................................... 2-107PRBS ............................................................................................................................................................................................. 2-108PyldMism ....................................................................................................................................................................................... 2-109

2.69.1 Clearing a PyldMism alarm ........................................................................................................................................... 2-110RDI-L ............................................................................................................................................................................................. 2-111

2.70.1 Clearing an RDI-L condition ......................................................................................................................................... 2-111RF .................................................................................................................................................................................................. 2-112

2.71.1 Clearing an RF condition .............................................................................................................................................. 2-112ScmNmiDown ................................................................................................................................................................................ 2-113

2.72.1 Clearing an ScmNmiDown alarm ................................................................................................................................ 2-113scmNoNmConn ............................................................................................................................................................................. 2-114

2.73.1 Clearing an scmNoNmConn alarm ............................................................................................................................... 2-114SD .................................................................................................................................................................................................. 2-115

2.74.1 Clearing an SD alarm ................................................................................................................................................... 2-116TIM ................................................................................................................................................................................................. 2-117

2.75.1 Clearing a TIM alarm .................................................................................................................................................... 2-118TlossRxHt ...................................................................................................................................................................................... 2-119

2.76.1 Clearing a TlossRxHt alarm .......................................................................................................................................... 2-119TlossRxLt ....................................................................................................................................................................................... 2-120

2.77.1 Clearing a TlossRxLt alarm .......................................................................................................................................... 2-120UPGRD .......................................................................................................................................................................................... 2-121

3.0 Fault masking 3-1 Equipment fault hierarchy .................................................................................................................................................................. 3-2Environment fault hierarchy ............................................................................................................................................................... 3-3Common fault hierarchy - OTN and CBR ports ................................................................................................................................. 3-4OTN interface fault hierarchy ............................................................................................................................................................. 3-5Ethernet interface fault hierarchy ....................................................................................................................................................... 3-6OC192, WAN PHY over OC192 interface fault hierarchy .................................................................................................................. 3-7STM64, WAN PHY over STM64 interface fault hierarchy ................................................................................................................. 3-8

vi BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Contents

DOL port fault hierarchy ..................................................................................................................................................................... 3-9DOL OSC fault hierarchy ................................................................................................................................................................. 3-10DOL OMS fault hierarchy ................................................................................................................................................................. 3-11DOL OCH fault hierarchy ................................................................................................................................................................. 3-12Terminal amplifier port fault hierarchy ............................................................................................................................................. 3-13

4.0 Alarm thresholds 4-1 Environment thresholds ..................................................................................................................................................................... 4-2

4.1.1 Temperature thresholds - equipment and traffic modules .................................................................................................. 4-24.1.2 Temperature thresholds - MSA transceivers ...................................................................................................................... 4-34.1.3 Fan-speed thresholds ......................................................................................................................................................... 4-44.1.4 Output-current thresholds ................................................................................................................................................... 4-44.1.5 Voltage thresholds .............................................................................................................................................................. 4-4

DOL thresholds .................................................................................................................................................................................. 4-64.2.1 DOL OSC power alarm thresholds ..................................................................................................................................... 4-64.2.2 DOL OMS power alarm thresholds ..................................................................................................................................... 4-74.2.3 DOL OCH power alarm thresholds ..................................................................................................................................... 4-84.2.4 DOL port power alarm thresholds ....................................................................................................................................... 4-94.2.5 DOL Rx-loss alarm thresholds .......................................................................................................................................... 4-10

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 2.1.1 STANDARD vii

Contents

Preface

This preface explains who should read this guide, related documentation, documentationconventions, how to obtain documentation, and how to obtain technical support.

Audience

This guide is primarily intended for site planners, planning engineers, and network operationcenter (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 Notes

Obtaining documentation

To obtain the most current version of all Juniper Networks technical documentation, see theproduct documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/.If the information in the latest release notes differs from the information in the documentation,follow the product Release Notes.Juniper Networks Books publishes books by Juniper Networks engineers and subject matterexperts. These books go beyond the technical documentation to explore the nuances of networkarchitecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books.

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical AssistanceCenter (JTAC). If you are a customer with an active J-Care or Partner Support Service supportcontract, or are covered under warranty, and need post-sales technical support, you can accessour 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 http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

• Product warranties - For product warranty information, visit http://www.juniper.net/support/warranty/.

viii BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Preface

http://www.juniper.net/techpubs/


http://www.juniper.net/books

http://www.juniper.net/books

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf

http://www.juniper.net/support/warranty/

http://www.juniper.net/support/warranty/

• JTAC hours of operation - The JTAC centers have resources available 24 hours a day, 7 daysa week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-serviceportal called the Customer Support Center (CSC) that provides you with the following features:• Find CSC offerings: http://www.juniper.net/customers/support/• Search for known bugs: http://www2.juniper.net/kb/• Find product documentation: http://www.juniper.net/techpubs/• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/• Download the latest versions of software and review release notes: http://www.juniper.net/

customers/csc/software/• Search technical bulletins for relevant hardware and software notifications: http://

kb.juniper.net/InfoCenter/• Join and participate in the Juniper Networks Community Forum: http://www.juniper.net/

company/communities/• Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/To verify service entitlement by product serial number, use our Serial Number Entitlement(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

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 http://www.juniper.net/cm/.• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html.

End User License Agreement

The Juniper Networks product that is the subject of this technical documentation consists of (oris intended for use with) Juniper Networks software. Use of such software is subject to the termsand conditions of the End User License Agreement (EULA) posted at http://www.juniper.net/cm/. By downloading, installing or using such software, you agree to the terms and conditions ofthat EULA.

Documentation conventions

Convention DescriptionNote Means reader take note. Notes contain helpful suggestions or background information.

Means reader be careful. Equipment damage or loss of data can result from your actions.

Product Release 2.1.1 STANDARD ix

Preface

http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/


http://kb.juniper.net/

http://www.juniper.net/customers/csc/software/

http://www.juniper.net/customers/csc/software/

http://kb.juniper.net/InfoCenter/

http://kb.juniper.net/InfoCenter/

http://www.juniper.net/company/communities/

http://www.juniper.net/company/communities/

http://www.juniper.net/cm/

https://tools.juniper.net/SerialNumberEntitlementSearch/


http://www.juniper.net/support/requesting-support.html

http://www.juniper.net/support/requesting-support.html



Convention Description

Caution

Warning

Means reader be careful. Harm to yourself or others can result from your actions.

Laser Warning

Invisible laser radiation can be emitted from the aperture ports of amplifier circuit packswhen no fiber cable is connected. Avoid exposure and do not stare into open apertures toavoid permanent eye damage.

x BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Preface

Caution USE OF CONTROLS OR ADJUSTMENTS OR PERFORMANCE OFPROCEDURES OTHER THAN THOSE SPECIFIED IN THIS GUIDE MAYRESULT IN HAZARDOUS RADIATION EXPOSURE.

Product Release 2.1.1 STANDARD xi

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 reproductionin whole or in part is strictly prohibited. Juniper, Juniper Networks, BTI, BTI SYSTEMS, packetVX, proNX, and TheNetwork You Need are trademarks or registered trademarks of Juniper Networks, Inc. and/or its subsidiaries in theU.S. and/or other countries.Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the rightto change, modify, transfer, or otherwise revise this publication without notice.

Copyright © 2003-2016 BTI Systems, Inc. All rights reserved.

xii BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Preface

1.0 Fault monitoring on the BTI7800

Fault monitoring is enabled by default for all managed entities and is conducted at the physicallayer, covering optical signals and channel-specific transceiver faults, and at the protocol layerwith specific fault points defined for all supported protocols. Monitoring is also conducted onsupporting BTI7800 equipment, including the various sensors located throughout the chassis andon the modules.You can enable or disable the reporting of a fault. When reporting is enabled and fault maskingdoes not occur, the fault is reported as either an alarm (alarmed) or a condition (not alarmed). Analarm generates a notification as the fault becomes active. A condition does not generate anotification and is typically used to report lower-severity faults. For more information about faultmasking, 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 theBTI7800 Command Line Reference Guide.This section covers the following topics:• “Fault reporting”• “Maintenance signaling”For detailed information about BTI7800 alarms and conditions, including alarm-clearingprocedures, see Chapter 2, “Alarms and conditions”.

Product Release 2.1.1 STANDARD 1-1

C H A P T E R 1

Fault reporting

When reporting is enabled for a fault that becomes active on a managed entity, the reportingbehavior of that fault depends on the administrative status (enabled or disabled) of the entity, asdescribed in Table 1-1.

Table 1-1 Entity administrative status and fault reporting Status Fault-Reporting BehaviorEnabled 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 conditionsretrieves a list of all active faults (both alarms and conditions), and the command showalarms retrieves a list of all active alarms.

Disabled When a fault with critical, major, or minor severity either becomes active or is cleared, noreporting is provided. Polling results retrieved with either show conditions or showalarms 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 theentity affected, the fault code, the time the fault was reported, the fault severity, the impact onservice, 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 DescriptionCritical A failure that is likely causing serious loss or interruption of traffic.

Major A failure that could potentially lead to loss or interruption of traffic.

Minor A failure that does not significantly affect traffic.

Not alarmed A fault that results in a standing condition, not an alarm.

Not reported A non-alarmed fault that is discovered only when standing conditions are polled.

1-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

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-affectingtrue) or not (service-affecting false). Depending on the entity type, the operational status of theentity is reported as down when a fault is service-affecting.



Maintenance signaling

When normal traffic cannot be transmitted from a port, for example, when a received signal is ina failed state or when a port is administratively disabled and traffic is disrupted, the BTI7800Series will usually forward a maintenance signal from the transmit port to indicate to thedownstream node that a local outage exists. For all interface protocols, the default maintenancesignal (Table 1-3) enables the receiving node to conclude that the link to the adjacent upstreamnode is intact.

Table 1-3 Default maintenance signals - interface protocols Protocol Default Maintenance SignalOTN OTU “ODU-AIS”

OTN ODU “ODU-AIS”

Ethernet “LF”

OC192, WAN PHY over OC192 “AIS–L”

STM64, WAN PHY over STM64 “MS-AIS”



2.0 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)

SONET interfaces Not alarmed Yes (true)

“APR” (Automatic Power Reduction) • DOL ports

• Terminal amplifierclient ports

• Terminal amplifierDCM ports

Critical Yes (true)

“APSD” (Automatic Power Shutdown) • DOL ports

• Terminal amplifierline ports

Critical Yes (true)

“BDI” (Backward Defect Indication, OTN) OTN OTU interfaces Not alarmed No (false)

“ContComS” (Control CommunicationsFailure, Span Section)

• DOL optical servicechannels

• Terminal amplifierOptical SupervisoryChannels

Major Yes (true)


C H A P T E R 2

Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting“DiskHighUsage” (Disk High Usage) • Management

modules

• Traffic modules

Major No (false)

“EnvCurrentHighTh” (Current Above HighTemperature)

AC PEM Major Yes (true)

“EnvCurrentLowTh” (Current Below LowTemperature)

AC PEM Major Yes (true)

“EnvTempHighTh” (EnvironmentTemperature Above High Threshold)

• PEMs

• Fan modules

• Managementmodules

• Traffic modules

Major Yes (true)

“EnvTempLowTh” (EnvironmentTemperature Above Low Threshold)

• PEMs

• Fan modules


• Traffic modules

Not alarmed Yes (true)

“EnvVoltHighTh” (Environment VoltageAbove High Threshold)

• AC PEMs

• Traffic modules

Major Yes (true)

“EnvVoltLowTh” (Environment VoltageBelow Low Threshold)

• AC PEMs

• Traffic modules

Major Yes (true)

“EqptComm” (Equipment ManagementCommunications Failure)

Traffic modules Major Depends on causeof alarm

“EqptDgrd” (Equipment Degrade) • UFM modules

• BIC modules

Major Yes (true)

“EqptFail” (Equipment Failure) • Equipment


• Traffic modules

• Pluggabletransceivers

Critical Yes (true)

“EqptMism” (Equipment Mismatch) • Equipment


• Traffic modules


Critical Yes (true)


Alarms and conditions

Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting“EqptMiss” (Equipment Missing) • Equipment


• Traffic modules


Critical Yes (true)

“FanSpeedLowTh” (Fan Speed BelowThreshold)

Fan module Major Yes (true)

“FECI” (Far-End Node ConfigurationMismatch)

• DOL ports


Major Yes (true)

“FEIM” (Far-End Node IdentificationMismatch)

• DOL ports


Major Yes (true)

“FirmUpgrdInProg” (Automatic ShelfManagement Firmware Upgrade inProgress)

Management modules Not alarmed No (false)

“FirmUpgrdFail” (Shelf ManagementFirmware Upgrade Failed)

Management modules Major No (false)

“FirmUpgrdReqd” (Firmware UpgradeRequired)

Management modules Major No (false)

“Forced” (Forced Protection Switch Active) Wavelength protectionports

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/SDHinterfaces

• Wavelength channels

Critical Yes (true)



Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting“LaserTempHighTh” (Laser TemperatureAbove High Temperature Threshold)

• OTN OTU interfaces




Major No (false)

“LaserTempLowTh” (Laser TemperatureBelow Low Temperature Threshold)





Major 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 protectionports


“LOF” (Loss of Frame) • OTN OTU interfaces


Critical Yes (true)

“LoLightRx” (Loss of Light, Receive) • DOL PRE ports

• DOL optical servicechannels

• DOL optical multiplexsections

• DOL optical channels

• Wavelengthprotection ports

• Terminal amplifierports

Critical Yes (true)

“LoLightTx” (Loss of Light, Transmit) DOL optical channels Major Yes (true)

“LOM” (Loss of Multiframe) OTN OTU interfaces Critical Yes (true)



Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting“LOS” (Loss of Signal) • OTN OTU interfaces




Critical Yes (true)

“LoSpecRx” (Loss out of Specification,Receive)

DOL ports Critical Yes (true)

“LoSync” (Loss of Synchronization) Ethernet interfaces Critical Yes (true)

“LPBK” (Loopback Operated) • OTN OTU interfaces




“MemHighUsage” (Memory High Usage) • Managementmodules

• Traffic modules

Major No (false)

“ModTempHighTh” (Module TemperatureAbove High Threshold)

OTN OTU4 lineinterfaces

Major No (false)

“ModTempLowTh” (Module TemperatureBelow Low Threshold)


Major No (false)

“ModTempShutdown” (ModuleTemperature Shutdown)


Critical Yes (true)

“MS-AIS” (Multiplex Section AlarmIndication Signal, SDH)

SDH interfaces Not alarmed Yes (true)

“MS-RDI” (Multiplex Section RemoteDefect Indication, SDH)

SDH interfaces Not alarmed No (false)

“NonCoLocatedController” (Controllers arein Different Chassis)

• BTI7814 chassis

• BTI7802 chassis

Critical Yes (true)

“ObrHt” (Optical Backreflection HighThreshold Exceeded)

Terminal amplifierOptical Supervisorychannels

Minor 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) DOL optical multiplexsections

Not alarmed Yes (true)

“OneCableDisconnected” (One Multi-Chassis Cable Disconnected)

• BTI7814 chassis

• BTI7802 chassis

Major Yes (true)



Table 2-1 BTI7800 alarms and conditions (Continued) Code Entities Affected Default Severity Service Affecting“OprHighTh” (Optical Power ReceivedAbove High Threshold)





Major No (false)

“OprLowTh” (Optical Power ReceivedBelow Low Threshold)





Major No (false)

“OptHighTh” (Optical Power TransmittedAbove High Threshold)





Major No (false)

“OptLowTh” (Optical Power TransmittedBelow Low Threshold)





Major No (false)

“OTU-AIS” (OTU Alarm Indication Signal) OTN OTU interfaces Not alarmed Yes (false)

“PartitionFault” (Disk Partition FaultDetected)


• Traffic modules

Major No (false)

“PosRxHigh” (Receive Power Out ofSpecification, High)

DOL optical channels Minor Yes (true)

“PosRxLow” (Receive Power Out ofSpecification, Low)

• DOL optical multiplexsections

• DOL optical channels

Major Yes (true)

“PosTxHigh” (Transmit Power Out ofSpecification, High)


“PosTxLow” (Transmit Power Out ofSpecification, Low)


“PowerAbsent” (No Power Available) PEM Critical Yes (true)

“PRBS” (PRBS Test Activated) • OTN OTU interfaces




“PyldMism” (Payload Mismatch) OTN ODU interfaces Critical Yes (true)

“RDI-L” (Remote Defect Indication, Line) SONET interfaces Not alarmed No (false)



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 ControllerManagement Interface Down)

Management modules Major Yes (true)

“scmNoNmConn” (No NetworkManagement Connectivity on SCM)

Management modules Critical Yes (true)

“SD” (Signal Degrade) • OTN OTU interfaces


Minor No (false)

“TIM” (Trace Identifier Mismatch) • OTN OTU interfaces


Critical Yes (true)

“TlossRxHt” (Loss Above High Threshold,Receive)

Terminal amplifier lineports

Minor Yes (true)

“TlossRxLt” (Loss Below Low Threshold,Receive)

Terminal amplifier lineports

Minor Yes (true)

“UPGRD” (Upgrade in Progress) • Managementmodules

• Traffic modules

Minor Yes (true)



AirFilterAbsenceTable 2-2 Alarm details Parameter DescriptionCode AirFilterAbsenceDescription/Cause 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). Note This alarm is supported on the BTI7814 chassis only.

Default Severity Major.

Service Affecting No (false).

Alarm Clearing See “Clearing an AirFilterAbsence alarm”.

Related Fault Hierarchy –

Table 2-3 BTI7800 chassis

Entity NameFault Indicator

Equipment Indicator Statuschassis:<1 | 2> BTI78141 See equipment specifications in the

BTI7800 Series Hardware Overview andInstallation Guide.

Clearing an AirFilterAbsence alarmNote 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 beforeinstalling 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 Install an air filter in the chassis. Step 4 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.



AIS–LTable 2-4 Condition details Parameter DescriptionCode ais-lDescription 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 signalis being transmitted upstream of (and toward) the local NE. See also “Maintenancesignaling”.

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


Module Indicator Statusoc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –

wanoc192:<chassis>/<slot>/<subslot>/<port>

Clearing an AIS-L conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms upstream of the local NE. Step 2 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.



APRTable 2-6 Alarm details Parameter DescriptionCode aprDescription Automatic Power Reduction: For safety reasons, the local port has automatically

reduced laser power. For more information about APR, see the BTI7800 SeriesSoftware Configuration Guide.

Entities Affected • DOL ports (see Table 2-7).

• Terminal amplifier client and DCM ports (see Table 2-8).

Possible Cause A fiber cut has been detected.

Default Severity Critical.


Alarm Clearing See:• “Clearing an APR alarm (PRE port)”

• “Clearing an APR alarm (terminal amplifier port)”

Related Fault Hierarchy See:• “DOL port fault hierarchy”

• “Terminal amplifier port fault hierarchy”

Table 2-7 DOL ports


Module Indicator Statusport:<chassis>/<slot>/1/PRE PRE Fault LED, PRE port On

Table 2-8 Terminal amplifier ports


Module Indicator Statusclient:<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)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for a “LoLightRx” alarm on the host module's PRE In port. Step 2 Inspect the fiber at the following locations, and ensure that the fiber is intact, thoroughly

clean, and correctly connected:



• 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)Note Follow all applicable safety requirements as described in the BTI7800 Series


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 transmittedcounters.show statistics current client:identifier

• If the alarm is raised against the DCM Out port, check for a “LoLightRx” alarm onthe DCM In port.

Step 2 Inspect the fiber, and ensure that it is intact, thoroughly clean, and correctly connected. Step 3 Check for alarms on the terminal amplifier line port.




APSDTable 2-9 Alarm details Parameter DescriptionCode apsdDescription 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 ConfigurationGuide.


• Terminal amplifier line ports (see Table 2-11).

Possible Causes • The fiber connection is poor.

• There is a problem with the fiber.

• There is a problem at the far-end transmitter.



Alarm Clearing See:• “Clearing an APSD alarm (DOL port)”

• “Clearing an APSD alarm (terminal amplifier line port)”



Table 2-10 DOL ports


Module Indicator Statusport:<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


Module Indicator Statusline:<chassis>/<slot>/1/<portNum> AMP1 Fault LED, Line port On



Clearing an APSD alarm (DOL port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 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

Step 2 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.

Step 3 Check for and clear an APSD alarm on the NE at the far-end of the fiber. Step 4 Check for alarms on the local DOL port.


Clearing an APSD alarm (terminal amplifier line port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check whether an “LoLightRx” alarm has been raised against the input amplifierOptical Supervisory Channel on the line port, and clear the alarm if it exists.

Step 2 Check for alarms on the terminal amplifier line port.


Step 3 Check for and clear an APSD alarm on the far-end NE. Step 4 Check for alarms on the local terminal amplifier line port.




BDITable 2-12 Condition details Parameter DescriptionCode bdiDescription/Cause 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 beingtransmitted downstream of (and away from) the local NE. (See also “Maintenancesignaling”.)

Entities Affected OTN OTU interfaces (see Table 2-13).



Condition Clearing See “Clearing a BDI condition”.

Related Fault Hierarchy See “OTN interface fault hierarchy”.

Table 2-13 OTN OTU interfaces


Module Indicator Statusotu4:<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 conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms downstream of the local NE. Step 2 Check for conditions on the local interface.




ContComSTable 2-14 Alarm details Parameter DescriptionCode contComSDescription Control Communications Failure, Span Section: Control communications with the

NE at either end of the span section have failed.

Possible Cause There are alarms on the far-end OSC.

Entities Affected • DOL optical service channels (see Table 2-15).

• Terminal amplifier Optical Supervisory Channels (see Table 2-16).



Alarm Clearing See “Clearing a ContComS alarm”.

Related Fault Hierarchy See:• “DOL OSC fault hierarchy”


Table 2-15 DOL optical service channels (OSCs)


Module Indicator Statusosc:<chassis>/<slot>/0/L1 ROADM2 or ILA Fault LED, L1 port On

osc:<chassis>/<slot>/0/C<n>



Table 2-16 Terminal amplifier Optical Supervisory Channels (OSCs)


Module Indicator Statusosc:<chassis>/<slot>/1/<portNum>.<oscNum> AMP1 – –



Clearing a ContComS alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear alarms on OSC entities at both the local and far-end NEs. Step 2 Check the far-end NE for conditions indicating a module reset. Step 3 Check for alarms on the local OSC.




DiskHighUsageTable 2-17 Alarm details Parameter DescriptionCode diskHighUsageDescription Disk High Usage.

Entities Affected Management and traffic modules (see Table 2-18).



Alarm Clearing This alarm indicates that disk usage on the module has exceeded 90%. Forinformation about clearing this alarm, contact your next level of support.


Table 2-18 Management and traffic modules


Module Indicator Statuscmm:<chassis>/<slot> CMM See Appendix C, “BTI7800 Series

module and BIC LED behavior”.ufm:<chassis>/<slot> UFM

roadm:<chassis>/<slot> ROADM2

ila:<chassis>/<slot> ILA

amp:<chassis>/<slot> AMP1

wps:<chassis>/<slot> WPS4



EnvCurrentHighThTable 2-19 Alarm details Parameter DescriptionCode envCurrentHighThDescription/Cause Current Above High Threshold: The output current at the AC power entry module

(PEM) is above the high-current threshold. For information, see “Output-currentthresholds”.

Entities Affected Equipment (see Table 2-20).



Alarm Clearing See “Clearing an EnvCurrentHighTh alarm”.

Related Fault Hierarchy See “Environment fault hierarchy”.

Table 2-20 Equipment


Equipment Indicator Statuspem:<chassis>/<slot> AC PEM See the PEM specifications in the


Clearing an EnvCurrentHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereseating (removing and reinstalling) or replacing equipment.

Step 1 Retrieve environment information to view output-current readings for the PEM:show environment current

Step 2 Reseat the PEM.


Step 3 Replace the PEM. Step 4 Check for alarms on the PEM.




EnvCurrentLowThTable 2-21 Alarm details Parameter DescriptionCode envCurrentLowThDescription/Cause Current Below Low Threshold: The output current at the AC power entry module

(PEM) is below the low-current threshold. For information, see “Output-currentthresholds”.




Alarm Clearing See “Clearing an EnvCurrentLowTh alarm”.






Clearing an EnvCurrentLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Retrieve environment information to view current readings for the PEM:show environment current

Step 2 Reseat the PEM.


Step 3 Replace the PEM. Step 4 Check for alarms on the PEM.




EnvTempHighThTable 2-23 Alarm details Parameter DescriptionCode envTempHighThDescription/Cause Environment Temperature Above High Threshold: The temperature at the

equipment or module has exceeded the high temperature threshold. Forinformation, see “Temperature thresholds - equipment and traffic modules”.

Entities Affected • Equipment (see Table 2-24).

• Management and traffic modules (see Table 2-25).



Alarm Clearing See “Clearing an EnvTempHighTh alarm”.




Equipment Indicator Statuspem:<chassis>/<slot> PEM See equipment specifications in the


fan:<chassis>/<slot> Cooling module





bic:<chassis>/<slot>/<subslot> BIC







Clearing an EnvTempHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Software Configuration Guide before rebooting atraffic module or to the BTI7800 Series Hardware Overview and InstallationGuide before reseating (removing and reinstalling) or replacing equipment ortraffic modules.

Step 1 Retrieve environment information to view the temperature reading for the equipment ortraffic module:show environment temperature

Step 2 Check for and clear a “FanSpeedLowTh” alarm on each cooling module installed in the

chassis. Step 3 Check for alarms on the affected equipment or traffic module.


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. Step 5 Check for alarms on the affected equipment or traffic module.


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.

Step 7 Check for alarms on the equipment or module.


Step 8 Replace the equipment or module. Step 9 Check for alarms on the equipment or module.




EnvTempLowThTable 2-26 Condition details Parameter DescriptionCode envTempLowThDescription/Cause Environment Temperature Above Low Threshold: The temperature at the

equipment or module is higher than the temperature at the low end of the high-temperature threshold range. For information, see “Temperature thresholds -equipment and traffic modules”.





Alarm Clearing See “Clearing an EnvTempLowTh condition”.




Equipment Indicator Statuspem:<chassis>/<slot> PEM – –




Module Indicator Statuscmm:<chassis>/<slot> CMM – –

ufm:<chassis>/<slot> UFM








Clearing an EnvTempLowTh conditionNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Retrieve environment information to view the temperature reading for the equipment ortraffic module:show environment temperature


For information, see the BTI7800 Series Hardware Overview and Installation Guide. Step 3 Check for alarms on the equipment or module.








EnvVoltHighThTable 2-29 Alarm details Parameter DescriptionCode envVoltHighThDescription/Cause Environment Voltage Above High Threshold: The voltage on the equipment (PEM)

or module exceeds the high-voltage threshold. For information, see “Voltagethresholds”. Caution Continued operation might cause equipment damage.


• Traffic modules (see Table 2-31).



Alarm Clearing See “Clearing an EnvVoltHighTh alarm”.






Table 2-31 Traffic modules


Module Indicator Statusufm:<chassis>/<slot> UFM See Appendix C, “BTI7800 Series

module and BIC LED behavior”.amp:<chassis>/<slot> AMP1




Clearing an EnvVoltHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Retrieve environment information to view voltage readings for the equipment or trafficmodule:show environment voltage









EnvVoltLowThTable 2-32 Alarm details Parameter DescriptionCode envVoltLowThDescription/Cause Environment Voltage Above High Threshold: The voltage on the equipment (PEM)

or module is below the low-voltage threshold. For information, see “Voltagethresholds”. Caution Continued operation might cause equipment damage.





Alarm Clearing See “Clearing an EnvVoltLowTh alarm”.









module and BIC LED behavior”.amp:<chassis>/<slot> AMP1




Clearing an EnvVoltLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Retrieve environment information to view voltage readings for the equipment or trafficmodule:show environment voltage



Step 3 Check for alarms on the equipment or module:






EqptCommTable 2-35 Alarm details Parameter DescriptionCode eqptCommDescription/Cause Equipment Management Communications Failure: The CMM is not able to

communicate with the equipment.

Entities Affected Traffic modules (see Table 2-36).


Service Affecting Depends on reason alarm has been raised.

Alarm Clearing See “Clearing an EqptComm alarm”.

Related Fault Hierarchy See “Equipment fault hierarchy”.




module and BIC LED behavior”.roadm:<chassis>/<slot> ROADM2




Clearing an EqptComm alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Software Configuration Guide before rebooting anactive CMM.

Step 1 Perform a warm reboot of the active CMM, and then check for alarms on the affectedmodule.• If the alarm has cleared, you have completed this procedure.• If the alarm does not clear, go to Step 2.

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.



EqptDgrdTable 2-37 Alarm details Parameter DescriptionCode eqptDgrdDescription/Cause Equipment Degrade: Initialization of a module has failed.

Entities Affected Traffic modules (see Table 2-38).



Alarm Clearing See “Clearing an EqptDgrd alarm”.




Module Indicator Statusufm:<chassis>/<slot> UFM See Appendix C, “BTI7800 Series module

and BIC LED behavior”.bic:<chassis>/<slot>/<subslot> 1x CFP BIC or12x SFP+ BIC

Clearing an EqptDgrd alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Software Configuration Guide before eitherrebooting or changing the administrative status of equipment.

Step 1 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. Step 2 Check for alarms on the module.




EqptFailTable 2-39 Alarm details Parameter DescriptionCode eqptFailDescription/Cause Equipment Failure: A hardware self-test has detected faulty equipment.



• Pluggable transceivers (see Table 2-41).



Alarm Clearing See “Clearing an EqptFail alarm”.


.



Equipment Indicator Statuscap:<chassis>/<slot> CAP See equipment specifications in the



esl:<chassis>/<slot> ESL

pem:<chassis>/<slot> PEM












Table 2-42 Pluggable transceivers


Transceiver Indicator Status<transceiver-type>:<chassis>/<slot>/<subslot>/<port>

where transceiver-type corresponds to the typeof transceiver installed in the port; for example,cfp or sfpPlus.

CFP, SFP+ Fail LED, CFP or SFP+ clientport on BIC

On

pre:<chassis>/<slot> PRE Fail LED, PRE port

Clearing an EqptFail alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Reseat the equipment (equipment, traffic module, or pluggable transceiver). Step 2 Check for alarms.


Step 3 Replace the equipment. Step 4 Check for alarms on the equipment.




EqptMismTable 2-43 Alarm details Parameter DescriptionCode eqptMismDescription/Cause Equipment Mismatch: The installed equipment does not match the equipment

provisioned for the slot or subslot.






Alarm Clearing See “Clearing an EqptMism alarm”.




Equipment Indicator Statusfan:<chassis>/<slot> Cooling module See equipment specifications in the







module and BIC LED behavior”.bic:<chassis>/<slot>/<subslot> BIC











CFP, SFP+ Fail LED, CFP or SFP+ clientport on BIC

On

Clearing an EqptMism alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Note Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing equipment.

Step 1 Retrieve equipment-provisioning information:show equipment

Step 2 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 theBTI7800 Software Configuration Guide.

• Replace the equipment with equipment that matches the provisioned settings. Step 3 Check for alarms on the equipment.




EqptMissTable 2-47 Alarm details Parameter DescriptionCode eqptMissDescription/Cause Equipment Missing: Provisioned equipment is not physically present in a slot or

subslot.






Alarm clearing See “Clearing an EqptMiss alarm”.




Equipment Indicator Statusfan:<chassis>/<slot> Cooling module – –





Module Indicator Statuscmm:<chassis>/<slot> CMM – –

ufm:<chassis>/<slot> UFM












CFP, SFP+ – –

pre:<chassis>/<slot> PRE – –

Clearing an EqptMiss alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Note Refer to the BTI7800 Series Hardware Overview and Installation Guide beforeinstalling equipment.

Step 1 Retrieve inventory and provisioned-equipment information:show inventoryshow equipment

Step 2 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 Install the missing equipment, ensuring that its attributes match the attributes of the

equipment provisioned for the slot or subslot. For information, see the BTI7800Hardware Overview and Installation Guide.

Step 5 Check for alarms on the equipment.




FanSpeedLowThTable 2-51 Alarm details Parameter DescriptionCode fanSpeedLowThDescription 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.

• The power entry module is faulty.



Alarm Clearing See “Clearing a FanSpeedLowTh alarm”.




Equipment Indicator Statusfan:<chassis>/<slot> Cooling module See cooling module specifications in the


Clearing a FanSpeedLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 1 Retrieve fan-speed information for the cooling modules installed in the chassis:show environment fanspeed


Note See the BTI7800 Series Hardware Overview and Installation Guide forinformation 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 4.



Step 4 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.

Step 5 Replace the cooling module, and then check for alarms.




FECITable 2-53 Alarm details Parameter DescriptionCode feciDescription/Cause Far-End Node Configuration ID Mismatch: Either the configuration of the DOL fiber-

connection is not supported or the expected far-end degree and group valuesprovisioned on a terminal amplifier Optical Supervisory Channel do not match theactual (far-end) degree and group values.





Alarm Clearing See:• “Clearing a FECI alarm (DOL port)”

• “Clearing a FECI alarm (terminal amplifier OSC)”














Clearing a FECI alarm (DOL port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve DOL fiber-connection information to identify the unsupported fiber-connectionconfiguration:show dol fiber-conn

Step 2 Delete the unsupported fiber connection, and reprovision the fiber connection using a

supported configuration. For information, see the BTI7800 Series SoftwareConfiguration Guide.



Clearing a FECI alarm (terminal amplifier OSC)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve information for the OSC:show amp

Step 2 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

Step 3 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 theBTI7800 Series Software Configuration Guide.

Step 4 Check for alarms on the OSC.




FEIMTable 2-56 Alarm details Parameter DescriptionCode feimDescription/Cause 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 systeminformation provisioned on a terminal amplifier Optical Supervisory Channel doesnot match the actual (far-end) system information





Alarm Clearing See:• “Clearing a FEIM alarm (DOL port)”

• “Clearing a FEIM alarm (terminal amplifier OSC)”














Clearing a FEIM alarm (DOL port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve DOL fiber-connection information to determine whether the provisionedendpoints or the actual endpoints of the fiber connection are incorrect:show dol fiber-conn

Step 2 Delete the incorrect fiber connection, and reprovision the fiber-connection so that the

mismatch is resolved. For information, see the BTI7800 Series Software ConfigurationGuide.



Clearing a FEIM alarm (terminal amplifier OSC)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve information for the OSC:show amp

Step 2 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

Step 3 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.

Step 4 Check for alarms on the OSC.




FirmUpgrdInProgTable 2-59 Condition details Parameter DescriptionCode firmUpgrdInProgDescription/Cause Automatic Shelf Management Firmware Upgrade in Progress: A shelf management

(SHMM) firmware upgrade is in progress.

Entities Affected Management modules (see Table 2-60)



Condition Clearing This condition clears when the firmware is successfully upgraded. For information,see the BTI7800 Series Software Configuration Guide.


Table 2-60 Management modules



module and BIC LED behavior”.



FirmUpgrdFailTable 2-61 Alarm details Parameter DescriptionCode firmUpgrdFailDescription/Cause Shelf Management Firmware Upgrade Failed: A shelf management (SHMM)

firmware upgrade (manual or automatic) has failed.

Entities Affected Management modules (see Table 2-62).



Alarm Clearing See “Clearing a FirmUpgrdFail alarm”.






Clearing a FirmUpgrdFail alarmStep 1 Reattempt the firmware upgrade. For information, see the BTI7800 Series Hardware

Overview and Installation Guide. Step 2 Check for alarms on the CMM.




FirmUpgrdReqdTable 2-63 Alarm details Parameter DescriptionCode firmUpgrdReqdDescription/Cause 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.




Alarm Clearing This alarm clears when the firmware is successfully upgraded. For information, seethe BTI7800 Series Software Configuration Guide.








ForcedTable 2-65 Condition details Parameter DescriptionCode forcedDescription/Cause Forced Protection Switch Active: The operator has forced a protection switch.

Entities Affected Wavelength protection ports (see Table 2-66).



Condition Clearing This condition clears when the protection switch is released. For information, seethe BTI7800 Series Software Configuration Guide.


Table 2-66 Wavelength protection ports


Module Indicator Statuswpsport:<chassis>/<slot>/L<n>

where n is in the range of 1A to 4A or 1B to 4B.

WPS4 – –



HighBerTable 2-67 Alarm details Parameter DescriptionCode highBerDescription 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.

• There is excessive attenuation of the signal, causing high a signal-to-noise ratio.



Alarm Clearing See “Clearing a HighBer alarm”.

Related Fault Hierarchy See “Ethernet interface fault hierarchy”.

Table 2-68 Ethernet interfaces


Module Indicator Status100ge:<chassis>/<slot>/<subslot>/<port>/<subport>

1x CFP BIC Fault LED, 100G port On

10ge:<chassis>/<slot>/<subslot>/<port>/<subport>

12x SFP+ BIC Fault LED, 10G port



Clearing a HighBer alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 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 PowerReceived Minimum Threshold and Optical Power Received Maximum Thresholdvalues.show interface name:identifier detail

Note For detailed transceiver specifications, see Appendix B, “BTI7800 Seriestransceivers”.

Step 2 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and

correctly connected to the port. Step 3 Ensure that no unintentional attenuation has been added to the fiber. Step 4 Check for alarms on the interface.




InvUnknownTable 2-69 Alarm details Parameter DescriptionCode invUnknownDescription/Cause Inventory Unknown: The installed pluggable transceiver is not readable.

Entities Affected Pluggable transceivers (see Table 2-70).



Alarm Clearing See “Clearing an InvUnknown alarm”.






CFP, SFP+ Fail LED, 100GE or 10GEport

On

Clearing an InvUnknown alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing a transceiver.

Step 1 Replace the unknown transceiver with a readable transceiver. For information aboutsupported transceivers, see Appendix B, “BTI7800 Series transceivers”.

Step 2 Check for alarms on the port.




LaserFailTable 2-71 Alarm details Parameter DescriptionCode laserFailDescription/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).



Alarm Clearing See “Clearing a LaserFail alarm”.

Related Fault Hierarchy See “Common fault hierarchy - OTN and CBR ports”.












Table 2-74 SONET/SDH interfaces


Module Indicator Statusoc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port On


stm64:<chassis>/<slot>/<subslot>/<port>

wanstm64:<chassis>/<slot>/<subslot>/<port>



Table 2-75 Wavelength channels


Module Indicator Statuschannel:<chassis>/<slot>/<subslot>/<port.channel>

1x CFP BIC1 Fault LED, 100G port On

1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers.

Clearing a LaserFail alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Software Configuration Guide before rebooting atraffic module or to the BTI7800 Series Hardware Overview and InstallationGuide replacing a traffic module or transceiver.

Step 1 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. Step 2 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.

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 MSAtransceiver, replace the UFM.

• If the alarm is raised against a client-port interface provisioned on a pluggabletransceiver, replace the pluggable transceiver.

Step 4 Check for alarms on the interface.




LaserTempHighThTable 2-76 Alarm details Parameter DescriptionCode laserTempHighThDescription Laser Temperature Above High Temperature Threshold: The transmit laser

temperature has exceeded the high temperature threshold.





Possible Causes The transmit laser is malfunctioning.



Alarm Clearing See “Clearing a LaserTempHighTh alarm”.


























Clearing a LaserTempHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing a traffic module or a transceiver.

Step 1 Optionally, retrieve detailed information for the interface to view the LaserTemperature and Laser Temperature Max. Threshold values:show interface name:identifier detail

Step 2 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. Step 3 Check for alarms on the interface.




LaserTempLowThTable 2-81 Alarm details Parameter DescriptionCode laserTempLowThDescription Laser Temperature Below Low Temperature Threshold: The transmit laser

temperature has fallen below the low temperature threshold.





Possible Causes The transmit laser is malfunctioning.



Alarm Clearing See “Clearing a LaserTempLowTh alarm”.

Related Fault Hierarchy See Chapter 3, “Fault masking”.

























Clearing a LaserTempLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing a traffic module or a transceiver.

Step 1 Optionally, retrieve detailed information for the interface to view the LaserTemperature and Laser Temperature Min. Threshold values:show interface name:identifier detail


against a line-port interface provisioned on an integrated MSA, the UFM. Step 3 Check for alarms on the interface.




LCKTable 2-86 Alarm details Parameter DescriptionCode lckDescription 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 islocked.

Entities Affected OTN ODU interfaces (see Table 2-87).

Possible Causes The transmitting OTN OTU interface at an upstream NE is either administrativelydisabled or in loopback mode.



Alarm Clearing See “Clearing an LCK alarm”.


Table 2-87 OTN ODU interfaces


Module Indicator Statusodu4:<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.sub-interface>

odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port



Clearing an LCK alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve data for the transmitting OTU interface at the upstream NE to determinewhether it is either administratively disabled (Admin State = disabled) or in loopbackmode (Loopback = loopback)show interface name:identifier

Step 2 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.

Step 3 Check for alarms on the local interface.




LFTable 2-88 Condition details Parameter DescriptionCode lfDescription 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 upstreamof (and toward) the local NE. (See also “Maintenance signaling”.)




Condition Clearing See “Clearing an LF condition ”.





1x CFP BIC – –


12x SFP+ BIC

Clearing an LF conditionNote Follow all applicable safety requirements as described in the BTI7800 Series






LockoutTable 2-90 Condition details Parameter DescriptionCode lockoutDescription/Cause Lockout of Protection: The operator has locked out a line port for protection.

Entities Affected Wavelength protection ports (see Table 2-91).



Condition Clearing This condition clears when the protection switch is released. For information, seethe BTI7800 Series Software Configuration Guide.






WPS4 – –



LOFTable 2-92 Alarm details Parameter DescriptionCode lofDescription 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.



Possible Causes • Either the fiber link or the optical connection is severely degraded.

• The far-end optical transmitter is faulty.



Alarm Clearing See “Clearing an LOF alarm”.

Related Fault Hierarchy 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-94 SONET /SDH interfaces








Clearing an LOF alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, andcorrectly connected to the port.

Step 2 Check for and clear all alarms raised against the far-end optical transmitter. Step 3 Check for alarms on the local interface.




LoLightRxTable 2-95 Alarm details Parameter DescriptionCode loLightRxDescription/Cause Loss of Light, Receive: The optical power received has dropped below the loss-of-

light threshold.

Entities Affected • DOL PRE Ports (see Table 2-96).

• 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).



Alarm Clearing See:• “Clearing a LoLightRx alarm (DOL entity)”

• “Clearing a LoLightRx alarm (wavelength protection port)”

• “Clearing a LoLightRx alarm (terminal amplifier port)”


• “DOL OSC fault hierarchy”

• “DOL OMS fault hierarchy”

• “DOL OCH fault hierarchy”

• “Terminal amplifier port fault hierarchy” Note For wavelength protection ports, this alarm is not masked by any other alarm.

Table 2-96 DOL PRE ports


Module Indicator Statusport:<chassis>/<slot>/0/PRE PRE Fault LED, PRE port On

port:<chassis>/<slot>/1/PRE



Table 2-97 DOL optical service channels (OSCs)


Module Indicator Statusosc:<chassis>/<slot>/0/L1 ROADM2 or ILA Fault LED, L1 port On

osc:<chassis>/<slot>/0/C<n>



Table 2-98 DOL optical multiplex sections (OMSs)


Module Indicator Statusoms:<chassis>/<slot>/0/L1<> ROADM2 or ILA Fault LED, L1 port On

oms:<chassis>/<slot>/0/C<n>



Table 2-99 DOL optical channels (OCHs)


Module Indicator Statusoch:<chassis>/<slot>/0/C<n>/<channel>

where the range of n depends on the moduleand channel is an alphanumeric string.

ROADM2 – –





WPS4 Fault LED, Line<n> port On

Table 2-101 Terminal amplifier ports



Online:<chassis>/<slot>/1/<portNum> Fault LED, Line port

dcm:<chassis>/<slot>/1/<portNum> Fault LED, DCM port

client:<chassis>/<slot>/1/<portNum> Fault LED, C1 port



Clearing a LoLightRx alarm (DOL entity)Note Follow all applicable safety requirements as described in the BTI7800 Series


Note In some ROADM network topologies with ILAs deployed, amplifiedspontaneous emissions (ASE) might accumulate sufficiently to cause this alarmto clear on provisioned but unoccupied optical channels. (The ASE will not behigh enough to affect optical performance, however.)

Step 1 Retrieve statistics for the affected entity to view the value of the Optical powerreceived counter:show statistics current name:identifier


• 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 “DOLOSC power alarm thresholds”, “DOL OMS power alarm thresholds”, or “DOL OCHpower 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 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.

Step 5 Check for alarms on the local DOL entity.




Clearing a LoLightRx alarm (wavelength protection port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve information for the wavelength protection port to view the values of thereceived-loss-of-light threshold (LoLightRx Th) and the optical power received Opt.Pw.Rx counter:show protection wavelength port name:identifier


• Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, andcorrectly connected to the port.

• Check for and clear all alarms on the upstream NE. Step 3 Check for alarms on the local port.


Clearing a LoLightRx alarm (terminal amplifier port)Note Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the port to view the value of the Optical power receivedcounter:show statistics current name:identifier


• 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.

Step 3 Check for alarms on the local port.




LoLightTxTable 2-102 Alarm details Parameter DescriptionCode loLightTxDescription/Cause Loss of Light, Transmit: The optical power transmitted has dropped below the loss-

of-light threshold.

Entities Affected DOL optical channels (see Table 2-103).



Alarm Clearing See “Clearing a LoLightTx alarm”.

Related Fault Hierarchy See “DOL OCH fault hierarchy”.



Module Indicator Statusoch:<chassis>/<slot>/0/L1/<channel>

where channel is an alphanumeric string.

ROADM2 – –

och:<chassis>/<slot>/0/C<n>/<channel>

where the range of n depends on the moduleand channel is an alphanumeric string.

Clearing a LoLightTx alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Note In some ROADM network topologies with ILAs deployed, amplifiedspontaneous emissions (ASE) might accumulate sufficiently to cause this alarmto clear on provisioned but unoccupied optical channels. (The ASE will not behigh enough to affect optical performance, however.)

Step 1 Retrieve statistics for the DOL OCH to view the value of the Optical powerreceived counter, and then refer to “DOL OCH power alarm thresholds”:show statistics current och:identifier

Step 2 Ensure that the upstream fiber connections are thoroughly clean and correctly connected. Step 3 Check for alarms on the DOL optical channel.




LOMTable 2-104 Alarm details Parameter DescriptionCode lomDescription Loss of Multiframe: The multiframe alignment process is in the out-of-multiframe

state.






Alarm Clearing See “Clearing an LOM alarm”.







Clearing an LOM alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 2 Check for and clear all alarms on the far-end optical transmitter. Step 3 Check for alarms on the local interface.




LOSTable 2-106 Alarm details Parameter DescriptionCode losDescription Loss of Signal: The local port has detected a loss of received signal power.





Possible Causes • The fiber input is disconnected.

• The far-end interface is not yet provisioned.

• The far-end transmit laser is disabled or has failed.



Alarm Clearing See “LOS”.

Related Fault Hierarchy See:• “Common fault hierarchy - OTN and CBR ports”

• “OTN interface fault hierarchy”

• “Ethernet interface fault hierarchy”


























1 Monitoring and reporting of this alarm for a wavelength channel is supported only on multiwavelength CFPtransceivers.

Clearing an LOS alarmNote Follow all applicable safety requirements as described in the BTI7800 Series



Step 2 Ensure that the light path on the optical line system, if it exists, is correctly provisioned

and fault free. Step 3 Check for and resolve the following problems:

• The far-end transmitter is disabled or has failed.• The far-end interface is not provisioned.

Step 4 Check for alarms on the local interface




LoSpecRxTable 2-111 Alarm details Parameter DescriptionCode loSpecRxDescription Loss out of Specification, Receive: The optical loss received is outside the

specification range.

Entities Affected DOL ports (see Table 2-112).

Possible Cause Either the upstream fiber link or the optical connection is degraded.



Alarm Clearing See “Clearing a LoSpecRx alarm”.

Related Fault Hierarchy See “DOL port fault hierarchy”.







Clearing a LoSpecRx alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the DOL port to view the value of the Optical power loss inrecv. direction counter, and then refer to “DOL Rx-loss alarm thresholds”:show statistics current port:identifier

Step 2 Ensure that the upstream fiber connections are intact, thoroughly clean, and correctly

connected. Step 3 Check for alarms on the DOL port.




LoSyncTable 2-113 Alarm details Parameter DescriptionCode loSyncDescription Loss of Synchronization: The signal received on the local interface is sufficiently

degraded that it cannot be synchronized.


Possible Causes • Either the fiber link or the optical connection is severely degraded.




Alarm Clearing See “Clearing a LoSync alarm”.










Clearing a LoSync alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve detailed information for the interface, and ensure that the value of the OpticalPower Rx counter is within the range indicated by the Optical Power ReceivedMinimum Threshold and Optical Power Received Maximum Threshold values.show interface name:identifier detail



correctly connected to the port. Step 3 Check for and clear alarms on the far-end optical transmitter. Step 4 Check for alarms on the local interface.




LPBKTable 2-115 Condition details Parameter DescriptionCode lpbkDescription/Cause Loopback Operated: A loopback test is active on the local port.




Default Severity Not alarmed. (Default severity should not be changed.)


Condition Clearing This condition clears when the loopback is released. For information, see theBTI7800 Series Software Configuration Guide.




Module Indicator Statusotu4:<chassis>/<slot>/<subslot>/<port> UFM4 – –

otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC

otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC




1x CFP BIC – –


12x SFP+ BIC









MemHighUsageTable 2-119 Alarm details Parameter DescriptionCode memHighUsageDescription/Cause Memory High Usage.




Alarm Clearing This alarm indicates that memory usage on the module has exceeded 90%. Forinformation about clearing this alarm, contact your next level of support.












ModTempHighThTable 2-121 Alarm details Parameter DescriptionCode modTempHighThDescription Module Temperature Above High Threshold: The temperature of the MSA

transceiver is above the high-temperature threshold. For information, see“Temperature thresholds - MSA transceivers”.


Possible Causes • The ambient temperature is above the normal operating range of the chassis.

• The output power of the MSA transceiver is excessive.



Alarm Clearing See “Clearing a ModTempHighTh alarm”.







Clearing a ModTempHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Optionally retrieve statistics for the OTU4 interface to view the value of the Moduletemperature parameter:show statistics current otu4:identifier


• Either a cooling module is not present in the chassis or is present but is operationallydown 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. Step 3 Check for alarms on the interface.




ModTempLowThTable 2-123 Alarm details Parameter DescriptionCode modTempLowThDescription Module Temperature Below Low Threshold: The temperature of the MSA

transceiver is below low-temperature threshold. For information, see “Temperaturethresholds - MSA transceivers”.


Possible Cause The ambient temperature is lower than the normal operating range of the chassis.



Alarm Clearing See “Clearing a ModTempLowTh alarm”.





Clearing a ModTempLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Optionally retrieve statistics for the OTU4 interface to view the value of the Moduletemperature parameter:show statistics current otu4:identifier

Step 2 Retrieve environment information to view data on equipment temperature, and ensure

that the ambient temperature is within the specified range for chassis operation. Forinformation, see the BTI7800 Series Hardware Overview and Installation Guide.show environment





ModTempShutdownTable 2-125 Alarm details Parameter DescriptionCode modTempShutdownDescription Module Temperature Shutdown: The temperature of the MSA transceiver has

exceeded the high-temperature-shutdown threshold, causing the transmit laser toshut down. For information, see “Temperature thresholds - MSA transceivers”.

Entities Affected OTN OTU interfaces (see Table 2-122 on page 2-74).

Possible Causes The ambient temperature is excessively higher than the normal operating range ofthe MSA transceiver.



Alarm Clearing See “Clearing ModTempShutdown alarm”.







Clearing ModTempShutdown alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing a traffic module.

Step 1 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. Step 2 Check for alarms on the OTU4 interface.


Step 3 Replace the UFM4. Step 4 Check for alarms on the interface.




MS-AISTable 2-127 Condition details Parameter DescriptionCode ms-aisDescription/Cause 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 isbeing transmitted upstream of (and toward) the local NE. (See also “Maintenancesignaling”.)

Entities Affected SDH (STM64, WAN PHY STM64) interfaces (see Table 2-128).



Condition Clearing See “Clearing an MS-AIS condition”.

Related Fault Hierarchy See “STM64, WAN PHY over STM64 interface fault hierarchy”.

Table 2-128 SDH (STM64, WAN PHY STM64) interfaces


Module Indicator Statusstm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –


Clearing an MS-AIS conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms on the upstream NE. Step 2 Check for conditions on the local interface.




MS-RDITable 2-129 Alarm details Parameter DescriptionCode ms-rdiDescription/Cause 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 SDHsignal 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).



Alarm Clearing See “Clearing an MS-RDI condition”.

Related Fault Hierarchy See “STM64, WAN PHY over STM64 interface fault hierarchy”.

Table 2-130 SDH (STM64, WAN PHY STM64) interfaces


Module Indicator Statusstm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –


Clearing an MS-RDI conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms on the downstream NE. Step 2 Check for conditions on the local interface.




NonCoLocatedControllerTable 2-131 Alarm details Parameter DescriptionCode nonCoLocatedControllerDescription/Cause Controllers are in Different Chassis: The active CMMs in a multi-chassis

configuration are not located in the same chassis.

Entities Affected Equipment (see Table 2-132). Note This alarm is supported on the BTI7814 and BTI7802 chassis only.



Alarm Clearing See “NonCoLocatedController”.




Equipment Indicator Statuschassis:<1 | 2> BTI7814 or BTI7802 See equipment specifications in the


Clearing a NonCoLocatedController alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve information for the hub and satellite chassis:show system chassis

Step 2 Ensure that multi-chassis system is correctly configured. For information, see the

BTI7800 Series Software Configuration Guide. Step 3 Check for alarms on the chassis.




ObrHtTable 2-133 Alarm details Parameter DescriptionCode obrHtDescription Optical Backreflection High Threshold Exceeded: The optical backreflection has

exceeded the high threshold. Note The default administrative status of this alarm is disabled.

Entities Affected Terminal amplifier Optical Supervisory Channels (see Table 2-134).

Possible Cause The fiber connection is poor.

Default Severity Minor.


Alarm Clearing See “Clearing an ObrHt alarm”.

Related Fault Hierarchy See “Terminal amplifier port fault hierarchy”.




Clearing an ObrHt alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the entity to view the value of the Optical back reflectedpower counter:show statistics current name:identifier

Step 2 Retrieve statistics information from the running configuration file to view the threshold

profile for the OSC:show running-config statistics

Examplebti7800# show running-config statistics threshold profilestatistics threshold profile obrdis entityType osc statistic opt-back-ref-ratio alarmHigh unTimed enabled



dec64RaiseValue -27.0 dec64ClearValue -28.0 !

Step 3 Ensure that the span fiber at the Line output port is intact, thoroughly clean, and

correctly connected. Step 4 Ensure that the fiber connectors are compatible. Step 5 Ensure that any downstream fiber connections are thoroughly cleaned and correctly

connected. Step 6 Check for alarms on the OSC.




OchAisTable 2-135 Condition details Parameter DescriptionCode ochAisDescription 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 (andtoward) the local NE.




Condition Clearing See “Clearing an OchAis condition”.




Module Indicator Statusoch:<chassis>/<slot>/0L1/<channel>


ROADM2 – –


where n depends on the module and channel isan alphanumeric string.

Clearing an OchAis conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms upstream of the local NE. Step 2 Check for excessive loss on the receive span fiber, and, if required, ensure that all

upstream fibers are thoroughly cleaned and correctly connected. Step 3 Ensure that all upstream fibers are thoroughly clean and correctly connected. Step 4 Check for conditions on the DOL optical channel.




OchOciTable 2-137 Alarm details Parameter DescriptionCode ochOciDescription 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 missingoptical cross-connect on an upstream node.




Alarm Clearing See “Clearing an OchOci condition”.






ROADM2 – –

Clearing an OchOci conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 If required, retrieve cross-connect information for the upstream node:show dol och-xcon

Step 2 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.

Step 3 Check for conditions on the local DOL OCH.




OchUeqTable 2-139 Alarm details Parameter DescriptionCode ochUeqDescription/Cause OCH Unequipped: The downstream optical channel is not provisioned.




Alarm Clearing See “Clearing an OchUeq alarm”.






ROADM2 – –

Clearing an OchUeq alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Provision the DOL OCH on the downstream node. For information, see the BTI7800Series Software Configuration Guide.

Step 2 Check for alarms on the local DOL OCH.




OCITable 2-141 Alarm details Parameter DescriptionCode ociDescription/Cause 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 presenton an upstream node.




Alarm Clearing See “Clearing an OCI alarm”.








Clearing an OCI alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Provision the missing cross-connect. For information, see the BTI7800 Series SoftwareConfiguration Guide.

Step 2 Check for alarms on the local interface.




ODU-AISTable 2-143 Condition details Parameter DescriptionCode odu-aisDescription/Cause 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 ODUsignal is being transmitted upstream of (and toward) the local NE. (See also“Maintenance signaling”.)


• OTN ODU interfaces (see Table 2-145).



Condition Clearing See “Clearing an ODU-AIS condition”.







Module Indicator Statusodu4:<chassis>/<slot>/<subslot>/<port> UFM4 – –

odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC


odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC



Clearing an ODU-AIS conditionNote Follow all applicable safety requirements as described in the BTI7800 Series






OmsAisTable 2-146 Condition details Parameter DescriptionCode OmsAisDescription 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 (andtoward) the local NE.

Entities Affected DOL optical multiplex sections (see Table 2-147).



Condition Clearing “Clearing an OmsAis condition”

Related Fault Hierarchy See “DOL OMS fault hierarchy”.



Module Indicator Statusoms:<chassis>/<slot>/0/L1<> ROADM2 or ILA Fault LED, L1 port On




Clearing an OmsAis conditionNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Check for and clear all alarms upstream of the local NE. Step 2 Ensure that the far-end NE has at least one optical channel provisioned and cross-

connected. Step 3 Check for excessive loss on the receive span fiber, and, if required, ensure that all

upstream fibers are intact, thoroughly clean, and correctly connected. Step 4 Check for conditions on the DOL OMS.




OneCableDisconnectedTable 2-148 Alarm/condition details Parameter DescriptionCode oneCableDisconnectDescription/Cause One Multi-Chassis Cable Disconnected: A cable that connects two CMMs in a multi-

chassis configuration is not connected to a CMM.

Entities Affected Equipment (see Table 2-149). Note This alarm is supported on the BTI7814 and BTI7802 chassis only.



Alarm Clearing See “Clearing a OneCableDisconnected alarm”.




Equipment Indicator Statuschassis:<1 | 2> BTI7814 or BTI7802 See equipment specifications in the


Clearing a OneCableDisconnected alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Inspect the cable connecting the CMMs, and ensure that it is intact and correctlyconnected.

Step 2 Check for alarms on the chassis.




OprHighThTable 2-150 Alarm details Parameter DescriptionCode oprHighThDescription Optical Power Received Above High Threshold: The optical power received is

above the high threshold.





Possible Causes • There is inadequate attenuation on the optical connection to signal source.

• The output power on the remote optical transmitter is too high.



Alarm Clearing See “Clearing an OprHighTh alarm”.




















Table 2-153 SONET/SDH interfaces (Continued)


Module Indicator Statuswanstm64:<chassis>/<slot>/<subslot>/<port>






Clearing an OprHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series




Step 2 Check for and clear alarms on the far-end optical transmitter. Step 3 Check for alarms on the local interface.


Step 4 Add an attenuation pad in the optical path. Step 5 Check for alarms on the local interface.




OprLowThTable 2-155 Alarm details Parameter DescriptionCode oprLowThDescription Optical Power Received Below Low Threshold: The optical power received is below

the low threshold.





Possible Causes • There is excessive attenuation on either the fiber link or the optical connection.




Alarm Clearing See “Clearing an OprLowTh alarm”.




















Table 2-158 SONET/SDH interfaces (Continued)


Module Indicator Statuswanstm64:<chassis>/<slot>/<subslot>/<port>






Clearing an OprLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series




Step 2 Check for and clear alarms on the far-end optical transmitter. Step 3 Check for alarms on the local interface.


Step 4 Inspect the fiber at the local port, and ensure that it is intact, thoroughly clean, and

correctly connected to the port. Step 5 Check for alarms on the local interface.




OptHighThTable 2-160 Alarm details Parameter DescriptionCode optHighThDescription Optical Power Transmitted Above High Threshold: The optical power transmitted is

above the high threshold.





Possible Cause The optical transmitter is faulty.



Alarm Clearing See “Clearing an OptHighTh alarm”.


























Clearing an OptHighTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing 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 PowerTransmitted Minimum Threshold and Optical Power Transmitted MaximumThreshold values.show interface name:identifier detail







OptLowThTable 2-165 Alarm details Parameter DescriptionCode optLowThDescription Optical Power Transmitted Below Low Threshold: The optical power transmitted is

below the low threshold.





Possible Cause The transmit laser is failing.



Alarm Clearing See “Clearing an OptLowTh alarm”.


























Clearing an OptLowTh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Hardware Overview and Installation Guide beforereplacing 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 PowerTransmitted Minimum Threshold and Optical Power Transmitted MaximumThreshold values.show interface name:identifier detail







OTU-AISTable 2-170 Condition details Parameter DescriptionCode otu-aisDescription/Cause 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 beingtransmitted upstream of (and toward) the local NE. Note This signal is generated by non-BTI7800 NEs only.




Condition Clearing The condition will clear when the fault that resulted in the transmission of the OTU-AIS signal is resolved.









PartitionFaultTable 2-172 Alarm details Parameter DescriptionCode partitionFaultDescription/Cause Disk Partition Fault Detected.




Alarm Clearing See “Clearing a ParitionFault alarm”.




Modules Indicator Statuscmm:<chassis>/<slot> CMM See Appendix C, “BTI7800 Series






Clearing a ParitionFault alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Important Refer to the BTI7800 Series Software Configuration Guide before rebooting atraffic module.

Step 1 Perform a warm reboot of the module. Step 2 Check for alarms on the module.




PosRxHighTable 2-174 Alarm details Parameter DescriptionCode posRxHighDescription/Cause Receive Power Out of Specification, High: The optical power received is above the

specified range for operation.




Alarm Clearing See “Clearing a PosRxHigh alarm”.






ROADM2 – –



Clearing a PosRxHigh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve PM statistics for the DOL OCH:show statistics current och:identifier

Step 2 Refer to “DOL OCH power alarm thresholds” to determine whether the optical power

received is higher than the specified range for operation. Step 3 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. Step 4 Check for alarms on the DOL OCH.




PosRxLowTable 2-176 Alarm details Parameter DescriptionCode posRxLowDescription 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).

• DOL optical channels (see Table 2-178).

Possible Cause



Alarm Clearing See “Clearing a PosRxHigh alarm”.

Related Fault Hierarchy See:• “DOL OMS fault hierarchy”

• “DOL OCH fault hierarchy”



Module Indicator Statusoms:<chassis>/<slot>/0/L1<> ROADM2 or ILA – –







ROADM2 – –





Clearing a PosRxLow alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the DOL entity:show statistics current name:identifier

Step 2 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 specifiedrange for operation.

Step 3 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. Step 4 Check for alarms on the DOL entity.




PosTxHighTable 2-179 Alarm details Parameter DescriptionCode posTxHighDescription/Cause 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 2-182 on page 2-106).



Alarm Clearing See “Clearing a PosTxHigh alarm”.






ROADM2 – –



Clearing a PosTxHigh alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the DOLOCH:show statistics current och:identifier


transmitted is out of the specified range for operation. Step 3 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. Step 4 Check for alarms on the DOL OCH.




PosTxLowTable 2-181 Alarm details Parameter DescriptionCode posTxLowDescription/Cause Transmit Power Out of Specification, Low: The optical power transmitted is below

the specified range for operation.




Alarm Clearing See “Clearing a PosTxLow alarm”.






ROADM2 – –



Clearing a PosTxLow alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the DOL OCH:show statistics current och:identifier


transmitted is lower than the range specified for operation. Step 3 If the optical power transmitted is too low, ensure that the upstream fiber connections

are intact, thoroughly clean, and correctly connected. Step 4 Check for alarms on the DOL OCH.




PowerAbsentTable 2-183 Alarm details Parameter DescriptionCode powerAbsentDescription No Power Available: No power is available to the power entry module (PEM).

Caution Continued operation might cause equipment damage.


Possible Causes • AC PEM: The input AC voltage is either less than 90 Vac or greater than 255Vac, and the output DC voltage is either less than 40 Vdc or greater than 60Vdc.

• DC PEM: The input and output DC voltages are either less than 40 Vdc orgreater than 60 Vdc.



Alarm Clearing See “Clearing a PowerAbsent alarm”.




Equipment Indicator Statuspem:<chassis>/<slot> PEM See the PEM specifications in the


Clearing a PowerAbsent alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


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.



PRBSTable 2-185 Condition details Parameter DescriptionCode prbsDescription/Cause PRBS Test Activated: A PRBS test is active on the local port.




Default Severity Not alarmed. (Default severity should not be changed.)


Condition Clearing This condition clears when PRBS-signal generation is turned off. For information,see the BTI7800 Series Software Configuration Guide.





otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC

otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC




1x CFP BIC – –


12x SFP+ BIC









PyldMismTable 2-189 Alarm details Parameter DescriptionCode pyldMismDescription Payload Mismatch: The payload type in the received signal is not the expected

payload type.


Possible Cause The cross-connect configuration at the far-end NE does not match the cross-connect configuration at the local NE.



Alarm Clearing See “Clearing a PyldMism alarm”.










Clearing a PyldMism alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve interface data to compare the values of the Payload Type and ReceivedPayload Type parameters.show interface name:identifier

Step 2 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

Step 3 Delete the correct cross-connect, and reprovision it to resolve the mismatch. For

information, see the BTI7800 Series Software Configuration Guide. Step 4 Check for alarms on the local interface.




RDI-LTable 2-191 Condition details Parameter DescriptionCode rdi-lDescription/Cause 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 beingtransmitted downstream of (and away from) the local NE. (See also “Maintenancesignaling”.)

Entities Affected SONET (OC192, WAN PHY OC192) interfaces (see Table 2-192).



Condition Clearing See “Clearing an RDI-L condition”.

Related Fault Hierarchy See “OC192, WAN PHY over OC192 interface fault hierarchy”.

Table 2-192 SONET (OC192, WAN PHY OC192) interfaces




Clearing an RDI-L conditionNote Follow all applicable safety requirements as described in the BTI7800 Series






RFTable 2-193 Condition details Parameter DescriptionCode rfDescription/Cause 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 transmitteddownstream of (and away from) the local NE. (See also “Maintenance signaling”.)




Condition Clearing See “Clearing an RF condition”.





1x CFP BIC – –


12x SFP+ BIC

Clearing an RF conditionNote Follow all applicable safety requirements as described in the BTI7800 Series






ScmNmiDownTable 2-195 Alarm details Parameter DescriptionCode scmNmiDownDescription/Cause System Controller Module (SCM) Interface Down: One of the SCMs in a dual-CMM

system cannot connect to the management IP network.




Alarm Clearing See “Clearing an ScmNmiDown alarm ”.






Clearing an ScmNmiDown alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Provision a static management IP address on the affected CMM. For information, seethe BTI7800 Series Software Configuration Guide.

Step 2 Check for alarms on the CMM.




scmNoNmConnTable 2-197 Alarm details Parameter DescriptionCode scmNoNmConnDescription/Cause No Network Management Connectivity on System Controller Module (SCM):

• In a dual-CMM system, neither SCM can connect to the management IPnetwork.

• In a single-CMM system, the SCM cannot connect to the management IPnetwork.




Alarm Clearing See “Clearing an scmNoNmConn alarm”.






Clearing an scmNoNmConn alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Provision a static management IP address on each affected CMM. For information, seethe BTI7800 Series Software Configuration Guide.

Step 2 Check for alarms on the CMM.




SDTable 2-199 Alarm details Parameter DescriptionCode sdDescription Signal Degrade: The local port is in a signal-degrade state because of a number of

errors in the received signal.




• Excessive signal attenuation has resulted in a high signal-to-noise ratio.



Alarm Clearing See “Clearing an SD alarm”.

Related Fault Hierarchy See:• “OTN interface fault hierarchy”
















Clearing an SD alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Reprieve statistics for the interface, and ensure that the optical power received and theoptical signal-to-noise ratio are within specification:show statistics current name:identifier



correctly connected to the port. Step 3 Check for alarms on the interface.




TIMTable 2-202 Alarm details Parameter DescriptionCode timDescription Trace Identifier Mismatch: The received trace identifier is different from the

expected trace identifier.



Possible Causes • 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.



Alarm Clearing See “Clearing a TIM alarm”.

Related Fault Hierarchy See:• “OTN interface fault hierarchy”
















Clearing a TIM alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 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 Messageshow interface name:identifier detail

Step 2 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.





TlossRxHtTable 2-205 Alarm details Parameter DescriptionCode tlossRxHtDescription/Cause 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).



Alarm Clearing See “Clearing a TlossRxHt alarm”.





Clearing a TlossRxHt alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Opticalpower loss in recv. direction counter:show statistics current line:identifier

Note For detailed AMP1 specifications, see the BTI7800 Series Hardware Overviewand Installation Guide.

Step 2 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.

Step 3 Check for alarms on the terminal amplifier line port:




TlossRxLtTable 2-207 Alarm/condition details Parameter DescriptionCode tlossRxLtDescription/Cause 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).



Alarm Clearing See “Clearing a TlossRxLt alarm”.





Clearing a TlossRxLt alarmNote Follow all applicable safety requirements as described in the BTI7800 Series


Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Opticalpower loss in recv. direction counter:show statistics current line:identifier

Note For detailed AMP1 specifications, see the BTI7800 Series Hardware Overviewand Installation Guide.

Step 2 Check the upstream fiber connections, and ensure that the fiber is intact, thoroughly

clean, and properly connected. Step 3 Check for alarms on the terminal amplifier line port:




UPGRDTable 2-209 Alarm details Parameter DescriptionCode upgrdDescription/Cause Upgrade in Progress: A system software upgrade is in progress.




Alarm Clearing This alarms clear when the system software upgrade is completed.














3.0 Fault masking

Fault masking occurs when a service-affecting alarm or condition raised against a monitoredentity suppresses the reporting of other alarms or conditions that are raised against the sameentity. A fault that masks another fault is in a higher position in the fault hierarchy for amonitored entity and indicates either a higher priority fault or a fault that more accuratelyidentifies the source of a problem. This means that when a fault that masks other faults iscleared, each masked fault will be reported if it was not cleared by the resolution of the maskingfault.The following sections list faults common to specific monitored entities and include fault-hierarchy 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”


C H A P T E R 3

Equipment fault hierarchyTable 3-1 Equipment fault hierarchy Alarms/Conditions Fault Hierarchy“EqptMiss”

“EqptMism”

“EqptComm”

“EqptFail”

“EqptDgrd”


Fault masking

Environment fault hierarchyTable 3-2 Environment fault hierarchy Alarms/Conditions Fault Hierarchy“Equipment faulthierarchy”

“EnvCurrentHighTh”

“EnvCurrentLowTh”

“EnvTempHighTh”

“EnvTempLowTh”

“EnvVoltHighTh”

“EnvVoltLowTh”


Fault masking

Common fault hierarchy - OTN and CBR portsTable 3-3 Common fault hierarchy - OTN and CBR ports Alarms/Conditions Fault Hierarchy“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 OC192interface fault hierarchy”

• “STM64, WAN PHY over STM64interface fault hierarchy”

“OptHighTh”

“OptLowTh”

“ModTempHighTh”

“ModTempLowTh”


Fault masking

OTN interface fault hierarchy

Note In the OTN fault hierarchy, a service-affecting fault raised against an OTN OTUinterface will mask all faults raised against each OTU ODU interface it contains.

Table 3-4 OTN interface fault hierarchy Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“LOS”

“LOF”

“SD”

“LOM”

“BDI”

“TIM”

“ODU-AIS”

“LCK”

“OCI”

“PyldMism”


Fault masking

Ethernet interface fault hierarchyTable 3-5 Ethernet interface fault summary Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“LOS”

“LoSync”

“HighBer”

“LF”

“RF”


Fault masking

OC192, WAN PHY over OC192 interface fault hierarchyTable 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”


Fault masking

STM64, WAN PHY over STM64 interface fault hierarchyTable 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”


Fault masking

DOL port fault hierarchyTable 3-8 DOL port fault summary Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“APSD”

“FECI”

“FEIM”

“LoSpecRx”

“APR”

“LoLightRx”


Fault masking

DOL OSC fault hierarchyTable 3-9 DOL OSC fault summary Alarms/Condition Fault Hierarchy“Equipment fault hierarchy”

“ContComS”

“LoLightRx”


Fault masking

DOL OMS fault hierarchyTable 3-10 DOL OMS alarms summary Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“OmsAis”

“LoLightRx”

“PosRxLow”


Fault masking

DOL OCH fault hierarchyTable 3-11 DOL OCH fault summary Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“OchOci”

“OchUeq”

“PosTxHigh”

“LoLightTx”

“DOL OMS fault hierarchy”

“PosTxLow”

“PosRxHigh”

“OchAis”

“LoLightRx”

“PosRxLow”


Fault masking

Terminal amplifier port fault hierarchyTable 3-12 Terminal amplifier port fault summary Alarms/Conditions Fault Hierarchy“Equipment fault hierarchy”

“APSD”

“ContComS”

“FECI”

“FEIM”

“ObrHt”

“TlossRxHt”

“TlossRxLt”

“APR”

“LoLightRx”


Fault masking


Fault masking

4.0 Alarm thresholds

This section covers the following topics:• “Environment thresholds”• “DOL thresholds”


C H A P T E R 4

Environment thresholds

This section provides information about the following environment-related alarm thresholds:• “Temperature thresholds - equipment and traffic modules”• “Temperature thresholds - MSA transceivers”• “Fan-speed thresholds”• “Output-current thresholds”• “Voltage thresholds”

Temperature thresholds - equipment and traffic modulesTable 4-1 and Table 4-2 provide information about available temperature sensors and the alarmthresholds for BTI7800 Series equipment and traffic modules.

Table 4-1 Temperature sensors - equipment and modules Sensor DescriptionAlarm Panel Temp Local ambient temperature

BIC Temp DIGI internal ASIC temperature

CMM Temp Local ambient temperature

DS75 Temp 1 Local ambient temperature

DS75 Temp 3 Local ambient temperature

DS75 Temp BIC Local ambient temperature

Exhaust Temp Cooling-module exhaust temperature

FAN Internal Temp Internal cooling-module temperature

FAN Temperature Local ambient temperature

Line Card Temp Local ambient temperature

OTN Framer Temp DIGI internal ASIC temperature

PEM <n> Temperature

where <n> is A1, A2, B1, or B2.

Local ambient temperature

PEM AC <n> Temperature


Local ambient temperature

Table 4-2 Temperature thresholds - equipment and modules Equipment/Module Sensor Low Threshold High ThresholdAMP1 DS75 Temp 1 – 72°C (161.6°F)

DS75 Temp 3 – –

Line Card Temp – –

BIC DS75 Temp BIC – 72°C (161.6°F)

BIC Temp – 105°C (221°F)


Alarm thresholds

Table 4-2 Temperature thresholds - equipment and modules (Continued) Equipment/Module Sensor Low Threshold High ThresholdChassis Alarm Panel Alarm Panel Temp – –

CMM CMM Temp – 90°C (194°F)

Cooling module Exhaust Temp – 75°C (167°F)

FAN Temperature – 75°C (167°F)

FAN Internal Temp – 75°C (167°F)

ILA DS75 Temp 1 – 85°C (185°F)

DS75 Temp 3 – –


DC PEM PEM <n> Temperature – 80°C (176°F)

AC PEM PEMAC <n> Temperature 55°C / 131°F 75°C (167°F)

ROADM2 DS75 Temp 1 – 85°C (185°F)

DS75 Temp 3 – –


UFM DS75 Temp 1 – –

DS75 Temp 3 – –

Line Card Temp – 85°C (185°F)

OTN Framer Temp Note Supported on UFM4 only.

– 105°C (221°F)

WPS4 DS75 Temp 3 – 85°C (185°F)


Temperature thresholds - MSA transceiversTable 4-3 provides alarm-related module temperature thresholds for the 100G Coherent MSAXCVR

Table 4-3 Temperature thresholds - 100G Coherent MSA XCVR module Low Threshold High Threshold Shutdown Threshold-5°C (23°F) 80°C (176°F) 90°C (194°F)


Alarm thresholds

Fan-speed thresholdsTable 4-4 provides information about available fan-speed sensors and the alarm thresholds forBTI7800 Series cooling modules.

Table 4-4 Fan-speed thresholds

Cooling ModuleSensor

Low ThresholdName Description

FAN2 Fan Tach <n>

where n is a value from 1 to 3.

Fan speed 1500 RPM

FAN3 Fan RPM Fan speed 1500 RPM

FAN5 Fan Tach <n>

where n is a value from 1 to 5.

Fan speed 2500 RPM

Output-current thresholdsTable 4-5 provides information about available output-current sensors and the alarm thresholdsfor BTI7800 Series equipment.

Table 4-5 Output-current sensors and thresholds Equipment Sensor Description Low Threshold High ThresholdAC PEM Iout PEMAC <n>

where <n> is A1, A2, B1, orB2

Output current (Vdc) 0.2 Vdc 60 Vdc

Voltage thresholdsTable 4-6 and Table 4-7 provide information about available voltage sensors and the alarmthresholds for BTI7800 Series equipment and traffic modules.

Table 4-6 Voltage sensors Sensor Description12V_MAIN 12V main voltage threshold sensor

2V5_CORE 2V5 core voltage threshold sensor

2V5_IO 2V5 I/O voltage threshold sensor

3V3_MAIN 3.3V main voltage threshold sensor

3V3_STBY 3.3V standby voltage threshold sensor

5V_MAIN 5V main voltage threshold sensor

ADC_1V2_GIGE ADC 1V2 GIGE voltage threshold senor

ADCS_5V ADCS 5V voltage threshold senor

ADCS_5V_USB ADCS 5V USB voltage threshold sensor


Alarm thresholds

Table 4-6 Voltage sensors (Continued) Sensor DescriptionVin PEM AC <n>


Input voltage

Vout PEM AC <n>


Output voltage

Table 4-7 Voltage thresholds Equipment/Module Sensor Low Threshold High ThresholdAMP1 12V_MAIN 9.60 14.40

2V5_CORE 2.00 3.00

2V5_IO 2.00 3.00

3V3_MAIN 2.64 3.96

3V3_STBY 2.64 3.96

5V_MAIN 4.00 6.00

ADC_1V2_GIGE 1.02 1.52

AC PEM Vin PEM AC <n> 90 255

Vout PEM AC <n> 40 60

UFM 12V_MAIN 9.60 14.40

2V5_CORE 2.25 2.75

2V5_IO 2.00 3.00

3V3_MAIN 2.64 3.96

3V3_STBY 2.64 3.96

5V_MAIN 4.00 6.00

ADC_1V2_GIGE 1.02 1.52

WPS4 12V_MAIN 10.86 13.26

3V3_MAIN 2.68 3.96

3V3_STBY 2.68 3.96

ADCS_5V 4.52 5.56

ADCS_5V_USB 4.52 5.56

ADC_1V2_GIGE 4.52 5.56


Alarm thresholds

DOL thresholds

This section covers the following topics:• “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”

DOL OSC power alarm thresholdsTable 4-8 ROADM2 OSC power alarm thresholds (all values in dBm)

Threshold Client Input Client OutputL1

OPT OPRHardware min. -22.0 -13.0 -22.2 -43.0

Loss of Light raise -21.0 N/A N/A -42.0

Loss of Light clear -20.0 N/A N/A -41.0

Hardware max. 0.0 0.0 7.0 6.0

Table 4-9 ILA OSC power alarm thresholds (all values in dBm)

Threshold Client Input Client OutputL1

OPT OPRHardware min. -22.0 -13.0 -22.2 -43.0

Loss of Light raise -21.0 N/A N/A -42.0

Loss of Light clear -20.0 N/A N/A -41.0

Hardware max. 0.0 0.0 7.0 6.0


Alarm thresholds

DOL OMS power alarm thresholdsTable 4-10 ROADM2 OMS power alarm thresholds (all values in dBm)

ThresholdClient Input Client

OutputL1

Add-Drop Pass-Thru OPT OPR OPR + PREHardware min. -18.0 -18.0 -8.5 -21.8 -29.0 -39.0

Loss of Lightraise

-17.0 -8.8 N/A N/A -28.0 -38.0

Loss of Lightclear

-16.0 -7.8 N/A N/A -27.0 -37.0

Power Out ofSpecificationLow raise

-14.0 -6.8 N/A N/A -26.0 -36.0

Power Out ofSpecificationLow clear

-13.5 -6.3 N/A N/A -25.5 -35.5

Hardwaremax.

23.0 23.0 23.0 23.3 14.4 3.4

Table 4-11 ILA OMS power alarm thresholds (all values in dBm)

ThresholdClient Input

Client OutputL1

Pass-Thru OPT OPR OPR + PREHardware min. -8.3 -4.3 -21.8 -29.0 -39.0

Loss of Lightraise

-7.3 N/A N/A -28.0 -38.0

Loss of Lightclear

-6.3 N/A N/A -27.0 -37.0


-4.3 N/A N/A -26.0 -36.0


-3.8 N/A N/A -25.5 -35.5

Hardware max. 25.1 25.1 23.3 -14.4 3.4


Alarm thresholds

DOL OCH power alarm thresholdsTable 4-12 ROADM2 50 GHz OCH optical-power alarm thresholds (all values in dBm)

Threshold Client Input Client Output PostAmp IN(Internal)

L1OPT OPR

Hardware min. -20.3 -14.5 -27.0 Alarm state setfrom PostAmp IN

Not supported

Loss of Lightraise

-16.6 -10.8 -23.3

Loss of Lightclear

-15.5 -9.7 -22.2


-13.6 -7.8 -20.3


-13.0 -7.2 -19.7

Power Out ofSpecificationHigh raise

5.1 5.1 -13.3

Power Out ofSpecificationHigh clear

5.7 5.7 -12.8

Hardware max. 17.2 17.2 -1.2


Alarm thresholds

DOL port power alarm thresholdsTable 4-13 ROADM2 PRE port-power alarm thresholds (all values in dBm)

ThresholdMainboard PRE Port CFP2 PRE Port

Input Output Input OutputHardware min. -29.0 -41.0 -40.0 -19.0

Loss of Light raise -21.0 N/A -40.0 N/A

Loss of Light clear -20.0 N/A -39.0 N/A

Power Out ofSpecification, Lowraise

-18.0 N/A -38.5 N/A

Power Out ofSpecification, Lowclear

-17.5 N/A -38.0 N/A

Hardware max. 15.6 4.6 4.0 19.0

Table 4-14 ILA PRE port-power alarm thresholds (all values in dBm)

ThresholdMainboard PRE Port CFP2 PRE Port

Input Output Input OutputHardware min. -29.0 -41.0 -40.0 -19.0

Loss of Light raise -21.0 N/A -40.0 N/A

Loss of Light clear -20.0 N/A -39.0 N/A

Power Out ofSpecification Lowraise

-18.0 N/A -38.5 N/A

Power Out ofSpecification Lowclear

-17.5 N/A -38.0 N/A

Hardware max. 15.6 4.6 4.0 19.0


Alarm thresholds

DOL Rx-loss alarm thresholdsTable 4-15 ROADM2 Rx-loss alarm thresholds (all values in dB)

Threshold Client (to Clientor MD03)

Line

with PRE without PRE forNDSF

without PRE forNZDSF

LoSpecRx raise 5.2 33.2 23.2 19.7

LoSpecRx clear 5.0 33.0 23.0 19.5

Table 4-16 ILA Rx-loss alarm thresholds (all values in dB)

Threshold Client (to Client)Line

with PRE without PRE forNDSF

without PRE forNZDSF

LoSpecRx raise 2.2 33.2 23.2 19.7

LoSpecRx clear 2.0 33.0 23.0 19.5


Alarm thresholds

Appendix A: BTI7800 Series equipment andmodules

Table A-1 and Table A-2 list the common equipment components and the management andtraffic modules supported on the BTI7800.

Table A- 1 BTI7800 Series common equipment components System Component PECBTI7814 BTI7814 Chassis BT8A78CH14

14-Slot Chassis Alarm Panel BT8A78CAP1

14-Slot Chassis Front Cooling Module BT8A78FAN3

14-Slot Chassis DC Power Entry Module BT8A78PEM3-DC

2900W (53.5V) AC Rectifier Module BT8A78ACM1

BTI7802 BTI7802 Chassis BT8A78CH2-I02

2-Slot Chassis Alarm Panel BT8A78CAP2

2-Slot Chassis Cooling Module BT8A78FAN2

1/2-Slot Chassis DC Power Entry Module BT8A78PEM1-DC

1/2-Slot Chassis AC Power Entry Module BT8A78PEM1-AC

Chassis Management Module (CMM) BT8A78CMM1

BTI7801 BTI7801 Chassis BT8A78CH1

Ethernet and Serial Link (ESL) module BT8A78ESL1

1-Slot Chassis Front Cooling Module BT8A78FAN5

1/2-Slot Chassis DC Power Entry Module BT8A78PEM1-DC

1/2-Slot Chassis AC Power Entry Module BT8A78PEM1-AC

Chassis Management Module (CMM) BT8A78CMM1

Product Release 2.1.1 STANDARD A-1

A P P E N D I X A

Table A- 2 BTI7800 Series management and traffic modules Module Description PECManagement modulesChassis Management Module 1 (CMM1) Provides management and control of the

system.BT8A78CMM1

Service modulesUniversal Forwarding Module Lite (UFM3) Supports two BICs. BT8A78UFM3

Universal Forwarding Module Lite withIntegrated 100G Coherent MSA XCVR (UFM4)

Contains one 100G Coherent MSAXCVR and supports one BTI InterfaceCard (BIC).

BT8A78UFM4

96-Channel Amplifier (AMP1) Provides DWDM composite signalamplification in point-to-point applications.

BT8A78AMP1

Wavelength Protection Switch (WPS4) Provides revertive or non-revertivewavelength protection switching.

BT8A78WPS4

2-Port Reconfigurable Optical Add/DropMultiplexer (ROADM2)

2-degree ROADM module. BT8A78RDM2

Inline Amplifier (ILA) Provides unidirectional DWDM C-bandamplification and tilt control at transitsites.

BT8A78AMPL

BIC modules12x SFP+ BTI Interface Card (12x SFP+ BIC) For up to 12 SFP+ transceivers. BT8A78SFP12G

1x CFP BTI Interface Card (1x CFP BIC) For 1 CFP transceiver. BT8A78CFP1G

CFP2 modulesPluggable Pre-Amplifier (PRE) Pre-amplifier module that plugs into the

PRE slot of a host ROADM or ILAmodule.

BT8A78AMPP

Passive modules96-Channel Fixed Mux/Demux (FMD96) Provides local fixed grid access to all 96

wavelengths in the DWDM 50GHzchannel plan.

BT8A78MD03

A-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Appendix A: BTI7800 Series equipment and modules

Appendix B: BTI7800 Series transceivers

Table B-1 lists transceivers supported on the BTI7800 Series. For additional information, see thefollowing topics:• B.1, “BTI7800 SFP+ Transceiver Optical Specifications”• B.2, “BTI7800 CFP Transceiver Optical Specifications”

Table B- 1 Transceivers Type Fiber Type Bit Rate PEC IntroducedSFP+ 850nm 200m Dual-Rate 10.3and 10.5Gbps

Multimode 10.3 and 10.5 Gbps BP3AD6SS Release 1.1

SFP+ 1310nm 10km Multi-Rate 9.9to 11.1Gbps

Single-mode 9.9 to 11.1 Gbps BP3AM6MS Release 1.1

SFP+ DWDM Fixed 80km Multi-Rate 9.9 to 11.1Gbps

Single-mode 9.9 to 11.1 Gbps BP3AM6DL-xx Release 1.1

SFP+ DWDM Tunable 80km Multi-Rate 9.9 to 11.1Gbps

Single-mode 9.9 to 11.1 Gbps BP3AM6TL Release 1.1

CFP 100GBASE-SR10 100m Multiple single-mode fibers in asingle cable

100 Gbps BP3AMASS Release 1.1

CFP 100GBASE-LR4 10km Single-mode 100 Gbps BP3AMDLI Release 1.1

100G Coherent CFP Single-mode 100 Gbps BP3AMCTL

Installation rulesexist for thistransceiver.

Release 1.5

100G Coherent MSA XCVR Single-mode 100 Gbps Integrated on theUniversalForwardingModule Lite withIntegrated 100G

Release 1.1

Product Release 2.1.1 STANDARD B-1

A P P E N D I X B

Table B- 1 Transceivers Type Fiber Type Bit Rate PEC Introduced

Coherent MSAXCVR(BT8A78UFM4 )

B-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01


BTI7800 SFP+ Transceiver Optical SpecificationsTable B- 2 SFP+ 850nm 200m Dual-Rate 10.3 and 10.5Gbps (BP3AD6SS) Parameter Min Typ Max UnitsBit Rate 10.3125 - 10.52 Gb/s

TransmitterTX operating wavelength 840 850 860 nm

Average operating power -7.3 - -1 dBm

Spectral width (rms) - - 0.45 nm

Extinction ratio 3 - - dB

Optical return loss tolerance - - 12 dB

ReceiverReceiver operating wavelength 840 - 860 nm

Stressed receiver sensitivity(BER = 1e-12)

- - -7.5 dBm

Receiver overload 0.5 - - dBm

Optical path penalty - - 3.9 dB

Reflectance - - -12 dB

OtherReach (50m MMF, 2000MZHzkm)

- - 300 m

Connector/Latch type LC/Bail

Power Consumption (40°ambient)1

Typical: 0.8W

Maximum: 1W

Compliance IEEE 802.3, SFP+ MSA1Before using for planning or implementation purposes, contact Juniper Networks Support to confirm the power consumption values.

Table B- 3 SFP+ 1310nm 10km Multi-Rate 9.9 to 11.1Gbps (BP3AM6MS) Parameter Min Typ Max UnitsBit Rate 9.953 - 11.0957 Gb/s

TransmitterTransmitter operating wavelength 1260 1310 1360 nm

Average operating power -8.2 - 0.5 dBm

Spectral width (-20dB) - - 1 nm

Side mode suppression ratio 30 - - dB

Extinction ratio 3.5 - - dB

Optical return loss tolerance - - -12 dB




Table B- 3 SFP+ 1310nm 10km Multi-Rate 9.9 to 11.1Gbps (BP3AM6MS) (Continued) Parameter Min Typ Max UnitsStressed receiver sensitivity(BER = 1e-12)

- - -10.3 dBm

Receiver overload 0.5 - - dBm

Optical path penalty(@ 6.6 ps/nm) - - 3.2 dB


OtherReach - - 10 km

Connector/Latch type LC/Bail


Typical: 0.8W

Maximum: 1W

Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, SFP+ MSA1Before using for planning or implementation purposes, contact Juniper Networks Support to confirm the power consumption values.

Table B- 4 SFP+ DWDM Fixed 80km Multi-Rate 9.9 to 11.1Gbps (BP3AM6DL-xx xx=[01,40]) Parameter Min Typ Max UnitsBit Rate 9.953 - 11.0957 Gb/s

TransmitterTransmitter operating wavelength 192.1 - 196 THz

Average operating power -1 - 3 dBm

Spectral width (-20dB) - - 0.3 nm





Receiver overload 3 - - dBm


OtherConnector/Latch type LC/Bail


TBD




Table B- 5 Receiver Transmission Optical Performance Specifications: BP3AM6DL-xx xx=[01,40] Bit Rate (Gbps) Dispersion (ps/nm) OSNR (dB) Receiver

Sensitivity(Min to Max)

BER

9.95/10.3 -400 ≥30 -24 to -7 1e-12

≥27 -18 to -7

0 ≥30 -23 to -7

≥25 -18 to -7

1200 ≥30 -22 to -7

≥27 -18 to -7

1600 ≥30 -22 to -7

≥28 -18 to -7

10.5 -400 ≥30 -20 to -7 1e-12

≥28 -18 to -7

0 ≥30 -23 to -7

≥26 -18 to -7

1200 ≥30 -22 to -7

≥28 -18 to -7

1600 ≥30 -18 to -7

10.7 (FEC G.709) -400 ≥30 -24 to -7 1e-4

≥19 -18 to -7

0 ≥30 -23 to -7

≥19 -18 to -7

1200 ≥30 -22 to -7

≥28 -18 to -7

1600 ≥30 -24 to -7

≥19 -18 to -7

10.7 (EFEC) -400 ≥30 -25 to -7 1e-3

≥17 -18 to -7

0 ≥30 -27 to -7

≥16 -18 to -7

1200 ≥30 -26 to -7

≥16 -18 to -7

1600 ≥30 -25 to -7

≥17 -18 to -7

11.1 (FEC G.709) -400 ≥30 -24 to -7 1e-4

≥19 -18 to -7

0 ≥30 -26 to -7

≥18 -18 to -7

1200 ≥30 -25 to -7



Table B- 5 Receiver Transmission Optical Performance Specifications: BP3AM6DL-xx xx=[01,40] (Continued) Bit Rate (Gbps) Dispersion (ps/nm) OSNR (dB) Receiver


BER

≥18 -18 to -7

1600 ≥30 -24 to -7

≥19 -18 to -7

11.1 (EFEC) -400 ≥30 -25 to -7 1e-3

≥17 -18 to -7

-400 to 0 ≥30 -27 to -7

≥16 -18 to -7

1200 ≥30 -25 to -7

≥16 -18 to -7

1600 ≥30 -25 to -7

≥17 -18 to -7

Table B- 6 SFP+ DWDM Tunable 80km Multi-Rate 9.9 to 11.1Gbps (BP3AM6TL) Parameter Min Typ Max UnitsBit Rate 9.953 - 11.0957 Gb/s

TransmitterTX operating wavelength 191.35 - 196.1 THz

Average operating power -1 - 3 dBm

Spectral width (-20dB) - - 0.3 nm




ReceiverRx operating wavelength 1260 - 1600 nm

Rx overload 3 - - dBm


OtherConnector/Latch type LC/Bail


Typical: 1.7W

Maximum: 2W




Table B- 7 Receiver Transmission Optical Performance Specifications: BP3AM6TL Bit Rate (Gbps) Dispersion (ps/nm) OSNR (dB) Receiver


BER

9.95/10.3/10.5 0 ≥30 -24 to -7 1e-12

≥25 -19 to -7

1600 ≥30 -22 to -7

≥26 -19 to -7

10.7 (FEC G.709) 0 ≥30 -26 to -7 1e-4

≥16.5 -24 to -7

1600 ≥30 -24 to -7

≥18.5 -24 to -7

10.7 (EFEC G.709) 0 ≥30 -27 to -7 1e-3

≥14.5 -24to -7

1600 ≥30 -25 to -7

≥16.5 -24 to -7



BTI7800 CFP Transceiver Optical SpecificationsTable B- 8 CFP 100GBASE-SR10 100m: BP3AMASS Parameter Min Typ Max UnitsTransmitterSignaling speed per lane (100GE) - 10.3125 - Gb/s

Signaling speed per lane (OTU4) - 11.1809 - Gb/s

TX operating wavelength 840 - 860 nm

Average launch power per Lane -7.6 - 2.4 dBm

Spectral width (RMS) - - 0.65 nm

Extinction ratio 3 - - dB



Stressed receiver sensitivity perlane

- - -5.4 dBm

Rx overload 3.4 - - dBm

Optical path penalty - - 3.5 dB

OtherPower Consumption (40° ambient)

Before using for planning orimplementation purposes, contactJuniper Networks Support toconfirm the power consumptionvalues.

Typical: 10W

Maximum: 12W

Compliance IEEE 802.3, CFP MSA

Table B- 9 CFP 100GBASE-LR4 10km: BP3AMDLI Parameter Min Typ Max UnitsTransmitterSignaling speed per lane (100GE) - 25.78 - Gb/s

Signaling speed per lane (OTU4) - 27.95 - Gb/s

Lane wavelengths 1294.53 1295.56 1296.59 nm

1299.02 1300.05 1301.09 nm

1303.54 1304.58 1305.63 nm

1308.09 1309.14 1310.19 nm

Average launch power per Lane -4.3 - 4.5 dBm

Total average launch power 0 - 10.5 dBm

Side mode suppression ratio(SMSR)

30 - - dB

Extinction ratio (OTU4) 7 - - dB



Table B- 9 CFP 100GBASE-LR4 10km: BP3AMDLI (Continued) Parameter Min Typ Max UnitsOptical return loss tolerance - - 20 dB

ReceiverStressed Rx sensitivity per lane - - -6.8 dBm

Receiver overload - - 5.5 dBm




Typical: 20W

Maximum: 24W

Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, CFP MSA

Table B- 10 100G Coherent CFP: BP3AMCTL Parameter Min Typ Max UnitsTransmitterTransmitter frequency range 191.35 - 196.10 THz

Laser frequency stability -1.8 - 1.8 GHz

Output power range -15 - 1 dBm

Transmitter OSNR (in-band) 27 - - dB

Optical return loss tolerance 27 - - dB

ReceiverReceiver frequency range 191.35 - 196.10 THz

Input power range -18 (-21dBm inunamplifiedapplications)

- 0 dBm

OSNR tolerance 17.1 - - dB

PMD tolerance - - 15 ps

PDL tolerance - - 3 dB

Dispersion tolerance -22000 - 22000 ps/nm

Optical return loss from receiver 27 - - dB



Typical: 25W

Maximum: 32W

Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, CFP MSA



Table B- 11 100G Coherent MSA XCVR on UFM4 Parameter Min Typ Max UnitsTransmitterTransmitter frequency range 191.35 - 196.10 THz

Laser frequency stability -1.8 - 1.8 GHz

Output power range -5 - 1 dBm

Transmitter OSNR (in-band) 40 - - dB

Optical return loss tolerance 27 - - dB

ReceiverReceiver frequency range 191.35 - 196.10 THz

Input power range -18 (-22dBm inunamplified

systems)

- -2 dBm

OSNR tolerance 13.7 - - dB

PMD tolerance - - 30 ps

PDL tolerance - - 3 dB

Dispersion tolerance -50000 - 50000 ps/nm

Optical return loss from receiver 27 - - dB

OtherCompliance IEEE 802.3, Telcordia GR-253, ITU-T G.709



Appendix C: BTI7800 Series module and BICLED behavior

This section provides information about LED behavior on CMMs (Table C-1), service modules(Table C-2), BICs (Table C-3), and BIC ports (Table C-4).

Table C- 1 CMM LEDs LEDs Color DescriptionIdentify Amber Not used.

Active Green The CMM is operationally up.

Fail Red The CMM is operationally down or the CMM is not recognized.

Hot Swap Blue The CMM does not match the provisioned CMM.

Link (right) Green The link is up.

Activity (left) Green The LED flickers to indicate activity on the link.

Table C- 2 Service module LED behavior Name Description State State DescriptionIdentify

(AMBER)

The Identify LEDindicates whether theCMM has identified andacknowledged thenewly-inserted module.

OFF The CMM has identified and acknowledged themodule.

The CMM can only acknowledge the module if themodule is administratively up. A newly-insertedmodule is administratively up if either of thefollowing is true:

• The module has been pre-provisioned andconfigured to be administratively up.

• Auto-provisioning is enabled. If auto-provisioning is enabled and if the CMM is able

Product Release 2.1.1 STANDARD C-1

A P P E N D I X C

Table C- 2 Service module LED behavior (Continued) Name Description State State Description

to identify the module, the module isautomatically provisioned and its administrativestatus is set to up.

ON The CMM has failed to identify or acknowledge themodule.

BLINKING The CMM is attempting to identify andacknowledge the module.

Active

(GREEN)

The Active LED reflectsthe operational status ofthe module.

OFF The operational status of the module is down.

ON The operational status of the module is up.

Fail

(RED)

The Fail LED reflectsthe operational status ofthe module.

OFF The operational status of the module is up.

ON The operational status of the module is down.

H/S

(BLUE)

The Hot Swap H/S LEDindicates whether themodule can be removedfrom the chassis.

OFF The administrative status of the module is up, andthe actual module matches the provisioned module.

The module should not be removed from thechassis in this state.

ON The administrative status of the module is down, orthe actual module does not match the provisionedmodule.

The module can be removed from the chassis inthis state.

BLINKING This is a transient state that occurs when pluggingin a module, or when changing its administrativestatus.

The module should not be removed from thechassis in this state.

Table C- 3 BIC LEDs LEDs Color DescriptionActive Green The module is operating normally.

Fail Red The module has failed.

H/S (Hot Swap) Blue ON: The module is in a quiescent state, and can be removed from the slotafter a minimum of 5 seconds in this state.

BLINKING: The module is being placed into a quiescent state. It cannot beremoved from the slot.

OFF: The module is operating normally. It cannot be removed from the slot.

Table C- 4 BIC port LEDs LEDs Color DescriptionFail Red The port has failed.

Fault Amber A fault exists on the port.

C-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Appendix C: BTI7800 Series module and BIC LED behavior

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, CA 94089 USA

tel: 408-745-2000

www.juniper.net

Part Number:Document Version:Published:Type:

BT8A78PD0021 01 November 2016 STANDARD

product release 2.1.1

Date post:	10-Mar-2018
Category:	Documents
Upload:	trannhan
View:	239 times
Download:	2 times

BTI7800 Series Alarm and Troubleshooting Guide BTI7800 Series Alarm and Troubleshooting Guide –...

Documents