Cisco ONS 15454 SONET and DWDM Troubleshooting Guide, Release 4.7
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 2.6MB) The complete bookPDF (PDF - 5.97MB) | Feedback

Alarm Troubleshooting

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  Alarm Logical Objects

2.4  Alarm Index by Logical Object Type

2.5  DS3-12 E Line Alarms

2.6  Trouble Notifications

2.6.1  Alarm Characteristics

2.6.2  Condition Characteristics

2.6.3  Severities

2.6.4  Service Effect

2.6.5  States

2.7  Safety Summary

2.8  Alarm Procedures

2.8.1  AIS

Clear the AIS Condition

2.8.2  AIS-L

Clear the AIS-L Condition

2.8.3  AIS-P

Clear the AIS-P Condition

2.8.4  AIS-V

Clear the AIS-V Condition

2.8.5  ALS

2.8.6  AMPLI-INIT

2.8.7  APC-CORRECTION-SKIPPED

2.8.8  APC-DISABLED

Clear the APC-DISABLED Alarm

2.8.9  APC-END

2.8.10  APC-OUT-OF-RANGE

Clear the APC-OUT-OF-RANGE Condition

2.8.11  APSB

2.8.12  APSCDFLTK

Clear the APSCDFLTK Alarm

2.8.13  APSC-IMP

Clear the APSC-IMP Alarm

2.8.14  APSCINCON

Clear the APSCINCON Alarm

2.8.15  APSCM

Clear the APSCM Alarm

2.8.16  APSCNMIS

Clear the APSCNMIS Alarm

2.8.17  APSIMP

Clear the APSIMP Condition

2.8.18  APS-INV-PRIM

2.8.19  APS-PRIM-FAC

Clear the APS-PRIM-FAC Condition

2.8.20  APSMM

Clear the APSMM Alarm

2.8.21  APS-PRIM-SEC-MISM

Clear the APS-PRIM-SEC-MISM Alarm

2.8.22  AS-CMD

Clear the AS-CMD Condition

2.8.23  AS-MT

Clear the AS-MT Condition

2.8.24  AS-MT-OOG

Clear the AS-MT-OOG Alarm

2.8.25  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.8.26  AUD-LOG-LOW

2.8.27  AU-LOF

2.8.28  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.8.29  AUTORESET

Clear the AUTORESET Alarm

2.8.30  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.8.31  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.8.32  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Alarm

2.8.33  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.8.34  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.8.35  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.8.36  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.8.37  AUTOSW-UNEQ (VT-MON)

Clear the AUTOSW-UNEQ (VT-MON) Alarm

2.8.38  AWG-DEG

Clear the AWG-DEG Alarm

2.8.39  AWG-FAIL

Clear the AWG-FAIL Alarm

2.8.40  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.8.41  AWG-WARM-UP

2.8.42  BAT-FAIL

Clear the BAT-FAIL Alarm

2.8.43  BKUPMEMP

Clear the BKUPMEMP Alarm

2.8.44  BLSROSYNC

Clear the BLSROSYNC Alarm

2.8.45  BPV

2.8.46  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.8.47  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.8.48  CARLOSS (FC)

2.8.49  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.8.50  CARLOSS (GE)

Clear the CARLOSS (GE) Alarm

2.8.51  CARLOSS (ISC)

Clear the CARLOSS (ISC) Alarm

2.8.52  CARLOSS (ML100T, ML1000, ML2)

Clear the CARLOSS (ML100T, ML1000, ML2) Alarm

2.8.53  CARLOSS (TRUNK)

Clear the CARLOSS (TRUNK) Alarm

2.8.54  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.8.55  CKTDOWN

Clear the CKTDOWN Alarm

2.8.56  CLDRESTART

Clear the CLDRESTART Condition

2.8.57  COMIOXC

Clear the COMIOXC Alarm

2.8.58  COMM-FAIL

Clear the COMM-FAIL Alarm

2.8.59  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.8.60  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.8.61  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.8.62  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.8.63  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.8.64  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.8.65  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.8.66  DATAFLT

Clear the DATAFLT Alarm

2.8.67  DBOSYNC

Clear the DBOSYNC Alarm

2.8.68  DS3-MISM

Clear the DS3-MISM Condition

2.8.69  DSP-COMM-FAIL

2.8.70  DSP-FAIL

Clear the DSP-FAIL Alarm

2.8.71  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.8.72  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.8.73  EHIBATVG

Clear the EHIBATVG Alarm

2.8.74  ELWBATVG

Clear the ELWBATVG Alarm

2.8.75  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.8.76  EOC

Clear the EOC Alarm

2.8.77  EOC-L

Clear the EOC-L Alarm

2.8.78  EQPT

Clear the EQPT Alarm

2.8.79  EQPT-MISS

Clear the EQPT-MISS Alarm

2.8.80  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.8.81  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.8.82  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.8.83  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.8.84  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.8.85  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.8.86  EXCCOL

Clear the EXCCOL Alarm

2.8.87  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.8.88  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.8.89  EXT

Clear the EXT Alarm

2.8.90  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.8.91  FAILTOSW

Clear the FAILTOSW Condition

2.8.92  FAILTOSW-PATH

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration

2.8.93  FAILTOSWR

Clear the FAILTOSWR Condition in a BLSR Configuration

2.8.94  FAILTOSWS

Clear the FAILTOSWS Condition

2.8.95  FAN

Clear the FAN Alarm

2.8.96  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.8.97  FE-AIS

Clear the FE-AIS Condition

2.8.98  FEC-MISM

Clear the FEC-MISM Alarm

2.8.99  FE-DS1-MULTLOS

Clear the FE-DS1-MULTLOS Condition

2.8.100  FE-DS1-NSA

Clear the FE-DS1-NSA Condition

2.8.101  FE-DS1-SA

Clear the FE-DS1-SA Condition

2.8.102  FE-DS1-SNGLLOS

Clear the FE-DS1-SNGLLOS Condition

2.8.103  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.8.104  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.8.105  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.8.106  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.8.107  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.8.108  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.8.109  FE-IDLE

Clear the FE-IDLE Condition

2.8.110  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.8.111  FE-LOF

Clear the FE-LOF Condition

2.8.112  FE-LOS

Clear the FE-LOS Condition

2.8.113  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.8.114  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.8.115  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.8.116  FEPRLF

Clear the FEPRLF Alarm on a Four-Fiber BLSR

2.8.117  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.8.118  FORCED-REQ

Clear the FORCED-REQ Condition

2.8.119  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.8.120  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.8.121  FRCDSWTOINT

2.8.122  FRCDSWTOPRI

2.8.123  FRCDSWTOSEC

2.8.124  FRCDSWTOTHIRD

2.8.125  FRNGSYNC

Clear the FRNGSYNC Alarm

2.8.126  FSTSYNC

2.8.127  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.8.128  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.8.129  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.8.130  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.8.131  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.8.132  GCC-EOC

Clear the GCC-EOC Alarm

2.8.133  GE-OOSYNC

Clear the GE-OOSYNC Alarm

2.8.134  GFP-CSF

Clear the GFP-CSF Alarm

2.8.135  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.8.136  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.8.137  GFP-LFD

Clear the GFP-LFD Alarm

2.8.138  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.8.139  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.8.140  HELLO

Clear the HELLO Alarm

2.8.141  HIBATVG

Clear the HIBATVG Alarm

2.8.142  HI-CCVOLT

Clear the HI-CCVOLT Condition

2.8.143  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.8.144  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.8.145  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.8.146  HITEMP

Clear the HITEMP Alarm

2.8.147  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.8.148  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.8.149  I-HITEMP

Clear the I-HITEMP Alarm

2.8.150  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.8.151  INC-ISD

2.8.152  INHSWPR

Clear the INHSWPR Condition

2.8.153  INHSWWKG

Clear the INHSWWKG Condition

2.8.154  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.8.155  INVMACADR

Clear the INVMACADR Alarm

2.8.156  IOSCFGCOPY

2.8.157  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.8.158  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.8.159  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.8.160  LASER-APR

2.8.161  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.8.162  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.8.163  LASEREOL

Clear the LASEREOL Alarm

2.8.164  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.8.165  LCAS-CRC

Clear the LCAS-CRC Condition

2.8.166  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.8.167  LCAS-TX-ADD

2.8.168  LCAS-TX-DNU

2.8.169  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.8.170  LMP-HELLODOWN

Clear the LMP-HELLODOWN Alarm

2.8.171  LMP-NDFAIL

Clear the LMP-NDFAIL Alarm

2.8.172  LOA

Clear the LOA Alarm

2.8.173  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.8.174  LOF (BITS)

Clear the LOF (BITS) Alarm

2.8.175  LOF (DS1)

Clear the LOF (DS1) Alarm

2.8.176  LOF (DS3)

Clear the LOF (DS3) Alarm

2.8.177  LOF (EC1-12)

Clear the LOF (EC1-12) Alarm

2.8.178  LOF (OCN)

Clear the LOF (OCN) Alarm

2.8.179  LOF (TRUNK)

Clear the LOF (TRUNK) Alarm

2.8.180  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.8.181  LOM

Clear the LOM Alarm

2.8.182  LOP-P

Clear the LOP-P Alarm

2.8.183  LOP-V

Clear the LOP-V Alarm

2.8.184  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.8.185  LOS (2R)

Clear the LOS (2R) Alarm

2.8.186  LOS (BITS)

Clear the LOS (BITS) Alarm

2.8.187  LOS (DS1)

Clear the LOS (DS1) Alarm

2.8.188  LOS (DS3)

Clear the LOS (DS3) Alarm

2.8.189  LOS (EC1-12)

Clear the LOS (EC1-12) Alarm

2.8.190  LOS (ESCON)

2.8.191  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.8.192  LOS (ISC)

Clear the LOS (ISC) Alarm

2.8.193  LOS (MSUDC)

2.8.194  LOS (OCN)

Clear the LOS (OCN) Alarm

2.8.195  LOS (OTS)

Clear the LOS (OTS) Alarm

2.8.196  LOS (TRUNK)

Clear the LOS (TRUNK) Alarm

2.8.197  LOS-O

Clear the LOS-O Alarm

2.8.198  LOS-P (OCH, OMS, OTS)

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

2.8.199  LOS-P (TRUNK)

Clear the LOS-P (TRUNK) Alarm

2.8.200  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.8.201  LPBKCRS

Clear the LPBKCRS Condition

2.8.202  LPBKDS1FEAC

Clear the LPBKDS1FEAC Condition

2.8.203  LPBKDS1FEAC-CMD

2.8.204  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.8.205  LPBKDS3FEAC-CMD

2.8.206  LPBKFACILITY (TRUNK)

Clear the LPBKFACILITY (TRUNK) Condition

