BTI7800 Series Alarm and Troubleshooting GuideAlarmDetails.....107...

BTI7800Series AlarmandTroubleshootingGuide

Release

4.1

Modified: 2017-04-25

Copyright © 2017, Juniper Networks, Inc.

Juniper Networks, Inc.1133 InnovationWaySunnyvale, California 94089USA408-745-2000www.juniper.net

Copyright © 2017, Juniper Networks, Inc. All rights reserved.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

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.

BTI7800 Series Alarm and Troubleshooting Guide4.1Copyright © 2017, Juniper Networks, Inc.All rights reserved.

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through theyear 2038. However, the NTP application is known to have some difficulty in the year 2036.

ENDUSER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networkssoftware. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted athttp://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions ofthat EULA.

Copyright © 2017, Juniper Networks, Inc.ii

http://www.juniper.net/support/eula.html

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Chapter 1 Fault Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring Fault Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Fault Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Fault Impact on Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Fault Masking and Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Equipment Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Environment Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Common Fault Hierarchy - OTN and CBR Ports . . . . . . . . . . . . . . . . . . . . . . . . 27

OTN Interface Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Ethernet Interface Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

OC192, WAN PHY Over OC192 Interface Fault Hierarchy . . . . . . . . . . . . . . . . 29

STM64, WAN PHY Over STM64 Interface Fault Hierarchy . . . . . . . . . . . . . . . 30

DOL Port Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

DOL OSC Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

DOL OMS Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

DOL OCH Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Terminal Amplifier Port Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Maintenance Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 2 Alarms and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Alarm and Condition Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

AirFilterAbsence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Clearing an AirFilterAbsence Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

AIS–L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Clearing an AIS-L Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

