BTI7800 Alarm and Troubleshooting Guide 2.1

BTI7800 Series Alarm and Troubleshooting Guide
Juniper Networks, Inc. tel: 408-745-2000 www.juniper.net

1133 Innovation Way
Sunnyvale, CA 94089 USA

Part Number: BT8A78PD0021 product release 2.1.1
Document Version: 01
Published: November 2016
Type: STANDARD

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

Preface

viii
1.0

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

Alarms and conditions 2-1
AirFilterAbsence ................................................................................................................................................................................ 2-8
2.1.1 Clearing an AirFilterAbsence alarm .................................................................................................................................... 2-8
AIS–L ................................................................................................................................................................................................. 2-9
2.2.1 Clearing an AIS-L condition ................................................................................................................................................ 2-9
APR ................................................................................................................................................................................................. 2-10
2.3.1 Clearing an APR alarm (PRE port) ................................................................................................................................... 2-10
2.3.2 Clearing an APR alarm (terminal amplifier port) ............................................................................................................... 2-11
APSD ............................................................................................................................................................................................... 2-12
2.4.1 Clearing an APSD alarm (DOL port) ................................................................................................................................ 2-13
2.4.2 Clearing an APSD alarm (terminal amplifier line port) ...................................................................................................... 2-13
BDI ................................................................................................................................................................................................... 2-14
2.5.1 Clearing a BDI condition ................................................................................................................................................... 2-14
ContComS ....................................................................................................................................................................................... 2-15
2.6.1 Clearing a ContComS alarm ............................................................................................................................................. 2-16
DiskHighUsage ................................................................................................................................................................................ 2-17
EnvCurrentHighTh ........................................................................................................................................................................... 2-18
2.8.1 Clearing an EnvCurrentHighTh alarm .............................................................................................................................. 2-18
EnvCurrentLowTh ............................................................................................................................................................................ 2-19
2.9.1 Clearing an EnvCurrentLowTh alarm ............................................................................................................................... 2-19
EnvTempHighTh .............................................................................................................................................................................. 2-20
Product Release 2.1.1 STANDARD iii

Contents

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

EnvTempLowTh ............................................................................................................................................................................... 2-22
2.11.1 Clearing an EnvTempLowTh condition ........................................................................................................................... 2-23
EnvVoltHighTh ................................................................................................................................................................................. 2-24
2.12.1 Clearing an EnvVoltHighTh alarm .................................................................................................................................. 2-25
EnvVoltLowTh .................................................................................................................................................................................. 2-26
2.13.1 Clearing an EnvVoltLowTh alarm ................................................................................................................................... 2-27
EqptComm ....................................................................................................................................................................................... 2-28
2.14.1 Clearing an EqptComm alarm ........................................................................................................................................ 2-28
EqptDgrd .......................................................................................................................................................................................... 2-29
2.15.1 Clearing an EqptDgrd alarm ........................................................................................................................................... 2-29
EqptFail ............................................................................................................................................................................................ 2-30
2.16.1 Clearing an EqptFail alarm ............................................................................................................................................. 2-31
EqptMism ......................................................................................................................................................................................... 2-32
2.17.1 Clearing an EqptMism alarm .......................................................................................................................................... 2-33
EqptMiss .......................................................................................................................................................................................... 2-34
2.18.1 Clearing an EqptMiss alarm ........................................................................................................................................... 2-35
FanSpeedLowTh ............................................................................................................................................................................. 2-36
2.19.1 Clearing a FanSpeedLowTh alarm ................................................................................................................................. 2-36
FECI ................................................................................................................................................................................................. 2-38
2.20.1 Clearing a FECI alarm (DOL port) .................................................................................................................................. 2-39
2.20.2 Clearing a FECI alarm (terminal amplifier OSC) ............................................................................................................ 2-39
FEIM ................................................................................................................................................................................................ 2-40
2.21.1 Clearing a FEIM alarm (DOL port) .................................................................................................................................. 2-41
2.21.2 Clearing a FEIM alarm (terminal amplifier OSC) ............................................................................................................ 2-41
FirmUpgrdInProg ............................................................................................................................................................................. 2-42
FirmUpgrdFail .................................................................................................................................................................................. 2-43
2.23.1 Clearing a FirmUpgrdFail alarm ..................................................................................................................................... 2-43
FirmUpgrdReqd ............................................................................................................................................................................... 2-44
Forced .............................................................................................................................................................................................. 2-45
HighBer ............................................................................................................................................................................................ 2-46
2.26.1 Clearing a HighBer alarm ............................................................................................................................................... 2-47
InvUnknown ..................................................................................................................................................................................... 2-48
2.27.1 Clearing an InvUnknown alarm ...................................................................................................................................... 2-48
LaserFail .......................................................................................................................................................................................... 2-49
2.28.1 Clearing a LaserFail alarm ............................................................................................................................................. 2-50
LaserTempHighTh ........................................................................................................................................................................... 2-51
2.29.1 Clearing a LaserTempHighTh alarm .............................................................................................................................. 2-52
LaserTempLowTh ............................................................................................................................................................................ 2-53
2.30.1 Clearing a LaserTempLowTh alarm ............................................................................................................................... 2-54
LCK .................................................................................................................................................................................................. 2-55
2.31.1 Clearing an LCK alarm ................................................................................................................................................... 2-56
LF ..................................................................................................................................................................................................... 2-57
2.32.1 Clearing an LF condition ................................................................................................................................................ 2-57
Lockout ............................................................................................................................................................................................ 2-58
LOF .................................................................................................................................................................................................. 2-59
2.34.1 Clearing an LOF alarm ................................................................................................................................................... 2-60
iv BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Contents

LoLightRx ......................................................................................................................................................................................... 2-61

2.35.1 Clearing a LoLightRx alarm (DOL entity) ........................................................................................................................ 2-63
2.35.2 Clearing a LoLightRx alarm (wavelength protection port) .............................................................................................. 2-64
2.35.3 Clearing a LoLightRx alarm (terminal amplifier port) ...................................................................................................... 2-64
LoLightTx ......................................................................................................................................................................................... 2-65
2.36.1 Clearing a LoLightTx alarm ............................................................................................................................................ 2-65
LOM ................................................................................................................................................................................................. 2-66
2.37.1 Clearing an LOM alarm .................................................................................................................................................. 2-66
LOS .................................................................................................................................................................................................. 2-67
2.38.1 Clearing an LOS alarm ................................................................................................................................................... 2-68
LoSpecRx ........................................................................................................................................................................................ 2-69
2.39.1 Clearing a LoSpecRx alarm ............................................................................................................................................ 2-69
LoSync ............................................................................................................................................................................................. 2-70
2.40.1 Clearing a LoSync alarm ................................................................................................................................................ 2-71
LPBK ................................................................................................................................................................................................ 2-72
MemHighUsage ............................................................................................................................................................................... 2-73
ModTempHighTh ............................................................................................................................................................................. 2-74
2.43.1 Clearing a ModTempHighTh alarm ................................................................................................................................ 2-75
ModTempLowTh .............................................................................................................................................................................. 2-76
2.44.1 Clearing a ModTempLowTh alarm ................................................................................................................................. 2-76
ModTempShutdown ......................................................................................................................................................................... 2-77
2.45.1 Clearing ModTempShutdown alarm ............................................................................................................................... 2-78
MS-AIS ............................................................................................................................................................................................ 2-79
2.46.1 Clearing an MS-AIS condition ........................................................................................................................................ 2-79
MS-RDI ............................................................................................................................................................................................ 2-80
2.47.1 Clearing an MS-RDI condition ........................................................................................................................................ 2-80
NonCoLocatedController ................................................................................................................................................................. 2-81
2.48.1 Clearing a NonCoLocatedController alarm ..................................................................................................................... 2-81
ObrHt ............................................................................................................................................................................................... 2-82
2.49.1 Clearing an ObrHt alarm ................................................................................................................................................. 2-82
OchAis ............................................................................................................................................................................................. 2-84
2.50.1 Clearing an OchAis condition ......................................................................................................................................... 2-84
OchOci ............................................................................................................................................................................................. 2-85
2.51.1 Clearing an OchOci condition ......................................................................................................................................... 2-85
OchUeq ............................................................................................................................................................................................ 2-86
2.52.1 Clearing an OchUeq alarm ............................................................................................................................................. 2-86
OCI .................................................................................................................................................................................................. 2-87
2.53.1 Clearing an OCI alarm .................................................................................................................................................... 2-87
ODU-AIS .......................................................................................................................................................................................... 2-88
2.54.1 Clearing an ODU-AIS condition ...................................................................................................................................... 2-89
OmsAis ............................................................................................................................................................................................ 2-90
2.55.1 Clearing an OmsAis condition ........................................................................................................................................ 2-90
OneCableDisconnected ................................................................................................................................................................... 2-91
2.56.1 Clearing a OneCableDisconnected alarm ...................................................................................................................... 2-91
OprHighTh ....................................................................................................................................................................................... 2-92
2.57.1 Clearing an OprHighTh alarm ......................................................................................................................................... 2-93
OprLowTh ........................................................................................................................................................................................ 2-94
Product Release 2.1.1 STANDARD v

Contents

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