2.8.207  LPBKFACILITY(DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.8.208  LPBKFACILITY (EC1-12)

Clear the LPBKFACILITY (EC1-12) Condition

2.8.209  LPBKFACILITY (ESCON)

2.8.210  LPBKFACILITY (FC)

Clear the LPBKFACILITY (FC) Condition

2.8.211  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.8.212  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.8.213  LPBKFACILITY (GE)

Clear the LPBKFACILITY (GE) Condition

2.8.214  LPBKFACILITY (ISC)

Clear the LPBKFACILITY (ISC) Condition

2.8.215  LPBKFACILITY (ML2)

2.8.216  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.8.217  LPBKTERMINAL (TRUNK)

Clear the LPBKTERMINAL (TRUNK) Condition

2.8.218  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.8.219  LPBKTERMINAL (EC1-12)

Clear the LPBKTERMINAL (EC1-12) Condition

2.8.220  LPBKTERMINAL (ESCON)

2.8.221  LPBKTERMINAL (FC)

Clear the LPBKTERMINAL (FC) Condition

2.8.222  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.8.223  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.8.224  LPBKTERMINAL (GE)

Clear the LPBKTERMINAL (GE) Condition

2.8.225  LPBKTERMINAL (ISC)

Clear the LPBKTERMINAL (ISC) Condition

2.8.226  LPBKTERMINAL (ML2)

2.8.227  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.8.228  LWBATVG

Clear the LWBATVG Alarm

2.8.229  MAN-REQ

Clear the MAN-REQ Condition

2.8.230  MANRESET

2.8.231  MANSWTOINT

2.8.232  MANSWTOPRI

2.8.233  MANSWTOSEC

2.8.234  MANSWTOTHIRD

2.8.235  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.8.236  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.8.237  MEA (AIP)

Clear the MEA (AIP) Alarm

2.8.238  MEA (BIC)

Clear the MEA (BIC) Alarm

2.8.239  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.8.240  MEA (FAN)

Clear the MEA (FAN) Alarm

2.8.241  MEA (PPM)

Clear the MEA (PPM) Alarm

2.8.242  MEM-GONE

2.8.243  MEM-LOW

2.8.244  MFGMEM

Clear the MFGMEM Alarm

2.8.245  NO-CONFIG

Clear the NO-CONFIG Condition

2.8.246  OCHNC-INC

2.8.247  ODUK-1-AIS-PM

Clear the ODUK-1-AIS-PM Condition

2.8.248  ODUK-2-AIS-PM

Clear the ODUK-2-AIS-PM Condition

2.8.249  ODUK-3-AIS-PM

Clear the ODUK-3-AIS-PM Condition

2.8.250  ODUK-4-AIS-PM

Clear the ODUK-4-AIS-PM Condition

2.8.251  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.8.252  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.8.253  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.8.254  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.8.255  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.8.256  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.8.257  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.8.258  OOU-TPT

Clear the OOT-TPT Condition

2.8.259  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.8.260  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.8.261  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.8.262  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.8.263  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.8.264  OSRION

Clear the OSRION Condition

2.8.265  OTUK-AIS

Clear the OTUK-AIS Condition

2.8.266  OTUK-BDI

Clear the OTUK-BDI Condition

2.8.267  OTUK-IAE

2.8.268  OTUK-LOF

Clear the OTUK-LOF Alarm

2.8.269  OTUK-SD

Clear the OTUK-SD Condition

2.8.270  OTUK-SF

Clear the OTUK-SF Condition

2.8.271  OTUK-TIM

Clear the OTUK-TIM Condition

2.8.272  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.8.273  PARAM-MISM

2.8.274  PDI-P

Clear the PDI-P Condition

2.8.275  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.8.276  PLM-P

Clear the PLM-P Alarm

2.8.277  PLM-V

Clear the PLM-V Alarm

2.8.278  PORT-ADD-PWR-DEG-HI

2.8.279  PORT-ADD-PWR-DEG-LOW

2.8.280  PORT-ADD-PWR-FAIL-HI

2.8.281  PORT-ADD-PWR-FAIL-LOW

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

2.8.282  PORT-MISMATCH

2.8.283  PRC-DUPID

Clear the PRC-DUPID Alarm

2.8.284  PROTNA

Clear the PROTNA Alarm

2.8.285  PTIM

Clear the PTIM Alarm

2.8.286  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.8.287  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.8.288  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm:

2.8.289  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.8.290  RAI

Clear the RAI Condition

2.8.291  RCVR-MISS

Clear the RCVR-MISS Alarm

2.8.292  RFI

Clear the RFI Condition

2.8.293  RFI-L

Clear the RFI-L Condition

2.8.294  RFI-P

Clear the RFI-P Condition

2.8.295  RFI-V

Clear the RFI-V Condition

2.8.296  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.8.297  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.8.298  RING-SW-EAST

2.8.299  RING-SW-WEST

2.8.300  RSVP-HELLODOWN

Clear the RSVP-HELLODOWN Alarm

2.8.301  RUNCFG-SAVENEED

2.8.302  SD (TRUNK)

Clear the SD (TRUNK) Condition

2.8.303  SD (DS1, DS3)

Clear the SD (DS1, DS3) Condition

2.8.304  SD-L

Clear the SD-L Condition

2.8.305  SD-P

Clear the SD-P Condition

2.8.306  SD-V

Clear the SD-V Condition

2.8.307  SF (TRUNK)

Clear the SF (TRUNK) Condition

2.8.308  SF (DS1, DS3)

Clear the SF (DS1, DS3) Condition

2.8.309  SF-L

Clear the SF-L Condition

2.8.310  SF-P

Clear the SF-P Condition

2.8.311  SF-V

2.8.312  SFTWDOWN

2.8.313  SH-INS-LOSS-VAR-DEG-HIGH

2.8.314  SH-INS-LOSS-VAR-DEG-LOW

2.8.315  SHUTTER-OPEN

Clear the SHUTTER-OPEN Alarm

2.8.316  SIGLOSS

Clear the SIGLOSS Alarm

2.8.317  SNTP-HOST

Clear the SNTP-HOST Alarm

2.8.318  SPAN-SW-EAST

2.8.319  SPAN-SW-WEST

2.8.320  SQUELCH

Clear the SQUELCH Condition

2.8.321  SQUELCHED

Clear the SQUELCHED Alarm

2.8.322  SQM

Clear the SQM Alarm

2.8.323  SSM-DUS

2.8.324  SSM-FAIL

Clear the SSM-FAIL Alarm

2.8.325  SSM-LNC

2.8.326  SSM-OFF

Clear the SSM-OFF Condition

2.8.327  SSM-PRC

2.8.328  SSM-PRS

2.8.329  SSM-RES

2.8.330  SSM-SDN-TN

2.8.331  SSM-SETS

2.8.332  SSM-SMC

2.8.333  SSM-ST2

2.8.334  SSM-ST3

2.8.335  SSM-ST3E

2.8.336  SSM-ST4

2.8.337  SSM-STU

Clear the SSM-STU Condition

2.8.338  SSM-TNC

2.8.339  SWMTXMOD

Clear the SWMTXMOD Alarm

2.8.340  SWTOPRI

2.8.341  SWTOSEC

Clear the SWTOSEC Condition

2.8.342  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.8.343  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.8.344  SYNCLOSS

Clear the SYNCLOSS Alarm

2.8.345  SYNCPRI

Clear the SYNCPRI Alarm

2.8.346  SYNCSEC

Clear the SYNCSEC Alarm

2.8.347  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.8.348  SYSBOOT

2.8.349  TIM

Clear the TIM Alarm or Condition

2.8.350  TIM-MON

Clear the TIM-MON Alarm

2.8.351  TIM-P

Clear the TIM-P Alarm

2.8.352  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.8.353  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.8.354  TPTFAIL (ML1000, ML100T, ML2)

Clear the TPTFAIL (ML1000, ML100T, ML2) Alarm

2.8.355  TRMT

Clear the TRMT Alarm

2.8.356  TRMT-MISS

Clear the TRMT-MISS Alarm

2.8.357  TX-AIS

Clear the TX-AIS Condition

2.8.358  TX-RAI

Clear the TX-RAI Condition

2.8.359  UNC-WORD

Clear the UNC-WORD Condition

2.8.360  UNEQ-P

Clear the UNEQ-P Alarm

2.8.361  UNEQ-V

Clear the UNEQ-V Alarm

2.8.362  UNREACHABLE-TARGET-POWER

2.8.363  UT-COMM-FAIL

Clear the UT-COMM-FAIL Alarm

2.8.364  UT-FAIL

Clear the UT-FAIL Alarm

2.8.365  VCG-DEG

Clear the VCG-DEG Condition

2.8.366  VCG-DOWN

Clear the VCG-DOWN Condition

2.8.367  VOA-HDEG

Clear the VOA-HDEG Alarm

2.8.368  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.8.369  VOA-LDEG

Clear the VOA-LDEG Alarm

2.8.370  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.8.371  WKSWPR

Clear the WKSWPR Condition

2.8.372  WTR

2.8.373  WVL-MISMATCH

Clear the WVL-MISMATCH alarm

2.9  DWDM Card LED Activity

2.9.1  DWDM Card LED Activity After Insertion

2.9.2  DWDM Card LED Activity During Reset

2.10  Traffic Card LED Activity

2.10.1  Typical Traffic Card LED Activity After Insertion

2.10.2  Typical Traffic Card LED Activity During Reset

2.10.3  Typical Card LED State After Successful Reset

2.10.4  Typical Cross-Connect LED Activity During Side Switch

2.11  Frequently Used Alarm Troubleshooting Procedures

2.11.1  Node and Ring Identification, Change, Visibility, and Termination

Identify a BLSR Ring Name or Node ID Number

Change a BLSR Ring Name

Change a BLSR Node ID Number

Verify Node Visibility for Other Nodes

2.11.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Protection Port Manual Switch Command

Clear a 1+1 Protection Port Force or Manual Switch Command

Initiate a Card or Port Lock On Command

Initiate a Card or Port Lock Out Command

Clear a Card or Port Lock On or Lock Out Command

Initiate a 1:1 Card Switch Command

Initiate a Force Switch for All Circuits on a Path Protection Span

Initiate a Manual Switch for All Circuits on a Path Protection Span

Initiate a Lock Out of Protect-Switch for All Circuits on a Path Protection Span

Clear Path Protection Span External Switching Command

Initiate a Force Switch a BLSR

Initiate a Force Span Switch a Four-Fiber BLSR

Initiate a Manual Ring Switch on a BLSR

Initiate a Lock Out on a BLSR Protect Span

Initiate an Exercise Ring Switch on a BLSR

Initiate an Exercise Ring Switch on a Four Fiber BLSR

Clear a BLSR External Switching Command

2.11.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Reset an Active TCC2 and Activate the Standby Card

Side Switch the Active and Standby XC10G Cross-Connect Cards

2.11.4  Physical Card Reseating, Resetting, and Replacement

Remove and Reinsert (Reseat) the Standby TCC2 Card

Remove and Reinsert (Reseat) Any Card

Physically Replace a Traffic Card

Physically Replace an In-Service Cross-Connect Card

2.11.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node SDCC Terminations

Clear an OC-N Card Facility or Terminal Loopback Circuit

Clear an OC-N Card XC Loopback Circuit

Clear a DS3XM-6 or DS3XM-12 Card Loopback Circuit

Clear Other DS-N Card, EC-1, or G1000 Card Loopbacks

Clear an MXP, TXP, or FCMR Card Loopback Circuit

Clear an Ethernet Card Loopback Circuit

2.11.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly

2.11.7  Interface Procedures

Replace the Electrical Interface Assembly

Replace the Alarm Interface Panel


Alarm Troubleshooting



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


This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15454 alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-8 gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in Table 2-8.

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

More information about alarm profile information modification and downloads are located in the Cisco ONS 15454 DWDM Installation and Operations Guide.


Note Release 4.7 is DWDM only. It supports all DWDM, transponder (TXP), and muxponder (MXP) cards but not optical, electrical, fibre storage, or Ethernet cards.


2.1  Alarm Index by Default Severity

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


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


2.1.1  Critical Alarms (CR)

Table 2-1 alphabetically lists ONS 15454 Critical alarms.


2.1.2  Major Alarms (MJ)

Table 2-2 alphabetically lists ONS 15454 Major alarms.

Table 2-2 ONS 15454 Major Alarm Index 

APC-DISABLED

EOC

LOS (ISC)

APSCM

EOC-L

LWBATVG

APSCNMIS

E-W-MISMATCH

MEM-GONE

AS-MT-OOG for VT

EXTRA-TRAF-PREEMPT

OPTNTWMIS

AU-LOF

FC-NO-CREDITS

PEER-NORESPONSE

BAT-FAIL

FEC-MISM

PTIM

BLSROSYNC

GCC-EOC

PLM-V

BPV

GFP-CSF

PRC-DUPID

CARLOSS (E100T, E1000F)

GFP-DE-MISMATCH

RCVR-MISS

CARLOSS (EQPT)

GFP-EX-MISMATCH

RING-ID-MIS

CARLOSS (G1000)

GFP-LFD

RING-MISMATCH

CARLOSS (GE)

GFP-NO-BUFFERS

SIGLOSS

CARLOSS (ISC)

GFP-UP-MISMATCH

SQM (VT-TERM)

CARLOSS (ML100T, ML1000, ML2)

HIBATVG

SSM-FAIL for double failure

CARLOSS (TRUNK)

HLDOVRSYNC

SYNCLOSS

CONTBUS-A-18

INVMACADR

SYSBOOT

CONTBUS-B-18

LASERBIAS-DEG

TPTFAIL (FCMR)

CONTBUS-IO-A

LASERBIAS-FAIL

TPTFAIL (G1000)

CONTBUS-IO-B

LASEREOL

TPTFAIL (ML1000, ML100T, ML2)

DBOSYNC

LASERTEMP-DEG

TRMT

DSP-COMM-FAIL

LOF (BITS)

TRMT-MISS

DSP-FAIL

LOF (DS1)

UNEQ-V

DUP-IPADDR

LOP-V

UT-COMM-FAIL

DUP-NODENAME

LOS (BITS)

UT-FAIL

EHIBATVG

LOS (DS1)

WVL-MISMATCH

ELWBATVG


2.1.3  Minor Alarms (MN)

Table 2-3 alphabetically lists ONS 15454 Minor alarms.

Table 2-3 ONS 15454 Minor Alarm Index 

APSB

HELLO

PORT-ADD-PWR-FAIL-HI

APSCDFLTK

HI-LASERBIAS

PORT-ADD-PWR-FAIL-LOW

APSC-IMP

HI-LASERTEMP

PROTNA

APSCINCON

HI-RXPOWER

PWR-FAIL-A

APS-INV-PRIM

HITEMP (EQPT)

PWR-FAIL-B

APSMM

HI-TXPOWER

PWR-FAIL-RET-A

APS-PRIM-SEC-MISM

KBYTE-APS-CHANNEL-FAILURE

PWR-FAIL-RET-B

AUTORESET

LASEREOL

RSVP-HELLODOWN

AUTOSW-LOP (VT-MON)

LMP-HELLODOWN

SFTWDOWN

AUTOSW-UNEQ (VT-MON)

LMP-NDFAIL

SH-INS-LOSS-VAR-DEG-HIGH

AWG-DEG

LO-LASERTEMP

SH-INS-LOSS-VAR-DEG-LOW

CASETEMP-DEG

LO-RXPOWER

SNTP-HOST

COMM-FAIL

LOS (FUDC)

SSM-FAIL

DATAFLT

LOS (MSUDC)

SYNCPRI

ERROR-CONFIG

LOS-O

SYNCSEC

EXCCOL

LO-TXPOWER

SYNCTHIRD

EXT

MEM-LOW

TIM-MON

FEPRLF

OPWR-HDEG

TIM-P (STSMON)

FIBERTEMP-DEG

OPWR-LDEG

UNREACHABLE-TARGET-POWER

FSTSYNC

PORT-ADD-PWR-DEG-HI

VOA-HDEG

GAIN-HDEG

PORT-ADD-PWR-DEG-LOW

VOA-LDEG

GAIN-LDEG


2.1.4  NA Conditions

Table 2-4 alphabetically lists ONS 15454 Not Alarmed conditions.

Table 2-4 ONS 15454 NA Conditions Index 

ALS

INC-ISD

OOU-TPT

AMPLI-INIT

INHSWPR

OSRION

APC-CORRECTION-SKIPPED

INHSWWKG

OTUK-SD

APC-END

INTRUSION-PSWD

OTUK-SF

APC-OUT-OF-RANGE

IOSCFGCOPY

OTUK-TIM

APSIMP

KB-PASSTHR

OUT-OF-SYNC

APS-PRIM-FAC

LAN-POL-REV

PARAM-MISM

AS-CMD

LASER-APR

PDI-P

AS-MT

LCAS-CRC

PORT-MISMATCH for FCMR

AUD-LOG-LOSS

LCAS-RX-FAIL

RAI

AUD-LOG-LOW

LCAS-TX-ADD

RING-SW-EAST

AUTOSW-LOP (STSMON)

LCAS-TX-DNU

RING-SW-WEST

AUTOSW-PDI

LKOUTPR-S

RUNCFG-SAVENEED

AUTOSW-SDBER

LOCKOUT-REQ

SD (TRUNK)

AUTOSW-SFBER

LPBKCRS

SD (DS1, DS3)

AUTOSW-UNEQ (STSMON)

LPBKDS1FEAC

SD-L

AWG-WARM-UP

LPBKDS1FEAC-CMD

SD-P

CLDRESTART

LPBKDS3FEAC

SD-V

CTNEQPT-MISMATCH

LPBKDS3FEAC-CMD

SF (TRUNK)

DS3-MISM

LPBKFACILITY (TRUNK)

SF (DS1, DS3)

ETH-LINKLOSS

LPBKFACILITY(DS1, DS3)

SF-L

EXERCISE-RING-FAIL

LPBKFACILITY (EC1-12)

SF-P

EXERCISE-SPAN-FAIL

LPBKFACILITY (ESCON)

SF-V

FAILTOSW

LPBKFACILITY (FC)

SHUTTER-OPEN

FAILTOSW-PATH

LPBKFACILITY (FCMR)

SPAN-SW-EAST

FAILTOSWR

LPBKFACILITY (G1000)

SPAN-SW-WEST

FAILTOSWS

LPBKFACILITY (GE)

SQUELCH

FE-AIS

LPBKFACILITY (ISC)

SQUELCHED

FE-DS1-MULTLOS

LPBKFACILITY (ML2)

SSM-DUS

FE-DS1-NSA

LPBKFACILITY (OCN)

SSM-LNC

FE-DS1-SA

LPBKTERMINAL (TRUNK)

SSM-OFF

FE-DS1-SNGLLOS

LPBKTERMINAL (DS1, DS3)

SSM-PRC

FE-DS3-NSA

LPBKTERMINAL (EC1-12)

SSM-PRS

FE-DS3-SA

LPBKTERMINAL (ESCON)

SSM-RES

FE-EQPT-NSA

LPBKTERMINAL (FC)

SSM-SDN-TN

FE-FRCDWKSWBK-SPAN

LPBKTERMINAL (FCMR)

SSM-SETS

FE-FRCDWKSWPR-RING

LPBKTERMINAL (G1000)

SSM-SMC

FE-FRCDWKSWPR-SPAN

LPBKTERMINAL (GE)

SSM-ST2

FE-IDLE

LPBKTERMINAL (ISC)

SSM-ST3

FE-LOCKOUTOFPR-SPAN

LPBKTERMINAL (ML2)

SSM-ST3E

FE-LOF

LPBKTERMINAL (OCN)

SSM-ST4

FE-LOS

MAN-REQ

SSM-STU

FE-MANWKSWBK-SPAN

MANRESET

SSM-TNC

FE-MANWKSWPR-RING

MANSWTOINT

SWTOPRI

FE-MANWKSWPR-SPAN

MANSWTOPRI

SWTOSEC

FORCED-REQ

MANSWTOSEC

SWTOTHIRD

FORCED-REQ-RING

MANSWTOTHIRD

SYNC-FREQ

FORCED-REQ-SPAN

MANUAL-REQ-RING

TIM (for OCN only)

FRCDSWTOINT

MANUAL-REQ-SPAN

TX-RAI

FRCDSWTOPRI

NO-CONFIG

UNC-WORD

FRCDSWTOSEC

OCHNC-INC

VCG-DEG

FRCDSWTOTHIRD

ODUK-SD-PM

VCG-DOWN

FRNGSYNC

ODUK-SF-PM

WKSWPR

FULLPASSTHR-BI

ODUK-TIM-PM

WTR

HI-CCVOLT


2.1.5  NR Conditions

Table 2-5 alphabetically lists ONS 15454 Not Reported conditions.


2.2  Alarms and Conditions Indexed By Alphabetical Entry

Table 2-6 alphabetically lists all ONS 15454 alarms and conditions.

Table 2-6 ONS 15454 Alarm and Condition Alphabetical Index 

AIS

FULLPASSTHR-BI

ODUK-AIS-PM

AIS-L

GAIN-HDEG

ODUK-BDI-PM

AIS-P

GAIN-HFAIL

ODUK-BDI-PM

AIS-V

GAIN-LDEG

ODUK-LCK-PM

ALS

GAIN-LFAIL

ODUK-OCI-PM

AMPLI-INIT

GCC-EOC

ODUK-SD-PM

APC-CORRECTION-SKIPPED

GE-OOSYNC

ODUK-SF-PM

APC-DISABLED

GFP-CSF

ODUK-TIM-PM

APC-END

GFP-DE-MISMATCH

OOU-TPT

APC-OUT-OF-RANGE

GFP-EX-MISMATCH

OPTNTWMIS

APSB

GFP-LFD

OPWR-HDEG

APSCDFLTK

GFP-NO-BUFFERS

OPWR-HFAIL

APSC-IMP

GFP-UP-MISMATCH

OPWR-LDEG

APSCINCON

HELLO

OPWR-LFAIL

APSCM

HIBATVG

OSRION

APSCNMIS

HI-CCVOLT

OTUK-AIS

APSIMP

HI-LASERBIAS

OTUK-BDI

APS-INV-PRIM

HI-LASERTEMP

OTUK-IAE

APS-PRIM-FAC

HI-RXPOWER

OTUK-LOF

APSMM

HITEMP

OTUK-SD

APS-PRIM-SEC-MISM

HI-TXPOWER

OTUK-SF

AS-CMD

HLDOVRSYNC

OTUK-TIM

AS-MT

I-HITEMP

OUT-OF-SYNC

AS-MT-OOG

IMPROPRMVL

PARAM-MISM

AUD-LOG-LOSS

INC-ISD

PDI-P

AUD-LOG-LOW

INHSWPR

PEER-NORESPONSE

AU-LOF

INHSWWKG

PLM-P

AUTOLSROFF

INTRUSION-PSWD

PLM-V

AUTORESET

INVMACADR

PORT-ADD-PWR-DEG-HI

AUTOSW-AIS

IOSCFGCOPY

PORT-ADD-PWR-DEG-LOW

AUTOSW-LOP (STSMON)

KB-PASSTHR

PORT-ADD-PWR-FAIL-HI

AUTOSW-LOP (VT-MON)

KBYTE-APS-CHANNEL-FAILURE

PORT-ADD-PWR-FAIL-LOW

AUTOSW-PDI

LAN-POL-REV

PORT-MISMATCH

AUTOSW-SDBER

LASER-APR

PRC-DUPID

AUTOSW-SFBER

LASERBIAS-DEG

PROTNA

AUTOSW-UNEQ (STSMON)

LASERBIAS-FAIL

PTIM

AUTOSW-UNEQ (VT-MON)

LASEREOL

PWR-FAIL-A

AWG-DEG

LASERTEMP-DEG

PWR-FAIL-B

AWG-FAIL

LCAS-CRC

PWR-FAIL-RET-A

AWG-OVERTEMP

LCAS-RX-FAIL

PWR-FAIL-RET-B

AWG-WARM-UP

LCAS-TX-ADD

RAI

BAT-FAIL

LCAS-TX-DNU

RCVR-MISS

BKUPMEMP

LKOUTPR-S

RFI

BLSROSYNC

LMP-HELLODOWN

RFI-L

BPV

LMP-NDFAIL

RFI-P

CARLOSS (E100T, E1000F)

LOA

RFI-V

CARLOSS (EQPT)

LOCKOUT-REQ

RING-ID-MIS

CARLOSS (G1000)

LOF (BITS)

RING-MISMATCH

CARLOSS (GE)

LOF (DS1)

RING-SW-EAST

CARLOSS (ISC)

LOF (DS3)

RING-SW-WEST

CARLOSS (ML100T, ML1000, ML2)

LOF (EC1-12)

RSVP-HELLODOWN

CARLOSS (TRUNK)

LOF (OCN)

RUNCFG-SAVENEED

CASETEMP-DEG

LOF (TRUNK)

SD (TRUNK)

CKTDOWN

LO-LASERTEMP

SD (DS1, DS3)

CLDRESTART

LOM

SD-L

COMIOXC

LOP-P

SD-P

COMM-FAIL

LOP-V

SD-V

CONTBUS-A-18

LO-RXPOWER

SF (TRUNK)

CONTBUS-B-18

LOS (2R)

SF (DS1, DS3)

CONTBUS-IO-A

LOS (BITS)

SF-L

CONTBUS-IO-B

LOS (DS1)

SF-P

CTNEQPT-MISMATCH

LOS (DS3)

SF-V

CTNEQPT-PBPROT

LOS (EC1-12)

SFTWDOWN

CTNEQPT-PBWORK

LOS (ESCON)

SH-INS-LOSS-VAR-DEG-HIGH

DATAFLT

LOS (ISC)

SH-INS-LOSS-VAR-DEG-LOW

DBOSYNC

LOS (FUDC)

SHUTTER-OPEN

DS3-MISM

LOS (MSUDC)

SIGLOSS

DSP-COMM-FAIL

LOS (OCN)

SNTP-HOST

DSP-FAIL

LOS (OTS)

SPAN-SW-EAST

DUP-IPADDR

LOS (TRUNK)

SPAN-SW-WEST

DUP-NODENAME

LOS-O

SQUELCH

EHIBATVG

LOS-P (OCH, OMS, OTS)

SQUELCHED

ELWBATVG

LOS-P (TRUNK)

SQM

EOC

LO-TXPOWER

SSM-DUS

EOC-L

LPBKCRS

SSM-FAIL

EQPT

LPBKDS1FEAC

SSM-LNC

EQPT-MISS

LPBKDS1FEAC-CMD

SSM-OFF

ERFI-P-CONN

LPBKDS3FEAC

SSM-PRC

ERFI-P-PAYLD

LPBKDS3FEAC-CMD

SSM-PRS

ERFI-P-SRVR

LPBKFACILITY (TRUNK)

SSM-RES

ERROR-CONFIG

LPBKFACILITY(DS1, DS3)

SSM-SDN-TN

ETH-LINKLOSS

LPBKFACILITY (EC1-12)

SSM-SETS

E-W-MISMATCH

LPBKFACILITY (ESCON)

SSM-SMC

EXCCOL

LPBKFACILITY (FC)

SSM-ST2

EXERCISE-RING-FAIL

LPBKFACILITY (FCMR)

SSM-ST3

EXERCISE-SPAN-FAIL

LPBKFACILITY (G1000)

SSM-ST3E

EXT

LPBKFACILITY (GE)

SSM-ST4

EXTRA-TRAF-PREEMPT

LPBKFACILITY (ISC)

SSM-STU

FAILTOSW

LPBKFACILITY (ML2)

SSM-TNC

FAILTOSW-PATH

LPBKFACILITY (OCN)

SWMTXMOD

FAILTOSWR

LPBKTERMINAL (TRUNK)

SWTOPRI

FAILTOSWS

LPBKTERMINAL (DS1, DS3)

SWTOSEC

FAN

LPBKTERMINAL (EC1-12)

SWTOTHIRD

FC-NO-CREDITS

LPBKTERMINAL (ESCON)

SYNC-FREQ

FE-AIS

LPBKTERMINAL (FC)

SYNCLOSS

FEC-MISM

LPBKTERMINAL (FCMR)

SYNCPRI

FE-DS1-MULTLOS

LPBKTERMINAL (G1000)

SYNCSEC

FE-DS1-NSA

LPBKTERMINAL (GE)

SYNCTHIRD

FE-DS1-SA

LPBKTERMINAL (ISC)

SYSBOOT

FE-DS1-SNGLLOS

LPBKTERMINAL (ML2)

TIM

FE-DS3-NSA

LPBKTERMINAL (OCN)

TIM-MON

FE-DS3-SA

LWBATVG

TIM-P

FE-EQPT-NSA

MAN-REQ

TPTFAIL (FCMR)

FE-FRCDWKSWBK-SPAN

MANRESET

TPTFAIL (G1000)

FE-FRCDWKSWPR-RING

MANSWTOINT

TPTFAIL (ML1000, ML100T, ML2)

FE-FRCDWKSWPR-SPAN

MANSWTOPRI

TRMT

FE-IDLE

MANSWTOSEC

TRMT-MISS

FE-LOCKOUTOFPR-SPAN

MANSWTOTHIRD

TX-AIS

FE-LOF

MANUAL-REQ-RING

TX-RAI

FE-LOS

MANUAL-REQ-SPAN

UNC-WORD

FE-MANWKSWBK-SPAN

MEA (AIP)

UNEQ-P

FE-MANWKSWPR-RING

MEA (BIC)

UNEQ-V

FE-MANWKSWPR-SPAN

MEA (EQPT)

UNREACHABLE-TARGET-POWER

FEPRLF

MEA (FAN)

UT-COMM-FAIL

FIBERTEMP-DEG

MEA (PPM)

UT-FAIL

FORCED-REQ

MEM-GONE

VCG-DEG

FORCED-REQ-RING

MEM-LOW

VCG-DOWN

FORCED-REQ-SPAN

MFGMEM

VOA-HDEG

FRCDSWTOINT

NO-CONFIG

VOA-HFAIL

FRCDSWTOPRI

OCHNC-INC

VOA-LDEG

FRCDSWTOSEC

ODUK-1-AIS-PM

VOA-LFAIL

FRCDSWTOTHIRD

ODUK-2-AIS-PM

WKSWPR

FRNGSYNC

ODUK-3-AIS-PM

WTR

FSTSYNC

ODUK-4-AIS-PM

WVL-MISMATCH


2.3  Alarm Logical Objects

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

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


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


Table 2-7 Alarm Logical Object Type Definition 

Logical Object
Definition
2R

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

AICI-AEP

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

AIP

Auxiliary interface protection module.

AOTS

Amplified optical transport section.

BIC

Backplane interface connector.

BITS

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

BPLANE

The backplane.

DS1

A DS-1 line on a DS-1 or DS-3 electrical card (DS1-14, DS1N-14, DS3-12, DS3N-12, DS3-12E, DS3N-12E, DS3XM-6, DS3XM-12).

DS3

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

E1000F

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

E100T

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

EC1-12

An EC1-12 electrical card.

ENV

An environmental alarm port.

EQPT

A card, its physical objects, and its logical objects as they are located 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.

ESCON

Enterprise System Connection fiber optic technology, referring to the following transponder (TXP) cards: TXP_MR_2.5G, TXPP_MR_2.5G.

EXT-SREF

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

FAN

Fan-tray assembly.

FC

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

FCMR

An FC_MR-4 Fibre Channel card.

FICON

Fiber Connection fiber optic technology, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G.

FUDC

SONET F1 byte user data channel for ONS 15454 ML-Series Ethernet cards.

G1000

A G1000 Ethernet card (G1000-4).

GE

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

GFP-FAC

Generic framing procedure facility port, referring to all MXP and TXP cards.

ISC

Inter-service channel, referring to MXP and TXP cards.

ML1000

An ML1000 Ethernet card (ML1000-2).

ML100T

An ML100 card (ML100T-12).

ML2

This object is used in the ONS 15310 platform and is reserved for future use in the ONS 15454 platform.

MSUDC

Multiplex section user data channel.

NE

The entire network element.

NE-SREF

The timing status of the NE.

OCH

The optical channel, referring to Dense Wavelength Division Multiplexer (DWDM) cards. DWDM cards on the ONS 15454 include the OSCM, OSC-CSM, OPT-PRE, OPT-BST, 32MUX-O, 32DMX-O, 32DMX, 4MD-xx.x,AD-4B-xx.x, AD-1B-xx.x, AD-4C-xx.x, AD-2C-xx.x, AD-1C-xx.x, and the 32WSS.

OCHNC_CONN

The optical channel connection, referring to DWDM cards.

OCN

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

OMS

Optical multiplex section.

OTS

Optical transport section.

PPM

Pluggable port module, referring to MXP and TXP cards.

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; referring to MXP or TXP cards.

UCP-CKT

Unified control plane circuit.

UCP-IPCC

Unified control plane IP control channel.

UCP-NBR

Unified control plane neighbor.

VCG

A virtual concatenation group of virtual tributaries (VT).

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 lists all ONS 15454 Release 4.7 alarms and logical objects as they are given in the system alarm profile. The list entries are organized by logical object name and then by alarm or condition name. Each entry contains a page number that refers to an alarm description in this chapter. Where appropriate, the alarm entries also contain troubleshooting procedures.


Note The list is given here exactly as it is shown in CTC, and in some cases does not follow alphabetical order.


Table 2-8 Alarm Index by Logical Object 

2R::ALS

FC::LOCKOUT-REQ

OCN::SQUELCH

2R::AS-CMD

FC::LPBKFACILITY (FC)

OCN::SQUELCHED

2R::AS-MT

FC::LPBKTERMINAL (FC)

OCN::SSM-DUS

2R::FAILTOSW

FC::MANUAL-REQ-SPAN

OCN::SSM-FAIL

2R::FORCED-REQ-SPAN

FC::OUT-OF-SYNC

OCN::SSM-OFF

2R::HI-LASERBIAS

FC::SIGLOSS

OCN::SSM-PRS

2R::HI-RXPOWER

FC::SQUELCHED

OCN::SSM-RES

2R::HI-TXPOWER

FC::SYNCLOSS

OCN::SSM-SMC

2R::LO-RXPOWER

FC::WKSWPR

OCN::SSM-ST2

2R::LO-TXPOWER

FC::WTR

OCN::SSM-ST3

2R::LOCKOUT-REQ

FCMR::AS-CMD

OCN::SSM-ST3E

2R::LOS (2R)

FCMR::AS-MT

OCN::SSM-ST4

2R::MANUAL-REQ-SPAN

FCMR::FC-NO-CREDITS

OCN::SSM-STU

2R::SQUELCHED

FCMR::LPBKFACILITY (FCMR)

OCN::SSM-TNC

2R::WKSWPR

FCMR::LPBKTERMINAL (FCMR)

OCN::SYNC-FREQ

2R::WTR

FCMR::PORT-MISMATCH

OCN::TIM

AICI-AEP::EQPT

FCMR::SIGLOSS

OCN::TIM-MON

AICI-AEP::MFGMEM

FCMR::SYNCLOSS

OCN::WKSWPR

AICI-AIE::EQPT

FCMR::TPTFAIL (FCMR)

OCN::WTR

AICI-AIE::MFGMEM

FUDC::AIS

OMS::APC-CORRECTION-SKIPPED

AIP::INVMACADR

FUDC::LOS (FUDC)

OMS::APC-OUT-OF-RANGE

AIP::MEA (AIP)

G1000::AS-CMD

OMS::AS-CMD

AIP::MFGMEM

G1000::AS-MT

OMS::AS-MT

AOTS::ALS

G1000::CARLOSS (G1000)

OMS::LOS-O

AOTS::AMPLI-INIT

G1000::LPBKFACILITY (G1000)

OMS::LOS-P (OCH, OMS, OTS)

AOTS::APC-CORRECTION-SKIPPED

G1000::LPBKTERMINAL (G1000)

OMS::OPWR-HDEG

AOTS::APC-OUT-OF-RANGE

G1000::TPTFAIL (G1000)

OMS::OPWR-HFAIL

AOTS::AS-CMD

GE::ALS

OMS::OPWR-LDEG

AOTS::AS-MT

GE::AS-CMD

OMS::OPWR-LFAIL

AOTS::CASETEMP-DEG

GE::AS-MT

OMS::PARAM-MISM

AOTS::FIBERTEMP-DEG

GE::CARLOSS (GE)

OMS::VOA-HDEG

AOTS::GAIN-HDEG

GE::FAILTOSW

OMS::VOA-HFAIL

AOTS::GAIN-HFAIL

GE::FORCED-REQ-SPAN

OMS::VOA-LDEG

AOTS::GAIN-LDEG

GE::GE-OOSYNC

OMS::VOA-LFAIL

AOTS::GAIN-LFAIL

GE::HI-LASERBIAS

OSC-RING::RING-ID-MIS

AOTS::LASER-APR

GE::HI-RXPOWER

OTS::APC-CORRECTION-SKIPPED

AOTS::LASERBIAS-DEG

GE::HI-TXPOWER

OTS::APC-OUT-OF-RANGE

AOTS::LASERBIAS-FAIL

GE::LO-RXPOWER

OTS::AS-CMD

AOTS::LASERTEMP-DEG

GE::LO-TXPOWER

OTS::AS-MT

AOTS::OPWR-HDEG

GE::LOCKOUT-REQ

OTS::AWG-DEG

AOTS::OPWR-HFAIL

GE::LPBKFACILITY (GE)

OTS::AWG-FAIL

AOTS::OPWR-LDEG

GE::LPBKTERMINAL (GE)

OTS::AWG-OVERTEMP

AOTS::OPWR-LFAIL

GE::MANUAL-REQ-SPAN

OTS::AWG-WARM-UP

AOTS::OSRION

GE::OUT-OF-SYNC

OTS::LASERBIAS-DEG

AOTS::PARAM-MISM

GE::SIGLOSS

OTS::LOS (OTS)

AOTS::VOA-HDEG

GE::SQUELCHED

OTS::LOS-O

AOTS::VOA-HFAIL

GE::SYNCLOSS

OTS::LOS-P (OCH, OMS, OTS)

AOTS::VOA-LDEG

GE::WKSWPR

OTS::OPWR-HDEG

AOTS::VOA-LFAIL

GE::WTR

OTS::OPWR-HFAIL

BIC::MEA (BIC)

GFP-FAC::GFP-CSF

OTS::OPWR-LDEG

BITS::AIS

GFP-FAC::GFP-DE-MISMATCH

OTS::OPWR-LFAIL

BITS::BPV

GFP-FAC::GFP-EX-MISMATCH

OTS::OSRION

BITS::HI-CCVOLT

GFP-FAC::GFP-LFD

OTS::PARAM-MISM

BITS::LOF (BITS)

GFP-FAC::GFP-NO-BUFFERS

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

BITS::LOS (BITS)

GFP-FAC::GFP-UP-MISMATCH

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

BITS::SSM-DUS

ISC::ALS

OTS::SHUTTER-OPEN

BITS::SSM-FAIL

ISC::AS-CMD

OTS::VOA-HDEG

BITS::SSM-OFF

ISC::AS-MT

OTS::VOA-HFAIL

BITS::SSM-PRS

ISC::CARLOSS (ISC)

OTS::VOA-LDEG

BITS::SSM-RES

ISC::FAILTOSW

OTS::VOA-LFAIL

BITS::SSM-SMC

ISC::FORCED-REQ-SPAN

PPM::AS-CMD

BITS::SSM-ST2

ISC::GE-OOSYNC

PPM::AS-MT

BITS::SSM-ST3

ISC::HI-LASERBIAS

PPM::EQPT

BITS::SSM-ST3E

ISC::HI-RXPOWER

PPM::HI-LASERBIAS

BITS::SSM-ST4

ISC::HI-TXPOWER

PPM::HI-LASERTEMP

BITS::SSM-STU

ISC::LO-RXPOWER

PPM::HI-TXPOWER

BITS::SSM-TNC

ISC::LO-TXPOWER

PPM::IMPROPRMVL

BITS::SYNC-FREQ

ISC::LOCKOUT-REQ

PPM::LO-TXPOWER

BPLANE::AS-CMD

ISC::LOS (ISC)

PPM::MEA (PPM)

BPLANE::MFGMEM

ISC::LPBKFACILITY (ISC)

PPM::MFGMEM

DS1::AIS

ISC::LPBKTERMINAL (ISC)

PWR::AS-CMD

DS1::AS-CMD

ISC::MANUAL-REQ-SPAN

PWR::BAT-FAIL

DS1::AS-MT

ISC::OUT-OF-SYNC

PWR::EHIBATVG

DS1::LOF (DS1)

ISC::SIGLOSS

PWR::ELWBATVG

DS1::LOS (DS1)

ISC::SQUELCHED

PWR::HIBATVG

DS1::LPBKDS1FEAC

ISC::SYNCLOSS

PWR::LWBATVG

DS1::LPBKDS1FEAC-CMD

ISC::WKSWPR

STSMON::AIS-P

DS1::LPBKFACILITY(DS1, DS3)

ISC::WTR

STSMON::AUTOSW-AIS

DS1::LPBKTERMINAL (DS1, DS3)

ML1000::AS-CMD

STSMON::AUTOSW-LOP (STSMON)

DS1::RAI

ML1000::AS-MT

STSMON::AUTOSW-PDI

DS1::RCVR-MISS

ML1000::CARLOSS (ML100T, ML1000, ML2)

STSMON::AUTOSW-SDBER

DS1::SD (DS1, DS3)

ML1000::GFP-CSF

STSMON::AUTOSW-SFBER

DS1::SF (DS1, DS3)

ML1000::GFP-DE-MISMATCH

STSMON::AUTOSW-UNEQ (STSMON)

DS1::SSM-DUS

ML1000::GFP-EX-MISMATCH

STSMON::ERFI-P-CONN

DS1::SSM-FAIL

ML1000::GFP-LFD

STSMON::ERFI-P-PAYLD

DS1::SSM-OFF

ML1000::GFP-NO-BUFFERS

STSMON::ERFI-P-SRVR

DS1::SSM-PRS

ML1000::GFP-UP-MISMATCH

STSMON::FAILTOSW-PATH

DS1::SSM-RES

ML1000::TPTFAIL (ML1000, ML100T, ML2)

STSMON::FORCED-REQ

DS1::SSM-SMC

ML100T::AS-CMD

STSMON::LOCKOUT-REQ

DS1::SSM-ST2

ML100T::AS-MT

STSMON::LOP-P

DS1::SSM-ST3

ML100T::CARLOSS (ML100T, ML1000, ML2)

STSMON::LPBKCRS

DS1::SSM-ST3E

ML100T::GFP-CSF

STSMON::MAN-REQ

DS1::SSM-ST4

ML100T::GFP-DE-MISMATCH

STSMON::PDI-P

DS1::SSM-STU

ML100T::GFP-EX-MISMATCH

STSMON::PLM-P

DS1::SSM-TNC

ML100T::GFP-LFD

STSMON::RFI-P

DS1::SYNC-FREQ

ML100T::GFP-NO-BUFFERS

STSMON::SD-P

DS1::TRMT

ML100T::GFP-UP-MISMATCH

STSMON::SF-P

DS1::TRMT-MISS

ML100T::TPTFAIL (ML1000, ML100T, ML2)

STSMON::TIM-P

DS1::TX-AIS

ML2::AS-CMD

STSMON::UNEQ-P

DS1::TX-RAI

ML2::AS-MT

STSMON::WKSWPR

DS3::AIS

ML2::CARLOSS (ML100T, ML1000, ML2)

STSMON::WTR

DS3::AS-CMD

ML2::GFP-CSF

STSTRM::AIS-P

DS3::AS-MT

ML2::GFP-LFD

STSTRM::AS-MT-OOG

DS3::DS3-MISM

ML2::LPBKFACILITY (ML2)

STSTRM::AU-LOF

DS3::FE-AIS

ML2::LPBKTERMINAL (ML2)

STSTRM::ENCAP-MISMATCH-P

DS3::FE-DS1-MULTLOS

ML2::TPTFAIL (ML1000, ML100T, ML2)

STSTRM::ERFI-P-CONN

DS3::FE-DS1-NSA

MSUDC::AIS

STSTRM::ERFI-P-PAYLD

DS3::FE-DS1-SA

MSUDC::LOS (MSUDC)

STSTRM::ERFI-P-SRVR

DS3::FE-DS1-SNGLLOS

NE-SREF::FRCDSWTOINT

STSTRM::LCAS-CRC

DS3::FE-DS3-NSA

NE-SREF::FRCDSWTOPRI

STSTRM::LCAS-RX-FAIL

DS3::FE-DS3-SA

NE-SREF::FRCDSWTOSEC

STSTRM::LCAS-TX-ADD

DS3::FE-EQPT-NSA

NE-SREF::FRCDSWTOTHIRD

STSTRM::LCAS-TX-DNU

DS3::FE-IDLE

NE-SREF::FRNGSYNC

STSTRM::LOM

DS3::FE-LOF

NE-SREF::FSTSYNC

STSTRM::LOP-P

DS3::FE-LOS

NE-SREF::HLDOVRSYNC

STSTRM::OOU-TPT

DS3::INC-ISD

NE-SREF::MANSWTOINT

STSTRM::PDI-P

DS3::LOF (DS3)

NE-SREF::MANSWTOPRI

STSTRM::PLM-P

DS3::LOS (DS3)

NE-SREF::MANSWTOSEC

STSTRM::RFI-P

DS3::LPBKDS1FEAC

NE-SREF::MANSWTOTHIRD

STSTRM::SD-P

DS3::LPBKDS3FEAC

NE-SREF::SSM-PRS

STSTRM::SF-P

DS3::LPBKDS3FEAC-CMD

NE-SREF::SSM-RES

STSTRM::SQM

DS3::LPBKFACILITY(DS1, DS3)

NE-SREF::SSM-SMC

STSTRM::TIM-P

DS3::LPBKTERMINAL (DS1, DS3)

NE-SREF::SSM-ST2

STSTRM::UNEQ-P

DS3::RAI

NE-SREF::SSM-ST3

TRUNK::AIS

DS3::SD (DS1, DS3)

NE-SREF::SSM-ST3E

TRUNK::ALS

DS3::SF (DS1, DS3)

NE-SREF::SSM-ST4

TRUNK::AS-CMD

E1000F::AS-CMD

NE-SREF::SSM-STU

TRUNK::AS-MT

E1000F::CARLOSS (E100T, E1000F)

NE-SREF::SSM-TNC

TRUNK::CARLOSS (TRUNK)

E100T::AS-CMD

NE-SREF::SWTOPRI

TRUNK::DSP-COMM-FAIL

E100T::CARLOSS (E100T, E1000F)

NE-SREF::SWTOSEC

TRUNK::DSP-FAIL

EC1-12::AIS-L

NE-SREF::SWTOTHIRD

TRUNK::EOC

EC1-12::AS-CMD

NE-SREF::SYNCPRI

TRUNK::EOC-L

EC1-12::AS-MT

NE-SREF::SYNCSEC

TRUNK::FAILTOSW

EC1-12::FE-FRCDWKSWBK-SPAN

NE-SREF::SYNCTHIRD

TRUNK::FEC-MISM

EC1-12::FE-MANWKSWBK-SPAN

NE::APC-DISABLED

TRUNK::FORCED-REQ-SPAN

EC1-12::HELLO

NE::APC-END

TRUNK::GCC-EOC

EC1-12::HI-LASERTEMP

NE::AS-CMD

TRUNK::GE-OOSYNC

EC1-12::LO-LASERTEMP

NE::AUD-LOG-LOSS

TRUNK::HI-LASERBIAS

EC1-12::LOF (EC1-12)

NE::AUD-LOG-LOW

TRUNK::HI-RXPOWER

EC1-12::LOS (EC1-12)

NE::DATAFLT

TRUNK::HI-TXPOWER

EC1-12::LPBKFACILITY (EC1-12)

NE::DBOSYNC

TRUNK::LO-RXPOWER

EC1-12::LPBKTERMINAL (EC1-12)

NE::DUP-IPADDR

TRUNK::LO-TXPOWER

EC1-12::RFI-L

NE::DUP-NODENAME

TRUNK::LOCKOUT-REQ

EC1-12::SD-L

NE::ETH-LINKLOSS

TRUNK::LOF (TRUNK)

EC1-12::SF-L

NE::HITEMP

TRUNK::LOM

EC1-12::SQUELCHED

NE::I-HITEMP

TRUNK::LOS (TRUNK)

EC1-12::TIM-MON

NE::INTRUSION-PSWD

TRUNK::LOS-P (TRUNK)

ENVALRM::EXT

NE::LAN-POL-REV

TRUNK::LPBKFACILITY (TRUNK)

EQPT::AS-CMD

NE::OPTNTWMIS

TRUNK::LPBKTERMINAL (TRUNK)

EQPT::AS-MT

NE::SNTP-HOST

TRUNK::MANUAL-REQ-SPAN

EQPT::AUTORESET

NE::SYSBOOT

TRUNK::ODUK-AIS-PM

EQPT::BKUPMEMP

OCH::AS-CMD

TRUNK::ODUK-2-AIS-PM

EQPT::CARLOSS (EQPT)

OCH::AS-MT

TRUNK::ODUK-3-AIS-PM

EQPT::CLDRESTART

OCH::LOS-O

TRUNK::ODUK-4-AIS-PM

EQPT::COMIOXC

OCH::LOS-P (OCH, OMS, OTS)

TRUNK::ODUK-BDI-PM

EQPT::COMM-FAIL

OCH::OPWR-HDEG

TRUNK::ODUK-LCK-PM

EQPT::CONTBUS-A-18

OCH::OPWR-HFAIL

TRUNK::ODUK-OCI-PM

EQPT::CONTBUS-B-18

OCH::OPWR-LDEG

TRUNK::ODUK-SD-PM

EQPT::CONTBUS-IO-A

OCH::OPWR-LFAIL

TRUNK::ODUK-SF-PM

EQPT::CONTBUS-IO-B

OCH::PARAM-MISM

TRUNK::ODUK-TIM-PM

EQPT::CTNEQPT-MISMATCH

OCH::PORT-ADD-PWR-DEG-HI

TRUNK::OTUK-AIS

EQPT::CTNEQPT-PBPROT

OCH::PORT-ADD-PWR-DEG-LOW

TRUNK::OTUK-BDI

EQPT::CTNEQPT-PBWORK

PORT-ADD-PWR-FAIL-HI

TRUNK::OTUK-IAE

EQPT::EQPT

OCH::PORT-ADD-PWR-FAIL-LOW

TRUNK::OTUK-LOF

EQPT::ERROR-CONFIG

OCH::UNREACHABLE-TARGET-POWER

TRUNK::OTUK-SD

EQPT::EXCCOL

OCH::VOA-HDEG

TRUNK::OTUK-SD

EQPT::FAILTOSW

OCH::VOA-HFAIL

TRUNK::OTUK-TIM

EQPT::FORCED-REQ

OCH::VOA-LDEG

TRUNK::OUT-OF-SYNC

EQPT::HITEMP

OCH::VOA-LFAIL

TRUNK::PTIM

EQPT::IMPROPRMVL

OCHNC-CONN::OCHNC-INC

TRUNK::RFI

EQPT::INHSWPR

OCN::AIS-L

TRUNK::SD (TRUNK)

EQPT::INHSWWKG

OCN::ALS

TRUNK::SF (TRUNK)

EQPT::IOSCFGCOPY

OCN::APS-INV-PRIM

TRUNK::SIGLOSS

EQPT::LOCKOUT-REQ

OCN::APS-PRIM-FAC

TRUNK::SQUELCHED

EQPT::MAN-REQ

OCN::APS-PRIM-SEC-MISM

TRUNK::SSM-DUS

EQPT::MANRESET

OCN::APSB

TRUNK::SSM-FAIL

EQPT::MEA (EQPT)

OCN::APSCDFLTK

TRUNK::SSM-LNC

EQPT::MEM-GONE

OCN::APSC-IMP

TRUNK::SSM-OFF

EQPT::MEM-LOW

OCN::APSCINCON

TRUNK::SSM-PRC

EQPT::NO-CONFIG

OCN::APSCM

TRUNK::SSM-PRS

EQPT::PEER-NORESPONSE

OCN::APSCNMIS

TRUNK::SSM-RES

EQPT::PROTNA

OCN::APSIMP

TRUNK::SSM-SDN-TN

EQPT::PWR-FAIL-A

OCN::APSMM

TRUNK::SSM-SETS

EQPT::PWR-FAIL-B

OCN::AS-CMD

TRUNK::SSM-SMC

EQPT::PWR-FAIL-RET-A

OCN::AS-MT

TRUNK::SSM-ST2

EQPT::PWR-FAIL-RET-B

OCN::AUTOLSROFF

TRUNK::SSM-ST3

EQPT::RUNCFG-SAVENEED

OCN::BLSROSYNC

TRUNK::SSM-ST3E

EQPT::SFTWDOWN

OCN::E-W-MISMATCH

TRUNK::SSM-ST4

EQPT::SWMTXMOD

OCN::EOC

TRUNK::SSM-STU

EQPT::WKSWPR

OCN::EOC-L

TRUNK::SSM-TNC

EQPT::WTR

OCN::EXERCISE-RING-FAIL

TRUNK::SYNC-FREQ

ESCON::ALS

OCN::EXERCISE-SPAN-FAIL

TRUNK::SYNCLOSS

ESCON::AS-CMD

OCN::EXTRA-TRAF-PREEMPT

TRUNK::TIM

ESCON::AS-MT

OCN::FAILTOSW

TRUNK::TIM-MON

ESCON::FAILTOSW

OCN::FAILTOSWR

TRUNK::UNC-WORD

ESCON::FORCED-REQ-SPAN

OCN::FAILTOSWS

TRUNK::UT-COMM-FAIL

ESCON::HI-LASERBIAS

OCN::FE-FRCDWKSWBK-SPAN

TRUNK::UT-FAIL

ESCON::HI-RXPOWER

OCN::FE-FRCDWKSWPR-RING

TRUNK::WKSWPR

ESCON::HI-TXPOWER

OCN::FE-FRCDWKSWPR-SPAN

TRUNK::WTR

ESCON::LO-RXPOWER

OCN::FE-LOCKOUTOFPR-SPAN

TRUNK::WVL-MISMATCH

ESCON::LO-TXPOWER

OCN::FE-MANWKSWBK-SPAN

UCP-CKT::CKTDOWN

ESCON::LOCKOUT-REQ

OCN::FE-MANWKSWPR-RING

UCP-IPCC::LMP-HELLODOWN

ESCON:: LOS (ESCON)

OCN::FE-MANWKSWPR-SPAN

UCP-IPCC::LMP-NDFAIL

ESCON::LPBKFACILITY (ESCON)

OCN::FEPRLF

UCP-NBR::RSVP-HELLODOWN

ESCON::LPBKTERMINAL (ESCON)

OCN::FORCED-REQ-RING

VCG::LOA

ESCON::MANUAL-REQ-SPAN

OCN::FORCED-REQ-SPAN

VCG::VCG-DEG

ESCON::SQUELCHED

OCN::FULLPASSTHR-BI

VCG::VCG-DOWN

ESCON::WKSWPR

OCN::HELLO

VT-MON::AIS-V

ESCON::WTR

OCN::HI-LASERBIAS

VT-MON::AUTOSW-AIS

EXT-SREF::FRCDSWTOPRI

OCN::HI-LASERTEMP

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

EXT-SREF::FRCDSWTOSEC

OCN::HI-RXPOWER

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

EXT-SREF::FRCDSWTOTHIRD

OCN::HI-TXPOWER

VT-MON::FAILTOSW-PATH

EXT-SREF::MANSWTOPRI

OCN::KB-PASSTHR

VT-MON::FORCED-REQ

EXT-SREF::MANSWTOSEC

OCN::KBYTE-APS-CHANNEL-FAILURE

VT-MON::LOCKOUT-REQ

EXT-SREF::MANSWTOTHIRD

OCN::LASEREOL

VT-MON::LOP-V

EXT-SREF::SWTOPRI

OCN::LKOUTPR-S

VT-MON::MAN-REQ

EXT-SREF::SWTOSEC

OCN::LO-LASERTEMP

VT-MON::SD-V

EXT-SREF::SWTOTHIRD

OCN::LO-RXPOWER

VT-MON::SF-V

EXT-SREF::SYNCPRI

OCN::LO-TXPOWER

VT-MON::UNEQ-V

EXT-SREF::SYNCSEC

OCN::LOCKOUT-REQ

VT-MON::WKSWPR

EXT-SREF::SYNCTHIRD

OCN::LOF (OCN)

VT-MON::WTR

FAN::EQPT-MISS

OCN::LOS (OCN)

VT-TERM::AIS-V

FAN::FAN

OCN::LPBKFACILITY (OCN)

VT-TERM::AS-MT-OOG

FAN::MEA (FAN)

OCN::LPBKTERMINAL (OCN)

VT-TERM::LCAS-CRC

FAN::MFGMEM

OCN::MANUAL-REQ-RING

VT-TERM::LCAS-RX-FAIL

FC::ALS

OCN::MANUAL-REQ-SPAN

VT-TERM::LCAS-TX-ADD

FC::AS-CMD

OCN::PRC-DUPID

VT-TERM::LCAS-TX-DNU

FC::AS-MT

OCN::RFI-L

VT-TERM::LOM

FC::CARLOSS (FC)

OCN::RING-ID-MIS

VT-TERM::LOP-V

FC::FAILTOSW

OCN::RING-MISMATCH

VT-TERM::OOU-TPT

FC::FORCED-REQ-SPAN

OCN::RING-SW-EAST

VT-TERM::PLM-V

FC::GE-OOSYNC

OCN::RING-SW-WEST

VT-TERM::RFI-V

FC::HI-LASERBIAS

OCN::SD-L

VT-TERM::SD-P

FC::HI-RXPOWER

OCN::SF-L

VT-TERM::SF-P

FC::HI-TXPOWER

OCN::SPAN-SW-EAST

VT-TERM::SQM

FC::LO-RXPOWER

OCN::SPAN-SW-WEST

VT-TERM::UNEQ-V

FC::LO-TXPOWER


2.5  DS3-12 E Line Alarms

Unlike the standard DS-3 card, which uses the unframed format exclusively, the DS3-12E card provides three choices: unframed, M13, or C Bit. The choice of framing format determines the line alarms that the DS3-12E card reports. The following table lists the line alarms reported under each format.

The choice of framing format does not affect the reporting of STS alarms. Regardless of format, the DS3-12E card reports the same STS alarms and conditions, listed in Table 2-9, as the standard DS-3 card reports.

Table 2-9 DS3-12E Line Alarms 

Alarm
UNFRAMED
M13
CBIT

LOS (DS1), LOS (DS3)

Yes

Yes

Yes

AIS

Yes

Yes

Yes

LOF (DS1), LOF (DS3)

No

Yes

Yes

FE-IDLE

No

Yes

Yes

RAI

No

Yes

Yes

Terminal Lpbk (LPBKTERMINAL (DS1, DS3)

Yes

Yes

Yes

Facility Lpbk (LPBKFACILITY(DS1, DS3)

Yes

Yes

Yes

FE Lpbk (LPBKDS1FEAC, LPBKDS3FEAC)

No

No

Yes

FE Common Equipment Failure (FE-DS1-NSA, FE-DS3-NSA)

No

No

Yes

FE Equipment Failure-SA (FE-DS3-SA)

No

No

Yes

FE-LOS

No

No

Yes

FE-LOF

No

No

Yes

FE-AIS

No

No

Yes

FE-IDLE

No

No

Yes

FE Equipment Failure-NSA (FE-EQPT-NSA)

No

No

Yes


2.6  Trouble Notifications

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

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

2.6.1  Alarm Characteristics

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

2.6.2  Condition Characteristics

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

2.6.3  Severities

The ONS 15454 uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR):

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

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

Minor (MN) alarms generally are those that do not affect service.

Not Alarmed (NA) conditions are information indicators, such as for state (FRNGSYNC) or an event (FRCSWTOPRI). They might or might not require troubleshooting, as indicated in the entries.

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

All alarm, condition, and not-reported event severities listed in this manual are default profile settings. However in situations when traffic is not lost—such as when the alarm occurs on protected ports or circuits—alarms having Critical (CR) or Major (MJ) default severities can be demoted to lower severities such as Minor (MN) or Non-Service Affecting (NSA) as defined in Telcordia GR-474.

Severities can also be customized for an entire network or for single nodes, down to the port level by changing or downloading customized alarm profiles. These custom severities are subject to the standard severity-demoting rules given in Telcordia GR-474.

2.6.4  Service Effect

Service-Affecting (SA) alarms—those that interrupt service—might be Critical (CR), Major (MJ), or Minor (MN) severity alarms. In some cases the severity of an alarm might not correspond to its service effect. For example, the AUTOSW-LOP alarm for the VTMON object is minor but service-affecting because it indicates a traffic switch has occurred directing traffic away from a loss of circuit path. Non-Service Affecting (NSA) alarms always have a Minor (MN) default severity.

2.6.5  States

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

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

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

A transient (T) event is one that is automatically raised and cleared in CTC during system changes such as user login, logout, loss of connection to node view, etc. Transient events do not require user action.


Note Transient events are not defined in this documentation release.


2.7  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-NR) 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.8  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, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the Cisco ONS 15454 DWDM Installation and Operations 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 DWDM Installation and Operations Guide.


2.8.1  AIS

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

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

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 AIS condition 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 ONS 15454 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-142, or out-of-service (OOS,MT or OOS,DSBLD) ports.

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

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


2.8.2  AIS-L

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

Logical Objects: EC1-12, OCN

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

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 AIS condition 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).


