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  AIS-P

Clear the AIS-P Condition

2.5.4  ALS

2.5.5  ALS-DISABLED

Clear the ALS-DISABLED Condition

2.5.6  AMPLI-INIT

Clear the AMPLI-INIT Condition

2.5.7  APC-CORR-SKIPPED

2.5.8  APC-DISABLED

Clear the APC-DISABLED Alarm

2.5.9  APC-END

2.5.10  APC-OUT-OF-RANGE

Clear the APC-OUT-OF-RANGE Alarm

2.5.11  APC-WRONG-GAIN

Clear the APC-WRONG-GAIN Alarm

2.5.12  APSB

Clear the APSB Alarm

2.5.13  APSCM

Clear the APSCM Alarm

2.5.14  APSIMP

Clear the APSIMP Alarm

2.5.15  APS-INV-PRIM

2.5.16  APSMM

Clear the APSMM Alarm

2.5.17  APS-PRIM-FAC

Clear the APS-PRIM-FAC Condition

2.5.18  APS-PRIM-SEC-MISM

Clear the APS-PRIM-SEC-MISM Alarm

2.5.19  AS-CMD

Clear the AS-CMD Condition

2.5.20  AS-MT

Clear the AS-MT Condition

2.5.21  AU-AIS

Clear the AU-AIS Condition

2.5.22  AU-LOP

Clear the AU-LOP Alarm

2.5.23  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.5.24  AUTORESET

Clear the AUTORESET Alarm

2.5.25  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.5.26  AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-path protection Condition

2.5.27  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.5.28  AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.5.29  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.5.30  AUTOSW-PDI-SNCP

Clear the AUTOSW-PDI-SNCP Condition

2.5.31  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.5.32  AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.5.33  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.5.34  AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.5.35  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.5.36  AUTOSW-UNEQ-SNCP (VCMON-HP)

Clear the AUTOSW-UNEQ-SNCP (VCMON-HP) Condition

2.5.37  AWG-DEG

Clear the AWG-DEG Alarm

2.5.38  AWG-FAIL

Clear the AWG-FAIL Alarm

2.5.39  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.5.40  AWG-WARM-UP

2.5.41  BAT-FAIL

Clear the BAT-FAIL Alarm

2.5.42  BKUPMEMP

Clear the BKUPMEMP Alarm

2.5.43  BPV

Clear the BPV Alarm

2.5.44  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.5.45  CARLOSS (FC)

Clear the CARLOSS (FC) Alarm

2.5.46  CARLOSS (GE)

Clear the CARLOSS (GE) Alarm

2.5.47  CARLOSS (ISC)

Clear the CARLOSS (ISC) Alarm

2.5.48  CARLOSS (TRUNK)

Clear the CARLOSS (TRUNK) Alarm

2.5.49  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.5.50  CHANLOSS

Clear the CHANLOSS Condition

2.5.51  CLDRESTART

Clear the CLDRESTART Condition

2.5.52  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.5.53  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.5.54  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.5.55  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.5.56  DATAFLT

Clear the DATAFLT Alarm

2.5.57  DBOSYNC

Clear the DBOSYNC Alarm

2.5.58  DCU-LOSS-FAIL

Clear the DCU-LOSS-FAIL Condition

2.5.59  DISCONNECTED

Clear the DISCONNECTED Alarm

2.5.60  DSP-COMM-FAIL

2.5.61  DSP-FAIL

Clear the DSP-FAIL Alarm

2.5.62  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.5.63  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.5.64  DUP-SHELF-ID

Clear the DUP-SHELF-ID Alarm

2.5.65  EHIBATVG

Clear the EHIBATVG Alarm

2.5.66  ELWBATVG

Clear the ELWBATVG Alarm

2.5.67  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.5.68  EOC

Clear the EOC Alarm

2.5.69  EOC-L

Clear the EOC-L Alarm

2.5.70  EQPT

Clear the EQPT Alarm

2.5.71  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.5.72  EQPT-MISS

Clear the EQPT-MISS Alarm

2.5.73  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.5.74  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.5.75  EXCCOL

Clear the EXCCOL Alarm

2.5.76  EXT

Clear the EXT Alarm

2.5.77  FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS)

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

2.5.78  FAILTOSW (TRUNK)

Clear the FAILTOSW (TRUNK) Condition

2.5.79  FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.5.80  FAILTOSW-PATH

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration

2.5.81  FAN

Clear the FAN Alarm

2.5.82  FAPS

Clear the FAPS Alarm

2.5.83  FAPS-CONFIG-MISMATCH

Clear the FAPS-CONFIG-MISMATCH Condition

2.5.84  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.5.85  FDI

Clear the FDI Condition

2.5.86  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.5.87  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.5.88  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.5.89  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.5.90  FEC-MISM

Clear the FEC-MISM Alarm

2.5.91  FEPRLF

Clear the FEPRLF Alarm on an BLSR

2.5.92  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.5.93  FORCED-REQ

Clear the FORCED-REQ Condition

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

2.5.95  FORCED-REQ-SPAN (TRUNK)

2.5.96  FP-LINK-LOSS

Clear the FP-LINK-LOSS Condition

2.5.97  FRCDSWTOINT

2.5.98  FRCDSWTOPRI

2.5.99  FRCDSWTOSEC

2.5.100  FRCDSWTOTHIRD

2.5.101  FRNGSYNC

Clear the FRNGSYNC Condition

2.5.102  FSTSYNC

2.5.103  FTA-MISMATCH

Clear the FTA-MISMATCH Condition

2.5.104  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.5.105  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.5.106  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.5.107  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.5.108  GCC-EOC

Clear the GCC-EOC Alarm

2.5.109  GE-OOSYNC (FC, GE, ISC)

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

2.5.110  GE-OOSYNC (TRUNK)

Clear the GE-OOSYNC (TRUNK) Alarm

2.5.111  GFP-CSF

Clear the GFP-CSF Alarm

2.5.112  GFP-LFD

Clear the GFP-LFD Alarm

2.5.113  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.5.114  HELLO

Clear the HELLO Alarm

2.5.115  HIBATVG

Clear the HIBATVG Alarm

2.5.116  HI-CCVOLT

Clear the HI-CCVOLT Condition

2.5.117  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.5.118  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.5.119  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.5.120  HITEMP

Clear the HITEMP Alarm

2.5.121  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.5.122  HLDOVRSYNC

Clear the HLDOVRSYNC Condition

2.5.123  HP-DEG

Clear the HP-DEG Condition

2.5.124  HP-ENCAP-MISMATCH

Clear the HP-ENCAP-MISMATCH Alarm

2.5.125  HP-EXC

Clear the HP-EXC Condition

2.5.126  HP-PLM

2.5.127  HP-RFI

Clear the HP-RFI Condition

2.5.128  HP-TIM

Clear the HP-TIM Alarm

2.5.129  HP-UNEQ

Clear the HP-UNEQ Alarm

2.5.130  I-HITEMP

Clear the I-HITEMP Alarm

2.5.131  ILK-FAIL

Clear the ILK-FAIL Alarm

2.5.132  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.5.133  INHSWPR

Clear the INHSWPR Condition

2.5.134  INHSWWKG

Clear the INHSWWKG Condition

2.5.135  INCOMPATIBLE-SEND-PDIP

Clear the INCOMPATIBLE-SEND-PDIP Alarm

2.5.136  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.5.137  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.5.138  INVMACADR

Clear the INVMACADR Alarm

2.5.139  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.5.140  LASER-APR

2.5.141  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.5.142  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.5.143  LASEREOL

Clear the LASEREOL Alarm

2.5.144  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.5.145  LMP-FAIL

Clear the LMP-FAIL Alarm

2.5.146  LMP-SD

Clear the LMP-SD Condition

2.5.147  LMP-SF

Clear the LMP-SF Condition

2.5.148  LMP-UNALLOC

2.5.149  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

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

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

2.5.151  LOCKOUT-REQ (TRUNK)

Clear the LOCKOUT-REQ (TRUNK) Condition

2.5.152  LOF (BITS)

Clear the LOF (BITS) Alarm

2.5.153  LOF (TRUNK)

Clear the LOF (TRUNK) Alarm

2.5.154  LOGBUFR90

2.5.155  LOGBUFROVFL

Clear the LOGBUFROVFL Alarm

2.5.156  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.5.157  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.5.158  LOM

Clear the LOM Alarm

2.5.159  LOP-P

Clear the LOP-P Alarm

2.5.160  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.5.161  LOS (2R)

Clear the LOS (2R) Alarm

2.5.162  LOS (BITS)

Clear the LOS (BITS) Alarm

2.5.163  LOS (ESCON)

Clear the LOS (ESCON) Alarm

2.5.164  LOS (ISC)

Clear the LOS (ISC) Alarm

2.5.165  LOS (OTS)

Clear the LOS (OTS) Alarm

2.5.166  LOS (TRUNK)

Clear the LOS (TRUNK) Alarm

2.5.167  LOS-O

Clear the LOS-O Alarm

2.5.168  LOS-P (AOTS, OMS, OTS)

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

2.5.169  LOS-P (OCH)

Clear the LOS-P (OCH) Alarm

2.5.170  LOS-P (TRUNK)

Clear the LOS-P (TRUNK) Alarm

2.5.171  LOS-RAMAN (OTS)

Clear the LOS-RAMAN Condition

2.5.172  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.5.173  LPBKCRS

Clear the Condition

2.5.174  LPBKFACILITY (ESCON)

Clear the LPBKFACILITY (ESCON) Condition

2.5.175  LPBKFACILITY (FC)

Clear the LPBKFACILITY (FC) Condition

2.5.176  LPBKFACILITY (GE)

Clear the LPBKFACILITY (GE) Condition

2.5.177  LPBKFACILITY (ISC)

Clear the LPBKFACILITY (ISC) Condition

2.5.178  LPBKFACILITY (TRUNK)

Clear the LPBKFACILITY (TRUNK) Condition

2.5.179  LPBKTERMINAL (ESCON)

Clear the LPBKTERMINAL (ESCON) Condition

2.5.180  LPBKTERMINAL (FC)

Clear the LPBKTERMINAL (FC) Condition

2.5.181  LPBKTERMINAL (GE)

Clear the LPBKTERMINAL (GE) Condition

2.5.182  LPBKTERMINAL (ISC)

Clear the LPBKTERMINAL (ISC) Condition

2.5.183  LPBKTERMINAL (TRUNK)

Clear the LPBKTERMINAL (TRUNK) Condition

2.5.184  LWBATVG

Clear the LWBATVG Alarm

2.5.185  MAN-REQ

Clear the MAN-REQ Condition

2.5.186  MANRESET

2.5.187  MANSWTOINT

2.5.188  MANSWTOPRI

2.5.189  MANSWTOSEC

2.5.190  MANSWTOTHIRD

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

2.5.192  MANUAL-REQ-SPAN (TRUNK)

2.5.193  MEA (AIP)

Clear the MEA (AIP) Alarm

2.5.194  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.5.195  MEA (FAN)

Clear the MEA (FAN) Alarm

2.5.196  MEA (PPM)

Clear the MEA (PPM) Alarm

2.5.197  MEM-GONE

2.5.198  MEM-LOW

2.5.199  MFGMEM

Clear the MFGMEM Alarm

2.5.200  MS-AIS

Clear the MS-AIS Condition

2.5.201  MS-DEG

Clear the MS-DEG Condition

2.5.202  MS-EOC

Clear the MS-EOC Alarm

2.5.203  MS-EXC

Clear the MS-EXC Condition

2.5.204  MS-RFI

Clear the MS-RFI Condition

2.5.205  MT-OCHNC

Clear the MT-OCHNC Condition

2.5.206  NON-CISCO-PPM

Clear the NON-CISCO-PPM Condition

2.5.207  NOT-AUTHENTICATED

2.5.208  OCHNC-INC

Clear the OCHNC-INC Alarm

2.5.209  OCHTERM-INC

Clear the OCHTERM-INC Condition

2.5.210  ODUK-1-AIS-PM

Clear the ODUK-1-AIS-PM Condition

2.5.211  ODUK-2-AIS-PM

Clear the ODUK-2-AIS-PM Condition

2.5.212  ODUK-3-AIS-PM

Clear the ODUK-3-AIS-PM Condition

2.5.213  ODUK-4-AIS-PM

Clear the ODUK-4-AIS-PM Condition

2.5.214  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.5.215  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.5.216  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.5.217  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.5.218  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.5.219  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.5.220  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.5.221  OPEN-SLOT

Clear the OPEN-SLOT Condition

2.5.222  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.5.223  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.5.224  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.5.225  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.5.226  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.5.227  OSRION

Clear the OSRION Condition

2.5.228  OTUK-AIS

Clear the OTUK-AIS Condition

2.5.229  OTUK-BDI

Clear the OTUK-BDI Condition

2.5.230  OTUK-IAE

Clear the OTUK-IAE Alarm

2.5.231  OTUK-LOF

Clear the OTUK-LOF Alarm

2.5.232  OTUK-SD

Clear the OTUK-SD Condition

2.5.233  OTUK-SF

Clear the OTUK-SF Condition

2.5.234  OTUK-TIM

Clear the OTUK-TIM Condition

2.5.235  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.5.236  PARAM-MISM

2.5.237  PDI-P

Clear the PDI-P Condition

2.5.238  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.5.239  PMI

Clear the PMI Condition

2.5.240  PORT-FAIL

Clear the PORT-FAIL Alarm

2.5.241  PROTNA

Clear the PROTNA Alarm

2.5.242  PROV-MISMATCH

Clear the PROV-MISMATCH Alarm

2.5.243  PTIM

Clear the PTIM Alarm

2.5.244  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.5.245  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.5.246  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.5.247  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.5.248  PWR-PROT-ON

Clear the PWR-PROT-ON Alarm

2.5.249  RFI

Clear the RFI Condition

2.5.250  RFI-L

Clear the RFI-L Condition

2.5.251  RFI-P

Clear the RFI-P Condition

2.5.252  RLS

Clear the RLS Condition

2.5.253  ROUTE-OVERFLOW

Clear the ROUTE-OVERFLOW Condition

2.5.254  RS-EOC

Clear the RS-EOC Alarm

2.5.255  RS-TIM

Clear the RS-TIM Alarm

2.5.256  SD (TRUNK)

Clear the SD (TRUNK) Condition

2.5.257  SD-L

Clear the SD-L Condition

2.5.258  SD-P

Clear the SD-P Condition

2.5.259  SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.5.260  SF (TRUNK)

Clear the SF (TRUNK) Condition

2.5.261  SF-L

Clear the SF-L Condition

2.5.262  SF-P

Clear the SF-P Condition

2.5.263  SFTWDOWN

2.5.264  SHELF-COMM-FAIL

Clear the SHELF-COMM-FAIL Alarm

2.5.265  SH-IL-VAR-DEG-HIGH

Clear the SH-IL-VAR-DEG-HIGH Alarm

2.5.266  SH-IL-VAR-DEG-LOW

Clear the SH-IL-VAR-DEG-LOW Alarm

2.5.267  SHUTTER-OPEN

Clear the SHUTTER-OPEN Condition

2.5.268  SIGLOSS

Clear the SIGLOSS Alarm

2.5.269  SNTP-HOST

Clear the SNTP-HOST Alarm

2.5.270  SPANLEN-OUT-OF-RANGE

Clear the SPANLEN-OUT-OF-RANGE Alarm

