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

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Index by Default Severity

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.2  Alarms and Conditions Indexed By Alphabetical Entry

2.3  Logical Object Type Definitions

2.4  Alarm Index by Logical Object Type

2.5  Trouble Notifications

2.5.1  Conditions

2.5.2  Severities

2.6  Safety Summary

2.7  Alarm Procedures

2.7.1  AIS

Clear the AIS Condition

2.7.2  AIS-L

Clear the AIS-L Condition

2.7.3  AIS-P

Clear the AIS-P Condition

2.7.4  AIS-V

Clear the AIS-V Condition

2.7.5 ALS

2.7.6  AMPLI-INIT

Clear the AMPLI-INIT Condition

2.7.7  APC-DISABLED

Clear the APC-DISABLED Alarm

2.7.8  APC-FAIL

Clear the APC-FAIL Alarm

2.7.9  APSB

Clear the APSB Alarm

2.7.10  APSC-IMP

Clear the APSC-IMP Alarm

2.7.11  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.12  APSC-IMP

Clear the APSC-IMP Alarm

2.7.13  APSCINCON

Clear the APSCINCON Alarm

2.7.14  APSCM

Clear the APSCM Alarm

2.7.15  APSCNMIS

Clear the APSCNMIS Alarm

2.7.16  APSIMP

Clear the APSIMP Condition

2.7.17  APSMM

Clear the APSMM Alarm

2.7.18  AS-CMD

Clear the AS-CMD Condition

2.7.19  AS-MT

Clear the AS-MT Condition

2.7.20  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.21  AUD-LOG-LOW

2.7.22  AU-LOF

2.7.23  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.7.24  AUTORESET

Clear the AUTORESET Alarm

2.7.25  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.7.26  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.7.27  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Alarm

2.7.28  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.7.29  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.7.30  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.7.31  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.7.32  AUTOSW-UNEQ (VT-MON)

Clear the AUTOSW-UNEQ (VT-MON) Alarm

2.7.33  AWG-DEG

Clear the AWG-DEG Alarm

2.7.34  AWG-FAIL

Clear the AWG-FAIL Alarm

2.7.35  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.7.36  AWG-WARM-UP

2.7.37  BAT-FAIL

Clear the BAT-FAIL Alarm

2.7.38  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.39  BLSROSYNC

Clear the BLSROSYNC Alarm

2.7.40  CARLOSS (CLIENT)

Clear the CARLOSS (CLIENT) Alarm

2.7.41  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.42  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.7.43  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.7.44  CARLOSS (ML100T, ML1000)

Clear the CARLOSS (ML100T, ML1000) Alarm

2.7.45  CARLOSS (TRUNK)

Clear the CARLOSS (TRUNK) Alarm

2.7.46  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.7.47  CKTDOWN

Clear the CKTDOWN Alarm

2.7.48  CLDRESTART

Clear the CLDRESTART Condition

2.7.49  COMIOXC

Clear the COMIOXC Alarm

2.7.50  COMM-FAIL

Clear the COMM-FAIL Alarm

2.7.51  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.52  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.7.53  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.54  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.55  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.7.56  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.57  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.58  DATAFLT

Clear the DATAFLT Alarm

2.7.59  DBOSYNC

Clear the DBOSYNC Alarm

2.7.60  DSP-COMM-FAIL

2.7.61  DSP-FAIL

Clear the DSP-FAIL Alarm

2.7.62  DS3-MISM

Clear the DS3-MISM Condition

2.7.63  DUP-IPADDR

Clear the DUP-IDADDR Alarm

2.7.64  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.65  EHIBATVG

Clear the EHIBATVG Alarm

2.7.66  ELWBATVG

Clear the ELWBATVG Alarm

2.7.67  EOC

Clear the EOC Alarm

2.7.68  EOC-L

Clear the EOC-L Alarm

2.7.69  EQPT

Clear the EQPT Alarm

2.7.70  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.71  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.7.72  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.7.73  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.7.74  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.75  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.76  E-W-MISMATCH

Clear the E-W-MISMATCH Alarm with a Physical Switch

Clear the E-W-MISMATCH Alarm in CTC

2.7.77  EXCCOL

Clear the EXCCOL Alarm

2.7.78  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.79  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.7.80  EXT

Clear the EXT Alarm

2.7.81  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.82  FAILTOSW

Clear the FAILTOSW Condition

2.7.83  FAILTOSW-PATH

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration

2.7.84  FAILTOSWR

Clear the FAILTOSWR Condition in a Four-Fiber BLSR Configuration

2.7.85  FAILTOSWS

Clear the FAILTOSWS Condition

2.7.86  FAN

Clear the FAN Alarm

2.7.87  FANDEGRADE

Clear the FANDEGRADE Alarm

2.7.88  FE-AIS

Clear the FE-AIS Condition

2.7.89  FEC-MISM

Clear the FEC-MISM Alarm

2.7.90  FE-DS1-MULTLOS

Clear the FE-DS1-MULTLOS Condition

2.7.91  FE-DS1-NSA

Clear the FE-DS1-NSA Condition

2.7.92  FE-DS1-SA

Clear the FE-DS1-SA Condition

2.7.93  FE-DS1-SNGLLOS

Clear the FE-DS1-SNGLLOS Condition

2.7.94  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.7.95  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.7.96  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.97  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.98  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.99  FE-IDLE

Clear the FE-IDLE Condition

2.7.100  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.101  FE-LOF

Clear the FE-LOF Condition

2.7.102  FE-LOS

Clear the FE-LOS Condition

2.7.103  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.104  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.105  FEPRLF

Clear the FEPRLF Alarm on a Four-Fiber BLSR

2.7.106  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.7.107  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.108  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.109  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.110  FRCDSWTOINT

2.7.111  FRCDSWTOPRI

2.7.112  FRCDSWTOSEC

2.7.113  FRCDSWTOTHIRD

2.7.114  FRNGSYNC

Clear the FRNGSYNC Alarm

2.7.115  FSTSYNC

2.7.116  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.117  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.7.118  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.7.119  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.7.120  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.7.121  GCC-EOC

Clear the GCC-EOC Alarm

2.7.122  GE-OOSYNC

Clear the GE-OOSYNC Alarm

2.7.123  HIBATVG

Clear the HIBATVG Alarm

2.7.124  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.125  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.126  HITEMP

Clear the HITEMP Alarm

2.7.127  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.128  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.129  I-HITEMP

Clear the I-HITEMP Alarm

2.7.130  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.131  INC-GFP-OUTOFFRAME

Clear the INC-GFP-OUTOFFRAME Condition

2.7.132  INC-GFP-SIGLOSS

Clear the INC-GFP-SIGLOSS Condition

2.7.133  INC-GFP-SYNCLOSS

Clear the INC-GFP-SYNCLOSS Condition

2.7.134  INC-ISD

2.7.135  INC-SIGLOSS

Clear the INC-SIGLOSS Alarm

2.7.136  INC-SYNCLOSS

Clear the INC-SYNCLOSS Alarm

2.7.137  INHSWPR

Clear the INHSWPR Condition

2.7.138  INHSWWKG

Clear the INHSWWKG Condition

2.7.139  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.140  INVMACADR

Clear the INVMACADR Alarm

2.7.141  IOSCFGCOPY

2.7.142  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.143  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.7.144  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.7.145  LASER-APR

2.7.146  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.7.147  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.7.148  LASEREOL

Clear the LASEREOL Alarm

2.7.149  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.7.150  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.151  LKOUTWK-S (NA)

2.7.152  LMP-HELLODOWN

Clear the LMP-HELLODOWN Alarm

2.7.153  LMP-NDFAIL

Clear the LMP-NDFAIL Alarm

2.7.154  LOA

Clear the LOA Alarm

2.7.155  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.156  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.157  LOF (CLIENT)

Clear the LOF (CLIENT) Alarm

2.7.158  LOF (DS1)

Clear the LOF (DS1) Alarm

2.7.159  LOF (DS3)

Clear the LOF (DS3) Alarm

2.7.160  LOF (EC1-12)

Clear the LOF (EC1-12) Alarm

2.7.161  LOF (OCN)

Clear the LOF (OCN) Alarm

2.7.162  LOF (TRUNK)

Clear the LOF (TRUNK) Alarm

2.7.163  LOM

Clear the LOM Alarm

2.7.164  LOP-P

Clear the LOP-P Alarm

2.7.165  LOP-V

Clear the LOP-V Alarm

2.7.166  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.167  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.168  LOS (CLIENT)

Clear the LOS (CLIENT) Alarm

2.7.169  LOS (DS1)

Clear the LOS (DS1) Alarm

2.7.170  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.171  LOS (EC1-12)

Clear the LOS (EC1-12) Alarm

2.7.172  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.173  LOS (MSUDC)

2.7.174  LOS (OCN)

Clear the LOS (OCN) Alarm

2.7.175  LOS (OTS)

Clear the LOS (OTS) Alarm

2.7.176  LOS (TRUNK)

Clear the LOS (TRUNK) Alarm

2.7.177  LOS-P

Clear the LOS-P Alarm

2.7.178  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.7.179  LPBKCRS

Clear the LPBKCRS Condition

2.7.180  LPBKDS1FEAC

Clear the LPBKDS1FEAC Condition

2.7.181  LPBKDS1FEAC-CMD

2.7.182  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.183  LPBKDS3FEAC-CMD

2.7.184  LPBKFACILITY (CLIENT, TRUNK)

Clear the LPBKFACILITY (CLIENT, TRUNK) Condition

2.7.185  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.186  LPBKFACILITY (EC1-12)

Clear the LPBKFACILITY (EC1-12) Condition

2.7.187  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.7.188  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.7.189  LPBKTERMINAL (CLIENT, TRUNK)

Clear the LPBKTERMINAL (CLIENT) Condition

2.7.190  LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

Clear the LPBKTERMINAL (DS1, DS3, EC1-12, OCN) Condition

2.7.191  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.7.192  LWBATVG

Clear the LWBATVG Alarm

2.7.193  MAN-REQ

Clear the MAN-REQ Condition

2.7.194  MANRESET

2.7.195  MANSWTOINT

2.7.196  MANSWTOPRI

2.7.197  MANSWTOSEC

2.7.198  MANSWTOTHIRD

2.7.199  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.200  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.201  MEA (AIP)

Clear the MEA (AIP) Alarm

2.7.202  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.203  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.204  MEM-GONE

2.7.205  MEM-LOW

2.7.206  MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

Clear the MFGMEM (AICI-AEP, AIE, BPLANE, FAN) Alarm

2.7.207  NO-CONFIG

Clear the NO-CONFIG Condition

2.7.208  NOT-AUTHENTICATED

2.7.209  NTWTPINC

2.7.210  OCHNC-ACTIV-FAIL

2.7.211  OCHNC-DEACTIV-FAIL

2.7.212  OCHNC-FAIL

2.7.213  OCHNC-INC

2.7.214  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.7.215  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.7.216  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.7.217  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.7.218  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.7.219  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.7.220  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.7.221  OOU-TPT

Clear the OOT-TPT Condition

2.7.222  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.7.223  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.7.224  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.7.225  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.7.226  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.7.227  OTUK-AIS

Clear the OTUK-AIS Condition

2.7.228  OTUK-BDI

Clear the OTUK-BDI Condition

2.7.229  OTUK-LOF

Clear the OTUK-LOF Alarm

2.7.230  OTUK-SD

Clear the OTUK-SD Condition

2.7.231  OTUK-SF

Clear the OTUK-SF Condition

2.7.232  OTUK-TIM

Clear the OTUK-TIM Condition

2.7.233  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.7.234  PDI-P

Clear the PDI-P Condition

2.7.235  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.236  PLM-P

Clear the PLM-P Alarm

2.7.237  PLM-V

Clear the PLM-V Alarm

2.7.238  PORT-CODE-MISM

Clear the PORT-CODE-MISM Alarm

2.7.239  PORT-COMM-FAIL

Clear the PORT-COMM-FAIL Alarm

2.7.240  PORT-MISMATCH

2.7.241  PORT-MISSING

Clear the PORT-MISSING Alarm

2.7.242  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.243  PROTNA

Clear the PROTNA Alarm

2.7.244  PTIM

Clear the PTIM Alarm

2.7.245  PWR-A

2.7.246  PWR-B

2.7.247  PWR-REDUN

Clear the PWR-REDUN Alarm

2.7.248  RAI

Clear the RAI Condition

2.7.249  RCVR-MISS

Clear the RCVR-MISS Alarm

2.7.250  RFI

Clear the RFI Condition

2.7.251  RFI-L

Clear the RFI-L Condition

2.7.252  RFI-P

Clear the RFI-P Condition

2.7.253  RFI-V

Clear the RFI-V Condition

2.7.254  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.7.255  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.256  RING-SW-EAST

2.7.257  RING-SW-WEST

2.7.258  RSVP-HELLODOWN

Clear the RSVP-HELLODOWN Alarm

2.7.259  RUNCFG-SAVENEED

2.7.260  SD (CLIENT, TRUNK)

Clear the SD (CLIENT or TRUNK) Condition

2.7.261  SD (DS1, DS3)

Clear the SD (DS1, DS3) Condition

2.7.262  SD-L

Clear the SD-L Condition

2.7.263  SD-P

Clear the SD-P Condition

2.7.264  SF (CLIENT, TRUNK)

Clear the SF (CLIENT, TRUNK) Condition

2.7.265  SF (DS1, DS3)

Clear the SF (DS1, DS3) Condition

2.7.266  SF-L

Clear the SF-L Condition

2.7.267  SF-P

Clear the SF-P Condition

2.7.268  SFTWDOWN

2.7.269  SH-INS-LOSS-VAR-DEG-HIGH

2.7.270  SH-INS-LOSS-VAR-DEG-LOW