2.8.3  AIS-P

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

Logical Objects: STSMON, STSTRM

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

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 AIS condition 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).


2.8.4  AIS-V

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

Logical Objects: VT-MON, VT-TERM

The AIS Virtual Tributary (VT) condition 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 AIS condition 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 "1.8.2  AIS-V on DS3XM-6 Unused VT Circuits" section on page 1-59 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).


2.8.5  ALS

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

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

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


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


2.8.6  AMPLI-INIT

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

2.8.7  APC-CORRECTION-SKIPPED

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

Logical Objects: AOTS, OMS, OTS

The Automatic Power Control (APC) Correction Skipped condition occurs when the actual power level of a DWDM channel exceeds the threshold setting by 3 dB or more. The APC compares actual power levels with power level thresholds every 10 minutes or after any channel allocation is performed. If the actual power level is above or below the setting within 3 dB, APC corrects the level. If the actual power level exceeds the threshold by +3 dB or -3 dB, APC cannot correct the level and the APC-CORRECTION-SKIPPED condition is raised.

There is no operator action to resolve this condition. It stays raised until the power level problem is resolved and APC takes a normal reading.


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


2.8.8  APC-DISABLED

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

Logical Object: NE

The APC Disabled alarm occurs when the information related to the number of DWDM channels is not reliable. The alarm can occur when the any related alarms also occur: the "AMPLI-INIT" condition on page 2-24, the "EQPT" alarm on page 2-72, the "IMPROPRMVL" alarm on page 2-115, or the "MEA (EQPT)" alarm on page 2-166. 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 using procedures in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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