OptHighTh ....................................................................................................................................................................................... 2-96
2.59.1 Clearing an OptHighTh alarm ......................................................................................................................................... 2-97
OptLowTh ........................................................................................................................................................................................ 2-98
2.60.1 Clearing an OptLowTh alarm .......................................................................................................................................... 2-99
OTU-AIS ........................................................................................................................................................................................ 2-100
PartitionFault .................................................................................................................................................................................. 2-101
2.62.1 Clearing a ParitionFault alarm ...................................................................................................................................... 2-101
PosRxHigh ..................................................................................................................................................................................... 2-102
2.63.1 Clearing a PosRxHigh alarm ........................................................................................................................................ 2-102
PosRxLow ...................................................................................................................................................................................... 2-103
2.64.1 Clearing a PosRxLow alarm ......................................................................................................................................... 2-104
PosTxHigh ..................................................................................................................................................................................... 2-105
2.65.1 Clearing a PosTxHigh alarm ......................................................................................................................................... 2-105
PosTxLow ...................................................................................................................................................................................... 2-106
2.66.1 Clearing a PosTxLow alarm ......................................................................................................................................... 2-106
PowerAbsent ................................................................................................................................................................................. 2-107
2.67.1 Clearing a PowerAbsent alarm ..................................................................................................................................... 2-107
PRBS ............................................................................................................................................................................................. 2-108
PyldMism ....................................................................................................................................................................................... 2-109
2.69.1 Clearing a PyldMism alarm ........................................................................................................................................... 2-110
RDI-L ............................................................................................................................................................................................. 2-111
2.70.1 Clearing an RDI-L condition ......................................................................................................................................... 2-111
RF .................................................................................................................................................................................................. 2-112
2.71.1 Clearing an RF condition .............................................................................................................................................. 2-112
ScmNmiDown ................................................................................................................................................................................ 2-113
2.72.1 Clearing an ScmNmiDown alarm ................................................................................................................................ 2-113
scmNoNmConn ............................................................................................................................................................................. 2-114
2.73.1 Clearing an scmNoNmConn alarm ............................................................................................................................... 2-114
SD .................................................................................................................................................................................................. 2-115
2.74.1 Clearing an SD alarm ................................................................................................................................................... 2-116
TIM ................................................................................................................................................................................................. 2-117
2.75.1 Clearing a TIM alarm .................................................................................................................................................... 2-118
TlossRxHt ...................................................................................................................................................................................... 2-119
2.76.1 Clearing a TlossRxHt alarm .......................................................................................................................................... 2-119
TlossRxLt ....................................................................................................................................................................................... 2-120
2.77.1 Clearing a TlossRxLt alarm .......................................................................................................................................... 2-120
UPGRD .......................................................................................................................................................................................... 2-121
3.0

Fault masking 3-1
Equipment fault hierarchy .................................................................................................................................................................. 3-2
Environment fault hierarchy ............................................................................................................................................................... 3-3
Common fault hierarchy - OTN and CBR ports ................................................................................................................................. 3-4
OTN interface fault hierarchy ............................................................................................................................................................. 3-5
Ethernet interface fault hierarchy ....................................................................................................................................................... 3-6
OC192, WAN PHY over OC192 interface fault hierarchy .................................................................................................................. 3-7
STM64, 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-9

DOL OSC fault hierarchy ................................................................................................................................................................. 3-10
DOL OMS fault hierarchy ................................................................................................................................................................. 3-11
DOL OCH fault hierarchy ................................................................................................................................................................. 3-12
Terminal 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-2
4.1.2 Temperature thresholds - MSA transceivers ...................................................................................................................... 4-3
4.1.3 Fan-speed thresholds ......................................................................................................................................................... 4-4
4.1.4 Output-current thresholds ................................................................................................................................................... 4-4
4.1.5 Voltage thresholds .............................................................................................................................................................. 4-4
DOL thresholds .................................................................................................................................................................................. 4-6
4.2.1 DOL OSC power alarm thresholds ..................................................................................................................................... 4-6
4.2.2 DOL OMS power alarm thresholds ..................................................................................................................................... 4-7
4.2.3 DOL OCH power alarm thresholds ..................................................................................................................................... 4-8
4.2.4 DOL port power alarm thresholds ....................................................................................................................................... 4-9
4.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

Preface

Preface

This preface explains who should read this guide, related documentation, documentation
conventions, how to obtain documentation, and how to obtain technical support.
Audience
This guide is primarily intended for site planners, planning engineers, and network operation
center (NOC) staff.
BTI7800 Series Documentation

The following guides are provided in the BTI7800 documentation suite.
• BTI7800 Series Command Line Reference Guide
• BTI7800 Series Hardware Overview and Installation Guide

• BTI7800 Series Software Configuration Guide
• BTI7800 Series Alarm and Troubleshooting Guide
• BTI7800 Series Release Notes
Obtaining documentation
To obtain the most current version of all Juniper Networks technical documentation, see the
product documentation page on the Juniper Networks website at 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 matter
experts. These books go beyond the technical documentation to explore the nuances of network
architecture, deployment, and administration. The current list can be viewed at http://
www.juniper.net/books.
Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support
contract, or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
• JTAC policies - For a complete understanding of our JTAC procedures and policies, review
the JTAC User Guide located at 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

• JTAC hours of operation - The JTAC centers have resources available 24 hours a day, 7 days
a week, 365 days a year.
Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service
portal called the Customer Support Center (CSC) that provides you with the following features:
• Find CSC offerings: 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 (or
is intended for use with) Juniper Networks software. Use of such software is subject to the terms
and conditions of the End User License Agreement (EULA) posted at http://www.juniper.net/
cm/. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
Documentation conventions
Convention Description
Note 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

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

Preface

Caution USE OF CONTROLS OR ADJUSTMENTS OR PERFORMANCE OF

PROCEDURES OTHER THAN THOSE SPECIFIED IN THIS GUIDE MAY
RESULT IN HAZARDOUS RADIATION EXPOSURE.
Product Release 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 reproduction
in whole or in part is strictly prohibited. Juniper, Juniper Networks, BTI, BTI SYSTEMS, packetVX, proNX, and The
Network You Need are trademarks or registered trademarks of Juniper Networks, Inc. and/or its subsidiaries in the
U.S. and/or other countries.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right
to change, modify, transfer, or otherwise revise this publication without notice.
Copyright © 2003-2016 BTI Systems, Inc. All rights reserved.
xii BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

C H A P T E R 1
1.0 Fault monitoring on the BTI7800

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

Fault monitoring on the BTI7800

Fault reporting
When reporting is enabled for a fault that becomes active on a managed entity, the reporting
behavior of that fault depends on the administrative status (enabled or disabled) of the entity, as
described in Table 1-1.
Table 1-1 Entity administrative status and fault reporting

Status Fault-Reporting Behavior
Enabled When a fault with critical, major, or minor severity (see Table 1-2) becomes active, it is reported
with an alarm notification. When the fault is no longer active, a condition-clear alarm is generated.
Polling retrieves active faults on enabled entities. The CLI command show conditions
retrieves a list of all active faults (both alarms and conditions), and the command show
alarms retrieves a list of all active alarms.
Disabled When a fault with critical, major, or minor severity either becomes active or is cleared, no
reporting is provided. Polling results retrieved with either show conditions or show
alarms do not include any active faults (alarms or conditions) on disabled entities.
To retrieve alarms and conditions, use the show alarms and show conditions CLI commands,
respectively. For both alarms and conditions, the information retrieved shows the name of the
entity affected, the fault code, the time the fault was reported, the fault severity, the impact on
service, and the name of the fault in plain language.
Figure 1-1 Alarm information retrieved using the CLI
Fault severity
Each fault is associated with one of the default severity types listed in the following table.
Table 1-2 Fault severities

Severity Description
Critical 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


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


Maintenance signaling
When normal traffic cannot be transmitted from a port, for example, when a received signal is in
a failed state or when a port is administratively disabled and traffic is disrupted, the BTI7800
Series will usually forward a maintenance signal from the transmit port to indicate to the
downstream node that a local outage exists. For all interface protocols, the default maintenance
signal (Table 1-3) enables the receiving node to conclude that the link to the adjacent upstream
node is intact.
Table 1-3 Default maintenance signals - interface protocols

Protocol Default Maintenance Signal
OTN OTU “ODU-AIS”
OTN ODU “ODU-AIS”
Ethernet “LF”
OC192, WAN PHY over OC192 “AIS–L”
STM64, WAN PHY over STM64 “MS-AIS”

C H A P T E R 2
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 interfaces Not alarmed Yes (true)
SONET)
“APR” (Automatic Power Reduction) • DOL ports Critical Yes (true)
• Terminal amplifier
client ports
DCM ports
“APSD” (Automatic Power Shutdown) • DOL ports Critical Yes (true)
line ports
“BDI” (Backward Defect Indication, OTN) OTN OTU interfaces Not alarmed No (false)
“ContComS” (Control Communications • DOL optical service Major Yes (true)
Failure, Span Section) channels

Optical Supervisory
Channels

Alarms and conditions

Table 2-1 BTI7800 alarms and conditions (Continued)

“DiskHighUsage” (Disk High Usage) • Management Major No (false)
modules
• Traffic modules
“EnvCurrentHighTh” (Current Above High AC PEM Major Yes (true)
Temperature)
“EnvCurrentLowTh” (Current Below Low AC PEM Major Yes (true)
Temperature)
“EnvTempHighTh” (Environment • PEMs Major Yes (true)
Temperature Above High Threshold)

• Fan modules
• Management
modules
• Traffic modules
“EnvTempLowTh” (Environment • PEMs Not alarmed Yes (true)
Temperature Above Low Threshold)
• Fan modules
• Management
modules
• Traffic modules
“EnvVoltHighTh” (Environment Voltage
• AC PEMs Major Yes (true)
Above High Threshold)
• Traffic modules
“EnvVoltLowTh” (Environment Voltage • AC PEMs Major Yes (true)
Below Low Threshold)

• Traffic modules
“EqptComm” (Equipment Management Traffic modules Major Depends on cause
Communications Failure) of alarm
“EqptDgrd” (Equipment Degrade)
• UFM modules Major Yes (true)
• BIC modules
“EqptFail” (Equipment Failure)
• Equipment Critical Yes (true)
• Management
modules
• Traffic modules

• Pluggable
transceivers
“EqptMism” (Equipment Mismatch) • Equipment Critical Yes (true)

• Management
modules
• Traffic modules
• Pluggable
transceivers



“EqptMiss” (Equipment Missing) • Equipment Critical Yes (true)

• Management
modules
• Traffic modules
• Pluggable
transceivers
“FanSpeedLowTh” (Fan Speed Below Fan module Major Yes (true)
Threshold)
“FECI” (Far-End Node Configuration
• DOL ports Major Yes (true)
Mismatch)
Optical Supervisory
Channels
“FEIM” (Far-End Node Identification • DOL ports Major Yes (true)
Mismatch)
Optical Supervisory
Channels
“FirmUpgrdInProg” (Automatic Shelf Management modules Not alarmed No (false)
Management Firmware Upgrade in
Progress)
“FirmUpgrdFail” (Shelf Management Management modules Major No (false)
Firmware Upgrade Failed)
“FirmUpgrdReqd” (Firmware Upgrade Management modules Major No (false)
Required)
“Forced” (Forced Protection Switch Active) Wavelength protection Not alarmed No (false)
ports
“HighBer” (High Bit-Error Rate) Ethernet interfaces Major No (false)
“InvUnknown” (Inventory Unknown) Pluggable transceivers Major No (false)
“LaserFail” (Laser Fail) • OTN OTU interfaces Critical Yes (true)