2.5.271  SPAN-NOT-MEASURED

2.5.272  SQUELCHED

Clear the SQUELCHED Condition

2.5.273  SSM-DUS

2.5.274  SSM-FAIL

Clear the SSM-FAIL Alarm

2.5.275  SSM-LNC

2.5.276  SSM-OFF

Clear the SSM-OFF Condition

2.5.277  SSM-PRC

2.5.278  SSM-PRS

2.5.279  SSM-RES

2.5.280  SSM-SMC

2.5.281  SSM-ST2

2.5.282  SSM-ST3

2.5.283  SSM-ST3E

2.5.284  SSM-ST4

2.5.285  SSM-STU

Clear the SSM-STU Condition

2.5.286  SSM-TNC

2.5.287  SW-MISMATCH

Clear the SW-MISMATCH Condition

2.5.288  SWTOPRI

2.5.289  SWTOSEC

Clear the SWTOSEC Condition

2.5.290  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.5.291  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.5.292  SYNCLOSS

Clear the SYNCLOSS Alarm

2.5.293  SYNCPRI

Clear the SYNCPRI Alarm

2.5.294  SYNCSEC

Clear the SYNCSEC Alarm

2.5.295  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.5.296  SYSBOOT

2.5.297  TEMP-MISM

Clear the TEMP-MISM Condition

2.5.298  TIM

Clear the TIM Alarm

2.5.299  TIM-MON

Clear the TIM-MON Alarm

2.5.300  TIM-P

Clear the TIM-P Alarm

2.5.301  TIM-S

Clear the TIM-S Alarm

2.5.302  TRAIL-SIGNAL-FAIL

Clear the TRAIL-SIGNAL-FAIL Condition

2.5.303  UNC-WORD

Clear the UNC-WORD Condition

2.5.304  UNEQ-P

Clear the UNEQ-P Alarm

2.5.305  UNQUAL-PPM

Clear the UNQUAL-PPM Condition

2.5.306  UT-COMM-FAIL

Clear the UT-COMM-FAIL Alarm

2.5.307  UT-FAIL

Clear the UT-FAIL Alarm

2.5.308  VOA-DISABLED

Clear the VOA-DISABLED Condition

2.5.309  VOA-HDEG

Clear the VOA-HDEG Alarm

2.5.310  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.5.311  VOA-LDEG

Clear the VOA-LDEG Alarm

2.5.312  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.5.313  VOLT-MISM

Clear the VOLT-MISM Condition

2.5.314  WKSWPR (2R, EQPT, ESCON, FC, GE, ISC, OTS)

2.5.315  WKSWPR (TRUNK)

2.5.316  WTR (2R, ESCON, FC, GE, ISC)

2.5.317  WTR (TRUNK)

2.5.318  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  Node and Ring Identification, Change, Visibility, and Termination

Identify a BLSR Ring Name or Node ID Number

Change a BLSR Ring Name

Change a BLSR Node ID Number

Verify Node Visibility for Other Nodes

2.8.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Manual Switch Command

Initiate a 1:1 Card 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

Initiate a Lockout on a BLSR Protect Span

Clear a BLSR External Switching Command

2.8.3  CTC Card Resetting and Switching

Reset a Card in CTC

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

2.8.4  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.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node Section DCC Terminations

Clear an MXP, TXP, GE-XP, 10GE-XP, and ADM-10G Card Loopback Circuit

Verify or Create Node RS-DCC Terminations

Clear an STM-N Card XC Loopback Circuit

2.8.6  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

2.8.7  Interface Procedures

Replace the Alarm Interface Panel

Alarm Troubleshooting

---

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

—	HP-UNEQ (VCMON-HP)	OPWR-HFAIL (AOTS)
—	HP-UNEQ (VCTRM-HP)	OPWR-HFAIL (OCH)
AU-LOP (VCMON-HP)	I-HITEMP (NE)	OPWR-HFAIL (OMS)
AU-LOP (VCTRM-HP)	ILK-FAIL (TRUNK)	OPWR-HFAIL (OTS)
AUTOLSROFF (OCN)	IMPROPRMVL (EQPT)	OPWR-LFAIL (AOTS)
AWG-FAIL (OTS)	IMPROPRMVL (PPM)	OPWR-LFAIL (OCH-TERM)
AWG-OVERTEMP (OTS)	LOF (TRUNK)	OPWR-LFAIL (OCH)
BKUPMEMP (EQPT)	LOM (TRUNK)	OPWR-LFAIL (OMS)
CONTBUS-DISABLED (EQPT)	LOP-P (STSMON)	OPWR-LFAIL (OTS)
ENCAP-MISMATCH-P (POS)	LOP-P (STSTRM)	OTUK-LOF (TRUNK)
ENCAP-MISMATCH-P (STSTRM)	LOS (2R)	OTUK-TIM (TRUNK)
EQPT (AICI-AEP)	LOS (ESCON)	PORT-FAIL (OCH)
EQPT (AICI-AIE)	LOS (ISC)	RS-TIM (STMN)
EQPT-DIAG (EQPT)	LOS (OTS)	TIM (TRUNK)
EQPT (EQPT)	LOS (TRUNK)	TIM-P (STSTRM)
EQPT (PPM)	LOS-P (OCH)	TIM-S (OCN)
EQPT-MISS (FAN)	LOS-P (OMS)	UNEQ-P (STSMON)
FAN (FAN)	LOS-P (OTS)	UNEQ-P (STSTRM)
GAIN-HFAIL (AOTS)	LOS-P (TRUNK)	VOA-DISABLED (EQPT)
GAIN-LFAIL (AOTS)	LOS-RAMAN (OTS)	VOA-HFAIL (AOTS)
GE-OOSYNC (FC)	MEA (AIP)	VOA-HFAIL (OCH)
GE-OOSYNC (GE)	MEA (EQPT)	VOA-HFAIL (OMS)
GE-OOSYNC (ISC)	MEA (FAN)	VOA-HFAIL (OTS)
GE-OOSYNC (TRUNK)	MEA (PPM)	VOA-LFAIL (AOTS)
HITEMP (NE)	MFGMEM (AICI-AEP)	VOA-LFAIL (OCH)
HP-ENCAP-MISMATCH (VCTRM-HP)	MFGMEM (AICI-AIE)	VOA-LFAIL (OMS)
HP-PLM (VCMON-HP)	MFGMEM (BPLANE)	VOA-LFAIL (OTS)
HP-PLM (VCTRM-HP)	MFGMEM (FAN)	—
HP-TIM (VCMON-HP)	MFGMEM (PPM)	—

2.1.2  Major Alarms (MJ)

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

Table 2-2 Major DWDM Alarm List 

APSCNMIS (OCN)	GFP-LFD (CE100T)	ODUK-TIM-PM (TRUNK)
BAT-FAIL (PWR)	GFP-LFD (CE1000)	OUT-OF-SYNC (FC)
CARLOSS (EQPT)	GFP-LFD (CEMR)	OUT-OF-SYNC (GE)
CARLOSS (FC)	GFP-LFD (FCMR)	OUT-OF-SYNC (TRUNK)
CARLOSS (GE)	GFP-LFD (GFP-FAC)	PEER-NORESPONSE (EQPT)
CARLOSS (ISC)	GFP-LFD (ML100T)	PROV-MISMATCH (TRUNK)
CARLOSS (TRUNK)	GFP-LFD (ML1000)	PTIM (TRUNK)
DBOSYNC (NE)	GFP-LFD (MLMR)	PWR-PROT-ON (OTS)
DSP-COMM-FAIL (TRUNK)	GFP-LFD (POS)	RING-ID-MIS (OSC-RING)
DSP-FAIL (TRUNK)	GFP-UP-MISMATCH (CE100T)	SHELF-COMM-FAIL (SHELF)
DUP-SHELF-ID (SHELF)	GFP-UP-MISMATCH (CE1000)	SIGLOSS (ESCON)
EHIBATVG (PWR)	GFP-UP-MISMATCH (CEMR)	SIGLOSS (FC)
ELWBATVG (PWR)	GFP-UP-MISMATCH (FCMR)	SIGLOSS (GE)
FC-NO-CREDITS (FC)	GFP-UP-MISMATCH (GFP-FAC)	SIGLOSS (ISC)
FC-NO-CREDITS (TRUNK)	GFP-UP-MISMATCH (ML100T)	SIGLOSS (TRUNK)
FEC-MISM (TRUNK)	GFP-UP-MISMATCH (ML1000)	SYNCLOSS (FC)
GFP-CSF (CE100T)	GFP-UP-MISMATCH (MLMR)	SYNCLOSS (GE)
GFP-CSF (CE1000)	GFP-UP-MISMATCH (POS)	SYNCLOSS (ISC)
GFP-CSF (CEMR)	HIBATVG (PWR)	SYNCLOSS (TRUNK)
GFP-CSF (FCMR)	INVMACADR (AIP)	SYNCPRI (NE-SREF)
GFP-CSF (GFP-FAC)	LASERBIAS-FAIL (AOTS)	SYSBOOT (NE)
GFP-CSF (ML100T)	LWBATVG (PWR)	UT-COMM-FAIL (TRUNK)
GFP-CSF (ML1000)	MEA (SHELF)	UT-FAIL (TRUNK)
GFP-CSF (MLMR)	MEM-GONE (EQPT)	WVL-MISMATCH (TRUNK)

2.1.3  Minor Alarms (MN)

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

Table 2-3 Minor DWDM Alarm List 

—	HI-LASERBIAS (OCN)	LO-TXPOWER (ESCON)
—	HI-LASERBIAS (PPM)	LO-TXPOWER (FC)
AMPLI-INIT (AOTS)	HI-LASERBIAS (TRUNK)	LO-TXPOWER (GE)
APC-CORR-SKIPPED (AOTS)	HI-LASERTEMP (EQPT)	LO-TXPOWER (ISC)
APC-CORR-SKIPPED (OCH)	HI-LASERTEMP (OCN)	LO-TXPOWER (OCN)
APC-CORR-SKIPPED (OMS)	HI-LASERTEMP (PPM)	LO-TXPOWER (PPM)
APC-CORR-SKIPPED (OTS)	HI-RXPOWER (2R)	LO-TXPOWER (TRUNK)
APC-OUT-OF-RANGE (AOTS)	HI-RXPOWER (ESCON)	MEM-LOW (EQPT)
APC-OUT-OF-RANGE (OCH)	HI-RXPOWER (FC)	MS-EOC (STMN)
APC-OUT-OF-RANGE (OMS)	HI-RXPOWER (GE)	NON-CISCO-PPM (PPM)
APC-OUT-OF-RANGE (OTS)	HI-RXPOWER (ISC)	OPWR-HDEG (AOTS)
APS-INV-PRIM (OCN)	HI-RXPOWER (OCN)	OPWR-HDEG (OCH-TERM)
APS-PRIM-FAC (OCN)	HI-RXPOWER (TRUNK)	OPWR-HDEG (OCH)
APS-PRIM-SEC-MISM (OCN)	HITEMP (EQPT)	OPWR-HDEG (OMS)
APSB (OCN)	HI-TXPOWER (2R)	OPWR-HDEG (OTS)
APSC-IMP (OCN)	HI-TXPOWER (EQPT)	OPWR-LDEG (AOTS)
APSCDFLTK (OCN)	HI-TXPOWER (ESCON)	OPWR-LDEG (OCH-TERM)
APSCINCON (OCN)	HI-TXPOWER (FC)	OPWR-LDEG (OCH)
APSCM (OCN)	HI-TXPOWER (GE)	OPWR-LDEG (OMS)
APSIMP (OCN)	HI-TXPOWER (ISC)	OPWR-LDEG (OTS)
APSMM (OCN)	HI-TXPOWER (OCN)	OTUK-IAE (TRUNK)
AUTORESET (EQPT)	HI-TXPOWER (PPM)	PROTNA (EQPT)
AWG-DEG (OTS)	HI-TXPOWER (TRUNK)	PROV-MISMATCH (PPM)
BPV (BITS)	HP-TIM (VCMON-HP)	PWR-FAIL-A (EQPT)
CASETEMP-DEG (AOTS)	IS-ADJ-FAIL (OCN)	PWR-FAIL-B (EQPT)
CONTBUS-IO-A (CONTBUS-A) (EQPT)	IS-ADJ-FAIL (TRUNK)	PWR-FAIL-RET-A (EQPT)
CONTBUS-IO-B (CONTBUS-B) (EQPT)	LASERBIAS-DEG (AOTS)	PWR-FAIL-RET-B (EQPT)
DATAFLT (NE)	LASERBIAS-DEG (OTS)	RS-EOC (STMN)
DCU-LOSS-FAIL (OTS)	LASERTEMP-DEG (AOTS)	SFTWDOWN (EQPT)
DUP-IPADDR (NE)	LMP-FAIL (GE)	SH-IL-VAR-DEG-HIGH (OTS)
DUP-NODENAME (NE)	LMP-SD (GE)	SH-IL-VAR-DEG-LOW (OTS)
EOC (OCN)	LMP-SF (GE)	SNTP-HOST (NE)
EOC (TRUNK)	LOF (BITS)	SPANLEN-OUT-OF-RANGE (OTS)
EOC-L (OCN)	LO-LASERBIAS (EQPT)	SSM-FAIL (BITS)
EOC-L (TRUNK)	LO-LASERBIAS (OCN)	SSM-FAIL (TRUNK)
EXCCOL (EQPT)	LO-LASERBIAS (PPM)	SYNCPRI (EXT-SREF)
EXT (ENVALRM)	LO-LASERTEMP (EQPT)	SYNCSEC (EXT-SREF)
FAPS-CONFIG-MISMATCH (EQPT)	LO-LASERTEMP (OCN)	SYNCSEC (NE-SREF)
FEPRLF (OCN)	LO-LASERTEMP (PPM)	SYNCTHIRD (EXT-SREF)
FIBERTEMP-DEG (AOTS)	LO-RXPOWER (2R)	SYNCTHIRD (NE-SREF)
FP-LINK-LOSS (EQPT)	LO-RXPOWER (ESCON)	TIM-MON (TRUNK)
GAIN-HDEG (AOTS)	LO-RXPOWER (FC)	TIM-P (STSMON)
GAIN-LDEG (AOTS)	LO-RXPOWER (GE)	VOA-HDEG (AOTS)
GCC-EOC (TRUNK)	LO-RXPOWER (ISC)	VOA-HDEG (OCH)
HELLO (OCN)	LO-RXPOWER (OCN)	VOA-HDEG (OMS)
HELLO (TRUNK)	LO-RXPOWER (TRUNK)	VOA-HDEG (OTS)
HI-LASERBIAS (2R)	LOS (BITS)	VOA-LDEG (AOTS)
HI-LASERBIAS (EQPT)	LOS-O (OCH)	VOA-LDEG (OCH)
HI-LASERBIAS (ESCON)	LOS-O (OMS)	VOA-LDEG (OMS)
HI-LASERBIAS (FC)	LOS-O (OTS)	VOA-LDEG (OTS)
HI-LASERBIAS (GE)	LO-TXPOWER (2R)	—
HI-LASERBIAS (ISC)	LO-TXPOWER (EQPT)	—

2.1.4  NA Conditions

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

Table 2-4 NA DWDM Conditions List 