2.8.9  APC-END

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

Logical Object: NE

The APC Terminated on Manual Request condition is raised when the APC application terminates after being manually launched from CTC or TL1. It is an informational condition.


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


2.8.10  APC-OUT-OF-RANGE

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

Logical Objects: AOTS, OMS, OTS

The APC Out of Range condition is raised on amplifier cards (OPT-PRE and OPT-BST); optical service channel cards (OSCM and OSC-CSM); multiplexer cards (32MUX-O); demultiplexer cards (32DMX, 32DMX-O), and optical add/drop multiplexer cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x) when the requested gain or attenuation setpoint cannot be set because it exceeds the port parameter range.

Clear the APC-OUT-OF-RANGE Condition


Step 1 Provision the correct setpoint. For instructions, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Installation and Operations Guide. The condition clears when the APC setting is corrected, and APC does not detect any errors in its next cycle.

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


2.8.11  APSB

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

Logical Object: OCN

The Automatic Protection Switching (APS) Channel Byte Failure 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 15454.


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

Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you might need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Traffic Card" procedure.


Caution For the ONS 15454, 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used alarm troubleshooting procedures.


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


2.8.12  APSCDFLTK

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

Logical Object: OCN

The APS Default K Byte Received alarm occurs during bidirectional line switched ring (BLSR) provisioning or when a 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-43.

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 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-77.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 DWDM Installation and Operations Guide provides a procedure for fibering BLSRs.

Step 5 If the alarm does not clear and 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 SDCC Terminations" procedure to ensure that SONET data communications channel (SDCC) terminations exist on each node.

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


2.8.13  APSC-IMP

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

Logical Object: OCN

An Improper SONET APS Code alarm indicates bad or invalid K bytes. The APSC-IMP alarm occurs on OC-N cards in a BLSR configuration and can occur during 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 on the lower-right 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.



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


2.8.14  APSCINCON

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

Logical Object: OCN

An APS Inconsistent 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 system, 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-142, the "LOF (OCN)" alarm on page 2-132, or the "AIS" alarm on page 2-22. Clearing these alarms clears the APSCINCON alarm.

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


2.8.15  APSCM

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

Logical Object: OCN

The APS Channel Mismatch 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 ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS-NR) 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 on the lower-right 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 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 protection-card channel fibers.

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


2.8.16  APSCNMIS

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

Logical Object: OCN

The APS Node ID Mismatch 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 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 node 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 "Initiate a Lock Out on a BLSR Protect Span" procedure to lockout 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.17  APSIMP

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

Logical Object: OCN

The APS Invalid Code 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 remote defect indication (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. For instructions, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

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

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

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


2.8.18  APS-INV-PRIM

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

Logical Object: OCN

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


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


2.8.19  APS-PRIM-FAC

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

Logical Object: OCN

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


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


Clear the APS-PRIM-FAC Condition


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

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


2.8.20  APSMM

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

Logical Object: OCN

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

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

Clear the APSMM Alarm


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

a. Click the Provisioning > Protection tabs.

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

The chosen protection group is the protection group optically connected (with DCC connectivity) to the far end.

c. Click Edit.

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

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

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

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

Step 5 Click Apply.

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


2.8.21  APS-PRIM-SEC-MISM

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

Logical Object: OCN

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

Clear the APS-PRIM-SEC-MISM Alarm


Step 1 Ensure that the near end and far-end ports are correctly provisioned with the same way. For more information about optimized 1+1 configurations, refer to the Cisco ONS 15454 Procedure Guide.

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


2.8.22  AS-CMD

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

Logical Objects: 2R, AOTS, BPLANE, DS1, DS3, E1000F, E100T, EC1-12, EQPT, ESCON, FC, ML2, NE, OCH, OCN, OMS, OTS, PPM, PWR, TRUNK

The Alarms Suppressed by User Command 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. Suppressing alarms on a card also suppresses alarms on its ports.


Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.


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 ONS 15454 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).


2.8.23  AS-MT

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

Logical Objects: 2R, AOTS, DS1, DS3, EC1-12, EQPT, ESCON, FC, FCMR, G1000, GE, ISC, ML1000, ML100T, ML2, OCH, OCN, OMS, OTS, PPM, TRUNK

The Alarms Suppressed for Maintenance Command condition applies to OC-N and electrical cards and occurs when a port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations.


Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.


Clear the AS-MT Condition


Step 1 Complete the "Clear an OC-N Card Facility or Terminal Loopback Circuit" procedure.

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


2.8.24  AS-MT-OOG

Default Severity: Critical (CR), Service-Affecting (SA) if all VCAT members on an STS are placed OOS; Major (MJ), Service-Affecting (SA) for a single VT

Logical Object: VT-TERM

The Alarms Suppressed on an Out-Of-Group VCAT Member alarm is raised on an STS or VT member of a VCAT group whenever the member is in the IDLE (AS-MT-OOG) admin state. This alarm can be raised when a member is initially added to a group. In IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.

Clear the AS-MT-OOG Alarm


Step 1 The AS-MT-OOG alarm clears when an STS or VT member transitions to a different state from IDLE (AS-MT-OOG) or when it is removed completely from the VCAT group. It does not require troubleshooting unless it does not clear.

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


2.8.25  AUD-LOG-LOSS

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

Logical Object: NE

The Audit Trail 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. The log must be off-loaded using the following procedure 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.26  AUD-LOG-LOW

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

Logical Object: NE

The Audit Trail Log Low condition occurs when the audit trail log is 80 percent full.


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


2.8.27  AU-LOF

The Administrative Unit Loss of Multiframe alarm is not used in this platform in this release. It is reserved for future development.

2.8.28  AUTOLSROFF

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

Logical Object: OCN

The Auto Laser Shutdown 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 ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS-NR) 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-2).

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 Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used troubleshooting procedures.


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.8.29  AUTORESET

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

Logical Object: EQPT

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

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


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

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 Traffic Card" procedure.


Caution For the ONS 15454, 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.30  AUTOSW-AIS

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

Logical Objects: STSMON, VT-MON

The Automatic Path Protection Switch Caused by AIS condition indicates that automatic path 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 AIS condition 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.31  AUTOSW-LOP (STSMON)

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the "LOP-P" alarm on page 2-134. 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.32  AUTOSW-LOP (VT-MON)

Default Severity: 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 switching occurred because of the "LOP-V" alarm on page 2-135. 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.33  AUTOSW-PDI

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a "PDI-P" alarm on page 2-186. 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.34  AUTOSW-SDBER

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade (SD) caused automatic path 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 (DS1, DS3) Condition" procedure.

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


2.8.35  AUTOSW-SFBER

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

Logical Object: STSMON

The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal failure (SF) caused automatic path 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.36  AUTOSW-UNEQ (STSMON)

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

Logical Object: STSMON

The Automatic Path Protection Switch Caused by Unequipped condition indicates that an UNEQ 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.37  AUTOSW-UNEQ (VT-MON)

