Cisco ONS 15454 DWDM Troubleshooting Guide, Release 7.0 - Chapter 2, Alarm Troubleshooting [Cisco ONS 15400 Series]

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Indexes

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  NA Conditions

2.1.5  NR Conditions

2.1.6  Alarms and Conditions Listed By Alphabetical Entry

2.2  Logical Objects

2.2.1  Alarm Logical Objects

2.2.2  Alarm List by Logical Object Type

2.3  Trouble Characterizations

2.3.1  Alarm Characteristics

2.3.2  Condition Characteristics

2.3.3  Severity

2.3.4  Service Effect

2.3.5  State

2.4  Safety Summary

2.5  Trouble-Clearing Procedures

2.5.1  AIS

Clear the AIS Condition

2.5.2  AIS-L

Clear the AIS-L Condition

2.5.3  ALS

2.5.4  ALS-DISABLED

Clear the ALS-DISABLED Condition

2.5.5  AMPLI-INIT

Clear the AMPLI-INIT Condition

2.5.6  APC-CORRECTION-SKIPPED

2.5.7  APC-DISABLED

Clear the APC-DISABLED Condition

2.5.8  APC-END

2.5.9  APC-OUT-OF-RANGE

Clear the APC-OUT-OF-RANGE Condition

2.5.10  AS-CMD

Clear the AS-CMD Condition

2.5.11  AS-MT

Clear the AS-MT Condition

2.5.12  AUTORESET

Clear the AUTORESET Alarm

2.5.13  AWG-DEG

Clear the AWG-DEG Alarm

2.5.14  AWG-FAIL

Clear the AWG-FAIL Alarm

2.5.15  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.5.16  AWG-WARM-UP

2.5.17  BAT-FAIL

Clear the BAT-FAIL Alarm

2.5.18  BKUPMEMP

Clear the BKUPMEMP Alarm

2.5.19  BPV

Clear the BPV Alarm

2.5.20  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.5.21  CARLOSS (FC)

Clear the CARLOSS (FC) Alarm

2.5.22  CARLOSS (GE)

Clear the CARLOSS (GE) Alarm

2.5.23  CARLOSS (ISC)

Clear the CARLOSS (ISC) Alarm

2.5.24  CARLOSS (TRUNK)

Clear the CARLOSS (TRUNK) Alarm

2.5.25  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.5.26  DATAFLT

Clear the DATAFLT Alarm

2.5.27  DBOSYNC

Clear the DBOSYNC Alarm

2.5.28  DISCONNECTED

Clear the DISCONNECTED Alarm

2.5.29  DSP-COMM-FAIL

2.5.30  DSP-FAIL

Clear the DSP-FAIL Alarm

2.5.31  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.5.32  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.5.33  DUP-SHELF-ID

Clear the DUP-SHELF-ID Alarm

2.5.34  EHIBATVG

Clear the EHIBATVG Alarm

2.5.35  ELWBATVG

Clear the ELWBATVG Alarm

2.5.36  EOC

Clear the EOC Alarm

2.5.37  EOC-L

Clear the EOC-L Alarm

2.5.38  EQPT

Clear the EQPT Alarm

2.5.39  EQPT-MISS

Clear the EQPT-MISS Alarm

2.5.40  EXCCOL

Clear the EXCCOL Alarm

2.5.41  EXT

Clear the EXT Alarm

2.5.42  FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN)

Clear the FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN) Condition

2.5.43  FAILTOSW (TRUNK)

Clear the FAILTOSW (TRUNK) Condition

2.5.44  FAN

Clear the FAN Alarm

2.5.45  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.5.46  FDI

Clear the FDI Condition

2.5.47  FEC-MISM

Clear the FEC-MISM Alarm

2.5.48  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.5.49  FORCED-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN)

2.5.50  FORCED-REQ-SPAN (TRUNK)

2.5.51  FRCDSWTOINT

2.5.52  FRCDSWTOPRI

2.5.53  FRCDSWTOSEC

2.5.54  FRCDSWTOTHIRD

2.5.55  FRNGSYNC

Clear the FRNGSYNC Condition

2.5.56  FSTSYNC

2.5.57  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.5.58  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.5.59  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.5.60  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.5.61  GCC-EOC

Clear the GCC-EOC Alarm

2.5.62  GE-OOSYNC (FC, GE, ISC)

Clear the GE-OOSYNC (FC, GE, ISC) Alarm

2.5.63  GE-OOSYNC (TRUNK)

Clear the GE-OOSYNC (TRUNK) Alarm

2.5.64  GFP-LFD

2.5.65  HIBATVG

Clear the HIBATVG Alarm

2.5.66  HI-CCVOLT

Clear the HI-CCVOLT Condition

2.5.67  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.5.68  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.5.69  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.5.70  HITEMP

Clear the HITEMP Alarm

2.5.71  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.5.72  HLDOVRSYNC

Clear the HLDOVRSYNC Condition

2.5.73  I-HITEMP

Clear the I-HITEMP Alarm

2.5.74  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.5.75  INCOMPATIBLE-SEND-PDIP

Clear the INCOMPATIBLE-SEND-PDIP Alarm

2.5.76  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.5.77  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.5.78  INVMACADR

Clear the INVMACADR Alarm

2.5.79  LASER-APR

2.5.80  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.5.81  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.5.82  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.5.83  LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC)

Clear the LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC) Condition

2.5.84  LOCKOUT-REQ (TRUNK)

Clear the LOCKOUT-REQ (TRUNK) Condition

2.5.85  LOF (BITS)

Clear the LOF (BITS) Alarm

2.5.86  LOF (TRUNK)

Clear the LOF (TRUNK) Alarm

2.5.87  LOGBUFR90

2.5.88  LOGBUFROVFL

Clear the LOGBUFROVFL Alarm

2.5.89  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.5.90  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.5.91  LOM

Clear the LOM Alarm

2.5.92  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.5.93  LOS (2R)

Clear the LOS (2R) Alarm

2.5.94  LOS (BITS)

Clear the LOS (BITS) Alarm

2.5.95  LOS (ESCON)

Clear the LOS (ESCON) Alarm

2.5.96  LOS (ISC)

Clear the LOS (ISC) Alarm

2.5.97  LOS (OTS)

Clear the LOS (OTS) Alarm

2.5.98  LOS (TRUNK)

Clear the LOS (TRUNK) Alarm

2.5.99  LOS-O

Clear the LOS-O Alarm

2.5.100  LOS-P (AOTS, OMS, OTS)

Clear the LOS-P (AOTS, OMS, OTS) Alarm

2.5.101  LOS-P (OCH)

Clear the LOS-P (OCH) Alarm

2.5.102  LOS-P (TRUNK)

Clear the LOS-P (TRUNK) Alarm

2.5.103  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.5.104  LPBKFACILITY (ESCON)

Clear the LPBKFACILITY (ESCON) Condition

2.5.105  LPBKFACILITY (FC)

Clear the LPBKFACILITY (FC) Condition

2.5.106  LPBKFACILITY (GE)

Clear the LPBKFACILITY (GE) Condition

2.5.107  LPBKFACILITY (ISC)

Clear the LPBKFACILITY (ISC) Condition

2.5.108  LPBKFACILITY (TRUNK)

Clear the LPBKFACILITY (TRUNK) Condition

2.5.109  LPBKTERMINAL (ESCON)

Clear the LPBKTERMINAL (ESCON) Condition

2.5.110  LPBKTERMINAL (FC)

Clear the LPBKTERMINAL (FC) Condition

2.5.111  LPBKTERMINAL (GE)

Clear the LPBKTERMINAL (GE) Condition

2.5.112  LPBKTERMINAL (ISC)

Clear the LPBKTERMINAL (ISC) Condition

2.5.113  LPBKTERMINAL (TRUNK)

Clear the LPBKTERMINAL (TRUNK) Condition

2.5.114  LWBATVG

Clear the LWBATVG Alarm

2.5.115  MAN-REQ

Clear the MAN-REQ Condition

2.5.116  MANRESET

2.5.117  MANSWTOINT

2.5.118  MANSWTOPRI

2.5.119  MANSWTOSEC

2.5.120  MANSWTOTHIRD

2.5.121  MANUAL-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN)

2.5.122  MANUAL-REQ-SPAN (TRUNK)

2.5.123  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.5.124  MEA (FAN)

Clear the MEA (FAN) Alarm

2.5.125  MEA (PPM)

Clear the MEA (PPM) Alarm

2.5.126  MEM-GONE

2.5.127  MEM-LOW

2.5.128  MFGMEM

Clear the MFGMEM Alarm

2.5.129  NOT-AUTHENTICATED

2.5.130  OCHNC-INC

Clear the OCHNC-INC Alarm

2.5.131  OCHTERM-INC

Clear the OCHTERM-INC Condition

2.5.132  ODUK-1-AIS-PM

Clear the ODUK-1-AIS-PM Condition

2.5.133  ODUK-2-AIS-PM

Clear the ODUK-2-AIS-PM Condition

2.5.134  ODUK-3-AIS-PM

Clear the ODUK-3-AIS-PM Condition

2.5.135  ODUK-4-AIS-PM

Clear the ODUK-4-AIS-PM Condition

2.5.136  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.5.137  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.5.138  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.5.139  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.5.140  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.5.141  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.5.142  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.5.143  OPEN-SLOT

Clear the OPEN-SLOT Condition

2.5.144  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.5.145  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.5.146  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.5.147  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.5.148  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.5.149  OSRION

Clear the OSRION Condition

2.5.150  OTUK-AIS

Clear the OTUK-AIS Condition

2.5.151  OTUK-BDI

Clear the OTUK-BDI Condition

2.5.152  OTUK-IAE

Clear the OTUK-IAE Alarm

2.5.153  OTUK-LOF

Clear the OTUK-LOF Alarm

2.5.154  OTUK-SD

Clear the OTUK-SD Condition

2.5.155  OTUK-SF

Clear the OTUK-SF Condition

2.5.156  OTUK-TIM

Clear the OTUK-TIM Condition

2.5.157  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.5.158  PARAM-MISM

2.5.159  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.5.160  PMI

Clear the PMI Condition

2.5.161  PORT-ADD-PWR-DEG-HI

Clear the PORT-ADD-PWR-DEG-HI Alarm

2.5.162  PORT-ADD-PWR-DEG-LOW

Clear the PORT-ADD-PWR-DEG-LOW Alarm

2.5.163  PORT-ADD-PWR-FAIL-HI

Clear the PORT-ADD-PWR-FAIL-HI Alarm

2.5.164  PORT-ADD-PWR-FAIL-LOW

Clear the PORT-ADD-PWR-FAIL-LOW Alarm

2.5.165  PORT-FAIL

Clear the PORT-FAIL Alarm

2.5.166  PROTNA

Clear the PROTNA Alarm

2.5.167  PROV-MISMATCH

Clear the PROV-MISMATCH Alarm

2.5.168  PTIM

Clear the PTIM Alarm

2.5.169  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.5.170  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.5.171  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.5.172  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.5.173  RFI

Clear the RFI Condition

2.5.174  SD (TRUNK)

Clear the SD (TRUNK) Condition

2.5.175  SF (TRUNK)

Clear the SF (TRUNK) Condition

2.5.176  SFTWDOWN

2.5.177  SHELF-COMM-FAIL

Clear the SHELF-COMM-FAIL Alarm

2.5.178  SH-INS-LOSS-VAR-DEG-HIGH

Clear the SH-INS-LOSS-VAR-DEG-HIGH Alarm

2.5.179  SH-INS-LOSS-VAR-DEG-LOW

Clear the SH-INS-LOSS-VAR-DEG-LOW Alarm

2.5.180  SHUTTER-OPEN

Clear the SHUTTER-OPEN Condition

2.5.181  SIGLOSS

Clear the SIGLOSS Alarm

2.5.182  SNTP-HOST

Clear the SNTP-HOST Alarm

2.5.183  SPANLENGTH-OUT-OF-RANGE

Clear the SPANLENGTH-OUT-OF-RANGE Alarm

2.5.184  SPAN-NOT-MEASURED

2.5.185  SQUELCHED

Clear the SQUELCHED Condition

2.5.186  SSM-DUS

2.5.187  SSM-FAIL

Clear the SSM-FAIL Alarm

2.5.188  SSM-LNC

2.5.189  SSM-OFF

Clear the SSM-OFF Condition

2.5.190  SSM-PRC

2.5.191  SSM-PRS

2.5.192  SSM-RES

2.5.193  SSM-SMC

2.5.194  SSM-ST2

2.5.195  SSM-ST3

2.5.196  SSM-ST3E

2.5.197  SSM-ST4

2.5.198  SSM-STU

Clear the SSM-STU Condition

2.5.199  SSM-TNC

2.5.200  SW-MISMATCH

Clear the SW-MISMATCH Condition

2.5.201  SWTOPRI

2.5.202  SWTOSEC

Clear the SWTOSEC Condition

2.5.203  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.5.204  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.5.205  SYNCLOSS

Clear the SYNCLOSS Alarm

2.5.206  SYNCPRI

Clear the SYNCPRI Alarm

2.5.207  SYNCSEC

Clear the SYNCSEC Alarm

2.5.208  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.5.209  SYSBOOT

2.5.210  TEMP-MISM

Clear the TEMP-MISM Condition

2.5.211  TIM

Clear the TIM Alarm

2.5.212  TIM-MON

Clear the TIM-MON Alarm

2.5.213  TRAIL-SIGNAL-FAIL

Clear the TRAIL-SIGNAL-FAIL Condition

2.5.214  UNC-WORD

Clear the UNC-WORD Condition

2.5.215  UNREACHABLE-TARGET-POWER

2.5.216  UT-COMM-FAIL

Clear the UT-COMM-FAIL Alarm

2.5.217  UT-FAIL

Clear the UT-FAIL Alarm

2.5.218  VOA-HDEG

Clear the VOA-HDEG Alarm

2.5.219  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.5.220  VOA-LDEG

Clear the VOA-LDEG Alarm

2.5.221  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.5.222  VOLT-MISM

Clear the VOLT-MISM Condition

2.5.223  WKSWPR (2R, EQPT, ESCON, FC, GE, ISC)

2.5.224  WKSWPR (TRUNK)

2.5.225  WTR (2R, EQPT, ESCON, FC, GE, ISC)

2.5.226  WTR (TRUNK)

2.5.227  WVL-MISMATCH

Clear the WVL-MISMATCH alarm

2.6  DWDM Card LED Activity

2.6.1  DWDM Card LED Activity After Insertion

2.6.2  DWDM Card LED Activity During Reset

2.7  Traffic Card LED Activity

2.7.1  Typical Traffic Card LED Activity After Insertion

2.7.2  Typical Traffic Card LED Activity During Reset

2.7.3  Typical Card LED State After Successful Reset

2.8  Frequently Used Alarm Troubleshooting Procedures

2.8.1  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Manual Switch Command

Clear a 1+1 Force or Manual Switch Command

Initiate a Lock-On Command

Initiate a Card or Port Lockout Command

Clear a Lock-On or Lockout Command

2.8.2  CTC Card Resetting and Switching

Reset a Card in CTC

Reset an Active TCC2/TCC2P Card and Activate the Standby Card

2.8.3  Physical Card Reseating, Resetting, and Replacement

Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card

Remove and Reinsert (Reseat) Any Card

Physically Replace a Card

2.8.4  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node Section DCC Terminations

Clear an MXP or TXP Card Loopback Circuit

2.8.5  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly

Alarm Troubleshooting

Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.

This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco DWDM alarm and condition. Tables 2-1 through 2-5 provide lists of DWDM alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all DWDM alarm logical objects, which are the basis of the alarm profile list in Table 2-8. For a comprehensive list of all conditions and instructions for using TL1 commands, refer to the Cisco SONET TL1 Command Guide.

An alarm's troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

For more information about alarm profiles, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Note Unless otherwise noted, ONS 15454 refers to the ANSI and ETSI versions of the platform.

2.1  Alarm Indexes

The following tables group alarms and conditions by their default severities in the ONS DWDM system. These severities are the same whether they are reported in the CTC Alarms window severity (SEV) column or in TL1.

Note The CTC default alarm profile contains some alarms or conditions that are not currently implemented but are reserved for future use.

Note The CTC default alarm profile in some cases contains two severities for one alarm (for example, MJ/MN). The platform default severity comes first (in this example, MJ), but the alarm can be demoted to the second severity in the presence of a higher-ranking alarm. This is in accordance with Telcordia GR-474.

2.1.1  Critical Alarms (CR)

Table 2-1 alphabetically lists Critical (CR) DWDM alarms.

Table 2-1 Critical DWDM Alarm List

2R: LOS

FAN: MEA

OTS: AWG-FAIL

AICI-AEP: EQPT

FAN: MFGMEM

OTS: AWG-OVERTEMP

AICI-AEP: MFGMEM

FC: GE-OOSYNC

OTS: LOS

AICI-AIE: EQPT

GE: GE-OOSYNC

OTS: LOS-P

AICI-AIE: MFGMEM

ISC: GE-OOSYNC

OTS: OPWR-HFAIL

AIP: MEA

ISC: LOS

OTS: OPWR-LFAIL

AIP: MFGMEM

NE: HITEMP

OTS: VOA-HFAIL

AOTS: GAIN-HFAIL

NE: I-HITEMP

OTS: VOA-LFAIL

AOTS: GAIN-LFAIL

OCH: LOS-P

PPM: EQPT

AOTS: OPWR-HFAIL

OCH: OPWR-HFAIL

PPM: IMPROPRMVL

AOTS: OPWR-LFAIL

OCH: OPWR-LFAIL

PPM: MEA

AOTS: VOA-HFAIL

OCH: PORT-ADD-PWR-FAIL-HIGH

PPM: MFGMEM

AOTS: VOA-LFAIL

OCH: PORT-ADD-PWR-FAIL-LOW

TRUNK: GE-OOSYNC

BPLANE: MFGMEM

OCH: PORT-FAIL

TRUNK: LOF

EQPT: BKUPMEMP

OCH: VOA-HFAIL

TRUNK: LOM

EQPT: EQPT

OCH: VOA-LFAIL

TRUNK: LOS

EQPT: IMPROPRMVL

OMS: LOS-P

TRUNK: LOS-P

EQPT: MEA

OMS: OPWR-HFAIL

TRUNK: OTUK-LOF

ESCON: LOS

OMS: OPWR-LFAIL

TRUNK: OTUK-TIM

FAN: EQPT-MISS

OMS: VOA-HFAIL

TRUNK: TIM

FAN: FAN

OMS: VOA-LFAIL

—

2.1.2  Major Alarms (MJ)

Table 2-2 alphabetically lists Major (MJ) DWDM alarms.

Table 2-2 Major DWDM Alarm List

AIP: INVMACADR

ISC: CARLOSS

SHELF: MEA

AOTS: LASERBIAS-FAIL

ISC: SIGLOSS

SHELF: SHELF-COMM-FAIL

EQPT: CARLOSS