APC-DISABLED (OCH)	FORCED-REQ-SPAN (ISC)	SD-L (TRUNK)
APC-DISABLED (OMS)	FORCED-REQ-SPAN (OCN)	SD-P (STSMON)
APC-DISABLED (OTS)	FORCED-REQ-SPAN (OTS)	SD-P (STSTRM)
APC-DISABLED (SHELF)	FORCED-REQ-SPAN (TRUNK)	SF (TRUNK)
APC-END (NE)	FRCDSWTOINT (NE-SREF)	SFBER-EXCEED-HO (VCMON-HP)
APC-WRONG-GAIN (AOTS)	FRNGSYNC (NE-SREF)	SFBER-EXCEED-HO (VCTRM-HP)
ALS (2R)	FRCDSWTOPRI (EXT-SREF)	SFBER-EXCEED-HO (VCTRM-LP)
ALS (AOTS)	FRCDSWTOPRI (NE-SREF)	SF-L (TRUNK)
ALS (ESCON)	FRCDSWTOSEC (EXT-SREF)	SF-P (STSMON)
ALS (FC)	FRCDSWTOSEC (NE-SREF)	SF-P (STSTRM)
ALS (GE)	FRCDSWTOTHIRD (EXT-SREF)	SHUTTER-OPEN (OTS)
ALS (ISC)	FRCDSWTOTHIRD (NE-SREF)	SPAN-NOT-MEASURED (OTS)
ALS (OCN)	FSTSYNC (NE-SREF)	SQUELCHED (2R)
ALS (TRUNK)	FTA-MISMATCH (EQPT)	SQUELCHED (ESCON)
ALS-DISABLED (EQPT)	HI-CCVOLT (BITS)	SQUELCHED (FC)
APC-DISABLED (AOTS)	HLDOVRSYNC (NE-SREF)	WKSWPR (FC)
APC-DISABLED (EQPT)	HP-DEG (VCMON-HP)	WKSWPR (GE)
APC-DISABLED (NE)	HP-DEG (VCTRM-HP)	WKSWPR (ISC)
APS-PRIM-FAC (OCN)	HP-EXC (VCMON-HP)	WKSWPR (OTS)
AS-CMD (2R)	HP-EXC (VCTRM-HP)	WTR (2R)
AS-CMD (AOTS)	INHSWPR (EQPT)	WTR (EQPT)
AS-CMD (BPLANE)	INHSWWKG (EQPT)	WTR (ESCON)
AS-CMD (EQPT)	INTRUSION-PSWD (NE)	WTR (FC)
AS-CMD (ESCON)	LAN-POL-REV (NE)	WTR (GE)
AS-CMD (FC)	LASER-APR (AOTS)	WTR (ISC)
AS-CMD (GE)	LASER-APR (OTS)	WTR (TRUNK)
AS-CMD (ISC)	LMP-UNALLOC (GE)	SSM-LNC (BITS)
AS-CMD (NE)	LOCKOUT-REQ (2R)	SSM-LNC (NE-SREF)
AS-CMD (OCH)	LOCKOUT-REQ (EQPT)	SSM-LNC (TRUNK)
AS-CMD (OCN)	LOCKOUT-REQ (ESCON)	SSM-OFF (BITS)
AS-CMD (OMS)	LOCKOUT-REQ (FC)	SSM-OFF (TRUNK)
AS-CMD (OTS)	LOCKOUT-REQ (GE)	SSM-PRC (BITS)
AS-CMD (PPM)	LOCKOUT-REQ (ISC)	SQUELCHED (GE)
AS-CMD (PWR)	LOCKOUT-REQ (OCN)	SQUELCHED (ISC)
AS-CMD (SHELF)	LOCKOUT-REQ (OTS)	SQUELCHED (OCN)
AS-CMD (TRUNK)	LOCKOUT-REQ (STSMON)	SQUELCHED (TRUNK)
AS-MT (2R)	LOCKOUT-REQ (TRUNK)	SSM-DUS (BITS)
AS-MT (AOTS)	LPBKCRS (STSMON)	SSM-DUS (TRUNK)
AS-MT (EQPT)	LPBKFACILITY (ESCON)	SSM-PRC (NE-SREF)
AS-MT (ESCON)	LPBKFACILITY (FC)	SSM-PRC (TRUNK)
AS-MT (FC)	LPBKFACILITY (GE)	SSM-PRS (BITS)
AS-MT (GE)	LPBKFACILITY (ISC)	SSM-PRS (NE-SREF)
AS-MT (ISC)	LPBKFACILITY (TRUNK)	SSM-PRS (TRUNK)
AS-MT (OCH)	LPBKTERMINAL (ESCON)	SSM-RES (BITS)
AS-MT (OCN)	LPBKTERMINAL (FC)	SSM-RES (NE-SREF)
AS-MT (OMS)	LPBKTERMINAL (GE)	SSM-RES (TRUNK)
AS-MT (OTS)	LPBKTERMINAL (ISC)	SSM-SDH-TN (BITS)
AS-MT (PPM)	LPBKTERMINAL (TRUNK)	SSM-SDH-TN (NE-SREF)
AS-MT (SHELF)	MAN-REQ (EQPT)	SSM-SDH-TN (TRUNK)
AS-MT (TRUNK)	MANRESET (EQPT)	SSM-SETS (BITS)
AS-MT-OOG (STSTRM)	MANSWTOINT (NE-SREF)	SSM-SETS (NE-SREF)
AUD-LOG-LOSS (NE)	MANSWTOPRI (EXT-SREF)	SSM-SETS (TRUNK)
AUD-LOG-LOW (NE)	MANSWTOPRI (NE-SREF)	SSM-SMC (BITS)
AUTOSW-LOP (STSMON)	MANSWTOSEC (EXT-SREF)	SSM-SMC (NE-SREF)
AUTOSW-LOP-SNCP (VCMON-HP)	MANSWTOSEC (NE-SREF)	SSM-SMC (TRUNK)
AUTOSW-LOP-SNCP (VCMON-LP)	MANSWTOTHIRD (EXT-SREF)	SSM-ST2 (BITS)
AUTOSW-PDI-SNCP (VCMON-HP)	MANSWTOTHIRD (NE-SREF)	SSM-ST2 (NE-SREF)
AUTOSW-PDI (STSMON)	MANUAL-REQ-SPAN (2R)	SSM-ST2 (TRUNK)
AUTOSW-SDBER (STSMON)	MANUAL-REQ-SPAN (ESCON)	SSM-ST3 (BITS)
AUTOSW-SFBER (STSMON)	MANUAL-REQ-SPAN (FC)	SSM-ST3 (NE-SREF)
AUTOSW-SDBER-SNCP (VCMON-HP)	MANUAL-REQ-SPAN (GE)	SSM-ST3 (TRUNK)
AUTOSW-SFBER-SNCP (STSMON)	MANUAL-REQ-SPAN (ISC)	SSM-ST3E (BITS)
AUTOSW-UNEQ (STSMON)	MANUAL-REQ-SPAN (OCN)	SSM-ST3E (NE-SREF)
AUTOSW-UNEQ-SNCP (VCMON-HP)	MANUAL-REQ-SPAN (OTS)	SSM-ST3E (TRUNK)
AUTOSW-UNEQ-SNCP (VCMON-LP)	MANUAL-REQ-SPAN (TRUNK)	SSM-ST4 (BITS)
AWG-WARM-UP (OTS)	MS-DEG (STM1E)	SSM-ST4 (NE-SREF)
CHANLOSS (OCN)	MS-DEG (STMN)	SSM-ST4 (TRUNK)
CLDRESTART (EQPT)	MS-EOC (STMN)	SSM-STU (BITS)
CTNEQPT-MISMATCH (EQPT)	MS-EXC (STM1E)	SSM-STU (NE-SREF)
ETH-LINKLOSS (NE)	MS-EXC (STMN)	SSM-STU (TRUNK)
FAILTOSW (2R)	MT-OCHNC (OTS)	SSM-TNC (BITS)
FAILTOSW (EQPT)	OCHNC-INC (OCHNC-CONN)	SSM-TNC (NE-SREF)
FAILTOSW (ESCON)	OCHTERM-INC (OCH-TERM)	SSM-TNC (TRUNK)
FAILTOSW (GE)	ODUK-SD-PM (TRUNK)	SW-MISMATCH (EQPT)
FAILTOSW (FC)	ODUK-SF-PM (TRUNK)	SWTOPRI (EXT-SREF)
FAILTOSW (ISC)	OPEN-SLOT (EQPT)	SWTOPRI (NE-SREF)
FAILTOSW (OCN)	OSRION (AOTS)	SWTOSEC (EXT-SREF)
FAILTOSW (OTS)	OSRION (OTS)	SWTOSEC (NE-SREF)
FAILTOSW (TRUNK)	OTUK-SD (TRUNK)	SWTOTHIRD (EXT-SREF)
FAILTOSW-HO (VCMON-HP)	OTUK-SF (TRUNK)	TRAIL-SIGNAL-FAIL (OCH)
FAILTOSW-PATH (STSMON)	OUT-OF-SYNC (ISC)	SWTOTHIRD (NE-SREF)
FAPS (TRUNK)	PARAM-MISM (AOTS)	SYNC-FREQ (BITS)
FDI (OCH-TERM)	PARAM-MISM (OCH)	SYNC-FREQ (TRUNK)
FDI (OCH)	PARAM-MISM (OCH-TERM)	TEMP-MISM (NE)
FE-FRCDWKSWBK-SPAN (OCN)	PARAM-MISM (OMS)	TRAIL-SIGNAL-FAIL (TRUNK)
FORCED-REQ (STSMON)	PARAM-MISM (OTS)	UNC-WORD (TRUNK)
FE-FRCDWKSWPR-SPAN (OCN)	PDI-P (STSMON)	VOLT-MISM (PWR)
FE-MANWKSWBK-SPAN (OCN)	PDI-P (STSTRM)	WKSWPR (2R)
FE-MANWKSWPR-SPAN (OCN)	PMI (OMS)	WKSWPR (EQPT)
FORCED-REQ (EQPT)	PMI (OTS)	WKSWPR (ESCON)
FORCED-REQ (POS)	RLS (OTS)	WKSWPR (FC)
FORCED-REQ-SPAN (2R)	RUNCFG-SAVENEED (EQPT)	WKSWPR (GE)
FORCED-REQ-SPAN (ESCON)	SD (TRUNK)	WKSWPR (ISC)
FORCED-REQ-SPAN (FC)	SD-L (OCN)	WKSWPR (OTS)
FORCED-REQ-SPAN (GE)	SD-L (OCN)	—

2.1.5  NR Conditions

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

Table 2-5 NR DWDM Conditions List 

AIS (BITS)	ERFI-P-CONN (STSTRM)	ODUK-AIS-PM (TRUNK)
AIS (TRUNK)	ERFI-P-SRVR (STSMON)	ODUK-BDI-PM (TRUNK)
AIS-L (OCN)	ERFI-P-SRVR (STSTRM)	ODUK-LCK-PM (TRUNK)
AIS-L (TRUNK)	HP-RFI (VCMON-HP)	ODUK-OCI-PM (TRUNK)
AIS-P (STSMON)	MS-AIS (STMN)	OTUK-AIS (TRUNK)
AIS-P (STSTRM)	MS-AIS (STM1E)	OTUK-BDI (TRUNK)
AU-AIS (VCTRM-HP)	MS-RFI (STMN)	RFI (TRUNK)
AU-AIS (VCMON-HP)	MS-RFI (STM1E)	RFI-L (OCN)
AUTOSW-AIS (STSMON)	ODUK-1-AIS-PM (TRUNK)	RFI-L (TRUNK)
AUTOSW-AIS-SNCP (VCMON-HP)	ODUK-2-AIS-PM (TRUNK)	RFI-P (STSMON)
AUTOSW-AIS-SNCP (VCMON-LP)	ODUK-3-AIS-PM (TRUNK)	RFI-P (STSTRM)
ERFI-P-CONN (STSMON)	ODUK-4-AIS-PM (TRUNK)	UNQUAL-PPM

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 