Default Severity: Minor (MN), Service-Affecting (SA)

Logical Object: VT-MON

AUTOSW-UNEQ (VT-MON) indicates that the "UNEQ-V" alarm on page 2-231 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.38  AWG-DEG

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

Logical Object: OTS

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

Clear the AWG-DEG Alarm


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

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


2.8.39  AWG-FAIL

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

Logical Object: OTS

The AWG Failure alarm occurs when an DWDM card heater-control circuit completely fails. The circuit failure disables wavelength transmission. The card must be replaced to restore traffic.

Clear the AWG-FAIL Alarm


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

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


2.8.40  AWG-OVERTEMP

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

Logical Object: OTS

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

Clear the AWG-OVERTEMP Alarm


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

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


2.8.41  AWG-WARM-UP

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

Logical Object: OTS

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


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


2.8.42  BAT-FAIL

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

Logical Object: PWR

The Battery Fail alarm occurs when one of the two power supplies (A or B) is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so 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. For instructions, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

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


2.8.43  BKUPMEMP

Default Severity: Critical (CR), Non-Service Affecting (NSA)

Logical Object: EQPT

The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2 card flash memory. The alarm occurs when the TCC2 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.

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-72. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.


Caution Software updating on a standby TCC2 can take up to 30 minutes.

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 cards are powered and enabled, reset the active TCC2 to make the standby TCC2 active. Complete the "Reset an Active TCC2 and Activate the Standby Card" procedure.

Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2 LED should be green.

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


2.8.44  BLSROSYNC

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

Logical Object: OCN

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


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 BLSROSYNC Alarm


Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the Cisco ONS 15454 DWDM Installation and Operations 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.45  BPV

The BPV alarm is not used in this release.

2.8.46  CARLOSS (E100T, E1000F)

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

Logical Objects: E1000F, E100T

A Carrier Loss alarm on the LAN E-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-142. 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 card rather than an Ethernet device, or an improperly installed Ethernet card. Ethernet card ports must be enabled 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).


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

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) Any Card" procedure for the Ethernet card.

Step 7 If the alarm does not clear, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.47  CARLOSS (EQPT)

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

Logical Object: EQPT

A Carrier Loss on the LAN 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, or for the ONS 15454, the LAN backplane pin connection. 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 node.


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 on the lower-right edge of the shelf assembly.

Clear the CARLOSS (EQPT) Alarm


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

a. Double-click the reporting MXP or TXP card.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment column and compare this with the contents of the Selected PPM area Rate column.

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

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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.48  CARLOSS (FC)

The Carrier Loss alarm for Fibre Channel is not used in this release. It is reserved for future development.

2.8.49  CARLOSS (G1000)

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

Logical Object: G1000

A Carrier Loss alarm on the LAN G-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-142. 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 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-225 or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G1000s) 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-227 for more information about alarms that occur when a point-to-point circuit exists between two cards.

Ethernet card ports must be enabled 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 on the lower-right 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. The correct specifications are listed in the "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71.

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 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 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-225 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 card'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 Maintenance > Loopback tabs.

c. If the service state is listed as OOS-MA, LPBK&MT, a loopback is provisioned. Go to Step 11.

Step 11 If a loopback was provisioned, complete the "Clear Other DS-N Card, EC-1, or G1000 Card Loopbacks" procedure.

On the G1000-4, 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 loopback condition, continue to Step 13.

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 ONS 15454 Ethernet manual cross-connect is used when another vendors' equipment sits between ONS nodes, 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 node 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 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) Any Card" procedure.

Step 14 If the alarm does not clear, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.50  CARLOSS (GE)

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

Logical Object: GE

The Carrier Loss for Gigabit Ethernet (GE) alarm occurs on MXP and TXP card PPM clients supporting 1-Gbps or 10-Gbps traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.

Clear the CARLOSS (GE) Alarm


Step 1 Ensure that the GE client is correctly configured:

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

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment column and compare this with the client equipment. If no PPM is provisioned, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for provisioning instructions.

d. If a PPM has been created, view the contents of the Selected PPM area Rate column and compare this rate with the client equipment data rate. If the PPM rate is differently provisioned, select the PPM, click Delete, then click Create and choose the correct rate for the equipment type.

Step 2 If there is no PPM misprovisioning, check for a fiber cut. An LOS alarm will also be present. If there is an alarm, complete the "Clear the LOS (OCN) Alarm" procedure.

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

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


2.8.51  CARLOSS (ISC)

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

Logical Object: ISC

The Carrier Loss for Inter-Service Channel (ISC) alarm occurs on TXP card PPM clients supporting ISC client traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.

Clear the CARLOSS (ISC) Alarm


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

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


2.8.52  CARLOSS (ML100T, ML1000, ML2)

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

Logical Objects:ML1000, ML100T, ML2

A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-142. 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 Cisco 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 Cisco IOS interface, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.


Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.


Clear the CARLOSS (ML100T, ML1000, ML2) 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 Cisco IOS CLI. Autonegotiation will restart.

Step 6 If the alarm does not clear, complete the "Create the Facility (Line) Loopback on the Source-Node MXP or TXP Port" procedure on page 1-7 and test the loopback.

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

Step 8 If the alarm does not clear, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.53  CARLOSS (TRUNK)

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

Logical Object: TRUNK

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

Clear the CARLOSS (TRUNK) Alarm


Step 1 Complete the "Clear the LOS (2R) Alarm" procedure.

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


2.8.54  CASETEMP-DEG

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

Logical Object: AOTS

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

Clear the CASETEMP-DEG Alarm


Step 1 Check for and resolve the "FAN" alarm on page 2-86 if it is raised against the shelf.

Step 2 If the alarm does not clear, complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

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


2.8.55  CKTDOWN

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

Logical Object: UCP-CKT

The unified control plane (UCP) Circuit Down 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 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 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 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 drop-down list. 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 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.56  CLDRESTART

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

Logical Object: EQPT

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


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

Clear the CLDRESTART Condition


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

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

Step 3 If the condition does not clear, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.57  COMIOXC

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

Logical Object: EQPT

The Input/Output Slot To Cross-Connect Communication Failure 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 "Typical Traffic 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. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

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) Any Card" procedure for the reporting cross-connect card.

Step 5 If the alarm does not clear, complete the "Physically Replace an In-Service Cross-Connect 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.58  COMM-FAIL

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

Logical Object: EQPT

The Plug-In Module (card) Communication Failure 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 Traffic 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 "CTC Card Resetting and Switching" section for commonly used procedures.


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


2.8.59  CONTBUS-A-18

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

Logical Object: EQPT

A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2 slot to TCC2 slot occurs when the main processor on the TCC2 in the first slot ("TCC A") loses communication with the coprocessor on the same card. This applies to the Slot 7 TCC2.


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

Clear the CONTBUS-A-18 Alarm


Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure to make the Slot 11 TCC2 active.

Step 2 Wait approximately 10 minutes for the Slot 7 TCC2 to reset as the standby TCC2. Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

Step 3 Position the cursor over the Slot 11 TCC2 and complete the "Reset an Active TCC2 and Activate the Standby Card" procedure to return the card to the active state.

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


2.8.60  CONTBUS-B-18

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

Logical Object: EQPT

A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2 slot to TCC2 slot occurs when the main processor on the TCC2 in the second slot ("TCC B") loses communication with the coprocessor on the same card. This applies to the Slot 11 TCC2.


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

Clear the CONTBUS-B-18 Alarm


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

Step 2 Wait approximately 10 minutes for the Slot 11 TCC2 to reset as the standby TCC2. Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

Step 3 Position the cursor over the Slot 7 TCC2 and complete the "Reset an Active TCC2 and Activate the Standby Card" procedure to return the Slot 11 TCC2 card to the active state.

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


2.8.61  CONTBUS-IO-A

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

Logical Object: EQPT

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

The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 switches to the protect TCC2. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2. 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, 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 on the lower-right 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-166 for the reporting card.

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

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

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

If CONTBUS-IO-A is raised on several cards at the same time, complete the "Reset an Active TCC2 and Activate the Standby Card" procedure.

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

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

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

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


2.8.62  CONTBUS-IO-B

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

Logical Object: EQPT

A TCC B to Shelf Communication Failure alarm occurs when the active Slot 11 TCC2 (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. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2. 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, 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 on the lower-right 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-166 for the reporting card.

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

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

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

Step 4 If CONTBUS-IO-A is raised on several cards at the same time, complete the "Reset an Active TCC2 and Activate the Standby Card" procedure.

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

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

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

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


2.8.63  CTNEQPT-MISMATCH

Default Severity: 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 DWDM Installation and Operations 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 Traffic Card" procedure for the mismatched card.

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


2.8.64  CTNEQPT-PBPROT

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

Logical Object: EQPT

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the protect ONS 15454 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 and the reporting traffic card, or the TCC2 and the backplane.


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



Caution Software update on a standby TCC2 can take up to 30 minutes.


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

Clear the CTNEQPT-PBPROT Alarm


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

Step 2 If not all cards show the alarm, perform a CTC reset on the standby XC10G card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Typical Traffic 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. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

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 4 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the standby OC-192 card.

Step 5 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 6 If the reporting traffic card is the active card in the protection group, complete the "Initiate a 1:1 Card Switch Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.

Step 7 Complete the "Reset a Traffic Card in CTC" procedure on the reporting card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

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

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

Step 10 Complete the "Initiate a 1:1 Card Switch Command" procedure to switch traffic back.

Step 11 If the alarm does not clear, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" procedure for commonly used procedures.


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


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


2.8.65  CTNEQPT-PBWORK

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

Logical Object: EQPT

The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the ONS 15454 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 and the reporting traffic card, or the TCC2 and the backplane.


Note This alarm automatically raises and clears when the ONS 15454 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 on the lower-right edge of the shelf assembly.

Clear the CTNEQPT-PBWORK Alarm


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

Step 2 If not all traffic cards show the alarm, complete the "Side Switch the Active and Standby XC10G Cross-Connect Cards" procedure for the active XC10G cross-connect card.

Step 3 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

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

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

Step 6 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Initiate a 1:1 Card Switch Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.

Step 7 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

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

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

Step 10 If you switched traffic, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

Step 11 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the OC-192 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 12 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting traffic card.

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


2.8.66  DATAFLT

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

Logical Object: NE

The Software Data Integrity Fault 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 an Active TCC2 and Activate the Standby Card" procedure.

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


2.8.67  DBOSYNC

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

Logical Object: NE

The standby Database Out Of Synchronization 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. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for instructions.

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


2.8.68  DS3-MISM

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

Logical Object: DS3

The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on a signal transiting the ONS 15454 DS3XM-6 or DS3XM-12 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type for a DS3XM-6 card is set to C Bit and the incoming signal 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 or DS3XM-12 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 (C bit or M13).

Step 4 If the Line Type field does not match the expected incoming signal, select the correct Line Type in the drop-down list.

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


2.8.69  DSP-COMM-FAIL

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

Logical Object: TRUNK

The digital signal processor (DSP) Communication Failure alarm indicates that there is a communications failure between an MXP or TXP 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 or TXP 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 or TXP card raises the "DSP-FAIL" alarm on page 2-66, and could affect traffic.


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


2.8.70  DSP-FAIL

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

Logical Object: TRUNK

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

Clear the DSP-FAIL Alarm


Step 1 Complete the "Physically Replace a Traffic Card" procedure for the reporting MXP or TXP 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.71  DUP-IPADDR

Default Severity: 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.

Clear the DUP-IPADDR 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.72  DUP-NODENAME

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

Logical Object: NE

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

Clear the DUP-NODENAME Alarm


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

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

Step 3 Click Apply.

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


2.8.73  EHIBATVG

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

Logical Object: PWR

The Extreme High Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage exceeds the extreme high power threshold. This threshold, with a default value of -56.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the Cisco ONS 15454 DWDM Installation and Operations 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.74  ELWBATVG

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

Logical Object: PWR

The Extreme Low Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage falls below the extreme low power threshold. This threshold, with a default value of -40.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains over the threshold for 120 seconds. (For information about changing this threshold, refer to the Cisco ONS 15454 DWDM Installation and Operations 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.75  ENCAP-MISMATCH-P

Default Severity: Major (MJ), Service-Affecting

Logical Object: STS-TRM

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

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

The received C2 byte is not a PDI value.

The received C2 does not match the expected C2.

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

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

(This is in contrast to PLM-P, which must meet all five criteria.) For an ENCAP-MISMATCH-P to be raised, there is a mismatch between the received and expected C2 byte, with either the expected byte or received byte value being 0x01.

An example of a situation that would raise ENCAP-MISMATCH-P is if a circuit created between two ML-Series cards has generic framing procedure (GFP) framing provisioned on one end and high-level data link control (HDLC) framing with LEX encapsulation provisioned on the other. The GFP framing card transmits and expects a C2 byte of 0x1B, while the HDLC framing card will transmits and expects a C2 byte of 0x01.

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

Mode (HDLC, GFP-F)

Encapsulation (LEX, HDLC, PPP)

CRC size (16 or 32)

Scrambling state (on or off)

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


Note By default, an ENCAP-MISMATCH-P alarm will cause an ML-Series card data link to go down. This behavior can be modified using the command line interface (CLI) command no pos trigger defect encap.



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


Clear the ENCAP-MISMATCH-P Alarm


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

a. In node view, double-click the receive ML-Series card to display the card view.

b. Click the Provisioning > Card tabs.

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

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

a. In node view, double-click the transmit ML-Series card to display the card view.

b. Click the Provisioning > Card tabs.

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

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

Encapsulation

CRC size

Scrambling state

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

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


2.8.76  EOC

Default Severity: 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 ONS 15454 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS-NR) 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 on the lower-right edge of the shelf assembly.


Note If a circuit shows a partial 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-138 is also reported, complete the "Clear the LOS (DS1) Alarm" procedure.

Step 2 If the "SF-L" condition on page 2-206 is reported, complete the "Clear the SF-L Condition" procedure.

Step 3 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 SDCC traffic. If they are not, correct them.

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

Step 4 When the LEDs on the OC-N cards are correctly illuminated, complete the "Verify or Create Node SDCC 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 ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

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

c. Click the Provisioning > Line tabs.

d. Verify that the admin state column lists the port as IS.

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and click IS in the drop-down list. 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 "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71 for non-DWDM card levels and refer to the Cisco ONS 15454 DWDM Installation and Operations Guide 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 Cisco ONS 15454 DWDM Installation and Operations Guide.

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

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

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

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

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

a. Click the Provisioning > Comm Channels > SDCC tabs.

b. Highlight the problematic DCC termination.

c. Click Delete.

d. Click Yes in the Confirmation Dialog box.

Step 12 Recreate the SDCC termination. Refer to the Cisco ONS 15454 DWDM Installation and Operations 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 Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.


2.8.77  EOC-L

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

Logical Objects: CLIENT, 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-NR) 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 on the lower-right edge of the shelf assembly.


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


2.8.78  EQPT

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

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

An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card. If the EQPT alarm occurs with a BKUPMEMP alarm, refer to the "BKUPMEMP" section. The BKUPMEMP procedure also clears the EQPT alarm.

This alarm is also invoked if a diagnostic circuit detects a card application-specific integrated circuit (ASIC) failure. In this case, if the card is part of a protection group, an APS switch occurs. If the card is the protect card, switching is inhibited and a PROTNA alarm is raised. The standby path generates a path-type alarm.


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

Clear the EQPT Alarm


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

Step 2 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Typical Traffic 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. Verify the LED status. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

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

Step 5 If the physical reseat of the card fails to clear the alarm, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.79  EQPT-MISS

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

Logical Object: FAN

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

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

Clear the EQPT-MISS Alarm


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

Step 2 If the fan-tray assembly is present, complete the "Replace the Alarm Interface Panel" procedure.

Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for installation instructions.

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

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


2.8.80  ERFI-P-CONN

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the "UNEQ-P" alarm on page 2-229 and the "TIM-P" alarm on page 2-224 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.81  ERFI-P-PAYLD

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication Path Payload condition is triggered on DS-1, DS-3, or VT circuits when the "PLM-P" alarm on page 2-188 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.82  ERFI-P-SRVR

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication Path Server condition is triggered on DS-1, DS-3, or VT circuits when the "AIS-P" alarm on page 2-23 or the "LOP-P" alarm on page 2-134 is raised on the transmission signal.

Clear the ERFI-P-SRVR Condition


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

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


2.8.83  ERROR-CONFIG

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

Logical Object: EQPT

The Error in Startup Configuration alarm applies to the ML-Series Ethernet 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.


Note For information about provisioning the ML-Series Ethernet cards from the Cisco IOS interface, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.


Clear the 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 Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.

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 a Cisco 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 Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.84  ETH-LINKLOSS

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

Logical Object: NE

The Rear Panel Ethernet Link Removed 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.85  E-W-MISMATCH

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

Logical Object: OCN

A Procedural Error Misconnect East/West Direction alarm occurs during BLSR setup, or when nodes in a ring have slots misconnected. An east slot can be misconnected to another east slot, or a west slot can be 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 (IS-NR) 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.

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


Clear the E-W-MISMATCH Alarm in CTC


Step 1 Log into the misconnected node. A misconnected node has both ring fibers connecting it to its neighbor nodes misconnected.

Step 2 Click the Maintenance > BLSR tabs.

Step 3 From the row of information for the fiber span, complete the "Identify a BLSR Ring Name or Node ID Number" procedure to identify the node ID, ring name, and the slot and port in the East Line column and West Line column. Record the above information.

Step 4 Click View > Go to Network View.

Step 5 Delete and recreate the BLSR:

a. Click the Provisioning > BLSR tabs.

b. Click the row from Step 3 to select it and click Delete.

c. Click Create.

d. Fill in the ring name and node ID from the information collected in Step 3.

e. Click Finish.

Step 6 Display node view and click the Maintenance > BLSR tabs.

Step 7 Change the West Line field to the slot you recorded for the East Line in Step 3.

Step 8 Change the East Line field to the slot you recorded for the West Line in Step 3.

Step 9 Click OK.

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


2.8.86  EXCCOL

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

Logical Object: EQPT

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

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

Clear the EXCCOL Alarm


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

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

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


2.8.87  EXERCISE-RING-FAIL

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

Logical Object: OCN

The Exercise Ring command issues ring protection switching of the requested channel without completing the actual bridge and switch. The EXERCISE-RING-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.


Note If the exercise command gets rejected due to the existence of a higher-priority condition in the ring, EXERCISE-RING-FAIL is not reported.


Clear the EXERCISE-RING-FAIL Condition


Step 1 Look for and clear, if present, the "LOF (OCN)" alarm on page 2-132, the "LOS (OCN)" alarm on page 2-142, or BLSR alarms.

Step 2 Reissue the Exercise Ring command:

a. Click the Maintenance > BLSR tabs.

b. Click the row of the affected ring under the West Switch column.

c. Select Exercise Ring in the drop-down list.

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


2.8.88  EXERCISE-SPAN-FAIL

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

Logical Object: OCN

The Exercise Span command issues span switching of the requested channel without completing the actual bridge and switch. The EXERCISE-SPAN-FAIL alarm is raised if the command was issued and accepted but the exercise did not take place.


Note If the exercise command gets rejected due to the existence of a higher-priority condition in the span or ring, EXERCISE-SPAN-FAIL is not reported.


Clear the EXERCISE-SPAN-FAIL Condition


Step 1 Look for and clear, if present, the "LOF (OCN)" alarm on page 2-132, the "LOS (OCN)" alarm on page 2-142, or a BLSR alarm.

Step 2 Reissue the Exercise Span command:

a. Click the Maintenance > BLSR tabs.

b. Determine whether the card you would like to exercise is the west card or the east card.

c. Click the row of the affected span under the East Switch or West Switch column.

d. Select Exercise Span in the drop-down list.

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


2.8.89  EXT

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

Logical Object: ENVALRM

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

Clear the EXT Alarm


Step 1 In node view double-click the AIC or AIC-I card to display the card view.

Step 2 Double-click the AIC or AIC-I card Maintenance > External Alarms tab.

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

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


2.8.90  EXTRA-TRAF-PREEMPT

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

Logical Object: OCN

An Extra Traffic Preempted alarm occurs on OC-N cards in two-fiber and four-fiber BLSRs when low-priority traffic directed to the protect system has been preempted by a working system protection switch.