• Ethernet interfaces
• SONET/SDH
interfaces
• Wavelength channels



“LaserTempHighTh” (Laser Temperature • OTN OTU interfaces Major No (false)
Above High Temperature Threshold)

• SONET/SDH
interfaces
“LaserTempLowTh” (Laser Temperature • OTN OTU interfaces Major No (false)
Below Low Temperature Threshold)

• SONET/SDH
interfaces
“LCK” (Locked, ODU) OTN ODU interfaces Critical Yes (true)
“LF” (Local Fault) Ethernet interfaces Not alarmed No (false)
“Lockout” (Lockout of Protection) Wavelength protection Not alarmed No (false)
ports
“LOF” (Loss of Frame) • OTN OTU interfaces Critical Yes (true)

• SONET/SDH
interfaces
“LoLightRx” (Loss of Light, Receive) • DOL PRE ports Critical Yes (true)

• DOL optical service
channels
• DOL optical multiplex
sections

• DOL optical channels
• Wavelength
protection ports
ports
“LoLightTx” (Loss of Light, Transmit) DOL optical channels Major Yes (true)
“LOM” (Loss of Multiframe) OTN OTU interfaces Critical Yes (true)



“LOS” (Loss of Signal) • OTN OTU interfaces Critical Yes (true)

• SONET/SDH
interfaces
“LoSpecRx” (Loss out of Specification, DOL ports Critical Yes (true)
Receive)
“LoSync” (Loss of Synchronization) Ethernet interfaces Critical Yes (true)
“LPBK” (Loopback Operated)
• OTN OTU interfaces Not alarmed No (false)
• SONET/SDH
interfaces
“MemHighUsage” (Memory High Usage) • Management Major No (false)
modules
• Traffic modules
“ModTempHighTh” (Module Temperature OTN OTU4 line Major No (false)
Above High Threshold) interfaces
“ModTempLowTh” (Module Temperature OTN OTU4 line Major No (false)
Below Low Threshold) interfaces
“ModTempShutdown” (Module OTN OTU4 line Critical Yes (true)
Temperature Shutdown) interfaces
“MS-AIS” (Multiplex Section Alarm SDH interfaces Not alarmed Yes (true)
Indication Signal, SDH)
“MS-RDI” (Multiplex Section Remote SDH interfaces Not alarmed No (false)
Defect Indication, SDH)
“NonCoLocatedController” (Controllers are • BTI7814 chassis Critical Yes (true)
in Different Chassis)
• BTI7802 chassis
“ObrHt” (Optical Backreflection High Terminal amplifier Minor Yes (true)
Threshold Exceeded) Optical Supervisory
channels
“OchAis” (Alarm Indication Signal, OCH) DOL optical channels Not alarmed Yes (true)
“OchOci” (Open Connection Indication, DOL optical channels Critical Yes (true)
OCH)
“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 multiplex Not alarmed Yes (true)
sections
“OneCableDisconnected” (One Multi-
• BTI7814 chassis Major Yes (true)
Chassis Cable Disconnected)
• BTI7802 chassis