2.7.271  SHUTTER-OPEN

Clear the SHUTTER-OPEN Alarm

2.7.272  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.273  SPAN-SW-EAST

2.7.274  SPAN-SW-WEST

2.7.275  SQUELCH

Clear the SQUELCH Condition

2.7.276  SQUELCHED

Clear the SQUELCHED Alarm

2.7.277  SQM

Clear the SQM Alarm

2.7.278  SSM-DUS

2.7.279  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.280  SSM-LNC

2.7.281  SSM-OFF

Clear the SSM-OFF Condition

2.7.282  SSM-PRC

2.7.283  SSM-PRS

2.7.284  SSM-RES

2.7.285  SSM-SDH-TN

2.7.286  SSM-SETS

2.7.287  SSM-SMC

2.7.288  SSM-STU

Clear the SSM-STU Condition

2.7.289  SSM-ST2

2.7.290  SSM-ST3

2.7.291  SSM-ST3E

2.7.292  SSM-ST4

2.7.293  SSM-TNC

2.7.294  SWMTXMOD

Clear the SWMTXMOD Alarm

2.7.295  SWTOPRI

2.7.296  SWTOSEC

Clear the SWTOSEC Condition

2.7.297  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.7.298  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.299  SYNCPRI

Clear the SYNCPRI Alarm

2.7.300  SYNCSEC

Clear the SYNCSEC Alarm

2.7.301  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.302  SYSBOOT

2.7.303  TIM

Clear the TIM Alarm or Condition

2.7.304 TIM-MON

Clear the TIM-MON Alarm

2.7.305  TIM-P

Clear the TIM-P Alarm

2.7.306  TPTFAIL (FC_MR-4)

Clear the TPTFAIL (FC_MR-4) Alarm

2.7.307  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.7.308  TPTFAIL (ML100T, ML1000)

Clear the TPTFAIL (ML100T, ML1000) Alarm

2.7.309  TRMT

Clear the TRMT Alarm

2.7.310  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.311  TX-AIS

Clear the TX-AIS Condition

2.7.312  TX-RAI

Clear the TX-RAI Condition

2.7.313  UNC-WORD

Clear the UNC-WORD Condition

2.7.314  UNEQ-P

Clear the UNEQ-P Alarm

2.7.315  UNEQ-V

Clear the UNEQ-V Alarm

2.7.316  VCG-DEG

Clear the VCG-DEG Condition

2.7.317  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.318  VOA-HDEG

Clear the VOA-HDEG Alarm

2.7.319  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.7.320  VOA-LDEG

Clear the VOA-LDEG Alarm

2.7.321  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.7.322  WKSWPR

Clear the WKSWPR Condition

2.7.323  WTR

2.7.324  WVL-MISMATCH

Clear the WVL-MISMATCH alarm

2.8  DS3-12 E Line Alarms

2.9  DWDM and Non-DWDM Card LED Activity

2.9.1  DWDM Card LED Activity After Insertion

2.9.2  Non-DWDM Card LED Activity After Insertion

2.9.3  DWDM Card LED Activity During Reset

2.9.4  Non-DWDM Card LED Activity During Reset

2.9.5  Non-DWDM Cross-Connect LED Activity During Side Switch

2.9.6  Non-DWDM Card LED State After Successful Reset

2.10  Common Procedures in Alarm Troubleshooting

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

Verify or Create Node DCC Terminations

Lock Out a BLSR Span

Clear a BLSR External Switching Command

Clear a Path Protection Lockout

Switch Protection Group Traffic with an External Switching Command

Side Switch the Active and Standby XC10G Cross-Connect cards

Clear a Protection Group External Switching Command

Delete a Circuit

Clear a G-Series, OCN, MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G Loopback

Reset Active TCC2 Card and Activate Standby Card

Remove and Reinsert (Reseat) the Standby TCC2

Reset a Traffic Card in CTC

Verify BER Threshold Level

Physically Replace a Card

Remove and Reinsert (Reseat) a Card

Remove and Reinsert Fan-Tray Assembly

Alarm Troubleshooting

This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables 2-1 through 2-4 provide lists of ONS 15454 alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-8 provides a list of alarms organized by alarm type. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.

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

The troubleshooting procedure for an alarm applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log onto http://www.cisco.com/techsupport for more information or call the Cisco Technical Assistance Center (Cisco TAC) to report a service-affecting problem (1 800 553-2447).

For alarm profile information, refer to the Cisco ONS 15454 Procedure Guide.

2.1  Alarm Index by Default Severity

The following tables group alarms and conditions by the severity displayed in the CTC Alarms window in the severity (SEV) column, which is the same severity used when reported by TL1. All severities listed in this manual are the default profile settings. Alarm severities can be altered from default settings for individual alarms or groups of alarms by creating a nondefault alarm profile and applying it on a port, card, or shelf basis. All settings (default or user-defined) that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.

Note The CTC default alarm profile contains alarms that apply to multiple product platforms. The alarms that apply to this product are listed in the following tables and sections.

2.1.1  Critical Alarms (CR)

Table 2-1 lists Critical alarms.

Table 2-1 Critical Alarm Index

AUTOLSROFF

LOF (DS3)

MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

BKUPMEMP

LOF (EC1-12)

OPWR-HFAIL

CKTDOWN

LOF (OCN)

OPWR-LFAIL

COMIOXC

LOF (TRUNK)

OTUK-LOF

CTNEQPT-PBPROT

LOM for STSTRM, TRUNK

PLM-P

CTNEQPT-PBWORK

LOP-P for STSMON, STSTRM

PORT-CODE-MISM

EQPT

LOS (CLIENT)

PORT-COMM-FAIL

EQPT-MISS

LOS (DS3)

PORT-MISMATCH (for CLIENT only)

FAN

LOS (EC1-12)

PORT-MISSING

GAIN-HFAIL

LOS (OCN)

SQM for STSTRM

GAIN-LFAIL

LOS (OTS)

SWMTXMOD

GE-OOSYNC

LOS (TRUNK)

TIM (for CLIENT, TRUNK only)

HITEMP (for NE only)

LOS-P

TIM-P, for STSTRM

I-HITEMP

MEA (AIP)

UNEQ-P

IMPROPRMVL

MEA (EQPT)

VOA-HFAIL

LOA

MEA (FAN)

VOA-LFAIL

LOF (CLIENT)

—

—

2.1.2  Major Alarms (MJ)

Table 2-2 lists Major alarms.

Table 2-2 Major Alarm Index

APC-DISABLED

DUP-IPADDR

LOS (BITS)

APC-FAIL

DUP-NODENAME

LOS (DS1)

APSCM

EHIBATVG

LWBATVG

APSCNMIS

ELWBATVG

MEM-GONE

AWG-FAIL

EOC

OPTNTWMIS

AWG-OVERTEMP

EOC-L

PEER-NORESPONSE

BAT-FAIL

E-W-MISMATCH

PLM-V

BLSROSYNC

EXTRA-TRAF-PREEMPT

PRC-DUPID

CARLOSS (CLIENT)

FANDEGRADE

RCVR-MISS

CARLOSS (EQPT)

FEC-MISM

RING-ID-MIS

CARLOSS (E100T, E1000F)

GCC-EOC

RING-MISMATCH

CARLOSS (G1000)

HIBATVG

SQM for VT-TERM

CARLOSS (ML100T, ML1000)

HLDOVRSYNC

SYSBOOT

CARLOSS (TRUNK)

INC-SIGLOSS

TPTFAIL (FC_MR-4)

CONTBUS-A-18

INC-SYNCLOSS

TPTFAIL (G1000)

CONTBUS-B-18

INVMACADR

TPTFAIL (ML100T, ML1000)

CONTBUS-IO-A

LOF (BITS)

TRMT

CONTBUS-IO-B

LOF (DS1)

TRMT-MISS

DBOSYNC

LOM for VT-TERM

UNEQ-V

DSP-COMM-FAIL

LOP-V

WVL-MISMATCH

DSP-FAIL

—

—

2.1.3  Minor Alarms (MN)

Table 2-3 lists Minor alarms.

Table 2-3 Minor Alarm Index

APSB

GAIN-LDEG

OPWR-LDEG

APSCDFLTK

HI-LASERBIAS

PROTNA

APSC-IMP

HI-RXPOWER

PTIM

APSCINCON

HITEMP

PWR-REDUN

APSMM

HI-TXPOWER

RSVP-HELLODOWN

AUTORESET

KBYTE-APS-CHANNEL-FAILURE

SFTWDOWN

AUTOSW-LOP (VT-MON)

LASERBIAS-DEG

SH-INS-LOSS-VAR-DEG-HIGH

AUTOSW-UNEQ (VT-MON)

LASEREOL

SH-INS-LOSS-VAR-DEG-LOW

AWG-DEG

LASERTEMP-DEG

SNTP-HOST

CASETEMP-DEG

LMP-HELLODOWN

SSM-FAIL

COMM-FAIL

LMP-NDFAIL

SYNCPRI

DATAFLT

LO-RXPOWER

SYNCSEC

ERROR-CONFIG

LOS (FUDC)

SYNCTHIRD

EXCCOL

LO-TXPOWER

TIM-MON

EXT

MEM-LOW

TIM-P, for STSMON

FEPRLF

NOT-AUTHENTICATED

VOA-HDEG

FSTSYNC

OPTNTWMIS

VOA-LDEG

GAIN-HDEG

OPWR-HDEG

—

2.1.4  NA Conditions

Table 2-4 lists not alarmed (NA) conditions.

Table 2-4 NA Conditions Index

ALS

FRNGSYNC

OTUK-TIM

AMPLI-INIT

FULLPASSTHR-BI

OUT-OF-SYNC

APSIMP

INC-GFP-OUTOFFRAME

PDI-P

AS-CMD

INC-GFP-SIGLOSS

PORT-MISMATCH for FC_MR-4

AS-MT

INC-GFP-SYNCLOSS

RAI

AUD-LOG-LOSS

INC-ISD

RING-SW-EAST

AUD-LOG-LOW

INHSWPR

RING-SW-WEST

AUTOSW-LOP (STSMON)

INHSWWKG

RUNCFG-SAVENEED

AUTOSW-PDI

INTRUSION-PSWD

SD (CLIENT, TRUNK)

AUTOSW-SDBER

IOSCFGCOPY

SD (DS1, DS3)

AUTOSW-SFBER

KB-PASSTHR

SD-L

AUTOSW-UNEQ (STSMON)

LAN-POL-REV

SD-P

AWG-WARM-UP

LASER-APR

SF (CLIENT, TRUNK)

CLDRESTART

LASERBIAS-FAIL

SF (DS1, DS3)

CTNEQPT-MISMATCH

LASEREOL

SF-L

DS3-MISM

LKOUTPR-S

SF-P

ETH-LINKLOSS

LOCKOUT-REQ

SHUTTER-OPEN

EXERCISE-RING-FAIL

LPBKCRS

SPAN-SW-EAST

EXERCISE-SPAN-FAIL

LPBKDS1FEAC

SPAN-SW-WEST

FAILTOSW

LPBKDS1FEAC-CMD

SQUELCH

FAILTOSW-PATH

LPBKDS3FEAC

SQUELCHED

FAILTOSWR

LPBKDS3FEAC-CMD

SSM-DUS

FAILTOSWS

LPBKFACILITY (CLIENT, TRUNK)

SSM-LNC

FE-AIS

LPBKFACILITY (DS1, DS3)

SSM-OFF

FE-DS1-MULTLOS

LPBKFACILITY (EC1-12)

SSM-PRC

FE-DS1-NSA

LPBKFACILITY (G1000)

SSM-PRS

FE-DS1-SA

LPBKFACILITY (OCN)

SSM-RES

FE-DS1-SNGLLOS

LPBKTERMINAL (CLIENT, TRUNK)

SSM-SMC

FE-DS3-NSA

LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

SSM-STU

FE-DS3-SA

LPBKTERMINAL (G1000)

SSM-ST2

FE-EQPT-NSA

MAN-REQ

SSM-ST3

FE-FRCDWKSWPR-RING

MANRESET

SSM-ST3E

FE-FRCDWKSWPR-SPAN

MANSWTOINT

SSM-ST4

FE-IDLE

MANSWTOPRI

SSM-TNC

FE-LOCKOUTOFPR-SPAN

MANSWTOSEC

SWTOPRI

FE-LOF

MANSWTOTHIRD

SWTOSEC

FE-LOS

MANUAL-REQ-RING

SWTOTHIRD

FE-MANWKSWPR-RING

MANUAL-REQ-SPAN

SYNC-FREQ

FE-MANWKSWPR-SPAN

NO-CONFIG

TIM (for OCN only)

FORCED-REQ

ODUK-SD-PM

TX-RAI

FORCED-REQ-RING

ODUK-SF-PM

UNC-WORD

FORCED-REQ-SPAN

ODUK-TIM-PM

VCG-DEG

FRCDSWTOINT

OOU-TPT

VCG-DOWN

FRCDSWTOPRI

OTUK-SD

WKSWPR

FRCDSWTOSEC

OTUK-SF

WTR

FRCDSWTOTHIRD

—

—

2.1.5  NR Conditions

Table 2-5 lists not reported (NR) conditions.

Table 2-5 NR Conditions Index

AIS

ERFI-P-SRVR

OTUK-BDI

AIS-L

ODUK-AIS-PM

RFI

AIS-P

ODUK-BDI-PM

RFI-L

AIS-V

ODUK-LCK-PM

RFI-P

AUTOSW-AIS

ODUK-OCI-PM

RFI-V

ERFI-P-CONN

OTUK-AIS

TX-AIS

ERFI-P-PAYLD

—

—

2.2  Alarms and Conditions Indexed By Alphabetical Entry