ISC: SYNCLOSS

TRUNK: CARLOSS

EQPT: MEM-GONE

NE: DBOSYNC

TRUNK: DSP-COMM-FAIL

EQPT: PEER-NORESPONSE

NE: OPTNTWMIS

TRUNK: DSP-FAIL

ESCON: SIGLOSS

NE: SYSBOOT

TRUNK: FC-NO-CREDITS

FC: CARLOSS

NE-SREF: SYNCPRI

TRUNK: ODUK-TIM-PM

FC: FC-NO-CREDITS

OSC-RING: RING-ID-MIS

TRUNK: OUT-OF-SYNC

FC: OUT-OF-SYNC

PWR: BAT-FAIL

TRUNK: PROV-MISMATCH

FC: SIGLOSS

PWR: EHIBATVG

TRUNK: PTIM

FC: SYNCLOSS

PWR: ELWBATVG

TRUNK: SIGLOSS

GE: CARLOSS

PWR: HIBATVG

TRUNK: SYNCLOSS

GE: OUT-OF-SYNC

PWR: LWBATVG

TRUNK: UT-COMM-FAIL

GE: SIGLOSS

SHELF: DUP-SHELF-ID

TRUNK: WVL-MISMATCH

GE: SYNCLOSS

—

—

GFP: GFP-LFD

—

—

2.1.3  Minor Alarms (MN)

Table 2-3 alphabetically lists Minor (MN) DWDM alarms.

Table 2-3 Minor DWDM Alarm List

2R: HI-LASERBIAS

ESCON: HI-TXPOWER

OCN: EOC-L

2R: HI-RXPOWER

ESCON: LO-RXPOWER

OCN: HI-LASERBIAS

2R: HI-TXPOWER

ESCON: LO-TXPOWER

OCN: HI-LASERTEMP

2R: LO-RXPOWER

EXT-SREF: SYNCPRI

OCN: HI-RXPOWER

2R: LO-TXPOWER

EXT-SREF: SYNCSEC

OCN: HI-TXPOWER

AOTS: CASETEMP-DEG

EXT-SREF: SYNCTHIRD

OCN: LO-LASERBIAS

AOTS: FIBERTEMP-DEG

FC: HI-LASERBIAS

OCN: LO-LASERTEMP

AOTS: GAIN-HDEG

FC: HI-RXPOWER

OCN: LO-RXPOWER

AOTS: GAIN-LDEG

FC: HI-TXPOWER

OCN: LO-TXPOWER

AOTS: LASERBIAS-DEG

FC: LO-RXPOWER

OMS: LOS-O

AOTS: LASERTEMP-DEG

FC: LO-TXPOWER

OMS: OPWR-HDEG

AOTS: OPWR-HDEG

GE: HI-LASERBIAS

OMS: OPWR-LDEG

AOTS: OPWR-LDEG

GE: HI-RXPOWER

OMS: VOA-HDEG

AOTS: VOA-HDEG

GE: HI-TXPOWER

OMS: VOA-LDEG

AOTS: VOA-LDEG

GE: LO-RXPOWER

OTS: AWG-DEG

BITS: BPV

GE: LO-TXPOWER

OTS: LASERBIAS-DEG

BITS: LOF

ISC: HI-LASERBIAS

OTS: LOS-O

BITS: LOS

ISC: HI-RXPOWER

OTS: OPWR-HDEG

BITS: SSM-FAIL

ISC: HI-TXPOWER

OTS: OPWR-LDEG

ENVALRM: EXT

ISC: LO-RXPOWER

OTS: SH-INS-LOSS-VAR-DEG-HIGH

EQPT: AUTORESET

ISC: LO-TXPOWER

OTS: SH-INS-LOSS-VAR-DEG-LOW

EQPT: EXCCOL

NE: DATAFLT

OTS: SPANLENGTH-OUT-OF-RANGE

EQPT: HI-LASERBIAS

NE: DUP-IPADDR

OTS: VOA-HDEG

EQPT: HI-LASERTEMP

NE: DUP-NODENAME

OTS: VOA-LDEG

EQPT: HITEMP

NE: NET-POOL-LOW

PPM: HI-LASERBIAS

EQPT: HI-TXPOWER

NE: ROUTE-OVERFLOW

PPM: HI-LASERTEMP

EQPT: LO-LASERBIAS

NE: SNTP-HOST

PPM: HI-TXPOWER

EQPT: LO-LASERTEMP

NE-SREF: SYNCSEC

PPM: LO-LASERBIAS

EQPT: LO-TXPOWER

NE-SREF: SYNCTHIRD

PPM: LO-LASERTEMP

EQPT: MEM-LOW

OCH: LOS-O

PPM: LO-TXPOWER

EQPT: PROTNA

OCH: OPWR-HDEG

PPM: PROV-MISMATCH

EQPT: PWR-FAIL-A

OCH: OPWR-LDEG

TRUNK: EOC

EQPT: PWR-FAIL-B

OCH: PORT-ADD-PWR-DEG-HI

TRUNK: EOC-L

EQPT: PWR-FAIL-RET-A

OCH: PORT-ADD-PWR-DEG-LOW

TRUNK: GCC-EOC

EQPT: PWR-FAIL-RET-B

OCH: UNREACHABLE-TARGET-POWER

TRUNK: OTUK-IAE

EQPT: SFTWDOWN

OCH: VOA-HDEG

TRUNK: SSM-FAIL

ESCON: HI-LASERBIAS

OCH: VOA-LDEG

TRUNK: TIM-MON

ESCON: HI-RXPOWER

OCN: EOC

—

2.1.4  NA Conditions

Table 2-4 alphabetically lists Not Alarmed (NA) DWDM conditions.

Table 2-4 NA DWDM Conditions List

2R: ALS

FC: FORCED-REQ-SPAN

OCH: PARAM-MISM

2R: AS-CMD

FC: LOCKOUT-REQ

OCH: TRAIL-SIGNAL-FAIL

2R: AS-MT

FC: LPBKFACILITY

OCHNC-CONN: OCHNC-INC

2R: FAILTOSW

FC: LPBKTERMINAL

OCH-TERM: OCHTERM-INC

2R: FORCED-REQ-SPAN

FC: MANUAL-REQ-SPAN

OCN: ALS

2R: LOCKOUT-REQ

FC: SQUELCHED

OCN: AS-CMD

2R: MANUAL-REQ-SPAN

FC: WKSWPR

OCN: AS-MT

2R: SQUELCHED

FC: WTR

OCN: FAILTOSW

2R: WKSWPR

GE: ALS

OCN: FORCED-REQ-SPAN

2R: WTR

GE: AS-CMD

OCN: MANUAL-REQ-SPAN

AOTS: ALS

GE: AS-MT

OCN: SQUELCHED

AOTS: AMPLI-INIT

GE: FAILTOSW

OMS: APC-CORRECTION-SKIPPED

AOTS: APC-CORRECTION-SKIPPED

GE: FORCED-REQ-SPAN

OMS: APC-OUT-OF-RANGE

AOTS: APC-OUT-OF-RANGE

GE: LOCKOUT-REQ

OMS: AS-CMD

AOTS: AS-CMD

GE: LPBKFACILITY

OMS: AS-MT

AOTS: AS-MT

GE: LPBKTERMINAL

OMS: PARAM-MISM

AOTS: LASER-APR

GE: MANUAL-REQ-SPAN

OMS: PMI

AOTS: OSRION

GE: SQUELCHED

OTS: APC-CORRECTION-SKIPPED

AOTS: PARAM-MISM

GE: WKSWPR

OTS: APC-OUT-OF-RANGE

BITS: HI-CCVOLT

GE: WTR

OTS: AS-CMD

BITS: SSM-DUS

ISC: ALS

OTS: AS-MT

BITS: SSM-LNC

ISC: AS-CMD

OTS: AWG-WARM-UP

BITS: SSM-OFF

ISC: AS-MT

OTS: OSRION

BITS: SSM-PRC

ISC: FAILTOSW

OTS: PARAM-MISM

BITS: SSM-PRS

ISC: FORCED-REQ-SPAN

OTS: PMI

BITS: SSM-RES

ISC: LOCKOUT-REQ

OTS: SHUTTER-OPEN

BITS: SSM-SETS

ISC: LPBKFACILITY

OTS: SPAN-NOT-MEASURED

BITS: SSM-SMC

ISC: LPBKTERMINAL

PPM: AS-CMD

BITS: SSM-ST2

ISC: MANUAL-REQ-SPAN

PPM: AS-MT

BITS: SSM-ST3

ISC: OUT-OF-SYNC

PWR: AS-CMD

BITS: SSM-ST3E

ISC: SQUELCHED

PWR: VOLT-MISM

BITS: SSM-ST4

ISC: WKSWPR

SHELF: AS-CMD

BITS: SSM-STU

ISC: WTR

SHELF: AS-MT

BITS: SSM-TNC

NE: APC-DISABLED

TRUNK: ALS

BITS: SYNC-FREQ

NE: APC-END

TRUNK: AS-CMD

BPLANE: AS-CMD

NE: AS-CMD

TRUNK: AS-MT

EQPT: ALS-DISABLED

NE: AUD-LOG-LOSS

TRUNK: FAILTOSW

EQPT: AS-CMD

NE: AUD-LOG-LOW

TRUNK: FEC-MISM

EQPT: AS-MT

NE: ETH-LINKLOSS

TRUNK: FORCED-REQ-SPAN

EQPT: FAILTOSW

NE: INTRUSION-PSWD

TRUNK: HELLO

EQPT: LOCKOUT-REQ

NE: LAN-POL-REV

TRUNK: LOCKOUT-REQ

EQPT: MAN-REQ

NE: TEMP-MISM

TRUNK: LPBKFACILITY

EQPT: MANRESET

NE-SREF: FRCDSWTOINT

TRUNK: LPBKTERMINAL

EQPT: OPEN-SLOT

NE-SREF: FRCDSWTOPRI

TRUNK: MANUAL-REQ-SPAN

EQPT: RUNCFG-SAVENEED

NE-SREF: FRCDSWTOSEC

TRUNK: ODUK-SD-PM

EQPT: SW-MISMATCH

NE-SREF: FRCDSWTOTHIRD

TRUNK: ODUK-SF-PM

EQPT: WKSWPR

NE-SREF: FRNGSYNC

TRUNK: OTUK-SD

EQPT: WTR

NE-SREF: FSTSYNC

TRUNK: OTUK-SF

ESCON: ALS

NE-SREF: HLDOVRSYNC

TRUNK: SD

ESCON: AS-CMD

NE-SREF: MANSWTOINT

TRUNK: SD-L

ESCON: AS-MT

NE-SREF: MANSWTOPRI

TRUNK: SF

ESCON: FAILTOSW

NE-SREF: MANSWTOSEC

TRUNK: SF-L

ESCON: FORCED-REQ-SPAN

NE-SREF: MANSWTOTHIRD

TRUNK: SQUELCHED

ESCON: LOCKOUT-REQ

NE-SREF: SSM-LNC

TRUNK: SSM-DUS

ESCON: LPBKFACILITY

NE-SREF: SSM-PRC

TRUNK: SSM-LNC

ESCON: LPBKTERMINAL

NE-SREF: SSM-PRS

TRUNK: SSM-OFF

ESCON: MANUAL-REQ-SPAN

NE-SREF: SSM-RES

TRUNK: SSM-PRC

ESCON: SQUELCHED

NE-SREF: SSM-SETS

TRUNK: SSM-PRS

ESCON: WKSWPR

NE-SREF: SSM-SMC

TRUNK: SSM-RES

ESCON: WTR

NE-SREF: SSM-ST2

TRUNK: SSM-SDH-TN

EXT-SREF: FRCDSWTOPRI

NE-SREF: SSM-ST3

TRUNK: SSM-SETS

EXT-SREF: FRCDSWTOSEC

NE-SREF: SSM-ST3E

TRUNK: SSM-SMC

EXT-SREF: FRCDSWTOTHIRD

NE-SREF: SSM-ST4

TRUNK: SSM-ST2

EXT-SREF: MANSWTOPRI

NE-SREF: SSM-STU

TRUNK: SSM-ST3

EXT-SREF: MANSWTOSEC

NE-SREF: SSM-TNC

TRUNK: SSM-ST3E

EXT-SREF: MANSWTOTHIRD

NE-SREF: SWTOPRI

TRUNK: SSM-ST4

EXT-SREF: SWTOPRI

NE-SREF: SWTOSEC

TRUNK: SSM-STU

EXT-SREF: SWTOSEC

NE-SREF: SWTOTHIRD

TRUNK: SSM-TNC

EXT-SREF: SWTOTHIRD

OCH: APC-CORRECTION-SKIPPED

TRUNK: SYNC-FREQ

FC: ALS

OCH: APC-OUT-OF-RANGE

TRUNK: TRAIL-SIGNAL-FAIL

FC: AS-CMD

OCH: AS-CMD

TRUNK: UNC-WORD

FC: AS-MT

OCH: AS-MT

TRUNK: WTR

FC: FAILTOSW

OCH: FDI

—

2.1.5  NR Conditions

Table 2-5 alphabetically lists Not Reported (NR) DWDM conditions.

Table 2-5 NR DWDM Conditions List

BITS: AIS

TRUNK: ODUK-3-AIS-PM

TRUNK: ODUK-OCI-PM

OCN: AIS-L

TRUNK: ODUK-4-AIS-PM

TRUNK: OTUK-AIS

TRUNK: AIS

TRUNK: ODUK-AIS-PM

TRUNK: OTUK-BDI

TRUNK: AIS-L

TRUNK: ODUK-BDI-PM

TRUNK: RFI

TRUNK: ODUK-1-AIS-PM

TRUNK: ODUK-LCK-PM

TRUNK: RFI-L

TRUNK: ODUK-2-AIS-PM

—

—

2.1.6  Alarms and Conditions Listed By Alphabetical Entry

Table 2-6 alphabetically lists all DWDM alarms and conditions.

Table 2-6 Alphabetical DWDM Alarm and Condition List

AIS (BITS)

HITEMP (NE)

PARAM-MISM (OCH)

ALS (2R)

HITEMP (EQPT)

PARAM-MISM (OMS)

AIS (TRUNK)

HI-TXPOWER (2R)

PARAM-MISM (OTS)

AIS-L (OCN)

HI-TXPOWER (EQPT)

PEER-NORESPONSE (EQPT)

AIS-L (TRUNK)

HI-TXPOWER (ESCON)

PMI (OMS)

ALS (AOTS)

HI-TXPOWER (FC)

PMI (OTS)

ALS (ESCON)

HI-TXPOWER (GE)

PORT-ADD-PWR-DEG-HI (OCH)

ALS (FC)

HI-TXPOWER (ISC)

PORT-ADD-PWR-DEG-LOW (OCH)

ALS (GE)

HI-TXPOWER (OCN)

PORT-ADD-PWR-FAIL-HIGH (OCH)

ALS (ISC)

HI-TXPOWER (PPM)

PORT-ADD-PWR-FAIL-LOW (OCH)

ALS (OCN)

HLDOVRSYNC (NE-SREF)

PORT-FAIL (OCH)

ALS (TRUNK)

I-HITEMP (NE)

PROTNA (EQPT)

ALS-DISABLED (EQPT)

IMPROPRMVL (EQPT)

PROV-MISMATCH (PPM)

AMPLI-INIT (AOTS)

IMPROPRMVL (PPM)

PROV-MISMATCH (TRUNK)

APC-CORRECTION-SKIPPED (AOTS)

INTRUSION-PSWD (NE)

PTIM (TRUNK)

APC-CORRECTION-SKIPPED (OCH)

INVMACADR (AIP)

PWR-FAIL-A (EQPT)

APC-CORRECTION-SKIPPED (OMS)

LAN-POL-REV (NE)

PWR-FAIL-B (EQPT)

APC-CORRECTION-SKIPPED (OTS)

LASER-APR (AOTS)

PWR-FAIL-RET-A (EQPT)

APC-DISABLED (NE)

LASERBIAS-DEG (AOTS)

PWR-FAIL-RET-B (EQPT)

APC-END (NE)

LASERBIAS-DEG (OTS)

RFI (TRUNK)

APC-OUT-OF-RANGE (AOTS)

LASERBIAS-FAIL (AOTS)

RFI-L (TRUNK)

APC-OUT-OF-RANGE (OCH)

LASERTEMP-DEG (AOTS)

RING-ID-MIS (OSC-RING)

APC-OUT-OF-RANGE (OMS)

LOCKOUT-REQ (2R)

ROUTE-OVERFLOW (NE)

APC-OUT-OF-RANGE (OTS)

LOCKOUT-REQ (EQPT)

RUNCFG-SAVENEED (EQPT)

AS-CMD (2R)

LOCKOUT-REQ (ESCON)

SD (TRUNK)

AS-CMD (AOTS)

LOCKOUT-REQ (FC)

SD-L (TRUNK)

AS-CMD (BPLANE)

LOCKOUT-REQ (GE)

SF (TRUNK)

AS-CMD (EQPT)

LOCKOUT-REQ (ISC)

SF-L (TRUNK)

AS-CMD (ESCON)

LOCKOUT-REQ (TRUNK)

SFTWDOWN (EQPT)

AS-CMD (FC)

LOF (BITS)

SHELF-COMM-FAIL (SHELF)

AS-CMD (GE)

LOF (TRUNK)

SH-INS-LOSS-VAR-DEG-HIGH (OTS)

AS-CMD (ISC)

LO-LASERBIAS (EQPT)

SH-INS-LOSS-VAR-DEG-LOW (OTS)

AS-CMD (NE)

LO-LASERBIAS (OCN)

SHUTTER-OPEN (OTS)

AS-CMD (OCH)

LO-LASERBIAS (PPM)

SIGLOSS (ESCON)

AS-CMD (OCN)

LO-LASERTEMP (EQPT)

SIGLOSS (FC)

AS-CMD (OMS)

LO-LASERTEMP (OCN)

SIGLOSS (GE)

AS-CMD (OTS)

LO-LASERTEMP (PPM)

SIGLOSS (ISC)

AS-CMD (PPM)

LOM (TRUNK)

SIGLOSS (TRUNK)

AS-CMD (PWR)

LO-RXPOWER (2R)

SNTP-HOST (NE)

AS-CMD (SHELF)

LO-RXPOWER (ESCON)

SPANLENGTH-OUT-OF-RANGE (OTS)

AS-CMD (TRUNK)

LO-RXPOWER (FC)

SPAN-NOT-MEASURED (OTS)

AS-MT (2R)

LO-RXPOWER (GE)

SQUELCHED (2R)

AS-MT (AOTS)

LO-RXPOWER (ISC)

SQUELCHED (ESCON)

AS-MT (EQPT)

LO-RXPOWER (OCN)

SQUELCHED (FC)

AS-MT (ESCON)

LOS (2R)

SQUELCHED (GE)

AS-MT (FC)

LOS (BITS)

SQUELCHED (ISC)