“OprHighTh” (Optical Power Received • OTN OTU interfaces Major No (false)

• SONET/SDH
interfaces
“OprLowTh” (Optical Power Received • OTN OTU interfaces Major No (false)

• SONET/SDH
interfaces
“OptHighTh” (Optical Power Transmitted
• OTN OTU interfaces Major No (false)
• SONET/SDH
interfaces

“OptLowTh” (Optical Power Transmitted • OTN OTU interfaces Major No (false)

• SONET/SDH
interfaces
“OTU-AIS” (OTU Alarm Indication Signal) OTN OTU interfaces Not alarmed Yes (false)
“PartitionFault” (Disk Partition Fault • Management Major No (false)
Detected) modules

• Traffic modules
“PosRxHigh” (Receive Power Out of DOL optical channels Minor Yes (true)
Specification, High)
“PosRxLow” (Receive Power Out of
• DOL optical multiplex Major Yes (true)
Specification, Low) sections
• DOL optical channels
“PosTxHigh” (Transmit Power Out of DOL optical channels Critical Yes (true)
Specification, High)
“PosTxLow” (Transmit Power Out of DOL optical channels Critical Yes (true)
Specification, Low)
“PowerAbsent” (No Power Available) PEM Critical Yes (true)
“PRBS” (PRBS Test Activated)
• OTN OTU interfaces Not alarmed No (false)
• SONET/SDH
interfaces
“PyldMism” (Payload Mismatch) OTN ODU interfaces Critical Yes (true)
“RDI-L” (Remote Defect Indication, Line) SONET interfaces Not alarmed No (false)



“RF” (Remote Fault) Ethernet interfaces Not alarmed No (false)
“ScmNmiDown” (System Controller Management modules Major Yes (true)
Management Interface Down)
“scmNoNmConn” (No Network Management modules Critical Yes (true)
Management Connectivity on SCM)
“SD” (Signal Degrade) • OTN OTU interfaces Minor No (false)
• SONET/SDH
interfaces
“TIM” (Trace Identifier Mismatch) • OTN OTU interfaces Critical Yes (true)

• SONET/SDH
interfaces
“TlossRxHt” (Loss Above High Threshold, Terminal amplifier line Minor Yes (true)
Receive) ports
“TlossRxLt” (Loss Below Low Threshold, Terminal amplifier line Minor Yes (true)
Receive) ports
“UPGRD” (Upgrade in Progress) • Management Minor Yes (true)
modules

• Traffic modules


AirFilterAbsence
Table 2-2 Alarm details

Parameter Description
Code AirFilterAbsence
Description/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

Fault Indicator
Entity Name
Equipment Indicator Status
chassis:<1 | 2> BTI78141 See equipment specifications in the
BTI7800 Series Hardware Overview and
Installation Guide.
Clearing an AirFilterAbsence alarm

Note Follow all applicable safety requirements as described in the BTI7800 Series
Hardware Overview and Installation Guide.
Important Refer to the BTI7800 Series Hardware Overview and Installation Guide before
installing equipment in the chassis.

Step 1 Confirm whether an air filter is present in the chassis.
• If an air filter is present, go to Step 2.
• If an air filter is not present, go to Step 3.

Step 2 Ensure that the air filter is properly seated in the chassis, and then go to Step 4.

Step 3 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–L
Table 2-4 Condition details

Code ais-l
Description Alarm Indication Signal–Line (AIS-L), SONET: The local interface has received an
AIS-L signal from the NE at the far end of the fiber, indicating that no SONET signal
is being transmitted upstream of (and toward) the local NE. See also “Maintenance
signaling”.
Entities Affected SONET (OC192, WAN PHY OC192) interfaces (see Table 2-5).
Default Severity Not alarmed.
Service Affecting Yes (true).
Condition Clearing See “Clearing an AIS-L condition”.
Related Fault Hierarchy See “OC192, WAN PHY over OC192 interface fault hierarchy”.
Table 2-5 SONET (OC192, WAN PHY OC192) interfaces

Fault Indicator
Entity Name
Module Indicator Status
oc192:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –
wanoc192:<chassis>/<slot>/<subslot>/<port>
Clearing an AIS-L condition


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.



APR

Code apr
Description Automatic Power Reduction: For safety reasons, the local port has automatically
reduced laser power. For more information about APR, see the BTI7800 Series
Software Configuration Guide.
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

Fault Indicator
Entity Name
port:<chassis>/<slot>/1/PRE PRE Fault LED, PRE port On
Table 2-8 Terminal amplifier ports

Fault Indicator
Entity Name
client:<chassis>/<slot>/1/<portNum> AMP1 Fault LED, DCM port On
dcm:<chassis>/<slot>/1/<portNum> Fault LED, C1 port
Clearing an APR alarm (PRE port)


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.

Clearing an APR alarm (terminal amplifier port)


Step 1 Do one of the following:
• If the alarm is raised against the client Out port, retrieve statistics for the port to view
the values of the APR optical backreflection and Optical power transmitted
counters.
show statistics current client:identifier
• If the alarm is raised against the DCM Out port, check for a “LoLightRx” alarm on
the DCM In port.

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



APSD

Code apsd
Description Automatic Power Shutdown: The local port has automatically shut down its laser
because either the optical power received has dropped below the Loss of Light,
Receive threshold or APSD has been triggered on the NE at the far end of the fiber.
For more information about APSD, see the BTI7800 Series Software Configuration
Guide.
Entities Affected • DOL ports (see Table 2-10).
• Terminal amplifier line ports (see Table 2-11).
Possible Causes • The fiber connection is poor.
• 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

Fault Indicator
Entity Name
port:<chassis>/<slot>/0/L1 ROADM2 or ILA Fault LED, L1 port On
port:<chassis>/<slot>/0/C<n> Fault LED, C<n> port
where the range of n depends on the module.
Table 2-11 Terminal amplifier line ports

Fault Indicator
Entity Name
line:<chassis>/<slot>/1/<portNum> AMP1 Fault LED, Line port On


Clearing an APSD alarm (DOL port)


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


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

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.



BDI

Code bdi
Description/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 being
transmitted downstream of (and away from) the local NE. (See also “Maintenance
signaling”.)
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

Fault Indicator
Entity Name
otu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On
otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port
otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port
Clearing a BDI condition


Step 1 Check for and clear all alarms downstream of the local NE.




ContComS

Code contComS
Description 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”.

• “DOL OSC fault hierarchy”
Table 2-15 DOL optical service channels (OSCs)

Fault Indicator
Entity Name
osc:<chassis>/<slot>/0/L1 ROADM2 or ILA Fault LED, L1 port On
osc:<chassis>/<slot>/0/C<n> Fault LED, C<n> port
Table 2-16 Terminal amplifier Optical Supervisory Channels (OSCs)

Fault Indicator
Entity Name
osc:<chassis>/<slot>/1/<portNum>.<oscNum> AMP1 – –


Clearing a ContComS alarm


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.



DiskHighUsage

Code diskHighUsage
Description 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%. For
information about clearing this alarm, contact your next level of support.
Table 2-18 Management and traffic modules

Fault Indicator
Entity Name
cmm:<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


EnvCurrentHighTh

Code envCurrentHighTh
Description/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-current
thresholds”.
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

Fault Indicator
Entity Name
pem:<chassis>/<slot> AC PEM See the PEM specifications in the
Installation Guide.
Clearing an EnvCurrentHighTh alarm

reseating (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.



EnvCurrentLowTh

Code envCurrentLowTh
Description/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-current
thresholds”.
Alarm Clearing See “Clearing an EnvCurrentLowTh alarm”.

Fault Indicator
Entity Name
Installation Guide.
Clearing an EnvCurrentLowTh alarm


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.



EnvTempHighTh

Code envTempHighTh
Description/Cause Environment Temperature Above High Threshold: The temperature at the
equipment or module has exceeded the high temperature threshold. For
information, see “Temperature thresholds - equipment and traffic modules”.
Entities Affected • Equipment (see Table 2-24).

• Management and traffic modules (see Table 2-25).
Alarm Clearing See “Clearing an EnvTempHighTh alarm”.

Fault Indicator
Entity Name
pem:<chassis>/<slot> PEM See equipment specifications in the
fan:<chassis>/<slot> Cooling module
Installation Guide.

Fault Indicator
Entity Name
bic:<chassis>/<slot>/<subslot> BIC


Clearing an EnvTempHighTh alarm

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

Step 1 Retrieve environment information to view the temperature reading for the equipment or
traffic 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.




EnvTempLowTh

Code envTempLowTh
Description/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”.
Entities Affected
• Equipment (see Table 2-27).
Alarm Clearing See “Clearing an EnvTempLowTh condition”.

Fault Indicator
Entity Name
pem:<chassis>/<slot> PEM – –

Fault Indicator
Entity Name
cmm:<chassis>/<slot> CMM – –


Clearing an EnvTempLowTh condition

traffic modules.

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







EnvVoltHighTh

Code envVoltHighTh
Description/Cause Environment Voltage Above High Threshold: The voltage on the equipment (PEM)
or module exceeds the high-voltage threshold. For information, see “Voltage
thresholds”.

Caution

Continued operation might cause equipment damage.

Entities Affected
• Traffic modules (see Table 2-31).
Alarm Clearing See “Clearing an EnvVoltHighTh alarm”.

Fault Indicator
Entity Name
Installation Guide.
Table 2-31 Traffic modules

Fault Indicator
Entity Name
ufm:<chassis>/<slot> UFM See Appendix C, “BTI7800 Series


Clearing an EnvVoltHighTh alarm

traffic modules.

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







EnvVoltLowTh

Code envVoltLowTh
Description/Cause Environment Voltage Above High Threshold: The voltage on the equipment (PEM)
or module is below the low-voltage threshold. For information, see “Voltage
thresholds”.

Caution


Entities Affected
Alarm Clearing See “Clearing an EnvVoltLowTh alarm”.

Fault Indicator
Entity Name
Installation Guide.

Fault Indicator
Entity Name


Clearing an EnvVoltLowTh alarm

traffic modules.

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


Step 3 Check for alarms on the equipment or module:





EqptComm

Code eqptComm
Description/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”.

Fault Indicator
Entity Name
Clearing an EqptComm alarm

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

Step 1 Perform a warm reboot of the active CMM, and then check for alarms on the affected
module.

Step 2 Perform a cold reboot of the active CMM, and then check for alarms on the affected
module.



EqptDgrd

Code eqptDgrd
Description/Cause Equipment Degrade: Initialization of a module has failed.
Entities Affected Traffic modules (see Table 2-38).
Alarm Clearing See “Clearing an EqptDgrd alarm”.

Fault Indicator
Entity Name
ufm:<chassis>/<slot> UFM See Appendix C, “BTI7800 Series module
and BIC LED behavior”.
bic:<chassis>/<slot>/<subslot> 1x CFP BIC or
12x SFP+ BIC
Clearing an EqptDgrd alarm

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

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



EqptFail

Code eqptFail
Description/Cause Equipment Failure: A hardware self-test has detected faulty equipment.
• Pluggable transceivers (see Table 2-41).
Alarm Clearing See “Clearing an EqptFail alarm”.

Fault Indicator
Entity Name
cap:<chassis>/<slot> CAP See equipment specifications in the
Installation Guide.
esl:<chassis>/<slot> ESL
pem:<chassis>/<slot> PEM

Fault Indicator
Entity Name


Table 2-42 Pluggable transceivers

Fault Indicator
Entity Name
Transceiver Indicator Status
<transceiver-type>:<chassis>/<slot>/<subslot>/ CFP, SFP+ Fail LED, CFP or SFP+ client On
<port> port on BIC
where transceiver-type corresponds to the type
of transceiver installed in the port; for example,
cfp or sfpPlus.
pre:<chassis>/<slot> PRE Fail LED, PRE port
Clearing an EqptFail alarm


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.



EqptMism

Code eqptMism
Description/Cause Equipment Mismatch: The installed equipment does not match the equipment
provisioned for the slot or subslot.

Alarm Clearing See “Clearing an EqptMism alarm”.

Fault Indicator
Entity Name
fan:<chassis>/<slot> Cooling module See equipment specifications in the
Installation Guide.

Fault Indicator
Entity Name



Fault Indicator
Entity Name
<transceiver-type>:<chassis>/<slot>/<subslot>/ CFP, SFP+ Fail LED, CFP or SFP+ client On
<port> port on BIC
cfp or sfpPlus.
Clearing an EqptMism alarm

Note Refer to the BTI7800 Series Hardware Overview and Installation Guide before
replacing 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 the
BTI7800 Software Configuration Guide.
• Replace the equipment with equipment that matches the provisioned settings.




EqptMiss

Code eqptMiss
Description/Cause Equipment Missing: Provisioned equipment is not physically present in a slot or
subslot.

Alarm clearing See “Clearing an EqptMiss alarm”.

Fault Indicator
Entity Name
fan:<chassis>/<slot> Cooling module – –

Fault Indicator
Entity Name
cmm:<chassis>/<slot> CMM – –



Fault Indicator
Entity Name
<transceiver-type>:<chassis>/<slot>/<subslot>/ CFP, SFP+ – –
<port>
cfp or sfpPlus.
pre:<chassis>/<slot> PRE – –
Clearing an EqptMiss alarm

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

Step 1 Retrieve inventory and provisioned-equipment information:
show inventory
show 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 BTI7800




FanSpeedLowTh

Code fanSpeedLowTh
Description 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”.

Fault Indicator
Entity Name
fan:<chassis>/<slot> Cooling module See cooling module specifications in the
Installation Guide.
Clearing a FanSpeedLowTh alarm


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 for
information about environmental site requirements.

Step 3 Check for and clear alarms raised against each PEM, and then check for alarms on the
cooling module.



Step 4 Reseat the cooling module, and then check for alarms.

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



FECI

Code feci
Description/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 values
provisioned on a terminal amplifier Optical Supervisory Channel do not match the
actual (far-end) degree and group values.
Entities Affected
• DOL ports (see Table 2-54).
Alarm Clearing See:
• “Clearing a FECI alarm (DOL port)”
• “Clearing a FECI alarm (terminal amplifier OSC)”

Fault Indicator
Entity Name

Fault Indicator
Entity Name


Clearing a FECI alarm (DOL port)


Step 1 Retrieve DOL fiber-connection information to identify the unsupported fiber-connection
configuration:
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 Software
Configuration Guide.


Clearing a FECI alarm (terminal amplifier OSC)


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 the
BTI7800 Series Software Configuration Guide.

Step 4 Check for alarms on the OSC.



FEIM

Code feim
Description/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 system
information provisioned on a terminal amplifier Optical Supervisory Channel does
not match the actual (far-end) system information
Entities Affected
• DOL ports (see Table 2-57).
Alarm Clearing See:
• “Clearing a FEIM alarm (DOL port)”
• “Clearing a FEIM alarm (terminal amplifier OSC)”

Fault Indicator
Entity Name

Fault Indicator
Entity Name


Clearing a FEIM alarm (DOL port)


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

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 Configuration
Guide.


Clearing a FEIM alarm (terminal amplifier OSC)


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.




FirmUpgrdInProg

Code firmUpgrdInProg
Description/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,
Table 2-60 Management modules

Fault Indicator
Entity Name


FirmUpgrdFail

Code firmUpgrdFail
Description/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”.

Fault Indicator
Entity Name
Clearing a FirmUpgrdFail alarm

Step 1 Reattempt the firmware upgrade. For information, see the BTI7800 Series Hardware
Overview and Installation Guide.

Step 2 Check for alarms on the CMM.



FirmUpgrdReqd

Code firmUpgrdReqd
Description/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, see
the BTI7800 Series Software Configuration Guide.

Fault Indicator
Entity Name


Forced

Code forced
Description/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, see
Table 2-66 Wavelength protection ports

Fault Indicator
Entity Name
wpsport:<chassis>/<slot>/L<n> WPS4 – –
where n is in the range of 1A to 4A or 1B to 4B.


HighBer

Code highBer
Description 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

Fault Indicator
Entity Name
100ge:<chassis>/<slot>/<subslot>/<port>/ 1x CFP BIC Fault LED, 100G port On
<subport>
10ge:<chassis>/<slot>/<subslot>/<port>/ 12x SFP+ BIC Fault LED, 10G port
<subport>


Clearing a HighBer alarm


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 Power
Received Minimum Threshold and Optical Power Received Maximum Threshold
values.
show interface name:identifier detail
Note For detailed transceiver specifications, see Appendix B, “BTI7800 Series

transceivers”.

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.



InvUnknown

Code invUnknown
Description/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”.

Fault Indicator
Entity Name
<transceiver-type>:<chassis>/<slot>/<subslot>/ CFP, SFP+ Fail LED, 100GE or 10GE On
<port> port
cfp or sfpPlus.
Clearing an InvUnknown alarm

replacing a transceiver.

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

Step 2 Check for alarms on the port.



LaserFail

Code laserFail
Description/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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>
Table 2-74 SONET/SDH interfaces

Fault Indicator
Entity Name
oc192:<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

Fault Indicator
Entity Name
channel:<chassis>/<slot>/<subslot>/ 1x CFP BIC1 Fault LED, 100G port On
<port.channel>
1 Reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP transceivers.
Clearing a LaserFail alarm

Guide 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 3 Replace the either the UFM or the pluggable transceiver:
• If the alarm is raised against a line-port interface provisioned on an integrated MSA
transceiver, replace the UFM.
• If the alarm is raised against a client-port interface provisioned on a pluggable
transceiver, replace the pluggable transceiver.




LaserTempHighTh

Code laserTempHighTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name



Fault Indicator
Entity Name
<port.channel>
Clearing a LaserTempHighTh alarm

replacing a traffic module or a transceiver.

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

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.




LaserTempLowTh

Code laserTempLowTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name



Fault Indicator
Entity Name
<port.channel>
Clearing a LaserTempLowTh alarm

replacing a traffic module or a transceiver.

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

against a line-port interface provisioned on an integrated MSA, the UFM.




LCK

Code lck
Description Locked, ODU: The local interface has received an ODU-LCK signal from the NE at
the far end of the fiber, indicating that the connection at the transmitting interface is
locked.
Entities Affected OTN ODU interfaces (see Table 2-87).
Possible Causes The transmitting OTN OTU interface at an upstream NE is either administratively
disabled or in loopback mode.
Alarm Clearing See “Clearing an LCK alarm”.
Table 2-87 OTN ODU interfaces

Fault Indicator
Entity Name
odu4:<chassis>/<slot>/<subslot>/<port> UFM4 Fault LED, 100G line port On
odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC Fault LED, 100G port
odu2:<chassis>/<slot>/<subslot>/<port.sub-
interface>
odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC Fault LED, 10G port


Clearing an LCK alarm


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

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.



LF

Code lf
Description Local Fault: The local interface has received a local-fault signal from the NE at the
far end of the fiber, indicating that no Ethernet signal is being transmitted upstream
of (and toward) the local NE. (See also “Maintenance signaling”.)

Condition Clearing See “Clearing an LF condition ”.

Fault Indicator
Entity Name
100ge:<chassis>/<slot>/<subslot>/<port>/ 1x CFP BIC – –
<subport>
10ge:<chassis>/<slot>/<subslot>/<port>/ 12x SFP+ BIC
<subport>
Clearing an LF condition





Lockout

Code lockout
Description/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, see

Fault Indicator
Entity Name
wpsport:<chassis>/<slot>/L<n> WPS4 – –


LOF

Code lof
Description 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”.
• “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”

Fault Indicator
Entity Name
Table 2-94 SONET /SDH interfaces

Fault Indicator
Entity Name


Clearing an LOF alarm



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





LoLightRx

Code loLightRx
Description/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 OMS fault hierarchy”

• “DOL OCH fault hierarchy”

Note

For wavelength protection ports, this alarm is not masked by any other alarm.

Table 2-96 DOL PRE ports

Fault Indicator
Entity Name
port:<chassis>/<slot>/0/PRE PRE Fault LED, PRE port On
port:<chassis>/<slot>/1/PRE


Table 2-97 DOL optical service channels (OSCs)

Fault Indicator
Entity Name
osc:<chassis>/<slot>/0/L1 ROADM2 or ILA Fault LED, L1 port On
osc:<chassis>/<slot>/0/C<n> Fault LED, C<n> port
Table 2-98 DOL optical multiplex sections (OMSs)

Fault Indicator
Entity Name
oms:<chassis>/<slot>/0/L1<> ROADM2 or ILA Fault LED, L1 port On
oms:<chassis>/<slot>/0/C<n> Fault LED, C<n> port
Table 2-99 DOL optical channels (OCHs)

Fault Indicator
Entity Name
och:<chassis>/<slot>/0/C<n>/<channel> ROADM2 – –
where the range of n depends on the module
and channel is an alphanumeric string.

Fault Indicator
Entity Name
wpsport:<chassis>/<slot>/L<n> WPS4 Fault LED, Line<n> port On
Table 2-101 Terminal amplifier ports

Fault Indicator
Entity Name
line:<chassis>/<slot>/1/<portNum> Fault LED, Line port On
dcm:<chassis>/<slot>/1/<portNum> Fault LED, DCM port
client:<chassis>/<slot>/1/<portNum> Fault LED, C1 port


Clearing a LoLightRx alarm (DOL entity)

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

Step 1 Retrieve statistics for the affected entity to view the value of the Optical power
received 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 “DOL
OSC power alarm thresholds”, “DOL OMS power alarm thresholds”, or “DOL OCH
power alarm thresholds”, and then go to Step 4.

Step 3 Check for and resolve any of the following problems, and then go to Step 5:
• The span fiber or patch panel fiber is cut or disconnected or has excessive loss.
• The amplifier transmitting into the patch fiber has shut down.
• There is excessive loss on each module that is connected to the alarmed port.
• There is excessive loss on upstream patch fibers.

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


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

• Inspect the fiber connection, and ensure that the fiber is intact, thoroughly clean, and
• 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)


Step 1 Retrieve statistics for the port to view the value of the Optical power received
counter:

• 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.
• The far-end port is administratively disabled.

Step 3 Check for alarms on the local port.



LoLightTx

Code loLightTx
Description/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”.

Fault Indicator
Entity Name
och:<chassis>/<slot>/0/L1/<channel> ROADM2 – –
where channel is an alphanumeric string.
och:<chassis>/<slot>/0/C<n>/<channel>
where the range of n depends on the module
and channel is an alphanumeric string.
Clearing a LoLightTx alarm

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

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

Step 2 Ensure that the upstream fiber connections are thoroughly clean and correctly connected.

Step 3 Check for alarms on the DOL optical channel.



LOM

Code lom
Description Loss of Multiframe: The multiframe alignment process is in the out-of-multiframe
state.
Alarm Clearing See “Clearing an LOM alarm”.

Fault Indicator
Entity Name
Clearing an LOM alarm



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





LOS

Code los
Description 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”.

• “Ethernet interface fault hierarchy”

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>



Fault Indicator
Entity Name

Fault Indicator
Entity Name
<port.channel>
1 Monitoring and reporting of this alarm for a wavelength channel is supported only on multiwavelength CFP
transceivers.
Clearing an LOS alarm



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




LoSpecRx

Code loSpecRx
Description 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”.

Fault Indicator
Entity Name
Clearing a LoSpecRx alarm


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

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




LoSync

Code loSync
Description 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”.

Fault Indicator
Entity Name
<subport>
<subport>


Clearing a LoSync alarm


Step 1 Retrieve detailed information for the interface, and ensure that the value of the Optical
Power Rx counter is within the range indicated by the Optical Power Received
Minimum Threshold and Optical Power Received Maximum Threshold values.

transceivers”.


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





LPBK

Code lpbk
Description/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 the

Fault Indicator
Entity Name
otu4:<chassis>/<slot>/<subslot>/<port> UFM4 – –
otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC
otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name


MemHighUsage

Code memHighUsage
Description/Cause Memory High Usage.
Alarm Clearing This alarm indicates that memory usage on the module has exceeded 90%. For
information about clearing this alarm, contact your next level of support.

Fault Indicator
Entity Name


ModTempHighTh

Code modTempHighTh
Description 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”.

Fault Indicator
Entity Name


Clearing a ModTempHighTh alarm


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

• Either a cooling module is not present in the chassis or is present but is operationally
down or administratively disabled.
• A “FanSpeedLowTh” alarm has been raised against a cooling module.
• An “EnvTempHighTh” alarm has been raised against the UFM.
• The ambient temperature is higher than the specified operating range for the chassis.




ModTempLowTh

Code modTempLowTh
Description Module Temperature Below Low Threshold: The temperature of the MSA
transceiver is below low-temperature threshold. For information, see “Temperature
thresholds - MSA transceivers”.
Possible Cause The ambient temperature is lower than the normal operating range of the chassis.
Alarm Clearing See “Clearing a ModTempLowTh alarm”.

Fault Indicator
Entity Name
Clearing a ModTempLowTh alarm


Step 1 Optionally retrieve statistics for the OTU4 interface to view the value of the Module
temperature 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. For
information, see the BTI7800 Series Hardware Overview and Installation Guide.
show environment




ModTempShutdown

Code modTempShutdown
Description Module Temperature Shutdown: The temperature of the MSA transceiver has
exceeded the high-temperature-shutdown threshold, causing the transmit laser to
shut down. For information, see “Temperature thresholds - MSA transceivers”.
Entities Affected OTN OTU interfaces (see Table 2-122 on page 2-74).
Possible Causes The ambient temperature is excessively higher than the normal operating range of
the MSA transceiver.
Alarm Clearing See “Clearing ModTempShutdown alarm”.

Fault Indicator
Entity Name


Clearing ModTempShutdown alarm

replacing a traffic module.

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

Step 2 Check for alarms on the OTU4 interface.

Step 3 Replace the UFM4.




MS-AIS

Code ms-ais
Description/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 is
being transmitted upstream of (and toward) the local NE. (See also “Maintenance
signaling”.)
Entities Affected SDH (STM64, WAN PHY STM64) interfaces (see Table 2-128).
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

Fault Indicator
Entity Name
stm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –
Clearing an MS-AIS condition


Step 1 Check for and clear all alarms on the upstream NE.




MS-RDI

Code ms-rdi
Description/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 SDH
signal is being transmitted downstream of (and away from) the local NE. (See also
“Maintenance signaling”.)
Entities Affected SDH (STM64, WAN PHY STM64) interfaces (see Table 2-130).
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

Fault Indicator
Entity Name
stm64:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC – –
Clearing an MS-RDI condition


Step 1 Check for and clear all alarms on the downstream NE.




NonCoLocatedController

Code nonCoLocatedController
Description/Cause Controllers are in Different Chassis: The active CMMs in a multi-chassis
configuration are not located in the same chassis.

Note

This alarm is supported on the BTI7814 and BTI7802 chassis only.

Alarm Clearing See “NonCoLocatedController”.

Fault Indicator
Entity Name
chassis:<1 | 2> BTI7814 or BTI7802 See equipment specifications in the
Installation Guide.
Clearing a NonCoLocatedController alarm


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




ObrHt

Code obrHt
Description 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”.

Fault Indicator
Entity Name
Clearing an ObrHt alarm


Step 1 Retrieve statistics for the entity to view the value of the Optical back reflected
power counter:

Step 2 Retrieve statistics information from the running configuration file to view the threshold
profile for the OSC:
show running-config statistics
Example
bti7800# show running-config statistics threshold profile
statistics
threshold profile obrdis
entityType osc
statistic opt-back-ref-ratio alarmHigh unTimed
enabled


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.




OchAis

Code ochAis
Description Alarm Indication Signal (AIS), OCH: The local NE has received an OCH-AIS signal
from the far-end NE, indicating that no signal is being transmitted upstream of (and
toward) the local NE.
Condition Clearing See “Clearing an OchAis condition”.

Fault Indicator
Entity Name
och:<chassis>/<slot>/0L1/<channel> ROADM2 – –
where n depends on the module and channel is
an alphanumeric string.
Clearing an OchAis condition



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.



OchOci

Code ochOci
Description Open Connection Indication (OCI), OCH: The optical channel has received an OCH–
OCI signal from the NE at the far end of the fiber, indicating that there is a missing
optical cross-connect on an upstream node.
Alarm Clearing See “Clearing an OchOci condition”.

Fault Indicator
Entity Name
Clearing an OchOci condition


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.



OchUeq

Code ochUeq
Description/Cause OCH Unequipped: The downstream optical channel is not provisioned.
Alarm Clearing See “Clearing an OchUeq alarm”.

Fault Indicator
Entity Name
Clearing an OchUeq alarm


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

Step 2 Check for alarms on the local DOL OCH.



OCI

Code oci
Description/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 present
on an upstream node.
Alarm Clearing See “Clearing an OCI alarm”.

Fault Indicator
Entity Name
interface>
Clearing an OCI alarm


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




ODU-AIS

Code odu-ais
Description/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 ODU
signal 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
odu4:<chassis>/<slot>/<subslot>/<port> UFM4 – –
odu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC
interface>
odu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC


Clearing an ODU-AIS condition






OmsAis

Code OmsAis
Description Alarm Indication Signal, OMS: The local NE has received an OMS-AIS signal from
the far-end NE, indicating that no signal is being transmitted upstream of (and
toward) the local NE.
Entities Affected DOL optical multiplex sections (see Table 2-147).
Condition Clearing “Clearing an OmsAis condition”
Related Fault Hierarchy See “DOL OMS fault hierarchy”.

Fault Indicator
Entity Name
oms:<chassis>/<slot>/0/L1<> ROADM2 or ILA Fault LED, L1 port On
oms:<chassis>/<slot>/0/C<n> Fault LED, C<n> port
Clearing an OmsAis condition



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.



OneCableDisconnected
Table 2-148 Alarm/condition details

Code oneCableDisconnect
Description/Cause One Multi-Chassis Cable Disconnected: A cable that connects two CMMs in a multi-
chassis configuration is not connected to a CMM.

Note

This alarm is supported on the BTI7814 and BTI7802 chassis only.

Alarm Clearing See “Clearing a OneCableDisconnected alarm”.

Fault Indicator
Entity Name
chassis:<1 | 2> BTI7814 or BTI7802 See equipment specifications in the
Installation Guide.
Clearing a OneCableDisconnected alarm


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




OprHighTh

Code oprHighTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name


Table 2-153 SONET/SDH interfaces (Continued)

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<port.channel>
Clearing an OprHighTh alarm


values.

transceivers”.



Step 4 Add an attenuation pad in the optical path.




OprLowTh

Code oprLowTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name


Table 2-158 SONET/SDH interfaces (Continued)

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<port.channel>
Clearing an OprLowTh alarm


values.

transceivers”.



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




OptHighTh

Code optHighTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name



Fault Indicator
Entity Name
<port.channel>
Clearing an OptHighTh alarm


Optical Power Tx counter is within the range indicated by the Optical Power
Transmitted Minimum Threshold and Optical Power Transmitted Maximum
Threshold values.

transceivers”.





OptLowTh

Code optLowTh
Description 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”.

Fault Indicator
Entity Name

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name



Fault Indicator
Entity Name
<port.channel>
Clearing an OptLowTh alarm


Optical Power Tx counter is within the range indicated by the Optical Power
Transmitted Minimum Threshold and Optical Power Transmitted Maximum
Threshold values.

transceivers”.





OTU-AIS

Code otu-ais
Description/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 being
transmitted upstream of (and toward) the local NE.

Note

This signal is generated by non-BTI7800 NEs only.

Entities Affected
• OTN OTU interfaces (see Table 2-171).
Condition Clearing The condition will clear when the fault that resulted in the transmission of the OTU-
AIS signal is resolved.

Fault Indicator
Entity Name


PartitionFault

Code partitionFault
Description/Cause Disk Partition Fault Detected.
Alarm Clearing See “Clearing a ParitionFault alarm”.

Fault Indicator
Entity Name
Modules Indicator Status
Clearing a ParitionFault alarm

traffic module.

Step 1 Perform a warm reboot of the module.

Step 2 Check for alarms on the module.



PosRxHigh

Code posRxHigh
Description/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”.

Fault Indicator
Entity Name
Clearing a PosRxHigh alarm


Step 1 Retrieve PM statistics for the DOL OCH:

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.



PosRxLow

Code posRxLow
Description 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”.

Fault Indicator
Entity Name
oms:<chassis>/<slot>/0/L1<> ROADM2 or ILA – –
oms:<chassis>/<slot>/0/C<n>

Fault Indicator
Entity Name


Clearing a PosRxLow alarm


Step 1 Retrieve statistics for the DOL entity:

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 specified
range 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.



PosTxHigh

Code posTxHigh
Description/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”.

Fault Indicator
Entity Name
Clearing a PosTxHigh alarm


Step 1 Retrieve statistics for the DOLOCH:

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.




PosTxLow

Code posTxLow
Description/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”.

Fault Indicator
Entity Name
Clearing a PosTxLow alarm


Step 1 Retrieve statistics for the DOL OCH:

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.




PowerAbsent

Code powerAbsent
Description No Power Available: No power is available to the power entry module (PEM).

Caution


Possible Causes • AC PEM: The input AC voltage is either less than 90 Vac or greater than 255
Vac, and the output DC voltage is either less than 40 Vdc or greater than 60
Vdc.
• DC PEM: The input and output DC voltages are either less than 40 Vdc or
greater than 60 Vdc.
Alarm Clearing See “Clearing a PowerAbsent alarm”.

Fault Indicator
Entity Name
pem:<chassis>/<slot> PEM See the PEM specifications in the
Installation Guide.
Clearing a PowerAbsent alarm


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.



PRBS

Code prbs
Description/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,

Fault Indicator
Entity Name
otu4:<chassis>/<slot>/<subslot>/<port> 1x CFP BIC
otu2:<chassis>/<slot>/<subslot>/<port> 12x SFP+ BIC

Fault Indicator
Entity Name
<subport>
<subport>

Fault Indicator
Entity Name


PyldMism

Code pyldMism
Description 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”.

Fault Indicator
Entity Name
interface>


Clearing a PyldMism alarm


Step 1 Retrieve interface data to compare the values of the Payload Type and Received
Payload 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.




RDI-L

Code rdi-l
Description/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 being
transmitted downstream of (and away from) the local NE. (See also “Maintenance
signaling”.)
Entities Affected SONET (OC192, WAN PHY OC192) interfaces (see Table 2-192).
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

Fault Indicator
Entity Name
Clearing an RDI-L condition






RF

Code rf
Description/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 transmitted
downstream of (and away from) the local NE. (See also “Maintenance signaling”.)

Condition Clearing See “Clearing an RF condition”.

Fault Indicator
Entity Name
<subport>
<subport>
Clearing an RF condition





ScmNmiDown

Code scmNmiDown
Description/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 ”.

Fault Indicator
Entity Name
Clearing an ScmNmiDown alarm


Step 1 Provision a static management IP address on the affected CMM. For information, see




scmNoNmConn

Code scmNoNmConn
Description/Cause No Network Management Connectivity on System Controller Module (SCM):
• In a dual-CMM system, neither SCM can connect to the management IP
network.
• In a single-CMM system, the SCM cannot connect to the management IP
network.
Alarm Clearing See “Clearing an scmNoNmConn alarm”.

Fault Indicator
Entity Name
Clearing an scmNoNmConn alarm


Step 1 Provision a static management IP address on each affected CMM. For information, see




SD

Code sd
Description 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”.


Fault Indicator
Entity Name

Fault Indicator
Entity Name


Clearing an SD alarm

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

transceivers”.





TIM

Code tim
Description 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”.


Fault Indicator
Entity Name

Fault Indicator
Entity Name


Clearing a TIM alarm


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 Message

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.




TlossRxHt

Code tlossRxHt
Description/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”.

Fault Indicator
Entity Name
Clearing a TlossRxHt alarm


Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Optical
power loss in recv. direction counter:
show statistics current line:identifier
Note For detailed AMP1 specifications, see the BTI7800 Series Hardware Overview
and 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.

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



TlossRxLt
Table 2-207 Alarm/condition details

Code tlossRxLt
Description/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”.

Fault Indicator
Entity Name
Clearing a TlossRxLt alarm


Step 1 Retrieve statistics for the terminal amplifier line port to view the value of the Optical
power loss in recv. direction counter:
show statistics current line:identifier
Note For detailed AMP1 specifications, see the BTI7800 Series Hardware Overview
and 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:



UPGRD

Code upgrd
Description/Cause Upgrade in Progress: A system software upgrade is in progress.
Alarm Clearing This alarms clear when the system software upgrade is completed.

Fault Indicator
Entity Name



C H A P T E R 3
3.0 Fault masking

Fault masking occurs when a service-affecting alarm or condition raised against a monitored
entity suppresses the reporting of other alarms or conditions that are raised against the same
entity. A fault that masks another fault is in a higher position in the fault hierarchy for a
monitored entity and indicates either a higher priority fault or a fault that more accurately
identifies the source of a problem. This means that when a fault that masks other faults is
cleared, each masked fault will be reported if it was not cleared by the resolution of the masking
fault.
The following sections list faults common to specific monitored entities and include fault-
hierarchy flow charts that illustrate the masking relationships among those faults.
• “Equipment fault hierarchy”
• “Environment fault hierarchy”




Fault masking

Equipment fault hierarchy

Table 3-1 Equipment fault hierarchy

Alarms/Conditions Fault Hierarchy
“EqptMiss”
“EqptMism”
“EqptComm”
“EqptFail”
“EqptDgrd”

Fault masking

Environment fault hierarchy

Table 3-2 Environment fault hierarchy

“Equipment fault
hierarchy”
“EnvCurrentHighTh”
“EnvCurrentLowTh”
“EnvTempHighTh”
“EnvTempLowTh”
“EnvVoltHighTh”
“EnvVoltLowTh”

Fault masking

Common fault hierarchy - OTN and CBR ports

Table 3-3 Common fault hierarchy - OTN and CBR ports

“Equipment fault hierarchy”
“LOS”
“LPBK”
“PRBS”
“LaserTempHighTh”
“LaserTempLowTh”
“LaserFail”
“ModTempShutdown”
“OptHighTh”
“OprLowTh”
“LOF”
Protocol Faults:

• “OC192, WAN PHY over OC192
interface fault hierarchy”
• “STM64, WAN PHY over STM64
interface 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 OTU
interface will mask all faults raised against each OTU ODU interface it contains.
Table 3-4 OTN interface fault hierarchy

“LOS”
“LOF”
“SD”
“LOM”
“BDI”
“TIM”
“ODU-AIS”
“LCK”
“OCI”
“PyldMism”

Fault masking

Ethernet interface fault hierarchy

Table 3-5 Ethernet interface fault summary

“LOS”
“LoSync”
“HighBer”
“LF”
“RF”

Fault masking

OC192, WAN PHY over OC192 interface fault hierarchy

Table 3-6 OC192, WAN PHY over OC192 interface fault summary

“LOS”
“LOF”
“SD”
“TIM”
“AIS–L”
“RDI-L”

Fault masking

STM64, WAN PHY over STM64 interface fault hierarchy

Table 3-7 STM64, WAN PHY over STM64 interface fault summary

“LOS”
“LOF”
“SD”
“TIM”
“MS-AIS”
“MS-RDI”

Fault masking

DOL port fault hierarchy

Table 3-8 DOL port fault summary

“APSD”
“FECI”
“FEIM”
“LoSpecRx”
“APR”
“LoLightRx”

Fault masking

DOL OSC fault hierarchy

Table 3-9 DOL OSC fault summary

Alarms/Condition Fault Hierarchy
“ContComS”
“LoLightRx”

Fault masking

DOL OMS fault hierarchy

Table 3-10 DOL OMS alarms summary

“OmsAis”
“LoLightRx”
“PosRxLow”

Fault masking

DOL OCH fault hierarchy

Table 3-11 DOL OCH fault summary

“OchOci”
“OchUeq”
“PosTxHigh”
“LoLightTx”
“DOL OMS fault hierarchy”
“PosTxLow”
“PosRxHigh”
“OchAis”
“LoLightRx”
“PosRxLow”

Fault masking

Terminal amplifier port fault hierarchy

Table 3-12 Terminal amplifier port fault summary

“APSD”
“ContComS”
“FECI”
“FEIM”
“ObrHt”
“TlossRxHt”
“TlossRxLt”
“APR”
“LoLightRx”

Fault masking


C H A P T E R 4
4.0 Alarm thresholds


• “Environment thresholds”
• “DOL thresholds”

Alarm thresholds

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 modules

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

Sensor Description
Alarm 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 Local ambient temperature
where <n> is A1, A2, B1, or B2.
PEM AC <n> Temperature Local ambient temperature
Table 4-2 Temperature thresholds - equipment and modules

Equipment/Module Sensor Low Threshold High Threshold
AMP1 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)

Chassis 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 – 105°C (221°F)

Note

Supported on UFM4 only.

WPS4 DS75 Temp 3 – 85°C (185°F)
Temperature thresholds - MSA transceivers

Table 4-3 provides alarm-related module temperature thresholds for the 100G Coherent MSA
XCVR
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 thresholds
Table 4-4 provides information about available fan-speed sensors and the alarm thresholds for
BTI7800 Series cooling modules.
Table 4-4 Fan-speed thresholds

Sensor
Cooling Module Low Threshold
Name Description
FAN2 Fan Tach <n> Fan speed 1500 RPM
where n is a value from 1 to 3.
FAN3 Fan RPM Fan speed 1500 RPM
FAN5 Fan Tach <n> Fan speed 2500 RPM
where n is a value from 1 to 5.
Output-current thresholds
Table 4-5 provides information about available output-current sensors and the alarm thresholds
for BTI7800 Series equipment.
Table 4-5 Output-current sensors and thresholds

Equipment Sensor Description Low Threshold High Threshold
AC PEM Iout PEMAC <n> Output current (Vdc) 0.2 Vdc 60 Vdc
where <n> is A1, A2, B1, or
B2
Voltage thresholds
Table 4-6 and Table 4-7 provide information about available voltage sensors and the alarm
thresholds for BTI7800 Series equipment and traffic modules.
Table 4-6 Voltage sensors

Sensor Description
12V_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 Description
Vin PEM AC <n> Input voltage
Vout PEM AC <n> Output voltage
Table 4-7 Voltage thresholds

AMP1 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
• “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 thresholds

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

L1
Threshold Client Input Client Output
OPT OPR
Hardware 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)

L1
OPT OPR
Hardware 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 thresholds

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

Client Input Client L1
Threshold
Add-Drop Pass-Thru Output OPT OPR OPR + PRE
Hardware min. -18.0 -18.0 -8.5 -21.8 -29.0 -39.0
Loss of Light -17.0 -8.8 N/A N/A -28.0 -38.0
raise
Loss of Light -16.0 -7.8 N/A N/A -27.0 -37.0
clear
Power Out of -14.0 -6.8 N/A N/A -26.0 -36.0
Specification
Low raise
Power Out of -13.5 -6.3 N/A N/A -25.5 -35.5
Specification
Low clear
Hardware 23.0 23.0 23.0 23.3 14.4 3.4
max.
Table 4-11 ILA OMS power alarm thresholds (all values in dBm)

Client Input L1
Threshold Client Output
Pass-Thru OPT OPR OPR + PRE
Hardware min. -8.3 -4.3 -21.8 -29.0 -39.0
Loss of Light -7.3 N/A N/A -28.0 -38.0
raise
Loss of Light -6.3 N/A N/A -27.0 -37.0
clear
Power Out of -4.3 N/A N/A -26.0 -36.0
Specification
Low raise
Power Out of -3.8 N/A N/A -25.5 -35.5
Specification
Low clear
Hardware max. 25.1 25.1 23.3 -14.4 3.4

Alarm thresholds

DOL OCH power alarm thresholds

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

PostAmp IN L1
(Internal) OPT OPR
Hardware min. -20.3 -14.5 -27.0 Alarm state set Not supported
from PostAmp IN
Loss of Light -16.6 -10.8 -23.3
raise
Loss of Light -15.5 -9.7 -22.2
clear
Power Out of -13.6 -7.8 -20.3
Specification
Low raise
Power Out of -13.0 -7.2 -19.7
Specification
Low clear
Power Out of 5.1 5.1 -13.3
Specification
High raise
Power Out of 5.7 5.7 -12.8
Specification
High clear
Hardware max. 17.2 17.2 -1.2

Alarm thresholds

DOL port power alarm thresholds

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

Mainboard PRE Port CFP2 PRE Port
Threshold
Input Output Input Output
Hardware 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 of -18.0 N/A -38.5 N/A
Specification, Low
raise
Specification, Low
clear
Hardware max. 15.6 4.6 4.0 19.0
Table 4-14 ILA PRE port-power alarm thresholds (all values in dBm)

Mainboard PRE Port CFP2 PRE Port
Threshold
Input Output Input Output
Hardware 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
Specification Low
raise
Specification Low
clear
Hardware max. 15.6 4.6 4.0 19.0

Alarm thresholds

DOL Rx-loss alarm thresholds

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

Line
Client (to Client
Threshold without PRE for without PRE for
or MD03) with PRE
NDSF NZDSF
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)

Line
Threshold Client (to Client) without PRE for without PRE for
with PRE
NDSF NZDSF
LoSpecRx raise 2.2 33.2 23.2 19.7
LoSpecRx clear 2.0 33.0 23.0 19.5

A P P E N D I X A
Appendix A: BTI7800 Series equipment and

modules

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

System Component PEC
BTI7814 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

Appendix A: BTI7800 Series equipment and modules

Table A- 2 BTI7800 Series management and traffic modules

Module Description PEC
Management modules
Chassis Management Module 1 (CMM1) Provides management and control of the BT8A78CMM1
system.
Service modules
Universal Forwarding Module Lite (UFM3) Supports two BICs. BT8A78UFM3
Universal Forwarding Module Lite with Contains one 100G Coherent MSA BT8A78UFM4
Integrated 100G Coherent MSA XCVR (UFM4) XCVR and supports one BTI Interface
Card (BIC).
96-Channel Amplifier (AMP1) Provides DWDM composite signal BT8A78AMP1
amplification in point-to-point applications.
Wavelength Protection Switch (WPS4) Provides revertive or non-revertive BT8A78WPS4
wavelength protection switching.
2-Port Reconfigurable Optical Add/Drop 2-degree ROADM module. BT8A78RDM2
Multiplexer (ROADM2)
Inline Amplifier (ILA) Provides unidirectional DWDM C-band BT8A78AMPL
amplification and tilt control at transit
sites.
BIC modules
12x 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 modules
Pluggable Pre-Amplifier (PRE) Pre-amplifier module that plugs into the BT8A78AMPP
PRE slot of a host ROADM or ILA
module.
Passive modules
96-Channel Fixed Mux/Demux (FMD96) Provides local fixed grid access to all 96 BT8A78MD03
wavelengths in the DWDM 50GHz
channel plan.
A-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

A P P E N D I X B
Appendix B: BTI7800 Series transceivers

Table B-1 lists transceivers supported on the BTI7800 Series. For additional information, see the
following 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 Introduced
SFP+ 850nm 200m Dual-Rate 10.3 Multimode 10.3 and 10.5 Gbps BP3AD6SS Release 1.1
and 10.5Gbps
SFP+ 1310nm 10km Multi-Rate 9.9 Single-mode 9.9 to 11.1 Gbps BP3AM6MS Release 1.1
to 11.1Gbps
SFP+ DWDM Fixed 80km Multi- Single-mode 9.9 to 11.1 Gbps BP3AM6DL-xx Release 1.1
Rate 9.9 to 11.1Gbps
SFP+ DWDM Tunable 80km Multi- Single-mode 9.9 to 11.1 Gbps BP3AM6TL Release 1.1
Rate 9.9 to 11.1Gbps
CFP 100GBASE-SR10 100m Multiple single- 100 Gbps BP3AMASS Release 1.1
mode fibers in a
single cable
CFP 100GBASE-LR4 10km Single-mode 100 Gbps BP3AMDLI Release 1.1
100G Coherent CFP Single-mode 100 Gbps BP3AMCTL Release 1.5
Installation rules
exist for this
transceiver.
100G Coherent MSA XCVR Single-mode 100 Gbps Integrated on the Release 1.1
Universal
Forwarding
Module Lite with
Integrated 100G
Product Release 2.1.1 STANDARD B-1


Table B- 1 Transceivers

Type Fiber Type Bit Rate PEC Introduced
Coherent MSA
XCVR
(BT8A78UFM4 )
B-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01


BTI7800 SFP+ Transceiver Optical Specifications

Table B- 2 SFP+ 850nm 200m Dual-Rate 10.3 and 10.5Gbps (BP3AD6SS)

Parameter Min Typ Max Units
Bit Rate 10.3125 - 10.52 Gb/s
Transmitter
TX 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
Receiver
Receiver operating wavelength 840 - 860 nm
Stressed receiver sensitivity - - -7.5 dBm
(BER = 1e-12)
Receiver overload 0.5 - - dBm
Optical path penalty - - 3.9 dB
Reflectance - - -12 dB
Other
Reach (50m MMF, 2000 - - 300 m
MZHzkm)
Connector/Latch type LC/Bail
Power Consumption (40° Typical: 0.8W
ambient)1 Maximum: 1W
Compliance IEEE 802.3, SFP+ MSA
1Before 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)