Table 2-6 lists alarms and conditions by the name displayed on the CTC Alarms window or Conditions window.

Table 2-6 Alphabetical Alarm Index

AIS

FRCDSWTOINT

ODUK-OCI-PM

AIS-L

FRCDSWTOPRI

ODUK-SD-PM

AIS-P

FRCDSWTOSEC

ODUK-SF-PM

AIS-V

FRCDSWTOTHIRD

ODUK-TIM-PM

ALS

FRNGSYNC

OOU-TPT

AMPLI-INIT

FSTSYNC

OPTNTWMIS

APC-DISABLED

FULLPASSTHR-BI

OPWR-HDEG

APC-FAIL

GAIN-HDEG

OPWR-HFAIL

APSB

GAIN-HFAIL

OPWR-LDEG

APSCDFLTK

GAIN-LDEG

OPWR-LFAIL

APSC-IMP

GAIN-LFAIL

OTUK-AIS

APSCINCON

GCC-EOC

OTUK-BDI

APSCM

GE-OOSYNC

OTUK-LOF

APSCNMIS

HIBATVG

OTUK-SD

APSIMP

HI-LASERBIAS

OTUK-SF

APSMM

HI-RXPOWER

OTUK-TIM

AS-CMD

HITEMP

OUT-OF-SYNC

AS-MT

HI-TXPOWER

PDI-P

AUD-LOG-LOSS

HLDOVRSYNC

PEER-NORESPONSE

AUD-LOG-LOW

I-HITEMP

PLM-P

AU-LOF

IMPROPRMVL

PLM-V

AUTOLSROFF

INC-GFP-OUTOFFRAME

PORT-CODE-MISM

AUTORESET

INC-GFP-SIGLOSS

PORT-COMM-FAIL

AUTOSW-AIS

INC-GFP-SYNCLOSS

PORT-MISMATCH

AUTOSW-LOP (STSMON)

INC-ISD

PORT-MISSING

AUTOSW-LOP (VT-MON)

INC-SIGLOSS

PRC-DUPID

AUTOSW-PDI

INC-SYNCLOSS

PROTNA

AUTOSW-SDBER

INC-ISD

PTIM

AUTOSW-SFBER

INHSWPR

PWR-REDUN

AUTOSW-UNEQ (STSMON)

INHSWWKG

RAI

AUTOSW-UNEQ (VT-MON)

INTRUSION-PSWD

RCVR-MISS

AWG-DEG

INVMACADR

RFI

AWG-FAIL

IOSCFGCOPY

RFI-L

AWG-OVERTEMP

KB-PASSTHR

RFI-P

AWG-WARM-UP

KBYTE-APS-CHANNEL-FAILURE

RFI-V

BAT-FAIL

LAN-POL-REV

RING-ID-MIS

BKUPMEMP

LASER-APR

RING-MISMATCH

BLSROSYNC

LASERBIAS-DEG

RING-SW-EAST

CARLOSS (CLIENT)

LASERBIAS-FAIL

RING-SW-WEST

CARLOSS (EQPT)

LASEREOL

RSVP-HELLODOWN

CARLOSS (E100T, E1000F)

LASERTEMP-DEG

RUNCFG-SAVENEED

CARLOSS (G1000)

LKOUTWK-S (NA)

SD (CLIENT, TRUNK)

CARLOSS (ML100T, ML1000)

LKOUTPR-S

SD (DS1, DS3)

CARLOSS (TRUNK)

LMP-HELLODOWN

SD-L

CASETEMP-DEG

LMP-NDFAIL

SD-P

CKTDOWN

LOA

SF (CLIENT, TRUNK)

CLDRESTART

LOCKOUT-REQ

SF (DS1, DS3)

COMIOXC

LOF (BITS)

SF-L

COMM-FAIL

LOF (CLIENT)

SF-P

CONTBUS-A-18

LOF (DS1)

SFTWDOWN

CONTBUS-B-18

LOF (DS3)

SH-INS-LOSS-VAR-DEG-HIGH

CONTBUS-IO-A

LOF (EC1-12)

SH-INS-LOSS-VAR-DEG-LOW

CONTBUS-IO-B

LOF (OCN)

SHUTTER-OPEN

CTNEQPT-MISMATCH

LOF (TRUNK)

SNTP-HOST

CTNEQPT-PBPROT

LOM

SPAN-SW-EAST

CTNEQPT-PBWORK

LOP-P

SPAN-SW-WEST

DATAFLT

LOP-V

SQUELCH

DBOSYNC

LO-RXPOWER

SQUELCHED

DSP-COMM-FAIL

LO-TXPOWER

SQM

DSP-FAIL

LOS (BITS)

SSM-DUS

DS3-MISM

LOS (CLIENT)

SSM-FAIL

DUP-IPADDR

LOS (DS1)

SSM-LNC

DUP-NODENAME

LOS (DS3)

SSM-OFF

EHIBATVG

LOS (EC1-12)

SSM-PRC

ELWBATVG

LOS (FUDC)

SSM-PRS

EOC

LOS (OCN)

SSM-RES

EOC-L

LOS (OTS)

SSM-SDH-TN

EQPT

LOS (TRUNK)

SSM-SETS

EQPT-MISS

LOS-P

SSM-SMC

ERFI-P-CONN

LPBKCRS

SSM-ST2

ERFI-P-PAYLD

LPBKDS1FEAC

SSM-ST3

ERFI-P-SRVR

LPBKDS1FEAC-CMD

SSM-ST3E

ERROR-CONFIG

LPBKDS3FEAC

SSM-ST4

ETH-LINKLOSS

LPBKDS3FEAC-CMD

SSM-STU

E-W-MISMATCH

LPBKFACILITY (DS1, DS3)

SSM-TNC

EXCCOL

LPBKFACILITY (CLIENT, TRUNK)

SWMTXMOD

EXERCISE-RING-FAIL

LPBKFACILITY (EC1-12)

SWTOPRI

EXERCISE-SPAN-FAIL

LPBKFACILITY (G1000)

SWTOSEC

EXT

LPBKFACILITY (OCN)

SWTOTHIRD

EXTRA-TRAF-PREEMPT

LPBKTERMINAL (CLIENT, TRUNK)

SYNC-FREQ

FAILTOSW

LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

SYNCPRI

FAILTOSW-PATH

LPBKTERMINAL (G1000)

SYNCSEC

FAILTOSWR

LWBATVG

SYNCTHIRD

FAILTOSWS

MAN-REQ

SYSBOOT

FAN

MANRESET

TIM

FANDEGRADE

MANSWTOINT

TIM-MON

FE-AIS

MANSWTOPRI

TIM-P

FEC-MISM

MANSWTOSEC

TPTFAIL (FC_MR-4)

FE-DS1-MULTLOS

MANSWTOTHIRD

TPTFAIL (G1000)

FE-DS1-NSA

MANUAL-REQ-RING

TPTFAIL (ML100T, ML1000)

FE-DS1-SA

MANUAL-REQ-SPAN

TRMT

FE-DS1-SNGLLOS

MEA (AIP)

TRMT-MISS

FE-DS3-NSA

MEA (EQPT)

TX-AIS

FE-DS3-SA

MEA (FAN)

TX-RAI

FE-EQPT-NSA

MEM-GONE

UNC-WORD

FE-FRCDWKSWPR-RING

MEM-LOW

UNEQ-P

FE-FRCDWKSWPR-SPAN

MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

UNEQ-V

FE-IDLE

NO-CONFIG

VCG-DEG

FE-LOCKOUTOFPR-SPAN

NOT-AUTHENTICATED

VCG-DOWN

FE-LOF

NTWTPINC

VOA-HDEG

FE-LOS

OCHNC-ACTIV-FAIL

VOA-HFAIL

FE-MANWKSWPR-RING

OCHNC-DEACTIV-FAIL

VOA-LDEG

FE-MANWKSWPR-SPAN

OCHNC-FAIL

VOA-LFAIL

FEPRLF

OCHNC-INC

WKSWPR

FORCED-REQ

ODUK-AIS-PM

WTR

FORCED-REQ-RING

ODUK-BDI-PM

WVL-MISMATCH

FORCED-REQ-SPAN

ODUK-LCK-PM

—

2.3  Logical Object Type Definitions

ONS 15454 alarms are grouped according to their logical object types in alarm profile listings (for example OCN::LOS). Each alarm entry in this chapter lists its type. These 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.

Table 2-7 Alarm Type/Object Definition

AICI-AEP

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

AICI-AIE

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

AIP

Auxiliary interface protection module.

AOTS

Amplified optical transport section.

BITS

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

BPLANE

The backplane.

CLIENT

The low-speed port, such as a transponder (TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G) or muxponder (MXP_2.5G_10G), where the optical signal is dropped.

DS1

A DS-1 line on a DS-1 card.

DS3

A DS-3 line on a DS-3 card.

EC1-12

An EC1-12 line on an EC1-12 card.

ENVALRM

An environmental alarm port.

EQPT

A card in any of the eight non-common 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, STS, and VT.

EXT-SREF

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

E100T

An E100 Ethernet card (E100T-12, E100T-G).

E1000F

An E1000 Ethernet card (E1000-2, E1000-2G).

FAN

Fan-tray assembly.

FCMR

An FC_MR-4 Fibre Channel card, not currently used in this release.

FUDC

SONET F1 byte user data channel.

G1000

A G1000 Ethernet card (G1000-4).

ML100T

An ML100 card (ML100T-12).

ML1000

An ML1000 Ethernet card (ML1000-2).

NE

The entire network element.

NE-SYNCH

Represents the timing status of the NE.

OCH

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

OCN

An OC-N line on an OC-N card.

OMS

Optical multiplex section.

OTN

Optical transport network.

OSC-RING

Optical service channel ring.

PWR

Power.

STSMON

STS alarm detection at the monitor point (upstream from the cross-connect).

STSTRM

STS alarm detection at termination (downstream from the cross-connect).

TRUNK

The optical or dense wavelength division multiplexing (DWDM) card carrying the high-speed signal.

UCP-IPCC

Unified control plane (UCP) communication channel.

UCP-CKT

UCP circuit.

VCG

VT concatenation.

VT-MON

VT1 alarm detection at the monitor point (upstream from the cross-connect).

VT-TERM

VT1 alarm detection at termination (downstream from the cross-connect).

2.4  Alarm Index by Logical Object Type

Table 2-8 gives the name and page number of every alarm in the chapter, organized by logical object type.

Note This alarm profile list is taken directly from the CTC interface. Some items do not appear in alphabetical order.

Table 2-8 Alarm Index by Alarm Type

AICI-AEP: EQPT

EQPT: MANRESET

OCN: SSM-STU

AICI-AEP: MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

EQPT: MEA (EQPT)

OCN: SSM-TNC

AICI-AIE: EQPT

MEM-GONE

OCN: SYNC-FREQ

AICI-AIE: MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

EQPT:MEM-LOW

OCN: TIM

AIP: INVMACADR

EQPT: NO-CONFIG

OCN: WKSWPR

AIP: MEA (AIP)

EQPT: PEER-NORESPONSE

OCN: WTR

AIP: MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

EQPT: PROTNA

OMS: AS-CMD

AOTS: AMPLI-INIT

EQPT: PWR-REDUN

OMS: AS-MT

AOTS: AS-CMD

EQPT: RUNCFG-SAVENEED

OMS: OPWR-HDEG

AOTS: AS-MT

EQPT: SFTWDOWN

OMS: OPWR-HFAIL

AOTS: CASETEMP-DEG

EQPT: SWMTXMOD

OMS: OPWR-LDEG

AOTS: FIBERTEMP-DEG

EQPT: WKSWPR

OMS: OPWR-LFAIL

AOTS: GAIN-HDEG

EQPT: WTR

OMS: VOA-HDEG

AOTS: GAIN-HFAIL

EXT-SREF: FRCDSWTOPRI

OMS: VOA-HFAIL

AOTS: GAIN-LDEG

EXT-SREF: FRCDSWTOSEC

OMS: VOA-LDEG

AOTS: GAIN-LFAIL

EXT-SREF: FRCDSWTOTHIRD

OMS: VOA-LFAIL

AOTS: LASER-APR

EXT-SREF: MANSWTOPRI

OSC-RING: NTWTPINC

AOTS: LASERBIAS-DEG

EXT-SREF: MANSWTOSEC

OSC-RING: RING-ID-MIS

AOTS: LASERBIAS-FAIL

EXT-SREF: MANSWTOTHIRD

OTS: AS-CMD

AOTS: LASERTEMP-DEG

EXT-SREF: SWTOPRI

OTS: AS-MT

AOTS: OPWR-HDEG

EXT-SREF: SWTOSEC

OTS: AWG-DEG

AOTS: OPWR-HFAIL

EXT-SREF: SWTOTHIRD

OTS: AWG-FAIL

AOTS: OPWR-LDEG

EXT-SREF: SYNCPRI

OTS: AWG-OVERTEMP

AOTS: OPWR-LFAIL

EXT-SREF: SYNCSEC

OTS: AWG-WARM-UP

AOTS: VOA-HDEG

EXT-SREF: SYNCTHIRD

OTS: LASERBIAS-DEG

AOTS: VOA-HFAIL

FAN: EQPT-MISS

OTS: LOS (OTS)

AOTS: VOA-LDEG

FAN: FAN

OTS: OPWR-HDEG

AOTS: VOA-LFAIL

FAN: FANDEGRADE

OTS: OPWR-HFAIL

BITS: AIS

FAN: MEA (FAN)

OTS: OPWR-LDEG

BITS: LOF (BITS)

FAN: MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

OTS: OPWR-LFAIL

BITS: LOS (BITS)

FCMR: AS-CMD

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

BITS: SSM-DUS

FCMR: AS-MT

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

BITS: SSM-FAIL