AS-MT (GE)

LOS (ESCON)

SQUELCHED (OCN)

AS-MT (ISC)

LOS (ISC)

SQUELCHED (TRUNK)

AS-MT (OCH)

LOS (OTS)

SSM-DUS (BITS)

AS-MT (OCN)

LOS (TRUNK)

SSM-DUS (TRUNK)

AS-MT (OMS)

LOS-O (OCH)

SSM-FAIL (BITS)

AS-MT (OTS)

LOS-O (OMS)

SSM-FAIL (TRUNK)

AS-MT (PPM)

LOS-O (OTS)

SSM-LNC (BITS)

AS-MT (SHELF)

LOS-P (OCH)

SSM-LNC (NE-SREF)

AS-MT (TRUNK)

LOS-P (OMS)

SSM-LNC (TRUNK)

AUD-LOG-LOSS (NE)

LOS-P (OTS)

SSM-OFF (BITS)

AUD-LOG-LOW (NE)

LOS-P (TRUNK)

SSM-OFF (TRUNK)

AUTORESET (EQPT)

LO-TXPOWER (2R)

SSM-PRC (BITS)

AWG-DEG (OTS)

LO-TXPOWER (EQPT)

SSM-PRC (NE-SREF)

AWG-FAIL (OTS)

LO-TXPOWER (ESCON)

SSM-PRC (TRUNK)

AWG-OVERTEMP (OTS)

LO-TXPOWER (FC)

SSM-PRS (BITS)

AWG-WARM-UP (OTS)

LO-TXPOWER (GE)

SSM-PRS (NE-SREF)

BAT-FAIL (PWR)

LO-TXPOWER (ISC)

SSM-PRS (TRUNK)

BKUPMEMP (EQPT)

LO-TXPOWER (OCN)

SSM-RES (BITS)

BPV (BITS)

LO-TXPOWER (PPM)

SSM-RES (NE-SREF)

CARLOSS (EQPT)

LPBKFACILITY (ESCON)

SSM-RES (TRUNK)

CARLOSS (FC)

LPBKFACILITY (FC)

SSM-SDH-TN (TRUNK)

CARLOSS (GE)

LPBKFACILITY (GE)

SSM-SETS (BITS)

CARLOSS (ISC)

LPBKFACILITY (ISC)

SSM-SETS (NE-SREF)

CARLOSS (TRUNK)

LPBKFACILITY (TRUNK)

SSM-SETS (TRUNK)

CASETEMP-DEG (AOTS)

LPBKTERMINAL (ESCON)

SSM-SMC (BITS)

DATAFLT (NE)

LPBKTERMINAL (FC)

SSM-SMC (NE-SREF)

DBOSYNC (NE)

LPBKTERMINAL (GE)

SSM-SMC (TRUNK)

DSP-COMM-FAIL (TRUNK)

LPBKTERMINAL (ISC)

SSM-ST2 (BITS)

DSP-FAIL (TRUNK)

LPBKTERMINAL (TRUNK)

SSM-ST2 (NE-SREF)

DUP-IPADDR (NE)

LWBATVG (PWR)

SSM-ST2 (TRUNK)

DUP-NODENAME (NE)

MAN-REQ (EQPT)

SSM-ST3 (BITS)

DUP-SHELF-ID (SHELF)

MANRESET (EQPT)

SSM-ST3 (NE-SREF)

EHIBATVG (PWR)

MANSWTOINT (NE-SREF)

SSM-ST3 (TRUNK)

ELWBATVG (PWR)

MANSWTOPRI (EXT-SREF)

SSM-ST3E (BITS)

EOC (OCN)

MANSWTOPRI (NE-SREF)

SSM-ST3E (NE-SREF)

EOC (TRUNK)

MANSWTOSEC (EXT-SREF)

SSM-ST3E (TRUNK)

EOC-L (OCN)

MANSWTOSEC (NE-SREF)

SSM-ST4 (BITS)

EOC-L (TRUNK)

MANSWTOTHIRD (EXT-SREF)

SSM-ST4 (NE-SREF)

EQPT (EQPT)

MANSWTOTHIRD (NE-SREF)

SSM-ST4 (TRUNK)

EQPT (AICI-AEP)

MANUAL-REQ-SPAN (2R)

SSM-STU (BITS)

EQPT (AICI-AIE)

MANUAL-REQ-SPAN (ESCON)

SSM-STU (NE-SREF)

EQPT (PPM)

MANUAL-REQ-SPAN (FC)

SSM-STU (TRUNK)

EQPT-MISS (FAN)

MANUAL-REQ-SPAN (GE)

SSM-TNC (BITS)

ETH-LINKLOSS (NE)

MANUAL-REQ-SPAN (ISC)

SSM-TNC (NE-SREF)

EXCCOL (EQPT)

MANUAL-REQ-SPAN (OCN)

SSM-TNC (TRUNK)

EXT (ENVALRM)

MANUAL-REQ-SPAN (TRUNK)

SW-MISMATCH (EQPT)

FAILTOSW (2R)

MEA (EQPT)

SWTOPRI (EXT-SREF)

FAILTOSW (EQPT)

MEA (AIP)

SWTOPRI (NE-SREF)

FAILTOSW (ESCON)

MEA (FAN)

SWTOSEC (EXT-SREF)

FAILTOSW (FC)

MEA (PPM)

SWTOSEC (NE-SREF)

FAILTOSW (GE)

MEA (SHELF)

SWTOTHIRD (EXT-SREF)

FAILTOSW (ISC)

MEM-GONE (EQPT)

SWTOTHIRD (NE-SREF)

FAILTOSW (OCN)

MEM-LOW (EQPT)

SYNC-FREQ (BITS)

FAILTOSW (TRUNK)

MFGMEM (AICI-AEP)

SYNC-FREQ (TRUNK)

FAN (FAN)

MFGMEM (AICI-AIE)

SYNCLOSS (FC)

FC-NO-CREDITS (FC)

MFGMEM (AIP)

SYNCLOSS (GE)

FC-NO-CREDITS (TRUNK)

MFGMEM (BPLANE)

SYNCLOSS (ISC)

FDI (OCH)

MFGMEM (FAN)

SYNCLOSS (TRUNK)

FEC-MISM (TRUNK)

MFGMEM (PPM)

SYNCPRI (EXT-SREF)

FIBERTEMP-DEG (AOTS)

NET-POOL-LOW (NE)

SYNCPRI (NE-SREF)

FORCED-REQ-SPAN (ESCON)

OCHNC-INC (OCHNC-CONN)

SYNCSEC (EXT-SREF)

FORCED-REQ-SPAN (FC)

OCHTERM-INC (OCH-TERM)

SYNCSEC (NE-SREF)

FORCED-REQ-SPAN (GE)

ODUK-1-AIS-PM (TRUNK)

SYNCTHIRD (EXT-SREF)

FORCED-REQ-SPAN (ISC)

ODUK-2-AIS-PM (TRUNK)

SYNCTHIRD (NE-SREF)

FORCED-REQ-SPAN (OCN)

ODUK-3-AIS-PM (TRUNK)

SYSBOOT (NE)

FORCED-REQ-SPAN (TRUNK)

ODUK-4-AIS-PM (TRUNK)

TEMP-MISM (NE)

FORCED-REQ-SPAN (2R)

ODUK-AIS-PM (TRUNK)

TIM (TRUNK)

FRCDSWTOINT (NE-SREF)

ODUK-BDI-PM (TRUNK)

TIM-MON (TRUNK)

FRCDSWTOPRI (EXT-SREF)

ODUK-LCK-PM (TRUNK)

TRAIL-SIGNAL-FAIL (OCH)

FRCDSWTOPRI (NE-SREF)

ODUK-OCI-PM (TRUNK)

TRAIL-SIGNAL-FAIL (TRUNK)

FRCDSWTOSEC (EXT-SREF)

ODUK-SD-PM (TRUNK)

UNC-WORD (TRUNK)

FRCDSWTOSEC (NE-SREF)

ODUK-SF-PM (TRUNK)

UNREACHABLE-TARGET-POWER (OCH)

FRCDSWTOTHIRD (EXT-SREF)

ODUK-TIM-PM (TRUNK)

UT-COMM-FAIL (TRUNK)

FRCDSWTOTHIRD (NE-SREF)

OPEN-SLOT (EQPT)

UT-FAIL (TRUNK)

FRNGSYNC (NE-SREF)

OPTNTWMIS (NE)

VOA-HDEG (AOTS)

FSTSYNC (NE-SREF)

OPWR-HDEG (AOTS)

VOA-HDEG (OCH)

GAIN-HDEG (AOTS)

OPWR-HDEG (OCH)

VOA-HDEG (OMS)

GAIN-HFAIL (AOTS)

OPWR-HDEG (OMS)

VOA-HDEG (OTS)

GAIN-LDEG (AOTS)

OPWR-HDEG (OTS)

VOA-HFAIL (AOTS)

GAIN-LFAIL (AOTS)

OPWR-HFAIL (AOTS)

VOA-HFAIL (OCH)

GCC-EOC (TRUNK)

OPWR-HFAIL (OCH)(OCH)

VOA-HFAIL (OMS)

GE-OOSYNC (FC)

OPWR-HFAIL (OMS)

VOA-HFAIL (OTS)

GE-OOSYNC (GE)

OPWR-HFAIL (OTS)

VOA-LDEG (AOTS)

GE-OOSYNC (ISC)

OPWR-LDEG (AOTS)

VOA-LDEG (OCH)

GE-OOSYNC (TRUNK)

OPWR-LDEG (OCH)

VOA-LDEG (OMS)

HELLO (TRUNK)

OPWR-LDEG (OMS)

VOA-LDEG (OTS)

HIBATVG (PWR)

OPWR-LDEG (OTS)

VOA-LFAIL (AOTS)

HI-CCVOLT (BITS)

OPWR-LFAIL (AOTS)

VOA-LFAIL (OCH)

HI-LASERBIAS (2R)

OPWR-LFAIL (OCH)

VOA-LFAIL (OMS)

HI-LASERBIAS (EQPT)

OPWR-LFAIL (OMS)

VOA-LFAIL (OTS)

HI-LASERBIAS (ESCON)

OPWR-LFAIL (OTS)

VOLT-MISM (PWR)

HI-LASERBIAS (FC)

OSRION (AOTS)

WKSWPR (2R)

HI-LASERBIAS (GE)

OSRION (OTS)

WKSWPR (EQPT)

HI-LASERBIAS (ISC)

OTUK-AIS (TRUNK)

WKSWPR (ESCON)

HI-LASERBIAS (OCN)

OTUK-BDI (TRUNK)

WKSWPR (FC)

HI-LASERBIAS (PPM)

OTUK-IAE (TRUNK)

WKSWPR (GE)

HI-LASERTEMP (OCN)

OTUK-LOF (TRUNK)

WKSWPR (ISC)

HI-LASERTEMP (PPM)

OTUK-SD (TRUNK)

WTR (2R)

HI-LASERTEMP (EQPT)

OTUK-SF (TRUNK)

WTR (EQPT)

HI-RXPOWER (2R)

OTUK-TIM (TRUNK)

WTR (ESCON)

HI-RXPOWER (ESCON)

OUT-OF-SYNC (FC)

WTR (FC)

HI-RXPOWER (FC)

OUT-OF-SYNC (GE)

WTR (GE)

HI-RXPOWER (GE)

OUT-OF-SYNC (ISC)

WTR (ISC)

HI-RXPOWER (ISC)

OUT-OF-SYNC (TRUNK)

WTR (TRUNK)

HI-RXPOWER (OCN)

PARAM-MISM (AOTS)

WVL-MISMATCH (TRUNK)

2.2  Logical Objects