Bit Rate 9.953 - 11.0957 Gb/s
Transmitter
Transmitter 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
Receiver


Table B- 3 SFP+ 1310nm 10km Multi-Rate 9.9 to 11.1Gbps (BP3AM6MS) (Continued)

Stressed receiver sensitivity - - -10.3 dBm
(BER = 1e-12)
Receiver overload 0.5 - - dBm
Optical path penalty(@ 6.6 ps/nm) - - 3.2 dB
Other
Reach - - 10 km
Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, SFP+ MSA
Table B- 4 SFP+ DWDM Fixed 80km Multi-Rate 9.9 to 11.1Gbps (BP3AM6DL-xx xx=[01,40])

Bit Rate 9.953 - 11.0957 Gb/s
Transmitter
Transmitter operating wavelength 192.1 - 196 THz
Average operating power -1 - 3 dBm
Spectral width (-20dB) - - 0.3 nm
Receiver
Receiver overload 3 - - dBm
Other
Power Consumption (40° TBD
ambient)1


Table B- 5 Receiver Transmission Optical Performance Specifications: BP3AM6DL-xx xx=[01,40]

Bit Rate (Gbps) Dispersion (ps/nm) OSNR (dB) Receiver BER
Sensitivity
(Min to Max)
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)

Sensitivity
(Min to Max)
≥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)