FCMR: INC-GFP-OUTOFFRAME

OTS: SHUTTER-OPEN

BITS: SSM-OFF

FCMR: INC-GFP-SIGLOSS

OTS: VOA-HDEG

BITS: SSM-PRS

FCMR: INC-GFP-SYNCLOSS

OTS: VOA-HFAIL

BITS: SSM-RES

FCMR: INC-SIGLOSS

OTS: VOA-LDEG

BITS: SSM-SMC

FCMR: INC-SYNCLOSS

OTS: VOA-LFAIL

BITS: SSM-ST2

FCMR: PORT-MISMATCH

PWR: AS-CMD

BITS: SSM-ST3

FCMR: TPTFAIL (FC_MR-4)

PWR: BAT-FAIL

BITS: SSM-ST3E

FUDC: AIS

PWR: EHIBATVG

BITS: SSM-ST4

FUDC: LOS (FUDC)

PWR: ELWBATVG

BITS: SSM-STU

G1000: AS-CMD

PWR: HIBATVG

BITS: SSM-TNC

G1000: AS-MT

PWR: LWBATVG

BITS: SYNC-FREQ

G1000: CARLOSS (G1000)

STSMON: AIS-P

BPLANE: AS-CMD

G1000: LPBKFACILITY (G1000)

STSMON: AUTOSW-AIS

BPLANE: MFGMEM (AICI-AEP, AICI-AIE, BPLANE, FAN)

G1000: LPBKTERMINAL (G1000)

STSMON: AUTOSW-LOP (STSMON)

CLIENT: AIS

G1000: TPTFAIL (G1000)

STSMON: AUTOSW-PDI

CLIENT: ALS

ML1000: AS-CMD

STSMON: AUTOSW-SDBER

CLIENT: AS-CMD

ML1000: CARLOSS (ML100T, ML1000)

STSMON: AUTOSW-SFBER

CLIENT: AS-MT

ML1000: TPTFAIL (ML100T, ML1000)

STSMON: AUTOSW-UNEQ (STSMON)

CLIENT: CARLOSS (CLIENT)

ML100T: AS-CMD

STSMON: ERFI-P-CONN

CLIENT: EOC

ML100T: CARLOSS (ML100T, ML1000)

STSMON: ERFI-P-PAYLD

CLIENT: EOC-L

ML100T: TPTFAIL (ML100T, ML1000)

STSMON: ERFI-P-SRVR

CLIENT: FAILTOSW

MSUDC: AIS

STSMON: FAILTOSW-PATH

CLIENT: FORCED-REQ-SPAN

MSUDC: LOS (MSUDC)

STSMON: FORCED-REQ

CLIENT: GE-OOSYNC

NE-SREF: FRCDSWTOINT

STSMON: LOCKOUT-REQ

CLIENT: HI-LASERBIAS

NE-SREF: FRCDSWTOPRI

STSMON: LOP-P

CLIENT: HI-RXPOWER

NE-SREF: FRCDSWTOSEC

STSMON: LPBKCRS

CLIENT: HI-TXPOWER

NE-SREF: FRCDSWTOTHIRD

STSMON: MAN-REQ

CLIENT: LO-RXPOWER

NE-SREF: FRNGSYNC

STSMON: PDI-P

CLIENT: LO-TXPOWER

NE-SREF: FSTSYNC

STSMON: PLM-P

CLIENT: LOCKOUT-REQ

NE-SREF: HLDOVRSYNC

STSMON: RFI-P

CLIENT: LOF (CLIENT)

NE-SREF: MANSWTOINT

STSMON: SD-P

CLIENT: LOS (CLIENT)

NE-SREF: MANSWTOPRI

STSMON: SF-P

CLIENT: LPBKFACILITY (CLIENT, TRUNK)

NE-SREF: MANSWTOSEC

STSMON: TIM-P

CLIENT: LPBKTERMINAL (CLIENT, TRUNK)

NE-SREF: MANSWTOTHIRD

STSMON: UNEQ-P

CLIENT: MANUAL-REQ-SPAN

NE-SREF: SSM-PRS

STSMON: WKSWPR

CLIENT: OUT-OF-SYNC

NE-SREF: SSM-RES

STSMON: WTR

CLIENT: PORT-CODE-MISM

NE-SREF: SSM-SMC

STSTRM: AIS-P

CLIENT: PORT-COMM-FAIL

NE-SREF: SSM-ST2

STSTRM: AU-LOF

CLIENT: PORT-MISMATCH

NE-SREF: SSM-ST3

STSTRM: ERFI-P-CONN

CLIENT: PORT-MISSING

NE-SREF: SSM-ST3E

STSTRM: ERFI-P-PAYLD

CLIENT: RFI

NE-SREF: SSM-ST4

STSTRM: ERFI-P-SRVR

CLIENT: SD (CLIENT, TRUNK)

NE-SREF: SSM-STU

STSTRM: LOM

CLIENT: SF (CLIENT, TRUNK)

NE-SREF: SSM-TNC

STSTRM: LOP-P

CLIENT: SQUELCHED

NE-SREF: SWTOPRI

STSTRM: OOU-TPT

CLIENT: SSM-DUS

NE-SREF: SWTOSEC

STSTRM: PDI-P

CLIENT: SSM-FAIL

NE-SREF: SWTOTHIRD

STSTRM: PLM-P

CLIENT: SSM-LNC

NE-SREF: SYNCPRI

STSTRM: RFI-P

CLIENT: SSM-OFF

NE-SREF: SYNCSEC

STSTRM: SD-P

CLIENT: SSM-PRC

NE-SREF: SYNCTHIRD

STSTRM: SF-P

CLIENT: SSM-PRS

NE: APC-DISABLED

STSTRM: SQM

CLIENT: SSM-RES

NE: APC-FAIL

STSTRM: TIM-P

CLIENT: SSM-SDH-TN

NE: AS-CMD

STSTRM: UNEQ-P

CLIENT: SSM-SETS

NE: AUD-LOG-LOSS

TRUNK: AIS

CLIENT: SSM-SMC

NE: AUD-LOG-LOW

TRUNK: ALS

CLIENT: SSM-ST2

NE: DATAFLT

TRUNK: AS-CMD

CLIENT: SSM-ST3

NE: DBOSYNC

TRUNK: AS-MT

CLIENT: SSM-ST3E

NE: DUP-IPADDR

TRUNK: CARLOSS (TRUNK)

CLIENT: SSM-ST4

NE: DUP-NODENAME

TRUNK: DSP-COMM-FAIL

CLIENT: SSM-STU

NE: ETH-LINKLOSS

TRUNK: DSP-FAIL

CLIENT: SSM-TNC

NE: HITEMP

TRUNK: EOC

CLIENT: SYNC-FREQ

NE: I-HITEMP

TRUNK: EOC-L

CLIENT: TIM

NE: INTRUSION-PSWD

TRUNK: FAILTOSW

CLIENT: TIM-MON

NE: LAN-POL-REV

TRUNK: FEC-MISM

CLIENT: WKSWPR

NE: OPTNTWMIS

TRUNK: FORCED-REQ-SPAN

CLIENT: WTR

NE: SNTP-HOST

TRUNK: GCC-EOC

DS1: AIS

NE: SYSBOOT

TRUNK: GE-OOSYNC

DS1: AS-CMD

OCH: AS-CMD

TRUNK: HI-LASERBIAS

DS1: AS-MT

OCH: AS-MT

TRUNK: HI-RXPOWER

DS1: LOF (DS1)

OCH: OPWR-HDEG

TRUNK: HI-TXPOWER

DS1: LOS (DS1)

OCH: OPWR-HFAIL

TRUNK: LO-RXPOWER

DS1: LPBKDS1FEAC

OCH: OPWR-LDEG

TRUNK: LO-TXPOWER

DS1: LPBKDS1FEAC-CMD

OCH: OPWR-LFAIL

TRUNK: LOCKOUT-REQ

DS1: LPBKFACILITY (DS1, DS3)

OCH: VOA-HDEG

TRUNK: LOF (TRUNK)

DS1: LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

OCH: VOA-HFAIL

TRUNK: LOM

DS1: RAI

OCH: VOA-LDEG

TRUNK: LOS (TRUNK)

DS1: RCVR-MISS

OCH: VOA-LFAIL

TRUNK: LOS-P

DS1: SD (DS1, DS3)

OCHNC-CONN: OCHNC-ACTIV-FAIL

TRUNK: LPBKFACILITY (CLIENT, TRUNK)

DS1: SF (DS1, DS3)

OCHNC-CONN: OCHNC-DEACTIV-FAIL

TRUNK: LPBKTERMINAL (CLIENT, TRUNK)

DS1: TRMT

OCHNC-CONN: OCHNC-FAIL

TRUNK: MANUAL-REQ-SPAN

DS1: TRMT-MISS

OCHNC-CONN: OCHNC-INC

TRUNK: ODUK-AIS-PM

DS1: TX-AIS

OCN: AIS-L

TRUNK: ODUK-BDI-PM

DS1: TX-RAI

OCN: ALS

TRUNK: ODUK-LCK-PM

DS3: AIS

OCN: APSB

TRUNK: ODUK-OCI-PM

DS3: AS-CMD

OCN: APSC-IMP

TRUNK: ODUK-SD-PM

DS3: AS-MT

OCN: APSCDFLTK

TRUNK: ODUK-SF-PM

DS3: DS3-MISM

OCN: APSCINCON

TRUNK: ODUK-TIM-PM

DS3: FE-AIS

OCN: APSCM

TRUNK: OTUK-AIS

DS3: FE-DS1-MULTLOS

OCN: APSCNMIS

TRUNK: OTUK-BDI

DS3: FE-DS1-NSA

OCN: APSIMP

TRUNK: OTUK-LOF

DS3: FE-DS1-SA

OCN: APSMM

TRUNK: OTUK-SD

DS3: FE-DS1-SNGLLOS

OCN: AS-CMD

TRUNK: OTUK-LOF

DS3: FE-DS3-NSA

OCN: AS-MT

TRUNK: OTUK-TIM

DS3: FE-DS3-SA

OCN: AUTOLSROFF

TRUNK: OUT-OF-SYNC

DS3: FE-EQPT-NSA

OCN: BLSROSYNC

TRUNK: PTIM

DS3: FE-IDLE

OCN: E-W-MISMATCH

TRUNK: RFI

DS3: FE-LOF

OCN: EOC

TRUNK: SD (CLIENT, TRUNK)

DS3: FE-LOS

OCN: EOC-L

TRUNK: SF (DS1, DS3)

DS3: INC-ISD

OCN: EXERCISE-RING-FAIL

TRUNK: SSM-DUS

DS3: LOF (DS3)

OCN: EXERCISE-SPAN-FAIL

TRUNK: SSM-FAIL

DS3: LOS (DS3)

OCN: EXTRA-TRAF-PREEMPT

TRUNK: SSM-LNC

DS3: LPBKDS1FEAC

OCN: FAILTOSW

TRUNK: SSM-OFF

DS3: LPBKDS3FEAC

OCN: FAILTOSWR

TRUNK: SSM-PRC

DS3: LPBKDS3FEAC-CMD

OCN: FAILTOSWS

TRUNK: SSM-PRS

DS3: LPBKFACILITY (DS1, DS3)

OCN: FE-FRCDWKSWPR-RING

TRUNK: SSM-RES

DS3: LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

OCN: FE-FRCDWKSWPR-SPAN

TRUNK: SSM-SDH-TN

DS3: RAI

OCN: FE-LOCKOUTOFPR-SPAN

TRUNK: SSM-SETS

DS3: SD (DS1, DS3)

OCN: FE-MANWKSWPR-RING

TRUNK: SSM-SMC

DS3: SF (DS1, DS3)

OCN: FE-MANWKSWPR-SPAN

TRUNK: SSM-ST2

E1000F: AS-CMD

OCN: FEPRLF

TRUNK: SSM-ST3

E1000F: CARLOSS (E100T, E1000F)

OCN: FORCED-REQ-RING

TRUNK: SSM-ST3E

E100T: AS-CMD

OCN: FORCED-REQ-SPAN

TRUNK: SSM-ST4

E100T: CARLOSS (E100T, E1000F)

OCN: FULLPASSTHR-BI

TRUNK: SSM-STU

EC1-12: AIS-L

OCN: HI-LASERBIAS

TRUNK: SSM-TNC

EC1-12: AS-CMD

OCN: HI-RXPOWER

TRUNK: SYNC-FREQ

EC1-12: AS-MT

OCN: HI-TXPOWER

TRUNK: TIM

EC1-12: LOF (EC1-12)

OCN: KB-PASSTHR

TRUNK: TIM-MON

EC1-12: LOS (EC1-12)

OCN: KBYTE-APS-CHANNEL-FAILURE

TRUNK: UNC-WORD

EC1-12: LPBKFACILITY (EC1-12)

OCN: LASEREOL

TRUNK: WKSWPR

EC1-12: LPBKFACILITY (EC1-12)

OCN: LKOUTPR-S

TRUNK: WTR

EC1-12: RFI-L

OCN: LO-RXPOWER

TRUNK: WVL-MISMATCH

EC1-12: SD-L

OCN: LO-TXPOWER

UCP-CKT: CKTDOWN

EC1-12: SF-L

OCN: LOCKOUT-REQ

UCP-IPCC: LMP-HELLODOWN

ENVALRM: EXT

OCN: LOF (OCN)

UCP-IPCC: LMP-NDFAIL

EQPT: AS-CMD

OCN: LOS (OCN)

UCP-NBR: RSVP-HELLODOWN

EQPT: AUTORESET

OCN: LPBKFACILITY (OCN)

VCG: LOA

EQPT: BKUPMEMP

OCN: LPBKTERMINAL (DS1, DS3, EC-1-12, OCN)