Clear the EXTRA-TRAF-PREEMPT Alarm


Step 1 Verify that the protection switch has occurred by checking the Conditions tab.

Step 2 If a ring switch has occurred, clear the ring switch on the working system by following the appropriate alarm in this chapter. For more information about protection switches, refer to the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm occurred on a four-fiber BLSR and the span switch occurred on this OC-N, clear the span switch on the working system.

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


2.8.91  FAILTOSW

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

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

The Failure to Switch to Protection condition occurs when a working electrical card cannot switch to the protect card in a protection group because another working electrical card with a higher-priority alarm has switched to the protect card.

Clear the FAILTOSW Condition


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


Note A higher-priority alarm is an alarm raised on the working DS-N card using the 1:N card protection group. The working DS-N card is reporting an alarm but not reporting a FAILTOSW condition.


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

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


Note 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.



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


2.8.92  FAILTOSW-PATH

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

Logical Objects: STSMON, VT-MON

The Fail to Switch to Protection Path condition occurs when the working circuit does not switch to the protection circuit on a path protection. Common causes of the FAILTOSW-PATH alarm include a missing or defective protection port, a lockout set on one of the path protection nodes, or path level alarms that would cause a path protection switch to fail including the "AIS-P" condition on page 2-23, the "LOP-P" alarm on page 2-134, the "SD-P" condition on page 2-203, the "SF-P" condition on page 2-206, and the "UNEQ-P" alarm on page 2-229.

The "LOF (OCN)" alarm on page 2-132, the "LOS (OCN)" alarm on page 2-142, the "SD-L" condition on page 2-203, or the "SF-L" condition on page 2-206 can also occur on the failed path.


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

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration


Step 1 Look up and clear the higher-priority alarm. Clearing this condition frees the standby card and clears the FAILTOSW-PATH condition. If the "AIS-P" condition on page 2-23, the "LOP-P" alarm on page 2-134, the "UNEQ-P" alarm on page 2-229, the "SF-P" condition on page 2-206, the "SD-P" condition on page 2-203, the "LOF (OCN)" alarm on page 2-132, the "LOS (OCN)" alarm on page 2-142, the "SD-L" condition on page 2-203, or the "SF-L" condition on page 2-206 are also occurring on the reporting port, complete the applicable alarm clearing procedure.


Note A higher-priority alarm is an alarm raised on the working DS-N card using the 1:N card protection group. The working DS-N card is reporting an alarm but not reporting a FAILTOSW condition.


Step 2 If the alarm does not clear, replace the active OC-N card that is reporting the higher-priority alarm. Complete the "Physically Replace a Traffic Card" procedure. Replacing the active OC-N card that is reporting the higher-priority alarm allows traffic to revert to the active slot. Reverting frees the standby card, which can then take over traffic from the card reporting the lower-priority alarm and the FAILTOSW-PATH condition.


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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.93  FAILTOSWR

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

Logical Object: OCN

The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems.

FAILTOSWR clears when one of the following situations occurs:

A physical card pull of the active TCC2 card (done under TAC supervision).

A node power cycle.

A higher-priority event such as an external switch command.

The next ring switch succeeds.

The cause of the APS switch (such as the "SD (DS1, DS3)" condition on page 2-201 or the "SF (DS1, DS3)" condition on page 2-205) clears.


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-NR) 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 FAILTOSWR Condition in a BLSR Configuration


Step 1 Perform the EXERCISE RING command on the reporting card:

a. Click the Maintenance > BLSR tabs.

b. Click the row of the affected ring under the West Switch column.

c. Select Exercise Ring in the drop-down list.

Step 2 If the condition does not clear, from the view menu, choose Go to Network View.

Step 3 Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.

Step 4 If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node.

Step 5 Click the Maintenance > BLSR tabs.

Step 6 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards and ports and port are active and in service:

a. Verify the LED status: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

b. Double-click the card in CTC to display the card view.

c. Click the Provisioning > Line tabs.

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

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 7 If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.

Step 8 If fiber continuity to the ports is okay, use an optical test set to verify that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.


Caution Using an optical test set disrupts service on the optical card. It could be necessary to manually switch traffic carrying circuits over to a protection path.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the OC-N card receiver specifications. The "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71 lists these specifications.

Step 11 Repeat Steps 7 through 10 for any other ports on the card.

Step 12 If the optical power level for all OC-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby OC-N 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


Step 13 If the condition does not clear after you replace the BLSR cards on the node one by one, repeat
Steps 4 through 12 for each of the nodes in the ring.

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


2.8.94  FAILTOSWS

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

Logical Object: OCN

The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber BLSR, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS condition does not appear. If the ring switch does not occur, the FAILTOSWS condition appears. FAILTOSWS clears when one of the following situations occurs:

A physical card pull of the active TCC2 done under TAC supervision.

A node power cycle.

A higher-priority event such as an external switch command occurs.

The next span switch succeeds.

The cause of the APS switch (such as the "SD (DS1, DS3)" condition on page 2-201 or the "SF (DS1, DS3)" condition on page 2-205) clears.

Clear the FAILTOSWS Condition


Step 1 Perform the EXERCISE SPAN command on the reporting card:

a. Click the Maintenance > BLSR tabs.

b. Determine whether the card you would like to exercise is the west card or the east card.

c. Click the row of the affected span under the East Switch or West Switch column.

d. Select Exercise Span in the drop-down list.

Step 2 If the condition does not clear, from the view menu, choose Go to Network View.

Step 3 Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.

Step 4 If clearing other alarms does not clear the FAILTOSWS condition, log into the near-end node.

Step 5 Click the Maintenance > BLSR tabs.

Step 6 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards are active and in service:

a. Verify the LED status: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.

b. To determine whether the OC-N 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 Admin State column lists the port as IS.

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 7 If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.

Step 8 If fiber continuity to the ports is okay, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.


Caution Using an optical test set disrupts service on the optical card. It could be necessary to manually switch traffic carrying circuits over to a protection path.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the OC-N card receiver specifications. The "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71 lists these specifications.

Step 11 Repeat Steps 7 through 10 for any other ports on the card.

Step 12 If the optical power level for all OC-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby OC-N 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


Step 13 If the condition does not clear after you replace the BLSR cards on the node one by one, follow
Steps 4 through 12 for each of the nodes in the ring.

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


2.8.95  FAN

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

Logical Object: FAN

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

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


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

Clear the FAN Alarm


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

Step 2 If the filter is clean, complete the "Replace the Alarm Interface Panel" procedure.


Note The fan should run immediately when correctly inserted.


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

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


2.8.96  FC-NO-CREDITS

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

Logical Object: FCMR

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

FC-NO-CREDITS is raised only if transmission is completely prevented. (If traffic is slowed but still passing, this alarm is not raised.) The alarm is raised in conjunction with the GFP-NO-BUFFERS alarm. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm might be raised at the upstream remote FC_MR-4 data port.

Clear the FC-NO-CREDITS Alarm


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

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

a. Double-click the FC_MR-4 card.

b. Place the port out of service (OOS,MT).

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

d. Uncheck the Autodetect Credits column check box.

e. Click Apply.

f. Place the port back in service (IS).

Step 3 Program the Credits Available value based on the buffers available on the connected equipment:


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


a. Double-click the FC_MR-4 card.

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

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

d. Click Apply.

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


2.8.97  FE-AIS

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

Logical Object: DS3

The Far-End AIS condition occurs when an AIS has occurred at the far-end node. FE-AIS usually occurs in conjunction with a downstream LOS alarm (see the "LOS (OCN)" alarm on page 2-142).

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 AIS condition 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 FE-AIS Condition


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

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


2.8.98  FEC-MISM

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

Logical Object: TRUNK

The Forward Error Correction (FEC) Mismatch alarm occurs if one end of a span using MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, or TXPP_MR_2.5G cards is configured to use FEC and the other is not. FEC-MISM is related to ITU-T G.709 and is only raised against a trunk port.

Clear the FEC-MISM Alarm


Step 1 Double-click the MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G,TXP_MR_10E or TXPP_MR_2.5G card.

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

Step 3 Check the FEC column check box.

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

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


2.8.99  FE-DS1-MULTLOS

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

Logical Object: DS3

The Far-End Multiple DS-1 LOS Detected condition occurs when multiple DS-1 signals are lost on a far-end DS-1 card. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-MULTLOS condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS1-MULTLOS Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an ONS 15454 FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.100  FE-DS1-NSA

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

Logical Object: DS3

The Far End DS-1 Equipment Failure Non-Service Affecting condition occurs when a far-end DS-1 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-NSA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS1-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an alarm from a card in an ONS 15454 Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.101  FE-DS1-SA

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

Logical Object: DS3

The Far End DS-1 Equipment Failure Service Affecting condition occurs when there is a far-end equipment failure on a DS-1 card that affects service because traffic is unable to switch to the protect port.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-SA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS1-SA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.102  FE-DS1-SNGLLOS

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

Logical Object: DS3

The Far-End Single DS-1 LOS condition occurs when a single DS-1 signal is lost on far-end DS-1 equipment. Signal loss also causes the "LOS (OCN)" alarm on page 2-142. The prefix FE in an alarm or condition means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-SNGLLOS alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS1-SNGLLOS Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.103  FE-DS3-NSA

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

Logical Object: DS3

The Far End DS-3 Equipment Failure Non-Service Affecting condition occurs when a far-end ONS 15454 DS-3 equipment failure occurs in C-bit framing mode, but does not affect service because the port is protected and traffic is able to switch to the protect port.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting FE-DS3-NSA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS3-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.104  FE-DS3-SA

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

Logical Object: DS3

The Far End DS-3 Equipment Failure Service Affecting condition occurs when there is a far-end equipment failure on an ONS 15454 DS-3 card in C-bit framing mode that affects service because traffic is unable to switch to the protect port.

The prefix FE in an alarm or condition means the main alarm is occurring at the far-end node and not at the node reporting the FE condition. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-DS3-SA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an alarm from a card in Slot 12 of Node 1 could link to an alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.105  FE-EQPT-NSA

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

Logical Object: DS3

The Far End Common Equipment Failure condition occurs when a non-service-affecting equipment failure is detected on far-end DS-3 equipment. The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-EQPT-NSA alarm. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.


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

Clear the FE-EQPT-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.8.106  FE-FRCDWKSWBK-SPAN

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

Logical Objects: EC1-12, OCN

The Far End Forced Switch Back to Working—Span condition is raised on a far-end 1+1 protection port when it is Force switched to the working port.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWBK-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the primary alarm clears.

Clear the FE-FRCDWKSWBK-SPAN Condition


Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure for the far-end port.

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


2.8.107  FE-FRCDWKSWPR-RING

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

Logical Object: OCN

The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a BLSR ring is forced from working to protect using the FORCE RING command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the primary alarm clears.

Clear the FE-FRCDWKSWPR-RING Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-RING condition does not also clear, complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.108  FE-FRCDWKSWPR-SPAN

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

Logical Object: OCN

The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber BLSR is forced from working to protect using the FORCE SPAN command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-FRCDWKSWPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-SPAN condition does not also clear, complete the "Clear a BLSR External Switching Command" procedure for instructions.

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


2.8.109  FE-IDLE

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

Logical Object: DS3

The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal in C-bit framing mode.

The prefix FE in an alarm or condition occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-IDLE condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. Both alarms clear when the main alarm clears.

Clear the FE-IDLE Condition


Step 1 To troubleshoot the FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm by clearing the protection switch. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.

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


2.8.110  FE-LOCKOUTOFPR-SPAN

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

Logical Object: OCN

The Far-End Lock Out of Protection Span condition occurs when a BSLR span is locked out of the protection system from a far-end node using the Lockout Protect Span command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-LOCKOUTOFPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-LOCKOUTOFPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Ensure there is no lockout set. Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.111  FE-LOF

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

Logical Object: DS3

The Far End LOF condition occurs when a far-end node reports the "LOF (DS3)" alarm on page 2-131 in C-bit framing mode.

The prefix FE in an alarm or condition occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-LOF condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-LOF Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear the LOF (DS1) Alarm" procedure. It also applies to FE-LOF.

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


2.8.112  FE-LOS

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

Logical Object: DS3

The Far End LOS condition occurs in C-bit framing mode when a far-end node reports the "LOS (DS3)" alarm on page 2-139.

The prefix FE occurs when the main alarm is occurring at the far-end node, and not at the node reporting the FE-LOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-LOS Condition


Step 1 To troubleshoot the FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear the LOS (DS1) Alarm" procedure.

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


2.8.113  FE-MANWKSWBK-SPAN

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

Logical Objects: EC1-12, OCN

The Far End Manual Switch Back to Working—Span condition occurs when a far-end path protection span is Manual switched back to working.

The prefix FE occurs when the main alarm is occurring at the far-end node, and not at the node reporting the FE-LOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-MANWKSWBK-SPAN Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.114  FE-MANWKSWPR-RING

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

Logical Object: OCN

The Far End Ring Manual Switch of Working Facility to Protect condition occurs when a BLSR working ring is switched from working to protect at a far-end node using the MANUAL RING command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-MANWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-MANWKSWPR-RING Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.115  FE-MANWKSWPR-SPAN

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

Logical Object: OCN

The Far-End Span Manual Switch Working Facility to Protect condition occurs when a four-fiber BLSR span is switched from working to protect at the far-end node using the Manual to Protect command.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-MANWKSWPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear a BLSR External Switching Command" alarm on page 2-247.

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


2.8.116  FEPRLF

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

Logical Object: OCN

The Far End Protection Line Failure alarm occurs when an APS channel "SF (DS1, DS3)" condition on page 2-205 occurs on the protect card coming into the node.


Note The FEPRLF only alarm occurs when bidirectional protection is used on optical cards in a 1+1 configuration or four-fiber BLSR configuration.


Clear the FEPRLF Alarm on a Four-Fiber BLSR


Step 1 To troubleshoot the FE alarm, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter in this chapter for instructions.

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


2.8.117  FIBERTEMP-DEG

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

Logical Object: AOTS

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

Clear the FIBERTEMP-DEG Alarm


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

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


2.8.118  FORCED-REQ

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

Logical Objects: EQPT, STSMON, VT-MON

The Force Switch Request condition occurs when you enter the Force command on a port or span to force traffic from a working port or working span to a protection port or protection span (or vice versa). You do not need to clear the condition if you want the Force switch to remain.

Clear the FORCED-REQ Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

Step 2 If the condition is raised against a card, complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

Step 3 If it is raised against a span, complete the "Clear Path Protection Span External Switching Command" procedure.

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


2.8.119  FORCED-REQ-RING

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

Logical Object: OCN

The Force Switch Request Ring condition applies to optical trunk cards when the FORCE RING command is applied to two-fiber and four-fiber BLSRs to move traffic from working to protect.

Clear the FORCED-REQ-RING Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.120  FORCED-REQ-SPAN

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

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

The Force Switch Request Span condition applies to optical trunk cards in two-fiber or four-fiber BLSRs when the FORCE SPAN command is applied to a BLSR to force traffic from working to protect or from protect to working.

Clear the FORCED-REQ-SPAN Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.121  FRCDSWTOINT

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

Logical Object: NE-SREF

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


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


2.8.122  FRCDSWTOPRI

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

Logical Objects: EXT-SREF, NE-SREF

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


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


2.8.123  FRCDSWTOSEC

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

Logical Objects: EXT-SREF, NE-SREF

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


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


2.8.124  FRCDSWTOTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

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


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


2.8.125  FRNGSYNC

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

Logical Object: NE-SREF

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


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


Clear the FRNGSYNC Alarm


Step 1 If the ONS 15454 is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for more information about timing.

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

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


2.8.126  FSTSYNC

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

Logical Object: NE-SREF

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

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


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


2.8.127  FULLPASSTHR-BI

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

Logical Object: OCN

The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are active and carrying traffic and there is a change in the receive K byte from No Request.

Clear the FULLPASSTHR-BI Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.128  GAIN-HDEG

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

Logical Object: AOTS

The Gain High Degrade alarm is raised on OPT-BST and OPT-PRE amplifier cards when the gain reaches the high degrade threshold and is prevented from reaching the setpoint due to an internal failure. The card should be replaced at the first opportunity.


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


Clear the GAIN-HDEG Alarm


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 3 Verify that the received power (opwrMin) is within the expected range shown in Cisco MetroPlanner. To check the level in CTC:

a. Double-click the amplifier card to display the card view.

b. Display the optical thresholds by clicking the OPT-BST or OPT-PRE Provisioning > Opt. Ampli. Line > Optics Thresholds tab.

Step 4 If the power value is outside the expected range, verify that all impacted optical signal sources are in IS-NR service state and that their outputs are within expected range. Optical signal sources include the trunk port of a TXP or MXP card, or an ITU-T line card.

Step 5 If the signal source is OOS,DSBLD admin state, put it in IS state. This will create the IS-NR service state.

Step 6 If the service state is IS-NR but the output power is outside of specifications, complete the "Clear the LOS-P (OCH, OMS, OTS) Alarm" procedure.

Step 7 If the signal source is IS and the power is within the expected range, go back to the unit reporting the alarm and clean the fiber connected to amplifier's COM-RX port according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.


Note Unplugging fiber from the COM-RX port can cause a traffic hit. To avoid this, perform a traffic switch if possible using the procedures outlined in the "Protection Switching, Lock Initiation, and Clearing" section. For more in-depth information about protection switches, refer to the Cisco ONS 15454 Reference Manual.


Step 8 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem. To do this, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for acceptance testing procedures that can be used for troubleshooting purposes.

Step 9 If no other alarms exist that could be the source of the GAIN-HDEG, or if clearing an alarm did not clear the GAIN-HDEG, place all of the card ports in OOS,DSBLD admin state.

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


Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform a traffic switch if possible.



Note When you replace a card with an identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS,AINS admin state.


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


2.8.129  GAIN-HFAIL

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

Logical Object: AOTS

The Gain High Fail alarm is raised on OPT-BST and OPT-PRE amplifier cards when the gain crosses the high failure point threshold. The card will need to be replaced.


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


Clear the GAIN-HFAIL Alarm


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

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


2.8.130  GAIN-LDEG

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

Logical Object: AOTS

The Gain Low Degrade alarm is raised on OPT-BST and OPT-PRE amplifier cards when the gain has crossed the low degrade threshold and is prevented from reaching the setpoint due to an internal failure. The card should be replaced at the first opportunity.


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


Clear the GAIN-LDEG Alarm


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

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


2.8.131  GAIN-LFAIL

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

Logical Object: AOTS

The Gain Low Fail alarm is raised on OPT-BST and OPT-PRE amplifier cards when the gain crosses the low failure point threshold. The card will need to be replaced.


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


Clear the GAIN-LFAIL Alarm


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

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


2.8.132  GCC-EOC

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

Logical Object: TRUNK

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

Clear the GCC-EOC Alarm


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

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


2.8.133  GE-OOSYNC

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

Logical Objects: FC, GE, ISC, TRUNK

The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when the Gigabit Ethernet signal is out of synchronization and is very similar to the SONET LOS alarm. This alarm can occur when you try to input a SONET signal to the TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card. A signal is present, so there is no CARLOSS alarm, but it is not correctly formatted for the card and so it raises the GE-OOSYNC alarm.

Clear the GE-OOSYNC Alarm


Step 1 Ensure that the incoming signal is provisioned with the correct physical-layer protocol.

Step 2 Ensure that the line is provisioned with the correct line speed (10 Gbps).

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


2.8.134  GFP-CSF

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

Logical Objects: GFP-FAC, ML1000, ML100T, ML2

The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote service-affecting alarm causes invalid data transmission. The alarm is raised locally on FC_MR-4, ML100T, ML1000, MXP_MR_25G, MXPP_MR_25G GFP data ports and does not indicate that a service-affecting failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm is affecting a remote data port's transmission capability.


Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.


Clear the GFP-CSF Alarm


Step 1 Clear the service-affecting alarm at the remote data port.

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


2.8.135  GFP-DE-MISMATCH

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

Logical Objects: GFP-FAC, ML1000, ML100T

The GFP Fibre Channel Distance Extension Mismatch alarm indicates that a port configured for Distance Extension is connected to a port that is not operating in Cisco's proprietary Distance Extension mode. It is raised on Fibre Channel and FICON card GFP ports supporting distance extension. The alarm occurs when distance extension is enabled on one side of the transport but not on the other. To clear, distance extension must be enabled on both ports connected by a circuit.