The CTC alarm profile list organizes all alarms and conditions according to the logical objects they are raised against. These logical objects represent physical objects such as cards, logical objects such as circuits, or transport and signal monitoring entities such as the SONET or ITU-T G.709 optical overhead bits. One alarm can appear in multiple entries. It can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (OC-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both OCN: LOS and OTN: LOS appear in the list (as well as the other objects).

Alarm profile list objects are defined in Table 2-7.

Note Alarm logical object names can appear as abbreviated versions of standard terms used in the system and the documentation. For example, the "OCN" logical object refers to the OC-N signal. Logical object names or industry-standard terms are used within the entries as appropriate.

2.2.1  Alarm Logical Objects

Table 2-7 lists all logical alarm objects used in this chapter.

Table 2-7 Alarm Logical Object Type Definitions

Logical Object

Definition

2R

Reshape and retransmit (used for transponder [TXP] cards).

AICI-AEP

Alarm Interface Controller-International/alarm expansion panel. A combination term that refers to this platform's AIC-I card.

AICI-AIE

Alarm Interface Controller-International/Alarm Interface Extension. A combination term that refers to this platform's AIC-I card.

AOTS

Amplified optical transport section.

BITS

Building integrated timing supply incoming references (BITS-1, BITS-2).

BPLANE

The backplane.

ENVALRM

An environmental alarm port.

EQPT

A card, its physical objects, and its logical objects as they are located in any of the eight noncommon card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signals (STS), and virtual tributaries (VT).

ESCON

Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G.

EXT-SREF

BITS outgoing references (SYNC-BITS1, SYNC-BITS2).

FAN

Fan-tray assembly.

FC

Fibre channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L

GE

Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10G, TXP_MR_10E,TXP_MR_10E_C, TXP_MR_10E_L, MXP_MR_10DME_C, MXP_MR_10DME_L.

ISC

Inter-service channel, referring to TXPP_MR_2.5G or TXP_MR_2.5G cards.

NE

The entire network element.

NE-SREF

The timing status of the NE.

OCH

The optical channel, referring to dense wavelength division multiplexing (DWDM) cards.

OCHNC-CONN

The optical channel network connection, referring to DWDM cards.

OMS

Optical multiplex section.

OSC-RING

Optical service channel ring.

OTS

Optical transport section.

PPM

Pluggable port module (PPM, also called SFP), referring to MXP and TXP cards.

PWR

Power equipment.

TRUNK

The optical or DWDM card carrying the high-speed signal; referring to MXP or TXP cards.

2.2.2  Alarm List by Logical Object Type

Table 2-8 lists all Release 7.0 DWDM alarms and logical objects as they are given in the system alarm profile. The list entries are organized by logical object name and then by alarm or condition name. Where appropriate, the alarm entries also contain troubleshooting procedures.

Note In a mixed network containing different types of nodes (for example, ONS 15310-CL, ONS 15454, and ONS 15600), the initially displayed alarm list in the node view (single-shelf mode) or shelf view (multishelf mode) Provisioning > Alarm Profiles tabs > Alarm Profile Editor tab lists all conditions that are applicable to all nodes in the network. However, when you load the default severity profile from a node, only applicable alarms will display severity levels. Nonapplicable alarms can display "use default" or "unset."

Note In some cases this list does not follow alphabetical order, but it does reflect the order shown in CTC.

Table 2-8 Alarm List by Logical Object in Alarm Profile

2R: ALS (NA)

FC: HI-LASERBIAS (MN)

OCN: SQUELCHED (NA)

2R: AS-CMD (NA)

FC: HI-RXPOWER (MN)

OMS: APC-CORRECTION-SKIPPED (NA)

2R: AS-MT (NA)

FC: HI-TXPOWER (MN)

OMS: APC-OUT-OF-RANGE (NA)

2R: FAILTOSW (NA)

FC: LOCKOUT-REQ (NA)

OMS: AS-CMD (NA)

2R: FORCED-REQ-SPAN (NA)

FC: LO-RXPOWER (MN)

OMS: AS-MT (NA)

2R: HI-LASERBIAS (MN)

FC: LO-TXPOWER (MN)

OMS: LOS-O (MN)

2R: HI-RXPOWER (MN)

FC: LPBKFACILITY (NA)

OMS: LOS-P (CR)

2R: HI-TXPOWER (MN)

FC: LPBKTERMINAL (NA)

OMS: OPWR-HDEG (MN)

2R: LOCKOUT-REQ (NA)

FC: MANUAL-REQ-SPAN (NA)

OMS: OPWR-HFAIL (CR)

2R: LO-RXPOWER (MN)

FC: OUT-OF-SYNC (MJ)

OMS: OPWR-LDEG (MN)

2R: LOS (CR)

FC: SIGLOSS (MJ)

OMS: OPWR-LFAIL (CR)

2R: LO-TXPOWER (MN)

FC: SQUELCHED (NA)

OMS: PARAM-MISM (NA)

2R: MANUAL-REQ-SPAN (NA)

FC: SYNCLOSS (MJ)

OMS: PMI (NA)

2R: SQUELCHED (NA)

FC: WKSWPR (NA)

OMS: VOA-HDEG (MN)

2R: WKSWPR (NA)

FC: WTR (NA)

OMS: VOA-HFAIL (CR)

2R: WTR (NA)

GE: ALS (NA)

OMS: VOA-LDEG (MN)

AICI-AEP: EQPT (CR)

GE: AS-CMD (NA)

OMS: VOA-LFAIL (CR)

AICI-AEP: MFGMEM (CR)

GE: AS-MT (NA)

OSC-RING: RING-ID-MIS (MJ)

AICI-AIE: EQPT (CR)

GE: CARLOSS (MJ)

OTS: APC-CORRECTION-SKIPPED (NA)

AICI-AIE: MFGMEM (CR)

GE: FAILTOSW (NA)

OTS: APC-OUT-OF-RANGE (NA)

AIP: INVMACADR (MJ)

GE: FORCED-REQ-SPAN (NA)

OTS: AS-CMD (NA)

AIP: MEA (CR)

GE: GE-OOSYNC (CR)

OTS: AS-MT (NA)

AIP: MFGMEM (CR)

GE: HI-LASERBIAS (MN)

OTS: AWG-DEG (MN)

AOTS: ALS (NA)

GE: HI-RXPOWER (MN)

OTS: AWG-FAIL (CR)

AOTS: AMPLI-INIT (NA)

GE: HI-TXPOWER (MN)

OTS: AWG-OVERTEMP (CR)

AOTS: APC-CORRECTION-SKIPPED (NA)

GE: LOCKOUT-REQ (NA)

OTS: AWG-WARM-UP (NA)

AOTS: APC-OUT-OF-RANGE (NA)

GE: LO-RXPOWER (MN)

OTS: LASERBIAS-DEG (MN)

AOTS: AS-CMD (NA)

GE: LO-TXPOWER (MN)

OTS: LOS (CR)

AOTS: AS-MT (NA)

GE: LPBKFACILITY (NA)

OTS: LOS-O (MN)

AOTS: CASETEMP-DEG (MN)

GE: LPBKTERMINAL (NA)

OTS: LOS-P (CR)

AOTS: FIBERTEMP-DEG (MN)

GE: MANUAL-REQ-SPAN (NA)

OTS: OPWR-HDEG (MN)

AOTS: GAIN-HDEG (MN)

GE: OUT-OF-SYNC (MJ)

OTS: OPWR-HFAIL (CR)

AOTS: GAIN-HFAIL (CR)

GE: SIGLOSS (MJ)

OTS: OPWR-LDEG (MN)

AOTS: GAIN-LDEG (MN)

GE: SQUELCHED (NA)

OTS: OPWR-LFAIL (CR)

AOTS: GAIN-LFAIL (CR)

GE: SYNCLOSS (MJ)

OTS: OSRION (NA)

AOTS: LASER-APR (NA)

GE: WKSWPR (NA)

OTS: PARAM-MISM (NA)

AOTS: LASERBIAS-DEG (MN)

GE: WTR (NA)

OTS: PMI (NA)

AOTS: LASERBIAS-FAIL (MJ)

ISC: ALS (NA)

OTS: SH-INS-LOSS-VAR-DEG-HIGH (MN)

AOTS: LASERTEMP-DEG (MN)

ISC: AS-CMD (NA)

OTS: SH-INS-LOSS-VAR-DEG-LOW (MN)

AOTS: OPWR-HDEG (MN)

ISC: AS-MT (NA)

OTS: SHUTTER-OPEN (NA)

AOTS: OPWR-HFAIL (CR)

ISC: CARLOSS (MJ)

OTS: SPANLENGTH-OUT-OF-RANGE (MN)

AOTS: OPWR-LDEG (MN)

ISC: FAILTOSW (NA)

OTS: SPAN-NOT-MEASURED (NA)

AOTS: OPWR-LFAIL (CR)

ISC: FORCED-REQ-SPAN (NA)

OTS: VOA-HDEG (MN)

AOTS: OSRION (NA)

ISC: GE-OOSYNC (CR)

OTS: VOA-HFAIL (CR)

AOTS: PARAM-MISM (NA)

ISC: HI-LASERBIAS (MN)

OTS: VOA-LDEG (MN)

AOTS: VOA-HDEG (MN)

ISC: HI-RXPOWER (MN)

OTS: VOA-LFAIL (CR)

AOTS: VOA-HFAIL (CR)

ISC: HI-TXPOWER (MN)

PPM: AS-CMD (NA)

AOTS: VOA-LDEG (MN)

ISC: LOCKOUT-REQ (NA)

PPM: AS-MT (NA)

AOTS: VOA-LFAIL (CR)

ISC: LO-RXPOWER (MN)

PPM: EQPT (CR)

BITS: AIS (NR)

ISC: LOS (CR)

PPM: HI-LASERBIAS (MN)

BITS: BPV (MN)

ISC: LO-TXPOWER (MN)

PPM: HI-LASERTEMP (MN)

BITS: HI-CCVOLT (NA)

ISC: LPBKFACILITY (NA)

PPM: HI-TXPOWER (MN)

BITS: LOF (MN)

ISC: LPBKTERMINAL (NA)

PPM: IMPROPRMVL (CR)

BITS: LOS (MN)

ISC: MANUAL-REQ-SPAN (NA)

PPM: LO-LASERBIAS (MN)

BITS: SSM-DUS (NA)

ISC: OUT-OF-SYNC (NA)

PPM: LO-LASERTEMP (MN)

BITS: SSM-FAIL (MN)

ISC: SIGLOSS (MJ)

PPM: LO-TXPOWER (MN)

BITS: SSM-LNC (NA)

ISC: SQUELCHED (NA)

PPM: MEA (CR)

BITS: SSM-OFF (NA)

ISC: SYNCLOSS (MJ)

PPM: MFGMEM (CR)

BITS: SSM-PRC (NA)

ISC: WKSWPR (NA)

PPM: PROV-MISMATCH (MN)

BITS: SSM-PRS (NA)

ISC: WTR (NA)

PWR: AS-CMD (NA)

BITS: SSM-RES (NA)

NE: APC-DISABLED (NA)

PWR: BAT-FAIL (MJ)

BITS: SSM-SETS (NA)

NE: APC-END (NA)

PWR: EHIBATVG (MJ)

BITS: SSM-SMC (NA)

NE: AS-CMD (NA)

PWR: ELWBATVG (MJ)

BITS: SSM-ST2 (NA)

NE: AUD-LOG-LOSS (NA)

PWR: HIBATVG (MJ)

BITS: SSM-ST3 (NA)

NE: AUD-LOG-LOW (NA)

PWR: LWBATVG (MJ)

BITS: SSM-ST3E (NA)

NE: DATAFLT (MN)

PWR: VOLT-MISM (NA)

BITS: SSM-ST4 (NA)

NE: DBOSYNC (MJ)

SHELF: AS-CMD (NA)

BITS: SSM-STU (NA)

NE: DUP-IPADDR (MN)

SHELF: AS-MT (NA)

BITS: SSM-TNC (NA)

NE: DUP-NODENAME (MN)

SHELF: DUP-SHELF-ID (MJ)

BITS: SYNC-FREQ (NA)

NE: ETH-LINKLOSS (NA)

SHELF: MEA (MJ)

BPLANE: AS-CMD (NA)

NE: HITEMP (CR)

SHELF: SHELF-COMM-FAIL (MJ)

BPLANE: MFGMEM (CR)

NE: I-HITEMP (CR)

TRUNK: AIS (NR)

ENVALRM: EXT (MN)

NE: INTRUSION-PSWD (NA)

TRUNK: AIS-L (NR)

EQPT: ALS-DISABLED (NA)

NE: LAN-POL-REV (NA)

TRUNK: ALS (NA)

EQPT: AS-CMD (NA)

NE: NET-POOL-LOW (MN)

TRUNK: AS-CMD (NA)

EQPT: AS-MT (NA)

NE: OPTNTWMIS (MJ)

TRUNK: AS-MT (NA)

EQPT: AUTORESET (MN)

NE: ROUTE-OVERFLOW (MN)

TRUNK: CARLOSS (MJ)

EQPT: BKUPMEMP (CR)

NE: SNTP-HOST (MN)

TRUNK: DSP-COMM-FAIL (MJ)

EQPT: CARLOSS (MJ)

NE: SYSBOOT (MJ)

TRUNK: DSP-FAIL (MJ)

EQPT: EQPT (CR)

NE: TEMP-MISM (NA)

TRUNK: EOC (MN)

EQPT: EXCCOL (MN)

NE-SREF: FRCDSWTOINT (NA)

TRUNK: EOC-L (MN)

EQPT: FAILTOSW (NA)

NE-SREF: FRCDSWTOPRI (NA)

TRUNK: FAILTOSW (NA)

EQPT: HI-LASERBIAS (MN)

NE-SREF: FRCDSWTOSEC (NA)

TRUNK: FC-NO-CREDITS (MJ)

EQPT: HI-LASERTEMP (MN)

NE-SREF: FRCDSWTOTHIRD (NA)

TRUNK: FEC-MISM (NA)

EQPT: HITEMP (MN)

NE-SREF: FRNGSYNC (NA)

TRUNK: FORCED-REQ-SPAN (NA)

EQPT: HI-TXPOWER (MN)

NE-SREF: FSTSYNC (NA)

TRUNK: GCC-EOC (MN)

EQPT: IMPROPRMVL (CR)

NE-SREF: HLDOVRSYNC (NA)

TRUNK: GE-OOSYNC (CR)

EQPT: LOCKOUT-REQ (NA)

NE-SREF: MANSWTOINT (NA)

TRUNK: HELLO (NA)

EQPT: LO-LASERBIAS (MN)

NE-SREF: MANSWTOPRI (NA)

TRUNK: LOCKOUT-REQ (NA)

EQPT: LO-LASERTEMP (MN)

NE-SREF: MANSWTOSEC (NA)

TRUNK: LOF (CR)

EQPT: LO-TXPOWER (MN)

NE-SREF: MANSWTOTHIRD (NA)

TRUNK: LOM (CR)

EQPT: MAN-REQ (NA)

NE-SREF: SSM-LNC (NA)

TRUNK: LOS (CR)

EQPT: MANRESET (NA)

NE-SREF: SSM-PRC (NA)

TRUNK: LOS-P (CR)

EQPT: MEA (CR)

NE-SREF: SSM-PRS (NA)

TRUNK: LPBKFACILITY (NA)

EQPT: MEM-GONE (MJ)

NE-SREF: SSM-RES (NA)

TRUNK: LPBKTERMINAL (NA)

EQPT: MEM-LOW (MN)

NE-SREF: SSM-SETS (NA)

TRUNK: MANUAL-REQ-SPAN (NA)

EQPT: OPEN-SLOT (NA)

NE-SREF: SSM-SMC (NA)

TRUNK: ODUK-1-AIS-PM (NR)

EQPT: PEER-NORESPONSE (MJ)

NE-SREF: SSM-ST2 (NA)

TRUNK: ODUK-2-AIS-PM (NR)

EQPT: PROTNA (MN)

NE-SREF: SSM-ST3 (NA)

TRUNK: ODUK-3-AIS-PM (NR)

EQPT: PWR-FAIL-A (MN)

NE-SREF: SSM-ST3E (NA)

TRUNK: ODUK-4-AIS-PM (NR)

EQPT: PWR-FAIL-B (MN)

NE-SREF: SSM-ST4 (NA)

TRUNK: ODUK-AIS-PM (NR)

EQPT: PWR-FAIL-RET-A (MN)

NE-SREF: SSM-STU (NA)

TRUNK: ODUK-BDI-PM (NR)

EQPT: PWR-FAIL-RET-B (MN)

NE-SREF: SSM-TNC (NA)

TRUNK: ODUK-LCK-PM (NR)

EQPT: RUNCFG-SAVENEED (NA)

NE-SREF: SWTOPRI (NA)

TRUNK: ODUK-OCI-PM (NR)

EQPT: SFTWDOWN (MN)

NE-SREF: SWTOSEC (NA)

TRUNK: ODUK-SD-PM (NA)

EQPT: SW-MISMATCH (NA)

NE-SREF: SWTOTHIRD (NA)

TRUNK: ODUK-SF-PM (NA)

EQPT: WKSWPR (NA)

NE-SREF: SYNCPRI (MJ)

TRUNK: ODUK-TIM-PM (MJ)

EQPT: WTR (NA)

NE-SREF: SYNCSEC (MN)

TRUNK: OTUK-AIS (NR)

ESCON: ALS (NA)

NE-SREF: SYNCTHIRD (MN)

TRUNK: OTUK-BDI (NR)

ESCON: AS-CMD (NA)

OCH: APC-CORRECTION-SKIPPED (NA)

TRUNK: OTUK-IAE (MN)

ESCON: AS-MT (NA)

OCH: APC-OUT-OF-RANGE (NA)

TRUNK: OTUK-LOF (CR)

ESCON: FAILTOSW (NA)

OCH: AS-CMD (NA)

TRUNK: OTUK-SD (NA)

ESCON: FORCED-REQ-SPAN (NA)

OCH: AS-MT (NA)

TRUNK: OTUK-SF (NA)

ESCON: HI-LASERBIAS (MN)

OCH: FDI (NA)

TRUNK: OTUK-TIM (CR)

ESCON: HI-RXPOWER (MN)

OCH: LOS-O (MN)

TRUNK: OUT-OF-SYNC (MJ)

ESCON: HI-TXPOWER (MN)

OCH: LOS-P (CR)

TRUNK: PROV-MISMATCH (MJ)

ESCON: LOCKOUT-REQ (NA)

OCH: OPWR-HDEG (MN)

TRUNK: PTIM (MJ)

ESCON: LO-RXPOWER (MN)

OCH: OPWR-HFAIL (CR)

TRUNK: RFI (NR)

ESCON: LOS (CR)

OCH: OPWR-LDEG (MN)

TRUNK: RFI-L (NR)

ESCON: LO-TXPOWER (MN)

OCH: OPWR-LFAIL (CR)

TRUNK: SD (NA)

ESCON: LPBKFACILITY (NA)

OCH: PARAM-MISM (NA)

TRUNK: SD-L (NA)

ESCON: LPBKTERMINAL (NA)

OCH: PORT-ADD-PWR-DEG-HI (MN)

TRUNK: SF (NA)

ESCON: MANUAL-REQ-SPAN (NA)

OCH: PORT-ADD-PWR-DEG-LOW (MN)

TRUNK: SF-L (NA)

ESCON: SIGLOSS (MJ)

OCH: PORT-ADD-PWR-FAIL-HIGH (CR)

TRUNK: SIGLOSS (MJ)

ESCON: SQUELCHED (NA)

OCH: PORT-ADD-PWR-FAIL-LOW (CR)

TRUNK: SQUELCHED (NA)

ESCON: WKSWPR (NA)

OCH: PORT-FAIL (CR)

TRUNK: SSM-DUS (NA)

ESCON: WTR (NA)

OCH: TRAIL-SIGNAL-FAIL (NA)

TRUNK: SSM-FAIL (MN)

EXT-SREF: FRCDSWTOPRI (NA)

OCH: UNREACHABLE-TARGET-POWER (MN)

TRUNK: SSM-LNC (NA)

EXT-SREF: FRCDSWTOSEC (NA)

OCH: VOA-HDEG (MN)

TRUNK: SSM-OFF (NA)

EXT-SREF: FRCDSWTOTHIRD (NA)

OCH: VOA-HFAIL (CR)

TRUNK: SSM-PRC (NA)

EXT-SREF: MANSWTOPRI (NA)

OCH: VOA-LDEG (MN)

TRUNK: SSM-PRS (NA)

EXT-SREF: MANSWTOSEC (NA)

OCH: VOA-LFAIL (CR)

TRUNK: SSM-RES (NA)

EXT-SREF: MANSWTOTHIRD (NA)

OCHNC-CONN: OCHNC-INC (NA)

TRUNK: SSM-SDH-TN (NA)

EXT-SREF: SWTOPRI (NA)

OCH-TERM: OCHTERM-INC (NA)

TRUNK: SSM-SETS (NA)

EXT-SREF: SWTOSEC (NA)

OCN: AIS-L (NR)

TRUNK: SSM-SMC (NA)

EXT-SREF: SWTOTHIRD (NA)

OCN: ALS (NA)

TRUNK: SSM-ST2 (NA)

EXT-SREF: SYNCPRI (MN)

OCN: AS-CMD (NA)

TRUNK: SSM-ST3 (NA)

EXT-SREF: SYNCSEC (MN)

OCN: AS-MT (NA)

TRUNK: SSM-ST3E (NA)

EXT-SREF: SYNCTHIRD (MN)

OCN: EOC (MN)

TRUNK: SSM-ST4 (NA)

FAN: EQPT-MISS (CR)

OCN: EOC-L (MN)

TRUNK: SSM-STU (NA)

FAN: FAN (CR)

OCN: FAILTOSW (NA)

TRUNK: SSM-TNC (NA)

FAN: MEA (CR)

OCN: FORCED-REQ-SPAN (NA)

TRUNK: SYNC-FREQ (NA)

FAN: MFGMEM (CR)

OCN: HI-LASERBIAS (MN)

TRUNK: SYNCLOSS (MJ)

FC: ALS (NA)

OCN: HI-LASERTEMP (MN)

TRUNK: TIM (CR)

FC: AS-CMD (NA)

OCN: HI-RXPOWER (MN)

TRUNK: TIM-MON (MN)

FC: AS-MT (NA)

OCN: HI-TXPOWER (MN)

TRUNK: TRAIL-SIGNAL-FAIL (NA)

FC: CARLOSS (MJ)

OCN: LO-LASERBIAS (MN)

TRUNK: UNC-WORD (NA)

FC: FAILTOSW (NA)

OCN: LO-LASERTEMP (MN)

TRUNK: UT-COMM-FAIL (MJ)

FC: FC-NO-CREDITS (MJ)

OCN: LO-RXPOWER (MN)

TRUNK: UT-FAIL (MJ)

FC: FORCED-REQ-SPAN (NA)

OCN: LO-TXPOWER (MN)

TRUNK: WTR (NA)

FC: GE-OOSYNC (CR)

OCN: MANUAL-REQ-SPAN (NA)

TRUNK: WVL-MISMATCH (MJ)

2.3  Trouble Characterizations

The ONS DWDM system reports trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253-CORE, and graphical user interface (GUI) state indicators.These notifications are described in the following paragraphs.

The ONS System uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and status or descriptive notifications (if configured to do so) as conditions in the CTC Alarms window. Alarms typically signify a problem that the user needs to remedy, such as a loss of signal. Conditions do not necessarily require troubleshooting.

Note Unless otherwise specified in this chapter, "ONS 15454" refers to both ANSI and ETSI versions of the platform.

Note For a description of CTC-view terminology, refer to the "Cisco Transport Controller Operation" chapter in the Cisco ONS 15454 DWDM Reference Manual.

2.3.1  Alarm Characteristics

The ONS DWDM system uses standard alarm entities to identify what is causing trouble. All alarms stem from hardware, software, environment, or operator-originated problems whether or not they affect service. Current alarms for the network, CTC session, node, or card are listed in the Alarms tab. (In addition, cleared alarms are also found in the History tab.)

2.3.2  Condition Characteristics

Conditions include any problem detected on an ONS DWDM shelf. They can include standing or transient notifications. A snapshot of all current raised, standing conditions on the network, node, or card can be retrieved in the CTC Conditions window or using TL1's set of RTRV-COND commands. (In addition, some but not all cleared conditions are also found in the History tab.)

For a comprehensive list of all conditions, refer to the Cisco SONET TL1 Command Guide. For information about transients, see Chapter 3, "Transient Conditions."

Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. You can retrieve alarms and events on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab.

2.3.3  Severity

The ONS DWDM system uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are described below:

•A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs immediate correction. Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.

•A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, loss of traffic on more than five DS-1 circuits is Critical (CR), but loss of traffic on one to four DS-1 circuits is Major (MJ).

•Minor (MN) alarms generally are those that do not affect service. For example, the automatic protection switching (APS) byte failure (APSB) alarm indicates that line terminating equipment (LTE) detects a byte failure on the signal that could prevent traffic from properly executing a traffic switch.

•Not Alarmed (NA) conditions are information indicators, such as for free-run synchronization state (FRNGSYNC) or a forced-switch to primary (FRCSWTOPRI) timing event. They could or could not require troubleshooting, as indicated in the entries.

•Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be expected in the presence of primary alarms.

Severities can be customized for an entire network or for single nodes, from the network level down to the port level by changing or downloading customized alarm profiles. These custom severities are subject to the standard severity-demoting rules given in Telcordia GR-474-CORE. Procedures for customizing alarm severities are located in the "Manage Alarms" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

2.3.4  Service Effect

Service-Affecting (SA) alarms—those that interrupt service—could be Critical (CR), Major (MJ), or Minor (MN) severity alarms. Service-Affecting (SA) alarms indicate service is affected. Non-Service-Affecting (NSA) alarms always have a Minor (MN) default severity.

2.3.5  State

The Alarms or History tab State (ST) column indicate the disposition of the alarm or condition as follows:

•A raised (R) event is one that is active.

•A cleared (C) event is one that is no longer active.

•A transient (T) event is one that is automatically raised and cleared in CTC during system changes such as user login, logout, loss of connection to node/shelf view, etc. Transient events do not require user action. These are listed in Chapter 3, "Transient Conditions."

2.4  Safety Summary

This section covers safety considerations designed to ensure safe operation of the ONS DWDM system. Personnel should not perform any procedures in this chapter unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances users should pay close attention to the following caution.

Caution Hazardous voltage or energy could be present on the backplane when the system is operating. Use caution when removing or installing cards.

Some troubleshooting procedures require installation or removal of OC-192 cards; in these instances users should pay close attention to the following warnings.

Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Warning Class 1 laser product. Statement 1008

Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206

Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207

2.5  Trouble-Clearing Procedures

This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.

Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner of the GUI is not indented. If it is, click it to turn it off. When you are done checking for alarms, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Note When checking alarms, ensure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab.

2.5.1  AIS

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)