VCG: VCG-DEG

EQPT: CARLOSS (EQPT)

OCN: MANUAL-REQ-RING

VCG: VCG-DOWN

EQPT: CLDRESTART

OCN: MANUAL-REQ-SPAN

VT-MON: AIS-V

EQPT: COMIOXC

OCN: PRC-DUPID

VT-MON: AUTOSW-AIS

EQPT: COMM-FAIL

OCN: RFI-L

VT-MON: AUTOSW-LOP (VT-MON)

EQPT: CONTBUS-A-18

OCN: RING-ID-MIS

VT-MON: AUTOSW-UNEQ (VT-MON)

EQPT: CONTBUS-B-18

OCN: RING-MISMATCH

VT-MON: FAILTOSW-PATH

EQPT: CONTBUS-IO-A

OCN: RING-SW-EAST

VT-MON: FORCED-REQ

EQPT: CONTBUS-IO-B

OCN: RING-SW-WEST

VT-MON: LOCKOUT-REQ

EQPT: CTNEQPT-MISMATCH

OCN: SD-L

VT-MON: LOP-V

EQPT: CTNEQPT-PBPROT

OCN: SF-L

VT-MON: MAN-REQ

EQPT: CTNEQPT-PBWORK

OCN: SPAN-SW-EAST

VT-MON: UNEQ-V

EQPT: EQPT

OCN: SPAN-SW-WEST

VT-MON: WKSWPR

EQPT: ERROR-CONFIG

OCN: SQUELCH

VT-MON: WTR

EQPT: EXCCOL

OCN: SSM-DUS

VT-TERM: AIS-V

EQPT: FAILTOSW

OCN: SSM-FAIL

VT-TERM: LOM

EQPT: FORCED-REQ

OCN: SSM-OFF

VT-TERM: LOP-V

EQPT: HITEMP

OCN: SSM-PRS

VT-TERM: OOU-TPT

EQPT: IMPROPRMVL

OCN: SSM-RES

VT-TERM: PLM-V

EQPT: INHSWPR

OCN: SSM-SMC

VT-TERM: RFI-V

EQPT: INHSWWKG

OCN: SSM-ST2

VT-TERM: SD-P

EQPT: IOSCFGCOPY

OCN: SSM-ST3

VT-TERM: SF-P

EQPT: LOCKOUT-REQ

OCN: SSM-ST3E

VT-TERM: SQM

EQPT: MAN-REQ

OCN: SSM-ST4

VT-TERM: UNEQ-V

2.5  Trouble Notifications

The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The ONS 15454 reports alarmed trouble notifications and Not-Alarmed (NA) notifications, if selected, in the CTC Alarms window. Alarms typically signify a problem that the user needs to fix, such as a loss of signal (LOS), while Not-Alarmed (NA) notifications do not necessarily need immediate troubleshooting.

Telcordia further divides alarms into Service-Affecting (SA) and NSA status. A Service-Affecting (SA) failure affects a provided service or the network's ability to provide service. For example, the "TRMT-MISS" alarm on page 2-199 is characterized by default as an SA failure. TRMT-MISS occurs when a cable connector is removed from an active DS-1 card port. The default severity assumes that service has been interrupted or moved. If the DS-1 card is in a protection group and the traffic is on the protect card rather than the working card, or if the port with the TRMT-MISS alarm has no circuits provisioned, TRMT-MISS would be raised as NSA because traffic was not interrupted or moved.

2.5.1  Conditions

The term "Condition" refers to any problem detected on an ONS 15454 shelf whether or not the problem is reported (that is, whether or not it generates a trouble notification). Reported conditions include alarms, Not-Alarmed conditions, and Not-Reported (NR) conditions. A snapshot of all current raised conditions on a node, whether they are reported or not, can be retrieved using the CTC Conditions window or using TL1's set of RTRV-COND commands. You can see the actual reporting messages for alarms and NAs in the CTC History tab.

For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.

2.5.2  Severities

The ONS 15454 uses Telcordia standard severities: Critical (CR), Major (MJ), and Minor (MN). Non-Service Affecting (NSA) alarms always have a Minor (MN) severity. Service-Affecting (SA) alarms can be Critical (CR), Major (MJ), or Minor (MN). Critical alarms generally indicate severe, service-affecting trouble that needs immediate correction. A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For SONET signal alarms, loss of traffic on more than five DS-1 circuits is Critical. Loss of traffic on one to five DS-1 circuits is Major (MJ). Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.

An example of a Non-Service Affecting (NSA) alarm is the "FSTSYNC" condition on page 2-93 (Fast Start Synchronization Mode), which indicates the ONS 15454 is choosing a new timing reference because the previously used reference has failed. The user needs to troubleshoot the loss of the prior timing source, but the loss is not immediately disruptive to service.

Telcordia standard severities are the default settings for the ONS 15454. A user can customize ONS 15454 alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the Cisco ONS 15454 Procedure Guide.

This chapter lists the default profile alarm severity for the Service-Affecting (SA) case of each alarm when it is applicable. Any alarm with a profile value of Critical (CR) or Major (MJ) will, if reported as Non-Service Affecting (NSA) because no traffic is lost, be reported with a Minor (MN) severity instead, in accordance with Telcordia rules.

2.6  Safety Summary

This section covers safety considerations designed to ensure safe operation of the ONS 15454. 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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

Warning Class 1 laser product.

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

2.7  Alarm 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 is not indented. If it is, click it to turn it off. When you are done checking for alarms, click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the Cisco ONS 15454 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 Cisco ONS 15454 Procedure Guide.

2.7.1  AIS

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: BITS, CLIENT, DS1, DS3, FUDC, MSUDC, TRUNK

Note The MSUDC object is not supported in this platform in this release. It is reserved for future development.

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

Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees 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.

Note DS-3 and EC-1 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.

Clear the AIS Condition

Step 1 Determine whether there are alarms on the upstream nodes and equipment, especially the "LOS (OCN)" alarm on page 2-129, or out-of-service (OOS) ports.

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

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

2.7.2  AIS-L

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: EC1-12, OCN

The AIS Line (AIS-L) condition indicates that this node is detecting line-level AIS in the incoming signal.

Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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-L Condition

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

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

2.7.3  AIS-P

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: STSMON, STSTRM

The AIS Path (AIS-P) condition means that this node is detecting AIS in the incoming path.

Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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-P Condition

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

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

2.7.4  AIS-V

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: VT-MON, VT-TERM

The AIS Virtual Tributary (VT) condition (AIS-V) means that this node is detecting AIS in the incoming VT-level path.

Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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.

See the "AIS-V on DS3XM-6 Unused VT Circuits" section on page 1-89 for more information.

Clear the AIS-V Condition

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

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

2.7.5 ALS

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Objects: CLIENT, OCN, TRUNK

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

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

2.7.6  AMPLI-INIT

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: AOTS

The Amplifier Initialized (AMPLI-INIT) condition occurs when a DWDM amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition is typically raised with the "APC-DISABLED" alarm on page 2-21.

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 Cisco ONS 15454 Procedure Guide.

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

2.7.7  APC-DISABLED

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The Automatic Power Control (APC) Disabled (APC-DISABLED) alarm occurs when the information related to the number of channels is not reliable. The alarm can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-66, the "IMPROPRMVL" alarm on page 2-102, or the "MEA (EQPT)" alarm on page 2-145. If the alarm occurs with the creation of the first circuit, delete and recreate it.

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 alarm does not clear, complete the "Delete a Circuit" procedure and then recreate it.

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

2.7.8  APC-FAIL

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The APC Failure (APC-FAIL) alarm occurs when APC has not been able to create a setpoint on a node because it has exceeded all allocated power margins including gain, power, or attenuation. These power margins (from 0 dB to 3 dB) are allocated when the network is installed. Margins can be consumed due to fiber aging or the insertion of unexpected extra loss in the span after a fiber cut.

Clear the APC-FAIL Alarm

Step 1 Determine whether the increased margin use is due to fiber aging:

a. Complete the task for checking OSC span attenuation in the Cisco ONS 15454 Procedure Guide Chapter 7, "Turn Up DWDM Network."

b. Obtain the original MetroPlanner *.cmn file, then cross-reference original span values with current ones (obtained in CTC) to determine whether a loss of 0 dB to 3dB or more has occurred across the questioned span. To obtain current values, complete the procedure for verifying optical receive power in the Cisco ONS 15454 Procedure Guide Chapter 7, "Turn Up DWDM Network."

c. On the degraded span, test fiber integrity by using optical testing equipment to verify port levels. Then verify these levels against each termination listed in CTC. To do this, complete the task for verifying DWDM card parameters in the Cisco ONS 15454 Procedure Guide Chapter 7, "Turn Up DWDM Network."

Note Throughout this trouble isolation process, ensure that safe and proper fiber cleaning and scoping procedures are used. Follow established site practices or, if none exists, complete the procedure for cleaning fiber connectors in the Cisco ONS 15454 Procedure Guide Chapter 17, "Maintain the Node."

Step 2 If the span problem is due to aged fiber, replace it by completing the task to install fiber optic cables on DWDM cards in the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

Step 3 If the trouble is not due to aging but to a fiber cut:

a. Verify the alarms by completing the procedure for viewing alarms, history, events and conditions in the Cisco ONS 15454 Procedure Guide Chapter 9, "Manage Alarms."

b. Complete the procedures in the "Identify Points of Failure on an Optical Circuit Path" section on page 1-37.

c. Resolve the issue and alarm by completing the procedure to verify the optical receive power in the Cisco ONS 15454 Procedure Guide Chapter 7, "Turn Up DWDM Network."

d. If the LOS alarm is raised against a relevant OCN object, complete the "Clear the LOS (OCN) Alarm" procedure.

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

2.7.9  APSB

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

The Automatic Protection Switching (APS) Channel Byte Failure (APSB) alarm occurs when line terminating equipment detects protection switching byte failure or an invalid code in the incoming APS signal. Some older, non-Cisco SONET nodes send invalid APS codes if they are configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15454. These invalid codes causes an APSB on an ONS node.

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 may 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 may need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Card" procedure.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

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

2.7.10  APSC-IMP

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

An Improper APS Code (APSC-IMP) alarm indicates bad or invalid K bytes. APSC-IMP occurs on OC-N cards in an MS-SPRing configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.

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

Note This alarm can occur when the exercise command or a Lock Out is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.

Clear the APSC-IMP Alarm

Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.

For specific procedures to use the test set equipment, consult the manufacturer.

If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.

Step 2 If the K byte is valid, complete the "Identify a BLSR Ring Name or Node ID Number" procedure.

Step 3 Repeat Step 2 for all nodes in the ring.

Step 4 If a node has a ring name number that does not match the other nodes, complete the "Change a BLSR Ring Name" procedure to make the ring names identical.

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

2.7.11  APSCDFLTK

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

The APS Default K Byte Received (APSCDFLTK) alarm occurs when a bidirectional line switched ring (BLSR) is not properly configured, for example, when a four-node BLSR has one node configured as a path protection. When this misconfiguration occurs, a node in a path protection or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.

Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "BLSROSYNC" alarm on page 2-39.

Clear the APSCDFLTK Alarm

Step 1 Complete the "Identify a BLSR Ring Name or Node ID Number" procedure to verify that each node has a unique node ID number.

Step 2 Repeat Step 1 for all nodes in the ring.

Step 3 If two nodes have the same node ID number, complete the "Change a BLSR Node ID Number" procedure to change one node's ID number so that each node ID is unique.

Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" alarm on page 2-70.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 Procedure Guide provides a procedure for fibering BLSRs.

Step 5 If the alarm does not clear and if the network is a four-fiber BLSR, ensure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if a working fiber is incorrectly attached to a protection fiber.

Step 6 If the alarm does not clear, complete the "Verify Node Visibility for Other Nodes" procedure.

Step 7 If nodes are not visible, complete the "Verify or Create Node DCC Terminations" procedure to ensure that SONET data communications channel (DCC) terminations exist on each node.

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

2.7.12  APSC-IMP

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

An Improper SONET APS Code (APSC-IMP) alarm indicates bad or invalid K bytes. The APSC-IMP alarm occurs on OC-N cards in a BLSR configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.

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

Note This alarm can occur on a virtual tributary (VT) tunnel when it does not have VT circuits provisioned. It can also occur when the exercise command or a lockout is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.

Clear the APSC-IMP Alarm

Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.

For specific procedures to use the test set equipment, consult the manufacturer.

If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.

Step 2 If the K byte is valid, verify that each node has a ring name that matches the other node ring names. Complete the "Identify a BLSR Ring Name or Node ID Number" procedure.

Step 3 Repeat Step 2 for all nodes in the ring.

Step 4 If a node has a ring name that does not match the other nodes, make the ring name of that node identical to the other nodes. Complete the "Change a BLSR Ring Name" procedure.

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

2.7.13  APSCINCON

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

An APS Inconsistent (APSCINCON) alarm means that an inconsistent APS byte is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the SONET signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.

Clear the APSCINCON Alarm

Step 1 Look for other alarms, especially the "LOS (OCN)" alarm on page 2-129, the "LOF (OCN)" alarm on page 2-120, or the "AIS" alarm on page 2-18. Clearing these alarms clears the APSCINCON alarm.

Step 2 If an APSINCON alarm occurs with no other alarms, log onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.14  APSCM

•Major (MJ), Service-Affecting (SA)

•Logical Object: OCN

The APS Channel Mismatch (APSCM) alarm occurs when the ONS 15454 expects a working channel but receives a protection channel. In many cases, the working and protection 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 configuration.

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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

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

Clear the APSCM Alarm

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 onto 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.7.15  APSCNMIS

•Major (MJ), Service-Affecting (SA)

•Logical Object: OCN