—	GFP-CSF (CE1000)	ODUK-TIM-PM (TRUNK)
—	GFP-CSF (CEMR)	OPEN-SLOT (EQPT)
—	GFP-CSF (FCMR)	OPWR-HDEG (AOTS)
—	GFP-CSF (GFP-FAC)	OPWR-HDEG (OCH)
AIS (BITS)	GFP-CSF (ML100T)	OPWR-HDEG (OCH-TERM)
AIS (TRUNK)	GFP-CSF (ML1000)	OPWR-HDEG (OMS)
AIS-L (OCN)	GFP-CSF (MLMR)	OPWR-HDEG (OTS)
AIS-L (TRUNK)	GFP-LFD (CE100T)	OPWR-HFAIL (AOTS)
AIS-P (STSMON)	GFP-LFD (CE1000)	OPWR-HFAIL (OCH)
AIS-P (STSTRM)	GFP-LFD (CEMR)	OPWR-HFAIL (OMS)
ALS (2R)	GFP-LFD (FCMR)	OPWR-HFAIL (OTS)
ALS (AOTS)	GFP-LFD (GFP-FAC)	OPWR-LDEG (AOTS)
ALS (ESCON)	GFP-LFD (ML100T)	OPWR-LDEG (OCH)
ALS (FC)	GFP-LFD (ML1000)	OPWR-LDEG (OCH-TERM)
ALS (GE)	GFP-LFD (MLMR)	OPWR-LDEG (OMS)
ALS (ISC)	GFP-LFD (POS)	OPWR-LDEG (OTS)
ALS (OCN)	GFP-UP-MISMATCH (CE100T)	OPWR-LFAIL (AOTS)
ALS (TRUNK)	GFP-UP-MISMATCH (CE1000)	OPWR-LFAIL (OCH)
ALS-DISABLED (EQPT)	GFP-UP-MISMATCH (CEMR)	OPWR-LFAIL (OCH-TERM)
AMPLI-INIT (AOTS)	GFP-UP-MISMATCH (FCMR)	OPWR-LFAIL (OMS)
APC-CORR-SKIPPED (AOTS)	GFP-UP-MISMATCH (GFP-FAC)	OPWR-LFAIL (OTS)
APC-CORR-SKIPPED (OCH)	GFP-UP-MISMATCH (ML100T)	OSRION (AOTS)
APC-CORR-SKIPPED (OMS)	GFP-UP-MISMATCH (ML1000)	OSRION (OTS)
APC-CORR-SKIPPED (OTS)	GFP-UP-MISMATCH (MLMR)	OTUK-AIS (TRUNK)
APC-DISABLED (AOTS)	GFP-UP-MISMATCH (POS)	OTUK-BDI (TRUNK)
APC-DISABLED (EQPT)	HELLO (TRUNK)	OTUK-IAE (TRUNK)
APC-DISABLED (NE)	HIBATVG (PWR)	OTUK-LOF (TRUNK)
APC-DISABLED (OCH)	HI-CCVOLT (BITS)	OTUK-SD (TRUNK)
APC-DISABLED (OMS)	HI-LASERBIAS (2R)	OTUK-SF (TRUNK)
APC-DISABLED (OTS)	HI-LASERBIAS (EQPT)	OTUK-TIM (TRUNK)
APC-DISABLED (SHELF)	HI-LASERBIAS (ESCON)	OUT-OF-SYNC (FC)
APC-END (NE)	HI-LASERBIAS (FC)	OUT-OF-SYNC (GE)
APC-OUT-OF-RANGE (AOTS)	HI-LASERBIAS (GE)	OUT-OF-SYNC (ISC)
APC-OUT-OF-RANGE (OCH)	HI-LASERBIAS (ISC)	OUT-OF-SYNC (TRUNK)
APC-OUT-OF-RANGE (OMS)	HI-LASERBIAS (OCN)	PARAM-MISM (AOTS)
APC-OUT-OF-RANGE (OTS)	HI-LASERBIAS (PPM)	PARAM-MISM (OCH)
APC-WRONG-GAIN (AOTS)	HI-LASERBIAS (TRUNK)	PARAM-MISM (OCH-TERM)
APS-INV-PRIM (OCN)	HI-LASERTEMP (EQPT)	PARAM-MISM (OMS)
APS-PRIM-FAC (OCN)	HI-LASERTEMP (OCN)	PARAM-MISM (OTS)
APS-PRIM-SEC-MISM (OCN)	HI-LASERTEMP (PPM)	PDI-P (STSMON)
APSB (OCN)	HI-RXPOWER (2R)	PDI-P (STSTRM)
APSC-IMP (OCN)	HI-RXPOWER (ESCON)	PEER-NORESPONSE (EQPT)
APSCDFLTK (OCN)	HI-RXPOWER (FC)	PM-TCA
APSCINCON (OCN)	HI-RXPOWER (GE)	PMI (OMS)
APSCM (OCN)	HI-RXPOWER (ISC)	PMI (OTS)
APSCNMIS (OCN)	HI-RXPOWER (OCN)	PORT-FAIL (OCH)
APSIMP (OCN)	HI-RXPOWER (TRUNK)	PROTNA (EQPT)
APSMM (OCN)	HITEMP (EQPT)	PROV-MISMATCH (PPM)
AS-CMD (2R)	HITEMP (NE)	PROV-MISMATCH (TRUNK)
AS-CMD (AOTS)	HI-TXPOWER (2R)	PTIM (TRUNK)
AS-CMD (BPLANE)	HI-TXPOWER (EQPT)	PWR-FAIL-A (EQPT)
AS-CMD (EQPT)	HI-TXPOWER (ESCON)	PWR-FAIL-B (EQPT)
AS-CMD (ESCON)	HI-TXPOWER (FC)	PWR-FAIL-RET-A (EQPT)
AS-CMD (FC)	HI-TXPOWER (GE)	PWR-FAIL-RET-B (EQPT)
AS-CMD (GE)	HI-TXPOWER (ISC)	PWR-PROT-ON (OTS)
AS-CMD (ISC)	HI-TXPOWER (OCN)	RFI (TRUNK)
AS-CMD (NE)	HI-TXPOWER (PPM)	RFI-L (OCN)
AS-CMD (OCH)	HI-TXPOWER (TRUNK)	RFI-P (STSMON)
AS-CMD (OCN)	HLDOVRSYNC (NE-SREF)	RFI-P (STSTRM)
AS-CMD (OMS)	HP-DEG (VCMON-HP)	RLS (OTS)
AS-CMD (OTS)	HP-DEG (VCTRM-HP)	RMON-ALARM
AS-CMD (PPM)	HP-ENCAP-MISMATCH (VCTRM-HP)	RMON-RESET
AS-CMD (PWR)	HP-EXC (VCMON-HP)	RING-ID-MIS (OSC-RING)
AS-CMD (SHELF)	HP-EXC (VCTRM-HP)	RS-EOC (STMN)
AS-CMD (TRUNK)	HP-PLM (VCMON-HP)	RS-TIM (STMN)
AS-MT-OOG (STSTRM)	HP-PLM (VCTRM-HP)	RUNCFG-SAVENEED (EQPT)
AS-MT (2R)	HP-RFI (VCMON-HP)	SD (TRUNK)
AS-MT (AOTS)	HP-TIM (VCMON-HP)	SD-L (OCN)
AS-MT (EQPT)	HP-UNEQ (VCMON-HP)	SD-P (STSMON)
AS-MT (ESCON)	HP-UNEQ (VCTRM-HP)	SD-P (STSTRM)
AS-MT (FC)	I-HITEMP (NE)	SF (TRUNK)
AS-MT (GE)	ILK-FAIL (TRUNK)	SF-L (TRUNK)
AS-MT (ISC)	IMPROPRMVL (EQPT)	SF-P (STSMON)
AS-MT (OCH)	IMPROPRMVL (PPM)	SF-P (STSTRM)
AS-MT (OCN)	INTRUSION-PSWD (NE)	SFBER-EXCEED-HO (VCMON-HP)
AS-MT (OMS)	INVMACADR (AIP)	SFBER-EXCEED-HO (VCTRM-HP)
AS-MT (OTS)	INHSWPR (EQPT)	SFBER-EXCEED-HO (VCTRM-LP)
AS-MT (PPM)	INHSWWKG (EQPT)	SFTWDOWN (EQPT)
AS-MT (SHELF)	ISIS-ADJ-FAIL (OCN)	SHELF-COMM-FAIL (SHELF)
AS-MT (TRUNK)	ISIS-ADJ-FAIL (TRUNK)	SH-IL-VAR-DEG-HIGH (OTS)
AU-AIS (VCTRM-HP)	LAN-POL-REV (NE)	SH-IL-VAR-DEG-LOW (OTS)
AU-AIS (VCMON-HP)	LASEREOL (OCN)	SHUTTER-OPEN (OTS)
AU-LOP (VCTRM-HP)	LASER-APR (AOTS)	SIGLOSS (ESCON)
AU-LOP (VCMON-HP)	LASER-APR (OTS)	SIGLOSS (FC)
AUD-LOG-LOSS (NE)	LASERBIAS-DEG (AOTS)	SIGLOSS (GE)
AUD-LOG-LOW (NE)	LASERBIAS-DEG (OTS)	SIGLOSS (ISC)
AUTORESET (EQPT)	LASERBIAS-FAIL (AOTS)	SIGLOSS (TRUNK)
AUTOLSROFF (OCN)	LASERTEMP-DEG (AOTS)	SNTP-HOST (NE)
AUTOSW-AIS (STSMON)	LMP-FAIL (GE)	SPANLEN-OUT-OF-RANGE (OTS)
AUTOSW-AIS-SNCP (VCMON-HP)	LMP-SD (GE)	SPAN-NOT-MEASURED (OTS)
AUTOSW-AIS-SNCP (VCMON-LP)	LMP-SF (GE)	SQUELCHED (2R)
AUTOSW-LOP (STSMON)	LMP-UNALLOC (GE)	SQUELCHED (ESCON)
AUTOSW-LOP-SNCP (VCMON-HP)	LOCKOUT-REQ (2R)	SQUELCHED (FC)
AUTOSW-LOP-SNCP (VCMON-LP)	LOCKOUT-REQ (EQPT)	SQUELCHED (GE)
AUTOSW-PDI (STSMON)	LOCKOUT-REQ (ESCON)	SQUELCHED (ISC)
AUTOSW-PDI-SNCP (VCMON-HP)	LOCKOUT-REQ (FC)	SQUELCHED (OCN)
AUTOSW-SDBER (STSMON)	LOCKOUT-REQ (GE)	SQUELCHED (TRUNK)
AUTOSW-SDBER-SNCP (VCMON-HP)	LOCKOUT-REQ (ISC)	SSM-DUS (BITS)
AUTOSW-SFBER (STSMON)	LOCKOUT-REQ (OTS)	SSM-DUS (TRUNK)
AUTOSW-SFBER-SNCP (STSMON)	LOCKOUT-REQ (TRUNK)	SSM-FAIL (BITS)
AUTOSW-UNEQ (STSMON)	LOF (BITS)	SSM-FAIL (TRUNK)
AUTOSW-UNEQ-SNCP (VCMON-HP)	LOF (TRUNK)	SSM-LNC (BITS)
AUTOSW-UNEQ-SNCP (VCMON-LP)	LO-LASERBIAS (EQPT)	SSM-LNC (NE-SREF)
AWG-DEG (OTS)	LO-LASERBIAS (OCN)	SSM-LNC (TRUNK)
AWG-FAIL (OTS)	LO-LASERBIAS (PPM)	SSM-OFF (BITS)
AWG-OVERTEMP (OTS)	LO-LASERTEMP (EQPT)	SSM-OFF (TRUNK)
AWG-WARM-UP (OTS)	LO-LASERTEMP (OCN)	SSM-PRC (BITS)
BAT-FAIL (PWR)	LO-LASERTEMP (PPM)	SSM-PRC (NE-SREF)
BKUPMEMP (EQPT)	LOM (TRUNK)	SSM-PRC (TRUNK)
BPV (BITS)	LOP-P (TRUNK)	SSM-PRS (BITS)
CARLOSS (EQPT)	LOP-P (OCH)	SSM-PRS (NE-SREF)
CARLOSS (FC)	LOP-P (OMS)	SSM-PRS (TRUNK)
CARLOSS (GE)	LOP-P (OTS)	SSM-RES (BITS)
CARLOSS (ISC)	LO-RXPOWER (2R)	SSM-RES (NE-SREF)
CARLOSS (TRUNK)	LO-RXPOWER (ESCON)	SSM-RES (TRUNK)
CASETEMP-DEG (AOTS)	LO-RXPOWER (FC)	SSM-SDH-TN (BITS)
CHANLOSS (OCN)	LO-RXPOWER (GE)	SSM-SDH-TN (NE-SREF)
CLDRESTART (EQPT)	LO-RXPOWER (ISC)	SSM-SDH-TN (TRUNK)
CONTBUS-DISABLED (EQPT)	LO-RXPOWER (OCN)	SSM-SETS (BITS)
CONTBUS-IO-A (CONTBUS-A) (EQPT)	LO-RXPOWER (TRUNK)	SSM-SETS (NE-SREF)
CONTBUS-IO-B (CONTBUS-B) (EQPT)	LOS (2R)	SSM-SETS (TRUNK)
CTNEQPT-MISMATCH (EQPT)	LOS (BITS)	SSM-SMC (BITS)
DATAFLT (NE)	LOS (ESCON)	SSM-SMC (NE-SREF)
DBOSYNC (NE)	LOS (ISC)	SSM-SMC (TRUNK)
DCU-LOSS-FAIL (OTS)	LOS (OTS)	SSM-ST2 (BITS)
DSP-COMM-FAIL (TRUNK)	LOS (TRUNK)	SSM-ST2 (NE-SREF)
DSP-FAIL (TRUNK)	LOS-O (OCH)	SSM-ST2 (TRUNK)
DUP-IPADDR (NE)	LOS-O (OMS)	SSM-ST3 (BITS)
DUP-NODENAME (NE)	LOS-O (OTS)	SSM-ST3 (NE-SREF)
DUP-SHELF-ID (SHELF)	LOS-P (OCH)	SSM-ST3 (TRUNK)
EHIBATVG (PWR)	LOS-P (OMS)	SSM-ST3E (BITS)
ELWBATVG (PWR)	LOS-P (OTS)	SSM-ST3E (NE-SREF)
ENCAP-MISMATCH-P (STSTRM)	LOS-P (TRUNK)	SSM-ST3E (TRUNK)
ENCAP-MISMATCH-P (POS)	LOS-RAMAN (OTS)	SSM-ST4 (BITS)
EOC (OCN)	LO-TXPOWER (2R)	SSM-ST4 (NE-SREF)
EOC (TRUNK)	LO-TXPOWER (EQPT)	SSM-ST4 (TRUNK)
EOC-L (OCN)	LO-TXPOWER (ESCON)	SSM-STU (BITS)
EOC-L (TRUNK)	LO-TXPOWER (FC)	SSM-STU (NE-SREF)
ERFI-P-CONN (STSMON)	LO-TXPOWER (GE)	SSM-STU (TRUNK)
ERFI-P-CONN (STSTRM)	LO-TXPOWER (ISC)	SSM-TNC (BITS)
ERFI-P-SRVR (STSMON)	LO-TXPOWER (OCN)	SSM-TNC (NE-SREF)
ERFI-P-SRVR (STSTRM)	LO-TXPOWER (PPM)	SSM-TNC (TRUNK)
EQPT (AICI-AEP)	LO-TXPOWER (TRUNK)	SW-MISMATCH (EQPT)
EQPT (AICI-AIE)	LPBKCRS (STSMON)	SWTOPRI (EXT-SREF)
EQPT (EQPT)	LPBKFACILITY (ESCON)	SWTOPRI (NE-SREF)
EQPT (PPM)	LPBKFACILITY (FC)	SWTOSEC (EXT-SREF)
EQPT-DIAG (EQPT)	LPBKFACILITY (GE)	SWTOSEC (NE-SREF)
EQPT-MISS (FAN)	LPBKFACILITY (ISC)	SWTOTHIRD (EXT-SREF)
ETH-LINKLOSS (NE)	LPBKFACILITY (TRUNK)	SWTOTHIRD (NE-SREF)
EXCCOL (EQPT)	LPBKTERMINAL (ESCON)	SYNC-FREQ (BITS)
EXT (ENVALRM)	LPBKTERMINAL (FC)	SYNC-FREQ (TRUNK)
FAILTOSW (2R)	LPBKTERMINAL (GE)	SYNCLOSS (FC)
FAILTOSW (EQPT)	LPBKTERMINAL (ISC)	SYNCLOSS (GE)
FAILTOSW (ESCON)	LPBKTERMINAL (TRUNK)	SYNCLOSS (ISC)
FAILTOSW (FC)	LWBATVG (PWR)	SYNCLOSS (TRUNK)
FAILTOSW (GE)	MAN-REQ (EQPT)	SYNCPRI (EXT-SREF)
FAILTOSW (ISC)	MANRESET (EQPT)	SYNCPRI (NE-SREF)
FAILTOSW (OCN)	MANSWTOINT (NE-SREF)	SYNCSEC (EXT-SREF)
FAILTOSW (OTS)	MANSWTOPRI (EXT-SREF)	SYNCSEC (NE-SREF)
FAILTOSW (TRUNK)	MANSWTOPRI (NE-SREF)	SYNCTHIRD (EXT-SREF)
FAILTOSW-HO (STSMON)	MANSWTOSEC (EXT-SREF)	SYNCTHIRD (NE-SREF)
FAILTOSW-PATH (STSMON)	MANSWTOSEC (NE-SREF)	SYSBOOT (NE)
FAN (FAN)	MANSWTOTHIRD (EXT-SREF)	TEMP-MISM (NE)
FAPS (TRUNK)	MANSWTOTHIRD (NE-SREF)	TIM (TRUNK)
FAPS-CONFIG-MISMATCH (EQPT)	MANUAL-REQ-SPAN (2R)	TIM-MON (TRUNK)
FC-NO-CREDITS (FC)	MANUAL-REQ-SPAN (ESCON)	TIM-P (TRUNK)
FC-NO-CREDITS (TRUNK)	MANUAL-REQ-SPAN (FC)	TIM-S (TRUNK)
FDI (OCH)	MANUAL-REQ-SPAN (GE)	TRAIL-SIGNAL-FAIL (OCH)
FDI (OCH-TERM)	MANUAL-REQ-SPAN (ISC)	TRAIL-SIGNAL-FAIL (TRUNK)
FE-FRCDWKSWBK-SPAN (OCN)	MANUAL-REQ-SPAN (OCN)	UNC-WORD (TRUNK)
FE-FRCDWKSWPR-SPAN (OCN)	MANUAL-REQ-SPAN (OTS)	UNEQ-P (STSMON, STSTRM)
FE-MANWKSWBK-SPAN (OCN)	MANUAL-REQ-SPAN (TRUNK)	UNQUAL-PPM (PPM)
FE-MANWKSWPR-SPAN (OCN)	MANWKSWBK-NO-TRFSW (OCN)	UT-COMM-FAIL (TRUNK)
FEC-MISM (TRUNK)	MANWKSWPR-NO-TRFSW (OCN)	UT-FAIL (TRUNK)
FEPRLF (OCN)	MEA (AIP)	VOA-DISABLED (EQPT)
FIBERTEMP-DEG (AOTS)	MEA (EQPT)	VOA-HDEG (AOTS)
FORCED-REQ (EQPT)	MEA (FAN)	VOA-HDEG (OCH)
FORCED-REQ (STSMON)	MEA (PPM)	VOA-HDEG (OMS)
FORCED-REQ (POS)	MEA (SHELF)	VOA-HDEG (OTS)
FORCED-REQ-SPAN (2R)	MEM-GONE (EQPT)	VOA-HFAIL (AOTS)
FORCED-REQ-SPAN (ESCON)	MEM-LOW (EQPT)	VOA-HFAIL (OCH)
FORCED-REQ-SPAN (FC)	MFGMEM (AICI-AEP)	VOA-HFAIL (OMS)
FORCED-REQ-SPAN (GE)	MFGMEM (AICI-AIE)	VOA-HFAIL (OTS)
FORCED-REQ-SPAN (ISC)	MFGMEM (AIP)	VOA-LDEG (AOTS)
FORCED-REQ-SPAN (OCN)	MFGMEM (BPLANE)	VOA-LDEG (OCH)
FORCED-REQ-SPAN (OTS)	MFGMEM (FAN)	VOA-LDEG (OMS)
FORCED-REQ-SPAN (TRUNK)	MFGMEM (PPM)	VOA-LDEG (OTS)
FP-LINK-LOSS (EQPT)	MS-AIS (STMN)	VOA-LFAIL (AOTS)
FRCDSWTOINT (NE-SREF)	MS-AIS (STM1E)	VOA-LFAIL (OCH)
FRCDSWTOPRI (EXT-SREF)	MS-DEG (STMN)	VOA-LFAIL (OMS)
FRCDSWTOPRI (NE-SREF)	MS-DEG (STM1E)	VOA-LFAIL (OTS)
FRCDSWTOSEC (EXT-SREF)	MS-EOC (STMN)	VOLT-MISM (PWR)
FRCDSWTOSEC (NE-SREF)	MS-EXC (STMN)	WKSWBK (EQPT)
FRCDSWTOTHIRD (EXT-SREF)	MS-EXC (STM1E)	WKSWBK (OCN)
FRCDSWTOTHIRD (NE-SREF)	MS-RFI (STMN)	WKSWBK (OTS)
FRCDWKSWBK-NO-TRFSW (OCN)	MS-RFI (STM1E)	WKSWPR (2R)
FRCDWKSWPR-NO-TRFSW (OCN)	MT-OCHNC (OTS)	WKSWPR (EQPT)
FRNGSYNC (NE-SREF)	NON-CISCO-PPM (PPM)	WKSWPR (ESCON)
FSTSYNC (NE-SREF)	OCHNC-INC (OCHNC-CONN)	WKSWPR (FC)
FTA-MISMATCH (EQPT)	OCHTERM-INC (OCH-TERM)	WKSWPR (GE)
GAIN-HDEG (AOTS)	ODUK-1-AIS-PM (TRUNK)	WKSWPR (ISC)
GAIN-HFAIL (AOTS)	ODUK-2-AIS-PM (TRUNK)	WKSWPR (OTS)
GAIN-LDEG (AOTS)	ODUK-3-AIS-PM (TRUNK)	WORK-QUEUE-FULL (EQPT)
GAIN-LFAIL (AOTS)	ODUK-4-AIS-PM (TRUNK)	WTR (2R)
GCC-EOC (TRUNK)	ODUK-AIS-PM (TRUNK)	WTR (EQPT)
GE-OOSYNC (FC)	ODUK-BDI-PM (TRUNK)	WTR (ESCON)
GE-OOSYNC (GE)	ODUK-LCK-PM (TRUNK)	WTR (FC)
GE-OOSYNC (ISC)	ODUK-OCI-PM (TRUNK)	WTR (GE)
GE-OOSYNC (TRUNK)	ODUK-SD-PM (TRUNK)	WTR (ISC)
GFP-CSF (CE100T)	ODUK-SF-PM (TRUNK)	WTR (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.
AIP	Alarm Interface Panel.
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_XP, 10GE_XP, ADM-10G, and OTU2_XP.
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, GE-XP, 10GE-XP, ADM-10G, and OTU2_XP.
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.
OCH-TERM	The optical channel termination node, referring to 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.
SHELF	The shelf assembly.
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 8.5 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)	GE: SQUELCHED (NA)	POS: ENCAP-MISMATCH-P (CR)
2R: AS-CMD (NA)	GE: SYNCLOSS (MJ)	POS: FORCED-REQ (NA)
2R: AS-MT (NA)	GE: WKSWPR (NA)	POS: GFP-CSF (MJ)
2R: FAILTOSW (NA)	GE: WTR (NA)	POS: GFP-LFD (MJ)
2R: FORCED-REQ-SPAN (NA)	GFP-FAC: GFP-CSF (MJ)	PPM: AS-CMD (NA)
2R: HI-LASERBIAS (MN)	GFP-FAC: GFP-LFD (MJ)	PPM: AS-MT (NA)
2R: HI-RXPOWER (MN)	GFP-FAC: GFP-UP-MISMATCH (MJ)	PPM: EQPT (CR)
2R: HI-TXPOWER (MN)	ISC: ALS (NA)	PPM: HI-LASERBIAS (MN)
2R: LO-RXPOWER (MN)	ISC: AS-CMD (NA)	PPM: HI-LASERTEMP (MN)
2R: LO-TXPOWER (MN)	ISC: AS-MT (NA)	PPM: HI-TXPOWER (MN)
2R: LOCKOUT-REQ (NA)	ISC: CARLOSS (MJ)	PPM: IMPROPRMVL (CR)
2R: LOS (CR)	ISC: FAILTOSW (NA)	PPM: LO-LASERBIAS (MN)
2R: MANUAL-REQ-SPAN (NA)	ISC: FORCED-REQ-SPAN (NA)	PPM: LO-LASERTEMP (MN)
2R: SQUELCHED (NA)	ISC: GE-OOSYNC (CR)	PPM: LO-TXPOWER (MN)
2R: WKSWPR (NA)	ISC: HI-LASERBIAS (MN)	PPM: MEA (CR)
2R: WTR (NA)	ISC: HI-RXPOWER (MN)	PPM: MFGMEM (CR)
AICI-AEP: EQPT (CR)	ISC: HI-TXPOWER (MN)	PPM: NON-CISCO-PPM (MN)
AICI-AEP: MFGMEM (CR)	ISC: LO-RXPOWER (MN)	PPM: PROV-MISMATCH (MN)
AICI-AIE: EQPT (CR)	ISC: LO-TXPOWER (MN)	PPM: UNQUAL-PPM (NR)
AICI-AIE: MFGMEM (CR)	ISC: LOCKOUT-REQ (NA)	PWR: AS-CMD (NA)
AIP: INVMACADR (MJ)	ISC: LOS (CR)	PWR: BAT-FAIL (MJ)
AIP: MEA (CR)	ISC: LPBKFACILITY (NA)	PWR: EHIBATVG (MJ)
AIP: MFGMEM (CR)	ISC: LPBKTERMINAL (NA)	PWR: ELWBATVG (MJ)
AOTS: ALS (NA)	ISC: MANUAL-REQ-SPAN (NA)	PWR: HIBATVG (MJ)
AOTS: AMPLI-INIT (NA)	ISC: OUT-OF-SYNC (NA)	PWR: LWBATVG (MJ)
AOTS: APC-CORR-SKIPPED (MN)	ISC: SIGLOSS (MJ)	PWR: VOLT-MISM (NA)
AOTS: APC-DISABLED (MN)	ISC: SQUELCHED (NA)	SHELF: APC-DISABLED (MN)
AOTS: APC-OUT-OF-RANGE (MN)	ISC: SYNCLOSS (MJ)	SHELF: AS-CMD (NA)
AOTS: APC-WRONG-GAIN (NA)	ISC: WKSWPR (NA)	SHELF: AS-MT (NA)
AOTS: AS-CMD (NA)	ISC: WTR (NA)	SHELF: DUP-SHELF-ID (MJ)
AOTS: AS-MT (NA)	ML100T: GFP-CSF (MJ)	SHELF: MEA (MJ)
AOTS: CASETEMP-DEG (MN)	ML100T: GFP-LFD (MJ)	SHELF: SHELF-COMM-FAIL (MJ)
AOTS: FIBERTEMP-DEG (MN)	ML100T: GFP-UP-MISMATCH (MJ)	STM1E: MS-AIS (NR)
AOTS: GAIN-HDEG (MN)	ML1000: GFP-CSF (MJ)	STM1E: MS-DEG (NA)
AOTS: GAIN-HFAIL (CR)	ML1000: GFP-LFD (MJ)	STM1E: MS-EXC (NA)
AOTS: GAIN-LDEG (MN)	ML1000: GFP-UP-MISMATCH (MJ)	STM1E: MS-RFI (NR)
AOTS: GAIN-LFAIL (CR)	MLMR: GFP-CSF (MJ)	STM1E: SD-L (NA)
AOTS: LASER-APR (NA)	MLMR: GFP-LFD (MJ)	STM1E: SF-L (NA)
AOTS: LASERBIAS-DEG (MN)	MLMR: GFP-UP-MISMATCH (MJ)	STMN: APSB (MN)
AOTS: LASERBIAS-FAIL (MJ)	NE-SREF: FRCDSWTOINT (NA)	STMN: APSC-IMP (MN)
AOTS: LASERTEMP-DEG (MN)	NE-SREF: FRCDSWTOPRI (NA)	STMN: APSCDFLTK (MN)
AOTS: OPWR-HDEG (MN)	NE-SREF: FRCDSWTOSEC (NA)	STMN: APSCINCON (MN)
AOTS: OPWR-HFAIL (CR)	NE-SREF: FRCDSWTOTHIRD (NA)	STMN: APSCM (MN)
AOTS: OPWR-LDEG (MN)	NE-SREF: FRNGSYNC (NA)	STMN: APSCNMIS (MJ)
AOTS: OPWR-LFAIL (CR)	NE-SREF: FSTSYNC (NA)	STMN: APSMM (MN)
AOTS: OSRION (NA)	NE-SREF: HLDOVRSYNC (NA)	STMN: AUTOLSROFF (CR)
AOTS: PARAM-MISM (NA)	NE-SREF: MANSWTOINT (NA)	STMN: FE-FRCDWKSWBK-SPAN (NA)
AOTS: VOA-HDEG (MN)	NE-SREF: MANSWTOPRI (NA)	STMN: FE-FRCDWKSWPR-SPAN (NA)
AOTS: VOA-HFAIL (CR)	NE-SREF: MANSWTOSEC (NA)	STMN: FE-MANWKSWBK-SPAN (NA)
AOTS: VOA-LDEG (MN)	NE-SREF: MANSWTOTHIRD (NA)	STMN: FE-MANWKSWPR-SPAN (NA)
AOTS: VOA-LFAIL (CR)	NE-SREF: SSM-LNC (NA)	STMN: FEPRLF (MN)
BITS: AIS (NR)	NE-SREF: SSM-PRC (NA)	STMN: HELLO (MN)
BITS: BPV (MN)	NE-SREF: SSM-PRS (NA)	STMN: ISIS-ADJ-FAIL (MN)
BITS: HI-CCVOLT (NA)	NE-SREF: SSM-RES (NA)	STMN: LASEREOL (MN)
BITS: LOF (MN)	NE-SREF: SSM-SDH-TN (NA)	STMN: LOCKOUT-REQ (NA)
BITS: LOS (MN)	NE-SREF: SSM-SETS (NA)	STMN: MANWKSWBK-NO-TRFSW (NA)
BITS: SSM-DUS (NA)	NE-SREF: SSM-SMC (NA)	STMN: MANWKSWPR-NO-TRFSW (NA)
BITS: SSM-FAIL (MN)	NE-SREF: SSM-ST2 (NA)	STMN: MS-AIS (NR)
BITS: SSM-LNC (NA)	NE-SREF: SSM-ST3 (NA)	STMN: MS-DEG (NA)
BITS: SSM-OFF (NA)	NE-SREF: SSM-ST3E (NA)	STMN: MS-EOC (MN)
BITS: SSM-PRC (NA)	NE-SREF: SSM-ST4 (NA)	STMN: MS-EXC (NA)
BITS: SSM-PRS (NA)	NE-SREF: SSM-STU (NA)	STMN: MS-RFI (NR)
BITS: SSM-RES (NA)	NE-SREF: SSM-TNC (NA)	STMN: RS-EOC
BITS: SSM-SDH-TN (NA)	NE-SREF: SWTOPRI (NA)	STMN: RS-TIM
BITS: SSM-SETS (NA)	NE-SREF: SWTOSEC (NA)	STSMON: AIS-P (NR)
BITS: SSM-SMC (NA)	NE-SREF: SWTOTHIRD (NA)	STSMON: AUTOSW-AIS (NR)
BITS: SSM-ST2 (NA)	NE-SREF: SYNCPRI (MJ)	STSMON: AUTOSW-LOP (NA)
BITS: SSM-ST3 (NA)	NE-SREF: SYNCSEC (MN)	STSMON: AUTOSW-PDI (NA)
BITS: SSM-ST3E (NA)	NE-SREF: SYNCTHIRD (MN)	STSMON: AUTOSW-SDBER (NA)
BITS: SSM-ST4 (NA)	NE: APC-DISABLED (MN)	STSMON: AUTOSW-SFBER (NA)
BITS: SSM-STU (NA)	NE: APC-END (NA)	STSMON: AUTOSW-UNEQ (NA)
BITS: SSM-TNC (NA)	NE: AS-CMD (NA)	STSMON: ERFI-P-CONN (NR)
BITS: SYNC-FREQ (NA)	NE: AUD-LOG-LOSS (NA)	STSMON: ERFI-P-SRVR (NR)
BPLANE: AS-CMD (NA)	NE: AUD-LOG-LOW (NA)	STSMON: FAILTOSW-PATH (NA)
BPLANE: MFGMEM (CR)	NE: DATAFLT (MN)	STSMON: FORCED-REQ (NA)
CE100T: GFP-CSF (MJ)	NE: DBOSYNC (MJ)	STSMON: LOCKOUT-REQ (NA)
CE100T: GFP-LFD (MJ)	NE: DUP-IPADDR (MN)	STSMON: LOP-P (CR)
CE100T: GFP-UP-MISMATCH (MJ)	NE: DUP-NODENAME (MN)	STSMON: LPBKCRS (NA)
CE1000: GFP-CSF (MJ)	NE: ETH-LINKLOSS (NA)	STSMON: PDI-P (NA)
CE1000: GFP-LFD (MJ)	NE: HITEMP (CR)	STSMON: RFI-P (NA)
CE1000: GFP-UP-MISMATCH (MJ)	NE: I-HITEMP (CR)	STSMON: SD-P (NA)
CEMR: GFP-CSF (MJ)	NE: INTRUSION-PSWD (NA)	STSMON: SF-P (NA)
CEMR: GFP-LFD (MJ)	NE: LAN-POL-REV (NA)	STSMON: TIM-P (NA)
CEMR: GFP-UP-MISMATCH (MJ)	NE: SNTP-HOST (MN)	STSMON: UNEQ-P (CR)
ENVALRM: EXT (MN)	NE: SYSBOOT (MJ)	STSTRM: AIS-P (NR)
EQPT: ALS-DISABLED (NA)	NE: TEMP-MISM (NA)	STSTRM: AS-MT-OOG (NA)
EQPT: APC-DISABLED (MN)	OCH-TERM: FDI (NA)	STSTRM: ENCAP-MISMATCH-P (CR)
EQPT: AS-CMD (NA)	OCH-TERM: OCHTERM-INC (NA)	STSTRM: ERFI-P-CONN (NR)
EQPT: AS-MT (NA)	OCH-TERM: OPWR-HDEG (MN)	STSTRM: ERFI-P-SRVR (NR)
EQPT: AUTORESET (MN)	OCH-TERM: OPWR-LDEG (MN)	STSTRM: LOP-P (CR)
EQPT: BKUPMEMP (CR)	OCH-TERM: OPWR-LFAIL (CR)	STSTRM: PDI-P (NA)
EQPT: CARLOSS (MJ)	OCH-TERM: PARAM-MISM (NA)	STSTRM: RFI-P (NA)
EQPT: CLDRESTART (NA)		STSTRM: SD-P (NA)
EQPT: CONTBUS-DISABLED (CR)		STSTRM: SF-P (NA)
EQPT: CONTBUS-IO-A (CONTBUS-A) (MN)		STSTRM: TIM-P (NA)
EQPT: CONTBUS-IO-B (CONTBUS-B) (MN)		STSTRM: UNEQ-P (CR)
EQPT: CTNEQPT-MISMATCH (NA)	OCH: APC-CORR-SKIPPED (MN)	TRUNK: AIS (NR)
EQPT: DIAG (CR)	OCH: APC-DISABLED (MN)	TRUNK: AIS-L (NR)
EQPT: EQPT (CR)	OCH: APC-OUT-OF-RANGE (MN)	TRUNK: ALS (NA)
EQPT: EXCCOL (MN)	OCH: AS-CMD (NA)	TRUNK: AS-CMD (NA)
EQPT: FAILTOSW (NA)	OCH: AS-MT (NA)	TRUNK: AS-MT (NA)
EQPT: FAPS-CONFIG-MISMATCH (MN)	OCH: FDI (NA)	TRUNK: CARLOSS (MJ)
EQPT: FORCED-REQ (NA)	OCH: LOS-O (MN)	TRUNK: DSP-COMM-FAIL (MJ)
EQPT: FP-LINK-LOSS (MN)	OCH: LOS-P (CR)	TRUNK: DSP-FAIL (MJ)
EQPT: FTA-MISMATCH (NA)	OCH: OPWR-HDEG (MN)	TRUNK: EOC (MN)
EQPT: HI-LASERBIAS (MN)	OCH: OPWR-HFAIL (CR)	TRUNK: EOC-L (MN)
EQPT: HI-LASERTEMP (MN)	OCH: OPWR-LDEG (MN)	TRUNK: FAILTOSW (NA)
EQPT: HI-TXPOWER (MN)	OCH: OPWR-LFAIL (CR)	TRUNK: FAPS (NA)
EQPT: HITEMP (MN)	OCH: PARAM-MISM (NA)	TRUNK: FC-NO-CREDITS (MJ)
EQPT: IMPROPRMVL (CR)	OCH: PORT-FAIL (CR)	TRUNK: FEC-MISM (MJ)
EQPT: INHSWPR (NA)	OCH: TRAIL-SIGNAL-FAIL (NA)	TRUNK: FORCED-REQ-SPAN (NA)
EQPT: INHSWWKG (NA)	OCH: VOA-HDEG (MN)	TRUNK: GCC-EOC (MN)
EQPT: LO-LASERBIAS (MN)	OCH: VOA-HFAIL (CR)	TRUNK: GE-OOSYNC (CR)
EQPT: LO-LASERTEMP (MN)	OCH: VOA-LDEG (MN)	TRUNK: HELLO (MN)
EQPT: LO-TXPOWER (MN)	OCH: VOA-LFAIL (CR)	TRUNK: HI-LASERBIAS (MN)
EQPT: LOCKOUT-REQ (NA)	OCHNC-CONN: OCHNC-INC (NA)	TRUNK: HI-RXPOWER (MN)
EQPT: MAN-REQ (NA)	OCN: AIS-L (NR)	TRUNK: HI-TXPOWER (MN)
EQPT: MANRESET (NA)	OCN: ALS (NA)	TRUNK: ILK-FAIL (CR)
EQPT: MEA (CR)	OCN: APS-INV-PRIM (MN)	TRUNK: ISIS-ADJ-FAIL (MN)
EQPT: MEM-GONE (MJ)	OCN: APS-PRIM-FAC (NA)	TRUNK: LO-RXPOWER (MN)
EQPT: MEM-LOW (MN)	OCN: APS-PRIM-SEC-MISM (MN)	TRUNK: LO-TXPOWER (MN)
EQPT: OPEN-SLOT (NA)	OCN: APSB (MN)	TRUNK: LOCKOUT-REQ (NA)
EQPT: PEER-NORESPONSE (MJ)	OCN: APSC-IMP (MN)	TRUNK: LOF (CR)
EQPT: PROTNA (MN)	OCN: APSCDFLTK (MN)	TRUNK: LOM (CR)
EQPT: PWR-FAIL-A (MN)	OCN: APSCINCON (MN)	TRUNK: LOS (CR)
EQPT: PWR-FAIL-B (MN)	OCN: APSCM (MN)	TRUNK: LOS-P (CR)
EQPT: PWR-FAIL-RET-A (MN)	OCN: APSCNMIS (MJ)	TRUNK: LPBKFACILITY (NA)
EQPT: PWR-FAIL-RET-B (MN)	OCN: APSIMP (MN)	TRUNK: LPBKTERMINAL (NA)
EQPT: RS-EOC (MN)	OCN: APSMM (MN)	TRUNK: MANUAL-REQ-SPAN (NA)
EQPT: RS-TIM (CR)	OCN: AS-CMD (NA)	TRUNK: ODUK-1-AIS-PM (NR)
EQPT: RUNCFG-SAVENEED (NA)	OCN: AS-MT (NA)	TRUNK: ODUK-2-AIS-PM (NR)
EQPT: SFTWDOWN (MN)	OCN: AUTOLSROFF (CR)	TRUNK: ODUK-3-AIS-PM (NR)
EQPT: SW-MISMATCH (NA)	OCN: CHANLOSS (NA)	TRUNK: ODUK-4-AIS-PM (NR)
EQPT: UNEQ-P (CR)	OCN: EOC (MN)	TRUNK: ODUK-AIS-PM (NR)
EQPT: VOA-DISABLED (CR)	OCN: EOC-L (MN)	TRUNK: ODUK-BDI-PM (NR)
EQPT: WKSWBK (NA)	OCN: FAILTOSW (NA)	TRUNK: ODUK-LCK-PM (NR)
EQPT: WKSWPR (NA)	OCN: FE-FRCDWKSWBK-SPAN (NA)	TRUNK: ODUK-OCI-PM (NR)
EQPT: WORK-QUEUE-FULL (NA)	OCN: FE-FRCDWKSWPR-SPAN (NA)	TRUNK: ODUK-SD-PM (NA)
EQPT: WTR (NA)	OCN: FE-MANWKSWBK-SPAN (NA)	TRUNK: ODUK-SF-PM (NA)
ESCON: ALS (NA)	OCN: FE-MANWKSWPR-SPAN (NA)	TRUNK: ODUK-TIM-PM (MJ)
ESCON: AS-CMD (NA)	OCN: FEPRLF (MN)	TRUNK: OTUK-AIS (NR)
ESCON: AS-MT (NA)	OCN: FORCED-REQ-SPAN (NA)	TRUNK: OTUK-BDI (NR)
ESCON: FAILTOSW (NA)	OCN: FRCDWKSWBK-NO-TRFSW (NA)	TRUNK: OTUK-IAE (MN)
ESCON: FORCED-REQ-SPAN (NA)	OCN: FRCDWKSWPR-NO-TRFSW (NA)	TRUNK: OTUK-LOF (CR)
ESCON: HI-LASERBIAS (MN)	OCN: HELLO (MN)	TRUNK: OTUK-SD (NA)
ESCON: HI-RXPOWER (MN)	OCN: HI-LASERBIAS (MN)	TRUNK: OTUK-SF (NA)
ESCON: HI-TXPOWER (MN)	OCN: HI-LASERTEMP (MN)	TRUNK: OTUK-TIM (CR)
ESCON: LO-RXPOWER (MN)	OCN: HI-RXPOWER (MN)	TRUNK: OUT-OF-SYNC (MJ)
ESCON: LO-TXPOWER (MN)	OCN: HI-TXPOWER (MN)	TRUNK: PROV-MISMATCH (MJ)
ESCON: LOCKOUT-REQ (NA)	OCN: ISIS-ADJ-FAIL (MN)	TRUNK: PTIM (MJ)
ESCON: LOS (CR)	OCN: LASEREOL (MN)	TRUNK: RFI (NR)
ESCON: LPBKFACILITY (NA)	OCN: LOCKOUT-REQ (NA)	TRUNK: RFI-L (NR)
ESCON: LPBKTERMINAL (NA)	OCN: LO-LASERBIAS (MN)	TRUNK: SD (NA)
ESCON: MANUAL-REQ-SPAN (NA)	OCN: LO-LASERTEMP (MN)	TRUNK: SD-L (NA)
ESCON: SIGLOSS (MJ)	OCN: LO-RXPOWER (MN)	TRUNK: SF (NA)
ESCON: SQUELCHED (NA)	OCN: LO-TXPOWER (MN)	TRUNK: SF-L (NA)
ESCON: WKSWPR (NA)	OCN: MANUAL-REQ-SPAN (NA)	TRUNK: SIGLOSS (MJ)
ESCON: WTR (NA)	OCN: MANWKSWBK-NO-TRFSW (NA)	TRUNK: SQUELCHED (NA)
EXT-SREF: FRCDSWTOPRI (NA)	OCN: MANWKSWPR-NO-TRFSW (NA)	TRUNK: SSM-DUS (NA)
EXT-SREF: FRCDSWTOSEC (NA)	OCN: RFI-L (NA)	TRUNK: SSM-FAIL (MN)
EXT-SREF: FRCDSWTOTHIRD (NA)	OCN: SD-L (NA)	TRUNK: SSM-LNC (NA)
EXT-SREF: MANSWTOPRI (NA)	OCN: SF-L (NA)	TRUNK: SSM-OFF (NA)
EXT-SREF: MANSWTOSEC (NA)	OCN: SQUELCHED (NA)	TRUNK: SSM-PRC (NA)
EXT-SREF: MANSWTOTHIRD (NA)	OCN: TIM-S (CR)	TRUNK: SSM-PRS (NA)
EXT-SREF: SWTOPRI (NA)	OMS: APC-DISABLED (MN)	TRUNK: SSM-RES (NA)
EXT-SREF: SWTOSEC (NA)	OMS: APC-CORR-SKIPPED (MN)	TRUNK: SSM-SDH-TN (NA)
EXT-SREF: SWTOTHIRD (NA)	OMS: APC-OUT-OF-RANGE (MN)	TRUNK: SSM-SETS (NA)
EXT-SREF: SYNCPRI (MN)	OMS: AS-CMD (NA)	TRUNK: SSM-SMC (NA)
EXT-SREF: SYNCSEC (MN)	OMS: AS-MT (NA)	TRUNK: SSM-ST2 (NA)
EXT-SREF: SYNCTHIRD (MN)	OMS: LOS-O (MN)	TRUNK: SSM-ST3 (NA)
FAN: EQPT-MISS (CR)	OMS: LOS-P (CR)	TRUNK: SSM-ST3E (NA)
FAN: FAN (CR)	OMS: OPWR-HDEG (MN)	TRUNK: SSM-ST4 (NA)
FAN: MEA (CR)	OMS: OPWR-HFAIL (CR)	TRUNK: SSM-STU (NA)
FAN: MFGMEM (CR)	OMS: OPWR-LDEG (MN)	TRUNK: SSM-TNC (NA)
FC: ALS (NA)	OMS: OPWR-LFAIL (CR)	TRUNK: SYNC-FREQ (NA)
FC: AS-CMD (NA)	OMS: PARAM-MISM (NA)	TRUNK: SYNCLOSS (MJ)
FC: AS-MT (NA)	OMS: PMI (NA)	TRUNK: TIM (CR)
FC: CARLOSS (MJ)	OMS: VOA-HDEG (MN)	TRUNK: TIM-MON (MN)
FC: FAILTOSW (NA)	OMS: VOA-HFAIL (CR)	TRUNK: TRAIL-SIGNAL-FAIL (NA)
FC: FC-NO-CREDITS (MJ)	OMS: VOA-LDEG (MN)	TRUNK: UNC-WORD (NA)
FC: FORCED-REQ-SPAN (NA)	OMS: VOA-LFAIL (CR)	TRUNK: UT-COMM-FAIL (MJ)
FC: GE-OOSYNC (CR)	OSC-RING: RING-ID-MIS (MJ)	TRUNK: UT-FAIL (MJ)
FC: HI-LASERBIAS (MN)	OTS: APC-CORR-SKIPPED (MN)	TRUNK: WTR (NA)
FC: HI-RXPOWER (MN)	OTS: APC-DISABLED (MN)	TRUNK: WVL-MISMATCH (MJ)
FC: HI-TXPOWER (MN)	OTS: APC-OUT-OF-RANGE (MN)	VCMON-HP: AU-AIS (NR)
FC: LO-RXPOWER (MN)	OTS: AS-CMD (NA)	VCMON-HP: AU-LOP (NA)
FC: LO-TXPOWER (MN)	OTS: AS-MT (NA)	VCMON-HP: AUTOSW-AIS-SNCP (NR)
FC: LOCKOUT-REQ (NA)	OTS: AWG-DEG (MN)	VCMON-HP: AUTOSW-LOP-SNCP (NA)
FC: LPBKFACILITY (NA)	OTS: AWG-FAIL (CR)	VCMON-HP: AUTOSW-PDI-SNCP (NA)
FC: LPBKTERMINAL (NA)	OTS: AWG-OVERTEMP (CR)	VCMON-HP: AUTOSW-SDBER-SNCP (NA)
FC: MANUAL-REQ-SPAN (NA)	OTS: AWG-WARM-UP (NA)	VCMON-HP: AUTOSW-SFBER-SNCP (NA)
FC: OUT-OF-SYNC (MJ)	OTS: DCU-LOSS-FAIL (MN)	VCMON-HP: AUTOSW-UNEQ-SNCP (NA)
FC: SIGLOSS (MJ)	OTS: FAILTOSW (NA)	VCMON-HP: FAILTOSW-HO (NA)
FC: SQUELCHED (NA)	OTS: FORCED-REQ-SPAN (NA)	VCMON-HP: FORCED-REQ (NA)
FC: SYNCLOSS (MJ)	OTS: LASERBIAS-DEG (MN)	VCMON-HP: HP-DEG (NA)
FC: WKSWPR (NA)	OTS: LOS (CR)	VCMON-HP: HP-EXC (NA)
FC: WTR (NA)	OTS: LOS-O (MN)	VCMON-HP: HP-PLM (CR)
FCMR: GFP-CSF (MJ)	OTS: LOS-P (CR)	VCMON-HP: HP-RFI (NR)
FCMR: GFP-LFD (MJ)	OTS: LOS-RAMAN (CR)	VCMON-HP: HP-TIM (MN)
FCMR: GFP-UP-MISMATCH (MJ)	OTS: LOCKOUT-REQ (NA)	VCMON-HP: HP-UNEQ (CR)
GE: ALS (NA)	OTS: MANUAL-REQ-SPAN (NA)	VCMON-HP: LOCKOUT-REQ (NA)
GE: AS-CMD (NA)	OTS: MT-OCHNC (NA)	VCMON-HP: LPBKCRS (NA)
GE: AS-MT (NA)	OTS: OPWR-HDEG (MN)	VCMON-HP: SFBER-EXCEED-HO (NA)
GE: CARLOSS (MJ)	OTS: OPWR-HFAIL (CR)	VCMON-LP: AUTOSW-AIS-SNCP (NR)
GE: FAILTOSW (NA)	OTS: OPWR-LDEG (MN)	VCMON-LP: AUTOSW-LOP-SNCP (NA)
GE: FORCED-REQ-SPAN (NA)	OTS: OPWR-LFAIL (CR)	VCMON-LP: AUTOSW-UNEQ-SNCP (NA)
GE: GE-OOSYNC (CR)	OTS: OSRION (NA)	VCMON-LP: FORCED-REQ (NA)
GE: HI-LASERBIAS (MN)	OTS: PARAM-MISM (NA)	VCMON-LP: LOCKOUT-REQ (NA)
GE: HI-RXPOWER (MN)	OTS: PMI (NA)	VCTRM-HP: AS-MT-OOG (NA)
GE: HI-TXPOWER (MN)	OTS: PWR-PROT-ON (MJ)	VCTRM-HP: AU-AIS (NR)
GE: LMP-FAIL (MN)	OTS: RLS (NA)	VCTRM-HP: AU-LOP (CR)
GE: LMP-SD (MN)	OTS: SH-IL-VAR-DEG-HIGH (MN)	VCTRM-HP: HP-DEG (NA)
GE: LMP-SF (MN)	OTS: SH-IL-VAR-DEG-LOW (MN)	VCTRM-HP: HP-ENCAP-MISMATCH (CR)
GE: LMP-UNALLOC (NA)	OTS: SHUTTER-OPEN (NA)	VCTRM-HP: HP-EXC (NA)
GE: LO-RXPOWER (MN)	OTS: SPAN-NOT-MEASURED (NA)	VCTRM-HP: HP-PLM (CR)
GE: LO-TXPOWER (MN)	OTS: SPANLEN-OUT-OF-RANGE (MN)	VCTRM-HP: HP-TIM (CR)
GE: LOCKOUT-REQ (NA)	OTS: VOA-HDEG (MN)	VCTRM-HP: HP-UNEQ (CR)
GE: LPBKFACILITY (NA)	OTS: VOA-HFAIL (CR)	VCTRM-HP: SFBER-EXCEED-HO (NA)
GE: LPBKTERMINAL (NA)	OTS: VOA-LDEG (MN)	VCTRM-LP: AS-MT-OOG (NA)
GE: MANUAL-REQ-SPAN (NA)	OTS: VOA-LFAIL (CR)	VCTRM-LP: SFBER-EXCEED-HO (NA)
GE: OUT-OF-SYNC (MJ)	OTS: WKSWBK (NA)	—
GE: SIGLOSS (MJ)	OTS: WKSWPR (NA)	—

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 ONS 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, FUDC, MSUDC

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  AIS-P

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