Clear the GFP-DE-MISMATCH Alarm


Step 1 Ensure that the data extension protocol is configured correctly on both sides:

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

b. Place the port in the OOS,MT state.

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

d. Check the check box in the Enable Distance Extension column.

e. Click Apply.

f. Place the port back IS-NR admin state

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


2.8.136  GFP-EX-MISMATCH

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

Logical Objects: GFP-FAC, ML1000, ML100T

The GFP Extension Header Mismatch alarm is raised on Fibre Channel/FICON cards when it receives frames with an extension header that is not null. The alarm occurs when a provisioning error causes all GFP frames to be dropped for 2.5 seconds.

The user needs to make sure that both end ports are sending a null extension header for a GFP frame. The FC_MR-4 card always sends a null extension header, so if the equipment is connected to other equipment vendors, those need to be provisioned appropriately.

Clear the GFP-EX-MISMATCH Alarm


Step 1 Ensure that the vendor equipment is provisioned to send a null extension header in order to interoperate with the FC_MR-4 card. (The FC_MR-4 card always sends a null extension header.)

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


2.8.137  GFP-LFD

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

Logical Objects: GFP-FAC, ML1000, ML100T, ML2

The GFP Loss of Frame Delineation alarm applies to Fibre Channel/FICON GFP ports and occurs if there is a bad SONET connection, if SONET path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. The loss causes traffic stoppage.


Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.


Clear the GFP-LFD Alarm


Step 1 Look for and clear any associated SONET path errors such as LOS or AIS-L originating at the transmit node.

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


2.8.138  GFP-NO-BUFFERS

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

Logical Objects: GFP-FAC, ML1000, ML100T

The GFP Fibre Channel Distance Extension Buffer Starvation alarm is raised on Fibre Channel/FICON card ports supporting GFP and the distance extension protocol when the GFP transmitter cannot send GFP frames due to lack of remote GFP receiver buffers. This occurs when the remote GFP-T receiver experiences congestion and is unable to send frames over the Fibre Channel/FICON link.

This alarm might be raised in conjunction with the FC-NO-CREDITS alarm. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm might be raised at the upstream remote FC_MR-4 data port.

Clear the GFP-NO-BUFFERS Alarm


Step 1 Complete the "Clear the FC-NO-CREDITS Alarm" procedure.

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


2.8.139  GFP-UP-MISMATCH

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

Logical Objects: GFP-FAC, ML1000, ML100T

The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type. For example, the local port media type could be set to Fibre Channel 1 Gig or Fibre Channel 2 Gig and the remote port media type could be set to FICON 1 Gig or FICON 2 Gig.

Clear the GFP-UP-MISMATCH Alarm


Step 1 Ensure that the transmit port and receive port are provisioned the same way for distance extension:

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

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

c. Check the check box in the Enable Distance Extension column.

d. Click Apply.

Step 2 Ensure that both ports are set for the correct media type. For each port, complete the following:

a. Double-click the card to display the card view (if you are not already in card view).

b. Click the Provisioning > Port> General tabs.

c. Choose the correct media type (Fibre Channel 1 Gbps, Fibre Channel 2 Gbps, FICON 1 Gbps, or FICON 2 Gbps) from the drop-down list.

d. Click Apply.

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


2.8.140  HELLO

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

Logical ObjectS: EC1-12, OCN

The Open Shortest Path First (OSPF) Hello alarm is raised when the two end nodes cannot bring an OSPF neighbor up to the full state. Typically, this problem is caused by an area ID mismatch, and/or an OSPF HELLO packet loss over the DCC.

Clear the HELLO Alarm


Step 1 Ensure that the area ID is correct on the missing neighbor:

a. In node view, click the Provisioning > Network > OSPF tabs.

b. Ensure that the IP address in the Area ID column matches the other nodes.

c. If the address does not match, click the incorrect cell and correct it.

d. Click Apply.

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


2.8.141  HIBATVG

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

Logical Object: PWR

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

Clear the HIBATVG 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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.142  HI-CCVOLT

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

Logical Object: BITS

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

Clear the HI-CCVOLT Condition


Step 1 Lower the source voltage to the clock.

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

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


2.8.143  HI-LASERBIAS

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

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

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

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

Clear the HI-LASERBIAS Alarm


Step 1 Complete the "Clear the LASEREOL Alarm" procedure. Replacement is not urgent and can be scheduled during a maintenance window.


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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.144  HI-LASERTEMP

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

Logical Objects: EC1-12, OCN, PPM

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

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The "LOS (OCN)" alarm on page 2-142 is raised at the far-end node and the "DSP-FAIL" alarm on page 2-66 is raised at the near end. To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Clear the HI-LASERTEMP Alarm


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

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

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


2.8.145  HI-RXPOWER

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

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

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

Clear the HI-RXPOWER Alarm


Step 1 Find out whether gain (the amplification power) of any amplifiers has been changed. This change also causes channel power to need adjustment.

Step 2 Find out whether channels have been dropped from the fiber. Increasing or decreasing channels can affect power. If channels have been dropped, the power levels of all channels have to be adjusted.


Note If the card is part of an amplified DWDM system, dropping channels on the fiber affects the transmission power of each channel more than it would in an unamplified system.


Step 3 At the transmit end of the errored circuit, decrease the transmit power level within safe limits.

Step 4 If neither of these problems cause the HI-RXPOWER alarm, there is a slight possibility that another wavelength is drifting on top of the alarmed signal. In this case, the receiver gets signals from two transmitters at the same time and data alarms would be present. If wavelengths are drifting, the data is garbled and receive power increases by about +3 dB.

Step 5 If the alarm does not clear, add fiber attenuators to the receive ports. Start with low-resistance attenuators and use stronger ones as needed, depending on factors such as the transmission distance, according to standard practice.

Step 6 If the alarm does not clear and no faults are present on the other port(s) of the transmit or receive card, use a known-good loopback cable to complete the "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71 and test the loopback.

Step 7 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Traffic Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.


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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.146  HITEMP

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

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

Logical Objects: EQPT, NE

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


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

Clear the HITEMP Alarm


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

Figure 2-2 Shelf LCD Panel

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

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

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

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

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


Note The fan should run immediately when correctly inserted.


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


2.8.147  HI-TXPOWER

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

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

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

Clear the HI-TXPOWER Alarm


Step 1 In node view, display the card view for the TXP_MR_E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Decrease (change toward the negative direction) the TX Power High column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.148  HLDOVRSYNC

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

Logical Object: NE-SREF

The Holdover Synchronization Mode alarm indicates a loss of the primary or secondary timing reference. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS 15454. It also usually occurs during the selection of a new node reference clock. The HLDOVRSYNC alarm indicates that the ONS 15454 has gone into holdover and is using the ONS node internal reference clock, which is a Stratum 3-level timing device. The alarm clears when primary or secondary timing is reestablished.

Clear the HLDOVRSYNC Alarm


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

FRNGSYNC

FSTSYNC

HLDOVRSYNC

LOF (BITS)

LOS (BITS)

MANSWTOINT

MANSWTOPRI

MANSWTOSEC

MANSWTOTHIRD

SWTOPRI

SWTOSEC

SWTOTHIRD

SYNC-FREQ

SYNCPRI

SYNCSEC

SYNCTHIRD

Step 2 Reestablish a primary and secondary timing source according to local site practice.

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


2.8.149  I-HITEMP

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

Logical Object: NE

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

Clear the I-HITEMP Alarm


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

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


2.8.150  IMPROPRMVL

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

Logical Objects: EQPT, PPM

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


Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot. When you delete the card, CTC will lose connection with the node view and go to network view.


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


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



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


Clear the IMPROPRMVL Alarm


Step 1 In node view, right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.


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


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


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

a. In node view, double-click the reporting card to display the card view.

b. Click the Provisioning > Line tab.

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

d. Choose OOS,MT to take the ports out of service.

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


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

Step 5 If the card is paired in a protection scheme, delete the protection group:

a. Click View > Go to Previous View to return to node view.

b. If you are already in node view, click the Provisioning > Protection tabs.

c. Click the protection group of the reporting card.

d. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning:

a. Click the ONS 15454 Provisioning > Comm Channels > SDCC tabs.

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

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

Step 7 If the card is used as a timing reference, change the timing reference:

a. Click the Provisioning > Timing tabs.

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

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

d. Click Apply.

Step 8 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.

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


2.8.151  INC-ISD

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

Logical Object: DS3

The DS-3 Idle condition indicates that the DS-3 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has an OOS-MA,MT service state. It is resolved when the OOS-MA,MT state ends.


Note INC-ISD is a condition and not an alarm. It is for information only and does not require troubleshooting.


2.8.152  INHSWPR

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

Logical Object: EQPT

The Inhibit Switch To Protect Request on Equipment condition occurs on traffic cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.

Clear the INHSWPR Condition


Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

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


2.8.153  INHSWWKG

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

Logical Object: EQPT

The Inhibit Switch To Working Request on Equipment condition occurs on traffic cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the protect system. If the card is part of a protection scheme, traffic can be switched between protect cards when the switch to working is disabled.

Clear the INHSWWKG Condition


Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch traffic back.

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


2.8.154  INTRUSION-PSWD

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

Logical Object: NE

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

Clear the INTRUSION-PSWD Condition


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

Step 2 Click the Clear security intrusion alarm button.

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


2.8.155  INVMACADR

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

Logical Object: AIP

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

Under normal circumstances, the read-only MAC address can be viewed in the Provisioning/Network tab in CTC.

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

An invalid MAC address can by caused when:

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

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

An AIP component failure causes a read error.

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

Clear the INVMACADR Alarm


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

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

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


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


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

b. Identify the active TCC2 card.

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

c. Right-click the standby TCC2 card in CTC.

d. Choose Reset Card from the shortcut menu.

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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


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

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

Step 10 If the alarm persists, complete the "Replace the Alarm Interface Panel" procedure.

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


2.8.156  IOSCFGCOPY

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

Logical Object: EQPT

The IOS Configuration Copy in Progress condition occurs on ML-Series Ethernet cards when a Cisco IOS startup configuration file is being uploaded or downloaded to or from an ML-Series card. (This condition is very similar to the "SFTWDOWN" condition on page 2-207 but it applies to ML-Series Ethernet cards rather than to the TCC2.)

The condition clears after the copy operation is complete. (If it does not complete correctly, the "NO-CONFIG" condition on page 2-171 might be raised.)


Note IOSCFGCOPY is an informational condition.



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


2.8.157  KB-PASSTHR

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

Logical Object: OCN

The K Bytes Pass Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are not active and the node is in K Byte pass-through state. It also occurs when a BLSR ring is being exercised using the Exercise Ring command.

Clear the KB-PASSTHR Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.158  KBYTE-APS-CHANNEL-FAILURE

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

Logical Object: OCN

The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For instance, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.

This alarm is also raised during checksum failure if the K1 and K2 bytes are overwritten by test equipment. It is not raised in bidirectional full pass-through or K-byte pass-through states. The alarm is overridden by AIS-P, LOF, LOS, or SF-BER alarms.

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm


Step 1 The alarm is most frequently raised due to mismatched span provisioning. In this case, reprovision one side of the span with the same parameters. To do this, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 2 If the error is not caused by misprovisioning, it is due to checksum errors within an OC-N, cross-connect, or TCC2 card. In this case, complete the "Side Switch the Active and Standby XC10G Cross-Connect Cards" procedure to allow CTC to resolve the issue.

Step 3 If third-party equipment is involved, ensure that it is configured for the same APS channel as the Cisco ONS equipment.

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


2.8.159  LAN-POL-REV

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

Logical Object: NE

The Lan Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised by the TCC+ card during software upgrade when the card detects that a connected Ethernet cable has reversed receive wire pairs. The TCC+ automatically compensates for this reversal, but LAN-POL-REV stays active.

Clear the LAN-POL-REV Condition


Step 1 Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the Cisco ONS 15454 Procedure Guide.

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


2.8.160  LASER-APR

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

Logical Object: AOTS

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


Note LASER-APR is an informational condition and does not require troubleshooting.


2.8.161  LASERBIAS-DEG

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

Logical Objects: AOTS, OTS

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

Clear the LASERBIAS-DEG Alarm


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

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


2.8.162  LASERBIAS-FAIL

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

Logical Object: AOTS

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

Clear the LASERBIAS-FAIL Alarm


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

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


2.8.163  LASEREOL

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

Logical Object: OCN

The Laser Approaching End of Life alarm applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards. It is typically accompanied by the "HI-LASERBIAS" alarm on page 2-110. It is an indicator that the laser in the card will need to be replaced. How soon the replacement must happen depends upon the HI-LASERBIAS threshold. If the threshold is set under 100 percent, the laser replacement can usually be done during a maintenance window. But if the HI-LASERBIAS threshold is set at 100 percent and is accompanied by data errors, the card must be replaced sooner.

Clear the LASEREOL Alarm


Step 1 Complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


2.8.164  LASERTEMP-DEG

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

Logical Object: AOTS

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

Clear the LASERTEMP-DEG Alarm


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

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


2.8.165  LCAS-CRC

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

Logical Objects: STSTRM, VT-TERM

The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against ML-Series Ethernet cards. It occurs when there is an equipment, path, or provisioning error on the virtual concatenation group (VCG) that causes consecutive 2.5 second CRC failures in the LCAS control word.

The condition can occur if an LCAS-enabled node (containing ML2 cards) transmitting to another LCAS-enabled node delivers faulty traffic due to an equipment or SONET path failure. Transmission errors would also be reflected in CV-P, ES-P, or SES-P performance monitoring statistics. If these errors do not exist, an equipment failure is indicated.

If LCAS is not supported on the peer node, the condition will not clear.

LCAS-CRC can also occur if the VCG source node is not LCAS-enabled, but the receiving node does have the capability enabled. Both source and destination nodes must have LCAS enabled. Otherwise, the LCAS-CRC condition will persist on the VCG.


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


Clear the LCAS-CRC Condition


Step 1 Look for and clear any associated equipment failures, such as the EQPT alarm, on the receive node or transmit node.

Step 2 Look for and clear any bit error rate alarms such as SDBER or SFBER at the transmit node.

Step 3 If no equipment or SONET path errors exist, ensure that the remote node has LCAS enabled on the circuit:

a. In node view, click the Circuit tab.

b. Choose the VCAT circuit and click Edit.

c. In the Edit Circuit window, click the General tab.

d. Verify that the Mode column says LCAS.

Step 4 If the column does not say LCAS, complete the "Delete a Circuit" procedure and recreate it in LCAS mode using the instructions in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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


2.8.166  LCAS-RX-FAIL

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Receive-Side-In Fail condition is raised against FC_MR-4 cards and ML-Series Ethernet cards with LCAS-enabled VCG or software-enabled LCAS (SW-LCAS) VCG.


Note ML1-series and FC_MR-4 cards, used in the ONS 15454, are SW-LCAS enabled.


LCAS VCGs treat failures unidirectionally, meaning that failures of the transmit or receive points occur independently of each other. The LCAS-RX-FAIL condition can occur on the receive side of an LCAS VCG member for the following reasons:

SONET path failure (a unidirectional failure as seen by the receive side).

VCAT member is set out of group at the transmit side, but is set in group at the receive side.

VCAT member does not exist at the transmit side but does exist and is in group at the receive side.

The condition can be raised during provisioning operations on LCAS VCGs but should clear when the provisioning is completed.

Software-enabled LCAS VCGs treat failure bidirectionally, meaning that both directions of a VCG member are considered failed if either transmit or receive fails. The LCAS-RX-FAIL condition is raised on these VCG members when a member receive side fails due to a SONET path failure.


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


Clear the LCAS-RX-FAIL Condition


Step 1 Check for and clear any line or path alarms.

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


2.8.167  LCAS-TX-ADD

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-Series Ethernet cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed.


Note LCAS-TX-ADD is an informational condition and does not require troubleshooting.



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


2.8.168  LCAS-TX-DNU

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Do Not Use (DNU) State condition is raised on FC_MR-4 cards and ML-Series Ethernet cards when the transmit side of an LCAS VCG member is in the DNU state. For a unidirectional failure, this condition is only raised at the source node.

The node reporting this condition will likely report an RDI-P alarm, and the remote node will likely report a path alarm such as AIS-P or UNEQ-P.


Note LCAS-TX-DNU is an informational condition and does not require troubleshooting.



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


2.8.169  LKOUTPR-S

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

Logical Object: OCN

The Lockout of Protection Span condition occurs when path protection traffic is locked out of a protect span using the Lockout of Protect command.

Clear the LKOUTPR-S Condition


Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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


2.8.170  LMP-HELLODOWN

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

Logical Object: UPC-IPCC

The Link Management Protocol (LMP) Hello Down alarm occurs when the Hello protocol, which monitors UCP control channel status, is not available for link management. The unavailability can be caused by physical layer errors (such as cabling) or by control channel misconfiguration.

Clear the LMP-HELLODOWN Alarm


Step 1 Verify that the transmit and receive cables are not crossed at each end (login site and neighbor site).

Step 2 Verify that the "LOF (OCN)" alarm on page 2-132 is not present on the source or destination nodes. If so, complete the "Clear the LOS (OCN) Alarm" procedure.

Step 3 If the alarm does not clear, complete the "Clear the CKTDOWN Alarm" procedure to verify that IPCC provisioning is valid on both ends of the user-to-network interface (UNI).

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


2.8.171  LMP-NDFAIL

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

Logical Object: UCP-IPCC

The LMP Neighbor Detection Fail alarm occurs when neighbor detection within the UCP has failed. LMP-NDFAIL can be caused by physical failure (such as cabling) between the neighbors or by control channel misconfiguration.

Clear the LMP-NDFAIL Alarm


Step 1 Complete the "Clear the LMP-HELLODOWN Alarm" procedure.

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


2.8.172  LOA

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

Logical Object: VCG

The Loss of Alignment on a VCG is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.


Note This alarm occurs only if you provision circuits outside of CTC, such as by using TL1.


Clear the LOA Alarm


Step 1 In network view, click the Circuits tab.

Step 2 Click the alarmed VCG and then click Edit.

Step 3 In the Edit Circuit dialog box, click Show Detailed Map to see the source and destination circuit slots, ports, and STSs.

Step 4 Identify whether the STS travels across different fibers. If it does, complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit using the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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


2.8.173  LOCKOUT-REQ

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

Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN, STSMON, TRUNK, VT-MON

The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an OC-N card or a lockout switch request on a path protection at the path level. A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Clear the LOCKOUT-REQ Condition


Step 1 Complete the "Clear Path Protection Span External Switching Command" procedure.

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


2.8.174  LOF (BITS)

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

Logical Object: BITS

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

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


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


Clear the LOF (BITS) Alarm


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

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

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

c. Click the Provisioning > Timing tabs to display the General Timing window.

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

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

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

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


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


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


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.175  LOF (DS1)

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

Logical Object: DS1

The DS-1 LOF alarm indicates that the receiving ONS 15454 has lost frame delineation in an incoming DS-1 data stream. If the LOF appears on theDS1N-14 card, the transmitting equipment could have its framing set to a format that differs from the receiving node.

Clear the LOF (DS1) Alarm


Step 1 Verify that the line framing and line coding match between the DS1N-14 port and the signal source:

a. In CTC, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the signal source for the card reporting the alarm. You might need to contact your network administrator for the format information.

c. Display the card view of the reporting ONS 15454 card.

d. Click the ONS 15454 Provisioning > Line tabs.

e. Verify that the line type of the reporting port matches the line type of the signal source (DS4 and DS4, unframed and unframed, or ESF and ESF). If the signal source line type does not match the reporting port, click the Line Type cell to reveal a drop-down list and choose the matching type.

f. Verify that the reporting Line Coding matches the signal source line coding (AMI and AMI or B8ZS and B8ZS). If the signal source line coding does not match the reporting port, click the Line Coding cell and choose the correct type from the drop-down list.

g. Click Apply.


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



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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.176  LOF (DS3)

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

Logical Object: DS3

The DS-3 LOF alarm indicates that the receiving ONS 15454 has lost frame delineation in the incoming DS-3 data stream. The framing of the transmitting equipment could be set to a format that differs from the receiving system. On DS3XM-6 cards, the alarm occurs only on cards with the provisionable framing format set to C bit or M13 and not on cards with the provisionable framing format is set to unframed.