The APS Node ID Mismatch (APSCNMIS) alarm occurs when the source node ID contained in the SONET K2 byte of the incoming APS channel is not present in the ring map. The APSCNMIS alarm could occur and clear when a BLSR is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains, the alarm clears when a K byte with a valid source node ID is received.

Clear the APSCNMIS Alarm

Step 1 Complete the "Identify a BLSR Ring Name or Node ID Number" procedure to verify that each node has a unique node ID number.

Step 2 If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.

Step 3 Click Close in the Ring Map dialog box.

Step 4 If two nodes have the same node ID number, complete the "Change a BLSR Node ID Number" procedure to change one node's ID number so that each node ID is unique.

Note If the node names shown in the network view do not correlate with the node IDs, log into each node and click the Provisioning > BLSR tabs. The BLSR window shows the node ID of the login node.

Note Applying and removing a lockout on a span causes the ONS 15454 to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.

Step 5 If the alarm does not clear, use the "Lock Out a BLSR Span" procedure to lock out the span.

Step 6 Complete the "Clear a BLSR External Switching Command" procedure to clear the lockout.

Step 7 If the alarm does not clear, log onto 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.7.16  APSIMP

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: OCN

The APS Invalid Code (APSIMP) condition 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 proper type of byte.

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

Clear the APSIMP Condition

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.

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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.17  APSMM

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OCN

An APS Mode Mismatch (APSMM) failure alarm occurs when there is a mismatch of the protection switching schemes at the two ends of the span. If one node is provisioned for bidirectional switching, the node at the other end of the span must also be provisioned for bidirectional switching. If one end is provisioned for bidirectional and the other is provisioned for unidirectional, an APSMM alarm occurs in the ONS node that is provisioned for bidirectional. The APSMM alarm occurs in a 1+1 configuration.

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 DCC connectivity) to the far end.

Click Edit.

Record whether the Bidirectional Switching check box is checked.

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

Step 3 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 4 Click Apply.

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

2.7.18  AS-CMD

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Objects: AOTS, BPLANE, CLIENT, DS1, DS3, E100T, E1000F, EC1-12, EQPT, FCMR, G1000, ML100T, ML1000, NE, OCH, OCN, OMS, OTS, PWR, TRUNK

The Alarms Suppressed by User Command (AS-CMD) condition applies to the network element (NE object), backplane, a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects; that is, suppressing alarms on a card also suppresses alarms on its ports.

Clear the AS-CMD Condition

Step 1 For all nodes, in node view, 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 display the card view.

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

•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, click View > Go to Previous View.

Step 4 If the AS-CMD condition is reported for a card and not an individual port, in node view 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 AIP that are not in the optical or electrical slots. To clear the alarm:

a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

b. In the backplane row, deselect 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:

a. In node view, 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.19  AS-MT

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Objects: AOTS, CLIENT, DS1, DS3, EC1-12, FCMR, G1000, OCH, OCN, OMS, OTS, TRUNK

The Alarms Suppressed for Maintenance Command (AS-MT) condition applies to OC-N and electrical (traffic) cards and occurs when a port is placed in the out-of-service maintenance (OOS-MT) state for loopback testing operations.

Clear the AS-MT Condition

Step 1 Complete the "Clear a G-Series, OCN, MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G Loopback" procedure.

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

2.7.20  AUD-LOG-LOSS

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: NE

The Audit Trail Log Loss (AUD-LOG-LOSS) condition occurs when the log is 100 percent full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries. You will have to off-load (save) the log to make room for more entries.

Clear the AUD-LOG-LOSS Condition

Step 1 In node view, click the Maintenance > Audit tabs.

Step 2 Click Retrieve.

Step 3 Click Archive.

Step 4 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.

Step 5 Enter a name in the File Name field.

You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.

Step 6 Click Save.

The 640 entries will be saved in this file. New entries will continue with the next number in the sequence, rather than starting over.

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

2.7.21  AUD-LOG-LOW

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Object: NE

The Audit Trail Log Low (AUD-LOG-LOW) condition occurs when the audit trail log is 80 percent full.

Note AUD-LOG-LOW is an informational condition. It does not require troubleshooting.

2.7.22  AU-LOF

The AU-LOF condition is not used in this platform in this release. It is reserved for future development.

2.7.23  AUTOLSROFF

•Critical (CR), Service-Affecting (SA)

•Logical Object: OCN

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

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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

Clear the AUTOLSROFF Alarm

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

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.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

Note When you replace a card with an 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, call Cisco TAC (1 800 553-2447) to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.

2.7.24  AUTORESET

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: EQPT

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

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

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.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

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

2.7.25  AUTOSW-AIS

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: STSMON, VT-MON

The Automatic path protection Switch Caused by AIS (AUTOSW-AIS) condition indicates that automatic path protection protection switching occurred because of an AIS condition. The path protection is configured for revertive switching and reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.

Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.26  AUTOSW-LOP (STSMON)

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: STSMON

The Automatic UPSR Switch Caused by Loss of Pointer (LOP) condition (AUTOSW-LOP) for the STS monitor (STSMON) indicates that automatic path protection protection switching occurred because of the "LOP-P" alarm on page 2-122. The path protection is configured for revertive switching and reverts to the working path after the fault clears.

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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.27  AUTOSW-LOP (VT-MON)

•Minor (MN), Service-Affecting (SA)

•Logical Object: VT-MON

The AUTOSW-LOP alarm for the virtual tributary monitor (VT-MON) indicates that automatic path protection protection switching occurred because of the "LOP-V" alarm on page 2-122. The path protection is configured for revertive switching and reverts to the working path after the fault clears.

Clear the AUTOSW-LOP (VT-MON) Alarm

Step 1 Complete the "Clear the LOP-V Alarm" procedure.

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

2.7.28  AUTOSW-PDI

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: STSMON

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

Clear the AUTOSW-PDI Condition

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

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

2.7.29  AUTOSW-SDBER

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: STSMON

The Automatic UPSR Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition (AUTOSW-SDBER) indicates that a signal degrade [see the "SD (CLIENT, TRUNK)" condition on page 2-175] caused automatic path protection protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SD is resolved.

Clear the AUTOSW-SDBER Condition

Step 1 Complete the "Clear the SD-L Condition" procedure.

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

2.7.30  AUTOSW-SFBER

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: STSMON

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

Clear the AUTOSW-SFBER Condition

Step 1 Complete the "Clear the SF (DS1, DS3) Condition" procedure.

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

2.7.31  AUTOSW-UNEQ (STSMON)

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: STSMON

The Automatic UPSR Switch Caused by Unequipped Path (AUTOSW-UNEQ) condition indicates that an UNEQ alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.

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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.32  AUTOSW-UNEQ (VT-MON)

•Minor (MN), Service-Affecting (SA)

•Logical Object: VT-MON

AUTOSW-UNEQ (VT-MON) indicates that the "UNEQ-V" alarm on page 2-202 alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.

Clear the AUTOSW-UNEQ (VT-MON) Alarm

Step 1 Complete the "Clear the UNEQ-V Alarm" procedure.

Step 2 If the alarm does not clear, log onto 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.7.33  AWG-DEG

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: OTS

The arrayed waveguide gratings (AWG) Temperature Degrade alarm (AWG-DEG) indicates that an internal failure on the multiplexer or demultiplexer heater control circuit causes the AWG temperature to rise above or fall below the degrade threshold.

Clear the AWG-DEG Alarm

Step 1 This alarm does not immediately affect traffic. But eventually, you will need to complete the "Physically Replace a Card" procedure on the reporting card to clear the alarm.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the Cisco ONS 15454 Procedure Guide for information.

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

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

2.7.34  AWG-FAIL

•Critical (CR), Service-Affecting (SA)

•Logical Object: OTS

The AWG Temperature Fail (AWG-FAIL) alarm indicates that a heater control circuit on the multiplexer or demultiplexer card has failed.

Clear the AWG-FAIL Alarm

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the Cisco ONS 15454 Procedure Guide for information.

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

Step 2 If the alarm does not clear, log onto 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.7.35  AWG-OVERTEMP

•Critical (CR), Service-Affecting (SA)

•Logical Object: OTS

The AWG Over Temperature (AWG-OVERTEMP) alarm occurs in conjunction with the "AWG-FAIL" alarm on page 2-37 when the AWG temperature exceeds 100 degrees C (212 degrees F). The multiplexer or demultiplexer goes into protection mode, disabling the AWG chip heater.

Clear the AWG-OVERTEMP Alarm

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the Cisco ONS 15454 Procedure Guide for information.

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

Step 2 If the alarm does not clear, log onto 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.7.36  AWG-WARM-UP

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: OTS

The AWG Warm-up (AWG-WARM-UP) condition occurs during AWG startup. The length of time needed for the condition to clear varies, depending upon environmental conditions. It can last up to approximately 10 minutes.

Note AWG-WARM-UP is an informational condition, and does not require troubleshooting unless it does not clear.

2.7.37  BAT-FAIL

•Major (MJ), Service-Affecting (SA)

•Logical Object: PWR

The Battery Fail (BAT-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 on-site 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.

Step 3 If the alarm does not clear, log onto 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.7.38  BKUPMEMP

•Critical (CR), Non-Service Affecting (NSA)

•Logical Object: EQPT

The Primary Non-Volatile Backup Memory Failure (BKUPMEMP) alarm refers to a problem with the TCC2 card's flash memory. The alarm occurs when the TCC2 card is in use and has one of four problems: the flash manager fails to format a flash partition; the flash manager fails to write a file to a flash partition; there is a problem at the driver level, or the code volume fails cyclic redundancy checking (CRC). CRC is a method to verify for errors in data transmitted to the TCC2.

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

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

Clear the BKUPMEMP Alarm

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

Step 2 If both TCC2 cards are powered and enabled, reset the TCC2 card against which the alarm is raised. If the card is the active TCC2 card, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure. If the card is the standby TCC2, use the substeps below.

a. Right-click the standby TCC2 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 3 If the TCC2 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" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.39  BLSROSYNC

•Major (MJ), Service-Affecting (SA)

•Logical Object: OCN

The BLSR Out Of Synchronization (BLSROSYNC) alarm occurs when you attempt to add or delete a circuit and a node on a working ring loses its DCC connection because all transmit and receive fiber has been removed. CTC cannot generate the ring table and causes the BLSROSYNC alarm.

Clear the BLSROSYNC Alarm

Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the Cisco ONS 15454 Procedure Guide for cabling information.

When the DCC is established between the node and the rest of the BLSR, it becomes visible to the BLSR and should be able to function on the circuits.

Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" section.

Step 3 If the alarm does not clear, log onto 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.7.40  CARLOSS (CLIENT)

•Major (MJ), Service-Affecting (SA)

•Logical Object: CLIENT

A Carrier Loss (CARLOSS) alarm on the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card occurs when ITU-T G.709 monitoring is turned off at the client port. It is similar to the "LOS (OCN)" alarm on page 2-129.

Clear the CARLOSS (CLIENT) Alarm

Step 1 From node view, double-click the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card to display card view.

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

Step 3 Check the check box under the G.709 OTN column.

Step 4 If the alarm does not clear, log onto 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.7.41  CARLOSS (EQPT)

•Major (MJ), Service-Affecting (SA)

•Logical Object: EQPT

A CARLOSS on Equipment alarm generally occurs on OC-N cards when the ONS 15454 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 card or the LAN backplane pin connection on the ONS 15454. The CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the ONS 15454.

Clear the CARLOSS (EQPT) Alarm

Step 1 If the reporting card is a TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card, verify the type of payload configured:

a. Double-click the reporting TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card.

b. Click the Provisioning > Card tabs.

c. From the Payload Data Type list, choose the correct payload for the card and click Apply.

Step 2 If the reporting card is an OC-N card, verify connectivity by pinging the ONS 15454 that is reporting the alarm:

a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Accessories > Command Prompt.

b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.

c. For both the Sun and Microsoft operating systems, at the prompt type:
ping ONS-15454-IP-address
For example:
ping 198.168.10.10.
If the workstation has connectivity to the ONS 15454, it shows a "reply from IP-Address" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.

Step 3 If the ping is successful, 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.

Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port.

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

Step 7 If you are unable to establish connectivity, replace the fiber cable with a new known-good cable.

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.

Step 9 If the alarm does not clear, log onto 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.7.42  CARLOSS (E100T, E1000F)

•Major (MJ), Service-Affecting (SA)

•Logical Objects: E100T, E1000F

A CARLOSS on the LAN E100T or E1000F Ethernet (traffic) card is the data equivalent of the "LOS (OCN)" alarm on page 2-129. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of the CARLOSS alarm are a disconnected cable, an Ethernet Gigabit Interface Converter (GBIC) fiber connected to an optical (traffic) card rather than an Ethernet device, or an improperly installed Ethernet card. Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

The CARLOSS alarm also occurs after a node database is restored. After restoration, the alarm clears in approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP). The database restoration circumstance applies to the E-Series Ethernet cards but not the G1000-4 card, because the G1000-4 card does not use STP and is unaffected by STP reestablishment.

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

Clear the CARLOSS (E100T, E1000F) Alarm

Step 1 Verify that the fiber cable is properly connected and attached to the correct port.

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

Step 3 If no misconnection to an OC-N card exists, verify that the transmitting device is operational. If not, troubleshoot the device.

Step 4 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port.

For specific procedures to use the test set equipment, consult the manufacturer.

Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port.

Step 6 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet (traffic) card.

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 8 If a CARLOSS alarm repeatedly appears and clears, use the following steps to examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect.

If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm could be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:

a. Right-click anywhere in the row of the CARLOSS alarm.

b. Click Select Affected Circuits in the shortcut menu that appears.

c. Record the information in the type and size columns of the highlighted circuit.

d. From the examination of the layout of your network, determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