Logical Object: STSMON, STSTRM

The AIS Path condition means that this node is detecting AIS in the incoming path. This alarm is secondary to another alarm occurring simultaneously in an upstream node.

Clear the AIS-P 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.4  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, OPT-AMP-C, or OMP-AMP-17-C) 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.5  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 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, OPT-AMP-C, or OMP-AMP-17-C 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.6  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-29.

---

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.7  APC-CORR-SKIPPED

Default Severity: Minor (MN), 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-CORR-SKIPPED condition is raised.

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

The APC Correction Skipped alarm strongly limits network management (for example, a new circuit cannot be turned into IS). The Force APC Correction button helps to restore normal conditions by clearing the APC Correction Skipped alarm. For more information about the Force APC Correction button, refer to the "Managing APC" section in "Network Reference" chapter of the Cisco ONS 15454 DWDM Reference Manual.

2.5.8  APC-DISABLED

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

Logical Objects: NE, SHELF, AOTS, OTS, OMS, OCH, EQPT

The APC Disabled alarm 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 "EQPT" alarm on page 2-72, the "IMPROPRMVL" alarm on page 2-109, or the "MEA (EQPT)" alarm on page 2-156. 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.

APC Disabled alarm is raised in the following conditions:

•When you manually disable APC in a given domain to prevent unexpected power regulations during maintenance or troubleshooting.