Logical Objects: BITS, TRUNK

The Alarm Indication Signal (AIS) condition indicates that this node is detecting an alarm indication signal in the incoming signal SONET overhead.

Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

Clear the AIS Condition

Step 1 Determine whether there are alarms such as LOS on the upstream nodes and equipment or if there are OOS,MT (or Locked,maintenance), or OOS,DSBLD (or Locked,disabled) ports.

Step 2 Clear the upstream alarms using the applicable procedures in this chapter.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.2  AIS-L

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)

logical Objects: OCN, TRUNK

The AIS Line condition indicates that this node is detecting line-level AIS in the incoming signal. This alarm is secondary to another alarm occurring simultaneously in an upstream node.

This condition can also be raised in conjunction with the "TIM-S" alarm if AIS-L is enabled. (For more information about the TIM-S alarm, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 Troubleshooting Guide.

Note ONS 15454 DS-3 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback.

Clear the AIS-L Condition

Step 1 Complete the "Clear the AIS Condition" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.3  ALS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCN, TRUNK

The Automatic Laser Shutdown (ALS) condition occurs when an amplifier card (OPT-BST or OPT-PRE) is switched on. The turn-on process lasts approximately nine seconds, and the condition clears after approximately 10 seconds.

Note ALS is an informational condition and does not require troubleshooting.

2.5.4  ALS-DISABLED

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: EQPT

The Automatic Laser Shutdown (ALS) condition occurs when a DWDM Optical Preamplifier (OPT-PRE) or Optical Booster (OPT-BST) Amplifier card's ALS is changed to Disabled from any other state (such as Enabled) by user command.

Clear the ALS-DISABLED Condition

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the OPT-BST or OPT-PRE card to display the card view.

Step 2 Click the Maintenance > ALS tabs.

Step 3 In the ALS Mode column, change the entry from Disabled to your required state.

Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.5  AMPLI-INIT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition typically accompanies the "APC-DISABLED" alarm on page 2-23.

Note For basic information about amplifier cards, refer to the "Card Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual. For information abut gain, refer to the "Network Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the AMPLI-INIT Condition

Step 1 Complete the "Delete a Circuit" procedure on the most recently created circuit.

Step 2 Recreate this circuit using the procedures in the "Create Channels and Circuits" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).

2.5.6  APC-CORRECTION-SKIPPED

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: AOTS, OCH, OMS, OTS

The Automatic Power Control (APC) Correction Skipped condition occurs when the actual power level of a DWDM channel exceeds the expected setting by 3 dBm or more. APC compares actual power levels with previous power levels every hour or after any channel allocation is performed. If the power difference to be compensated by APC exceeds the range of + 3 dBm or -3 dBm compared with the previous value set, APC is designed not to correct the level and the APC-CORRECTION-SKIPPED condition is raised.

There is no operator action to resolve this condition. It stays raised until the power level problem is resolved and APC obtains a normal reading. For more information about APC, refer to the "Network Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual, and the "1.12.2  System Restart after a Fiber Cut" section on page 1-69.

2.5.7  APC-DISABLED

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE

The APC Disabled condition occurs when the information related to the number of DWDM channels is not reliable. The condition can occur when any of the following related alarms also occur: the "AMPLI-INIT" condition on page 2-22, the "EQPT" alarm on page 2-45, the "IMPROPRMVL" alarm on page 2-66, or the "MEA (EQPT)" alarm on page 2-102. If the condition occurs with the creation of the first circuit, delete and recreate the circuit. (Refer to the "Create Channels and Circuits" chapter of the Cisco ONS 15454 DWDM Procedure Guide for information about this.) For more information about APC, refer to the "Network Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Clear the APC-DISABLED Condition

Step 1 Complete the appropriate procedure to clear the main alarm:

•Clear the EQPT Alarm

•Clear the IMPROPRMVL Alarm

•Clear the MEA (EQPT) Alarm

Step 2 If the condition does not clear, complete the "Delete a Circuit" procedure and then recreate it using procedures in the "Create Channels and Circuits" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.8  APC-END

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE

The APC Terminated on Manual Request condition is raised when APC terminates after it is manually launched from CTC or TL1. APC-END is an informational condition that is raised and cleared spontaneously by the system and is not visible in the CTC Condition window. It is visible only by retrieving it in the Conditions or History tabs. For more information about APC, refer to the "Network Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Note APC-END is an informational condition and does not require troubleshooting.

2.5.9  APC-OUT-OF-RANGE

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: AOTS, OCH, OMS, OTS

The APC Out of Range condition is raised on amplifier cards (OPT-PRE and OPT-BST); demultiplexer cards (32DMX) having a single variable optical attenuator (VOA); and optical add/drop multiplexer cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x) when the requested gain or attenuation setpoint cannot be set because it exceeds the port parameter range. For example, this condition is raised when APC attempts to set the OPT-BST gain higher than 20 dBm (the card's maximum setpoint) or to set the attenuation on the express VOA lower than 0 dBm (its minimum setpoint).

Note For general information about DWDM cards, refer to the "Card Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual. For more information about APC, refer to the "Network Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the APC-OUT-OF-RANGE Condition

Step 1 There are various root causes for the APC-OUT-OF-RANGE condition. To determine the correct root cause, complete the network-level troubleshooting procedures and node-level problems located in 1.13  Node Level (Intranode) Problems of Chapter 1, "General Troubleshooting."

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.10  AS-CMD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, AOTS, BPLANE, EQPT, ESCON, FC, GE, ISC, NE, OCH, OCN/STMN, OMS, OTS, PPM, PWR, SHELF, TRUNK

The Alarms Suppressed by User Command condition applies to the network element (NE object), backplane (BPLANE object), a single MXP or TXP card, or a port on one of these cards. It occurs when alarms are suppressed for that object and its subordinate objects. For example, suppressing alarms on a card also suppresses alarms on its ports.

Note For more information about suppressing alarms, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Note This condition is not raised for multiservice transport platform (MSTP) cards such as amplifiers, multiplexers, or demultiplexers.

Clear the AS-CMD Condition

Step 1 For all nodes, in node view (single-shelf mode) or shelf view (multishelf mode), click the Conditions tab.

Step 2 Click Retrieve. If you have already retrieved conditions, look under the Object column and Eqpt Type column and note what entity the condition is reported against, such as a port, slot, or shelf.

•If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with Step 3.

•If the condition is reported against the backplane, go to Step 7.

•If the condition is reported against the NE object, go to Step 8.

Step 3 Determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:

a. Double-click the card to open the card view.

b. Click the Provisioning > Alarm Profiles > Alarm Behavior tabs and complete one of the following substeps:

•If the Suppress Alarms column check box is checked for a port row, deselect it and click Apply.

•If the Suppress Alarms column check box is not checked for a port row, from the View menu choose Go to Previous View.

Step 4 If the AS-CMD condition is reported for a card and not an individual port, in node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

Step 5 Locate the row number for the reported card slot.

Step 6 Click the Suppress Alarms column check box to deselect the option for the card row.

Step 7 If the condition is reported for the backplane, the alarms are suppressed for cards such as the ONS 15454 AIP that are not in the optical or electrical slots. To clear the alarm, complete the following steps:

a. Click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

b. In the backplane row, uncheck the Suppress Alarms column check box.

c. Click Apply.

Step 8 If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm, complete the following steps:

a. In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Alarm Profiles > Alarm Behavior tabs if you have not already done so.

b. Click the Suppress Alarms check box located at the bottom of the window to deselect the option.

c. Click Apply.

Step 9 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.11  AS-MT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, AOTS, EQPT, ESCON, FC, GE, ISC, OCH, OCN/STMN, OMS, OTS, PPM, SHELF, TRUNK

The Alarms Suppressed for Maintenance Command condition applies to MXP or TXP cards and occurs when a client or trunk port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT or Locked,enabled, loopback & maintenance) service state for loopback testing operations.

Clear the AS-MT Condition

Step 1 Complete the "Clear an MXP or TXP Card Loopback Circuit" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.12  AUTORESET

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: EQPT

The Automatic System Reset alarm occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.

AUTORESET typically clears after a card reboots (up to ten minutes). If the alarm does not clear, complete the following procedure.

Clear the AUTORESET Alarm

Step 1 Determine whether there are additional alarms that could have triggered an automatic reset. If there are, troubleshoot these alarms using the applicable section of this chapter.

Step 2 If the card automatically resets more than once a month with no apparent cause, complete the "Physically Replace a Card" procedure.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.13  AWG-DEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: OTS

The Arrayed Waveguide Gratings (AWG) Degrade alarm occurs when a 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card heater-control circuit degrades. The heat variance can cause slight wavelength drift. The card does not need to be replaced immediately, but it should be at the next opportunity.

Note For General information about 32MUX-O, 32WSS-O, 32DMX-O and 32DMX cards, refer to the "Card Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual. For more information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the AWG-DEG Alarm

Step 1 For the alarmed 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card, complete the "Physically Replace a Card" procedure at the next opportunity.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.14  AWG-FAIL

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: OTS

The AWG Failure alarm occurs when a 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card heater-control circuit completely fails. The circuit failure disables wavelength transmission. The card must be replaced to restore traffic.

Note For general information about 32MUX-O, 32WSS-O, 32DMX-O and 32DMX cards, refer to the "Card Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the AWG-FAIL Alarm

Step 1 For the alarmed 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card, complete the "Physically Replace a Card" procedure.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.5.15  AWG-OVERTEMP

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: OTS

The AWG Over Temperature alarm is raised if a 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card having an AWG-FAIL alarm is not replaced and its heater-control circuit temperature exceeds 212 degrees F (100 degrees C). The card goes into protect mode and the heater is disabled.

Note For general information about these cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the AWG-OVERTEMP Alarm

Step 1 Complete the "Clear the AWG-FAIL Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.5.16  AWG-WARM-UP

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: OTS

The AWG Warm-Up condition occurs when a 32MUX-O, 32WSS-O, 32DMX-O, or 32DMX card heater-control circuit is attaining its operating temperature during startup. The condition lasts approximately 10 minutes but can vary somewhat from this period due to environmental temperature.

Note AWG-WARM-UP is an informational condition and does not require troubleshooting.

2.5.17  BAT-FAIL

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: PWR

The Battery Fail alarm occurs when one of the two power supplies (A or B) is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so onsite information about the conditions is necessary for troubleshooting.

Clear the BAT-FAIL Alarm

Step 1 At the site, determine which battery is not present or operational.

Step 2 Remove the power cable from the faulty supply. For procedures, refer to the "Install the Shelf and Common Control Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide. Reverse the power cable installation procedure.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.18  BKUPMEMP

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: EQPT

The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P card flash memory. The alarm occurs when the TCC2/TCC2P card is in use and has one of four problems:

•Flash manager fails to format a flash partition.

•Flash manager fails to write a file to a flash partition.

•Problem at the driver level.

•Code volume fails cyclic redundancy checking (CRC, which is a method to verify for errors in data transmitted to the TCC2/TCC2P card).

The BKUPMEMP alarm can also cause the "EQPT" alarm, page 2-45. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.

Caution A software update on a standby TCC2/TCC2P card can take up to 30 minutes.

Clear the BKUPMEMP Alarm

Step 1 Verify that both TCC2/TCC2P cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2/TCC2P cards.

Step 2 Determine whether the active or standby TCC2/TCC2P card has the alarm.

Step 3 If both TCC2/TCC2P cards are powered and enabled, reset the TCC2/TCC2P card where the alarm is raised. If the card is the active TCC2/TCC2P card, complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure. If the card is the standby TCC2/TCC2P card:

a. Right-click the standby TCC2/TCC2P card in CTC.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the Are You Sure dialog box. The card resets, the FAIL LED blinks on the physical card.

d. Wait ten minutes to verify that the card you reset completely reboots.

Step 4 If the TCC2/TCC2P card you reset does not reboot successfully, or the alarm has not cleared, call Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

2.5.19  BPV

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: BITS

The 64K Clock Bipolar Density Violation alarm is raised on the TCC2P card if there is a frequency variation in the 8K BITS clock.

The TCC2P card contains an 8K clock and a 64K clock. Each has some bipolar variation, which is normal. This alarm is raised on the 8K clock if that variation discontinues. The BPV alarm is demoted by an LOF or LOS against the BITS clock.

Note This alarm is not raised on the TCC2 card.

Clear the BPV Alarm

Step 1 Reestablish a normal BITS input signal to clear the alarm. Clear any alarms on the incoming signal or against the BITS timing sources.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.20  CARLOSS (EQPT)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: EQPT

A Carrier Loss on the LAN Equipment alarm generally occurs on MXP or TXP cards when the ONS system and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the TCC2/TCC2P card or the LAN backplane pin connection. This CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the node.

On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, and MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 encapsulation is turned off.

A TXP_MR_2.5G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data types.

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Note For more information about provisioning MXP or TXP PPMs (also called SFPs), refer to the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For PPM (SFP) specifications, refer to the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual. For more information about MRC-12 and OC192-XFP/STM64-XFP cards, refer to the "Optical Cards" chapter in the Cisco ONS 15454 Reference Manual.

Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.

Clear the CARLOSS (EQPT) Alarm

Step 1 If the reporting card is an MXP or TXP card in an ONS 15454 node, verify the data rate configured on the PPM (also called SFP):

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the reporting MXP or TXP card.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment Type column and compare this with the contents of the Selected PPM area Rate column for the MXP or TXP multirate port.

d. If the rate does not match the actual equipment, you must delete and recreate the selected PPM. Select the PPM (SFP), click Delete, then click Create and choose the correct rate for the port rate.

Note For more information about provisioning PPMs (SFPs), refer to the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For PPM (SFP) specifications, refer to the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual.

Step 2 If the reporting card is an OC-N/STM-N card, verify connectivity by pinging the ONS system that is reporting the alarm by completing the "1.6.8  Verify PC Connection to the ONS 15454 (ping)" procedure on page 1-40.

Step 3 If the ping is successful, it demonstrates that an active TCP/IP connection exists. Restart CTC:

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

Step 4 Using optical test equipment, verify that proper receive levels are achieved. (For instructions about using optical test equipment, refer to the manufacturer documentation.)

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.

Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 6 If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N/STM-N card.

Step 7 If you are unable to establish connectivity, replace the fiber cable with a new known-good cable. To do this, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 8 If you are unable to establish connectivity, perform standard network or LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node and CTC. To verify cable continuity, follow site practices.

Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.21  CARLOSS (FC)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: FC

The Carrier Loss for Fibre Channel (FC) alarm occurs on the client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, supporting 1-Gb Fibre Channel (FC1G), 2-Gb FC (FC2G), or 10Gb Fiber Channel (10G Fiber Channel) traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the CARLOSS (FC) Alarm

Step 1 Complete the "Clear the CARLOSS (GE) Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.22  CARLOSS (GE)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: GE

The Carrier Loss for Gigabit Ethernet (GE) alarm occurs on the client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L supporting 1-Gbps or 10-Gbps traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the CARLOSS (GE) Alarm

Step 1 Ensure that the GE client is correctly configured:

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card to open the card view.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment Type column and compare this with the client equipment. If no PPM (SFP) is provisioned, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide. PPM (SFP) specifications are listed in the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual.

d. If a PPM (SFP) has been created, view the contents of the Selected PPM area Rate column for the MXP or TXP MR card and compare this rate with the client equipment data rate. In this case, the rate should be ONE_GE or 10G Ethernet. If the PPM (SFP) rate is differently provisioned, select the PPM (SFP), click Delete, then click Create and choose the correct rate for the equipment type.

Note For information about installing provisioning PPMs (SFPs), refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 2 If there is no PPM (SFP) misprovisioning, check for a fiber cut. An LOS alarm would also be present. If there is an alarm, complete the "Clear the LOS (OCN/STMN) Alarm" procedure located in Chapter 2, "Alarm Troubleshooting," of the Cisco ONS 15454 Troubleshooting Guide or Cisco ONS 15454SDH Troubleshooting Guide.

Step 3 If there is no fiber cut or provisioning error, check the client-side equipment for any transmission errors on the line.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.23  CARLOSS (ISC)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: ISC

The Carrier Loss for Inter-Service Channel (ISC) alarm occurs on the client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, and MXPP_MR_2.5G supporting ISC traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the CARLOSS (ISC) Alarm

Step 1 Complete the "Clear the CARLOSS (GE) Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.24  CARLOSS (TRUNK)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: TRUNK

A Carrier Loss alarm is raised on the optical Trunk-RX port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, and MXPP_MR_2.5G when the Ethernet payload is lost. This alarm only occurs when ITU-T G.709 encapsulation is disabled.

Note For general information about TXP cards and their monitoring capabilities, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the CARLOSS (TRUNK) Alarm

Step 1 Check for any upstream equipment failures:

•Verify that the far-end TXP or MXP is generating the signal to be received by the alarmed card.

•Verify that the Trunk-Tx port is not reporting any performance monitoring (PM) problems.

•Verify that the Client-Rx port is not reporting any PM problems that could cause the CARLOSS in this card.

Note For more information about performance monitoring, refer to the "Performance Monitoring" chapter of the Cisco ONS 15454 DWDM Reference Manual.

Step 2 If there is no cause upstream, verify cabling continuity from the transmitting port of the DWDM card (AD-xC-xx.x-xx.x, 32DMX-O, or 32DMX) connected to the TXP receiving port reporting this alarm.

Step 3 If a patch panel is used, ensure that the LC-LC adapter managing the connection is in good working order.

Step 4 If the continuity is good, clean the fiber according to site practice. If none exists, complete the fiber cleaning procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 5 If the signal is valid, ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected (that is, the correct wavelength is coming from the patch panel). For more information about fiber connections and terminations, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 6 If the correct port is in service but the alarm has not cleared, use an optical test set to confirm that a valid signal exists on the input port of the alarmed TXP. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

Step 7 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting card.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.25  CASETEMP-DEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Case Temperature Degrade alarm is raised when a DWDM card temperature sensor detects an out-of-range external temperature at the shelf level. The working range for DWDM cards is from 23 degrees F (-5 degrees C) to 149 degrees F (65 degrees C).