Bit Rate 9.953 - 11.0957 Gb/s
Transmitter
TX operating wavelength 191.35 - 196.1 THz
Average operating power -1 - 3 dBm
Spectral width (-20dB) - - 0.3 nm
Receiver
Rx operating wavelength 1260 - 1600 nm
Rx overload 3 - - dBm
Other


Table B- 7 Receiver Transmission Optical Performance Specifications: BP3AM6TL

Sensitivity
(Min to Max)
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 Specifications

Table B- 8 CFP 100GBASE-SR10 100m: BP3AMASS

Transmitter
Signaling 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
Receiver
Stressed receiver sensitivity per - - -5.4 dBm
lane
Rx overload 3.4 - - dBm
Optical path penalty - - 3.5 dB
Other
Power Consumption (40° ambient) Typical: 10W
Before using for planning or Maximum: 12W
implementation purposes, contact
Juniper Networks Support to
confirm the power consumption
values.
Compliance IEEE 802.3, CFP MSA
Table B- 9 CFP 100GBASE-LR4 10km: BP3AMDLI

Transmitter
Signaling 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
(SMSR)
Extinction ratio (OTU4) 7 - - dB


Table B- 9 CFP 100GBASE-LR4 10km: BP3AMDLI (Continued)

Receiver
Stressed Rx sensitivity per lane - - -6.8 dBm
Receiver overload - - 5.5 dBm
Other
values.
Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, CFP MSA
Table B- 10 100G Coherent CFP: BP3AMCTL