•When an anomalous event impacting optical regulation occurs.

APC Disabled alarm is disabled in the following conditions:

•An EQPT alarm raised by any of the MSTP units in any of the domain nodes.

•A MEA alarm raised by any of the MSTP equipped cards in any of the domain nodes.

•An IMPROPRMVL alarm is raised by any of the equipped cards in any of the domain nodes.

•Gain Degrade, Power Degrade, Power Fail Alarm is raised by the output port of any Amplifier in any of domain nodes.

•A VOA degrade or fail alarm is raised by any by any of the equipped cards in any of the domain nodes.

•Signalling protocol detects that one of the APC instances in any of the domain nodes is no more reachable

•Not all nodes belonging to domain are set in Metro-Core (e.g. one is configured as Not-DWDM)

---

Note The MEA and IMPROPRMVL alarms does not disable APC when raised on OSCM, OSC-CSM, or MXP/TXP cards.

---

Clear the APC-DISABLED Alarm

---

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.9  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.10  APC-OUT-OF-RANGE

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

Logical Objects: AOTS, OCH, OMS, OTS

The APC Out of Range condition is raised on amplifier cards (OPT-PRE BST , OPT-BST-L, OPT-PRE, OPT-AMP-17-C, OPT-AMP-C, OPT-RAMP-C, OPT-AMP-L, and OPT-BST-E); demultiplexer cards (32-DMX, 40-DMX-C, and 32-DMX-L) 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 A common cause of an amplifier trying to attain a value higher than the maximum setpoint or an attenuator trying to attain a value lower than the minimum setpoint is the low input power.