Note For specific temperature and environmental information about each DWDM card, refer to the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual.

Clear the CASETEMP-DEG Alarm

Step 1 Determine whether the air filter needs replacement. Complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Step 2 If the filter is clean, complete the "Remove and Reinsert a Fan-Tray Assembly" procedure.

Step 3 If the fan does not run or the alarm persists, complete the "Replace the Fan-Tray Assembly" procedure. The fan should run immediately when correctly inserted.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.26  DATAFLT

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: NE

The Software Data Integrity Fault alarm occurs when the TCC2/TCC2P card exceeds its flash memory capacity.

Caution When the system reboots, the last configuration entered is not saved.

Clear the DATAFLT Alarm

Step 1 Complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.27  DBOSYNC

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: NE

The Standby Database Out Of Synchronization alarm occurs when the standby TCC2/TCC2P card database does not synchronize with the active database on the active TCC2/TCC2P card.

Caution If you reset the active TCC2/TCC2P card while this alarm is raised, you lose current provisioning.

Clear the DBOSYNC Alarm

Step 1 Save a backup copy of the active TCC2/TCC2P card database. Refer to the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide or the Cisco ONS 15454 SDH Procedure Guide as appropriate for your purpose.

Step 2 Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm:

a. In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > General > General tabs.

b. In the Description field, make a small change such as adding a period to the existing entry.

The change causes a database write but does not affect the node state. The write could take up to a minute.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.28  DISCONNECTED

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: SYSTEM

The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm is cleared when CTC is reconnected to the node.

Clear the DISCONNECTED Alarm

Step 1 Restart the CTC application.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).

2.5.29  DSP-COMM-FAIL

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: TRUNK

The Digital Signal Processor (DSP) Communication Failure alarm indicates that there is a communication failure between an MXP or TXP card microprocessor and the on-board DSP chip that controls the trunk (or DWDM) port. This alarm typically occurs after a DSP code upgrade.

The alarm is temporary and does not require user action. The MXP or TXP card microprocessor attempts to restore communication with the DSP chip until the alarm is cleared. (For general information about MXP and TXP cards, refer to the "Card Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual.)

If the alarm is raised for an extended period, the MXP or TXP card raises the "DUP-IPADDR" alarm on page 2-39 and could affect traffic.

Note DSP-COMM-FAIL is an informational alarm and does not require troubleshooting.

2.5.30  DSP-FAIL

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: TRUNK

The DSP Failure alarm indicates that a "DSP-COMM-FAIL" alarm, page 2-38, has persisted for an extended period on an MXP or TXP card. It indicates that the card is faulty.

Clear the DSP-FAIL Alarm

Step 1 Complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.

2.5.31  DUP-IPADDR

Default Severity: Minor (MN), Non-Service Affecting (NSA)

Logical Object: NE

The Duplicate IP Address alarm indicates that the alarmed node IP address is already in use within the same data communications channel (DCC) area. When this happens, CTC no longer reliably connects to either node. Depending on how the packets are routed, CTC could connect to either node (having the same IP address). If CTC has connected to both nodes before they shared the same address, it has two distinct NodeModel instances (keyed by the node ID portion of the MAC address).

Clear the DUP-IPADDR Alarm

Step 1 Isolate the alarmed node from the other node having the same address:

a. Connect to the alarmed node using the Craft port on the TCC2/TCC2P card.

b. Begin a CTC session.

c. In the login dialog box, uncheck the Network Discovery check box.

Step 2 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network > General tabs.

Step 3 In the IP Address field, change the IP address to a unique number.

Step 4 Click Apply.

Step 5 Restart any CTC sessions that are logged into either of the duplicate IP addresses. (For procedures to log in or log out, refer to the "Connect the PC and Log Into the GUI" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.32  DUP-NODENAME

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: NE

The Duplicate Node Name alarm indicates that the alarmed node alphanumeric name is already being used within the same DCC area.

Clear the DUP-NODENAME Alarm

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > General > General tabs.

Step 2 In the Node Name field, enter a unique name for the node.

Step 3 Click Apply.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.33  DUP-SHELF-ID

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: SHELF

The Duplicated Shelf Identifier alarm applies to a shelf that has multishelf management enabled when the TCC2/TCC2P detects that you have programmed an ID already in use by another shelf. For more information about provisioning an NC shelf or SS shelf for multishelf configurations, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide and "Node Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Clear the DUP-SHELF-ID Alarm

Step 1 Unprovision the shelf ID of the duplicate shelf by completing the following steps:

a. In shelf view (multishelf mode) or multishelf view (multishelf mode), click the node controller Provisioning > General > Multishelf Config tabs.

b. Enter a new value in the Shelf ID field.

c. Click Apply.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.34  EHIBATVG

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: PWR

The Extreme High Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage exceeds the extreme high power threshold. This threshold, with a default value of -56.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.)

Clear the EHIBATVG Alarm

Step 1 The problem is external to the ONS system. Troubleshoot the power source supplying the battery leads.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.35  ELWBATVG

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: PWR

The Extreme Low Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage falls below the extreme low power threshold. This threshold, with a default value of -40.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains over the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the ELWBATVG Alarm

Step 1 The problem is external to the ONS system. Troubleshoot the power source supplying the battery leads.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.36  EOC

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: OCN/STMN, TRUNK

The SONET DCC Termination Failure alarm occurs when the ONS system loses its DCC. Although this alarm is primarily SONET, it can apply to DWDM. For example, the OSCM card can raise this alarm on its OC-3 section overhead.

The SDCC consists of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS system uses the DCC on the SONET section layer to communicate network management information.

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Note If a circuit shows a partial state when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.

Note For general information about OSCM or other DWDM cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide. For more information about the SONET (ANSI) or SDH (ETSI) overhead, refer to the "SONET Topologies and Upgrades" chapter of the Cisco ONS 15454 Procedure Guide or the "SDH Topologies and Upgrades" chapter of the Cisco ONS 15454 SDH Procedure Guide.

Note The EOC alarm is raised on the DWDM trunk in MSTP systems. Its SDH (ETSI) counterpart, MS-EOC, is not raised against the trunk port.

Clear the EOC Alarm

Step 1 If the LOS (DS1) alarm or SF-L alarm is reported, complete the appropriate troubleshooting procedure in the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 Troubleshooting Guide.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.

Step 2 If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry SDCC traffic. For more information about fiber connections and terminations, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 If the physical connections are correct and configured to carry DCC traffic, ensure that both ends of the fiber span have in-service (IS or Unlocked) ports. Verify that the ACT/SBY LED on each card is green.

Step 4 When the LEDs on the cards are correctly illuminated, complete the "Verify or Create Node Section DCC Terminations" procedure to verify that the DCC is provisioned for the ports at both ends of the fiber span.

Step 5 Repeat Step 4 at the adjacent nodes.

Step 6 If DCC is provisioned for the ends of the span, verify that the port is active and in service by completing the following steps:

a. Confirm that the card shows a green LED in CTC or on the physical card. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

b. To determine whether the port is in service, in node view (single-shelf mode) or shelf view (multishelf mode), double-click the card in CTC to open the card view.

c. In card view, click the Provisioning > Line tabs.

d. Verify that the Admin State column lists the port as IS (or Unlocked).

e. If the Admin State column lists the port as OOS,MT (or Locked,maintenance) or OOS,DSBLD (or Locked,disabled), click the column and choose IS , or Unlocked. Click Apply.

Step 7 For all nodes, if the card is in service, use an optical test set to determine whether signal failures are present on fiber terminations. For specific procedures to use the test set equipment, consult the manufacturer.

Caution Using an optical test set disrupts service on a card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 8 If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. Refer to the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual for card power levels.

Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information about cabling, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure.

Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

Resetting the active TCC2/TCC2P card switches control to the standby TCC2/TCC2P card. If the alarm clears when the ONS system node switches to the standby TCC2/TCC2P card, the user can assume that the previously active card is the cause of the alarm.

Step 11 If the TCC2/TCC2P card reset does not clear the alarm, delete the problematic SDCC termination:

a. From the View menu in card view, choose Go to Previous View if you have not already done so.

b. In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Comm Channels > SDCC tabs.

c. Highlight the problematic DCC termination.

d. Click Delete.

e. Click Yes in the Confirmation Dialog box.

Step 12 Recreate the SDCC termination. Refer to the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide for procedures.

Step 13 Verify that both ends of the DCC have been recreated at the optical ports.

Step 14 If the alarm has not cleared, call Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

2.5.37  EOC-L

Default Severity: Minor (MN), Non-Service-Affecting (NSA) for OCN/STMN

Logical Object: TRUNK

The Line DCC (LDCC) Termination Failure alarm occurs when the ONS system loses its line data communications channel (LDCC) termination. For example, the OSCM card can raise this alarm on its OC-3 line overhead.

The LDCC consists of nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS system uses the LDCCs on the SONET line layer to communicate network management information.

Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Note If a circuit shows a partial status when the EOC or EOC-L alarm is raised, it occurs when the logical circuit is in place. The circuit is able to carry traffic when the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.

Note For general information about OSCM or other DWDM cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide. For more information about the SONET (ANSI) or SDH (ETSI) overhead, refer to the "SONET Topologies and Upgrades" chapter of the Cisco ONS 15454 Procedure Guide or the "SDH Topologies and Upgrades" chapter of the Cisco ONS 15454 SDH Procedure Guide.

Clear the EOC-L Alarm

Step 1 Complete the "Clear the EOC Alarm" procedure.

Step 2 If the alarm has not cleared, call Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

2.5.38  EQPT

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: AICI-AEP, AICI-AIE, EQPT, PPM

An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card. If the EQPT alarm occurs with a "BKUPMEMP" alarm, page 2-29, refer to the procedure to clear the alarm. (Clearing a BKUPMEMP alarm also clears an EQPT alarm.)

This alarm is also invoked if a diagnostic circuit detects a card application-specific integrated circuit (ASIC) failure. In this case, if the card is part of a protection group, an APS switch occurs. If the card is the protect card, switching is inhibited and a "PROTNA" alarm, page 2-133, is raised. The standby path generates a path-type alarm. For more information about provisioning PPMs (SFPs), refer to the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Clear the EQPT Alarm

Step 1 If traffic is active on the alarmed port, you could need to switch traffic away from it. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

Step 2 Complete the "Reset a Card in CTC" procedure for the reporting card.

Step 3 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the LED status. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

Step 4 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting card.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 5 If the physical reseat of the card fails to clear the alarm, complete the "Physically Replace a Card" procedure for the reporting card.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.39  EQPT-MISS

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: FAN

The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or is not fully inserted. It could also indicate that the ribbon cable connecting the AIP to the system board is bad.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.

Clear the EQPT-MISS Alarm

Step 1 If the alarm is reported against the fan, verify that the fan-tray assembly is present.

Step 2 If the fan-tray assembly is present, complete the "Replace the Fan-Tray Assembly" procedure.

Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the "Install the Fan-Tray Assembly," procedure in the "Install the Shelf and Common Control Cards" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Step 4 If the alarm does not clear, replace the ribbon cable from the AIP to the system board with a known-good ribbon cable.

Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.40  EXCCOL

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: EQPT

The Excess Collisions on the LAN alarm indicates that too many collisions are occurring between data packets on the network management LAN, and communications between the ONS system and CTC could be affected. The network management LAN is the data network connecting the workstation running the CTC software to the TCC2/TCC2P card. The problem causing the alarm is external to the ONS system.

Troubleshoot the network management LAN connected to the TCC2/TCC2P card for excess collisions. You might need to contact the system administrator of the network management LAN to accomplish the following steps.

Clear the EXCCOL Alarm

Step 1 Verify that the network device port connected to the TCC2/TCC2P card has a flow rate set to 10 Mb, half-duplex.

Step 2 If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the TCC2/TCC2P card and the network management LAN.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.41  EXT

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: ENVALRM

A Failure Detected External to the NE alarm occurs because an environmental alarm is present. For example, a door could be open or flooding could have occurred.

Clear the EXT Alarm

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the AIC-I card to open the card view.

Step 2 Double-click the Maintenance > External Alarms tabs.

Step 3 Follow your standard operating procedure to remedy environmental conditions that cause alarms. The alarm clears when the situation is remedied.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.42  FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK

The Failure to Switch to Protection Facility condition for MXP and TXP client ports occurs in a Y-cable protection group when a working or protect facility switches to its companion port by using a MANUAL command. For example, if you attempt to manually switch traffic from an unused protect port to an in-service working port, the switch will fail (because traffic is already present on the working port) and you will see the FAILTOSW condition.

Note For more information about protection schemes, refer to the "Manage the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Clear the FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN) Condition

Step 1 Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the card and clears the FAILTOSW.

Step 2 If the condition does not clear, replace the working card that is reporting the higher-priority alarm by following the "Physically Replace a Card" procedure. This card is the working facility using the protect facility and not reporting FAILTOSW.

Replacing the working card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.43  FAILTOSW (TRUNK)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: TRUNK

The Failure to Switch to Protection Facility condition applies to MXP and TXP trunk ports in splitter protection groups and occurs when a working or protect trunk port switches to its companion port by using a MANUAL command.

Note For more information about protection schemes, refer to the "Manage the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Clear the FAILTOSW (TRUNK) Condition

Step 1 Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the card and clears the FAILTOSW.

Step 2 If the condition does not clear, replace the working card that is reporting the higher-priority alarm by following the "Physically Replace a Card" procedure. This card is the working facility using the protect facility and not reporting FAILTOSW.

Replacing the working card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.44  FAN

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: FAN

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS system can rise above its normal operating range.

The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the shelf. However, even with five working fans, the fan-tray assembly could need replacement because a sixth working fan is required for extra protection against overheating.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.

Clear the FAN Alarm

Step 1 Determine whether the air filter needs replacement. Complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Step 2 If the filter is clean, complete the "Remove and Reinsert a Fan-Tray Assembly" procedure.

Step 3 If the fan does not run or the alarm persists, complete the "Replace the Fan-Tray Assembly" procedure. The fan should run immediately when correctly inserted.

Step 4 If the replacement fan-tray assembly does not operate correctly, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447).

2.5.45  FC-NO-CREDITS

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Objects: Client port

The Fibre Channel Distance Extension Credit Starvation alarm occurs on storage access networking (SAN) Fibre Channel/Fiber Connectivity (FICON) DWDM cards when the congestion prevents the GFP transmitter from sending frames to the DWDM card port. For example, the alarm can be raised when an operator configures a card to autodetect framing credits but the card is not connected to an interoperable FC-SW-standards-based Fibre Channel/FICON port.

FC-NO-CREDITS is raised only if transmission is completely prevented. (If traffic is slowed but still passing, this alarm is not raised.)

Clear the FC-NO-CREDITS Alarm

Step 1 If the port is connected to a Fibre Channel/FICON switch, make sure it is configured for interoperation mode using the manufacturer's instructions.

Step 2 If the port is not connected to a switch, turn off Autodetect Credits by completing the following steps:

a. Double-click the DWDM card.

b. Click the Provisioning > Port > General tabs.

c. Under Admin State, click the cell and choose OOS,MT (or Locked,maintenance).

d. Click Apply.

e. Click the Provisioning > Port > Distance Extension tabs.

f. Uncheck the Autodetect Credits column check box.

g. Click Apply.

h. Click the Provisioning > Port > General tabs.

i. Under Admin State, click the cell and choose IS , or Unlocked.

j. Click Apply.

Step 3 Program the Credits Available value based on the buffers available on the connected equipment by completing the following steps:

Note The NumCredits entry must be provisioned to a value smaller than or equal to the receive buffers or credits available on the connected equipment.

a. Double-click the DWDM card.

b. Click the Provisioning > Port > Distance Extension tabs.

c. Enter a new value in the Credits Available column.

d. Click Apply.

Step 4 If the replacement fan-tray assembly does not operate correctly, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447).

2.5.46  FDI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: OCH, OMS, OTS

The Forward Defect Indication (FDI) condition is part of MSTP network-level alarm correlation in R7.0. It is raised at the far end when the OCH optical payload is missing due to an optical channel signal (LOS), light (LOS-P), or optical power (OPWR-LFAIL) alarm root cause.

An LOS, LOS-P, or OPWR-LFAIL alarm on an MSTP circuit causes multiple alarms for each channel. Correlation simplifies troubleshooting by reporting a single alarm for multiple alarms having one root cause, then demoting the root alarms so that they are only visible in the Conditions window (showing their original severity.)

FDI clears when the optical channel is working on the aggregated or single-channel optical port.

Note Network-level alarm correlation is only supported for MSTP communication alarms. It is not supported for equipment alarms.

Clear the FDI Condition

Step 1 Clear the root-cause service-affecting alarm by using one of the following procedures, as appropriate:

•"Clear the LOS (OTS) Alarm" procedure

•"Clear the LOS (TRUNK) Alarm" procedure

•"Clear the LOS-P (OCH) Alarm" procedure

•"Clear the LOS-P (AOTS, OMS, OTS) Alarm" procedure

•"Clear the LOS-P (TRUNK) Alarm" procedure

•"Clear the OPWR-LFAIL Alarm" procedure

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.47  FEC-MISM

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: TRUNK

The Forward Error Correction (FEC) Mismatch alarm applies to all cards featuring FEC/E-FEC capability: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_10G, and MXP_MR_10E. FEC-MISMATCH is reported only on the card configured in Standard FEC mode or with FEC disabled. A card configured in enhanced FEC mode will report an "OTUK-LOF" alarm on page 2-122.

The alarm is related to ITU-T G.709 encapsulation and is only raised against a trunk port.

Note For general information about MXP and TXP cards and their monitoring capabilities, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the FEC-MISM Alarm

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_10G, and MXP_MR_10E card.

Step 2 Click the Provisioning > OTN > OTN Lines tabs.

Step 3 In the FEC column, click Enable to activate the FEC feature. This causes a different OTN frame to be transmitted. Alternately, in the E-FEC column (TXP_MR_10E and MXP_MR_10E), click Enable to activate the Enhanced FEC feature.

Step 4 Verify that the far-end card is configured the same way by repeating Step 1 through Step 3.

Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.48  FIBERTEMP-DEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Fiber Temperature Degrade alarm occurs when a DWDM card internal heater-control circuit fails. Degraded temperature can cause some signal drift. The card should be replaced at the next opportunity.

Note For general information about DWDM cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the FIBERTEMP-DEG Alarm

Step 1 For the alarmed card, complete the "Physically Replace a Card" procedure at the next opportunity.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.49  FORCED-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, ESCON, FC, GE, ISC, OCN/STMN

The Force Switch Request Span condition applies to Y-cable-protected TXP configurable clients (OC-3, OC-12/STM-4,OC-48/STM-16, OC-192/STM-64, FC, ESCON, or FICON). If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.

Note For more information about protection schemes, refer to the "Manage the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

2.5.50  FORCED-REQ-SPAN (TRUNK)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: TRUNK

The Force Switch Request Span condition applies to MXP and TXP trunk ports in splitter protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.