•Log into the ONS 15454 at the other end of the Ethernet manual cross-connect.

•Double-click the Ethernet card that is part of the Ethernet manual cross-connect.

•Click the Circuits tab.

•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The Ethernet manual cross-connect circuit connects the Ethernet card to an OC-N card at the same node.

e. Use the information you recorded to determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size.

If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. For more information, refer to the Cisco ONS 15454 Procedure Guide.

Step 9 If the alarm does not clear, log onto 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.7.43  CARLOSS (G1000)

•Major (MJ), Service-Affecting (SA)

•Logical Object: G1000

A CARLOSS on the LAN G1000 Ethernet (traffic) card is the data equivalent of the "LOS (OCN)" condition on page 2-129. The Ethernet card has lost its link and is not receiving a valid signal.

CARLOSS on the G1000-4 card is caused by one of two situations:

•The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. The CARLOSS can be caused by an improperly connected Ethernet cable or a problem with the signal between the Ethernet device and the G1000-4 port.

•If a problem exists in the end-to-end path (including possibly the far-end G1000-4 card), it causes the reporting G1000-4 card to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, other alarms such as the "TPTFAIL (G1000)" alarm on page 2-197 or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G-Series) alarm.

Refer to the Cisco ONS 15454 Reference Manual for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-198 for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.

Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

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

Clear the CARLOSS (G1000) Alarm

Step 1 Verify that the fiber cable is properly connected and attached to the correct port.

Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.

Step 3 If no misconnection to the OC-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.

Step 4 Verify that optical receive levels are within the normal range.

Step 5 If the alarm does not clear, use an Ethernet test set to determine that a valid signal is coming into the Ethernet port.

For specific procedures to use the test set equipment, consult the manufacturer.

Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port.

Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the G1000-4 card turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, determine whether there are conditions that could cause autonegotiation to fail:

a. Confirm that the attached Ethernet device has autonegotiation enabled and is configured for compatibility with the asymmetric flow control on the G1000-4 card.

b. Confirm that the attached Ethernet device configuration allows reception of flow control frames.

Step 8 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. (The autonegotiation process restarts.)

Step 9 If the alarm does not clear and the "TPTFAIL (G1000)" alarm on page 2-197 is also reported, complete the "Clear the TPTFAIL (G1000) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.

Note When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition could be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.

Step 10 If the TPTFAIL alarm was not reported, determine whether a terminal (inward) loopback has been provisioned on the port:

a. In node view, click the card to go to card view.

b. Click the Conditions tab and the Retrieve Conditions button.

c. If LPBKTERMINAL is listed for the port, a loopback is provisioned. Go to Step 11. If IS is listed, go to Step 12.

Step 11 If a loopback was provisioned, complete the "Clear a G-Series, OCN, MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G Loopback" procedure.

On the G1000-4 card, provisioning a terminal (inward) loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.

If the does not have a LPBKTERMINAL condition, continue to Step 12.

Step 12 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm could be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps if the Ethernet circuit is part of a manual cross-connect.

Note An Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454s, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.

a. Right-click anywhere in the row of the CARLOSS alarm.

b. Right-click or left-click Select Affected Circuits in the shortcut menu that appears.

c. Record the information in the type and size columns of the highlighted circuit.

d. Examine the layout of your network and determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

•Log into the ONS 15454 at the other end of the Ethernet manual cross-connect.

•Double-click the Ethernet (traffic) card that is part of the Ethernet manual cross-connect.

•Click the Circuits tab.

•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit connects the Ethernet card to an OC-N card at the same node.

e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.

f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.

Step 13 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure.

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 15 If the alarm does not clear, log onto 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.7.44  CARLOSS (ML100T, ML1000)

•Major (MJ), Service-Affecting (SA)

•Logical Objects: ML100T, ML1000

A CARLOSS on the ML100T or ML1000 Ethernet (traffic) card is the data equivalent of the "LOS (OCN)" alarm on page 2-129. The Ethernet port has lost its link and is not receiving a valid signal.

A CARLOSS alarm occurs when the Ethernet port has been configured from the IOS command line interface (CLI) as a no-shutdown port and one of the following items also occurs:

•The cable is not properly connected to the near or far port.

•Auto-negotiation is failing.

•The speed (10/100 ports only) is set incorrectly.

For information about provisioning ML-Series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.

Clear the CARLOSS (ML100T, ML1000) Alarm

Step 1 Verify that the LAN cable is properly connected and attached to the correct port on the ML-Series card and on the peer Ethernet port.

Step 2 If the alarm does not clear, verify that autonegotiation is set properly on the ML-Series card port and the peer Ethernet port.

Step 3 If the alarm does not clear, verify that the speed is set properly on the ML-Series card port and the peer Ethernet port if you are using 10/100 ports.

Step 4 If the alarm does not clear, the Ethernet signal is not valid, but the transmitting device is operational, replace the LAN cable connecting the transmitting device to the Ethernet port.

Step 5 If the alarm does not clear, disable and reenable the Ethernet port by performing a "shutdown" and then a "no shutdown" on the IOS CLI. Autonegotiation will restart.

Step 6 If the alarm does not clear, complete the "Perform a Facility (Line) Loopback on a Source DS-N Port (West to East)" procedure on page 1-8.

Step 7 If the problem persists with the loopback installed, complete the "Remove and Reinsert (Reseat) a Card" procedure.

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 9 If the alarm does not clear, log onto 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.7.45  CARLOSS (TRUNK)

•Major (MJ), Service-Affecting (SA)

•Logical Object: TRUNK

A CARLOSS on the optical trunk connecting to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards is raised when ITU-T G.709 monitoring is disabled.

Clear the CARLOSS (TRUNK) Alarm

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

Step 2 If the alarm does not clear, log onto 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.7.46  CASETEMP-DEG

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: AOTS

The Case Temperature Degrade (CASETEMP-DEG) alarm occurs when a card detects a case temperature value outside the desired range (-5 to 65 degrees C or 23 to 149 degrees F).

Clear the CASETEMP-DEG Alarm

Step 1 If a FAN alarm is also reported, complete the "Clear the FAN Alarm" procedure.

Step 2 If no FAN alarm is reported, complete the "Replace the Air Filter" procedure on page 3-5.

Step 3 If the alarm does not clear, log onto 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.7.47  CKTDOWN

•Critical (CR), Service-Affecting (SA)

•Logical Object: UCP-CKT

The unified control plane (UCP) Circuit Down (CKTDOWN) alarm applies to logical circuits created within the UCP between devices. It occurs when there is signaling failure across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 because it is an edge device.

Clear the CKTDOWN Alarm

Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:

a. In node view, click the Provisioning > UCP > Neighbor tabs.

b. View the entries to find out whether the node you are trying to contact is listed.

The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that it is physically and logically accessible.

c. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.

d. At the command prompt (C:\>), type:
ping {node-DNS-name | node-IP-address}
If you typed the domain name services (DNS) name and the ping was successful, you will see:
pinging node-dns-name.domain-name.com. node-IP-address with 32 bytes of data:
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Ping statistics for IP-address:
	Packets sent = 4 Received = 4 Lost = 0 (0% lost),
Approximate round trip time in milli-seconds:
Minimum = minimum-ms, Maximum = maximum-ms, Average = average-ms
If you typed the IP address and the ping command is successful, the result will look similar but will not include the DNS name in the first line.
e. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.

f. If the ping was unsuccessful, you will receive the following reply for each try:
Request timed out.
A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.

Step 2 If the neighbor has not been provisioned, or if you had to delete the neighbor, create one:

a. In the Provisioning > UCP > Neighbor tabs, click the Create button.

b. In the Neighbor Discovery window, enter the node's DNS node name in the Neighbor Name field. Leave the Enable Discovery check box checked (default setting) if you want the neighbor to be discovered through the network.

c. Click OK.

The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If it is not successful, the column lists 0.0.0.0.

Step 3 If neighbor discovery is enabled, ensure that the neighbor node ID and remote Internet protocol (IP) control channel (IPCC) have been discovered correctly.

Step 4 Click the Provisioning > UCP > IPCC tabs and view the IPCC listing. If the IPCC has been created correctly, the Remote IP column contains the neighbor's IP address.

Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.

a. Click the entry to select the neighbor IP address and click Delete.

b. If you get an error that will not allow you to delete the IPCC, you must delete the neighbor and recreate it. Click the Neighbor tab.

c. Click to select the neighbor and click Delete.

d. Go back to Step 2 to recreate the neighbor.

Step 6 If remote IPCC has not been discovered, or if it had to be deleted, create the connection:

a. In the Provisioning > UCP > IPCC tabs, click Create.

b. In the Unified Control Plane Provisioning window, click Next.

c. If no IPCCs are listed, click Create.

d. In the Create New IPCC window, click the DCC termination corresponding to the core network interface.

Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.

e. Click OK. The IPCC is listed in the Unified Control Plane Provisioning window.

f. Click the neighbor to select it, and click Next.

g. Choose the UCP interface [for example, Slot 5 (OC-48), port 1] where the core network is connected from the pull-down menu. The field default is the node where you are logged in.

h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.

i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab will contain the neighbor's IP address.

Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:

a. Click the Interface tab. View the slot and port listed in the Interface column [for example, Slot 5 (OC48), port 1].

b. Compare the listed interface listed with the IPCC tab SDCC column entry.

Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.

Step 9 Click Next.

Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.

The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.

Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.

Step 12 If the alarm does not clear, log onto 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.7.48  CLDRESTART

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: EQPT

The Cold Restart (CLDRESTART) condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 is first powered up.

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

Clear the CLDRESTART Condition

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

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

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

2.7.49  COMIOXC

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

The Input/Output Slot To Cross-Connect Communication Failure (COMIOXC) alarm is caused by the XC10G cross-connect card. It occurs when there is a communication failure for a traffic slot.

Clear the COMIOXC Alarm

Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the reporting XC10G cross-connect card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 2 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

Step 3 If the CTC reset does not clear the alarm, move traffic off the reporting cross-connect card. Complete the "Side Switch the Active and Standby XC10G Cross-Connect cards" procedure.

Step 4 Complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting cross-connect card.

Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting cross-connect card.

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

Step 6 If the alarm does not clear, log onto 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.7.50  COMM-FAIL

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: EQPT

The Plug-In Module (card) Communication Failure (COMM-FAIL) alarm indicates that there is a communication failure between the TCC2 and the card. The failure could indicate a broken card interface.

Clear the COMM-FAIL Alarm

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

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

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

2.7.51  CONTBUS-A-18

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Communication Failure from TCC2 A Slot to TCC2 Slot A (CONTBUS-A-18) alarm occurs when the main processor on the TCC2 card in Slot 7 (termed TCC A) loses communication with the coprocessor on the same 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 at the lower-right outside edge of the shelf assembly.

Clear the CONTBUS-A-18 Alarm

Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 11 active.

Step 2 Wait approximately 10 minutes for the TCC2 in Slot 7 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.

Step 3 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 7 active.

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

2.7.52  CONTBUS-B-18

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Communication Failure from TCC2 B Slot to TCC2 B Slot (CONTBUS-B-18) alarm occurs when the main processor on the TCC2 card in Slot 11 (termed TCC B) loses communication with the coprocessor on the same 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 at the lower-right outside edge of the shelf assembly.

Clear the CONTBUS-B-18 Alarm

Step 1 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 7 active.

Step 2 Wait approximately 10 minutes for the TCC2 in Slot 11 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.