---

---

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 Alarm

---

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.11  APC-WRONG-GAIN

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

Logical Object: AOTS

The APC-WRONG-GAIN condition is raised on the amplifier card (OMP-AMP-17-C), when the actual gain of the card (17dB) does not match the expected gain calculated by APC. There is a margin of +1 or -1 dB before the condition is raised.

---

Note The APC-WRONG-GAIN condition indicates a system issue and not the card problem.

---

Clear the APC-WRONG-GAIN Alarm

The condition can be cleared by recovering the power at the input port:

---

Step 1 Check the incoming fiber connection and clean them.

Step 2 Check the regulation points (VOA and amplifiers) along the optical path upstream of the OMP-AMP-17-C card.

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.12  APSB

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

Logical Object: OCN, STMN

The APS Channel Byte Failure alarm occurs when LTE detects protection switching byte failure or an invalid switching code in the incoming APS signal. Some older SONET not manufactured by Cisco send invalid APS codes if they are configured in a 1+1 protection group with newer SONET nodes, such as the ONS 15454. These invalid codes cause an APSB alarm on an ONS 15454.

Clear the APSB Alarm

---

Step 1 Use an optical test set to examine the incoming SONET overhead to confirm inconsistent or invalid K bytes. For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15454.

Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you could need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Card" 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).

---

2.5.13  APSCM

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

Logical Object: OCN, STMN

The APS Channel Mismatch alarm occurs when the ONS 15454 expects a working channel but receives a protect channel. In many cases, the working and protect channels are crossed and the protect channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. The APSCM alarm occurs only on the ONS 15454 when bidirectional protection is used on OC-N cards in a 1+1 protection group configuration. The APSCM alarm does not occur in an optimized 1+1 protection configuration.

---

Warning On the ONS 15454 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

---

Clear the APSCM Alarm

---

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

---

---

Step 1 Verify that the working-card channel fibers are physically connected directly to the adjoining node's working-card channel fibers.

Step 2 If the fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node's protection-card channel fibers.

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.14  APSIMP

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

Logical Object: OCN, STMN

The APS Invalid Code alarm occurs if a 1+1 protection group is not properly configured at both nodes to send or receive the correct APS byte. A node that is either configured for no protection or is configured for path protection or BLSR protection does not send the right K2 APS byte anticipated by a system configured for 1+1 protection. The 1+1 protect port monitors the incoming K2 APS byte and raises this alarm if it does not receive the byte.

The alarm is superseded by an APSCM or APSMM alarm, but not by an AIS condition. It clears when the port receives a valid code for 10 ms.

Clear the APSIMP Alarm

---

Step 1 Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group. For procedures, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure Guide.

Step 2 If the other end of the group is properly configured or the alarm does not clear after you have provisioned the group correctly, verify that the working ports and protect ports are cabled correctly.

Step 3 Ensure that both protect ports are configured for SONET.

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.15  APS-INV-PRIM

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

Logical Object: OCN

The Optimized 1+1 APS Primary Facility condition occurs on OC-N cards in an optimized 1+1 protection system if the incoming primary section header does not indicate whether it is primary or secondary.

---

Note APS-INV-PRIM is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.

---

2.5.16  APSMM

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

SONET Logical Object: STMN

An APS Mode Mismatch failure alarm occurs on OC-N cards when there is a mismatch of the protection switching schemes at the two ends of the span, such as being bidirectional at one end and unidirectional at the other. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional. APSMM can also occur if third-party equipment is provisioned as 1:N and the ONS 15454 is provisioned as 1+1.

If one end is provisioned for 1+1 protection switching and the other is provisioned for path protection protection switching, an APSMM alarm occurs in the ONS 15454 that is provisioned for 1+1 protection switching.

Clear the APSMM Alarm

---

Step 1 For the reporting ONS 15454, display node view and verify the protection scheme provisioning:

a. Click the Provisioning > Protection tabs.

b. Click the 1+1 protection group configured for the OC-N cards.

The chosen protection group is the protection group optically connected (with data communications channel, or DCC, connectivity) to the far end.

c. Click Edit.

d. Record whether the Bidirectional Switching check box is checked.

Step 2 Click OK in the Edit Protection Group dialog box.

Step 3 Log into the far-end node and verify that the OC-N 1+1 protection group is provisioned.

Step 4 Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in Step 1. If not, change it to match.

Step 5 Click Apply.

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.17  APS-PRIM-FAC

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

Logical Object: OCN

The Optimized 1+1 APS Invalid Primary Section condition occurs on OC-N cards in an optimized 1+1 protection system if there is an APS status switch between the primary and secondary facilities to identify which port is primary.

---

Note APS-PRIM-FAC is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.

---

Clear the APS-PRIM-FAC Condition

---

Step 1 This condition clears when the card receives a valid primary section indication (1 or 2).

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.18  APS-PRIM-SEC-MISM

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

Logical Object: OCN

The Optimized 1+1 APS Primary Section Mismatch condition occurs on OC-N cards in an optimized 1+1 protection system if there is a mismatch between the primary section of the local node facility and the primary section of the remote-node facility.

Clear the APS-PRIM-SEC-MISM Alarm

---

Step 1 Ensure that the local node and remote-node ports are correctly provisioned the same way. For more information about optimized 1+1 configurations, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure Guide.

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.19  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.20  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, TXP, GE-XP, 10GE-XP, and ADM-10G 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.21  AU-AIS

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

Logical Object: VCMON-HP, VCTRM-HP

An AU AIS condition applies to the administration unit, which consists of the virtual container (VC) capacity and pointer bytes (H1, H2, and H3) in the SDH frame.

Generally, any AIS is a special SDH 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 AU-AIS Condition

---

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

Step 2 If the condition does not clear, complete the "Clear the APSB Alarm" procedure.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.22  AU-LOP

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

Logical Objects: VCMON-HP, VCTRM-HP

An AU-LOP alarm indicates that the SDH high order path overhead section of the administration unit has detected a loss of path. AU-LOP occurs when there is a mismatch between the expected and provisioned circuit size. For the TXP card, an AU-LOP is raised if a port is configured for an SDH signal but receives a SDH signal instead. (This information is contained in the H1 byte bits 5 and 6.)

---

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 MXP and TXP cards, refer to the Cisco ONS 15454 SDH Reference Manual.

---

Clear the AU-LOP Alarm

---

Step 1 In node view, click the Circuits tab and view the alarmed circuit.

Step 2 Verify that the correct circuit size is listed in the Size column. If the size is different from what is expected, such as a VC4-4c instead of a VC4, this causes the alarm.

Step 3 If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm. Ensure that the test set monitoring is set up for the same size as the circuit provisioning. For specific procedures to use the test set equipment, consult the manufacturer.

Step 4 If you have not been using a test set, or if the test set is correctly set up, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit for the correct size. For procedures, refer to the "Create Circuits and Tunnels" chapter in the Cisco ONS 15454 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

---

2.5.23  AUTOLSROFF

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

Logical Object: STMN

The Auto Laser Shutdown alarm occurs when the STM-64 card temperature exceeds 194 degrees F (90 degrees C). The internal equipment automatically shuts down the STM-64 laser when the card temperature rises to prevent the card from self-destructing.

---

Warning On the OC192 LR/STM64 LH 1550 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

---

Clear the AUTOLSROFF Alarm

---

Step 1 View the temperature displayed on the ONS 15454 LCD front panel (Figure 2-2).

Figure 2-2 shows the shelf LCD panel.

Figure 2-1 Shelf LCD Panel

Step 2 If the temperature of the shelf exceeds 194 degrees F (90 degrees C), the alarm should clear if you solve the ONS 15454 temperature problem. Complete the "Clear the HITEMP Alarm" procedure.

Step 3 If the temperature of the shelf is under 194 degrees F (90 degrees C), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Card" procedure for the OC-192 card.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database.

---

Step 4 If card replacement does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

---

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

Resets performed during a software upgrade also prompt the condition. This condition clears automatically when the card finishes resetting. 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.25  AUTOSW-AIS

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

Logical Object: STSMON, VT-MON

The Automatic Path Protection Switch Caused by an AIS condition indicates that automatic path protection switching occurred because of an AIS condition. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

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 AUTOSW-AIS 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.26  AUTOSW-AIS-SNCP

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

Logical Object: VCMON-HP, VCMON-LP

The Automatic path protection Switch Caused by an AIS condition indicates that automatic path protection protection switching occurred because of the TU-AIS condition. If the path protection ring is configured for revertive switching, it switches back to the working path after the fault clears. The AUTOSW-AIS-path protection clears when you clear the primary alarm on the upstream node.

---

Note This condition is only reported if the SNCP is set up for revertive switching.

---

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 AUTOSW-AIS-path protection 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.27  AUTOSW-LOP (STSMON)

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the "LOP-P" alarm on page 2-130. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