Clear the LOF (DS3) Alarm


Step 1 Change the line type of the non-ONS equipment attached to the reporting card to C bit:

a. Display the card view of the reporting card.

b. Click the Provisioning > Line tabs.

c. Verify that the line type of the reporting port matches the line type of the signal source.

d. If the signal source line type does not match the reporting port, click Line Type and choose C Bit from the drop-down list.

e. Click Apply.

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


2.8.177  LOF (EC1-12)

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

Logical Object: EC1-12

The EC1-12 LOF alarm occurs when a port on the reporting EC1-12 card has an LOF condition. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.


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

Clear the LOF (EC1-12) Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If cabling continuity is okay, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 3 If the alarm does not clear, see the "1.1  Troubleshooting Non-DWDM Circuit Paths with Loopbacks" section on page 1-2 to isolate the fault causing the LOF alarm.

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


2.8.178  LOF (OCN)

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

Logical Object: OCN

The LOF alarm occurs when a port on the reporting card has an LOF condition. It can also occur on ONS 15454 MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G,TXP_MR_10E, or TXPP_MR_2.5G cards reporting LOF. The alarm indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.

When the alarm is raised on an OC-N card, it is sometimes an indication that the OC-N card expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver.


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

Clear the LOF (OCN) Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If cabling continuity is okay, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 3 If the alarm does not clear, see the "1.1  Troubleshooting Non-DWDM Circuit Paths with Loopbacks" section on page 1-2 to isolate the fault causing the LOF alarm.

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


2.8.179  LOF (TRUNK)

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

Logical Object: TRUNK

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

Clear the LOF (TRUNK) Alarm


Step 1 Complete the "Clear the LOF (OCN) Alarm" procedure.

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


2.8.180  LO-LASERTEMP

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

Logical Objects: EC1-12, OCN

The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. LO-LASERTEMP occurs when the internally measured transceiver temperature falls below the card setting by35.6 degrees F or 2 degrees C. A laser temperature change affects the transmitted wavelength. (Two degrees Celsius is equivalent to about 200 picometers in the wavelength.)

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The "LOS (OCN)" alarm on page 2-142 is raised at the far-end node and the "DSP-FAIL" alarm on page 2-66 is raised at the near end. To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM > Current PM tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Clear the LO-LASERTEMP Alarm


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

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

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


2.8.181  LOM

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

Logical Objects: STSTRM, TRUNK, VT-TERM

The Optical Transport Unit (OTU) Loss of Multiframe is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, or TXPP_MR_2.5G cards when the Multi Frame Alignment Signal (MFAS) overhead field is errored for more than five frames and persists for more than three milliseconds.

Clear the LOM Alarm


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

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


2.8.182  LOP-P

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

Logical Objects: STSMON, STSTRM

A Loss of Pointer Path alarm indicates that the SONET path pointer in the overhead has been lost. LOP occurs when valid H1/H2 pointer bytes are missing from the overhead. Receiving equipment monitors the H1/H2 pointer bytes to locate the SONET payload. An LOP-P alarm occurs when eight, nine, or ten consecutive frames do not have valid pointer values. The alarm clears when three consecutive valid pointers are received.

The LOP-P alarm can occur when the received payload does not match the provisioned payload. The alarm is caused by a circuit type mismatch on the concatenation facility. For example, if an STS-1 is sent across a circuit provisioned for STS-3c, an LOP-P alarm occurs.

For FC_MR-4 card, an LOP-P will be raised if a port is configured for a SONET signal but receives an SONET signal instead. (This information is contained in the H1 byte bits 5 and 6.)


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

Clear the LOP-P Alarm


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

Step 2 Verify the circuit size listed in the Size column. If the size is different from what is expected, such as an STS3c instead of an STS1, this will cause the alarm.

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

For instructions to use the optical test set, consult the manufacturer.

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

Step 5 Recreate the circuit for the correct size. For instructions, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

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


2.8.183  LOP-V

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

Logical Objects: VT-MON, VT-TERM

The LOP VT alarm indicates a loss of pointer at the VT level.

The LOP-V alarm can occur when the received payload does not match the provisioned payload. LOP-V is caused by a circuit size mismatch on the concatenation facility.


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

Clear the LOP-V Alarm


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

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


2.8.184  LO-RXPOWER

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

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

The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable.

Clear the LO-RXPOWER Alarm


Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits.

Step 2 Find out whether new channels have been added to the fiber. Up to 32 channels can be transmitted on the same fiber, but the number of channels affects power. If channels have been added, power levels of all channels need to be adjusted.


Note If the card is part of an amplified DWDM system, adding channels on the fiber affects the transmission power of each channel more than it would in an unamplified system.


Step 3 Find out whether gain (the amplification power) of any amplifiers has been changed. Changing amplification also causes channel power to need adjustment.

Step 4 If the alarm does not clear, remove any receive fiber attenuators or replace them with lower-resistance attenuators.

Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 6 If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility (line) loopback on a known-good port. The error readings you get will not be as precise, but you will generally know whether the fiber is faulty.

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

Step 7 If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, do a facility loopback on the transmit and receive ports with known-good loopback cable. Complete the "Create the Facility (Line) Loopback on the Source-Node MXP or TXP Port" procedure on page 1-7 and test the loopback.

Step 8 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Traffic Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.


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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.185  LOS (2R)

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

Logical Object:

The Loss of Signal for a 2R Client applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.

Clear the LOS (2R) Alarm


Step 1 Complete the "Clear the LOS (OCN) Alarm" procedure.

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


2.8.186  LOS (BITS)

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

Logical Object: BITS

The LOS (BITS) alarm indicates that the TCC2 has an LOS from the BITS timing source. The LOS (BITS-N) means the BITS clock or the connection to the BITS clock failed.


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

Clear the LOS (BITS) Alarm


Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15454 backplane to the timing source.

Step 2 If wiring is good, verify that the BITS clock is operating properly.

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


2.8.187  LOS (DS1)

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

Logical Object: DS1

A LOS (DS1) alarm for a DS-1 port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line.


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

Clear the LOS (DS1) Alarm


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

Step 2 Consult site records to determine whether the port raising the alarm has been assigned.

Step 3 If the port is not currently assigned, place the port out of service using the following steps:

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

b. For a DS1 card, click the Maintenance > Loopback tabs. For a DS-1 line on a DS3XM-6 or DS3XM-12 card, click the Maintenance > DS1 tabs.

c. Under Admin State, click OOS,DSBLD.

d. Click Apply.

Step 4 If the port is assigned, verify that the correct port is in service:

a. To confirm this physically, confirm that the LED is correctly illuminated on the physical card.

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

b. To determine this virtually, double-click the card in CTC to display the card view:

Click the Provisioning > Line tabs.

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

If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. For specific procedures to use the test set equipment, consult the manufacturer.

Step 6 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 7 If there is a valid signal, replace the electrical connector on the ONS 15454.

Step 8 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 9 Repeat Steps 1 to 8 for any other port on the card that reports the LOS.

Step 10 If no other alarms are present that could be the source of the LOS (DS-1), or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.188  LOS (DS3)

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

Logical Object: DS3

The LOS (DS3) for a DS-3 port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure or a fiber cut.


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


Note If a circuit shows a partial status 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 LOS (DS3) Alarm


Step 1 Complete the "Clear the LOS (DS1) Alarm" procedure.

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


2.8.189  LOS (EC1-12)

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

Logical Object: EC1-12

LOS on an EC1-12 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (EC1-12) means that the upstream transmitter has failed. If an EC1-12 LOS alarm is not accompanied by additional alarms, a cabling problem is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.


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


Note If a circuit shows a partial status 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 LOS (EC1-12) Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If the cabling is okay, verify that the correct port is in service:

a. Confirm that the LED is correctly lit on the physical card.

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

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

c. Click the Provisioning > Line tabs.

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

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 3 If the correct port is in service, use an optical test set to confirm that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

Step 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 5 If a valid signal exists, replace the cable connector on the ONS 15454.

Step 6 Repeat Steps 1 through 5 for any other port on the card that reports the LOS (EC1-12).

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

Step 8 If no other alarms exist that could be the source of the LOS (EC1-12), or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.


2.8.190  LOS (ESCON)

The LOS alarm for the ESCON Object is not used in this platform in this release. It is reserved for future development.

2.8.191  LOS (FUDC)

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

Logical Object: FUDC

The LOS (FUDC) alarm is raised if there is a UDC circuit created on an AIC-I UDC port but the port is not receiving signal input. The downstream node will have an AIS condition raised against the AIC-I port transmitting the UDC. FUDC refers to the 64-kb user data channel using the F1 byte.

Clear the LOS (FUDC) Alarm


Step 1 Verify cable continuity to the AIC-I UDC port.

Step 2 Verify that there is a valid input signal using a test set.

Step 3 If there is a valid signal, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 4 If the alarm does not clear, verify that the UDC is provisioned:

a. At the network view, click the Provisioning > Overhead Circuits tabs.

b. If no UDC circuit exists, create one. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

c. If a user data circuit exists (shown as User Data F1 under the Type column), check the source and destination ports. These must be located on AIC-I cards to function.

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

Step 6 If no other alarms exist that could be the source of the LOS (FUDC), or if clearing another alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


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


2.8.192  LOS (ISC)

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

Logical Object: ISC

The LOS alarm for the ISC port applies to TXP_MR_2.5G client PPMs provisioned at the ISC port rate. Troubleshooting is similar to the LOS (2R) alarm.

Clear the LOS (ISC) Alarm


Step 1 Complete the "Clear the LOS (2R) Alarm" procedure.

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


2.8.193  LOS (MSUDC)

The LOS (MSUDC) alarm is not used in this platform in this release. It is reserved for future development.

2.8.194  LOS (OCN)

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

Logical Object: OCN

An LOS alarm on an OC-N port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS alarm means the upstream transmitter has failed. If an OC-N LOS alarm is not accompanied by additional alarms, a fiber break is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.


Warning On the OCC-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-NR) 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 on the lower-right edge of the shelf assembly.


Note If a circuit shows a partial status 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 LOS (OCN) Alarm


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, verify that the correct port is in service:

a. Confirm that the LED is correctly illuminated on the physical card.

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

b. To determine whether the OC-N 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 admin state column lists the port as IS.

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 3 If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the OC-N card receiver specifications. The "1.9.3  OC-N Card Transmit and Receive Levels" section on page 1-71 lists these specifications for each OC-N card. For DWDM card levels, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 5 If the optical power level is within specifications, use an optical test set to verify that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

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

Step 7 Repeat Steps 1 to 6 for any other port on the card reporting the LOS (OC-N).

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

Step 9 If no other alarms exist that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


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


2.8.195  LOS (OTS)

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

Logical Object: OTS

The Loss of Signal for the OTS applies to the LINE-3-RX port of the OPT-BST amplifier and the LINE-2-RX port of the OSC-CSM card. It indicates that a fiber cut has occurred and no power is being received from the span. The alarm is raised when both LOS-P and LOS-O alarms occur, and demotes them.

Clear the LOS (OTS) Alarm


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 3 Verify that the received power (opwrMin value of the Line 4-1-RX port) is within the expected range shown in Cisco MetroPlanner. To check the level:

a. Double-click the amplifier card to display the card view.

b. Click the Provisioning > Opt. Ampli. Line > Optics Thresholds tabs.

c. Compare the opwrMin (dBm) column value with the MetroPlanner-generated value. (For more information about using MetroPlanner, refer to the Cisco MetroPlanner DWDM Operations Guide, Release 2.5.

Step 4 If the optical power level is within specifications, check and modify the channel LOS and OSC LOS thresholds, then run automatic node setup (ANS) to execute the changes:

a. In node view, click the Provisioning > WDM-ANS > Provisioning tabs.

b. Consult the Cisco MetroPlanner DWDM Operations Guide, Release 2.5 to decide what values to use, then modify the following items:

West Side Rx. Channel OSC LOS Threshold

West Side Rx. Channel LOS Threshold

c. Click the WDM-ANS > Port Status tabs.

d. Click Launch ANS and click Yes in the confirmation dialog box.

Step 5 If the optical power is outside of the expected range, check the power level transmitted at the other side of the span using CTC:

a. On the transmitting node, double-click the transmitting MXP or TXP to display the card view.

b. Click the Provisioning > Optics Thresholds tab.

c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.

Step 6 If the transmitted power value is within the expected range, clean the receiving node (where the LOS is raised) and clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 7 If the transmitted power value is outside of the expected range, troubleshoot using the DWDM acceptance tests in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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

Step 9 If no other alarms exist that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


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


2.8.196  LOS (TRUNK)

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

Logical Object: TRUNK

The Loss of Signal for a TRUNK applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.

Clear the LOS (TRUNK) Alarm


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, verify that the correct port is in service:

a. Confirm that the LED is correctly illuminated on the physical card.

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the admin state column lists the port as IS.

e. If the admin state column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Step 3 If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the TXP or MXP card receiver specifications. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for levels.

Step 5 If the optical power level is within specifications, use an optical test set to verify that a valid signal exists on the line.

For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

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

Step 7 Repeat Steps 1 to 6 for any other port on the card reporting the LOS (TRUNK).

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

Step 9 If no other alarms exist that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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


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


2.8.197  LOS-O

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

Logical Objects: OCH, OMS, OTS

The Incoming Overhead Loss of Signal alarm applies to the OSC-RX port of OPT-BST (LINE-2-RX), the OSC-RX port of OSCM (LINE-1-RX), and the internal optical port of OSC-CSM card (LINE-3-RX Port 3). It is raised when the monitored input power crosses the FAIL-LOW threshold and the OSC signal is lost. The is alarm is demoted if another LOS alarm is also present.

Clear the LOS-O Alarm


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 3 Verify that the received power (opwrMin) is within the expected range shown in Cisco MetroPlanner. To check the level:

a. Double-click the amplifier card to display the card view.

b. Display the optical thresholds by clicking the following tabs:

OPT-BST Provisioning > Opt. Ampli. Line > Optics Thresholds tab

OSCM Provisioning > Optical Line > Optics Thresholds tab

Step 4 If the optical power level is within specifications, check and modify the OSC LOS threshold, then run ANS to execute the changes:

a. In node view, click the Provisioning > WDM-ANS > Provisioning tabs.

b. Consult the Cisco MetroPlanner DWDM Operations Guide, Release 2.5 to decide upon values, then modify the West Side Rx. Channel OSC LOS Threshold.

c. Click the WDM-ANS > Port Status tabs.

d. Click Launch ANS and click Yes in the confirmation dialog box.

Step 5 If the port power is outside of the expected range, verify that OSC connections have been created on the other side of the span. If the connections are not present, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for procedures.

Step 6 If OSC connections are present, check the OSC transmitted power using CTC:

a. On the transmitting node, double-click the transmitting OSC-CSM to display the card view.

b. Click the Provisioning > Optics Thresholds tab.

c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.

Step 7 If the transmitted OSC value is out of range, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for DWDM acceptance test procedures that will aid in troubleshooting the problem.

Step 8 If the OSC value is within range, come back to the port reporting the LOS-O alarm and clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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

Step 10 If no other alarms exist that could be the source of the LOS-O, or if clearing an alarm did not clear the LOS-O, place all of the card ports in OOS,DSBLD admin state.

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


Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external traffic switch if possible.



Note When you replace a card with an identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS,AINS admin state.


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


2.8.198  LOS-P (OCH, OMS, OTS)

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

Logical Objects: OCH, OMS, OTS

The Path Loss of Signal Absent alarm applies to all input ports of AD-1B-xx.x, AD-4B-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, OPT-PRE, OPT-BST, 32MUX-O, 32DMX, 32DMX-O, 32WSS, and OSC-CSM cards. It indicates that there is a loss or received signal at the OSC-CSM card or the OPT-BST card Line-1-TX (COM-TX) port and that the monitored input power has crossed the opwrMin threshold.

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


Step 1 Verify fiber continuity to the port.

Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 3 Verify that the received power (opwrMin) is within the expected range shown in Cisco MetroPlanner. To check the level:

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

b. Display the optical thresholds by clicking the following tabs:

OPT-BST Provisioning > Opt. Ampli. Line > Optics Thresholds tab

OPT-PRE Provisioning > Opt. Ampli. Line > Optics Thresholds tab

AD-xC Provisioning > Optical Chn> Optics Thresholds tab

AD-xB Provisioning > Optical Band > Optics Thresholds tab

32DMX Provisioning > Optical Chn > Optics Thresholds tab

32MUX Provisioning > Optical Chn > Optics Thresholds tab

32WSS Provisioning > Optical Chn: Optical Connector x > Optics Thresholds tab

OSCM Provisioning > Optical Line > Optics Thresholds tab.

Step 4 If the optical power level is within specifications, check the opwrMin threshold. Consult the Cisco MetroPlanner DWDM Operations Guide, Release 2.5 to decide upon values, then modify the value as necessary.

Step 5 If the optical power is outside of the expected range, verify that all involved optical signal sources, namely the TXP or MXP trunk port or an ITU-T line card, are in IS admin state by clicking the appropriate tab:

MXPP_MR_2.5G Provisioning > Line > OC48 tab

MXP_2.5G_10E Provisioning > Line > Trunk tab

MXP_2.5G_10G Provisioning > Line > SONET tab

MXP_MR_2.5G Provisioning > Line > OC48 tab

TXPP_MR_2.5G Provisioning > Line > OC48 tab

TXP_MR_10E Provisioning > Line > SONET tab

TXP_MR_10G Provisioning > Line > SONET tab

TXP_MR_2.5G Provisioning > Line > SONET tab

If it is not IS, choose IS from the admin state drop-down list.

If the alarm does not clear, continue by completing the "Clear the LOS-P (TRUNK) Alarm" procedure.

Step 6 If the signal source is IS-NR and within the expected range, come back to the port reporting the LOS-P alarm and clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 DWDM Installation and Operations Guide.


Note Unplugging the fiber can cause a traffic hit. To avoid this, perform a traffic switch if possible. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for basic instructions, or to the Cisco ONS 15454 DWDM Installation and Operations Guide for more detailed information.


Step 7 Repeat Steps 1 through 6 for any other port on the card reporting the LOS-P alarm.

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

Step 9 If no other alarms exist that could be the source of the LOS-P, or if clearing an alarm did not clear the LOS-P, place all of the card ports in OOS,DSBLD admin state.

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


Note When you replace a card with an identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS,AINS admin state.


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


2.8.199  LOS-P (TRUNK)

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

Logical Object: TRUNK

The Path Loss of Signal Absent alarm applies to all input ports of AD-1B-xx.x, AD-4B-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, OPT-PRE, OPT-BST, 32MUX-O, 32DMX, 32DMX-O, 32WSS, and OSC-CSM cards when there is a loss or received signal at an input port caused by MXP or TXP transmit port errors.

Clear the LOS-P (TRUNK) Alarm


Step 1 On the transmit MXP or TXP card, check the output power using CTC:

a. On the transmitting node, double-click the card to display the card view.

b. Click the Provisioning > Optics Thresholds tab.

c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.

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

Step 3 If no other alarms exist that could be the source of the LOS-P, or if clearing an alarm did not clear the LOS-P, place all of the card ports in OOS,DSBLD admin state.

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


Note When you replace a card with an identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS,AINS admin state.


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


2.8.200  LO-TXPOWER

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

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

The Equipment Low Transmit Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G card transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.

Clear the LO-TXPOWER Alarm


Step 1 Display the MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card view.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Increase the TX Power Low column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be increased without affecting the signal, complete the "Physically Replace a Traffic 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 "Protection Switching, Lock Initiation, and Clearing" section for commonly used procedures.


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 no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.8.201  LPBKCRS

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

Logical Object: STSMON

The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between an optical card and an OC-192 card. A cross-connect loopback test occurs below line speed and does not affect traffic.


Note Cross-connect loopbacks occur below line speed. They do not affect traffic.


Clear the LPBKCRS Condition


Step 1 To remove the loopback cross-connect condition, double-click the optical card in CTC to display the card view.

Step 2 Complete the "Clear an OC-N Card XC Loopback Circuit" procedure.

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


2.8.202  LPBKDS1FEAC

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