Transmitter
Transmitter 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
Receiver
Receiver frequency range 191.35 - 196.10 THz
Input power range -18 (-21dBm in - 0 dBm
unamplified
applications)
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
Other
values.
Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709, CFP MSA


Table B- 11 100G Coherent MSA XCVR on UFM4

Transmitter
Transmitter 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
Receiver
Receiver frequency range 191.35 - 196.10 THz
Input power range -18 (-22dBm in - -2 dBm
unamplified
systems)
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
Other
Compliance IEEE 802.3, Telcordia GR-253, ITU-T G.709

A P P E N D I X C
Appendix C: BTI7800 Series module and BIC

LED 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 Description
Identify 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 Description
Identify The Identify LED OFF The CMM has identified and acknowledged the
(AMBER) indicates whether the module.
CMM has identified and The CMM can only acknowledge the module if the
acknowledged the module is administratively up. A newly-inserted
newly-inserted module. module is administratively up if either of the
following is true:
• The module has been pre-provisioned and
configured 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

Appendix C: BTI7800 Series module and BIC LED behavior

Table C- 2 Service module LED behavior (Continued)

Name Description State State Description
to identify the module, the module is
automatically provisioned and its administrative
status is set to up.
ON The CMM has failed to identify or acknowledge the
module.
BLINKING The CMM is attempting to identify and
acknowledge the module.
Active The Active LED reflects OFF The operational status of the module is down.
(GREEN) the operational status of ON The operational status of the module is up.
the module.
Fail The Fail LED reflects OFF The operational status of the module is up.
(RED) the operational status of ON The operational status of the module is down.
the module.
H/S The Hot Swap H/S LED OFF The administrative status of the module is up, and
(BLUE) indicates whether the the actual module matches the provisioned module.
module can be removed The module should not be removed from the
from the chassis. chassis in this state.
ON The administrative status of the module is down, or
the actual module does not match the provisioned
module.
The module can be removed from the chassis in
this state.
BLINKING This is a transient state that occurs when plugging
in a module, or when changing its administrative
status.
The module should not be removed from the
chassis in this state.
Table C- 3 BIC LEDs