Step 3 Position the cursor over the TCC2 card in Slot 7 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 11 active.

Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1 800 553-2447). If the TAC technician tells you to reseat the card, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.53  CONTBUS-IO-A

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A TCC A to Shelf Slot Communication Failure (CONTBUS-IO-A) alarm occurs when the active TCC2 card in Slot 7 (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 might appear briefly when the ONS 15454 switches to the protect TCC2 card. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2 card, the other card, and the backplane.

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

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 to reveal the provisioned type.

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

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

Step 3 If the alarm object is the standby TCC2 in Slot 11, perform a soft reset of this card:

a. Right-click the Slot 11 TCC2 card.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

Step 4 If CONTBUS-IO-A is raised on several cards at once, complete the "Reset Active TCC2 Card and Activate 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. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

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

2.7.54  CONTBUS-IO-B

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A TCC B to Shelf Slot Communication Failure (CONTBUS-IO-B) alarm occurs when the active TCC2 card in Slot 11 (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 might appear briefly when the ONS 15454 switches to the protect TCC2 card. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2 card, the other card, and the backplane.

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

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 to reveal the provisioned type.

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

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

Step 3 If the alarm object is the standby TCC2 in Slot 7, perform a soft reset of this card:

a. Right-click the Slot 7 TCC2 card.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

Step 4 If CONTBUS-IO-B is raised on several cards at once, complete the "Reset Active TCC2 Card and Activate 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. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

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

2.7.55  CTNEQPT-MISMATCH

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: EQPT

The Connection Equipment Mismatch (CTNEQPT-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 card may be preprovisioned in Slot 10, but an XCVT may be physically installed.

The alarm is raised against a card that is mismatched with the card. For example, CTNEQPT-MISMATCH is raised in the following situations:

•An XC card is replaced with an XCVT or XC10G card.

•An XCVT card is replaced with an XC10G card.

Note Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation may briefly occur during the upgrade process. (For example, you might have an XC in Slot 8 and an XC10G in Slot 10 while you are upgrading Slot 10.)

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

If you upgrade a node to R4.6 and replace an XC with XCVT or XC10G, or an XCVT with an XC10G, the CTNEQPT-MISMATCH condition is raised but it will be cleared when the upgrade process ends.

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 Cisco ONS 15454 Procedure Guide.

Clear the CTNEQPT-MISMATCH Condition

Step 1 Verify what card is preprovisioned in the slot:

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 might be provisioned for an XCVT card, which is shown in the Eqpt Type column, but an XC10G card could be physically present in the slot. The XC10G 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.56  CTNEQPT-PBPROT

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus (CTNEQPT-PBPROT) alarm indicates a failure of the main payload between the Slot 10 XC10G cross-connect card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, the TCC2 card, or the backplane.

Note If all traffic cards show CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) the Standby TCC2" procedure for the standby TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the standby TCC2 card. Do not physically reseat an active TCC2 card. Reseating the TCC2 disrupts traffic.

Note This alarm automatically raises and clears when the Slot 8 XC10G cross-connect card is reseated.

Caution It can take up to 30 minutes for software to be updated on a standby TCC2 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 at the lower-right outside edge of the shelf assembly.

Clear the CTNEQPT-PBPROT Alarm

Step 1 Perform a CTC reset on the standby XC10G cross-connect card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 2 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

If the cross-connect reset is not complete and error-free or if the TCC2 reboots automatically, call Cisco TAC (1 800 553-2447).

Step 3 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.

Step 4 Determine whether the card is an active card or standby card in a protection group. Click the node view Maintenance > Protection tabs, then click the protection group. The cards and their status are displayed in the list.

Step 5 If the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.

Step 6 Complete the "Reset a Traffic Card in CTC" procedure on the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 7 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

Step 8 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.

Step 9 Complete the "Clear a Protection Group External Switching Command" procedure.

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 11 If the alarm does not clear, log onto 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.7.57  CTNEQPT-PBWORK

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus (CTNEQPT-PBWORK) alarm indicates a failure in the main payload bus between the Slot 8 XC10G cross-connect card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, or the backplane.

Note If all traffic cards show CTNEEQPT-PBWORK alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure for the active TCC2 card and then complete the "Remove and Reinsert (Reseat) the Standby TCC2" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card. Do not physically reseat an active TCC2 card; it disrupts traffic.

Note This alarm automatically raises and clears when the Slot 10 XC10G cross-connect card is reseated.

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

Clear the CTNEQPT-PBWORK Alarm

Step 1 Complete the "Side Switch the Active and Standby XC10G Cross-Connect cards" procedure for the active XC10G cross-connect card.

Note After the active cross-connect goes into standby, the original standby slot becomes active. The active card ACT/SBY LED becomes green.

Step 2 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 3 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

Step 4 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.

Note The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.

Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.

Step 6 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 7 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

Step 9 If you switched traffic, complete the "Clear a Protection Group External Switching Command" procedure.

Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the cross-connect card.

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

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

Step 12 If the alarm does not clear, log onto 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.7.58  DATAFLT

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: NE

The Software Data Integrity Fault (DATAFLT) alarm occurs when the TCC2 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 Active TCC2 Card and Activate Standby Card" procedure.

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

2.7.59  DBOSYNC

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The standby Database Out Of Synchronization (DBOSYNC) alarm occurs when the standby TCC2 "To be Active" database does not synchronize with the active database on the active TCC2.

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

Clear the DBOSYNC Alarm

Step 1 Save a backup copy of the active TCC2 database. Complete the "Back Up the Database" procedure in the Cisco ONS 15454 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, 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.60  DSP-COMM-FAIL

•Major (MJ), Service-Affecting (SA)

•Logical Object: TRUNK

The digital signal processor (DSP) Communication Failure alarm (DSP-COMM-FAIL) indicates that there is a communications failure between an MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card microprocessor and the on-board DSP chip that controls the trunk (DWDM) port. This alarm typically occurs after a DSP code upgrade.

The alarm is temporary and does not require user action. The MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card microprocessor attempts to restore communication with the DSP chip until the alarm is cleared.

If the alarm is raised for an extended period, the MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card raises the "DSP-FAIL" alarm on page 2-60, and could affect traffic.

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

2.7.61  DSP-FAIL

•Major (MJ), Service-Affecting (SA)

•Logical Object: TRUNK

The DSP Failure (DSP-FAIL) alarm indicates that a "DSP-COMM-FAIL" alarm on page 2-60 has persisted for an extended period on an MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G 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_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 2 If the alarm does not clear, log onto 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.7.62  DS3-MISM

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: DS3

The DS-3 Frame Format Mismatch (DS3-MISM) condition indicates a frame format mismatch on a signal transiting the DS3XM-6 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C Bit for a DS3XM-6 card, and the incoming signal's frame format is detected as M13, then the ONS 15454 reports a DS3-MISM condition.

Clear the DS3-MISM Condition

Step 1 Display the CTC card view for the reporting DS3XM-6 card.

Step 2 Click the Provisioning > Line tabs.

Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal.

Step 4 If the Line Type pull-down menu does not match the expected incoming signal, select the correct Line Type in the pull-down menu.

Step 5 Click Apply.

Step 6 If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 matches the expected incoming signal.

For specific procedures to use the test set equipment, consult the manufacturer.

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

2.7.63  DUP-IPADDR

•Major (MJ), 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 DCC area. When this happens, TC no longer reliably connects to either node. Depending on how the packets are routed, CTC may 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-IDADDR Alarm

Step 1 In node view, click the Provisioning > Network > General tabs.

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

Step 3 Click Apply.

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

2.7.64  DUP-NODENAME

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The Duplicate Node Name (DUP-NODENAME) alarm indicates that the alarmed node's alphanumeric name is already being used within the same DCC area.

Clear the DUP-NODENAME Alarm

Step 1 In node view, 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.65  EHIBATVG

•Major (MJ), Service-Affecting (NSA)

•Logical Object: PWR

The Extreme High Voltage Battery (EHIBATVG) alarm occurs in a -48 VDC environment when a battery lead's 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 Cisco ONS 15454 Procedure Guide.)

Clear the EHIBATVG Alarm

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

Step 2 If the alarm does not clear, log onto 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.7.66  ELWBATVG

•Major (MJ), Service-Affecting (SA)

•Logical Object: PWR

The Extreme Low Voltage Battery (ELWBATVG) alarm occurs in a -48 VDC environment when a battery lead's 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 Cisco ONS 15454 Procedure Guide.)

Clear the ELWBATVG Alarm

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

Step 2 If the alarm does not clear, log onto 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.7.67  EOC

•Major (MJ), Non-Service Affecting (NSA)

•Logical Objects: CLIENT, OCN, TRUNK

The SONET Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 loses its data communications channel. 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 SDCCs consist of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 uses the DCC on the SONET section 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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

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

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

Clear the EOC Alarm

Step 1 If the "LOS (DS1)" alarm on page 2-125 is also reported, complete the "Clear the LOS (DS1) Alarm" procedure.

Step 2 If the alarm does not clear on the reporting node, verify the physical connections between the cards and the fiber-optic cables that are configured to carry DCC traffic.

Step 3 If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have in-service (IS) ports by checking that the ACT LED on each OC-N card is illuminated.

Step 4 If the ACT LEDs on OC-N cards are illuminated, complete the "Verify or Create Node 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:

a. Confirm that the OC-N card shows a green LED in CTC or on the physical card.

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

b. To determine whether the port is in service, double-click the card in CTC to display the card view.

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and click IS from the pull-down menu. 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 the OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path.

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. See the "OC-N Card Transmit and Receive Levels" section on page 1-102 non-DWDM card levels and see the Cisco ONS 15454 Reference Manual for DWDM card levels.

Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information refer to the "Install the Fiber-Optic Cables" procedure in the Cisco ONS 15454 Procedure Guide.

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

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

Resetting the active TCC2 switches control to the standby TCC2. If the alarm clears when the ONS 15454 switches to the standby TCC2, the user can assume that the original active TCC2 is the cause of the alarm.

Step 11 If the TCC2 reset does not clear the alarm, delete the problematic DCC termination:

a. From card view, click View > Go to Previous View if you have not already done so.

a. Click the Provisioning > DCC/GCC/OSC tabs.

b. Highlight the problematic DCC termination.

c. Click Delete.

d. Click Yes in the confirmation dialog box.

Step 12 Recreate the DCC termination. Refer to the Cisco ONS 15454 Procedure Guide for instructions.

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" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.68  EOC-L

•Major (MJ), Non-Service Affecting (NSA)

•Logical Objects: OCN, TRUNK

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

The LDCCs are nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS 15454 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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

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

Note If a circuit shows an incomplete state when the EOC alarm is raised, it occurs when the logical circuit is in place. The circuit will be able to carry traffic when the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.

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" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.69  EQPT

•Critical (CR), Service-Affecting (SA)

•Logical Objects: AICI-AIE, EQPT

An Equipment Failure (EQPT) alarm indicates that a hardware failure has occurred on the reporting card.

If the EQPT alarm occurs with a BKUPMEMP alarm, refer to the "BKUPMEMP" section. The BKUPMEMP procedure also clears the EQPT 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 at the lower-right outside edge of the shelf assembly.

Clear the EQPT Alarm

Step 1 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 2 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

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

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Switch Protection Group Traffic with an External Switching Command" procedure for more information.

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

Step 5 If the alarm does not clear, log onto 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.7.70  EQPT-MISS

•Critical (CR), Service-Affecting (SA)

•Logical Object: FAN

The Replaceable Equipment or Unit Missing (EQPT-MISS) alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or not fully inserted or that the ribbon cable connecting the AIP to the system board may be bad.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside 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 "Remove and Reinsert 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 Cisco ONS 15454 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 onto 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.7.71  ERFI-P-CONN

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: STSMON, STSTRM

The three-bit enhanced remote failure indication (ERFI) Path Connectivity condition (ERFI-P-CONN) is triggered on DS-1, DS-3, and VT circuits when the "UNEQ-P" alarm on page 2-200 and the "TIM-P" alarm on page 2-195 are raised on the transmission signal.

Clear the ERFI-P-CONN Condition

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

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

2.7.72  ERFI-P-PAYLD

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: STSMON, STSTRM

The ERFI Path Payload (ERFI-P-PAYLD) condition is triggered on DS-1, DS-3, and VT circuits when the "PLM-P" alarm on page 2-164 alarm is raised on the transmission signal.

Clear the ERFI-P-PAYLD Condition

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

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

2.7.73  ERFI-P-SRVR

•Not Reported (NR), Non-Service Affecting (NSA)

•Logical Objects: STSMON, STSTRM

The ERFI Path Server (ERFI-:P-SRVR) condition is triggered on DS-1, DS-3, and VT circuits when the "AIS-P" alarm on page 2-19 or the "LOP-P" alarm on page 2-122 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.74  ERROR-CONFIG

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: EQPT

The Error in Startup Configuration (ERROR-CONFIG) alarm applies to the ML-Series Ethernet (traffic) cards. These cards process startup configuration files line by line. If one or more lines cannot be executed, the error causes the ERROR-CONFIG alarm. ERROR-CONFIG is not caused by hardware failure.

The typical reasons for an errored startup file are:

•The user stored the configuration for one type of ML-Series card in the database and then installed another type in its slot.

•The configuration file contained a syntax error on one of the lines.

For information about provisioning the ML-Series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.

Clear the ERROR-CONFIG Alarm

Step 1 If you have a different type of ML-Series card specified in the startup configuration file than what you have installed, create the correct startup configuration.

Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.

Step 2 Upload the configuration file to the TCC2:

a. In node view, right-click the ML-Series card graphic.

b. Choose IOS Startup Config from the shortcut menu.

c. Click Local > TCC and navigate to the file location in the Open dialog box.

Step 3 Complete the "Reset a Traffic Card in CTC" procedure.

Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start an IOS CLI for the card:

a. Right click the ML-Series card graphic in node view.

b. Choose Open IOS Connection from the shortcut menu.

Note Open IOS Connection is not available unless the ML-Series card is physically installed in the shelf.

Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.

Step 5 Execute the CLI command copy run start. The command copies the new card configuration into the database and clears the alarm.

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

2.7.75  ETH-LINKLOSS

•Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: NE

The Rear Panel Ethernet Link Removed (ETH-LINKLOSS) condition, if enabled in the network defaults, is raised under the following conditions:

•The node.network.general.AlarmMissingBackplaneLAN field in NE default is enabled.

•The node is configured as a gateway network element (GNE).

•The backplane LAN cable is removed.

Clear the ETH-LINKLOSS Condition

Step 1 To clear this alarm, reconnect the backplane LAN cable. Refer to the Cisco ONS 15454 Procedure Guide for instructions to install this cable.

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

2.7.76  E-W-MISMATCH

•Major (MJ), Service-Affecting (SA)

•Logical Object: OCN

A Procedural Error Misconnect East/West Direction (E-W-MISMATCH) alarm occurs when nodes in a ring have an east slot misconnected to another east slot or a west slot misconnected to another west slot. In most cases, the user did not connect the fibers correctly or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but could change the traditional east-west node connection pattern of the ring.

Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its East-West slots configured correctly. If the alarm appears during the initial setup, the alarm clears itself shortly after the ring setup is complete.

Note The lower numbered slot at a node is traditionally labeled as the west slot and the higher numbered slot is labeled as the east slot. For example, Slot 6 is west and Slot 12 is east.

Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.

Clear the E-W-MISMATCH Alarm with a Physical Switch

Step 1 Diagram the ring setup, including nodes and spans, on a piece of paper or white board.

Step 2 In node view, click View > Go to Network View.

Step 3 Label each of the nodes on the diagram with the same name that appears on the network map.

Step 4 Right-click each span to reveal the node name/slot/port for each end of the span.

Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1 - Node2/Slot6/Port1 (2F BLSR OC48, ring name=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.

Step 6 Repeat Steps 4 and 5 for each span on your diagram.

Step 7 Label the highest slot at each node east and the lowest slot at each node west.

Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span. Refer to the Cisco ONS 15454 Procedure Guide for more information about configuring the system.

Step 9 If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.

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

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. Use of controls or adjustments or performance of procedures other t