Note For more information about protection schemes, refer to the "Manage the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

2.5.51  FRCDSWTOINT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE-SREF

The Force Switch to Internal Timing condition occurs when the user issues a Force command to switch to an internal timing source.

Note FRCDSWTOINT is an informational condition and does not require troubleshooting.

2.5.52  FRCDSWTOPRI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Primary Timing Source condition occurs when the user issues a Force command to switch to the primary timing source.

Note FRCDSWTOPRI is an informational condition and does not require troubleshooting.

2.5.53  FRCDSWTOSEC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Second Timing Source condition occurs when the user issues a Force command to switch to the second timing source.

Note FRCDSWTOSEC is an informational condition and does not require troubleshooting.

2.5.54  FRCDSWTOTHIRD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Third Timing Source condition occurs when the user issues a Force command to switch to a third timing source.

Note FRCDSWTOTHIRD is an informational condition and does not require troubleshooting.

2.5.55  FRNGSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE-SREF

The Free Running Synchronization Mode condition occurs when the reporting ONS system is in free-run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the node has lost its designated building integrated timing supply (BITS) timing source. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS system node relying on an internal clock.

Note If the ONS system is configured to operate from its internal clock, disregard the FRNGSYNC condition.

Clear the FRNGSYNC Condition

Step 1 If the ONS system is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the "Timing" chapter in the Cisco ONS 15454 Reference Manual for more information.

Step 2 If the BITS source is valid, clear alarms related to the failures of the primary and secondary reference sources, such as the "SYNCPRI" alarm on page 2-152 and the "SYNCSEC" alarm on page 2-153.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.56  FSTSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE-SREF

A Fast Start Synchronization Mode condition occurs when the node is choosing a new timing reference. The previous timing reference has failed.

The FSTSYNC alarm disappears after approximately 30 seconds. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

Note FSTSYNC is an informational condition. It does not require troubleshooting.

2.5.57  GAIN-HDEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Gain High Degrade alarm is raised on an amplifier card (OPT-BST or OPT-PRE) when the amplifier reaches the Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 2 dBm higher than the setpoint. The card should be replaced at the first opportunity.

Note This alarm is applicable only when the amplifier working mode is set to Control Gain.

Note For general information about DWDM amplifier cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about control gain, refer to the "Node Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GAIN-HDEG Alarm

Step 1 Verify that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 2 Complete "Reset a Card in CTC" procedure on the failing amplifier.

Step 3 If the alarm does not clear, identify all the OCHNC circuits applying to the failing card. Force all the protected circuits on the optical path that the faulty amplifier does not belong to. Switch the OCHNC administrative state of all these circuits to OOS,DSBLD (or Locked,disabled).

Caution All remaining unprotected circuits will suffer for a traffic hit when you disable the circuits.

Step 4 Switch the administrative state of only one of the OCHNC circuits to IS,AINS (or Unlocked,automaticInService. This forces the amplifier to recalculate its gain setpoint and value.

Step 5 If the alarm does not clear and no other alarms exist that could be the source of the GAIN-HDEG alarm, or if clearing an alarm did not clear the GAIN-HDEG, place all of the card ports in OOS,DSBLD (or Locked,disabled) administrative state.

Step 6 Complete the "Physically Replace a Card" procedure for the reporting card.

Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Note Before disconnecting any optical amplifier card fiber for troubleshooting, ensure that the optical amplifier card is unplugged.

Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.58  GAIN-HFAIL

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: AOTS

The Gain High Degrade alarm is raised on an amplifier card (OPT-BST or OPT-PRE) when the amplifier reaches the Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 5 dBm higher than the setpoint.) If the alarm cannot be cleared, the card must be replaced.

Note This alarm is applicable only when the amplifier working mode is set to Control Gain.

Note For general information about DWDM cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about control gain, refer to the "Node Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GAIN-HFAIL Alarm

Step 1 For the alarmed card, complete the "Clear the GAIN-HDEG Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.5.59  GAIN-LDEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Gain High Degrade alarm is raised on an amplifier card (OPT-BST or OPT-PRE) when the amplifier does not reach Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 2 dBm lower than the setpoint.) The card should be replaced at the first opportunity.

Note This alarm is applicable only when the amplifier working mode is set to Control Gain.

Note For general information about DWDM amplifier cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about control gain, refer to the "Node Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GAIN-LDEG Alarm

Step 1 For the alarmed card, complete the "Clear the GAIN-HDEG Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.60  GAIN-LFAIL

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: AOTS

The Gain High Degrade alarm is raised on an amplifier card (OPT-BST or OPT-PRE) when the amplifier does not reach Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 5 dBm lower than the setpoint. If the alarm cannot be cleared, the card must be replaced.

Note This alarm is applicable only when the amplifier working mode is set to Control Gain.

Note For general information about DWDM amplifier cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about control gain, refer to the "Node Reference" chapter in the same manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GAIN-LFAIL Alarm

Step 1 For the alarmed card, complete the "Clear the GAIN-HDEG Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.61  GCC-EOC

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: TRUNK

The GCC Embedded Operation Channel Failure alarm applies to the optical transport network (OTN) communication channel for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, and MXP_2.5G_10E cards. The GCC-EOC alarm is raised when the channel cannot operate.

This alarm applies to trunk ports only when ITU-T G.709 encapsulation is enabled and a general communication channel (GCC) has been provisioned between the two TXP/MXP cards.

Note For more information about GCC circuits, please refer to the "Create Channels and Circuits" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GCC-EOC Alarm

Step 1 Complete the "Clear the EOC Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.62  GE-OOSYNC (FC, GE, ISC)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: FC, GE, ISC

The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G,TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G,TXPP_MR_2.5G,MXP_MR_2.5G and MXPP_MR_2.5G cards when the Ethernet signal incoming on the Client-Rx port is out of synchronization.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GE-OOSYNC (FC, GE, ISC) Alarm

Step 1 Ensure that the incoming signal from the Client-Rx port is provisioned with the correct physical-layer protocol (Ethernet).

Step 2 Ensure that the line is provisioned with the correct line speed (10G or 1G Ethernet).

Step 3 Verify that the optical power and the optical signal-to-noise range (OSNR) of the incoming Client-Rx port optical signal are within the accepted ranges. You can find XFP/SFP ranges in the "Hardware Specifications" appendix of the Cisco ONS 15454 DWDM Reference Manual.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.63  GE-OOSYNC (TRUNK)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: TRUNK

The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G,TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G,TXPP_MR_2.5G,MXP_MR_2.5G and MXPP_MR_2.5G cards only when the ITU-T G.709 encapsulation framer is disabled.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the GE-OOSYNC (TRUNK) Alarm

Step 1 Verify that ITU-T G.709 encapsulation is disabled:

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card to display the card view.

b. Click the Provisioning > OTN > OTN Lines tabs.

c. If the G.709 OTN column says Enable, choose Disable from the drop-down list.

d. Click Apply.

Step 2 For the TRUNK-RX port, double-click the card and click the Performance > OTN PM > FEC PM tabs. If post-FEC errors are present, troubleshoot this problem first. If not, move to next step.

Step 3 Verify the status of far-end TXP/MXP connected to the faulty near-end card. Look for any alarms reported by the Client-Rx port of far-end card. If these alarms exist, troubleshoot them.

Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.64  GFP-LFD

Default Severity: Major (MJ), Service-Affecting (SA)

The alarm is raised when there is no more valid GFP stream coming from the far end card.

Possible root cause of this alarm is lack of valid Trunk/WDM signal or the far end client equipment have not been properly configured. In particular the client PPM has not been provisioned.

2.5.65  HIBATVG

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: PWR

The High Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage exceeds the high power threshold. This threshold, with a default value of -52 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 Procedure Guide or the Cisco ONS 15454 SDH Procedure Guide as appropriate for your purpose.

Clear the HIBATVG Alarm

Step 1 The problem is external to the ONS system. Troubleshoot the power source supplying the battery leads.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.66  HI-CCVOLT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: BITS

The 64K Composite Clock High NE Voltage alarm occurs when the 64K signal peak voltage exceeds 1.1 VDC.

Clear the HI-CCVOLT Condition

Step 1 Lower the source voltage to the clock.

Step 2 If the condition does not clear, add more cable length or add a 5 dBm attenuator to the cable.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.67  HI-LASERBIAS

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, PPM, TRUNK

The Equipment High Transmit Laser Bias Current alarm is raised against TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, and OC192-XFP card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.

Laser bias typically starts at about 30 percent of the manufacturer maximum laser bias specification and increases as the laser ages. If the HI-LASERBIAS alarm threshold is set at 100 percent of the maximum, the laser usability has ended. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. Specific hardware values are listed in the "Hardware Specifications" appendix of the same manual.

Clear the HI-LASERBIAS Alarm

Step 1 Complete the "Physically Replace a Card" procedure. Replacement is not urgent and can be scheduled during a maintenance window.

Warning Warning: High-performance devices on this card can get hot during operation. To remove the card, hold it by the faceplate and bottom edge. Allow the card to cool before touching any other part of it or before placing it in an antistatic bag. Statement 201

Caution Removing an active card can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.68  HI-LASERTEMP

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: EQPT, OCN/STMN, PPM

The Equipment High Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength.

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The LOS (OCN/STMN) alarm is raised at the far-end node and the "DUP-IPADDR" alarm, page 2-39, is raised at the near end. (For instructions to clear either of these alarms, you can also refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 Troubleshooting Guide or Cisco ONS 15454SDH Troubleshooting Guide.)

Note For information about MXP and TXP cards and PPMs (SFPs), refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the HI-LASERTEMP Alarm

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the TXP or MXP card to open the card view.

Step 2 Click the Performance > Optics PM > Current Values tabs.

Step 3 Verify the card laser temperature levels. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Step 4 Complete the "Reset a Card in CTC" procedure for the MXP or TXP card.

Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.69  HI-RXPOWER

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: 2R, ESCON, FC, GE, ISC, OCN/STMN, TRUNK

The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, or OC192-XFP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.

Note For general information about MXP and TXP cards and their power levels, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the HI-RXPOWER Alarm

Step 1 Check the PM of the TRUNK-RX port. Verify that received power is above the optics threshold:

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card to display the card view.

b. For the TRUNK-RX port, double-click the card and click the Performance > Optics PM > Historical PM tabs, choose the port in the Port drop-down list, and click Refresh.

c. Compare the refreshed PM values with the threshold (ensuring that it is above the threshold value) by clicking the Performance > Optics PM > Current Values tabs.

d. Ensure that a proper threshold has been provisioned for the receive value. (Refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.) If an incorrect threshold has been set, adjust it to a value within the allowed limits. If instead the alarm condition does not clear, move to next step.

Step 2 Verify that the Trunk-Rx port is cabled correctly, and clean the fiber connecting the faulty TXP/MXP to the Drop port of the DWDM card (32DMX, 32DMX-O or AD-xC-xx.x). If no site cleaning practices are available, refer to the fiber cleaning procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 Determine whether a bulk attenuator is specified by the Cisco MetroPlanner (MP) design. If so, verify that the proper fixed attenuation value has been used.

Step 4 Using a test set, check the optical power value of the Drop port of the DWDM card (32DMX, 32DMX-O or AD-xC-xx.x) connected to the faulty TXP/MXP. If the read value is different (+1 dBm or -1 dBm) from the ANS setpoint for "Padd&drop-Drop power," move to next step.

Step 5 Look for and troubleshoot any alarm reported by the DWDM cards belonging to the OCHNC circuit destinating at the faulty TXP/MXP. Possible alarms include amplifier Gain alarms (the "GAIN-HDEG" alarm on page 2-55, the "GAIN-HFAIL" alarm on page 2-56, the "GAIN-LDEG" alarm on page 2-57, or "GAIN-LFAIL" alarm on page 2-57); APC alarms ("APC-CORRECTION-SKIPPED" alarm on page 2-23 or "APC-OUT-OF-RANGE" alarm on page 2-24), or LOS-P alarms on the Add or Drop ports involved in the OCHNC circuit.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.70  HITEMP

Default Severity: Critical (CR), Service-Affecting (SA) for NE; Default Severity: Minor (MN), Non-Service-Affecting (NSA) for EQPT

Logical Objects: EQPT, NE

The High Temperature alarm occurs when the temperature of the ONS system is above 122 degrees F (50 degrees C).

Clear the HITEMP Alarm

Step 1 View the temperature displayed on the ONS system LCD front panel. For example, the ONS 15454 front panel is illustrated in Figure 2-1.

Figure 2-1 Shelf LCD Panel

Step 2 Verify that the environmental temperature of the room is not abnormally high.

Step 3 If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS system shelf.

Step 4 If airflow is not blocked, physically ensure that blank faceplates fill the ONS system shelf empty slots. Blank faceplates help airflow.

Step 5 If faceplates fill the empty slots, determine whether the air filter needs replacement. Refer to the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Step 6 If the fan does not run or the alarm persists, complete the "Replace the Fan-Tray Assembly" procedure.

Note The fan should run immediately when correctly inserted.

Step 7 If the replacement fan-tray assembly does not operate correctly, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447) if it applies to the NE, or a Non-Service-Affecting (NSA) problem if it applies to equipment.

2.5.71  HI-TXPOWER

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, PPM, TRUNK

The Equipment High Transmit Power alarm is an indicator on the TXP_MR_E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.

Note For general information about MXP and TXP cards and power levels, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the HI-TXPOWER Alarm

Step 1 Check the PM of the Trunk-Tx port. Verify that received power is above the optics threshold:

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card to display the card view.

b. For the Trunk-Tx port, double-click the card and click the Performance > Optics PM > Historical PM tabs, choose the port in the Port drop-down list, and click Refresh.

c. Compare the refreshed PM values with the threshold (ensuring that it is above the threshold value) by clicking the Performance > Optics PM > Current Values tabs.

d. Ensure that a proper threshold has been provisioned for the receive value. (Refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.) If an incorrect threshold has been set, adjust it to a value within the allowed limits. If instead the alarm condition does not clear, move to next step.

Step 2 Physically verify, by using a standard power meter that the optical output power is overcoming the expected power threshold. If so, the card should be replaced at first opportunity

Note The higher power level is not a major issue for the DWDM card (32MUX-O, 32WSS-O, or AD-xC-xx.x) connected to the faulty TXP/MXP, because an internal VOA can automatically decrease the optical power to the expected level.

Step 3 Complete the "Physically Replace a Card" procedure.

Step 4 If the alarm does not clear after the replacement, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.72  HLDOVRSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE-SREF

The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS system relying on an internal clock.

Clear the HLDOVRSYNC Condition

Step 1 Clear additional alarms that relate to timing, such as:

•FRNGSYNC

•FSTSYNC

•LOF (BITS)

•LOS (BITS)

•MANSWTOINT

•MANSWTOPRI

•MANSWTOSEC

•MANSWTOTHIRD

•SWTOPRI

•SWTOSEC

•SWTOTHIRD

•SYNC-FREQ

•SYNCPRI

•SYNCSEC

•SYNCTHIRD

Step 2 Reestablish a primary and secondary timing source according to local site practice. If none exists, refer to the "Turn Up the Network" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.73  I-HITEMP

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: NE

The Industrial High Temperature alarm occurs when the temperature of the ONS system is above 149 degrees F (65 degrees C) or below -40 degrees F (-40 degrees C). This alarm is similar to the HITEMP alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.

Clear the I-HITEMP Alarm

Step 1 Complete the "Clear the HITEMP Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.74  IMPROPRMVL

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: EQPT, PPM

The Improper Removal equipment alarm occurs when a card is physically removed from its slot before it is deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm; it only needs to be recognized by CTC. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node. It can also occur if the card is inserted into a slot but is not fully plugged into the backplane. For PPMs (SFPs), the alarm occurs if you provision a PPM (SFP) but no physical module is inserted on the port.

Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot. When you delete the card, CTC loses connection with the node view (single-shelf mode) or shelf view (multishelf mode), and goes to network view.

Note CTC gives the user approximately 15 seconds to physically remove the card before CTC begins a card reboot.

Note For more information about provisioning PPMs (SFPs), refer to the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For specific PPM (SFP) values, refer to the "Hardware Specifications" appendix of the Cisco ONS 15454 DWDM Reference Manual.

Note For more information about protection schemes, refer to the "Manage the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Note It can take up to 30 minutes for software to be updated on a standby TCC2/TCC2P card.

Clear the IMPROPRMVL Alarm

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.

Note CTC does not allow you to delete the reporting card if the card is in service, does have circuits mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.

Step 3 If any ports on the card are in service, place them out of service (OOS,MT or Locked,maintenance):

Caution Before placing a port out of service (OOS,MT or Locked,maintenance) or OOS,DSBLD (or Locked,disabled), ensure that no live traffic is present.

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the reporting card to open the card view.

b. Click the Provisioning > Line tabs.

c. Click the Admin State column of any in-service (IS or Unlocked) ports.

d. Choose OOS,MT (or Locked,maintenance) to take the ports out of service.

Step 4 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.

Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.

Step 5 If the card is paired in a protection scheme, delete the protection group by completing the following steps:

a. Click View > Go to Previous View to return to node view (single-shelf mode) or shelf view (multishelf mode).

b. If you are already in node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Protection tab.

c. Click the protection group of the reporting card.

d. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning by completing the following steps:

a. In node view (single-shelf mode) or multishelf view (multishelf mode), click the ONS system Provisioning > Comm Channels > SDCC (or Provisioning > Comm Channels > MS DCC) tabs.

b. Click the slots and ports listed in DCC terminations.

c. Click Delete and click Yes in the dialog box that appears.

Step 7 If the card is used as a timing reference, change the timing reference by completing the following steps:

a. In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Timing > General tabs.

b. Under NE Reference, click the drop-down arrow for Ref-1.

c. Change Ref-1 from the listed OC-N/STM-N card to Internal Clock.

d. Click Apply.

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.75  INCOMPATIBLE-SEND-PDIP

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: SYSTEM

The Incompatible Software alarm is raised when CTC'S send PDI-P provisioning differs from the host node's provisioning.

Clear the INCOMPATIBLE-SEND-PDIP Alarm

Step 1 Reconfigure CTC's send PDI-P alarm capability to align with the host node settings.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).

2.5.76  INCOMPATIBLE-SW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: SYSTEM

The Incompatible Software alarm is raised when CTC cannot connect to the NE due to differing, incompatible versions of software between CTC and the NE. The alarm is cleared by restarting CTC in order to redownload the CTC JAR files from the NE.

Clear the INCOMPATIBLE-SW Alarm

Step 1 Restart the CTC application.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).

2.5.77  INTRUSION-PSWD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: NE