Active 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 slot
after a minimum of 5 seconds in this state.
BLINKING: The module is being placed into a quiescent state. It cannot be
removed from the slot.
OFF: The module is operating normally. It cannot be removed from the slot.
Table C- 4 BIC port LEDs

Fail Red The port has failed.
Fault Amber A fault exists on the port.
C-2 BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Juniper Networks, Inc. tel: 408-745-2000 www.juniper.net
1133 Innovation Way
Sunnyvale, CA 94089 USA

Part Number: BT8A78PD0021 product release 2.1.1
Document Version: 01
Published: November 2016
Type: STANDARD

BTI7800 Alarm and Troubleshooting Guide 2.1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BTI7800 Alarm and Troubleshooting Guide 2.1

Uploaded by

Copyright:

Available Formats

BTI7800 Series Alarm and Troubleshooting Guide

Juniper Networks, Inc. tel: 408-745-2000 www.juniper.net

Product Release 2.1.1 STANDARD iii

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

iv BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

LoLightRx ......................................................................................................................................................................................... 2-61

Product Release 2.1.1 STANDARD v

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

vi BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

DOL port fault hierarchy ..................................................................................................................................................................... 3-9

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

BTI7800 Series Documentation

Requesting Technical Support

viii BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Self-Help Online Tools and Resources

Opening a Case with JTAC

End User License Agreement

Product Release 2.1.1 STANDARD ix

x BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

Caution USE OF CONTROLS OR ADJUSTMENTS OR PERFORMANCE OF

Product Release 2.1.1 STANDARD xi

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

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

xii BTI7800 Series Alarm and Troubleshooting Guide – Document Version 01

1.0 Fault monitoring on the BTI7800

Product Release 2.1.1 STANDARD 1-1

Figure 1-1 Alarm information retrieved using the CLI

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

Product Release 2.1.1 STANDARD 1-3

Table 1-3 Default maintenance signals - interface protocols

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

2.0 Alarms and conditions

Product Release 2.1.1 STANDARD 2-1

Table 2-1 BTI7800 alarms and conditions (Continued)

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

Table 2-1 BTI7800 alarms and conditions (Continued)

Product Release 2.1.1 STANDARD 2-3

Table 2-1 BTI7800 alarms and conditions (Continued)

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

Table 2-1 BTI7800 alarms and conditions (Continued)

Product Release 2.1.1 STANDARD 2-5

Table 2-1 BTI7800 alarms and conditions (Continued)

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

Table 2-1 BTI7800 alarms and conditions (Continued)

Product Release 2.1.1 STANDARD 2-7

Table 2-3 BTI7800 chassis

Clearing an AirFilterAbsence alarm

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

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

Clearing an AIS-L condition

Product Release 2.1.1 STANDARD 2-9

Table 2-7 DOL ports

Table 2-8 Terminal amplifier ports

Clearing an APR alarm (PRE port)

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

Clearing an APR alarm (terminal amplifier port)

Product Release 2.1.1 STANDARD 2-11

Table 2-10 DOL ports

Table 2-11 Terminal amplifier line ports

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

Clearing an APSD alarm (DOL port)