Clear the AUTOSW-LOP (STSMON) Condition

---

Step 1 Complete the "Clear the LOP-P 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.28  AUTOSW-LOP-SNCP

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

Logical Object: VCMON-HP, VCMON-LP

An Automatic path protection Switch Caused by LOP alarm indicates that an automatic path protection protection switching occurred because of the "AU-LOP" alarm, page 2-38. If the path protection ring is configured for revertive switching, it switches back to the working path after the fault clears.

---

Note This condition is only reported if the SNCP is set up for revertive switching.

---

Clear the AUTOSW-LOP-SNCP Alarm

---

Step 1 Complete the "Clear the AU-LOP 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.29  AUTOSW-PDI

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

Logical Object: STSMON, VT-MON

The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a "PDI-P" alarm on page 2-184. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

Clear the AUTOSW-PDI Condition

---

Step 1 Complete the "Clear the PDI-P 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.30  AUTOSW-PDI-SNCP

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

Logical Object: VCMON-HP, VCMON-LP

The Automatic path protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection protection switching occurred because of a PDI alarm. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

---

Note This condition is only reported if the SNCP is set up for revertive switching.

---

Clear the AUTOSW-PDI-SNCP Condition

---

Step 1 Complete the "Clear the PDI-P Condition" section.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.31  AUTOSW-SDBER

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

Logical Object: STSMON, VT-MON

The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a "SD-P" condition on page 2-200 caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SD-P is resolved.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

Clear the AUTOSW-SDBER Condition

---

Step 1 Complete the "Clear the SD-P 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.32  AUTOSW-SDBER-SNCP

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

Logical Object: VCMON-HP, VCMON-LP

The Automatic path protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade caused automatic path protection protection switching to occur. If the path protection ring is configured for revertive switching, it reverts to the working path when the SD is resolved.

---

Note This condition is only reported if the SNCP is set up for revertive switching.

---

Clear the AUTOSW-SDBER-SNCP Condition

---

Step 1 Complete the "Clear the SD (TRUNK) 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.33  AUTOSW-SFBER

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

Logical Object: STSMON, VT-MON

The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a "SF-P" condition on page 2-203 caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SF-P is resolved.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

Clear the AUTOSW-SFBER Condition

---

Step 1 Complete the "Clear the SF-P 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.34  AUTOSW-SFBER-SNCP

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

Logical Object: VCMON-HP, VCMON-LP

The Automatic path protection Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail caused automatic path protection protection switching to occur. If the path protection ring is configured for revertive switching, it reverts to the working path when the SF is resolved.

---

Note This condition is only reported if the SNCP is set up for revertive switching.

---

Clear the AUTOSW-SFBER-SNCP Condition

---

Step 1 Complete the "Clear the SF (TRUNK) 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.35  AUTOSW-UNEQ (STSMON)

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by Unequipped condition indicates that an "UNEQ-P" alarm on page 2-223, caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

---

Note This condition is only reported if the path protection is set up for revertive switching.

---

Clear the AUTOSW-UNEQ (STSMON) Condition

---

Step 1 Complete the "Clear the UNEQ-P 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.36  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

Logical Object: VCMON-HP

The Automatic path protection Switch Caused by an Unequipped condition indicates that an HP-UNEQ alarm caused automatic path protection protection switching to occur (see the "HP-UNEQ" alarm, page 2-106). If the path protection ring is configured for revertive switching, it reverts to the working path after the fault clears.

---

Warning Class 1 laser product. Statement 1008

---

---

Warning Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053

---

---

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 This condition is only reported if the SNCP is set up for revertive switching.

---

Clear the AUTOSW-UNEQ-SNCP (VCMON-HP) Condition

---

Step 1 Complete the "Clear the HP-UNEQ 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.37  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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, and 40DMX 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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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.38  AWG-FAIL

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

Logical Object: OTS

The AWG Failure alarm occurs when a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, and 40DMX 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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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.39  AWG-OVERTEMP

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

Logical Object: OTS

The AWG Over Temperature alarm is raised if a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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.40  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, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX 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.41  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.42  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-72. 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.43  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.44  CARLOSS (EQPT)

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

Logical Object: EQPT

A Carrier Loss on the LAN Equipment alarm generally occurs on MXP, TXP, or ADM-10G 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-42.

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.45  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.46  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, GE-XP, 10GE-XP, or ADM-10G cards 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.47  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.48  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, 32DMX, or 40DMX) 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.49  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.50  CHANLOSS

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

Logical Object: OCN

The SONET Section Layer DCC Termination Failure condition occurs when the ONS 15454 receives unrecognized data in the section layer DCC bytes.

---

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 may result in hazardous radiation exposure. Statement 1057

---

Clear the CHANLOSS Condition

---

Step 1 In the absence of other alarms, determine whether the alarmed port is connected to another vendor's equipment. If so, you can mask the alarm on this path using a custom alarm profile. For more information about custom profiles, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 Procedure Guide.

Step 2 If alternate vendor equipment is not the cause of the alarm, complete the "Reset a Card in CTC" procedure for the traffic card.

---

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

---

Step 3 If the alarm does not clear, complete the "Physically Replace a Card" procedure.

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.51  CLDRESTART

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

Logical Object: EQPT

The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 power is initialized.

Clear the CLDRESTART Condition

---

Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure.

Step 2 If the condition fails to clear after the card reboots, complete the "Remove and Reinsert (Reseat) Any Card" procedure.

Step 3 If the condition does not clear, complete the "Physically Replace a Card" procedure for the card.

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.52  CONTBUS-DISABLED

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

Logical Object: EQPT

The CONTBUS-DISABLED alarm is a function of the enhanced cell bus verification feature. This alarm occurs when a card is defective upon insertion into the chassis or when a card already present in the chassis becomes defective. (That is, the card fails the enhanced cell bus verification test.) The alarm persists as long as the defective card remains in the chassis. When the card is removed, CONTBUS-DISABLED will remain raised for a one-minute wait time. This wait time is designed as a guard period so that the system can distinguish this outage from a briefer card reset communication outage.

If no card is reinserted into the original slot during the wait time, the alarm clears. After this time, a different, nondefective card (not the original card) should be inserted.

When CONTBUS-DISABLED is raised, no message-oriented communication is allowed to or from this slot to the TCC2/TCC2P card (thus avoiding node communication failure).

---

Caution CONTBUS-DISABLED clears only when the faulty card is removed for one minute. If any card at all is reinserted before the one-minute guard period expires, the alarm does not clear.

---

CONTBUS-DISABLED overrides the IMPROPRMVL alarm during the one-minute wait period, but afterward IMPROPRMVL can be raised because it is no longer suppressed. IMPROPRMVL is raised after CONTBUS-DISABLED clears if the card is in the node database. If CONTBUS-DISABLED has cleared but IMPROPRMVL is still active, inserting a card will clear the IMPROPRMVL alarm.

Clear the CONTBUS-DISABLED Alarm

---

Step 1 If the IMPROPRMVL alarm is raised, complete the "Physically Replace a Card" procedure. (For general information about card installation, refer to the "Install Cards and Fiber-Optic Cable" chapter of the Cisco ONS 15454 Procedure Guide.)

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.53  CONTBUS-IO-A

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

Logical Object: EQPT

A TCCA to Shelf A Slot Communication Failure alarm occurs when the active Slot 7 TCC2/TCC2P card (TCC A) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.

The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 switches to the protect TCC2/TCC2P card. In the case of a TCC2/TCC2P card protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P card. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P card to the reporting card. The physical path of communication includes the TCC2/TCC2P card, the other card, and the backplane.

Clear the CONTBUS-IO-A Alarm

---

Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab and view the Eqpt Type column to reveal the provisioned type.

If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm, page 2-156 for the reporting card.

Step 2 If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P card, perform a CTC reset of the object card. Complete the "Reset a Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

Step 3 If the alarm object is the standby Slot 11 TCC2/TCC2P card, complete the "Reset a Card in CTC" procedure for it. The procedure is similar.

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

Step 4 If CONTBUS-IO-A is raised on several cards at once, 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.

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

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

---

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

---

Step 7 If the reset card has not rebooted successfully, or the alarm has not cleared, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

---

2.5.54  CONTBUS-IO-B

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

Logical Object: EQPT

A TCC B to Shelf Communication Failure alarm occurs when the active Slot 11 TCC2/TCC2P card (TCC B) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.

The CONTBUS-IO-B alarm could appear briefly when the ONS 15454 switches to the protect TCC2/TCC2P card. In the case of a TCC2/TCC2P card protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P card. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P card to the reporting card. The physical path of communication includes the TCC2/TCC2P card, the other card, and the backplane.

Clear the CONTBUS-IO-B Alarm

---

Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab and view the Eqpt Type column to reveal the provisioned type.

If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm, page 2-156 for the reporting card.

Step 2 If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P card, perform a CTC reset of the object card. Complete the "Reset a Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

Step 3 If the alarm object is the standby Slot 7 TCC2/TCC2P card, complete the "Reset a Card in CTC" procedure for it. The procedure is similar.

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

Step 4 If CONTBUS-IO-B is raised on several cards at once, 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.

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

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

---

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

---

Step 7 If the reset card has not rebooted successfully, or the alarm has not cleared, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

---

2.5.55  CTNEQPT-MISMATCH

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

Logical Object: EQPT

The Connection Equipment Mismatch condition is raised when there is a mismatch between the cross-connect card preprovisioned in the slot and the card actually present in the shelf. For example, an XC-VXL card could be preprovisioned in Slot 10, but another card could be physically installed.

---

Note Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation could briefly occur during the upgrade process.

---

---

Note The cross-connect card you are replacing should not be the active card. (It can be in SBY state or otherwise not in use.)

---

---

Note During an upgrade, this condition occurs and is raised as its default severity, Not Alarmed (NA). However, after the upgrade has occurred, if you wish to change the condition's severity so that it is Not Reported (NR), you can do this by modifying the alarm profile used at the node. For more information about modifying alarm severities, refer to the "Manage Alarms" chapter in the Cisco ONS 15454 Procedure Guide.

---

Clear the CTNEQPT-MISMATCH Condition

---

Step 1 Determine what kind of card is preprovisioned in the slot by completing the following steps:

a. In node view, click the Inventory tab.

b. View the slot's row contents in the Eqpt Type and Actual Eqpt Type columns.

The Eqpt Type column contains the equipment that is provisioned in the slot. The Actual Eqpt Type contains the equipment that is physically present in the slot. For example, Slot 8 could be provisioned for an XCVT card, which is shown in the Eqpt Type column, but a different cross-connect card could be physically present in the slot. (This card would be shown in the Actual Eqpt Type column.)

Step 2 Complete the "Physically Replace a Card" procedure for the mismatched 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.5.56  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.57  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 DWDM Procedure Guide.

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.58  DCU-LOSS-FAIL

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

Logical Object: OTS

The DCU-LOSS-FAIL condition occurs when the DCU loss monitored value exceeds the board's maximum acceptable DCU loss.

Clear the DCU-LOSS-FAIL Condition

---

Step 1 Verify that the optical fibers connecting the board (OPT-PRE, OPT-PRE-L, or OPT-AMP-L) and the DCU unit are clean, correctly plugged in, and not damaged.

Step 2 If the condition does not clear, verify that appropriate DCU unit, according to the installation requirements, is connected to the board and is correctly working.

Step 3 If the condition still does not clear, verify that the optical power signal is present on the DCU-TX port.

Step 4 If the alarm is still present, 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.59  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.60  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-64 and could affect traffic.

---

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

---

2.5.61  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-63, 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.62  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.63  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.64  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.65  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.66  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.67  ENCAP-MISMATCH-P

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

Logical Object: STSTRM

The Encapsulation C2 Byte Mismatch Path alarm applies to ML-Series Ethernet cards or the CE-1000 card. It occurs when the first three following conditions are met and one of the last two is false:

•The received C2 byte is not 0x00 (unequipped).

•The received C2 byte is not a PDI value.

•The received C2 does not match the expected C2.

•The expected C2 byte is not 0x01 (equipped unspecified).

•The received C2 byte is not 0x01 (equipped unspecified).

For an ENCAP-MISMATCH-P to be raised, there is a mismatch between the received and expected C2 byte, with either the expected byte or received byte value being 0x01.

For example, an ENCAP-MISMATCH-P alarm is raised if a circuit created between two ML-Series or two CE-1000 cards has generic framing procedure (GFP) framing provisioned on one end and HDLC framing with LEX encapsulation provisioned on the other. The GFP framing card transmits and expects a C2 byte of 0x1B, while the HDLC framing card transmits and expects a C2 byte of 0x01.

A mismatch between the transmit and receive cards on any of the following parameters can cause the alarm:

•Mode (HDLC, GFP-F)

•Encapsulation (LEX, HDLC, PPP)

•CRC size (16 or 32)

•Scrambling state (on or off)

This alarm is demoted by a PLM-P condition or a PLM-V condition.

---

Note By default, an ENCAP-MISMATCH-P alarm causes an ML-Series or CE-1000 card data link to go down. This behavior can be modified using the command line interface (CLI) command in interface configuration mode: no pos trigger defect encap.

---

---

Note For more information about the ML-Series or CE-1000 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 ENCAP-MISMATCH-P Alarm

---

Step 1 Ensure that the correct framing mode is in use on the receive card:

a. In node view, double-click the receive ML-Series or CE-1000 card to open the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply.

Step 2 Ensure that the correct framing mode is in use on the transmit card, and that it is identical to the receiving card:

a. In node view, double-click the transmit ML-Series or CE-1000 card to open the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply.

Step 3 If the alarm does not clear, use the CLI to ensure that the remaining settings are correctly configured on the ML-Series or CE-1000 card:

•Encapsulation

•CRC size

•Scrambling state

To open the interface, click the IOS tab and click Open IOS Command Line Interface (CLI). Refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 entries on all three of these topics to obtain the full configuration command sequences.

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.68  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.69  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.70  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-49, 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-188, 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.71  EQPT-DIAG

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

Logical Object: EQPT

An Equipment-Diagnostic Failure alarm indicates that a software or hardware failure has occurred on the reporting card. This alarm can be raised against a traffic card or a cross-connect card.

Clear the EQPT-DIAG Alarm

---

Step 1 If traffic is active on the alarmed card, you could need to switch traffic away from it. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for procedures.

Step 2 Complete the "Remove and Reinsert (Reseat) Any Card" procedure for the alarmed card

Step 3 If the alarm does not clear, complete the "Physically Replace a Card" procedure if it is raised against a traffic card, or complete the "Generic Signal and Circuit Procedures" procedure if the alarm is raised against the cross-connect card.

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.72  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.73  ERFI-P-CONN

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication (ERFI) Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the "UNEQ-P" alarm on page 2-223 and the "TIM-P" alarm on page 2-221 are raised on the transmission signal.

Clear the ERFI-P-CONN Condition

---

Step 1 Clear the UNEQ-P alarm. This should clear the ERFI condition.

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.74  ERFI-P-SRVR

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

Logical Object: STSMON, STSTRM

The Three-Bit ERFI Path Server condition is triggered on DS-1, DS-3, or VT circuits when the "AIS-P" condition, page 2-27 or the "LOP-P" alarm on page 2-130 is raised on the transmission signal.

Clear the ERFI-P-SRVR Condition

---

Step 1 Complete the "Clear the LOP-P Alarm" procedure. This should clear the ERFI condition.

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.75  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.76  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