The Security Intrusion Incorrect Password condition occurs after a user attempts a provisionable (by Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not in login sessions for lower-level users. The INTRUSION-PSWD condition is automatically cleared when a provisionable lockout timeout expires, or it can be manually cleared in CTC by the Superuser if the lockout is permanent.

Clear the INTRUSION-PSWD Condition

Step 1 Log in as a user ID with superuser rights. (For more information about this, refer to the "Connect the PC and Log Into the GUI" chapter in the Cisco ONS 15454 DWDM Procedure Guide.)

Step 2 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Security > Users tabs.

Step 3 Click Clear Security Intrusion Alarm.

Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.78  INVMACADR

Default Severity: Major (MJ), Non-Service Affecting (NSA)

Logical Object: AIP

The Equipment Failure Invalid MAC Address alarm occurs when the ONS system MAC address is invalid. Each ONS system has a unique, permanently assigned MAC address. The address resides on an AIP EEPROM. The TCC2/TCC2P card reads the address value from the AIP chip during boot-up and keeps this value in its synchronous dynamic RAM (SDRAM).

Under normal circumstances, the read-only MAC address can be viewed in the node view (single-shelf mode) or multishelf view (multishelf mode) Provisioning > Network tab in CTC.

The ONS system uses both IP and MAC addresses for circuit routing. When an INVMACADR alarm exists on a node, you see a PARTIAL circuit in the CTC circuit status column. The circuit works and is able to carry traffic, but CTC cannot logically display the circuit end-to-end information.

An invalid MAC address can be caused when:

•There is a read error from the AIP during boot-up; in this case, the reading TCC2/TCC2P card uses the default MAC address (00-10-cf-ff-ff-ff).

•There is a read error occurring on one of the redundant TCC2/TCC2P cards that read the address from the AIP; these cards read the address independently and could therefore each read different address values.

•An AIP component failure causes a read error.

•The ribbon cable connecting the AIP card to the backplane is bad.

Clear the INVMACADR Alarm

Step 1 Check for any outstanding alarms that were raised against the active and standby TCC2/TCC2P card and resolve them.

Step 2 If the alarm does not clear, determine whether the LCD display on the fan tray (Figure 2-1) is blank or if the text is garbled. If so, proceed to Step 8. If not, continue with Step 3.

Step 3 At the earliest maintenance window, reset the standby TCC2/TCC2P card:

Note The reset requires approximately five minutes. Do not perform any other step until the reset is complete.

a. Log into a node on the network. If you are already logged in, continue with Step b.

b. Identify the active TCC2/TCC2P card.

A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

c. In node view (single-shelf mode) or shelf view (multishelf mode), right-click the standby TCC2/TCC2P card in CTC.

d. Choose Reset Card from the shortcut menu.

e. Click Yes in the Are You Sure dialog box.

The card resets, the FAIL LED blinks on the physical card, and connection to the node is lost. CTC switches to network view.

f. Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

g. Double-click the node and ensure that the reset TCC2/TCC2P card is still in standby mode and that the other TCC2/TCC2P card is active.

A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

h. Ensure that no new alarms associated with this reset appear in the CTC Alarms window.

If the standby TCC2/TCC2P card fails to boot into standby mode and reloads continuously, the AIP is probably defective. In this case, the standby TCC2/TCC2P card is unsuccessfully attempting to read the EEPROM located on the AIP. The TCC2/TCC2P card reloads until it reads the EEPROM. Proceed to Step 8.

Step 4 If the standby TCC2/TCC2P card rebooted successfully into standby mode, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure.

Resetting the active TCC2/TCC2P card causes the standby TCC2/TCC2P card to become active. The standby TCC2/TCC2P card keeps a copy of the chassis MAC address. If its stored MAC address is valid, the alarm should clear.

Step 5 After the reset, note whether or not the INVMACADR alarm has cleared or is still present.

Step 6 Complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure again to place the standby TCC2/TCC2P card back into active mode.

After the reset, note whether or not the INVMACADR alarm has cleared or is still present. If the INVMACADR alarm remains standing through both TCC2/TCC2P card resets, this indicates that the AIP is probably defective. Proceed to Step 8.

If the INVMACADR was raised during one TCC2/TCC2P card reset and cleared during the other, the TCC2/TCC2P card that was active while the alarm was raised needs to be replaced. Continue with Step 7.

Step 7 If the faulty TCC2/TCC2P card is currently in standby mode, complete the "Physically Replace a Card" procedure for this card. If the faulty TCC2/TCC2P card is currently active, during the next available maintenance window complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure and then complete the "Physically Replace a Card" procedure.

Note If the replacement TCC2/TCC2P card is loaded with a different software version from the current TCC2/TCC2P card, the card boot-up could take up to 30 minutes. During this time, the card LEDs flicker between Fail and Act/Sby as the active TCC2/TCC2P card version software is copied to the new standby card.

Step 8 Open a case with Cisco TAC (1 800 553-2447) for assistance with determining the node's previous MAC address.

Step 9 Replace the ribbon cable between the system board and the AIP with a known-good cable.

Step 10 If the alarm persists, complete the "Replace an Alarm Interface Panel" procedure located in the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 Troubleshooting Guide.

Step 11 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.79  LASER-APR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Laser Automatic Power Reduction (APR) alarm condition is raised by OSC-CSM, OSCM, OPT-BST, and OPT-PRE cards when the laser is working in power reduction mode. The condition clears as soon as safety conditions are released and the power value reaches the normal setpoint.

Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments. Statement 1051.

Note Only inactivate the APR function temporarily for installation or maintenance reasons. Activate APR immediately after maintenance or installation.

Note LASER-APR is an informational condition and does not require troubleshooting. For more information about optical amplifier APR, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

2.5.80  LASERBIAS-DEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: AOTS, OTS

The Laser Bias Current Degrade alarm occurs on an amplifier card (OPT-BST or OPT-PRE) when laser aging causes a degrade, but not failure, of laser transmission. The card should be replaced at the next opportunity.

Note For general information about optical amplifier cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LASERBIAS-DEG Alarm

Step 1 For the alarmed card, complete the "Physically Replace a Card" procedure at the next opportunity.

Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056

Note Before disconnecting any optical amplifier card fiber for troubleshooting, ensure that the optical amplifier card is unplugged.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.81  LASERBIAS-FAIL

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Laser Bias Current Failure alarm occurs on an amplifier card (OPT-BST or OPT-PRE) when the laser control circuit fails or if the laser itself fails service. The card must be replaced to restore traffic.

Note For general information about optical amplifier cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LASERBIAS-FAIL Alarm

Step 1 For the alarmed card, complete the "Physically Replace a Card" procedure.

Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056

Note Before disconnecting any optical amplifier card fiber for troubleshooting, ensure that the optical amplifier card is unplugged.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.82  LASERTEMP-DEG

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: AOTS

The Laser Temperature Degrade alarm occurs when the Peltier control circuit fails on an amplifier card (OPT-BST or OPT-PRE). The Peltier control provides cooling for the amplifier. The card should be replaced at the next opportunity.

Note For general information about DWDM cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about changing their settings, refer to the "Change DWDM Card Settings" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LASERTEMP-DEG Alarm

Step 1 For the alarmed DWDM card, complete the "Physically Replace a Card" procedure at the next opportunity.

Warning Invisible laser radiation may be emitted from the end of the unterminated fiber cable or connector. Do not view directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm may pose an eye hazard. Statement 1056

Note Before disconnecting any optical amplifier card fiber for troubleshooting, ensure that the optical amplifier card is unplugged.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.83  LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC

The Lockout Switch Request on Facility or Equipment condition occurs in a Y-cable MXP or TXP client protection group for the above-listed clients when a user initiates a lockout switch request. The condition is raised when you lock traffic onto the working port with the Lock On command (thus locking it off the protect port), or you lock it off the protect port with the Lock Out command. In either case, the protect port will show "Lockout of Protection," and the Conditions window will show the LOCKOUT-REQ condition.

A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Clear the LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC) Condition

Step 1 Complete the "Clear a Lock-On or Lockout Command" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.84  LOCKOUT-REQ (TRUNK)

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: TRUNK

The Lockout Switch Request on Facility or Equipment condition occurs in an MXP or TXP trunk port splitter protection group when you lock traffic onto the working port with the Lock On command (thus locking it off the protect port), or lock it off the protect port with the Lock Out command. In either case, the protect port will show "Lockout of Protection," and the Conditions window will show the LOCKOUT-REQ condition.

A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Clear the LOCKOUT-REQ (TRUNK) Condition

Step 1 Complete the "Clear a Lock-On or Lockout Command" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.85  LOF (BITS)

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: BITS

The Loss of Frame (LOF) BITS alarm occurs when a port on theTCC2/TCC2P card BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS system has lost frame delineation in the incoming data.

Note The procedure assumes that the BITS timing reference signal is functioning properly. It also assumes the alarm is not appearing during node turn-up.

Clear the LOF (BITS) Alarm

Step 1 Verify that the line framing and line coding match between the BITS input and the TCC2/TCC2P card:

a. In node or card view, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.

c. In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Timing > BITS Facilities tabs.

d. Verify that the Coding setting matches the coding of the BITS timing source, either B8ZS or AMI.

e. If the coding does not match, click Coding and choose the appropriate coding from the drop-down list.

f. Verify that Framing matches the framing of the BITS timing source, either ESF or SF (D4).

g. If the framing does not match, click Framing and choose the appropriate framing from the drop-down list.

Note On the timing subtab, the B8ZS coding field is normally paired with ESF in the Framing field and the AMI coding field is normally paired with SF (D4) in the Framing field.

Step 2 If the alarm does not clear when the line framing and line coding match between the BITS input and the TCC2/TCC2P card, complete the "Physically Replace a Card" procedure for the TCC2/TCC2P card.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.86  LOF (TRUNK)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: TRUNK

The Loss of Frame for the DWDM trunk applies to the trunk optical or electrical signal that is carried to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and MXP_2.5G_10G cards. It indicates that the receiving ONS system has lost frame delineation in the incoming data from trunk that serves the cards. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.

Clear the LOF (TRUNK) Alarm

Step 1 Using site practices, verify fiber continuity to the port. Refer to the "Network Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual for a procedure to detect a fiber cut.

Step 2 If the cabling is good, verify that the correct port is in service by completing the following steps:

a. Confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

b. To determine whether the port is in service, in node view (single-shelf mode) or shelf view (multishelf mode), double-click the card in CTC to open the card view.

c. Click the Provisioning > Line tabs.

d. Verify that the Admin State column lists the port as IS (or Unlocked).

e. If the Admin State column lists the port as OOS,MT (or Locked,maintenance) or OOS,DSBLD (or Locked,disabled), click the column and choose IS , or Unlocked.

f. Click Apply.

Step 3 If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the fiber cleaning procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the TXP or MXP card receiver specifications. (These specifications are listed in the "Hardware Specifications" appendix of the Cisco ONS 15454 DWDM Reference Manual.)

Step 5 If the optical power level is within specifications, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

Step 6 If a valid signal exists, replace the connector on the backplane.

Step 7 Repeat Steps 1 to 6 for any other port on the card reporting the LOF.

Step 8 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.

Step 9 If no other alarms exist that could be the source of the LOF, or if clearing an alarm did not clear the LOF, complete the "Physically Replace a Card" procedure for the reporting card.

Step 10 If the alarm does not clear, or if you need assistance conducting network troubleshooting tests, call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.5.87  LOGBUFR90

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: SYSTEM

The Log Buffer Over 90 alarm indicates that the per-NE queue of incoming alarm, event, or update capacity of 5000 entries is over 90 percent full. LOGBUFR90 will clear if CTC recovers. If it does not clear, LOGBUFROVFL occurs.

Note LOGBUFR90 is an informational alarm and does not require troubleshooting.

2.5.88  LOGBUFROVFL

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: SYSTEM

The Log Buffer Overflow alarm indicates that the CTC per-NE queue of incoming alarm, event, or updates, which has a capacity of 5,000 entries, has overflowed. This happens only very rarely. However if it does, you must restart the CTC session. It is likely that some updates will have been missed if this alarm occurs.

Clear the LOGBUFROVFL Alarm

Step 1 Restart the CTC session.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).

2.5.89  LO-LASERBIAS

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: EQPT, OCN/STMN, PPM

The Equipment Low Transmit Laser Bias Current alarm is raised against the TXP and MXP card laser performance. The alarm indicates that the card laser has reached the minimum laser bias tolerance.

If the LO-LASERBIAS alarm threshold is set at 0 percent (the default), the laser's usability has ended. If the threshold is set at 5 percent to 10 percent, the card is still usable for several weeks or months before you need to replace it.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LO-LASERBIAS Alarm

Step 1 Complete the "Physically Replace a Card" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.90  LO-LASERTEMP

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: EQPT, OCN/STMN, PPM

The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. LO-LASERTEMP occurs when the internally measured transceiver temperature falls below the card setting by35.6 degrees F or 2 degrees C. A laser temperature change affects the transmitted wavelength. (This temperature is equivalent to about 200 picometers of wavelength.)

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The An LOS for OCN/STMN is raised at the far-end node and the "DUP-IPADDR" alarm on page 2-39 is raised at the near end. (Both of these alarms are described in the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 Troubleshooting Guide or the Cisco ONS 15454SDH Troubleshooting Guide). To verify the card laser temperature level, double-click the card in node view (single-shelf mode) or shelf view (multishelf mode) and click the Performance > Optics PM > Current Values tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LO-LASERTEMP Alarm

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), complete the "Reset a Card in CTC" procedure for the reporting MXP or TXP card.

Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.91  LOM

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: TRUNK

The Optical Transport Unit (OTU) Loss of Multiframe alarm is an OTN alarm for the trunk port and occurs when the Multi Frame Alignment Signal (MFAS) is corrupted. The alarm applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXPP_MR_2.5G cards when the MFAS) overhead field is errored for more than five frames and persists for more than 3 milliseconds.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual. For information about provisioning them, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Clear the LOM Alarm

Step 1 Ensure that the fiber connector for the card is completely plugged in. For more information about fiber connections and card insertion, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 2 If the bit error rate (BER) threshold is correct and at the expected level, use an optical test set to measure the power level of the line to ensure it is within guidelines. For specific procedures to use the test set equipment, consult the manufacturer.

Step 3 If the optical power level is good, verify that optical receive levels are within the acceptable range. Ranges for ONS 15454 DWDM cards are located in the "Hardware Specifications" appendix of the Cisco ONS 15454 DWDM Reference Manual.

Step 4 If receive levels are good, clean the fibers at both ends according to site practice. If no site practice exists, complete the fiber cleaning procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 5 If the condition does not clear, verify that single-mode fiber is used.

Step 6 If the fiber is of the correct type, verify that a single-mode laser is used at the far-end node.

Step 7 Clean the fiber connectors at both ends for a signal degrade according to site practice.

Step 8 Verify that a single-mode laser is used at the far end.

Step 9 If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement. Refer to the "Physical Card Reseating, Resetting, and Replacement" section.

Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.5.92  LO-RXPOWER

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Objects: 2R, ESCON, FC, GE, ISC, OCN/STMN, TRUNK

The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G and OC192-XFP card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls below the threshold value, which is user-provisionable.

Note For general information about MXP and TXP cards and their necessary levels, refer to the "Card Reference" chapter and the "Hardware Specifications" appendix in the Cisco ONS 15454 DWDM Reference Manual.

Clear the LO-RXPOWER Alarm

Step 1 Check the PM of the TRUNK-RX port. Verify that received power is above the optics threshold:

a. In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card to display the card view.

b. For the TRUNK-RX port, double-click the card and click the Performance > Optics PM > Historical PM tabs, choose the port in the Port drop-down list, and click Refresh.

c. Compare the refreshed PM values with the threshold (ensuring that they are above the threshold value) by clicking the Performance > Optics PM > Current Values tabs.

d. Ensure that a proper threshold has been provisioned for the receive value. (Refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.) If an incorrect threshold has been set, adjust it to a value within the allowed limits. If instead the alarm condition does not clear, move to next step.

Step 2 Verify that the Trunk-Rx port is cabled correctly, and clean the fiber connecting the faulty TXP/MXP to the Drop port of the DWDM card (32DMX, 32DMX-O or AD-xC-xx.x). If no site cleaning practices are available, refer to the "Maintain the Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide.

Step 3 Determine whether a bulk attenuator is specified by the Cisco MetroPlanner design. If so, verify that the proper fixed attenuation value has been used.

Step 4 Using a test set, check the optical power value of the Drop port of the DWDM card (32DMX, 32DMX-O or AD-xC-xx.x) connected to the faulty TXP/MXP. If the read value is different (+1 dBm or -1 dBm) from the ANS setpoint for "Padd&drop-Drop power," move to next step. If not, complete the "Physically Replace a Card" section.

Step 5 Look for any alarm reported by the DWDM cards belonging to the OCHNC circuit whose destination is the faulty TXP/MXP and first troubleshoot that alarm. Possible alarm related include: amplifier Gain alarms (the "GAIN-HDEG" alarm on page 2-55, the "GAIN-HFAIL" alarm on page 2-56, the "GAIN-LDEG" alarm on page 2-57, or "GAIN-LFAIL" alarm on page 2-57); APC alarms (the "APC-CORRECTION-SKIPPED" alarm on page 2-23 or "APC-OUT-OF-RANGE" alarm on page 2-24), and LOS-P alarms on the Add or Drop ports belonging to the OCHNC circuit.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.5.93  LOS (2R)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: 2R

The Loss of Signal for a 2R client applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly. To verify cable continuity, follow site practices.

Note For general information about MXP and TXP cards, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Clear the LOS (2R) Alarm

Step 1 Ensure that the signal entering the Client-Rx port is provisioned with the correct physical-layer protocol.

Step 2 Ensure that the signal feeding the Client-Rx port is provisioned with the correct line speed.

Step 3 Check the PM of the Client-Rx port.

Step 4 Verify that received power is above the optics threshold.

Step 5 Ensure that a proper threshold has been provisioned. (Refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide. Refer to the SFP/XFP plug-in specifications located in the "Hardware Specifications" appendix of the Cisco ONS 15454 DWDM Reference Manual.) If an incorrect threshold has been set, adjust it to a value within the allowed limits.

Step 6 Verify the proper cabling and clean the fibers according with the site practice. Cabling procedures are located in the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide, and a fiber-cleaning procedure is located in the "Maintain the Node" chapter of the same guide.

Step 7 Verify using an optical test set that a valid signal exists on the line and feeds the Client-Rx port. (For specific procedures to use the test set equipment, consult the manufacturer.) Test the line as close to the receiving card as possible. If the alarm condition does not clear, move to next step.

Step 8 Complete the XFP/SFP installation procedure in the "Turn Up a Node" chapter of the Cisco ONS 15454 DWDM Procedure Guide or the "Physically Replace a Card" procedure as appropriate for your purposes.

Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.5.94  LOS (BITS)

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

Logical Object: BITS

The LOS (BITS) alarm indicates that the TCC2/TCC2P card has an LOS from the BITS timing source. LOS for BITS means the BITS clock or the connection to it failed.

Clear the LOS (BITS) Alarm

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.

Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS system backplane to the timing source.

Step 2 If wiring is good, verify that the BITS cl