APR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Clearing an APR Alarm (PRE Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Clearing an APR Alarm (terminal Amplifier Port) . . . . . . . . . . . . . . . . . . . . . . 48

APSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Clearing an APSD Alarm (DOL Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Clearing an APSD Alarm (terminal Amplifier Line Port) . . . . . . . . . . . . . . . . . 50

iiiCopyright © 2017, Juniper Networks, Inc.

BDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Clearing a BDI Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

ContComS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Clearing a ContComS Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

DiskHighUsage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

EnvCurrentHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Clearing an EnvCurrentHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

EnvCurrentLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Clearing an EnvCurrentLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

EnvTempHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Clearing an EnvTempHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

EnvTempLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Clearing an EnvTempLowTh Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

EnvVoltHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Clearing an EnvVoltHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

EnvVoltLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Clearing an EnvVoltLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

EqptBrownout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Clearing an EqptBrownout Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

EqptComm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Clearing an EqptComm Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

EqptDgrd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Clearing an EqptDgrd Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

EqptFail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Clearing an EqptFail Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

EqptMism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Clearing an EqptMism Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

EqptMiss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Clearing an EqptMiss Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

FanSpeedLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Clearing a FanSpeedLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

FECI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Clearing a FECI Alarm (DOL Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Clearing a FECI Alarm (terminal Amplifier OSC) . . . . . . . . . . . . . . . . . . . . . . . 76

FEIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Clearing a FEIM Alarm (DOL Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Clearing a FEIM Alarm (terminal Amplifier OSC) . . . . . . . . . . . . . . . . . . . . . . 78

FirmUpgrdInProg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

FirmUpgrdFail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Clearing a FirmUpgrdFail Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

FirmUpgrdReqd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Forced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

HighBer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Clearing a HighBer Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

InvUnknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Clearing an InvUnknown Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

InventoryUnsupp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Clearing an InventoryUnsupp Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Copyright © 2017, Juniper Networks, Inc.iv

BTI7800 Series Alarm and Troubleshooting Guide

IsisAdjDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Clearing an IsisAdjDown Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

LaserFail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Clearing a LaserFail Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

LaserTempHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Clearing a LaserTempHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

LaserTempLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Clearing a LaserTempLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

LCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Clearing an LCK Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

LF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Clearing an LF Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Clearing an LOF Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Lolck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Clearing a Lolck Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

LoLightRx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Clearing a LoLightRx Alarm (DOL Entity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Clearing a LoLightRx Alarm (wavelength Protection Port) . . . . . . . . . . . . . . 104

Clearing a LoLightRx Alarm (terminal Amplifier Port) . . . . . . . . . . . . . . . . . . 104

LoLightTx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Clearing a LoLightTx Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Clearing an LOM Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Clearing an LOS Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

LoSpecRx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Clearing a LoSpecRx Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

LoSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Clearing a LoSync Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

LPBK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

MemHighUsage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

ModTempHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Clearing a ModTempHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

ModTempLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Clearing a ModTempLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

ModTempShutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Clearing a ModTempShutdown Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

MS-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Clearing an MS-AIS Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

MS-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Clearing an MS-RDI Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

NonCoLocatedController . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Clearing a NonCoLocatedController Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

ObrHt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Clearing an ObrHt Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

OchAis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Clearing an OchAis Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

vCopyright © 2017, Juniper Networks, Inc.

Table of Contents

OchOci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Clearing an OchOci Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

OchUeq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Clearing an OchUeq Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

OCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Clearing an OCI Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

ODU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Clearing an ODU-AIS Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

OmsAis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Clearing an OmsAis Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

OneCableDisconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Clearing a OneCableDisconnected Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

OprHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Clearing an OprHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

OprLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Clearing an OprLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

OptHighTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Clearing an OptHighTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

OptLowTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Clearing an OptLowTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

OTU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

PartitionFault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Clearing a ParitionFault Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

PosRxHigh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Clearing a PosRxHigh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

PosRxLow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Clearing a PosRxLow Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

PosTxHigh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Clearing a PosTxHigh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

PosTxLow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Clearing a PosTxLow Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

PowerAbsent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Clearing a PowerAbsent Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

PRBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

PreFecBerTh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Clearing a PreFecBerTh Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

PyldMism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Clearing a PyldMism Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

RDI-L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Clearing an RDI-L Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Clearing an RF Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

ScmNmiDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Clearing an ScmNmiDown Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

ScmNoNmConn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Clearing an ScmNoNmConn Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Clearing an SD Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Copyright © 2017, Juniper Networks, Inc.vi


TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Clearing a TIM Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

TlossRxHt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Clearing a TlossRxHt Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

TlossRxLt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Clearing a TlossRxLt Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

UPGRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 3 Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Environment Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Temperature Thresholds - Equipment and Traffic Modules . . . . . . . . . . . . . 169

Temperature Thresholds - MSA Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . 171

Fan-speed Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Output-current Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Voltage Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

DOL Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

DOL OSC Power and Optical Backreflection Alarm Thresholds . . . . . . . . . . 174

DOL OMS Power Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

DOL OCH Power Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

DOL Port Power Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

DOL Rx-loss Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Chapter 4 BTI7800 Series Equipment and Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Common Equipment Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Management and Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

BTI7800 Series Module and BIC LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

viiCopyright © 2017, Juniper Networks, Inc.

Table of Contents

List of Figures


Figure 1: Alarm Information Retrieved Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . 24

ixCopyright © 2017, Juniper Networks, Inc.

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii


Table 3: Entity Administrative Status and Fault Reporting . . . . . . . . . . . . . . . . . . . 23

Table 4: Fault Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 5: Equipment Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 6: Environment Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 7: Common Fault Hierarchy - OTN and CBR Ports . . . . . . . . . . . . . . . . . . . . 27

Table 8: OTN Interface Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 9: Ethernet Interface Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 10: OC192, WAN PHY Over OC192 Interface Fault Hierarchy . . . . . . . . . . . . 29

Table 11: STM64, WAN PHY Over STM64 Interface Fault Hierarchy . . . . . . . . . . . 30

Table 12: DOL Port Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table 13: DOL OSC Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 14: DOL OMS Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Table 15: DOL OCH Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 16: Terminal Amplifier Port Fault Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 17: Default Maintenance Signals - Interface Protocols . . . . . . . . . . . . . . . . . 33

Chapter 2 Alarms and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 18: BTI7800 Alarms and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 19: Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Table 20: BTI7800 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Table 21: Condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Table 22: SONET (OC192, WAN PHY OC192) Interfaces . . . . . . . . . . . . . . . . . . . . 46


Table 24: DOL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 25: Terminal Amplifier Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


Table 27: DOL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 28: Terminal Amplifier Line Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Table 29: Condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Table 30: OTN OTU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Table 31: Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Table 32: DOL Optical Service Channels (OSCs) . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Table 33: Terminal Amplifier Optical Supervisory Channels (OSCs) . . . . . . . . . . . 52


Table 35: Management and Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


xiCopyright © 2017, Juniper Networks, Inc.

Table 37: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


Table 39: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


Table 41: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56



Table 44: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table 45: Management and Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59


Table 47: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Table 48: Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Table 50: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62



Table 53: UFM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64





Table 58: Alarm Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Table 59: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


Table 61: Pluggable Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68


Table 63: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Table 64: Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Table 65: Pluggable Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70


Table 67: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71




Table 71: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74


Table 73: DOL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75



Table 76: DOL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77



Table 79: Management Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79






Table 85: Wavelength Protection Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Copyright © 2017, Juniper Networks, Inc.xii



Table 87: Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82




Table 91: Pluggable Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85


Table 93: Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86


Table 95: Optical Channel Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Table 96: OTN OTU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Table 97: Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table 98: SONET/SDH Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table 99: Wavelength Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table 100: Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89


Table 102: OTN OTU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90


Table 104: SONET/SDH Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90









Table 113: OTN ODU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95




Table 117: Wavelength Protection Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97






Table 123: Optical Channel Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100


Table 125: DOL PRE Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Table 126: DOL Optical Service Channels (OSCs) . . . . . . . . . . . . . . . . . . . . . . . . . 102

Table 127: DOL Optical Multiplex Sections (OMSs) . . . . . . . . . . . . . . . . . . . . . . . 102

Table 128: DOL Optical Channels (OCHs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Table 129: Wavelength Protection Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Table 130: Terminal Amplifier Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103




Table 134: OTN OTU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

xiiiCopyright © 2017, Juniper Networks, Inc.

List of Tables




Table 138: Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109


Table 140: Wavelength Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109


Table 142: DOL Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110



Table 145: Condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112





Table 150: Management and Traffic Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114








Table 158: SDH (STM64, WAN PHY STM64) Interfaces . . . . . . . . . . . . . . . . . . . . 119


Table 160: SDH (STM64, WAN PHY STM64) Interfaces . . . . . . . . . . . . . . . . . . . 120


Table 162: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


Table 164: DOL Optical Service Channels (OSCs) . . . . . . . . . . . . . . . . . . . . . . . . . 122

Table 165: Terminal Amplifier Optical Supervisory Channels (OSCs) . . . . . . . . . 122








Table 173: OTN ODU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128





Table 178: DOL Optical Multiplex Sections (OMSs) . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 179: Alarm/condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Table 180: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132




Copyright © 2017, Juniper Networks, Inc.xiv





















Table 203: SONET/SDH Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Table 204: Wavelength Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Table 205: Condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143


Table 207: Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144





Table 212: DOL Optical Multiplex Sections (OMSs) . . . . . . . . . . . . . . . . . . . . . . . . 147







Table 219: Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151










Table 229: SONET (OC192, WAN PHY OC192) Interfaces . . . . . . . . . . . . . . . . . . 158

Table 230: Condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158



xvCopyright © 2017, Juniper Networks, Inc.

List of Tables

Table 233: Management Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160


Table 235: Management Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161



Table 238: SONET/SDH Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163





Table 243: Terminal Amplifier Line Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Table 244: Alarm/condition Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Table 245: Terminal Amplifier Line Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167



Chapter 3 Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table 248: Temperature Sensors - Equipment and Modules . . . . . . . . . . . . . . . . 169

Table 249: Temperature Thresholds - Equipment and Modules . . . . . . . . . . . . . . 170

Table 250: Temperature Thresholds - 100G Coherent MSA XCVR Module . . . . . . 171

Table 251: Temperature Thresholds - 400G Coherent MSA XCVR Module . . . . . . 171

Table 252: Fan-speed Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Table 253: Output-current Sensors and Thresholds . . . . . . . . . . . . . . . . . . . . . . . 172

Table 254: Voltage Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Table 255: Voltage Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Table 256: ROADM2 OSC Power Alarm Thresholds (all Values in DBm) . . . . . . . 174

Table 257: ILA OSC Power Alarm Thresholds (all Values in DBm) . . . . . . . . . . . . 175

Table 258: Default OSC Back-Reflection Ratio Threshold Values (obrHt

Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Table 259: ROADM2 OMS Power Alarm Thresholds (all Values in DBm) . . . . . . . 175

Table 260: ILA OMS Power Alarm Thresholds (all Values in DBm) . . . . . . . . . . . 176

Table 261: ROADM2 50 GHz OCHOptical-power Alarm Thresholds (all Values

in DBm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Table 262: ROADM2 PRE Port-power Alarm Thresholds (all Values in DBm) . . . 177

Table 263: ILA PRE Port-power Alarm Thresholds (all Values in DBm) . . . . . . . . 178

Table 264: ROADM2 Rx-loss Alarm Thresholds (all Values in DB) . . . . . . . . . . . . 178

Table 265: ILA Rx-loss Alarm Thresholds (all Values in DB) . . . . . . . . . . . . . . . . . 178

Chapter 4 BTI7800 Series Equipment and Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Table 266: BTI7814 Major Common Equipment Components . . . . . . . . . . . . . . . 179

Table 267: BTI7802 Common Equipment Components . . . . . . . . . . . . . . . . . . . . 179

Table 268: BTI7801 Common Equipment Components . . . . . . . . . . . . . . . . . . . . 180

Table 269: BTI7800 Series Management and Traffic Modules . . . . . . . . . . . . . . 180

Table 270: CMM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Table 271: Service Module LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Table 272: BIC LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Table 273: Port LEDs (UFMs and BICs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Copyright © 2017, Juniper Networks, Inc.xvi


About the Documentation

• Documentation and Release Notes on page xvii

• Documentation Conventions on page xvii

• Documentation Feedback on page xix

• Requesting Technical Support on page xx

Documentation and Release Notes

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.

Documentation Conventions

Table 1 on page xviii defines notice icons used in this guide.

xviiCopyright © 2017, Juniper Networks, Inc.

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

http://www.juniper.net/books

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Indicates helpful information.Tip

Alerts you to a recommended use or implementation.Best practice

Table 2 on page xviii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, type theconfigure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on theterminal screen.

Fixed-width text like this

• A policy term is a named structurethat defines match conditions andactions.

• Junos OS CLI User Guide

• RFC 1997,BGPCommunities Attribute

• Introduces or emphasizes importantnew terms.

• Identifies guide names.

• Identifies RFC and Internet draft titles.

Italic text like this

Configure themachine’s domain name:

[edit]root@# set system domain-namedomain-name

Represents variables (options for whichyou substitute a value) in commands orconfiguration statements.

Italic text like this

Copyright © 2017, Juniper Networks, Inc.xviii


Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

• To configure a stub area, include thestub statement at the [edit protocolsospf area area-id] hierarchy level.

• Theconsoleport is labeledCONSOLE.

Represents names of configurationstatements, commands, files, anddirectories; configurationhierarchy levels;or labels on routing platformcomponents.

Text like this

stub <default-metricmetric>;Encloses optional keywords or variables.< > (angle brackets)

broadcast | multicast

(string1 | string2 | string3)

Indicates a choice between themutuallyexclusive keywords or variables on eitherside of the symbol. The set of choices isoften enclosed in parentheses for clarity.

| (pipe symbol)

rsvp { # Required for dynamicMPLS onlyIndicates a comment specified on thesame lineas theconfiguration statementto which it applies.

# (pound sign)

community namemembers [community-ids ]

Encloses a variable for which you cansubstitute one or more values.

[ ] (square brackets)

[edit]routing-options {static {route default {nexthop address;retain;

}}

}

Identifies a level in the configurationhierarchy.

Indention and braces ( { } )

Identifies a leaf statement at aconfiguration hierarchy level.

; (semicolon)

GUI Conventions

• In the Logical Interfaces box, selectAll Interfaces.

• To cancel the configuration, clickCancel.

Representsgraphicaluser interface(GUI)items you click or select.

Bold text like this

In the configuration editor hierarchy,select Protocols>Ospf.

Separates levels in a hierarchy of menuselections.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can provide feedback by using either of the following

methods:

• Online feedback rating system—On any page of the Juniper Networks TechLibrary site

athttp://www.juniper.net/techpubs/index.html, simply click the stars to rate thecontent,

and use the pop-up form to provide us with information about your experience.

Alternately, you can use the online feedback form at

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

xixCopyright © 2017, Juniper Networks, Inc.


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

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

• E-mail—Sendyourcommentsto [email protected]. Includethedocument

or topic name, URL or page number, and software version (if applicable).

Requesting Technical Support

Technical product support is available through the JuniperNetworksTechnicalAssistance

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

• 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 youwith 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/

Toverify serviceentitlementbyproduct serial number, useourSerialNumberEntitlement

(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Casewith JTAC

You can open a case with JTAC on theWeb 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).

Copyright © 2017, Juniper Networks, Inc.xx


mailto:[email protected]?subject=

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

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

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

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

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

http://kb.juniper.net/

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

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

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

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

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

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

For international or direct-dial options in countries without toll-free numbers, see

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

xxiCopyright © 2017, Juniper Networks, Inc.


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

CHAPTER 1

Fault Monitoring and Reporting

• Configuring Fault Monitoring and Reporting on page 23

• Fault Masking and Hierarchies on page 25

• Maintenance Signaling on page 33

Configuring Fault Monitoring and Reporting

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

theprotocol layerwith specific fault pointsdefined for all supportedprotocols.Monitoring

is also conducted on supporting BTI7800 equipment, including the various sensors

located throughout the chassis and on themodules.

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). Analarmgenerates anotificationas the fault becomesactive. A condition

does not generate a notification and is typically used to report lower-severity faults.

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 CLI command in the

BTI7800 Command Line Reference Guide.

Fault Reporting

When reporting is enabled for a fault that becomes active on amanaged entity, the

reportingbehaviorof that faultdependson theadministrativestatus (enabledordisabled)

of the entity, as described in the following table.

Table 3: Entity Administrative Status and Fault Reporting

Fault-Reporting BehaviorStatus

When a fault with critical, major, or minor severity (see Table 4 on page 24) becomes active, it is reportedwith 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 allactive faults (both alarms and conditions), and the command show alarms retrieves a list of all activealarms.

Enabled

23Copyright © 2017, Juniper Networks, Inc.

Table 3: Entity Administrative Status and Fault Reporting (continued)

Fault-Reporting BehaviorStatus

Whena faultwith critical,major, orminor severity either becomesactiveor is cleared, no reporting is provided.Polling results retrievedwith either show conditions or showalarms do not include any active faults (alarmsor conditions) on disabled entities.

Disabled

To retrieve alarms and conditions, use the show alarms and show conditions CLI

commands, respectively. Forbothalarmsandconditions, the information retrievedshows

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: Alarm Information Retrieved Using the CLI

Fault Severity

Each fault is associatedwith oneof thedefault severity types listed in the following table.

Table 4: Fault Severities

DescriptionSeverity

A failure that is likely causing serious loss or interruption of traffic.Critical

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

A failure that does not significantly affect traffic.Minor

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

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

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.

Fault 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 downwhen a fault is service-affecting.

Copyright © 2017, Juniper Networks, Inc.24


Fault Masking and Hierarchies

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 sameentity. A fault thatmasks 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, eachmasked 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 on page 25

• Environment Fault Hierarchy on page 26

• Common Fault Hierarchy - OTN and CBR Ports on page 27

• OTN Interface Fault Hierarchy on page 28

• Ethernet Interface Fault Hierarchy on page 29

• OC192, WAN PHY Over OC192 Interface Fault Hierarchy on page 29

• STM64, WAN PHY Over STM64 Interface Fault Hierarchy on page 30

• DOL Port Fault Hierarchy on page 30

• DOL OSC Fault Hierarchy on page 31

• DOL OMS Fault Hierarchy on page 31

• DOL OCH Fault Hierarchy on page 32

• Terminal Amplifier Port Fault Hierarchy on page 33

Equipment Fault Hierarchy

Table 5: Equipment Fault Hierarchy

Fault HierarchyAlarms/Conditions

“EqptMiss” on page 71

“EqptMism” on page 69

“EqptComm” on page 64

“EqptFail” on page 67

“EqptDgrd” on page 66


Chapter 1: Fault Monitoring and Reporting

Environment Fault Hierarchy

Table 6: Environment Fault Hierarchy


“Equipment FaultHierarchy” on page 25

“EnvCurrentHighTh” onpage 54

“EnvCurrentLowTh” onpage 55

“EnvTempHighTh” onpage 56

“EnvTempLowTh” onpage 58

“EnvVoltHighTh” onpage 60

“EnvVoltLowTh” onpage 62



Common Fault Hierarchy - OTN and CBR Ports

Table 7: Common Fault Hierarchy - OTN and CBR Ports


“Equipment Fault Hierarchy” on page 25

“LOS” on page 107

“LPBK” on page 112

“PRBS” on page 152

“LaserTempHighTh” on page 89

“LaserTempLowTh” on page 91

“LaserFail” on page 86

“ModTempShutdown” on page 117

“OptHighTh” on page 138

“OprLowTh” on page 135

“Lolck” on page 99

“LOF” on page 97

“PreFecBerTh” on page 153

Protocol Faults:

• OTN Interface Fault Hierarchy onpage 28

• Ethernet Interface Fault Hierarchy onpage 29

• OC192,WANPHYOverOC192 InterfaceFault Hierarchy on page 29

• STM64, WAN PHY Over STM64Interface Fault Hierarchy on page 30

“OptHighTh” on page 138

“OptLowTh” on page 140

“ModTempHighTh” on page 114

“ModTempLowTh” on page 116



OTN Interface Fault Hierarchy

NOTE: In the OTN fault hierarchy, a service-affecting fault raised against anOTNOTU interfacewillmaskall faults raisedagainsteachOTUODU interfaceit contains.

Table 8: OTN Interface Fault Hierarchy


“Equipment Fault Hierarchy” onpage 25



“SD” on page 162

“LOM” on page 106

“BDI” on page 50

“TIM” on page 163

“ODU-AIS” on page 128

“LCK” on page 94

“OCI” on page 126

“PyldMism” on page 155



Ethernet Interface Fault Hierarchy

Table 9: Ethernet Interface Fault Hierarchy




“LoSync” on page 111

“HighBer” on page 81

“LF” on page 96

“RF” on page 158

OC192,WANPHYOver OC192 Interface Fault Hierarchy

Table 10: OC192,WANPHYOver OC192 Interface Fault Hierarchy







“AIS–L” on page 45

“RDI-L” on page 157



STM64,WANPHYOver STM64 Interface Fault Hierarchy

Table 11: STM64,WANPHYOver STM64 Interface Fault Hierarchy







“MS-AIS” on page 118

“MS-RDI” on page 119

DOL Port Fault Hierarchy

Table 12: DOL Port Fault Hierarchy



“APSD” on page 48

“FECI” on page 75

“FEIM” on page 77

“LoSpecRx” on page 110

“APR” on page 46

“LoLightRx” on page 101



DOLOSC Fault Hierarchy

Table 13: DOLOSC Fault Hierarchy

Fault HierarchyAlarms/Condition


“ContComS” on page 51


“ObrHt” on page 121

DOLOMS Fault Hierarchy

Table 14: DOLOMS Fault Hierarchy



“OmsAis” on page 130


“PosRxLow” on page 147



DOLOCH Fault Hierarchy

Table 15: DOLOCH Fault Hierarchy



“OchOci” on page 124

“OchUeq” on page 125

“PosTxHigh” on page 149

“LoLightTx” on page 105

“DOL OMS Fault Hierarchy” onpage 31

“PosTxLow” on page 150

“PosRxHigh” on page 145

“OchAis” on page 123


“PosRxLow” on page 147



Terminal Amplifier Port Fault Hierarchy

Table 16: Terminal Amplifier Port Fault Hierarchy



“APSD” on page 48

“ContComS” on page 51

“FECI” on page 75

“FEIM” on page 77

“ObrHt” on page 121

“TlossRxHt” on page 165

“TlossRxLt” on page 166

“APR” on page 46


Maintenance Signaling

When normal traffic cannot be transmitted from a port, for example, when a received

signal is in a failed stateorwhenaport is administratively disabledand traffic is disrupted,

the BTI7800 Series will usually forward amaintenance 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 17 on page 33) enables the receiving node to

conclude that the link to the adjacent upstream node is intact.

Table 17: Default Maintenance Signals - Interface Protocols

Default Maintenance SignalProtocol

“ODU-AIS” on page 128OTNOTU

“ODU-AIS” on page 128OTNODU

“LF” on page 96Ethernet

“AIS–L” on page 45OC192, WAN PHY over OC192

“MS-AIS” on page 118STM64, WAN PHY over STM64



CHAPTER 2

Alarms and Conditions

• Alarm and Condition Summary on page 37

• AirFilterAbsence on page 44

• AIS–L on page 45

• APR on page 46

• APSD on page 48

• BDI on page 50

• ContComS on page 51

• DiskHighUsage on page 53

• EnvCurrentHighTh on page 54

• EnvCurrentLowTh on page 55

• EnvTempHighTh on page 56

• EnvTempLowTh on page 58

• EnvVoltHighTh on page 60

• EnvVoltLowTh on page 62

• EqptBrownout on page 63

• EqptComm on page 64

• EqptDgrd on page 66

• EqptFail on page 67

• EqptMism on page 69

• EqptMiss on page 71

• FanSpeedLowTh on page 73

• FECI on page 75

• FEIM on page 77

• FirmUpgrdInProg on page 79

• FirmUpgrdFail on page 79

• FirmUpgrdReqd on page 80

• Forced on page 81

• HighBer on page 81


• InvUnknown on page 83

• InventoryUnsupp on page 84

• IsisAdjDown on page 85

• LaserFail on page 86

• LaserTempHighTh on page 89

• LaserTempLowTh on page 91

• LCK on page 94

• LF on page 96

• Lockout on page 97

• LOF on page 97

• Lolck on page 99

• LoLightRx on page 101

• LoLightTx on page 105

• LOM on page 106

• LOS on page 107

• LoSpecRx on page 110

• LoSync on page 111

• LPBK on page 112

• MemHighUsage on page 114

• ModTempHighTh on page 114

• ModTempLowTh on page 116

• ModTempShutdown on page 117

• MS-AIS on page 118

• MS-RDI on page 119

• NonCoLocatedController on page 120

• ObrHt on page 121

• OchAis on page 123

• OchOci on page 124

• OchUeq on page 125

• OCI on page 126

• ODU-AIS on page 128

• OmsAis on page 130

• OneCableDisconnected on page 132

• OprHighTh on page 133

• OprLowTh on page 135

• OptHighTh on page 138

• OptLowTh on page 140



• OTU-AIS on page 143

• PartitionFault on page 144

• PosRxHigh on page 145

• PosRxLow on page 147

• PosTxHigh on page 149

• PosTxLow on page 150

• PowerAbsent on page 151

• PRBS on page 152

• PreFecBerTh on page 153

• PyldMism on page 155

• RDI-L on page 157

• RF on page 158

• ScmNmiDown on page 159

• ScmNoNmConn on page 161

• SD on page 162

• TIM on page 163

• TlossRxHt on page 165

• TlossRxLt on page 166

• UPGRD on page 167

Alarm and Condition Summary

Table 18: BTI7800 Alarms and Conditions

Service AffectingDefault SeverityEntities AffectedCode

No (false)MajorBTI7814 chassis“AirFilterAbsence”onpage44(Air FilterAbsent)

Yes (true)Not alarmedSONET interfaces“AIS–L” on page 45 (Alarm Indication Signal -Line, SONET)

Yes (true)Critical• DOL ports

• Terminal amplifier clientports

• Terminal amplifier DCMports

“APR”onpage46(AutomaticPowerReduction)

Yes (true)Critical• DOL ports

• Terminal amplifier lineports

“APSD” on page 48 (Automatic PowerShutdown)

No (false)Not alarmedOTNOTU interfaces“BDI” on page 50 (Backward Defect Indication,OTN)


Chapter 2: Alarms and Conditions

Table 18: BTI7800 Alarms and Conditions (continued)


Yes (true)Major• DOL optical servicechannels

• Terminal amplifierOptical SupervisoryChannels

“ContComS” on page 51 (ControlCommunications Failure, Span Section)

No (false)Major• Management modules

• Traffic modules

“DiskHighUsage” onpage 53 (DiskHighUsage)

Yes (true)MajorAC PEM“EnvCurrentHighTh”onpage54(CurrentAboveHigh Temperature)

Yes (true)MajorAC PEM“EnvCurrentLowTh”onpage55 (CurrentBelowLow Temperature)

Yes (true)Major• PEMs

• Fanmodules

• Management modules

• Traffic modules

“EnvTempHighTh” on page 56 (EnvironmentTemperature Above High Threshold)

Yes (true)Not alarmed• PEMs

• Fanmodules


• Traffic modules

“EnvTempLowTh” on page 58 (EnvironmentTemperature Above Low Threshold)

Yes (true)Major• AC PEMs

• Traffic modules

“EnvVoltHighTh” on page 60 (EnvironmentVoltage Above High Threshold)

Yes (true)Major• AC PEMs

• Traffic modules

“EnvVoltLowTh” on page 62 (EnvironmentVoltage Below Low Threshold)

Yes (true)MajorUFM6modules“EqptBrownout” on page 63 (EquipmentBrownout)

Depends on cause ofalarm

MajorTraffic modules“EqptComm” on page 64 (EquipmentManagement Communications Failure)

Yes (true)Major• UFMmodules

• BICmodules

“EqptDgrd” on page 66 (Equipment Degrade)

Yes (true)Critical• Equipment


• Traffic modules

• Pluggable transceivers

“EqptFail” on page 67 (Equipment Failure)







• Traffic modules


“EqptMism”onpage69(EquipmentMismatch)



• Traffic modules


“EqptMiss” on page 71 (Equipment Missing)

Yes (true)MajorFanmodule“FanSpeedLowTh” on page 73 (Fan SpeedBelow Threshold)

Yes (true)Major• DOL ports


“FECI” onpage75 (Far-EndNodeConfigurationMismatch)

Yes (true)Major• DOL ports


“FEIM” onpage 77 (Far-EndNode IdentificationMismatch)

No (false)Not alarmedManagement modules“FirmUpgrdInProg”onpage79(AutomaticShelfManagement Firmware Upgrade in Progress)

No (false)MajorManagement modules“FirmUpgrdFail”onpage79(ShelfManagementFirmware Upgrade Failed)

No (false)MajorManagement modules“FirmUpgrdReqd” on page 80 (FirmwareUpgrade Required)

No (false)Not alarmedWavelength protectionports

“Forced” on page 81 (Forced Protection SwitchActive)

No (false)MajorEthernet interfaces“HighBer” on page 81 (High Bit-Error Rate)

No (false)MajorPluggable transceivers“InvUnknown”onpage83(InventoryUnknown)

No (false)MajorQSFP28 pluggabletransceivers

“InventoryUnsupp” on page 84 (InventoryUnsupported)

Yes (true)Major• Management modules

• DOL optical servicechannels

“IsisAdjDown” on page 85 (IS-ISAdjacencyDown:)





Yes (true)Critical• Optical channelinterfaces

• OTNOTU interfaces

• Ethernet interfaces

• SONET/SDH interfaces

• Wavelength channels

“LaserFail” on page 86 (Laser Fail)

No (false)Major• Optical channelinterfaces





“LaserTempHighTh” on page 89 (LaserTemperature Above High TemperatureThreshold)






“LaserTempLowTh” on page 91 (LaserTemperature Below Low TemperatureThreshold)

Yes (true)CriticalOTN ODU interfaces“LCK” on page 94 (Locked, ODU)

No (false)Not alarmedEthernet interfaces“LF” on page 96 (Local Fault)

No (false)Not alarmedWavelength protectionports

“Lockout” on page 97 (Lockout of Protection)




“LOF” on page 97 (Loss of Frame)

Yes (true)CriticalOptical channel interfaces“Lolck” on page 99 (Loss of Lock)

Yes (true)Critical• DOL PRE ports

• DOL optical servicechannels

• DOL optical multiplexsections

• DOL optical channels

• Wavelength protectionports

• Terminal amplifier ports

“LoLightRx”onpage 101 (Lossof Light, Receive)

Yes (true)MajorDOL optical channels“LoLightTx”onpage105(LossofLight,Transmit)

Yes (true)CriticalOTN OTU interfaces“LOM” on page 106 (Loss of Multiframe)










“LOS” on page 107 (Loss of Signal)

Yes (true)CriticalDOL ports“LoSpecRx” on page 110 (Loss out ofSpecification, Receive)

Yes (true)CriticalEthernet interfaces“LoSync” on page 111 (Loss of Synchronization)

No (false)Not alarmed• OTNOTU interfaces



“LPBK” on page 112 (Loopback Operated)


• Traffic modules

“MemHighUsage” on page 114 (Memory HighUsage)

No (false)Major• 400G Coherent MSAXCVR

• OTNOTU4 lineinterfaces

“ModTempHighTh” on page 114 (ModuleTemperature Above High Threshold)

No (false)Major• 400G Coherent MSAXCVR


“ModTempLowTh” on page 116 (ModuleTemperature Below Low Threshold)

Yes (true)Critical• 400G Coherent MSAXCVR


“ModTempShutdown” on page 117 (ModuleTemperature Shutdown)

Yes (true)Not alarmedSDH interfaces“MS-AIS” on page 118 (Multiplex Section AlarmIndication Signal, SDH)

No (false)Not alarmedSDH interfaces“MS-RDI” on page 119 (Multiplex SectionRemote Defect Indication, SDH)

Yes (true)Critical• BTI7814 chassis

• BTI7802 chassis

“NonCoLocatedController” on page 120(Controllers are in Different Chassis)

Yes (true)Minor• DOL optical servicechannels


“ObrHt”onpage 121 (OpticalBackreflectionHighThreshold Exceeded)





Yes (true)Not alarmedDOL optical channels“OchAis” on page 123 (Alarm Indication Signal,OCH)

Yes (true)CriticalDOL optical channels“OchOci” on page 124 (Open ConnectionIndication, OCH)

Yes (true)CriticalDOL optical channels“OchUeq” on page 125 (OCH Unequipped)

Yes (true)CriticalOTN ODU interfaces“OCI”onpage 126(OpenConnection Indication,ODU)

Yes (true)Not alarmedOTN interfaces“ODU-AIS” on page 128 (ODUAlarm IndicationSignal)

Yes (true)Not alarmedDOL optical multiplexsections

“OmsAis”onpage 130(Alarm IndicationSignal,OMS)

Yes (true)Major• BTI7814 chassis

• BTI7802 chassis

“OneCableDisconnected” on page 132 (OneMulti-Chassis Cable Disconnected)






“OprHighTh” on page 133 (Optical PowerReceived Above High Threshold)






“OprLowTh” on page 135 (Optical PowerReceived Below Low Threshold)






“OptHighTh” on page 138 (Optical PowerTransmitted Above High Threshold)






“OptLowTh” on page 140 (Optical PowerTransmitted Below Low Threshold)





Yes (false)Not alarmedOTNOTU interfaces“OTU-AIS” on page 143 (OTU Alarm IndicationSignal)


• Traffic modules

“PartitionFault”onpage 144(DiskPartitionFaultDetected)

Yes (true)MinorDOL optical channels“PosRxHigh” on page 145 (Receive Power Outof Specification, High)

Yes (true)Major• DOL optical multiplexsections

• DOL optical channels

“PosRxLow”onpage 147 (ReceivePowerOutofSpecification, Low)

Yes (true)CriticalDOL optical channels“PosTxHigh” on page 149 (Transmit Power Outof Specification, High)

Yes (true)CriticalDOL optical channels“PosTxLow” on page 150 (Transmit Power Outof Specification, Low)

Yes (true)CriticalPEM“PowerAbsent” on page 151 (No PowerAvailable)

No (false)Not alarmed• OTNOTU interfaces



“PRBS” on page 152 (PRBS Test Activated)

No (false)MinorOptical channel interfaces“PreFecBerTh” on page 153 (Pre-FEC Bit ErrorRate Above High Threshold)

Yes (true)CriticalOTN ODU interfaces“PyldMism” on page 155 (Payload Mismatch)

No (false)Not alarmedSONET interfaces“RDI-L” on page 157 (RemoteDefect Indication,Line)

No (false)Not alarmedEthernet interfaces“RF” on page 158 (Remote Fault)

Yes (true)MajorManagement modules“ScmNmiDown”onpage159(SystemControllerManagement Interface Down)

Yes (true)CriticalManagement modules“ScmNoNmConn” on page 161 (No NetworkManagement Connectivity on SCM)

No (false)Minor• OTNOTU interfaces


“SD” on page 162 (Signal Degrade)

No (false)Critical• OTNOTU interfaces


“TIM” on page 163 (Trace Identifier Mismatch)





Yes (true)MinorTerminal amplifier lineports

“TlossRxHt” on page 165 (Loss Above HighThreshold, Receive)

Yes (true)MinorTerminal amplifier lineports

“TlossRxLt” on page 166 (Loss Below LowThreshold, Receive)

Yes (true)Minor• Management modules

• Traffic modules

“UPGRD” on page 167 (Upgrade in Progress)

AirFilterAbsence

Table 19: AlarmDetails

DescriptionParameter

AirFilterAbsenceCode

Air Filter Absent: The air filter required for operation of the chassis has not been detected inthe chassis.

Description/Cause

BTI7800 chassis (see table below).

NOTE: This alarm is supported on the BTI7814 chassis only.

Entities Affected

MajorDefault Severity

No (false).Service Affecting

See “Clearing an AirFilterAbsence Alarm” on page 44.Alarm Clearing

–Related Fault Hierarchy

Table 20: BTI7800 Chassis

Fault Indicator

Entity Name StatusIndicatorEquipment

See equipment specifications in theBTI7800Series Hardware Overview and InstallationGuide.

BTI7814chassis:<1 | 2>

Clearing an AirFilterAbsence Alarm

NOTE: Followallapplicablesafety requirementsasdescribed in theBTI7800Series Hardware Overview and Installation Guide.



NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore installing equipment in the chassis.

1. Confirm whether an air filter is present in the chassis.

• If an air filter is present, go to 2.

• If an air filter is not present, go to 3.

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

3. Install an air filter in the chassis.

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 21: Condition Details


ais-lCode

Alarm Indication Signal–Line (AIS-L), SONET: The local interface has received an AIS-Lsignal from the NE at the far end of the fiber, indicating that no SONET signal is beingtransmitted upstream of (and toward) the local NE. See also “Maintenance Signaling” onpage 33.

Description

SONET (OC192, WAN PHY OC192) interfaces (see table below).Entities Affected

Not alarmed.Default Severity

Yes (true).Service Affecting

See “Clearing an AIS-L Condition” on page 46.Condition Clearing

See “OC192, WAN PHY Over OC192 Interface Fault Hierarchy” on page 29.Related Fault Hierarchy



Table 22: SONET (OC192,WANPHYOC192) Interfaces

Fault Indicator

Entity Name StatusIndicatorModule

––12x SFP+ BICoc192:<chassis>/<slot>/<subslot>/<port>

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

Clearing an AIS-L Condition


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

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



aprCode

Automatic Power Reduction: For safety reasons, the local port has automatically reducedlaser power. Formore information aboutAPR, see theBTI7800Series SoftwareConfigurationGuide.

Description

• DOL ports (see respective table below).

• Terminal amplifier client and DCM ports (see respective table below).

Entities Affected

A fiber cut has been detected.Possible Cause

CriticalDefault Severity


See:

• Clearing an APR Alarm (PRE Port) on page 47

• Clearing an APR Alarm (terminal Amplifier Port) on page 48

Alarm Clearing



Table 23: AlarmDetails (continued)


See:



Related Fault Hierarchy

Table 24: DOL Ports

Fault Indicator


OnFault LED, PRE portPREport:<chassis>/<slot>/1/PRE

Table 25: Terminal Amplifier Ports

Fault Indicator


OnFault LED, DCM portAMP1client:<chassis>/<slot>/1/<portNum>

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

Clearing an APR Alarm (PRE Port)


1. Check for a “LoLightRx” on page 101 alarm on the host module's PRE In port.

2. Inspect the fiber at the following locations, and ensure that the fiber is intact,

thoroughly clean, and correctly connected:

• Between the PREmodule's Out port and the host module's PRE In port.

• Between the host module's PRE Out port and the PREmodule's In port.

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)


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 DCMOut port, check for a “LoLightRx” on page 101

alarm on the DCM In port.

2. Inspect the fiber, andensure that it is intact, thoroughly clean, andcorrectly connected.

3. Check for alarms on the terminal amplifier line port.



APSD



apsdCode

Automatic Power Shutdown: The local port has automatically shut down its laser becauseeither the optical power received has dropped below the Loss of Light, Receive threshold orAPSD 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.

Description


• Terminal amplifier line ports (see respective table below).

Entities Affected

• The fiber connection is poor.

• There is a problemwith the fiber.

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

Possible Causes







See:

• Clearing an APSD Alarm (DOL Port) on page 49

• Clearing an APSD Alarm (terminal Amplifier Line Port) on page 50

Alarm Clearing

See:




Table 27: DOL Ports

Fault Indicator


OnFault LED, L1 portROADM2 or ILAport:<chassis>/<slot>/0/L1

Fault LED, C<n> portport:<chassis>/<slot>/0/C<n>

where the range of n depends on themodule.

Table 28: Terminal Amplifier Line Ports

Fault Indicator


OnFault LED, Line portAMP1line:<chassis>/<slot>/1/<portNum>

Clearing an APSD Alarm (DOL Port)


1. Check for and clear the following alarms and conditions:

• “LoLightRx” on page 101 raised against the DOL OSC and the DOL OMS

• “ContComS” on page 51 raised against the DOL OSC

• “OmsAis” on page 130 raised against the DOL OMS

2. Check for alarms on the DOL port.


• If the alarm does not clear, go to the next step.



3. Check for and clear an APSD alarm on the NE at the far-end of the fiber.

4. Check for alarms on the local DOL port.



Clearing an APSD Alarm (terminal Amplifier Line Port)


1. Check whether an “LoLightRx” on page 101 alarm has been raised against the input

amplifier Optical Supervisory Channel on the line port, and clear the alarm if it exists.

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



3. Check for and clear an APSD alarm on the far-end NE.

4. Check for alarms on the local terminal amplifier line port.



BDI



bdiCode

Backward Defect Indication, OTN: The local interface has received a BDI signal from the NEat the far endof the fiber, indicating that noOTNOTUsignal is being transmitteddownstreamof (and away from) the local NE. (See also “Maintenance Signaling” on page 33.)

Description/Cause

OTNOTU interfaces (see respective table below).Entities Affected



Table 29: Condition Details (continued)




See “Clearing a BDI Condition” on page 51.Condition Clearing

See “OTN Interface Fault Hierarchy” on page 28.Related Fault Hierarchy

Table 30: OTNOTU Interfaces

Fault Indicator


OnFault LED, 200G line portUFM6otu4:<chassis>/<slot>/<2>/<1>/<subport.och.tributary>

OnFault LED, 100G line portUFM4otu4:<chassis>/<slot>/<1>/<1>

Fault LED, 100G port1x CFP BICotu4:<chassis>/<slot>/<subslot>/<port>

Fault LED, 10G port12x SFP+ BICotu2:<chassis>/<slot>/<subslot>/<port>

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

NOTE: Supported on UFM3 only.

Clearing a BDI Condition


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




ContComS



contComSCode





Control Communications Failure, Span Section: Control communications with the NE ateither end of the span section have failed.

Description

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

• DOL optical service channels (see respective table below).

• Terminal amplifier Optical Supervisory Channels (see respective table below).

Entities Affected



See “Clearing a ContComS Alarm” on page 52.Alarm Clearing

See:




Table 32: DOLOptical Service Channels (OSCs)

Fault Indicator


OnFault LED, L1 portROADM2 or ILAosc:<chassis>/<slot>/0/L1

Fault LED, C<n> portosc:<chassis>/<slot>/0/C<n>


Table 33: Terminal Amplifier Optical Supervisory Channels (OSCs)

Fault Indicator


––AMP1osc:<chassis>/<slot>/1/<portNum>.<oscNum>

Clearing a ContComSAlarm


1. Check for and clear alarms on OSC entities at both the local and far-end NEs.



2. Check the far-end NE for conditions indicating amodule reset.

3. Check for alarms on the local OSC.



DiskHighUsage



diskHighUsageCode

Disk High Usage.Description

Management and traffic modules (see respective table below).Entities Affected



This alarm indicates that disk usage on themodule has exceeded 90%. For informationabout clearing this alarm, contact your next level of support.

Alarm Clearing


Table 35: Management and Traffic Modules

Fault Indicator


See “BTI7800 Series Module and BIC LEDBehavior” on page 181.

CMMcmm:<chassis>/<slot>

UFMufm:<chassis>/<slot>

ROADM2roadm:<chassis>/<slot>

ILAila:<chassis>/<slot>

AMP1amp:<chassis>/<slot>

WPS4wps:<chassis>/<slot>



EnvCurrentHighTh



envCurrentHighThCode

Current Above High Threshold: The output current at the AC power entry module (PEM) isabove the high-current threshold. For information, see “Output-current Thresholds” onpage 172.

Description/Cause

Equipment (see respective table below).Entities Affected



See “Clearing an EnvCurrentHighTh Alarm” on page 54.Alarm Clearing

See “Environment Fault Hierarchy” on page 26.Related Fault Hierarchy

Table 37: Equipment

Fault Indicator


See the PEM specifications in the BTI7800Series Hardware Overview and InstallationGuide.

AC PEMpem:<chassis>/<slot>

Clearing an EnvCurrentHighTh Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore reseating (removing and reinstalling) or replacing equipment.

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

show environment current

2. Reseat the PEM.





3. Replace the PEM.

4. Check for alarms on the PEM.



EnvCurrentLowTh



envCurrentLowThCode

Current Below Low Threshold: The output current at the AC power entry module (PEM) isbelowthe low-current threshold.For information, see “Output-currentThresholds”onpage 172.

Description/Cause




See “Clearing an EnvCurrentLowTh Alarm” on page 55.Alarm Clearing


Table 39: Equipment

Fault Indicator




Clearing an EnvCurrentLowTh Alarm





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

show environment current

2. Reseat the PEM.



3. Replace the PEM.

4. Check for alarms on the PEM.



EnvTempHighTh



envTempHighThCode

Environment Temperature Above High Threshold: The temperature at the equipment ormodule has exceeded the high temperature threshold. For information, see “TemperatureThresholds - Equipment and Traffic Modules” on page 169.

Description/Cause

• Equipment (see respective table below).

• Management and traffic modules (see respective table below).

Entities Affected



See “Clearing an EnvTempHighTh Alarm” on page 57.Alarm Clearing


Table 41: Equipment

Fault Indicator



PEMpem:<chassis>/<slot>

Cooling modulefan:<chassis>/<slot>




Fault Indicator





BICbic:<chassis>/<slot>/<subslot>





Clearing an EnvTempHighTh Alarm


NOTE: Refer to the BTI7800 Series Software Configuration Guide beforerebooting a traffic module or to the BTI7800 Series Hardware Overview andInstallation Guide before reseating (removing and reinstalling) or replacingequipment or traffic modules.

1. Retrieve environment information to view the temperature reading for the equipment

or traffic module:

show environment temperature

2. Check for and clear a “FanSpeedLowTh” on page 73 alarm on each cooling module

installed in the chassis.

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



4. Ensure that theambient temperature iswithin thespecified range for chassisoperation.

For information, see the BTI7800 Series Hardware Overview and Installation Guide.

5. Check for alarms on the affected equipment or traffic module.





6. Do the following:

• If the alarm is raised against equipment, reseat the equipment.

• If the alarm is raisedagainst a trafficmodule, performawarm reboot of themodule.

7. Check for alarms on the equipment or module.



8. Replace the equipment or module.




EnvTempLowTh



envTempLowThCode

Environment Temperature Above Low Threshold: The temperature at the equipment ormodule is higher than the temperature at the low end of the high-temperature thresholdrange. For information, see “Temperature Thresholds - Equipment and Traffic Modules” onpage 169.

Description/Cause



Entities Affected



See “Clearing an EnvTempLowTh Condition” on page 59.Condition Clearing




Table 44: Equipment

Fault Indicator


––PEMpem:<chassis>/<slot>



Fault Indicator










Clearing an EnvTempLowTh Condition



1. Retrieve environment information to view the temperature reading for the equipment

or traffic module:

show environment temperature














EnvVoltHighTh



envVoltHighThCode

EnvironmentVoltageAboveHighThreshold: The voltageon theequipment (PEM)ormoduleexceeds the high-voltage threshold. For information, see “Voltage Thresholds” on page 172.

CAUTION: Continued operation might cause equipment damage.

Description/Cause


• Traffic modules (see respective table below).

Entities Affected



See “Clearing an EnvVoltHighTh Alarm” on page 61.Alarm Clearing


Table 47: Equipment

Fault Indicator






Table 48: Traffic Modules

Fault Indicator






Clearing an EnvVoltHighTh Alarm



1. Retrieveenvironment information to viewvoltage readings for theequipmentor traffic

module:

show environment voltage













EnvVoltLowTh



envVoltLowThCode

EnvironmentVoltageAboveHighThreshold: The voltageon theequipment (PEM)ormoduleis below the low-voltage threshold. For information, see “Voltage Thresholds” on page 172.


Description/Cause



Entities Affected



See “Clearing an EnvVoltLowTh Alarm” on page 63.Alarm Clearing


Table 50: Equipment

Fault Indicator





Fault Indicator








Clearing an EnvVoltLowTh Alarm



1. Retrieveenvironment information to viewvoltage readings for theequipmentor traffic

module:





3. Check for alarms on the equipment or module:







EqptBrownout



eqptBrownoutCode

Equipment Brownout: A brownout condition has been detected on a UFM6 that is installedin a BTI7800 Series chassis powered by a DC power entry module (PEM).


Description

UFMmodules (see respective table below).

NOTE: This alarm is supported on UFM6modules only.

Entities Affected





The 48 Vdc voltage supply to a UFM is lower than theminimum voltage threshold of thechassis, but not lower than the power-off threshold of the PEM.

Possible Cause



See “Clearing an EqptBrownout Alarm” on page 64.Alarm Clearing


Table 53: UFMModules

Fault Indicator



UFM6ufm:<chassis>/<slot>

Clearing an EqptBrownout Alarm


1. Retrieve environment information to view voltage data for the UFM6 and each PEM

installed in the chassis:


2. Check for and clear alarms raised against the PEMs, and ensure that they are properly

seated and connected to power.

3. Check for alarms on the UFM6.



EqptComm



eqptCommCode





Equipment Management Communications Failure: The CMM is not able to communicatewith the equipment.

Description/Cause

Traffic modules (see respective table below).Entities Affected


Depends on reason alarm has been raised.Service Affecting

See “Clearing an EqptCommAlarm” on page 65.Alarm Clearing

See “Equipment Fault Hierarchy” on page 25.Related Fault Hierarchy


Fault Indicator









Clearing an EqptCommAlarm


NOTE: Refer to the BTI7800 Series Software Configuration Guide beforerebooting an active CMM.

1. Perform awarm reboot of the active CMM, and then check for alarms on the affected

module.





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

module.



EqptDgrd



eqptDgrdCode

Equipment Degrade: Initialization of a module has failed.Description/Cause

Traffic modules (see respective table below).Entities Affected



See “Clearing an EqptDgrd Alarm” on page 66.Alarm Clearing



Fault Indicator




1x CFP BIC or 12xSFP+ BIC

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

Clearing an EqptDgrd Alarm


NOTE: Refer to theBTI7800SeriesSoftwareConfigurationGuidebeforeeitherrebooting or changing the administrative status of equipment.




• For a UFMmodule, perform a cold reboot of the module.

• For a BICmodule, administratively disable the module, and then administratively

enable it.

2. Check for alarms on themodule.



EqptFail

Table 58: AlarmDetails.


eqptFailCode

Equipment Failure: A hardware self-test has detected faulty equipment.Description/Cause



• Pluggable transceivers (see respective table below).

Entities Affected



See “Clearing an EqptFail Alarm” on page 68.Alarm Clearing


Table 59: Equipment

Fault Indicator



CAPcap:<chassis>/<slot>


ESLesl:<chassis>/<slot>





Fault Indicator










Table 61: Pluggable Transceivers

Fault Indicator

Entity Name StatusIndicatorTransceiver

OnFail LED, transceiver portCFP,QSFP+,QSFP28,SFP+

<transceiver-type>:<chassis>/<slot>/<subslot>/<port>

where transceiver-type corresponds to the type oftransceiver installed in theport; for example, cfp, qsfp,qsfp28, or sfpPlus.

Fail LED, PRE portPREpre:<chassis>/<slot>

Clearing an EqptFail Alarm



1. Perform a cold reload (system reload cold) of the failed equipment.

2. Check for alarms.





3. Reseat the equipment (equipment, traffic module, or pluggable transceiver).

4. Check for alarms.



5. Replace the equipment.

6. Check for alarms on the equipment.



EqptMism



eqptMismCode

Equipment Mismatch: The installed equipment does not match the equipment provisionedfor the slot or subslot.

Description/Cause




Entities Affected



See “Clearing an EqptMism Alarm” on page 70.Alarm Clearing


Table 63: Equipment

Fault Indicator









Fault Indicator










Fault Indicator





Clearing an EqptMismAlarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing equipment.

1. Retrieve equipment-provisioning information:

show equipment


• Modify theprovisionedsettings so that theymatch thoseof the installedequipment

(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



eqptMissCode

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




Entities Affected



See “Clearing an EqptMiss Alarm” on page 72.Alarm clearing


Table 67: Equipment

Fault Indicator


––Cooling modulefan:<chassis>/<slot>






Fault Indicator


––CMMcmm:<chassis>/<slot>








Fault Indicator


––CFP,QSFP+,QSFP28,SFP+



––PREpre:<chassis>/<slot>

Clearing an EqptMiss Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore installing equipment.



1. Retrieve inventory and provisioned-equipment information:

show inventoryshow equipment

2. Confirmwhether theequipment (equipment, trafficmodule, or pluggable transceiver)

is present in the slot or subslot.

• If the equipment is present in the slot or subslot, go to 3.

• If the equipment is not present in the slot or subslot, go to 4.

3. Ensure that the equipment is properly seated in the slot or subslot, and then go to 5.

4. Install themissing equipment, ensuring that its attributesmatch the attributes of the

equipment provisioned for the slot or subslot. For information, see the BTI7800

Hardware Overview and Installation Guide.




FanSpeedLowTh



fanSpeedLowThCode

FanSpeedBelowThreshold: The fan speedof the coolingmodule is below the low threshold.For information, see “Fan-speed Thresholds” on page 172.

Description


• The cooling module is faulty.

• The power entry module is faulty.

Possible Cause



See “Clearing a FanSpeedLowTh Alarm” on page 74.Alarm Clearing




Table 71: Equipment

Fault Indicator


See cooling module specifications in theBTI7800 Series Hardware Overview andInstallation Guide.


Clearing a FanSpeedLowTh Alarm



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

3. Check for and clear alarms raised against each PEM, and then check for alarms on

the cooling module.



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



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





FECI



feciCode

Far-EndNodeConfiguration IDMismatch:Either theconfigurationof theDOLfiber-connectionis not supported or the expected far-end degree and group values provisioned on a terminalamplifier Optical Supervisory Channel do not match the actual (far-end) degree and groupvalues.

Description/Cause



Entities Affected



See:

• Clearing a FECI Alarm (DOL Port) on page 76

• Clearing a FECI Alarm (terminal Amplifier OSC) on page 76

Alarm Clearing

See:




Table 73: DOL Ports

Fault Indicator






Fault Indicator





Clearing a FECI Alarm (DOL Port)


1. RetrieveDOLfiber-connection information to identify theunsupported fiber-connection

configuration:

show dol fiber-conn

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)


1. Retrieve information for the OSC:

show amp

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

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.

4. Check for alarms on the OSC.





FEIM



feimCode

Far-End Node Identification Mismatch: Either the provisioned endpoints of a DOL fiberconnection do not match the actual endpoints or the expected far-end system informationprovisioned on a terminal amplifier Optical Supervisory Channel does not match the actual(far-end) system information

Description/Cause



Entities Affected



See:

• Clearing a FEIM Alarm (DOL Port) on page 78

• Clearing a FEIM Alarm (terminal Amplifier OSC) on page 78

Alarm Clearing

See:




Table 76: DOL Ports

Fault Indicator






Fault Indicator





Clearing a FEIM Alarm (DOL Port)


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

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)


1. Retrieve information for the OSC:

show amp

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

3. Delete the OSC at either the local or far-end NE, and reprovision the OSC so that the

expectedandactual system IDand/or IPaddress valuesare the same. For information,

see the BTI7800 Series Software Configuration Guide.

4. Check for alarms on the OSC.





FirmUpgrdInProg



firmUpgrdInProgCode

AutomaticShelfManagement FirmwareUpgrade inProgress: A shelfmanagement (SHMM)firmware upgrade is in progress.

Description/Cause

Management modules (see respective table below)Entities Affected



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

Condition Clearing


Table 79: Management Modules

Fault Indicator




FirmUpgrdFail



firmUpgrdFailCode

Shelf Management Firmware Upgrade Failed: A shelf management (SHMM) firmwareupgrade (manual or automatic) has failed.

Description/Cause

Management modules (see respective table below).Entities Affected



See “Clearing a FirmUpgrdFail Alarm” on page 80.Alarm Clearing







Fault Indicator




Clearing a FirmUpgrdFail Alarm

1. Reattempt the firmware upgrade. For information, see the BTI7800 Series Hardware

Overview and Installation Guide.

2. Check for alarms on the CMM.



FirmUpgrdReqd



firmUpgrdReqdCode

Firmware Upgrade Required: The version of firmware running on the Chassis ManagementModule (CMM) does not match the version of the Shelf Management (SHMM) firmware.

Description/Cause




This alarm clears when the firmware is successfully upgraded. For information, see theBTI7800 Series Software Configuration Guide.

Alarm Clearing





Fault Indicator




Forced



forcedCode

Forced Protection Switch Active: The operator has forced a protection switch.Description/Cause

Wavelength protection ports (see respective table below).Entities Affected



This condition clearswhen theprotection switch is released. For information, see theBTI7800Series Software Configuration Guide.

Condition Clearing


Table 85:Wavelength Protection Ports

Fault Indicator


––WPS4wpsport:<chassis>/<slot>/L<n>

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

HighBer



highBerCode

High Bit-Error Rate: The local port has detected a bit-error rate in the received signal that is10-4 or greater.

Description





Ethernet interfaces (see respective table below).Entities Affected

• Either the fiber link or the optical connection is degraded.

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

Possible Causes



See “Clearing a HighBer Alarm” on page 82.Alarm Clearing

See “Ethernet Interface Fault Hierarchy” on page 29.Related Fault Hierarchy

Table 87: Ethernet Interfaces

Fault Indicator


OnFault LED, 100G port1x CFP BIC100ge:<chassis>/<slot>/<subslot>/<port>/<subport>

Fault LED, 100G portUFM6100ge:<chassis>/<slot>/<1>/<port>

Fault LED, 10G portUFM610ge:<chassis>/<slot>/<1>/<port>/<subport>

Fault LED, 10G port12x SFP+ BIC10ge:<chassis>/<slot>/<subslot>/<port>/<subport>

Clearing a HighBer Alarm




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

MinimumThreshold and Optical Power ReceivedMaximumThreshold values.

show interface name:identifier detail

NOTE: For detailed transceiver specifications, see the BTI7800 SeriesHardware Overview and Installation Guide.

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

correctly connected to the port.

3. Ensure that no unintentional attenuation has been added to the fiber.

4. Check for alarms on the interface.



InvUnknown



invUnknownCode

Inventory Unknown: The installed pluggable transceiver is not readable.Description/Cause

Pluggable transceivers (see respective table below).Entities Affected



See “Clearing an InvUnknown Alarm” on page 84.Alarm Clearing





Fault Indicator





Clearing an InvUnknown Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing a transceiver.

1. Replace the unknown transceiver with a readable transceiver.

2. Check for alarms on the port.



InventoryUnsupp



inventoryUnsuppCode

Inventory Unsupported: A QSFP28 transceiver is installed in a transceiver port that supportsonly QSFP+ transceivers.

Description/Cause

Pluggable transceivers (see respective table below).Entities Affected



See “InvUnknown” on page 83.Alarm Clearing





Fault Indicator


OnFail LED, 10G portQSFP28 pluggabletransceiver

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

Clearing an InventoryUnsupp Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing a transceiver.

1. Replace the QSFP28 transceiver with a supported QSFP+ transceiver.

2. Check for alarms on the port.



IsisAdjDown



isisAdjDownCode

IS-ISAdjacencyDown:An IS-ISadjacency isdownandno longerbeingconsidered for routing.

NOTE: This alarm can be raised only after an adjacency (neighbor) has been established.

Description

Management interfaces (see respective table below).Entities Affected

• A fiber is either cut or disconnected.

• Equipment (for example, the router ormodule) on the neighbor side is down; for example,it is being restarted.

Possible Causes



See “Clearing an IsisAdjDown Alarm” on page 86.Alarm Clearing






Table 93: Management Interfaces

Fault Indicator


OnFault LED, L1 portROADM2, ILAmgt:n

where n is an alphanumeric string.Fault LED, C<n> port


CMMsysmgt

Clearing an IsisAdjDown Alarm



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

and correctly connected to the port.

• Check the equipment on the neighbor side and ensure that it is powered on and

operating.

2. Check for alarms on themanagement interface.



LaserFail



laserFailCode

Laser Fail: The transmit laser of the transceiver has failed.Description/Cause





• Optical channel interfaces (see respective table below.)

• OTNOTU interfaces (see respective table below).

• Ethernet interfaces (see respective table below).

• SONET/SDH interfaces (see respective table below).

• Wavelength channels (see respective table below).

Entities Affected



See “Clearing a LaserFail Alarm” on page 88.Alarm Clearing

See “Common Fault Hierarchy - OTN and CBR Ports” on page 27.Related Fault Hierarchy

Table 95: Optical Channel Interfaces

Fault Indicator


OnFault LED, 200G line portUFM6och:<chassis>/<slot>/<2>/<1>/<subport.och>


Fault Indicator










Fault Indicator






Table 98: SONET/SDH Interfaces

Fault Indicator


OnFault LED, 10G port12x SFP+ BICoc192:<chassis>/<slot>/<subslot>/<port>


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

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

Table 99:Wavelength Channels

Fault Indicator


OnFault LED, 100G port1x CFP BIC1channel:<chassis>/<slot>/<subslot>/<port.channel>

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

Clearing a LaserFail Alarm


NOTE: Refer to the BTI7800 Series Software Configuration Guide beforerebooting a traffic module or to the BTI7800 Series Hardware Overview andInstallation Guide replacing a traffic module or transceiver.



1. Perform a cold reboot:

• If the alarm is raised against a line-port interface provisioned on an integratedMSA

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.




3. Replace the either the UFM or the pluggable transceiver:

• If the alarm is raised against a line-port interface provisioned on an integratedMSA

transceiver, replace the UFM.

• If the alarm is raised against a client-port interface provisioned on a pluggable

transceiver, replace the pluggable transceiver.




LaserTempHighTh



laserTempHighThCode

Laser Temperature Above High Temperature Threshold: The transmit laser temperature hasexceeded the high temperature threshold.

Description

• Optical channel interfaces (see respective table below).





Entities Affected

The transmit laser is malfunctioning.Possible Causes



See “Clearing a LaserTempHighTh Alarm” on page 91.Alarm Clearing





Fault Indicator




Fault Indicator








Fault Indicator







Fault Indicator









Fault Indicator




Clearing a LaserTempHighTh Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing a traffic module or a transceiver.

1. Optionally, retrievedetailed information for the interface toview the LaserTemperature

and Laser Temperature Max. Threshold values:


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



laserTempLowThCode

Laser Temperature Below Low Temperature Threshold: The transmit laser temperature hasfallen below the low temperature threshold.

Description










Entities Affected

The transmit laser is malfunctioning.Possible Causes



See “Clearing a LaserTempLowTh Alarm” on page 93.Alarm Clearing

See “Fault Masking and Hierarchies” on page 25.Related Fault Hierarchy


Fault Indicator




Fault Indicator










Fault Indicator







Fault Indicator






Table 111: Wavelength Channels

Fault Indicator




Clearing a LaserTempLowTh Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing a traffic module or a transceiver.



1. Optionally, retrievedetailed information for the interface toview the LaserTemperature

and Laser Temperature Min. Threshold values:



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




LCK



lckCode

Locked, ODU: The local interface has received anODU-LCK signal from the NE at the far endof the fiber, indicating that the connection at the transmitting interface is locked.

Description

OTNODU interfaces (see respective table below).Entities Affected

The transmitting OTN OTU interface at an upstream NE is either administratively disabledor in loopback mode.

Possible Causes



See “Clearing an LCK Alarm” on page 95.Alarm Clearing




Table 113: OTNODU Interfaces

Fault Indicator


OnFault LED, 200G line portUFM6odu4:<chassis>/<slot>/<2>/<1>/<subport.och.tributary>

odu2e:<chassis>/<slot>/<2>/<1>/<subport.och.tributary.sub-interface>

Fault LED, 100G line portUFM4odu4:<chassis>/<slot>/<1>/<1>

Fault LED, 100G line port1x CFP BICodu4:<chassis>/<slot>/<subslot>/<port>

odu2:<chassis>/<slot>/<subslot>/<port.sub-interface>

odu2e:<chassis>/<slot>/<subslot>/<port.sub-interface>


Fault LED, 10G port12x SFP+ BICodu2:<chassis>/<slot>/<subslot>/<port>

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


Clearing an LCK Alarm


1. Retrieve data for the transmitting OTU interface at the upstream NE to determine

whether it is either administratively disabled (AdminState = disabled ) or in loopback

mode ( Loopback = loopback )

show interface name:identifier

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.

3. Check for alarms on the local interface.





LF



lfCode

Local Fault: The local interface has received a local-fault signal from the NE at the far endof the fiber, indicating that no Ethernet signal is being transmitted upstreamof (and toward)the local NE. (See also “Maintenance Signaling” on page 33.)

Description




See “Clearing an LF Condition” on page 96.Condition Clearing



Fault Indicator


––1x CFP BIC100ge:<chassis>/<slot>/<subslot>/<port>/<subport>

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

UFM610ge:<chassis>/<slot>/<1>/<port>/<subport>

12x SFP+ BIC10ge:<chassis>/<slot>/<subslot>/<port>/<subport>

Clearing an LF Condition








Lockout



lockoutCode

Lockout of Protection: The operator has locked out a line port for protection.Description/Cause

Wavelength protection ports (see respective table below).Entities Affected



This condition clearswhen theprotection switch is released. For information, see theBTI7800Series Software Configuration Guide.

Condition Clearing


Table 117: Wavelength Protection Ports

Fault Indicator


––WPS4wpsport:<chassis>/<slot>/L<n>


LOF



lofCode

Loss of Frame: Either the frame-alignment process is in the out-of-frame (OOF) state or aseverely-errored-frame defect is present on an incoming signal.

Description




Entities Affected





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

• The far-end optical transmitter is faulty.

Possible Causes



See “Clearing an LOF Alarm” on page 99.Alarm Clearing

See:







Fault Indicator




Fault Indicator











Fault Indicator






Clearing an LOF Alarm




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




Lolck



lolckCode

Loss of Lock: The optical channel cannot lock on to the encoded signal received.Description

Optical channel interfaces (see respective table below).Entities Affected

• The encoding, modulation, or other configured parameter on the interface at the far-endNE does not match the configuration of the same parameter of the interface at the localNE.

• The signal-to-noise ratio is below specification.

Possible Causes







See “Clearing a Lolck Alarm” on page 100.Alarm Clearing



Fault Indicator



Clearing a Lolck Alarm


1. Retrieve information for both the local and far-end optical channel interfaces to view

configuration data:

show interface och:identifier detail

2. Correct the configuration settings where required. For information, see the BTI7800

Series Software Configuration Guide.

3. Retrieve statistics for the local and far-end optical channel interfaces to view the

values of all optical signal-to-noise ratio counters, and ensure that theOSNR iswithin

specification.

show statistics current och:identifier

4. If required, improve the signal-to-noise ratio.






LoLightRx



loLightRxCode

Loss of Light, Receive: The optical power received has dropped below the loss-of-lightthreshold.

Description/Cause

• DOL PRE Ports (see respective table below).


• DOL optical multiplex sections (see respective table below).

• DOL optical channels (see respective table below).

• Wavelength protection ports (see respective table below).

• Terminal amplifier ports (see respective table below).

Entities Affected



See:

• Clearing a LoLightRx Alarm (DOL Entity) on page 103

• Clearing a LoLightRx Alarm (wavelength Protection Port) on page 104

• Clearing a LoLightRx Alarm (terminal Amplifier Port) on page 104

Alarm Clearing

See:






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


Table 125: DOL PRE Ports

Fault Indicator


OnFault LED, PRE portPREport:<chassis>/<slot>/0/PRE

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




Fault Indicator


OnFault LED, L1 portROADM2 or ILAosc:<chassis>/<slot>/0/L1

Fault LED, C<n> portosc:<chassis>/<slot>/0/C<n>


Table 127: DOLOptical Multiplex Sections (OMSs)

Fault Indicator


OnFault LED, L1 portROADM2 or ILAoms:<chassis>/<slot>/0/L1<>

Fault LED, C<n> portoms:<chassis>/<slot>/0/C<n>


Table 128: DOLOptical Channels (OCHs)

Fault Indicator


––ROADM2och:<chassis>/<slot>/0/C<n>/<channel>

where the range of n depends on themodule andchannel is an alphanumeric string.

Table 129:Wavelength Protection Ports

Fault Indicator


OnFault LED, Line<n> portWPS4wpsport:<chassis>/<slot>/L<n>




Table 130: Terminal Amplifier Ports

Fault Indicator



OnFault LED, Line portline:<chassis>/<slot>/1/<portNum>

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

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

Clearing a LoLightRx Alarm (DOL Entity)


NOTE: In some ROADM network topologies with ILAs deployed, amplifiedspontaneous emissions (ASE)might accumulate sufficiently to cause thisalarm toclear onprovisionedbut unoccupiedoptical channels. (TheASEwillnot be high enough to affect optical performance, however.)

1. Retrieve statistics for theaffectedentity to view thevalueof the Opticalpower received

counter:

show statistics current name:identifier


• If thealarm is raisedagainst aPREport, refer to “DOLPortPowerAlarmThresholds”

on page 177, and then go to 3.

• If the alarm is raised against a DOLOSC, DOLOMS, or DOLOCH, refer to “DOLOSC

PowerandOpticalBackreflectionAlarmThresholds”onpage 174, “DOLOMSPower

AlarmThresholds” onpage 175, or “DOLOCHPowerAlarmThresholds” onpage 177,

and then go to 4.

3. Check for and resolve any of the following problems, and then go to 4:

• 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 eachmodule that is connected to the alarmed port.

• There is excessive loss on upstream patch fibers.

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.

5. Check for alarms on the local DOL entity.



Clearing a LoLightRx Alarm (wavelength Protection Port)


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 correctly connected to the port.

• Check for and clear all alarms on the upstream NE.

3. Check for alarms on the local port.



Clearing a LoLightRx Alarm (terminal Amplifier Port)


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 eachmodule that is connected to the alarmed port.




• The far-end port is administratively disabled.

3. Check for alarms on the local port.



LoLightTx



loLightTxCode

Loss of Light, Transmit: The optical power transmitted has dropped below the loss-of-lightthreshold.

Description/Cause

DOL optical channels (see respective table below).Entities Affected



See “Clearing a LoLightTx Alarm” on page 105.Alarm Clearing

See “DOL OCH Fault Hierarchy” on page 32.Related Fault Hierarchy


Fault Indicator


––ROADM2och:<chassis>/<slot>/0/L1/<channel>

where channel is an alphanumeric string.

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

where the range of n depends on themodule andchannel is an alphanumeric string.

Clearing a LoLightTx Alarm




NOTE: In some ROADM network topologies with ILAs deployed, amplifiedspontaneous emissions (ASE)might accumulate sufficiently to cause thisalarm toclear onprovisionedbut unoccupiedoptical channels. (TheASEwillnot be high enough to affect optical performance, however.)

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” on page 177:


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

connected.

3. Check for alarms on the DOL optical channel.



LOM



lomCode

Loss of Multiframe: Themultiframe alignment process is in the out-of-multiframe state.Description




Possible Causes



See “Clearing an LOM Alarm” on page 107.Alarm Clearing



Fault Indicator





Table 134: OTNOTU Interfaces (continued)

Fault Indicator







Clearing an LOMAlarm




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




LOS



losCode

Loss of Signal: The local port has detected a loss of received signal power.Description






Entities Affected





• The fiber input is disconnected.

• The far-end interface is not yet provisioned.

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

Possible Causes



See “LOS” on page 107.Alarm Clearing

See:



• Ethernet Interface Fault Hierarchy on page 29





Fault Indicator




Fault Indicator










Fault Indicator







Fault Indicator







Fault Indicator



1Monitoring and reporting of this alarm for a wavelength channel is supported only onmultiwavelength CFP transceivers.

Clearing an LOS Alarm




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

and fault free.



3. Check for and resolve the following problems:

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

• The far-end interface is not provisioned.

4. Check for alarms on the local interface



LoSpecRx



loSpecRxCode

LossoutofSpecification,Receive: Theoptical loss received isoutside thespecification range.Description

DOL ports (see respective table below).Entities Affected

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



See “Clearing a LoSpecRx Alarm” on page 110.Alarm Clearing

See “DOL Port Fault Hierarchy” on page 30.Related Fault Hierarchy

Table 142: DOL Ports

Fault Indicator





Clearing a LoSpecRx Alarm




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” on page 178:

show statistics current port:identifier

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

connected.




LoSync



loSyncCode

Loss of Synchronization: The signal received on the local interface is sufficiently degradedthat it cannot be synchronized.

Description


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


Possible Causes



See “Clearing a LoSync Alarm” on page 112.Alarm Clearing



Fault Indicator








Clearing a LoSync Alarm


1. Retrievedetailed information for the interface, andensure that the valueof the Optical

PowerRx counter iswithin the range indicatedby the OpticalPowerReceivedMinimum

Threshold and Optical Power ReceivedMaximumThreshold values.




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




LPBK



lpbkCode

Loopback Operated: A loopback test is active on the local port.Description/Cause




Entities Affected

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


This condition clears when the loopback is released. For information, see the BTI7800 SeriesSoftware Configuration Guide.

Condition Clearing





Fault Indicator


––UFM6otu4:<chassis>/<slot>/<2>/<1>/<subport.och.tributary>

––UFM4otu4:<chassis>/<slot>/<1>/<1>

1x CFP BICotu4:<chassis>/<slot>/<subslot>/<port>

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




Fault Indicator







Fault Indicator








MemHighUsage



memHighUsageCode

Memory High Usage.Description/Cause




This alarm indicates thatmemory usage on themodule has exceeded 90%. For informationabout clearing this alarm, contact your next level of support.

Alarm Clearing



Fault Indicator









ModTempHighTh



modTempHighThCode

Module Temperature Above High Threshold: The temperature of the MSA transceiver isabove the high-temperature threshold. For information, see “Temperature Thresholds -MSATransceivers” on page 171.

Description






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

• The output power of the MSA transceiver is excessive.

Possible Causes



See “Clearing a ModTempHighTh Alarm” on page 115.Alarm Clearing



Fault Indicator


OnFault LED, 100G line portUFM4otu4:<chassis>/<slot>/<subslot>/<port>

Clearing aModTempHighTh Alarm


1. Optionally retrieve statistics for the OTU4 interface to view the value of the Module

temperature parameter:

show statistics current otu4:identifier


• Either a coolingmodule is notpresent in the chassis or is presentbut is operationally

down or administratively disabled.

• A “FanSpeedLowTh” on page 73 alarm has been raised against a cooling module.

• An “EnvTempHighTh” on page 56 alarm has been raised against the UFM.

• Theambient temperature ishigher than thespecifiedoperating range for thechassis.







ModTempLowTh



modTempLowThCode

Module Temperature Below Low Threshold: The temperature of the MSA transceiver isbelow low-temperature threshold. For information, see “Temperature Thresholds - MSATransceivers” on page 171.

Description


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



See “Clearing a ModTempLowTh Alarm” on page 116.Alarm Clearing



Fault Indicator



Clearing aModTempLowTh Alarm


1. Optionally retrieve statistics for the OTU4 interface to view the value of the Module

temperature parameter:

show statistics current otu4:identifier

2. Retrieveenvironment information toviewdataonequipment temperature, andensure

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



modTempShutdownCode

Module Temperature Shutdown: The temperature of the MSA transceiver has exceeded thehigh-temperature-shutdown threshold, causing the transmit laser to shut down. Forinformation, see “Temperature Thresholds - MSA Transceivers” on page 171.

Description


The ambient temperature is excessively higher than the normal operating range of the MSAtransceiver.

Possible Causes



See “Clearing a ModTempShutdown Alarm” on page 117.Alarm Clearing



Fault Indicator



Clearing aModTempShutdown Alarm


NOTE: Refer to theBTI7800SeriesHardwareOverviewand InstallationGuidebefore replacing a traffic module.




• Either a coolingmodule is notpresent in the chassis or is presentbut is operationally

down or administratively disabled.

• A “FanSpeedLowTh” on page 73 has been raised against a cooling module.

• Theambient temperature ishigher than thespecifiedoperating range for thechassis.


2. Check for alarms on the OTU4 interface.



3. Replace the UFM4.




MS-AIS



ms-aisCode

Multiplex SectionAlarm IndicationSignal, SDH: The local port has received anMS-AIS signalfrom the NE at the far end of the fiber, indicating that no SDH signal is being transmittedupstream of (and toward) the local NE. (See also “Maintenance Signaling” on page 33.)

Description/Cause

SDH (STM64, WAN PHY STM64) interfaces (see respective table below).Entities Affected



See “Clearing an MS-AIS Condition” on page 119.Condition Clearing

See “STM64, WAN PHY Over STM64 Interface Fault Hierarchy” on page 30.Related Fault Hierarchy



Table 158: SDH (STM64,WANPHY STM64) Interfaces

Fault Indicator


––12x SFP+ BICstm64:<chassis>/<slot>/<subslot>/<port>


Clearing anMS-AIS Condition


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




MS-RDI



ms-rdiCode

MultiplexSectionRemoteDefect Indication,SDH:The local interfacehas receivedanMS-RDIsignal fromtheNEat the far endof the fiber, indicating thatnoSDHsignal is being transmitteddownstreamof (andaway from) the localNE. (Seealso “MaintenanceSignaling”onpage33.)

Description/Cause

SDH (STM64, WAN PHY STM64) interfaces (see respective table below).Entities Affected



See “Clearing an MS-RDI Condition” on page 120.Alarm Clearing





See “STM64, WAN PHY Over STM64 Interface Fault Hierarchy” on page 30.Related Fault Hierarchy

Table 160: SDH (STM64,WANPHY STM64) Interfaces

Fault Indicator


––12x SFP+ BICstm64:<chassis>/<slot>/<subslot>/<port>


Clearing anMS-RDI Condition


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




NonCoLocatedController



nonCoLocatedControllerCode

Controllers are in Different Chassis: The active CMMs in amulti-chassis configuration arenot located in the same chassis.

Description/Cause

Equipment (see respective table below).

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

Entities Affected



See “NonCoLocatedController” on page 120.Alarm Clearing






Table 162: Equipment

Fault Indicator



BTI7814 or BTI7802chassis:<1 | 2>

Clearing a NonCoLocatedController Alarm


1. Retrieve information for the hub and satellite chassis:

show system chassis

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

BTI7800 Series Software Configuration Guide.




ObrHt



obrHtCode

Optical Backreflection High Threshold Exceeded: The optical backreflection has exceededthe high threshold.

Description



Entities Affected

The fiber connection is poor.Possible Cause





MinorDefault Severity


See “Clearing an ObrHt Alarm” on page 122.Alarm Clearing

See:



.



Fault Indicator


Fault LED,L1 port

Fault LED, L1 portROADM2 or ILAosc:<chassis>/<slot>/0/L1


Fault Indicator



Clearing an ObrHt Alarm


1. Optionally, if the alarm is raised against a DOL OSC entity, refer to “DOL OSC Power

and Optical Backreflection Alarm Thresholds” on page 174 for optical-backreflection

threshold information.

2. Ensure that the span fiber at the Line output port is intact, thoroughly clean, and

correctly connected.

3. Ensure that the fiber connectors are compatible.



4. Ensure that any downstream fiber connections are thoroughly cleaned and correctly

connected, and that the span loss at the downstream node is in the supported range

for operation. Formore information about span loss, see theBTI7800 Series Software


5. Check for alarms on the affected OSC.



NOTE: The cleaning and reconnecting of fibers can increase (by severalminutes) the amount of time the system requires to re-evaluate opticalback-reflection ratio statistics for a DOL OSC entity and, therefore, showthe obrHt alarm as cleared.

OchAis



ochAisCode

Alarm Indication Signal (AIS), OCH: The local NE has received an OCH-AIS signal from thefar-endNE, indicating that no signal is being transmitted upstreamof (and toward) the localNE.

Description




See “Clearing an OchAis Condition” on page 124.Condition Clearing





Fault Indicator


––ROADM2och:<chassis>/<slot>/0L1/<channel>



where n depends on themodule and channel is analphanumeric string.

Clearing an OchAis Condition



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

upstream fibers are thoroughly cleaned and correctly connected.

3. Ensure that all upstream fibers are thoroughly clean and correctly connected.

4. Check for conditions on the DOL optical channel.



OchOci



ochOciCode

Open Connection Indication (OCI), OCH: The optical channel has received an OCH–OCIsignal from the NE at the far end of the fiber, indicating that there is a missing opticalcross-connect on an upstream node.

Description








See “Clearing an OchOci Condition” on page 125.Alarm Clearing



Fault Indicator




Clearing an OchOci Condition


1. If required, retrieve cross-connect information for the upstream node:

show dol och-xcon

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.

3. Check for conditions on the local DOL OCH.



OchUeq



ochUeqCode

OCH Unequipped: The downstream optical channel is not provisioned.Description/Cause








See “Clearing an OchUeq Alarm” on page 126.Alarm Clearing


Table 171: DOL Optical Channels (OCHs)

Fault Indicator




Clearing an OchUeq Alarm


1. Provision the DOL OCH on the downstream node. For information, see the BTI7800

Series Software Configuration Guide.

2. Check for alarms on the local DOL OCH.



OCI



ociCode





Open Connection Indication, ODU: The local interface has received an ODU-OCI signal fromthe far-endNE, indicating that an optical cross-connect is not present on an upstreamnode.

NOTE: The local interface that receives theODU-OCI signal raises this alarmonly if the localinterface is part of a cross-connect. If the local interface is not part of a cross-connect, thereceived ODU-OCI signal is ignored.

An interface transmits an ODU-OCI signal downstream if the interface is open (that is, notpart of any cross-connect).

FormultiplexedODU interfaces, the ODU-OCI signal is transmitted (and therefore received)on the containing ODU interface, not on the individual ODU sub-interfaces. The containingODU interface transmits the ODU-OCI signal if none of the contained ODU sub-interfacesis part of a cross-connect. The containing ODU interface stops transmitting the ODU-OCIsignal if at least one of the contained ODU sub-interfaces is part of a cross-connect. TheODU-OCI signal onmultiplexed interfaces does not indicate which specific sub-interface isopen (that is, not part of a cross-connect).

Description/Cause




See “Clearing an OCI Alarm” on page 128.Alarm Clearing





Fault Indicator












Clearing an OCI Alarm


1. Provision themissing cross-connect. For information, see theBTI7800SeriesSoftware





ODU-AIS



odu-aisCode





ODU Alarm Indication Signal: The local interface has received an ODU-AIS signal from theNE at the far end of the fiber, indicating that no OTNOTU or OTN ODU signal is beingtransmitted upstream of (and toward) the local NE. (See also “Maintenance Signaling” onpage 33.)

In addition to standard use of ODU-AIS signals, the BTI7800 originates an ODU-AIS signalin the following situations:

• Amultiplexed ODU sub-interface transmits an ODU-AIS signal when the sub-interfacedetects an ODTG tributary mismatch.

• On a UFM6, an optical channel transmits a default ODU4 signal containing ODU-AIS foreach ODU4 interface not created.

Description/Cause


• OTNODU interfaces (see respective table below).

Entities Affected



See “Clearing an ODU-AIS Condition” on page 130.Condition Clearing



Fault Indicator


––UFM4otu4:<chassis>/<slot>/<subslot>/<port>




Fault Indicator


––UFM6odu4:<chassis>/<slot>/<2>/<1>/<subport.och.tributary>


UFM4odu4:<chassis>/<slot>/<1>/<1>

1x CFP BICodu4:<chassis>/<slot>/<subslot>/<port>




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



Clearing an ODU-AIS Condition






OmsAis



OmsAisCode

Alarm IndicationSignal, OMS: The local NEhas received anOMS-AIS signal from the far-endNE, indicating that no signal is being transmitted upstream of (and toward) the local NE.

Description





DOL optical multiplex sections (see respective table below).Entities Affected



“Clearing an OmsAis Condition” on page 131Condition Clearing

See “DOL OMS Fault Hierarchy” on page 31.Related Fault Hierarchy


Fault Indicator


OnFault LED, L1 portROADM2 or ILAoms:<chassis>/<slot>/0/L1<>

Fault LED, C<n> portoms:<chassis>/<slot>/0/C<n>


Clearing an OmsAis Condition



2. Ensure that the far-end NE has at least one optical channel provisioned and

cross-connected.

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.

4. Check for conditions on the DOL OMS.





OneCableDisconnected

Table 179: Alarm/condition Details


oneCableDisconnectCode

One Multi-Chassis Cable Disconnected: A cable that connects two CMMs in amulti-chassisconfiguration is not connected to a CMM.

Description/Cause

Equipment (see respective table below).

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

Entities Affected



See “Clearing a OneCableDisconnected Alarm” on page 132.Alarm Clearing



Fault Indicator



BTI7814 or BTI7802chassis:<1 | 2>

Clearing a OneCableDisconnected Alarm


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

connected.






OprHighTh



oprHighThCode

Optical Power Received Above High Threshold: The optical power received is above the highthreshold.

Description






Entities Affected

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

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

Possible Causes



See “Clearing an OprHighTh Alarm” on page 135.Alarm Clearing



Fault Indicator






Fault Indicator








Fault Indicator







Fault Indicator







Fault Indicator





Table 186:Wavelength Channels (continued)

Fault Indicator



Clearing an OprHighTh Alarm










4. Add an attenuation pad in the optical path.




OprLowTh



oprLowThCode

Optical Power Received Below Low Threshold: The optical power received is below the lowthreshold.

Description










Entities Affected

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


Possible Causes



See “Clearing an OprLowTh Alarm” on page 137.Alarm Clearing



Fault Indicator




Fault Indicator










Fault Indicator







Fault Indicator







Fault Indicator




Clearing an OprLowTh Alarm












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





OptHighTh



optHighThCode

Optical Power Transmitted Above High Threshold: The optical power transmitted is abovethe high threshold.

Description






Entities Affected

The optical transmitter is faulty.Possible Cause



See “Clearing an OptHighTh Alarm” on page 140.Alarm Clearing





Fault Indicator




Fault Indicator








Fault Indicator







Fault Indicator









Fault Indicator




Clearing an OptHighTh Alarm




Optical Power Tx counter is within the range indicated by the Optical Power

TransmittedMinimumThreshold and Optical Power TransmittedMaximumThreshold

values.







OptLowTh



optLowThCode

Optical Power Transmitted Below Low Threshold: The optical power transmitted is belowthe low threshold.

Description










Entities Affected

The transmit laser is failing.Possible Cause



See “Clearing an OptLowTh Alarm” on page 142.Alarm Clearing



Fault Indicator




Fault Indicator










Fault Indicator







Fault Indicator







Fault Indicator




Clearing an OptLowTh Alarm






Optical Power Tx counter is within the range indicated by the Optical Power

TransmittedMinimumThreshold and Optical Power TransmittedMaximumThreshold

values.







OTU-AIS



otu-aisCode

OTU Alarm Indication Signal: The local interface has received an OTU-AIS signal from theNEat the far endof the fiber, indicating thatnoOTNOTUsignal is being transmittedupstreamof (and toward) the local NE.

NOTE: This signal is generated by non-BTI7800 NEs only.

Description/Cause

• OTNOTU interfaces (see respective table below).Entities Affected



The condition will clear when the fault that resulted in the transmission of the OTU-AISsignal is resolved.

Condition Clearing



Fault Indicator






Fault Indicator







PartitionFault



partitionFaultCode

Disk Partition Fault Detected.Description/Cause




See “Clearing a ParitionFault Alarm” on page 145.Alarm Clearing





Fault Indicator

Entity Name StatusIndicatorModules








Clearing a ParitionFault Alarm


NOTE: Refer to the BTI7800 Series Software Configuration Guide beforerebooting a traffic module.

1. Perform a warm reboot of the module.

2. Check for alarms on themodule.



PosRxHigh



posRxHighCode

Receive Power Out of Specification, High: The optical power received is above the specifiedrange for operation.

Description/Cause








See “Clearing a PosRxHigh Alarm” on page 146.Alarm Clearing



Fault Indicator






Clearing a PosRxHigh Alarm


1. Retrieve PM statistics for the DOL OCH:


2. Refer to “DOL OCH Power Alarm Thresholds” on page 177 to determine whether the

optical power received is higher than the specified range for operation.

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.

4. Check for alarms on the DOL OCH.





PosRxLow



posRxLowCode

Receive Power Out of Specification, Low: The optical power received is below the specifiedrange for operation.

Description

• DOL optical multiplex sections (see respective table below).

• DOL optical channels (see respective table below).

Entities Affected

Possible Cause



See “Clearing a PosRxHigh Alarm” on page 146.Alarm Clearing

See:





Fault Indicator


––ROADM2 or ILAoms:<chassis>/<slot>/0/L1<>

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





Fault Indicator






Clearing a PosRxLowAlarm


1. Retrieve statistics for the DOL entity:


2. Refer to “DOL OCH Power Alarm Thresholds” on page 177 or “DOL OMS Power Alarm

Thresholds”onpage 175 todeterminewhether theoptical power received for theentity

is lower than the specified range for operation.

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 sourceof theentity todeterminewhether it is transmittingat anadequate

level.

• Check the fibers and any attenuators in the path to ensure that no unintentional

attenuation has been added to the path.

4. Check for alarms on the DOL entity.





PosTxHigh



posTxHighCode

Transmit Power Out of Specification, High: The optical power transmitted is higher than thespecified range for operation.

Description/Cause




See “Clearing a PosTxHigh Alarm” on page 149.Alarm Clearing



Fault Indicator






Clearing a PosTxHigh Alarm


1. Retrieve statistics for the DOLOCH:



optical power transmitted is out of the specified range for operation.



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



posTxLowCode

Transmit Power Out of Specification, Low: The optical power transmitted is below thespecified range for operation.

Description/Cause




See “Clearing a PosTxLow Alarm” on page 150.Alarm Clearing



Fault Indicator






Clearing a PosTxLowAlarm




1. Retrieve statistics for the DOL OCH:



optical power transmitted is lower than the range specified for operation.

3. If theoptical power transmitted is too low, ensure that theupstreamfiber connections

are intact, thoroughly clean, and correctly connected.




PowerAbsent



powerAbsentCode

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


Description


• AC PEM: The input AC voltage is either less than 90 Vac or greater than 255 Vac, and theoutput 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 60Vdc.

Possible Causes



See “Clearing a PowerAbsent Alarm” on page 152.Alarm Clearing



Fault Indicator






Clearing a PowerAbsent Alarm


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.

2. Check for alarms on the PEM .

• If the alarm clears, you have successfully completed this procedure.


PRBS



prbsCode

PRBS Test Activated: A PRBS test is active on the local port.Description/Cause




Entities Affected

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


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

Condition Clearing



Fault Indicator


––UFM6otu4:<chassis>/<slot>/<2>/<1>/<subport.och.tributary>




Fault Indicator


––UFM4otu4:<chassis>/<slot>/<1>/<1>

1x CFP BICotu4:<chassis>/<slot>/<subslot>/<port>

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




Fault Indicator







Fault Indicator






PreFecBerTh



preFecBerThCode





Pre-FEC Bit Error Rate Above High Threshold: The pre-FEC bit error rate is above the highthreshold.

Description

Optical channel interfaces (see respective table below).Entities Affected

The link is degraded.Possible Cause



See “Clearing a PreFecBerTh Alarm” on page 154.Alarm Clearing



Fault Indicator



Clearing a PreFecBerTh Alarm





• Retrieve statistics for the interface to view the value of the FECmax bit error ratio

counter:


• Retrieve information from the running configuration file to view the statistics

threshold-profile for the interface:

show running-config statistics threshold profile

Example

bti7800# show running-config statistics threshold profile

statistics threshold profile def-och entityType och statistic fec-ber alarmHigh unTimed dblRaiseValue 2.700000000000000e-2 dblClearValue 2.300000000000000e-2 ! threshold profile def-otu4 entityType otu4 statistic fec-ber alarmHigh unTimed dblRaiseValue 4.500000000000000e-3 dblClearValue 7.500000000000000e-4 !


• If the actual pre-FEC BER exceeds the RaiseValue value specified for the alarm,

go to the next step.

• If the actual pre-FEC BER does not exceed the RaiseValue specified for the alarm,

contact your next level of support.

3. Analyze theoptical link, and resolveanyproblems that couldbe impacting thepre-FEC

bit error rate.




PyldMism



pyldMismCode

PayloadMismatch: The payload type in the received signal is not the expected payload type.Description






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

Possible Cause



See “Clearing a PyldMism Alarm” on page 156.Alarm Clearing



Fault Indicator












Clearing a PyldMismAlarm




1. Retrieve interface data to compare the values of the Payload Type and Received

Payload Type parameters.

show interface name:identifier

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

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

information, see the BTI7800 Series Software Configuration Guide.




RDI-L



rdi-lCode

Remote Defect Indication–Line: The local interface has received an RDI-L signal from theNEat the far endof the fiber, indicating thatnoSONETsignal isbeing transmitteddownstreamof (and away from) the local NE. (See also “Maintenance Signaling” on page 33.)

Description/Cause

SONET (OC192, WAN PHY OC192) interfaces (see respective table below).Entities Affected



See “Clearing an RDI-L Condition” on page 158.Condition Clearing

See “OC192, WAN PHY Over OC192 Interface Fault Hierarchy” on page 29.Related Fault Hierarchy



Table 229: SONET (OC192,WANPHYOC192) Interfaces

Fault Indicator




Clearing an RDI-L Condition






RF



rfCode

Remote Fault: The local interface has received a remote-fault signal from the NE at the farend of the fiber, indicating that no Ethernet signal is being transmitted downstream of (andaway from) the local NE. (See also “Maintenance Signaling” on page 33.)

Description/Cause




See “Clearing an RF Condition” on page 159.Condition Clearing







Fault Indicator






Clearing an RF Condition






ScmNmiDown



scmNmiDownCode

System Controller Module (SCM) Interface Down: One of the SCMs in a dual-CMM systemcannot connect to the management IP network.

Description/Cause


• Theconnectionbetween themanagement interfaceand thenetworkgateway isnot intact.

• Thenetworkgateway is configured toblockARPpacketswithnosource IPaddress (sourceIP address is 0.0.0.0), and a static IP address is not provisioned on the SCM.

Possible Causes







See “Clearing an ScmNmiDown Alarm” on page 160.Alarm Clearing



Fault Indicator




Clearing an ScmNmiDown Alarm



• If the network gateway is configured to block ARP packets with no specified source

IP address, go to “Clearing an ScmNmiDown Alarm” on page 160.

• If the network gateway is not configured to block ARP packets with no specified

source IP address, go to “Clearing an ScmNmiDown Alarm” on page 160.

2. Use the conditions CLI command to disable the reporting of this alarm, and then go

to4.For informationabout the conditions command, see theBTI7800SeriesCommand

Line Reference Guide.

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

the BTI7800 Series Software Configuration Guide.






ScmNoNmConn



scmNoNmConnCode

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.

Description/Cause




See “Clearing an ScmNoNmConn Alarm” on page 161.Alarm Clearing



Fault Indicator




Clearing an ScmNoNmConn Alarm


1. Ensure that the connections between themanagement interface and the gateway

on the active and standby CMMs is intact.






SD



sdCode

Signal Degrade: The local port is in a signal-degrade state because of a number of errors inthe received signal.

Description



Entities Affected


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

Possible Causes



See “Clearing an SD Alarm” on page 163.Alarm Clearing

See:






Fault Indicator











Fault Indicator






Clearing an SD Alarm


1. Reprieve statistics for the interface, and ensure that the optical power received and

the optical signal-to-noise ratio are within specification:







TIM



timCode

Trace Identifier Mismatch: The received trace identifier is different from the expected traceidentifier.

Description



Entities Affected

• The optical fiber link is from the wrong source (misconnected).

• Either the expected trace identifier configured on the local interface is incorrect, or thetrace identifier configured on the remote interface is incorrect.

Possible Causes







See “Clearing a TIM Alarm” on page 165.Alarm Clearing

See:






Fault Indicator









Fault Indicator








Clearing a TIM Alarm


1. Retrieve detailed interface data to view the values of the following attribute pairs:

• OTU interface: TraceMessage Expected / TraceMessage Received

• SONET/SDH interface: Expected Section TraceMessage / Received Section Trace

Message


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



tlossRxHtCode

Loss Above High Threshold, Receive: Themeasured optical power loss in the receive fiber isabove the high threshold.

Description/Cause

Terminal amplifier line ports (see respective table below).Entities Affected



See “Clearing a TlossRxHt Alarm” on page 166.Alarm Clearing

See “Terminal Amplifier Port Fault Hierarchy” on page 33.Related Fault Hierarchy




Fault Indicator



Clearing a TlossRxHt Alarm


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: FordetailedAMP1specifications, seetheBTI7800SeriesHardwareOverview and Installation Guide.

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.


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



TlossRxLt

Table 244: Alarm/condition Details


tlossRxLtCode

Loss Below Low Threshold, Receive: Themeasured optical power loss in the received fiberis below the low threshold.

Description/Cause

Terminal amplifier line ports (see respective table below).Entities Affected




Table 244: Alarm/condition Details (continued)



See “Clearing a TlossRxLt Alarm” on page 167.Alarm Clearing

See “Terminal Amplifier Port Fault Hierarchy” on page 33.Related Fault Hierarchy


Fault Indicator



Clearing a TlossRxLt Alarm


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: FordetailedAMP1specifications, seetheBTI7800SeriesHardwareOverview and Installation Guide.

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

clean, and properly connected.

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



UPGRD



upgrdCode





Upgrade in Progress: A system software upgrade is in progress.Description/Cause




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



Fault Indicator











CHAPTER 3

Alarm Thresholds

• Environment Thresholds on page 169

• DOL Thresholds on page 174

Environment Thresholds

Temperature Thresholds - Equipment and Traffic Modules

The following tables provide information about available temperature sensors and the

alarm thresholds for BTI7800 Series equipment and traffic modules.

Table 248: Temperature Sensors - Equipment andModules

DescriptionSensor

Local ambient temperatureAlarm Panel Temp

DIGI internal ASIC temperatureBIC Temp

Local ambient temperatureCMM Temp

Local ambient temperatureDS75 Temp 1

Local ambient temperatureDS75 Temp 3

Local ambient temperatureDS75 Temp BIC

Cooling-module exhaust temperatureExhaust Temp

Internal cooling-module temperatureFAN Internal Temp

Local ambient temperatureFAN Temperature

Local ambient temperatureLine Card Temp

DIGI internal ASIC temperatureOTN Framer Temp

Local ambient temperaturePEM <n> Temperature

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


Table 248: Temperature Sensors - Equipment andModules (continued)

DescriptionSensor

Local ambient temperaturePEM AC <n> Temperature


Table 249: Temperature Thresholds - Equipment andModules

High ThresholdLow ThresholdSensorEquipment/Module

72°C (161.6°F)–DS75 Temp 1AMP1

––DS75 Temp 3

––Line Card Temp

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

105°C (221°F)–BIC Temp

––Alarm Panel TempChassis Alarm Panel

90°C (194°F)–CMM TempCMM

75°C (167°F)–Exhaust TempCooling module

75°C (167°F)–FAN Temperature

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

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

––DS75 Temp 3


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

75°C (167°F)55°C / 131°FPEMAC <n> TemperatureAC PEM

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

––DS75 Temp 3




Table 249: Temperature Thresholds - Equipment andModules (continued)


––DS75 Temp 1UFM

––DS75 Temp 3

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

105°C (221°F)–OTN Framer Temp

NOTE: Supported on UFM4only.

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


Temperature Thresholds - MSA Transceivers

The following tables provide alarm-relatedmodule temperature thresholds for the 100G

Coherent MSA XCVR and the 400G Coherent MSA XCVR.

Table 250: Temperature Thresholds - 100G Coherent MSA XCVRModule

Shutdown ThresholdHigh ThresholdLow Threshold

90°C (194°F)80°C (176°F)-5°C (23°F)

Table 251: Temperature Thresholds - 400G Coherent MSA XCVRModule

ShutdownThresholdHigh ThresholdLow ThresholdDescriptionMDIO Register

88°C / 190.4°F83°C /181.4°F-10°C / 14°FNear TOF09060h

88°C / 190.4°F83°C /181.4°F-10°C / 14°FNear TOF19061h

90°C / 194°F85°C / 185°F-10°C / 14°FPump Lane09062h

90°C / 194°F85°C / 185°F-10°C / 14°FPump Lane19063h

100°C / 212°F95°C / 203°C-10°C / 14°FPIC Lane09064h

100°C / 212°F95°C / 203°C-10°C / 14°FPIC Lane19065h

200°C /392°F200°C / 392°F-10°C / 14°FASIC Core9067h


Chapter 3: Alarm Thresholds

Fan-speed Thresholds

The following table provides information about available fan-speed sensors and the

alarm thresholds for BTI7800 Series cooling modules.

Table 252: Fan-speed Thresholds

Low Threshold

Sensor

Cooling Module DescriptionName

1500 RPMFan speedFan Tach <n>

where n is a value from 1 to 3.

FAN2

1500 RPMFan speedFan RPMFAN3



FAN5



FAN9

NOTE: The RPM threshold for either a BTI7814 Booster Fan (BT8A78FAN9)or a 2-Slot Chassis Cooling Module (BT8A78FAN2) refers to an average ofthe RPM values of the individual fans in the coolingmodule.

Output-current Thresholds

The following table provides information about available output-current sensors and

the alarm thresholds for BTI7800 Series equipment.

Table 253: Output-current Sensors and Thresholds

High ThresholdLow ThresholdDescriptionSensorEquipment

60 Vdc0.2 VdcOutput current (Vdc)Iout PEMAC <n>

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

AC PEM

Voltage Thresholds

The following tables provide information about available voltage sensors and the alarm

thresholds for BTI7800 Series equipment and traffic modules.



Table 254: Voltage Sensors

DescriptionSensor

12Vmain voltage threshold sensor12V_MAIN

2V5 core voltage threshold sensor2V5_CORE

2V5 I/O voltage threshold sensor2V5_IO

3.3Vmain voltage threshold sensor3V3_MAIN

3.3V standby voltage threshold sensor3V3_STBY

5Vmain voltage threshold sensor5V_MAIN

ADC 1V2 GIGE voltage threshold senorADC_1V2_GIGE

ADCS 5V voltage threshold senorADCS_5V

ADCS 5V USB voltage threshold sensorADCS_5V_USB

Input voltageVin PEM AC <n>


Output voltageVout PEM AC <n>


Table 255: Voltage Thresholds


14.409.6012V_MAINAMP1

3.002.002V5_CORE

3.002.002V5_IO

3.962.643V3_MAIN

3.962.643V3_STBY

6.004.005V_MAIN

1.521.02ADC_1V2_GIGE

25590Vin PEM AC <n>AC PEM

6040Vout PEM AC <n>



Table 255: Voltage Thresholds (continued)


14.409.6012V_MAINUFM

2.752.252V5_CORE

3.002.002V5_IO

3.962.643V3_MAIN

3.962.643V3_STBY

6.004.005V_MAIN


13.2610.8612V_MAINWPS4

3.962.683V3_MAIN

3.962.683V3_STBY

5.564.52ADCS_5V

5.564.52ADCS_5V_USB


DOL Thresholds

DOLOSC Power and Optical Backreflection Alarm Thresholds

Table 256: ROADM2OSC Power Alarm Thresholds (all Values in DBm)

L1

Client OutputClient InputThreshold OPROPT

-43.0-22.2-13.0-22.0Hardware min.

-42.0––-21.0Loss of Light raise

-41.0––-20.0Loss of Light clear

6.07.00.00.0Hardware max.



Table 257: ILA OSC Power Alarm Thresholds (all Values in DBm)

L1

Client OutputClient InputThreshold OPROPT

-43.0-22.2-13.0-22.0Hardware min.

-42.0––-21.0Loss of Light raise

-41.0––-20.0Loss of Light clear


Table 258: Default OSC Back-Reflection Ratio Threshold Values (obrHt Alarm)

Status

Values

ParametersBinThreshold DefaultRange

Enabled-18 dB-37 to -6RaiseValueUnTimed1alarmHigh

-19 dB-37 to -6ClearValue

–––––alarmLow

–––––warningAlert

1Only the unTimed bin is supported.

DOLOMSPower Alarm Thresholds

Table 259: ROADM2OMSPower Alarm Thresholds (all Values in DBm)

L1

Client Output

Client Input

Threshold OPR + PREOPROPTPass-ThruAdd-Drop

-39.0-29.0-21.8-8.5-18.0-18.0Hardware min.

-38.0-28.0––-8.8-17.0Loss of Lightraise

-37.0-27.0––-7.8-16.0Loss of Lightclear

-36.0-26.0––-6.8-14.0Power Out ofSpecificationLow raise



Table 259: ROADM2OMSPower Alarm Thresholds (all Values in DBm) (continued)

L1

Client Output

Client Input

Threshold OPR + PREOPROPTPass-ThruAdd-Drop

-35.5-25.5––-6.3-13.5Power Out ofSpecificationLow clear

3.414.423.323.023.023.0Hardware max.

Table 260: ILA OMSPower Alarm Thresholds (all Values in DBm)

L1

Client Output

Client Input

Threshold OPR + PREOPROPTPass-Thru

-39.0-29.0-21.8-4.3-8.3Hardware min.

-38.0-28.0––-7.3Loss of Light raise

-37.0-27.0––-6.3Loss of Light clear

-36.0-26.0––-4.3Power Out ofSpecification Lowraise

-35.5-25.5––-3.8Power Out ofSpecification Lowclear

3.4-14.423.325.125.1Hardware max.



DOLOCHPower Alarm Thresholds

Table 261: ROADM2 50GHz OCHOptical-power Alarm Thresholds (all Values in DBm)

L1

PostAmp IN(Internal)Client OutputClient InputThreshold OPROPT

Not supportedAlarm state setfrom PostAmp IN

-27.0-14.5-20.3Hardware min.

-23.3-10.8-16.6Lossof Light raise

-22.2-9.7-15.5Lossof Light clear

-20.3-7.8-13.6Power Out ofSpecificationLowraise

-19.7-7.2-13.0Power Out ofSpecificationLowclear

-13.35.15.1Power Out ofSpecificationHighraise

-12.85.75.7Power Out ofSpecificationHighclear

-1.217.217.2Hardware max.

DOL Port Power Alarm Thresholds

Table 262: ROADM2 PRE Port-power Alarm Thresholds (all Values in DBm)

CFP2 PRE PortMainboard PRE Port

Threshold OutputInputOutputInput

-19.0-40.0-41.0-29.0Hardware min.

–-40.0–-21.0Loss of Light raise

–-39.0–-20.0Loss of Light clear

–-38.5–-18.0Power Out ofSpecification, Lowraise

–-38.0–-17.5Power Out ofSpecification, Lowclear



Table 262: ROADM2 PRE Port-power Alarm Thresholds (all Values in DBm) (continued)




Table 263: ILA PRE Port-power Alarm Thresholds (all Values in DBm)



-19.0-40.0-41.0-29.0Hardware min.

–-40.0–-21.0Loss of Light raise

–-39.0–-20.0Loss of Light clear

–-38.5–-18.0Power Out ofSpecificationLow raise

–-38.0–-17.5Power Out ofSpecificationLowclear


DOL Rx-loss Alarm Thresholds

Table 264: ROADM2 Rx-loss Alarm Thresholds (all Values in DB)

Line

Client (to Client orMD03)Threshold

without PRE forNZDSF

without PRE forNDSFwith PRE

19.723.233.25.2LoSpecRx raise

19.523.033.05.0LoSpecRx clear

Table 265: ILA Rx-loss Alarm Thresholds (all Values in DB)

Line

Client (to Client)Thresholdwithout PRE forNZDSF

without PRE forNDSFwith PRE

19.723.233.22.2LoSpecRx raise

19.523.033.02.0LoSpecRx clear



CHAPTER 4

BTI7800 Series Equipment and Modules

• Common Equipment Components on page 179

• Management and Traffic Modules on page 180

• BTI7800 Series Module and BIC LED Behavior on page 181

Common Equipment Components

Table 266: BTI7814Major Common Equipment Components

Release IntroducedPECComponent

Release 1.1BT8A78CAP114-Slot Chassis Alarm Panel

Release 1.1BT8A78FAN314-Slot Chassis Front Cooling Module

Release 4.1BT8A78FAN9BTI7814 Booster Fan

Release 1.1BT8A78PEM3-DC14-SlotChassisDCPowerEntryModule

Release 1.5BT8A78ACM12900W (53.5V) AC Rectifier Module

Release 1.1BT8A78CMM1Chassis Management Module

Table 267: BTI7802 Common Equipment Components


Release 1.3BT8A78CAP22-Slot Chassis Alarm Panel

Release 1.6BT8A78FAN22-Slot Chassis Cooling Module

Release 1.3BT8A78PEM1-DC1/2-Slot Chassis DC Power Entry Module

Release 1.3BT8A78PEM1-AC1/2-Slot Chassis AC Power Entry Module

Release 1.1BT8A78CMM1Chassis Management Module (CMM)


Table 268: BTI7801 Common Equipment Components


Release 2.1BT8A78ESL1Ethernet and Serial Link (ESL) module

Release 2.1BT8A78FAN51-Slot Chassis Front Cooling Module

Release 1.3BT8A78PEM1-DC1/2-Slot Chassis DC Power Entry Module

Release 1.3BT8A78PEM1-AC1/2-Slot Chassis AC Power Entry Module

Release 1.1BT8A78CMM1Chassis Management Module (CMM)

Management and Traffic Modules

Table 269: BTI7800 Series Management and Traffic Modules

IntroducedPECDescriptionModule

Managementmodules

Release 1.1BT8A78CMM1Provides management and control ofthe system.

Chassis Management Module 1 (CMM1)

Servicemodules

Release 1.1BT8A78UFM3Supports two BICs.Universal Forwarding Module (UFM3)

Release 1.1BT8A78UFM4Contains one 100G Coherent MSAXCVR and supports one BTI InterfaceCard (BIC).

UniversalForwardingModulewith Integrated100G Coherent MSA XCVR (UFM4)

Release 4.1BT8A78UFM6-I02Contains a total of ten client ports andone 400G Coherent MSA XCVR.1

UniversalForwardingModulewith Integrated400G Coherent MSA XCVR (UFM6)

Release 1.1BT8A78AMP1Provides DWDM composite signalamplification in point-to-pointapplications.

NOTE: This module is not supportedon the BTI7801.

96-Channel Amplifier (AMP1)

Release 1.6BT8A78WPS4Provides revertive or non-revertivewavelength protection switching.

Wavelength Protection Switch (WPS4)

Release 2.0BT8A78RDM22-degree ROADMmodule.


2-Port Reconfigurable Optical Add/DropMultiplexer (ROADM2)



Table 269: BTI7800 Series Management and Traffic Modules (continued)

IntroducedPECDescriptionModule

Release 2.1.1BT8A78AMPLProvidesunidirectionalDWDMC-bandamplification and tilt control at transitsites.


Inline Amplifier (ILA)

BICmodules

Release 1.1BT8A78SFP12GFor up to 12 SFP+ transceivers.12x SFP+ BTI Interface Card (12x SFP+ BIC)

Release 1.1BT8A78CFP1GFor 1 CFP transceiver.1x CFP BTI Interface Card (1x CFP BIC)

CFP2modules

Release 2.0BT8A78AMPPPre-amplifier module that plugs intothe PRE slot of a host ROADM or ILAmodule.

Pluggable Pre-Amplifier (PRE)

Passivemodules

Release 2.0BT8A78MD03Provides local fixed grid access to all96wavelengths in theDWDM50-GHzchannel plan.

96-Channel Fixed Mux/Demux (FMD96)

1 Client ports 1 to 10 support QSFP+ transceivers and client ports 1, 2, 6, 7 support both QSFP+ and QSFP28 transceivers.

BTI7800 Series Module and BIC LED Behavior

Table 270: CMM LEDs

DescriptionColorLEDs

Not used.AmberIdentify

The CMM is operationally up.GreenActive

The CMM is operationally down or the CMM is not recognized.RedFail

The CMM does not match the provisioned CMM.BlueHot Swap

The link is up.GreenLink (right)

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


Chapter 4: BTI7800 Series Equipment and Modules

Table 271: Service Module LED Behavior

State DescriptionStateDescriptionName

The CMMhas identified and acknowledged themodule.

The CMM can only acknowledge themodule if themodule is administratively up. A newly-insertedmoduleis administratively up if either of the following is true:

• Themodule has been pre-provisioned and configuredto be administratively up.

• Auto-provisioning is enabled. If auto-provisioning isenabled and if theCMM is able to identify themodule,the module is automatically provisioned and itsadministrative status is set to up.

OFFThe Identify LED indicateswhether the CMM hasidentified andacknowledged thenewly-insertedmodule.

Identify

(AMBER)

The CMM has failed to identify or acknowledge themodule.

ON

TheCMM is attempting to identify and acknowledge themodule.

BLINKING

The operational status of the module is down.OFFTheActiveLED reflects theoperational status of themodule.

Active

(GREEN)The operational status of the module is up.ON

The operational status of the module is up.OFFThe Fail LED reflects theoperational status of themodule.

Fail

(RED)The operational status of the module is down.ON

The administrative status of the module is up, and theactual module matches the provisionedmodule.

Themodule should not be removed from the chassis inthis state.

OFFThe Hot Swap H/S LEDindicates whether themodule can be removedfrom the chassis.

H/S

(BLUE)

The administrative status of the module is down, or theactual module does not match the provisionedmodule.

Themodule can be removed from the chassis in thisstate.

ON

This is a transient state that occurs when plugging in amodule, or when changing its administrative status.

Themodule should not be removed from the chassis inthis state.

BLINKING

Table 272: BIC LEDs


Themodule is operating normally.GreenActive

Themodule has failed.RedFail



Table 272: BIC LEDs (continued)


ON: Themodule is in a quiescent state, and can be removed from the slot after aminimum of 5 seconds in this state.

BLINKING: Themodule is being placed into a quiescent state. It cannot be removedfrom the slot.

OFF: Themodule is operating normally. It cannot be removed from the slot.

BlueH/S (Hot Swap)

Table 273: Port LEDs (UFMs and BICs)


The port has failed.RedFail

A fault exists on the port.AmberFault


Chapter 4: BTI7800 Series Equipment and Modules

BTI7800 Series Alarm and Troubleshooting GuideAlarmDetails.....107...

Documents

Transcript of BTI7800 Series Alarm and Troubleshooting GuideAlarmDetails.....107...