Cisco ONS 15454 Troubleshooting Guide, Release 7.0
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 2.52MB) The complete bookPDF (PDF - 10.83MB) | Feedback

Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Indexes 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 Listed By Alphabetical Entry

2.3  Alarm Logical Objects

2.4  Alarm List by Logical Object Type

2.5  Trouble Notifications

2.5.1  Alarm Characteristics

2.5.2  Condition Characteristics

2.5.3  Severities

2.5.4  Alarm Hierarchy

2.5.5  Service Effect

2.5.6  States

2.6  Safety Summary

2.7  Alarm Procedures

2.7.1  AIS

Clear the AIS Condition

2.7.2  AIS-L

Clear the AIS-L Condition

2.7.3  AIS-P

Clear the AIS-P Condition

2.7.4  AIS-V

Clear the AIS-V Condition

2.7.5  ALS

2.7.6  AMPLI-INIT

2.7.7  APC-CORRECTION-SKIPPED

2.7.8  APC-DISABLED

2.7.9  APC-END

2.7.10  APC-OUT-OF-RANGE

2.7.11  APSB

2.7.12  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.13  APSC-IMP

Clear the APSC-IMP Alarm

2.7.14  APSCINCON

Clear the APSCINCON Alarm

2.7.15  APSCM

Clear the APSCM Alarm

2.7.16  APSCNMIS

Clear the APSCNMIS Alarm

2.7.17  APSIMP

Clear the APSIMP Alarm

2.7.18  APS-INV-PRIM

2.7.19  APSMM

Clear the APSMM Alarm

2.7.20  APS-PRIM-FAC

Clear the APS-PRIM-FAC Condition

2.7.21  APS-PRIM-SEC-MISM

Clear the APS-PRIM-SEC-MISM Alarm

2.7.22  AS-CMD

Clear the AS-CMD Condition

2.7.23  AS-MT

Clear the AS-MT Condition

2.7.24  AS-MT-OOG

2.7.25  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.26  AUD-LOG-LOW

2.7.27  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.7.28  AUTORESET

Clear the AUTORESET Alarm

2.7.29  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.7.30  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.7.31  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Condition

2.7.32  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.7.33  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.7.34  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.7.35  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.7.36  AUTOSW-UNEQ (VT-MON)

Clear the AUTOSW-UNEQ (VT-MON) Condition

2.7.37  AWG-DEG

2.7.38  AWG-FAIL

2.7.39  AWG-OVERTEMP

2.7.40  AWG-WARM-UP

2.7.41  BAT-FAIL

Clear the BAT-FAIL Alarm

2.7.42  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.43  BLSROSYNC

2.7.44  BLSR-SW-VER-MISM

Clear the BLSR-SW-VER-MISM Alarm

2.7.45  BPV

Clear the BPV Alarm

2.7.46  CARLOSS (CE1000, CE100T)

Clear the CARLOSS (CE100T) Alarm

2.7.47  CARLOSS (E1000F, E100T)

Clear the CARLOSS (E1000F, E100T) Alarm

2.7.48  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.49  CARLOSS (FC)

2.7.50  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.7.51  CARLOSS (GE)

2.7.52  CARLOSS (ISC)

2.7.53  CARLOSS (ML1000, ML100T, MLFX)

Clear the CARLOSS (ML1000, ML100T, MLFX) Alarm

2.7.54  CARLOSS (TRUNK)

2.7.55  CASETEMP-DEG

2.7.56  CLDRESTART

Clear the CLDRESTART Condition

2.7.57  COMIOXC

Clear the COMIOXC Alarm

2.7.58  COMM-FAIL

Clear the COMM-FAIL Alarm

2.7.59  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.60  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.7.61  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.7.62  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.63  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.64  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.7.65  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.66  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.67  DATAFLT

Clear the DATAFLT Alarm

2.7.68  DBOSYNC

Clear the DBOSYNC Alarm

2.7.69  DISCONNECTED

Clear the DISCONNECTED Alarm

2.7.70  DS3-MISM

Clear the DS3-MISM Condition

2.7.71  DSP-COMM-FAIL

2.7.72  DSP-FAIL

2.7.73  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.74  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.75  DUP-SHELF-ID

2.7.76  EHIBATVG

Clear the EHIBATVG Alarm

2.7.77  ELWBATVG

Clear the ELWBATVG Alarm

2.7.78  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.7.79  EOC

Clear the EOC Alarm

2.7.80  EOC-L

Clear the EOC-L Alarm

2.7.81  EQPT

Clear the EQPT Alarm

2.7.82  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.7.83  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.84  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.7.85  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.7.86  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.7.87  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.88  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.89  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.7.90  EXCCOL

Clear the EXCCOL Alarm

2.7.91  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.92  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.7.93  EXT

Clear the EXT Alarm

2.7.94  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.95  FAILTOSW

Clear the FAILTOSW Condition

2.7.96  FAILTOSW-PATH

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration

2.7.97  FAILTOSWR

Clear the FAILTOSWR Condition in a BLSR Configuration

2.7.98  FAILTOSWS

Clear the FAILTOSWS Condition

2.7.99  FAN

Clear the FAN Alarm

2.7.100  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.7.101  FDI

2.7.102  FE-AIS

Clear the FE-AIS Condition

2.7.103  FEC-MISM

2.7.104  FE-DS1-MULTLOS

Clear the FE-DS1-MULTLOS Condition

2.7.105  FE-DS1-NSA

Clear the FE-DS1-NSA Condition

2.7.106  FE-DS1-SA

Clear the FE-DS1-SA Condition

2.7.107  FE-DS1-SNGLLOS

Clear the FE-DS1-SNGLLOS Condition

2.7.108  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.7.109  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.7.110  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.111  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.7.112  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.113  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.114  FE-IDLE

Clear the FE-IDLE Condition

2.7.115  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.116  FE-LOF

Clear the FE-LOF Condition

2.7.117  FE-LOS

Clear the FE-LOS Condition

2.7.118  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.7.119  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.120  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.121  FEPRLF

Clear the FEPRLF Alarm on a Four-Fiber BLSR

2.7.122  FIBERTEMP-DEG

2.7.123  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.124  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.125  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.126  FRCDSWTOINT

2.7.127  FRCDSWTOPRI

2.7.128  FRCDSWTOSEC

2.7.129  FRCDSWTOTHIRD

2.7.130  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.131  FSTSYNC

2.7.132  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.133  GAIN-HDEG

2.7.134  GAIN-HFAIL

2.7.135  GAIN-LDEG

2.7.136  GAIN-LFAIL

2.7.137  GCC-EOC

2.7.138  GE-OOSYNC

2.7.139  GFP-CSF

Clear the GFP-CSF Alarm

2.7.140  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.7.141  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.7.142  GFP-LFD

Clear the GFP-LFD Alarm

2.7.143  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.7.144  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.7.145  HELLO

Clear the HELLO Alarm

2.7.146  HIBATVG

Clear the HIBATVG Alarm

2.7.147  HI-CCVOLT

Clear the HI-CCVOLT Condition

2.7.148  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.149  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.7.150  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.151  HITEMP

Clear the HITEMP Alarm

2.7.152  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.153  HLDOVRSYNC

Clear the HLDOVRSYNC Condition

2.7.154  I-HITEMP

Clear the I-HITEMP Alarm

2.7.155  INCOMPATIBLE-SEND-PDIP

Clear the INCOMPATIBLE-SEND-PDIP Alarm

2.7.156  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.7.157  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.158  INC-ISD

2.7.159  INHSWPR

Clear the INHSWPR Condition

2.7.160  INHSWWKG

Clear the INHSWWKG Condition

2.7.161  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.162  INVMACADR

Clear the INVMACADR Alarm

2.7.163  IOSCFGCOPY

2.7.164  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.7.165  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.166  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.7.167  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.7.168  LASER-APR

2.7.169  LASERBIAS-DEG

2.7.170  LASERBIAS-FAIL

2.7.171  LASEREOL

Clear the LASEREOL Alarm

2.7.172  LASERTEMP-DEG

2.7.173  LCAS-CRC

Clear the LCAS-CRC Condition

2.7.174  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.7.175  LCAS-TX-ADD

2.7.176  LCAS-TX-DNU

2.7.177  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.178  LOA

Clear the LOA Alarm

2.7.179  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.180  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.181  LOF (DS1)

Clear the LOF (DS1) Alarm

2.7.182  LOF (DS3)

Clear the LOF (DS3) Alarm

2.7.183  LOF (E1)

Clear the LOF (E1) Alarm

2.7.184  LOF (EC1)

Clear the LOF (EC1) Alarm

2.7.185  LOF (OCN)

Clear the LOF (OCN) Alarm

2.7.186  LOF (STSTRM)

Clear the LOF (STSTRM) Alarm

2.7.187  LOF (TRUNK)

2.7.188  LOGBUFR90

2.7.189  LOGBUFROVFL

Clear the LOGBUFROVFL Alarm

2.7.190  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.7.191  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.7.192  LOM

Clear the LOM Alarm

2.7.193  LOP-P

Clear the LOP-P Alarm

2.7.194  LOP-V

Clear the LOP-V Alarm

2.7.195  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.196  LOS (2R)

2.7.197  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.198  LOS (DS1)

Clear the LOS (DS1) Alarm

2.7.199  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.200  LOS (E1)

Clear the LOS (E1) Alarm

2.7.201  LOS (EC1)

Clear the LOS (EC1) Alarm

2.7.202  LOS (ESCON)

2.7.203  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.204  LOS (ISC)

2.7.205  LOS (MSUDC)

2.7.206  LOS (OCN)

Clear the LOS (OCN) Alarm

2.7.207  LOS (OTS)

2.7.208  LOS (TRUNK)

2.7.209  LOS-O

2.7.210  LOS-P (OCH)

2.7.211  LOS-P (OMS, OTS)

2.7.212  LOS-P (TRUNK)

2.7.213  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.7.214  LPBKCRS

Clear the LPBKCRS Condition

2.7.215  LPBKDS1FEAC-CMD

2.7.216  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.217  LPBKDS3FEAC-CMD

2.7.218  LPBKFACILITY (CE1000, CE100T)

Clear the LPBKFACILITY (CE1000, CE100T) Condition

2.7.219  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.220  LPBKFACILITY (E1)

Clear the LPBKFACILITY (E1) Condition

2.7.221  LPBKFACILITY (EC1)

Clear the LPBKFACILITY (EC1) Condition

2.7.222  LPBKFACILITY (ESCON)

2.7.223  LPBKFACILITY (FC)

2.7.224  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.7.225  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.7.226  LPBKFACILITY (GE)

2.7.227  LPBKFACILITY (ISC)

2.7.228  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.7.229  LPBKFACILITY (TRUNK)

2.7.230  LPBKTERMINAL (CE1000, CE100T)

Clear the LPBKTERMINAL (CE1000, CE100T) Condition

2.7.231  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.7.232  LPBKTERMINAL (E1)

Clear the LPBKTERMINAL (E1) Condition

2.7.233  LPBKTERMINAL (EC1)

Clear the LPBKTERMINAL (EC1) Condition

2.7.234  LPBKTERMINAL (ESCON)

2.7.235  LPBKTERMINAL (FC)

2.7.236  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.7.237  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.7.238  LPBKTERMINAL (GE)

2.7.239  LPBKTERMINAL (ISC)

2.7.240  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.7.241  LPBKTERMINAL (TRUNK)

2.7.242  LWBATVG

Clear the LWBATVG Alarm

2.7.243  MAN-REQ

Clear the MAN-REQ Condition

2.7.244  MANRESET

2.7.245  MANSWTOINT

2.7.246  MANSWTOPRI

2.7.247  MANSWTOSEC

2.7.248  MANSWTOTHIRD

2.7.249  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.250  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.251  MEA (AIP)

Clear the MEA (AIP) Alarm

2.7.252  MEA (BIC)

Clear the MEA (BIC) Alarm

2.7.253  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.254  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.255  MEA (PPM)

2.7.256  MEM-GONE

2.7.257  MEM-LOW

2.7.258  MFGMEM

Clear the MFGMEM Alarm

2.7.259  NO-CONFIG

Clear the NO-CONFIG Condition

2.7.260  NOT-AUTHENTICATED

2.7.261  OCHNC-INC

2.7.262  OCHTERM-INC

2.7.263  ODUK-1-AIS-PM

2.7.264  ODUK-2-AIS-PM

2.7.265  ODUK-3-AIS-PM

2.7.266  ODUK-4-AIS-PM

2.7.267  ODUK-AIS-PM

2.7.268  ODUK-BDI-PM

2.7.269  ODUK-LCK-PM

2.7.270  ODUK-OCI-PM

2.7.271  ODUK-SD-PM

2.7.272  ODUK-SF-PM

2.7.273  ODUK-TIM-PM

2.7.274  OOU-TPT

Clear the OOT-TPT Condition

2.7.275  OPEN-SLOT

Clear the OPEN-SLOT Condition

2.7.276  OPTNTWMIS

2.7.277  OPWR-HDEG

2.7.278  OPWR-HFAIL

2.7.279  OPWR-LDEG

2.7.280  OPWR-LFAIL

2.7.281  OSRION

2.7.282  OTUK-AIS

2.7.283  OTUK-BDI

2.7.284  OTUK-IAE

2.7.285  OTUK-LOF

2.7.286  OTUK-SD

2.7.287  OTUK-SF

2.7.288  OTUK-TIM

2.7.289  OUT-OF-SYNC

2.7.290  PARAM-MISM

2.7.291  PDI-P

Clear the PDI-P Condition

2.7.292  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.293  PLM-P

Clear the PLM-P Alarm

2.7.294  PLM-V

Clear the PLM-V Alarm

2.7.295  PMI

2.7.296  PORT-ADD-PWR-DEG-HIGH

2.7.297  PORT-ADD-PWR-DEG-LOW

2.7.298  PORT-ADD-PWR-FAIL-HIGH

2.7.299  PORT-ADD-PWR-FAIL-LOW

2.7.300  PORT-FAIL

2.7.301  PORT-MISMATCH

Clear the PORT-MISMATCH Alarm

2.7.302  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.303  PROTNA

Clear the PROTNA Alarm

2.7.304  PROV-MISMATCH

2.7.305  PTIM

2.7.306  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.307  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.308  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.7.309  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.7.310  RAI

Clear the RAI Condition

2.7.311  RCVR-MISS

Clear the RCVR-MISS Alarm

2.7.312  RFI

2.7.313  RFI-L

Clear the RFI-L Condition

2.7.314  RFI-P

Clear the RFI-P Condition

2.7.315  RFI-V

Clear the RFI-V Condition

2.7.316  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.7.317  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.318  RING-SW-EAST

2.7.319  RING-SW-WEST

2.7.320  ROLL

2.7.321  ROLL-PEND

2.7.322  RPRW

Clear the RPRW Condition

2.7.323  RUNCFG-SAVENEED

2.7.324  SD (DS1, DS3)

Clear the SD (DS1, DS3) Condition

2.7.325  SD (E1)

Clear the SD (E1) Condition

2.7.326  SD (TRUNK)

2.7.327  SD-L

Clear the SD-L Condition

2.7.328  SD-L (TRUNK)

2.7.329  SD-P

Clear the SD-P Condition

2.7.330  SD-V

Clear the SD-V Condition

2.7.331  SF (DS1, DS3)

Clear the SF (DS1, DS3) Condition

2.7.332  SF (E1)

Clear the SF (E1) Condition

2.7.333  SF (TRUNK)

2.7.334  SF-L

Clear the SF-L Condition

2.7.335  SF-L (TRUNK)

2.7.336  SF-P

Clear the SF-P Condition

2.7.337  SFTWDOWN

2.7.338  SF-V

Clear the SF-V Condition

2.7.339  SHELF-COMM-FAIL

2.7.340  SH-INS-LOSS-VAR-DEG-HIGH

2.7.341  SH-INS-LOSS-VAR-DEG-LOW

2.7.342  SHUTTER-OPEN

2.7.343  SIGLOSS

Clear the SIGLOSS Alarm

2.7.344  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.345  SPANLENGTH-OUT-OF-RANGE

2.7.346  SPAN-SW-EAST

2.7.347  SPAN-SW-WEST

2.7.348  SQUELCH

Clear the SQUELCH Condition

2.7.349  SQUELCHED

Clear the SQUELCHED Condition

2.7.350  SQM

Clear the SQM Alarm

2.7.351  SSM-DUS

2.7.352  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.353  SSM-LNC

2.7.354  SSM-OFF

Clear the SSM-OFF Condition

2.7.355  SSM-PRC

2.7.356  SSM-PRS

2.7.357  SSM-RES

2.7.358  SSM-SDN-TN

2.7.359  SSM-SETS

2.7.360  SSM-SMC

2.7.361  SSM-ST2

2.7.362  SSM-ST3

2.7.363  SSM-ST3E

2.7.364  SSM-ST4

2.7.365  SSM-STU

Clear the SSM-STU Condition

2.7.366  SSM-TNC

2.7.367  STS-SQUELCH-L

2.7.368  SW-MISMATCH

Clear the SW-MISMATCH Condition

2.7.369  SWMTXMOD-PROT

Clear the SWMTXMOD-PROT Alarm

2.7.370  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.7.371  SWTOPRI

2.7.372  SWTOSEC

Clear the SWTOSEC Condition

2.7.373  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.7.374  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.375  SYNCLOSS

Clear the SYNCLOSS Alarm

2.7.376  SYNCPRI

Clear the SYNCPRI Alarm

2.7.377  SYNCSEC

Clear the SYNCSEC Alarm

2.7.378  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.379  SYSBOOT

2.7.380  TEMP-MISM

Clear the TEMP-MISM Condition

2.7.381  TIM

Clear the TIM Alarm

2.7.382  TIM-MON

Clear the TIM-MON Alarm

2.7.383  TIM-P

Clear the TIM-P Alarm

2.7.384  TIM-S

Clear the TIM-S Alarm

2.7.385  TIM-V

Clear the TIM-V Alarm

2.7.386  TPTFAIL (CE100T, CE1000)

Clear the TPTFAIL (CE100T, CE1000) Alarm

2.7.387  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.7.388  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.7.389  TPTFAIL (ML100T, ML1000, MLFX)

Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm

2.7.390  TRMT

Clear the TRMT Alarm

2.7.391  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.392  TX-AIS

Clear the TX-AIS Condition

2.7.393  TX-LOF

Clear the TX-LOF Condition

2.7.394  TX-RAI

Clear the TX-RAI Condition

2.7.395  UNC-WORD

2.7.396  UNEQ-P

Clear the UNEQ-P Alarm

2.7.397  UNEQ-V

Clear the UNEQ-V Alarm

2.7.398  UNREACHABLE-TARGET-POWER

2.7.399  UT-COMM-FAIL

2.7.400  UT-FAIL

2.7.401  VCG-DEG

Clear the VCG-DEG Condition

2.7.402  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.403  VOA-HDEG

2.7.404  VOA-HFAIL

2.7.405  VOA-LDEG

2.7.406  VOA-LFAIL

2.7.407  VOLT-MISM

Clear the VOLT-MISM Condition

2.7.408  VT-SQUELCH-L

2.7.409  WKSWPR

Clear the WKSWPR Condition

2.7.410  WTR

2.7.411  WVL-MISMATCH

2.8  Traffic Card LED Activity

2.8.1  Typical Traffic Card LED Activity After Insertion

2.8.2  Typical Traffic Card LED Activity During Reset

2.8.3  Typical Card LED State After Successful Reset

2.8.4  Typical Cross-Connect LED Activity During Side Switch

2.9  Frequently Used Alarm Troubleshooting Procedures

2.9.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.9.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Force Switch Command

Initiate a 1+1 Manual Switch Command

Clear a 1+1 Force or Manual Switch Command

Initiate a Lock-On Command

Initiate a Card or Port Lockout Command

Clear a Lock-On or Lockout Command

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 Lockout for All Circuits on a Protect Path Protection Span

Clear an External Switching Command on a Path Protection Span

Initiate a Force Ring Switch on a BLSR

Initiate a Force Span Switch on a Four-Fiber BLSR

Initiate a Manual Span Switch on a BLSR

Initiate a Manual Ring Switch on a BLSR

Initiate a Lockout 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.9.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

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

Side Switch the Active and Standby Cross-Connect Cards

2.9.4  Physical Card Reseating, Resetting, and Replacement

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

Remove and Reinsert (Reseat) Any Card

Physically Replace a Traffic Card

Physically Replace an In-Service Cross-Connect Card

2.9.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node Section DCC Terminations

Clear an OC-N Card Facility or Terminal Loopback Circuit

Clear an OC-N Card Cross-Connect (XC) Loopback Circuit

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

Clear Other Electrical Card or Ethernet Card Loopbacks

Clear an MXP, TXP, or FC_MR-4 Card Loopback Circuit

2.9.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.9.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-7 gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in Table 2-8. For a comprehensive list of all conditions and instructions for using TL1 commands, refer to the Cisco ONS SONET TL1 Command Guide .

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

Alarms can occur even in those cards that are not explicitly mentioned in the Alarm sections. When an alarm is raised, refer to its clearing procedure.

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

2.1  Alarm Indexes 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.



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


2.1.1  Critical Alarms (CR)

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

Table 2-1 ONS 15454 Critical Alarm List 

AUTOLSROFF (OCN)

LOF (TRUNK)

OPWR-HFAIL (OMS)

AWG-FAIL (OTS)

LOM (STSMON)

OPWR-HFAIL (OTS)

AWG-OVERTEMP (OTS)

LOM (STSTRM)

OPWR-LFAIL (AOTS)

BKUPMEMP (EQPT)

LOM (TRUNK)

OPWR-LFAIL (OCH)

COMIOXC (EQPT)

LOP-P (STSMON)

OPWR-LFAIL (OMS)

CONTBUS-DISABLED (EQPT)

LOP-P (STSTRM)

OPWR-LFAIL (OTS)

CTNEQPT-PBPROT (EQPT)

LOS (2R)

OTUK-LOF (TRUNK)

CTNEQPT-PBWORK (EQPT)

LOS (DS3)

OTUK-TIM (TRUNK)

ENCAP-MISMATCH-P (STSTRM)

LOS (EC1)

PLM-P (STSMON)

EQPT (AICI-AEP)

LOS (ESCON)

PLM-P (STSTRM)

EQPT (AICI-AIE)

LOS (ISC)

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

EQPT (EQPT)

LOS (OCN)

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

EQPT (PPM)

LOS (OTS)

PORT-FAIL (OCH)

EQPT-DIAG (EQPT)

LOS (TRUNK)

SQM (STSTRM)

EQPT-MISS (FAN)

LOS-P (OCH)

SWMTXMOD-PROT (EQPT)

FAN (FAN)

LOS-P (OMS)

SWMTXMOD-WORK (EQPT)

GAIN-HFAIL (AOTS)

LOS-P (OTS)

TIM (OCN)

GAIN-LFAIL (AOTS)

LOS-P (TRUNK)

TIM (TRUNK)

GE-OOSYNC (FC)

MEA (AIP)

TIM-P (STSTRM)

GE-OOSYNC (GE)

MEA (BIC)

TIM-S (EC1)

GE-OOSYNC (ISC)

MEA (EQPT)

TIM-S (OCN)

GE-OOSYNC (TRUNK)

MEA (FAN)

UNEQ-P (STSMON)

HITEMP (NE)

MEA (PPM)

UNEQ-P (STSTRM)

I-HITEMP (NE)

MFGMEM (AICI-AEP)

VOA-HFAIL (AOTS)

IMPROPRMVL (EQPT)

MFGMEM (AICI-AIE)

VOA-HFAIL (OCH)

IMPROPRMVL (PPM)

MFGMEM (AIP)

VOA-HFAIL (OMS)

LOA (VCG)

MFGMEM (BPLANE)

VOA-HFAIL (OTS)

LOF (DS3)

MFGMEM (FAN)

VOA-LFAIL (AOTS)

LOF (EC1)

MFGMEM (PPM)

VOA-LFAIL (OCH)

LOF (OCN)

OPWR-HFAIL (AOTS)

VOA-LFAIL (OMS)

LOF (STSTRM)

OPWR-HFAIL (OCH)

VOA-LFAIL (OTS)


2.1.2  Major Alarms (MJ)

Table 2-2 alphabetically lists ONS 15454 Major (MJ) alarms.

Table 2-2 ONS 15454 Major Alarm List 

APSCM (OCN)

GFP-EX-MISMATCH (FCMR)

PROV-MISMATCH (TRUNK)

APSCNMIS (OCN)

GFP-EX-MISMATCH (GFP-FAC)

PTIM (TRUNK)

BAT-FAIL (PWR)

GFP-LFD (CE1000)

RCVR-MISS (DS1)

BLSROSYNC (OCN)

GFP-LFD (CE100T)

RCVR-MISS (E1)

BLSR-SW-VER-MISM (OCN)

GFP-LFD (FCMR)

RING-ID-MIS (OCN)

CARLOSS (ML1000)

GFP-LFD (GFP-FAC)

RING-ID-MIS (OSC-RING)

CARLOSS (CE1000)

GFP-LFD (LOGFAC)

RING-MISMATCH (OCN)

CARLOSS (CE100T)

GFP-LFD (ML1000)

SHELF-COMM-FAIL (SHELF)

CARLOSS (E1000F)

GFP-LFD (ML100T)

SIGLOSS (ESCON)

CARLOSS (E100T)

GFP-LFD (MLFX)

SIGLOSS (FC)

CARLOSS (EQPT)

GFP-NO-BUFFERS (FCMR)

SIGLOSS (FCMR)

CARLOSS (FC)

GFP-NO-BUFFERS (GFP-FAC)

SIGLOSS (GE)

CARLOSS (G1000)

GFP-UP-MISMATCH (CE1000)

SIGLOSS (ISC)

CARLOSS (GE)

GFP-UP-MISMATCH (CE100T)

SIGLOSS (TRUNK)

CARLOSS (ISC)

GFP-UP-MISMATCH (FCMR)

SQM (VT-TERM)

CARLOSS (LOGFAC)

GFP-UP-MISMATCH (GFP-FAC)

SYNCLOSS (FC)

CARLOSS (ML100T)

GFP-UP-MISMATCH (LOGFAC)

SYNCLOSS (FCMR)

CARLOSS (MLFX)

GFP-UP-MISMATCH (ML1000)

SYNCLOSS (GE)

CARLOSS (TRUNK)

GFP-UP-MISMATCH (ML100T)

SYNCLOSS (ISC)

DBOSYNC (NE)

GFP-UP-MISMATCH (MLFX)

SYNCLOSS (TRUNK)

DSP-COMM-FAIL (TRUNK)

HIBATVG (PWR)

SYNCPRI (NE-SREF)

DSP-FAIL (TRUNK)

INVMACADR (AIP)

SYSBOOT (NE)

DUP-SHELF-ID (SHELF)

LASERBIAS-FAIL (AOTS)

TIM-V (VT-TERM)

EHIBATVG (PWR)

LOF (DS1)

TPTFAIL (CE1000)

ELWBATVG (PWR)

LOF (E1)

TPTFAIL (CE100T)

E-W-MISMATCH (OCN)

LOM (VT-TERM)

TPTFAIL (FCMR)

EXTRA-TRAF-PREEMPT (OCN)

LOP-V (VT-MON)

TPTFAIL (G1000)

FC-NO-CREDITS (FC)

LOP-V (VT-TERM)

TPTFAIL (LOGFAC)

FC-NO-CREDITS (FCMR)

LOS (DS1)

TPTFAIL (ML1000)

FC-NO-CREDITS (TRUNK)

LOS (E1)

TPTFAIL (ML100T)

GFP-CSF (CE1000)

LWBATVG (PWR)

TPTFAIL (MLFX)

GFP-CSF (CE100T)

MEA (SHELF)

TRMT (DS1)

GFP-CSF (FCMR)

MEM-GONE (EQPT)

TRMT (E1)

GFP-CSF (GFP-FAC)

ODUK-TIM-PM (TRUNK)

TRMT-MISS (DS1)

GFP-CSF (LOGFAC)

OPTNTWMIS (NE)

TRMT-MISS (E1)

GFP-CSF (ML100T)

OUT-OF-SYNC (FC)

UNEQ-V (VT-MON)

GFP-CSF (ML1000)

OUT-OF-SYNC (GE)

UNEQ-V (VT-TERM)

GFP-CSF (MLFX)

OUT-OF-SYNC (TRUNK)

UT-COMM-FAIL (TRUNK)

GFP-DE-MISMATCH (FCMR)

PEER-NORESPONSE (EQPT)

UT-FAIL (TRUNK)

GFP-DE-MISMATCH (GFP-FAC)

PLM-V (VT-TERM)

WVL-MISMATCH (TRUNK)

GFP-EX-MISMATCH (CE1000)

PRC-DUPID (OCN)


2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15454 Minor Alarm List 

APSB (OCN)

HI-RXPOWER (FC)

MEM-LOW (EQPT)

APSCDFLTK (OCN)

HI-RXPOWER (GE)

OPWR-HDEG (AOTS)

APSC-IMP (OCN)

HI-RXPOWER (ISC)

OPWR-HDEG (OCH)

APSCINCON (OCN)

HI-RXPOWER (OCN)

OPWR-HDEG (OMS)

APSIMP (OCN)

HITEMP (EQPT)

OPWR-HDEG (OTS)

APS-INV-PRIM (OCN)

HI-TXPOWER (2R)

OPWR-LDEG (AOTS)

APSMM (OCN)

HI-TXPOWER (EQPT)

OPWR-LDEG (OCH)

APS-PRIM-SEC-MISM (OCN)

HI-TXPOWER (ESCON)

OPWR-LDEG (OMS)

AUTORESET (EQPT)

HI-TXPOWER (FC)

OPWR-LDEG (OTS)

AUTOSW-UNEQ (VT-MON)

HI-TXPOWER (GE)

OTUK-IAE (TRUNK)

AWG-DEG (OTS)

HI-TXPOWER (ISC)

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

BPV (BITS)

HI-TXPOWER (OCN)

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

CASETEMP-DEG (AOTS)

HI-TXPOWER (PPM)

PROTNA (EQPT)

COMM-FAIL (EQPT)

ISIS-ADJ-FAIL (OCN)

PROV-MISMATCH (PPM)

CONTBUS-A-18 (EQPT)

KBYTE-APS-CHANNEL-FAILURE (OCN)

PWR-FAIL-A (EQPT)

CONTBUS-B-18 (EQPT)

LASERBIAS-DEG (AOTS)

PWR-FAIL-B (EQPT)

CONTBUS-IO-A (EQPT)

LASERBIAS-DEG (OTS)

PWR-FAIL-RET-A (EQPT)

CONTBUS-IO-B (EQPT)

LASEREOL (OCN)

PWR-FAIL-RET-B (EQPT)

DATAFLT (NE)

LASERTEMP-DEG (AOTS)

SFTWDOWN (EQPT)

DUP-IPADDR (NE)

LOF (BITS)

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

DUP-NODENAME (NE)

LO-LASERBIAS (EQPT)

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

EOC (OCN)

LO-LASERBIAS (OCN)

SNTP-HOST (NE)

EOC (TRUNK)

LO-LASERBIAS (PPM)

SPANLENGTH-OUT-OF-RANGE (OTS)

EOC-L (OCN)

LO-LASERTEMP (EQPT)

SSM-FAIL (BITS)

EOC-L (TRUNK)

LO-LASERTEMP (OCN)

SSM-FAIL (DS1)

ERROR-CONFIG (EQPT)

LO-LASERTEMP (PPM)

SSM-FAIL (E1)

EXCCOL (EQPT)

LO-RXPOWER (2R)

SSM-FAIL (OCN)

EXT (ENVALRM)

LO-RXPOWER (ESCON)

SSM-FAIL (TRUNK)

FEPRLF (OCN)

LO-RXPOWER (FC)

SYNCPRI (EXT-SREF)

FIBERTEMP-DEG (AOTS)

LO-RXPOWER (GE)

SYNCSEC (EXT-SREF)

GAIN-HDEG (AOTS)

LO-RXPOWER (ISC)

SYNCSEC (NE-SREF)

GAIN-LDEG (AOTS)

LO-RXPOWER (OCN)

SYNCTHIRD (EXT-SREF)

GCC-EOC (TRUNK)

LO-TXPOWER (2R)

SYNCTHIRD (NE-SREF)

HI-LASERBIAS (2R)

LOS (BITS)

TIM-MON (OCN)

HI-LASERBIAS (EQPT)

LOS (FUDC)

TIM-MON (TRUNK)

HI-LASERBIAS (ESCON)

LOS (MSUDC)

TIM-P (STSMON)

HI-LASERBIAS (FC)

LOS-O (OCH)

UNREACHABLE-TARGET-POWER (OCH)

HI-LASERBIAS (GE)

LOS-O (OMS)

VOA-HDEG (AOTS)

HI-LASERBIAS (ISC)

LOS-O (OTS)

VOA-HDEG (OCH)

HI-LASERBIAS (OCN)

LO-TXPOWER (EQPT)

VOA-HDEG (OMS)

HI-LASERBIAS (PPM)

LO-TXPOWER (ESCON)

VOA-HDEG (OTS)

HI-LASERTEMP (EQPT)

LO-TXPOWER (FC)

VOA-LDEG (AOTS)

HI-LASERTEMP (OCN)

LO-TXPOWER (GE)

VOA-LDEG (OCH)

HI-LASERTEMP (PPM)

LO-TXPOWER (ISC)

VOA-LDEG (OMS)

HI-RXPOWER (2R)

LO-TXPOWER (OCN)

VOA-LDEG (OTS)

HI-RXPOWER (ESCON)

LO-TXPOWER (PPM)


2.1.4  NA Conditions

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

Table 2-4 ONS 15454 NA Conditions List 

ALS (2R)

FRCDSWTOPRI (EXT-SREF)

SD-V (VT-TERM)

ALS (AOTS)

FRCDSWTOPRI (NE-SREF)

SF (DS1)

ALS (ESCON)

FRCDSWTOSEC (EXT-SREF)

SF (DS3)

ALS (FC)

FRCDSWTOSEC (NE-SREF)

SF (E1)

ALS (GE)

FRCDSWTOTHIRD (EXT-SREF)

SF (TRUNK)

ALS (ISC)

FRCDSWTOTHIRD (NE-SREF)

SF-L (EC1)

ALS (OCN)

FRNGSYNC (NE-SREF)

SF-L (OCN)

ALS (TRUNK)

FSTSYNC (NE-SREF)

SF-L (TRUNK)

AMPLI-INIT (AOTS)

FULLPASSTHR-BI (OCN)

SF-P (STSMON)

APC-CORRECTION-SKIPPED (AOTS)

HELLO (OCN)

SF-P (STSTRM)

APC-CORRECTION-SKIPPED (OCH)

HELLO (TRUNK)

SF-V (VT-MON)

APC-CORRECTION-SKIPPED (OMS)

HI-CCVOLT (BITS)

SF-V (VT-TERM)

APC-CORRECTION-SKIPPED (OTS)

HLDOVRSYNC (NE-SREF)

SHUTTER-OPEN (OTS)

APC-DISABLED (NE)

INC-ISD (DS3)

SPAN-NOT-MEASURED (OTS)

APC-END (NE)

INHSWPR (EQPT)

SPAN-SW-EAST (OCN)

APC-OUT-OF-RANGE (AOTS)

INHSWWKG (EQPT)

SPAN-SW-WEST (OCN)

APC-OUT-OF-RANGE (OCH)

INTRUSION-PSWD (NE)

SQUELCH (OCN)

APC-OUT-OF-RANGE (OMS)

IOSCFGCOPY (EQPT)

SQUELCHED (ESCON)

APC-OUT-OF-RANGE (OTS)

KB-PASSTHR (OCN)

SQUELCHED (2R)

APS-PRIM-FAC (OCN)

LAN-POL-REV (NE)

SQUELCHED (FC)

AS-CMD (2R)

LASER-APR (AOTS)

SQUELCHED (GE)

AS-CMD (AOTS)

LCAS-CRC (STSTRM)

SQUELCHED (ISC)

AS-CMD (BPLANE)

LCAS-CRC (VT-TERM)

SQUELCHED (OCN)

AS-CMD (CE1000)

LCAS-RX-FAIL (STSTRM)

SQUELCHED (TRUNK)

AS-CMD (CE100T)

LCAS-RX-FAIL (VT-TERM)

SSM-DUS (BITS)

AS-CMD (DS1)

LCAS-TX-ADD (STSTRM)

SSM-DUS (DS1)

AS-CMD (DS3)

LCAS-TX-ADD (VT-TERM)

SSM-DUS (E1)

AS-CMD (E1)

LCAS-TX-DNU (STSTRM)

SSM-DUS (OCN)

AS-CMD (E1000F)

LCAS-TX-DNU (VT-TERM)

SSM-DUS (TRUNK)

AS-CMD (E100T)

LKOUTPR-S (OCN)

SSM-LNC (BITS)

AS-CMD (EC1)

LOCKOUT-REQ (2R)

SSM-LNC (NE-SREF)

AS-CMD (EQPT)

LOCKOUT-REQ (EQPT)

SSM-LNC (TRUNK)

AS-CMD (ESCON)

LOCKOUT-REQ (ESCON)

SSM-OFF (BITS)

AS-CMD (FC)

LOCKOUT-REQ (FC)

SSM-OFF (DS1)

AS-CMD (FCMR)

LOCKOUT-REQ (GE)

SSM-OFF (E1)

AS-CMD (G1000)

LOCKOUT-REQ (ISC)

SSM-OFF (OCN)

AS-CMD (GE)

LOCKOUT-REQ (OCN)

SSM-OFF (TRUNK)

AS-CMD (GFP-FAC)

LOCKOUT-REQ (STSMON)

SSM-PRC (BITS)

AS-CMD (ISC)

LOCKOUT-REQ (TRUNK)

SSM-PRC (NE-SREF)

AS-CMD (LOGFAC)

LOCKOUT-REQ (VT-MON)

SSM-PRC (TRUNK)

AS-CMD (ML1000)

LPBKCRS (STSMON)

SSM-PRS (BITS)

AS-CMD (ML100T)

LPBKCRS (STSTRM)

SSM-PRS (DS1)

AS-CMD (MLFX)

LPBKDS1FEAC-CMD (DS1)

SSM-PRS (E1)

AS-CMD (NE)

LPBKDS3FEAC (DS3)

SSM-PRS (NE-SREF)

AS-CMD (OCH)

LPBKDS3FEAC-CMD (DS3)

SSM-PRS (OCN)

AS-CMD (OCN)

LPBKFACILITY (CE1000)

SSM-PRS (TRUNK)

AS-CMD (OMS)

LPBKFACILITY (CE100T)

SSM-RES (BITS)

AS-CMD (OTS)

LPBKFACILITY (DS1)

SSM-RES (DS1)

AS-CMD (PPM)

LPBKFACILITY (DS3)

SSM-RES (E1)

AS-CMD (PWR)

LPBKFACILITY (E1)

SSM-RES (NE-SREF)

AS-CMD (SHELF)

LPBKFACILITY (EC1)

SSM-RES (OCN)

AS-CMD (TRUNK)

LPBKFACILITY (ESCON)

SSM-RES (TRUNK)

AS-MT (2R)

LPBKFACILITY (FC)

SSM-SDH-TN (OCN)

AS-MT (AOTS)

LPBKFACILITY (FCMR)

SSM-SDH-TN (TRUNK)

AS-MT (CE1000)

LPBKFACILITY (G1000)

SSM-SETS (BITS)

AS-MT (CE100T)

LPBKFACILITY (GE)

SSM-SETS (NE-SREF)

AS-MT (DS1)

LPBKFACILITY (ISC)

SSM-SETS (TRUNK)

AS-MT (DS3)

LPBKFACILITY (OCN)

SSM-SMC (BITS)

AS-MT (E1)

LPBKFACILITY (TRUNK)

SSM-SMC (DS1)

AS-MT (EC1)

LPBKTERMINAL (CE1000)

SSM-SMC (E1)

AS-MT (EQPT)

LPBKTERMINAL (CE100T)

SSM-SMC (NE-SREF)

AS-MT (ESCON)

LPBKTERMINAL (DS1)

SSM-SMC (OCN)

AS-MT (FC)

LPBKTERMINAL (DS3)

SSM-SMC (TRUNK)

AS-MT (FCMR)

LPBKTERMINAL (E1)

SSM-ST2 (BITS)

AS-MT (G1000)

LPBKTERMINAL (EC1)

SSM-ST2 (DS1)

AS-MT (GE)

LPBKTERMINAL (ESCON)

SSM-ST2 (E1)

AS-MT (GFP-FAC)

LPBKTERMINAL (FC)

SSM-ST2 (NE-SREF)

AS-MT (ISC)

LPBKTERMINAL (FCMR)

SSM-ST2 (OCN)

AS-MT (LOGFAC)

LPBKTERMINAL (G1000)

SSM-ST2 (TRUNK)

AS-MT (ML1000)

LPBKTERMINAL (GE)

SSM-ST3 (BITS)

AS-MT (ML100T)

LPBKTERMINAL (ISC)

SSM-ST3 (DS1)

AS-MT (MLFX)

LPBKTERMINAL (OCN)

SSM-ST3 (E1)

AS-MT (OCH)

LPBKTERMINAL (TRUNK)

SSM-ST3 (NE-SREF)

AS-MT (OCN)

MAN-REQ (EQPT)

SSM-ST3 (OCN)

AS-MT (OMS)

MAN-REQ (STSMON)

SSM-ST3 (TRUNK)

AS-MT (OTS)

MAN-REQ (VT-MON)

SSM-ST3E (BITS)

AS-MT (PPM)

MANRESET (EQPT)

SSM-ST3E (DS1)

AS-MT (SHELF)

MANSWTOINT (NE-SREF)

SSM-ST3E (E1)

AS-MT (TRUNK)

MANSWTOPRI (EXT-SREF)

SSM-ST3E (NE-SREF)

AS-MT-OOG (STSTRM)

MANSWTOPRI (NE-SREF)

SSM-ST3E (OCN)

AS-MT-OOG (VT-TERM)

MANSWTOSEC (EXT-SREF)

SSM-ST3E (TRUNK)

AUD-LOG-LOSS (NE)

MANSWTOSEC (NE-SREF)

SSM-ST4 (BITS)

AUD-LOG-LOW (NE)

MANSWTOTHIRD (EXT-SREF)

SSM-ST4 (DS1)

AUTOSW-LOP (STSMON)

MANSWTOTHIRD (NE-SREF)

SSM-ST4 (E1)

AUTOSW-LOP (VT-MON)

MANUAL-REQ-RING (OCN)

SSM-ST4 (NE-SREF)

AUTOSW-PDI (STSMON)

MANUAL-REQ-SPAN (2R)

SSM-ST4 (OCN)

AUTOSW-SDBER (STSMON)

MANUAL-REQ-SPAN (ESCON)

SSM-ST4 (TRUNK)

AUTOSW-SFBER (STSMON)

MANUAL-REQ-SPAN (FC)

SSM-STU (BITS)

AUTOSW-UNEQ (STSMON)

MANUAL-REQ-SPAN (GE)

SSM-STU (DS1)

AWG-WARM-UP (OTS)

MANUAL-REQ-SPAN (ISC)

SSM-STU (E1)

CLDRESTART (EQPT)

MANUAL-REQ-SPAN (OCN)

SSM-STU (NE-SREF)

CTNEQPT-MISMATCH (EQPT)

MANUAL-REQ-SPAN (TRUNK)

SSM-STU (OCN)

DS3-MISM (DS3)

NO-CONFIG (EQPT)

SSM-STU (TRUNK)

ETH-LINKLOSS (NE)

OCHNC-INC (OCHNC-CONN)

SSM-TNC (BITS)

EXERCISE-RING-FAIL (OCN)

OCHTERM-INC (OCH-TERM)

SSM-TNC (NE-SREF)

EXERCISE-SPAN-FAIL (OCN)

ODUK-SD-PM (TRUNK)

SSM-TNC (TRUNK)

FAILTOSW (2R)

ODUK-SF-PM (TRUNK)

STS-SQUELCH-L (OCN)

FAILTOSW (EQPT)

OOU-TPT (STSTRM)

SW-MISMATCH (EQPT)

FAILTOSW (ESCON)

OOU-TPT (VT-TERM)

SWTOPRI (EXT-SREF)

FAILTOSW (FC)

OPEN-SLOT (EQPT)

SWTOPRI (NE-SREF)

FAILTOSW (GE)

OSRION (AOTS)

SWTOSEC (EXT-SREF)

FAILTOSW (ISC)

OSRION (OTS)

SWTOSEC (NE-SREF)

FAILTOSW (OCN)

OTUK-SD (TRUNK)

SWTOTHIRD (EXT-SREF)

FAILTOSW (TRUNK)

OTUK-SF (TRUNK)

SWTOTHIRD (NE-SREF)

FAILTOSW-PATH (STSMON)

OUT-OF-SYNC (ISC)

SYNC-FREQ (BITS)

FAILTOSW-PATH (VT-MON)

PARAM-MISM (AOTS)

SYNC-FREQ (DS1)

FAILTOSWR (OCN)

PARAM-MISM (OCH)

SYNC-FREQ (E1)

FAILTOSWS (OCN)

PARAM-MISM (OMS)

SYNC-FREQ (OCN)

FDI (OCH)

PARAM-MISM (OTS)

SYNC-FREQ (TRUNK)

FE-AIS (DS3)

PDI-P (STSMON)

TEMP-MISM (NE)

FEC-MISM (TRUNK)

PDI-P (STSTRM)

TRAIL-SIGNAL-FAIL (TRUNK)

FE-DS1-MULTLOS (DS3)

PMI (OMS)

TRAIL-SIGNAL-FAIL (OCH)

FE-DS1-NSA (DS3)

PMI (OTS)

TX-RAI (DS1)

FE-DS1-SA (DS3)

PORT-MISMATCH (FCMR)

TX-RAI (DS3)

FE-DS1-SNGLLOS (DS3)

RAI (DS1)

TX-RAI (E1)

FE-DS3-NSA (DS3)

RAI (DS3)

UNC-WORD (TRUNK)

FE-DS3-SA (DS3)

RAI (E1)

VCG-DEG (VCG)

FE-EQPT-NSA (DS3)

RING-SW-EAST (OCN)

VCG-DOWN (VCG)

FE-FRCDWKSWBK-SPAN (OCN)

RING-SW-WEST (OCN)

VOLT-MISM (PWR)

FE-FRCDWKSWPR-RING (OCN)

ROLL (STSMON)

VT-SQUELCH-L (OCN)

FE-FRCDWKSWPR-SPAN (OCN)

ROLL (STSTRM)

WKSWPR (2R)

FE-IDLE (DS3)

ROLL (VT-MON)

WKSWPR (EQPT)

FE-LOCKOUTOFPR-SPAN (OCN)

ROLL-PEND (STSMON)

WKSWPR (ESCON)

FE-LOF (DS3)

ROLL-PEND (VT-MON)

WKSWPR (FC)

FE-LOS (DS3)

RPRW (LOGFAC)

WKSWPR (GE)

FE-MANWKSWBK-SPAN (OCN)

RPRW (ML1000)

WKSWPR (ISC)

FE-MANWKSWPR-RING (OCN)

RPRW (ML100T)

WKSWPR (OCN)

FE-MANWKSWPR-SPAN (OCN)

RPRW (MLFX)

WKSWPR (STSMON)

FORCED-REQ (STSMON)

RUNCFG-SAVENEED (EQPT)

WKSWPR (VT-MON)

FORCED-REQ (EQPT)

SD (DS1)

WTR (2R)

FORCED-REQ (VT-MON)

SD (DS3)

WTR (EQPT)

FORCED-REQ-RING (OCN)

SD (E1)

WTR (ESCON)

FORCED-REQ-SPAN (2R)

SD (TRUNK)

WTR (FC)

FORCED-REQ-SPAN (ESCON)

SD-L (EC1)

WTR (GE)

FORCED-REQ-SPAN (FC)

SD-L (OCN)

WTR (ISC)

FORCED-REQ-SPAN (GE)

SD-L (TRUNK)

WTR (OCN)

FORCED-REQ-SPAN (ISC)

SD-P (STSMON)

WTR (STSMON)

FORCED-REQ-SPAN (OCN)

SD-P (STSTRM)

WTR (TRUNK)

FORCED-REQ-SPAN (TRUNK)

SD-V (VT-MON)

WTR (VT-MON)

FRCDSWTOINT (NE-SREF)


2.1.5  NR Conditions

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

Table 2-5 ONS 15454 NR Conditions List 

AIS (BITS)

ERFI-P-CONN (STSMON)

OTUK-BDI (TRUNK)

AIS (DS1)

ERFI-P-CONN (STSTRM)

RFI (TRUNK)

AIS (DS3)

ERFI-P-PAYLD (STSMON)

RFI-L (EC1)

AIS (E1)

ERFI-P-PAYLD (STSTRM)

RFI-L (OCN)

AIS (FUDC)

ERFI-P-SRVR (STSMON)

RFI-L (TRUNK)

AIS (MSUDC)

ERFI-P-SRVR (STSTRM)

RFI-P (STSMON)

AIS (TRUNK)

ODUK-1-AIS-PM (TRUNK)

RFI-P (STSTRM)

AIS-L (EC1)

ODUK-2-AIS-PM (TRUNK)

RFI-V (VT-MON)

AIS-L (OCN)

ODUK-3-AIS-PM (TRUNK)

RFI-V (VT-TERM)

AIS-L (TRUNK)

ODUK-4-AIS-PM (TRUNK)

ROLL-PEND (STSTRM)

AIS-P (STSMON)

ODUK-AIS-PM (TRUNK)

TX-AIS (DS1)

AIS-P (STSTRM)

ODUK-BDI-PM (TRUNK)

TX-AIS (DS3)

AIS-V (VT-MON)

ODUK-LCK-PM (TRUNK)

TX-AIS (E1)

AIS-V (VT-TERM)

ODUK-OCI-PM (TRUNK)

TX-LOF (DS1)

AUTOSW-AIS (STSMON)

OTUK-AIS (TRUNK)

TX-LOF (E1)

AUTOSW-AIS (VT-MON)


2.2  Alarms and Conditions Listed By Alphabetical Entry

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

Table 2-6 ONS 15454 Alarm and Condition Alphabetical List 

AIS (BITS)

GFP-LFD (FCMR)

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

AIS (DS1)

GFP-LFD (GFP-FAC)

PORT-FAIL (OCH)

AIS (DS3)

GFP-LFD (LOGFAC)

PORT-MISMATCH (FCMR)

AIS (E1)

GFP-LFD (ML1000)

PRC-DUPID (OCN)

AIS (FUDC)

GFP-LFD (ML100T)

PROTNA (EQPT)

AIS (MSUDC)

GFP-LFD (MLFX)

PROV-MISMATCH (PPM)

AIS (TRUNK)

GFP-NO-BUFFERS (FCMR)

PROV-MISMATCH (TRUNK)

AIS-L (EC1)

GFP-NO-BUFFERS (GFP-FAC)

PTIM (TRUNK)

AIS-L (OCN)

GFP-UP-MISMATCH (CE1000)

PWR-FAIL-A (EQPT)

AIS-L (TRUNK)

GFP-UP-MISMATCH (CE100T)

PWR-FAIL-B (EQPT)

AIS-P (STSMON)

GFP-UP-MISMATCH (FCMR)

PWR-FAIL-RET-A (EQPT)

AIS-P (STSTRM)

GFP-UP-MISMATCH (GFP-FAC)

PWR-FAIL-RET-B (EQPT)

AIS-V (VT-MON)

GFP-UP-MISMATCH (LOGFAC)

RAI (DS1)

AIS-V (VT-TERM)

GFP-UP-MISMATCH (ML1000)

RAI (DS3)

ALS (2R)

GFP-UP-MISMATCH (ML100T)

RAI (E1)

ALS (AOTS)

GFP-UP-MISMATCH (MLFX)

RCVR-MISS (DS1)

ALS (ESCON)

HELLO (OCN)

RCVR-MISS (E1)

ALS (FC)

HELLO (TRUNK)

RFI (TRUNK)

ALS (GE)

HIBATVG (PWR)

RFI-L (EC1)

ALS (ISC)

HI-CCVOLT (BITS)

RFI-L (OCN)

ALS (OCN)

HI-LASERBIAS (2R)

RFI-L (TRUNK)

ALS (TRUNK)

HI-LASERBIAS (EQPT)

RFI-P (STSMON)

AMPLI-INIT (AOTS)

HI-LASERBIAS (ESCON)

RFI-P (STSTRM)

APC-CORRECTION-SKIPPED (AOTS)

HI-LASERBIAS (FC)

RFI-V (VT-MON)

APC-CORRECTION-SKIPPED (OCH)

HI-LASERBIAS (GE)

RFI-V (VT-TERM)

APC-CORRECTION-SKIPPED (OMS)

HI-LASERBIAS (ISC)

RING-ID-MIS (OCN)

APC-CORRECTION-SKIPPED (OTS)

HI-LASERBIAS (OCN)

RING-ID-MIS (OSC-RING)

APC-DISABLED (NE)

HI-LASERBIAS (PPM)

RING-MISMATCH (OCN)

APC-END (NE)

HI-LASERTEMP (EQPT)

RING-SW-EAST (OCN)

APC-OUT-OF-RANGE (AOTS)

HI-LASERTEMP (OCN)

RING-SW-WEST (OCN)

APC-OUT-OF-RANGE (OCH)

HI-LASERTEMP (PPM)

ROLL (STSMON)

APC-OUT-OF-RANGE (OMS)

HI-RXPOWER (2R)

ROLL (STSTRM)

APC-OUT-OF-RANGE (OTS)

HI-RXPOWER (ESCON)

ROLL (VT-MON)

APSB (OCN)

HI-RXPOWER (FC)

ROLL-PEND (STSMON)

APSCDFLTK (OCN)

HI-RXPOWER (GE)

ROLL-PEND (STSTRM)

APSC-IMP (OCN)

HI-RXPOWER (ISC)

ROLL-PEND (VT-MON)

APSCINCON (OCN)

HI-RXPOWER (OCN)

RPRW (LOGFAC)

APSCM (OCN)

HITEMP (EQPT)

RPRW (ML1000)

APSCNMIS (OCN)

HITEMP (NE)

RPRW (ML100T)

APSIMP (OCN)

HI-TXPOWER (2R)

RPRW (MLFX)

APS-INV-PRIM (OCN)

HI-TXPOWER (EQPT)

RUNCFG-SAVENEED (EQPT)

APSMM (OCN)

HI-TXPOWER (ESCON)

SD (DS1)

APS-PRIM-FAC (OCN)

HI-TXPOWER (FC)

SD (DS3)

APS-PRIM-SEC-MISM (OCN)

HI-TXPOWER (GE)

SD (E1)

AS-CMD (2R)

HI-TXPOWER (ISC)

SD (TRUNK)

AS-CMD (AOTS)

HI-TXPOWER (OCN)

SD-L (EC1)

AS-CMD (BPLANE)

HI-TXPOWER (PPM)

SD-L (OCN)

AS-CMD (CE1000)

HLDOVRSYNC (NE-SREF)

SD-L (TRUNK)

AS-CMD (CE100T)

I-HITEMP (NE)

SD-P (STSMON)

AS-CMD (DS1)

IMPROPRMVL (EQPT)

SD-P (STSTRM)

AS-CMD (DS3)

IMPROPRMVL (PPM)

SD-V (VT-MON)

AS-CMD (E1)

INC-ISD (DS3)

SD-V (VT-TERM)

AS-CMD (E1000F)

INHSWPR (EQPT)

SF (DS1)

AS-CMD (E100T)

INHSWWKG (EQPT)

SF (DS3)

AS-CMD (EC1)

INTRUSION-PSWD (NE)

SF (E1)

AS-CMD (EQPT)

INVMACADR (AIP)

SF (TRUNK)

AS-CMD (ESCON)

IOSCFGCOPY (EQPT)

SF-L (EC1)

AS-CMD (FC)

ISIS-ADJ-FAIL (OCN)

SF-L (OCN)

AS-CMD (FCMR)

KB-PASSTHR (OCN)

SF-L (TRUNK)

AS-CMD (G1000)

KBYTE-APS-CHANNEL-FAILURE (OCN)

SF-P (STSMON)

AS-CMD (GE)

LAN-POL-REV (NE)

SF-P (STSTRM)

AS-CMD (GFP-FAC)

LASER-APR (AOTS)

SFTWDOWN (EQPT)

AS-CMD (ISC)

LASERBIAS-DEG (AOTS)

SF-V (VT-MON)

AS-CMD (LOGFAC)

LASERBIAS-DEG (OTS)

SF-V (VT-TERM)

AS-CMD (ML1000)

LASERBIAS-FAIL (AOTS)

SHELF-COMM-FAIL (SHELF)

AS-CMD (ML100T)

LASEREOL (OCN)

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

AS-CMD (MLFX)

LASERTEMP-DEG (AOTS)

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

AS-CMD (NE)

LCAS-CRC (STSTRM)

SHUTTER-OPEN (OTS)

AS-CMD (OCH)

LCAS-CRC (VT-TERM)

SIGLOSS (ESCON)

AS-CMD (OCN)

LCAS-RX-FAIL (STSTRM)

SIGLOSS (FC)

AS-CMD (OMS)

LCAS-RX-FAIL (VT-TERM)

SIGLOSS (FCMR)

AS-CMD (OTS)

LCAS-TX-ADD (STSTRM)

SIGLOSS (GE)

AS-CMD (PPM)

LCAS-TX-ADD (VT-TERM)

SIGLOSS (ISC)

AS-CMD (PWR)

LCAS-TX-DNU (STSTRM)

SIGLOSS (TRUNK)

AS-CMD (SHELF)

LCAS-TX-DNU (VT-TERM)

SNTP-HOST (NE)

AS-CMD (TRUNK)

LKOUTPR-S (OCN)

SPANLENGTH-OUT-OF-RANGE (OTS)

AS-MT (2R)

LOA (VCG)

SPAN-NOT-MEASURED (OTS)

AS-MT (AOTS)

LOCKOUT-REQ (2R)

SPAN-SW-EAST (OCN)

AS-MT (CE1000)

LOCKOUT-REQ (EQPT)

SPAN-SW-WEST (OCN)

AS-MT (CE100T)

LOCKOUT-REQ (ESCON)

SQM (STSTRM)

AS-MT (DS1)

LOCKOUT-REQ (FC)

SQM (VT-TERM)

AS-MT (DS3)

LOCKOUT-REQ (GE)

SQUELCH (OCN)

AS-MT (E1)

LOCKOUT-REQ (ISC)

SQUELCHED (ESCON)

AS-MT (EC1)

LOCKOUT-REQ (OCN)

SQUELCHED (2R)

AS-MT (EQPT)

LOCKOUT-REQ (STSMON)

SQUELCHED (FC)

AS-MT (ESCON)

LOCKOUT-REQ (TRUNK)

SQUELCHED (GE)

AS-MT (FC)

LOCKOUT-REQ (VT-MON)

SQUELCHED (ISC)

AS-MT (FCMR)

LOF (BITS)

SQUELCHED (OCN)

AS-MT (G1000)

LOF (DS1)

SQUELCHED (TRUNK)

AS-MT (GE)

LOF (DS3)

SSM-DUS (BITS)

AS-MT (GFP-FAC)

LOF (E1)

SSM-DUS (DS1)

AS-MT (ISC)

LOF (EC1)

SSM-DUS (E1)

AS-MT (LOGFAC)

LOF (OCN)

SSM-DUS (OCN)

AS-MT (ML1000)

LOF (STSTRM)

SSM-DUS (TRUNK)

AS-MT (ML100T)

LOF (TRUNK)

SSM-FAIL (BITS)

AS-MT (MLFX)

LO-LASERBIAS (EQPT)

SSM-FAIL (DS1)

AS-MT (OCH)

LO-LASERBIAS (OCN)

SSM-FAIL (E1)

AS-MT (OCN)

LO-LASERBIAS (PPM)

SSM-FAIL (OCN)

AS-MT (OMS)

LO-LASERTEMP (EQPT)

SSM-FAIL (TRUNK)

AS-MT (OTS)

LO-LASERTEMP (OCN)

SSM-LNC (BITS)

AS-MT (PPM)

LO-LASERTEMP (PPM)

SSM-LNC (NE-SREF)

AS-MT (SHELF)

LOM (STSMON)

SSM-LNC (TRUNK)

AS-MT (TRUNK)

LOM (STSTRM)

SSM-OFF (BITS)

AS-MT-OOG (STSTRM)

LOM (TRUNK)

SSM-OFF (DS1)

AS-MT-OOG (VT-TERM)

LOM (VT-TERM)

SSM-OFF (E1)

AUD-LOG-LOSS (NE)

LOP-P (STSMON)

SSM-OFF (OCN)

AUD-LOG-LOW (NE)

LOP-P (STSTRM)

SSM-OFF (TRUNK)

AUTOLSROFF (OCN)

LOP-V (VT-MON)

SSM-PRC (BITS)

AUTORESET (EQPT)

LOP-V (VT-TERM)

SSM-PRC (NE-SREF)

AUTOSW-AIS (STSMON)

LO-RXPOWER (2R)

SSM-PRC (TRUNK)

AUTOSW-AIS (VT-MON)

LO-RXPOWER (ESCON)

SSM-PRS (BITS)

AUTOSW-LOP (STSMON)

LO-RXPOWER (FC)

SSM-PRS (DS1)

AUTOSW-LOP (VT-MON)

LO-RXPOWER (GE)

SSM-PRS (E1)

AUTOSW-PDI (STSMON)

LO-RXPOWER (ISC)

SSM-PRS (NE-SREF)

AUTOSW-SDBER (STSMON)

LO-RXPOWER (OCN)

SSM-PRS (OCN)

AUTOSW-SFBER (STSMON)

LO-TXPOWER (2R)

SSM-PRS (TRUNK)

AUTOSW-UNEQ (STSMON)

LOS (2R)

SSM-RES (BITS)

AUTOSW-UNEQ (VT-MON)

LOS (BITS)

SSM-RES (DS1)

AWG-DEG (OTS)

LOS (DS1)

SSM-RES (E1)

AWG-FAIL (OTS)

LOS (DS3)

SSM-RES (NE-SREF)

AWG-OVERTEMP (OTS)

LOS (E1)

SSM-RES (OCN)

AWG-WARM-UP (OTS)

LOS (EC1)

SSM-RES (TRUNK)

BAT-FAIL (PWR)

LOS (ESCON)

SSM-SDH-TN (OCN)

BKUPMEMP (EQPT)

LOS (FUDC)

SSM-SDH-TN (TRUNK)

BLSROSYNC (OCN)

LOS (ISC)

SSM-SETS (BITS)

BLSR-SW-VER-MISM (OCN)

LOS (MSUDC)

SSM-SETS (NE-SREF)

BPV (BITS)

LOS (OCN)

SSM-SETS (TRUNK)

CARLOSS (ML1000)

LOS (OTS)

SSM-SMC (BITS)

CARLOSS (CE1000)

LOS (TRUNK)

SSM-SMC (DS1)

CARLOSS (CE100T)

LOS-O (OCH)

SSM-SMC (E1)

CARLOSS (E1000F)

LOS-O (OMS)

SSM-SMC (NE-SREF)

CARLOSS (E100T)

LOS-O (OTS)

SSM-SMC (OCN)

CARLOSS (EQPT)

LOS-P (OCH)

SSM-SMC (TRUNK)

CARLOSS (FC)

LOS-P (OMS)

SSM-ST2 (BITS)

CARLOSS (G1000)

LOS-P (OTS)

SSM-ST2 (DS1)

CARLOSS (GE)

LOS-P (TRUNK)

SSM-ST2 (E1)

CARLOSS (ISC)

LO-TXPOWER (EQPT)

SSM-ST2 (NE-SREF)

CARLOSS (LOGFAC)

LO-TXPOWER (ESCON)

SSM-ST2 (OCN)

CARLOSS (ML100T)

LO-TXPOWER (FC)

SSM-ST2 (TRUNK)

CARLOSS (MLFX)

LO-TXPOWER (GE)

SSM-ST3 (BITS)

CARLOSS (TRUNK)

LO-TXPOWER (ISC)

SSM-ST3 (DS1)

CASETEMP-DEG (AOTS)

LO-TXPOWER (OCN)

SSM-ST3 (E1)

CLDRESTART (EQPT)

LO-TXPOWER (PPM)

SSM-ST3 (NE-SREF)

COMIOXC (EQPT)

LPBKCRS (STSMON)

SSM-ST3 (OCN)

COMM-FAIL (EQPT)

LPBKCRS (STSTRM)

SSM-ST3 (TRUNK)

CONTBUS-A-18 (EQPT)

LPBKDS1FEAC-CMD (DS1)

SSM-ST3E (BITS)

CONTBUS-B-18 (EQPT)

LPBKDS3FEAC (DS3)

SSM-ST3E (DS1)

CONTBUS-DISABLED (EQPT)

LPBKDS3FEAC-CMD (DS3)

SSM-ST3E (E1)

CONTBUS-IO-A (EQPT)

LPBKFACILITY (CE1000)

SSM-ST3E (NE-SREF)

CONTBUS-IO-B (EQPT)

LPBKFACILITY (CE100T)

SSM-ST3E (OCN)

CTNEQPT-MISMATCH (EQPT)

LPBKFACILITY (DS1)

SSM-ST3E (TRUNK)

CTNEQPT-PBPROT (EQPT)

LPBKFACILITY (DS3)

SSM-ST4 (BITS)

CTNEQPT-PBWORK (EQPT)

LPBKFACILITY (E1)

SSM-ST4 (DS1)

DATAFLT (NE)

LPBKFACILITY (EC1)

SSM-ST4 (E1)

DBOSYNC (NE)

LPBKFACILITY (ESCON)

SSM-ST4 (NE-SREF)

DS3-MISM (DS3)

LPBKFACILITY (FC)

SSM-ST4 (OCN)

DSP-COMM-FAIL (TRUNK)

LPBKFACILITY (FCMR)

SSM-ST4 (TRUNK)

DSP-FAIL (TRUNK)

LPBKFACILITY (G1000)

SSM-STU (BITS)

DUP-IPADDR (NE)

LPBKFACILITY (GE)

SSM-STU (DS1)

DUP-NODENAME (NE)

LPBKFACILITY (ISC)

SSM-STU (E1)

DUP-SHELF-ID (SHELF)

LPBKFACILITY (OCN)

SSM-STU (NE-SREF)

EHIBATVG (PWR)

LPBKFACILITY (TRUNK)

SSM-STU (OCN)

ELWBATVG (PWR)

LPBKTERMINAL (CE1000)

SSM-STU (TRUNK)

ENCAP-MISMATCH-P (STSTRM)

LPBKTERMINAL (CE100T)

SSM-TNC (BITS)

EOC (OCN)

LPBKTERMINAL (DS1)

SSM-TNC (NE-SREF)

EOC (TRUNK)

LPBKTERMINAL (DS3)

SSM-TNC (TRUNK)

EOC-L (OCN)

LPBKTERMINAL (E1)

STS-SQUELCH-L (OCN)

EOC-L (TRUNK)

LPBKTERMINAL (EC1)

SW-MISMATCH (EQPT)

EQPT (AICI-AEP)

LPBKTERMINAL (ESCON)

SWMTXMOD-PROT (EQPT)

EQPT (AICI-AIE)

LPBKTERMINAL (FC)

SWMTXMOD-WORK (EQPT)

EQPT (EQPT)

LPBKTERMINAL (FCMR)

SWTOPRI (EXT-SREF)

EQPT (PPM)

LPBKTERMINAL (G1000)

SWTOPRI (NE-SREF)

EQPT-DIAG (EQPT)

LPBKTERMINAL (GE)

SWTOSEC (EXT-SREF)

EQPT-MISS (FAN)

LPBKTERMINAL (ISC)

SWTOSEC (NE-SREF)

ERFI-P-CONN (STSMON)

LPBKTERMINAL (OCN)

SWTOTHIRD (EXT-SREF)

ERFI-P-CONN (STSTRM)

LPBKTERMINAL (TRUNK)

SWTOTHIRD (NE-SREF)

ERFI-P-PAYLD (STSMON)

LWBATVG (PWR)

SYNC-FREQ (BITS)

ERFI-P-PAYLD (STSTRM)

MAN-REQ (EQPT)

SYNC-FREQ (DS1)

ERFI-P-SRVR (STSMON)

MAN-REQ (STSMON)

SYNC-FREQ (E1)

ERFI-P-SRVR (STSTRM)

MAN-REQ (VT-MON)

SYNC-FREQ (OCN)

ERROR-CONFIG (EQPT)

MANRESET (EQPT)

SYNC-FREQ (TRUNK)

ETH-LINKLOSS (NE)

MANSWTOINT (NE-SREF)

SYNCLOSS (FC)

E-W-MISMATCH (OCN)

MANSWTOPRI (EXT-SREF)

SYNCLOSS (FCMR)

EXCCOL (EQPT)

MANSWTOPRI (NE-SREF)

SYNCLOSS (GE)

EXERCISE-RING-FAIL (OCN)

MANSWTOSEC (EXT-SREF)

SYNCLOSS (ISC)

EXERCISE-SPAN-FAIL (OCN)

MANSWTOSEC (NE-SREF)

SYNCLOSS (TRUNK)

EXT (ENVALRM)

MANSWTOTHIRD (EXT-SREF)

SYNCPRI (EXT-SREF)

EXTRA-TRAF-PREEMPT (OCN)

MANSWTOTHIRD (NE-SREF)

SYNCPRI (NE-SREF)

FAILTOSW (2R)

MANUAL-REQ-RING (OCN)

SYNCSEC (EXT-SREF)

FAILTOSW (EQPT)

MANUAL-REQ-SPAN (2R)

SYNCSEC (NE-SREF)

FAILTOSW (ESCON)

MANUAL-REQ-SPAN (ESCON)

SYNCTHIRD (EXT-SREF)

FAILTOSW (FC)

MANUAL-REQ-SPAN (FC)

SYNCTHIRD (NE-SREF)

FAILTOSW (GE)

MANUAL-REQ-SPAN (GE)

SYSBOOT (NE)

FAILTOSW (ISC)

MANUAL-REQ-SPAN (ISC)

TEMP-MISM (NE)

FAILTOSW (OCN)

MANUAL-REQ-SPAN (OCN)

TIM (OCN)

FAILTOSW (TRUNK)

MANUAL-REQ-SPAN (TRUNK)

TIM (TRUNK)

FAILTOSW-PATH (STSMON)

MEA (AIP)

TIM-MON (OCN)

FAILTOSW-PATH (VT-MON)

MEA (BIC)

TIM-MON (TRUNK)

FAILTOSWR (OCN)

MEA (EQPT)

TIM-P (STSMON)

FAILTOSWS (OCN)

MEA (FAN)

TIM-P (STSTRM)

FAN (FAN)

MEA (PPM)

TIM-S (EC1)

FC-NO-CREDITS (FC)

MEA (SHELF)

TIM-S (OCN)

FC-NO-CREDITS (FCMR)

MEM-GONE (EQPT)

TIM-V (VT-TERM)

FC-NO-CREDITS (TRUNK)

MEM-LOW (EQPT)

TPTFAIL (CE1000)

FDI (OCH)

MFGMEM (AICI-AEP)

TPTFAIL (CE100T)

FDI (OMS)

MFGMEM (AICI-AIE)

TPTFAIL (FCMR)

FDI (OTS)

MFGMEM (AIP)

TPTFAIL (G1000)

FE-AIS (DS3)

MFGMEM (BPLANE)

TPTFAIL (LOGFAC)

FEC-MISM (TRUNK)

MFGMEM (FAN)

TPTFAIL (ML1000)

FE-DS1-MULTLOS (DS3)

MFGMEM (PPM)

TPTFAIL (ML100T)

FE-DS1-NSA (DS3)

NO-CONFIG (EQPT)

TPTFAIL (MLFX)

FE-DS1-SA (DS3)

OCHNC-INC (OCHNC-CONN)

TRAIL-SIGNAL-FAIL (TRUNK)

FE-DS1-SNGLLOS (DS3)

OCHTERM-INC (OCH-TERM)

TRAIL-SIGNAL-FAIL (OCH)

FE-DS3-NSA (DS3)

ODUK-1-AIS-PM (TRUNK)

TRMT (DS1)

FE-DS3-SA (DS3)

ODUK-2-AIS-PM (TRUNK)

TRMT (E1)

FE-EQPT-NSA (DS3)

ODUK-3-AIS-PM (TRUNK)

TRMT-MISS (DS1)

FE-FRCDWKSWBK-SPAN (OCN)

ODUK-4-AIS-PM (TRUNK)

TRMT-MISS (E1)

FE-FRCDWKSWPR-RING (OCN)

ODUK-AIS-PM (TRUNK)

TX-AIS (DS1)

FE-FRCDWKSWPR-SPAN (OCN)

ODUK-BDI-PM (TRUNK)

TX-AIS (DS3)

FE-IDLE (DS3)

ODUK-LCK-PM (TRUNK)

TX-AIS (E1)

FE-LOCKOUTOFPR-SPAN (OCN)

ODUK-OCI-PM (TRUNK)

TX-LOF (DS1)

FE-LOF (DS3)

ODUK-SD-PM (TRUNK)

TX-LOF (E1)

FE-LOS (DS3)

ODUK-SF-PM (TRUNK)

TX-RAI (DS1)

FE-MANWKSWBK-SPAN (OCN)

ODUK-TIM-PM (TRUNK)

TX-RAI (DS3)

FE-MANWKSWPR-RING (OCN)

OOU-TPT (STSTRM)

TX-RAI (E1)

FE-MANWKSWPR-SPAN (OCN)

OOU-TPT (VT-TERM)

UNC-WORD (TRUNK)

FEPRLF (OCN)

OPEN-SLOT (EQPT)

UNEQ-P (STSMON)

FIBERTEMP-DEG (AOTS)

OPTNTWMIS (NE)

UNEQ-P (STSTRM)

FORCED-REQ (STSMON)

OPWR-HDEG (AOTS)

UNEQ-V (VT-MON)

FORCED-REQ (EQPT)

OPWR-HDEG (OCH)

UNEQ-V (VT-TERM)

FORCED-REQ (VT-MON)

OPWR-HDEG (OMS)

UNREACHABLE-TARGET-POWER (OCH)

FORCED-REQ-RING (OCN)

OPWR-HDEG (OTS)

UT-COMM-FAIL (TRUNK)

FORCED-REQ-SPAN (2R)

OPWR-HFAIL (AOTS)

UT-FAIL (TRUNK)

FORCED-REQ-SPAN (ESCON)

OPWR-HFAIL (OCH)

VCG-DEG (VCG)

FORCED-REQ-SPAN (FC)

OPWR-HFAIL (OMS)

VCG-DOWN (VCG)

FORCED-REQ-SPAN (GE)

OPWR-HFAIL (OTS)

VOA-HDEG (AOTS)

FORCED-REQ-SPAN (ISC)

OPWR-LDEG (AOTS)

VOA-HDEG (OCH)

FORCED-REQ-SPAN (OCN)

OPWR-LDEG (OCH)

VOA-HDEG (OMS)

FORCED-REQ-SPAN (TRUNK)

OPWR-LDEG (OMS)

VOA-HDEG (OTS)

FRCDSWTOINT (NE-SREF)

OPWR-LDEG (OTS)

VOA-HFAIL (AOTS)

FRCDSWTOPRI (EXT-SREF)

OPWR-LFAIL (AOTS)

VOA-HFAIL (OCH)

FRCDSWTOPRI (NE-SREF)

OPWR-LFAIL (OCH)

VOA-HFAIL (OMS)

FRCDSWTOSEC (EXT-SREF)

OPWR-LFAIL (OMS)

VOA-HFAIL (OTS)

FRCDSWTOSEC (NE-SREF)

OPWR-LFAIL (OTS)

VOA-LDEG (AOTS)

FRCDSWTOTHIRD (EXT-SREF)

OSRION (AOTS)

VOA-LDEG (OCH)

FRCDSWTOTHIRD (NE-SREF)

OSRION (OTS)

VOA-LDEG (OMS)

FRNGSYNC (NE-SREF)

OTUK-AIS (TRUNK)

VOA-LDEG (OTS)

FSTSYNC (NE-SREF)

OTUK-BDI (TRUNK)

VOA-LFAIL (AOTS)

FULLPASSTHR-BI (OCN)

OTUK-IAE (TRUNK)

VOA-LFAIL (OCH)

GAIN-HDEG (AOTS)

OTUK-LOF (TRUNK)

VOA-LFAIL (OMS)

GAIN-HFAIL (AOTS)

OTUK-SD (TRUNK)

VOA-LFAIL (OTS)

GAIN-LDEG (AOTS)

OTUK-SF (TRUNK)

VOLT-MISM (PWR)

GAIN-LFAIL (AOTS)

OTUK-TIM (TRUNK)

VT-SQUELCH-L (OCN)

GCC-EOC (TRUNK)

OUT-OF-SYNC (FC)

WKSWPR (2R)

GE-OOSYNC (FC)

OUT-OF-SYNC (GE)

WKSWPR (EQPT)

GE-OOSYNC (GE)

OUT-OF-SYNC (ISC)

WKSWPR (ESCON)

GE-OOSYNC (ISC)

OUT-OF-SYNC (TRUNK)

WKSWPR (FC)

GE-OOSYNC (TRUNK)

PARAM-MISM (AOTS)

WKSWPR (GE)

GFP-CSF (CE1000)

PARAM-MISM (OCH)

WKSWPR (ISC)

GFP-CSF (CE100T)

PARAM-MISM (OMS)

WKSWPR (OCN)

GFP-CSF (FCMR)

PARAM-MISM (OTS)

WKSWPR (STSMON)

GFP-CSF (GFP-FAC)

PDI-P (STSMON)

WKSWPR (VT-MON)

GFP-CSF (LOGFAC)

PDI-P (STSTRM)

WTR (2R)

GFP-CSF (ML100T)

PEER-NORESPONSE (EQPT)

WTR (EQPT)

GFP-CSF (ML1000)

PLM-P (STSMON)

WTR (ESCON)

GFP-CSF (MLFX)

PLM-P (STSTRM)

WTR (FC)

GFP-DE-MISMATCH (FCMR)

PLM-V (VT-TERM)

WTR (GE)

GFP-DE-MISMATCH (GFP-FAC)

PMI (OCH)

WTR (ISC)

GFP-EX-MISMATCH (CE1000)

PMI (OMS)

WTR (OCN)

GFP-EX-MISMATCH (FCMR)

PMI (OTS)

WTR (STSMON)

GFP-EX-MISMATCH (GFP-FAC)

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

WTR (TRUNK)

GFP-LFD (CE1000)

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

WTR (VT-MON)

GFP-LFD (CE100T)

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

WVL-MISMATCH (TRUNK)


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 can appear in multiple entries. It can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (OC-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both OCN: LOS and OTN: LOS appear in the list (as well as the other objects).

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


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


Table 2-7 Alarm Logical Object Type Definitions 

Logical Object
Definition

2R

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

AICI-AEP

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

AICI-AIE

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

AOTS

Amplified optical transport section. For information about AOTS alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

BIC

Backplane interface connector.

BITS

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

BPLANE

The backplane.

CE100T

CE-100T-8 card.

DS1

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

DS3

A DS-3 line on a DS3-12, DS3N-12, DS3-12E, DS3XM-6, DS3XM-12, DS3/EC1-48 card.

E1

An E1 line on a DS1/E1-56 card.

E1000F

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

E100T

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

EC1

Any EC-1 port (including EC1-12 card ports).

ENVALRM

An environmental alarm port.

EQPT

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

ESCON

Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G. For more information about ESCON alarms, refer to the "Alarm Troubleshooting" chapter in the  Cisco ONS 15454 DWDM Troubleshooting Guide.

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. For more information about FC alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

FCMR

An FC_MR-4 Fibre Channel card.

FUDC

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

G1000

A G-Series Ethernet card.

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 TXPP_MR_2.5G or TXP_MR_2.5G cards. For more information about ISC alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

LOGFAC

The LOGFAC object is not used in this platform in this release.

ML1000

An ML1000 Ethernet card (ML1000-2).

ML100T

An ML100 Ethernet card (ML100T-12).

MLFX

An ML100X-8 Ethernet card.

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 multiplexing (DWDM) cards. For more information about OCH alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

OCHNC-CONN

The optical channel network connection, referring to DWDM cards. For more information about OCHNC-CONN alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

OCN

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

OMS

Optical multiplex section.

OSC-RING

Optical service channel ring. For more information about OSC-RING alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

OTS

Optical transport section. For more information about OTS alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

PPM

Pluggable port module (PPM), referring to MXP and TXP cards. For more information about PPM alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

PWR

Power equipment.

STSMON

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

Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of STSMON, if available, should be changed to the same severity as the customized severity for a specific STS alarm.

STSTRM

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

Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of STSTRM, if available, should be changed to the same severity as the customized severity for a specific STS alarm.

TRUNK

The optical or DWDM card carrying the high-speed signal; referring to MXP or TXP cards. For more information about TRUNK alarms, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.

VCG

A virtual concatenation group of VTs.

VT-MON

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

Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of VT-MON, if available, should be changed to the same severity as the customized severity for a specific VT alarm.

VT-TERM

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

Note The network element reports alarms or conditions on ingress ports of the card. Alarms detected at the internal ports (TERM side) will be ingress mapped to the MON side. The alarm profile entities of VT-TERM, if available, should be changed to the same severity as the customized severity for a specific VT alarm.


2.4  Alarm List by Logical Object Type

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


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



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


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

2R: ALS (NA)

EXT-SREF: SWTOTHIRD (NA)

OCN: PRC-DUPID (MJ)

2R: AS-CMD (NA)

EXT-SREF: SYNCPRI (MN)

OCN: RFI-L (NR)

2R: AS-MT (NA)

EXT-SREF: SYNCSEC (MN)

OCN: RING-ID-MIS (MJ)

2R: FAILTOSW (NA)

EXT-SREF: SYNCTHIRD (MN)

OCN: RING-MISMATCH (MJ)

2R: FORCED-REQ-SPAN (NA)

FAN: EQPT-MISS (CR)

OCN: RING-SW-EAST (NA)

2R: HI-LASERBIAS (MN)

FAN: FAN (CR)

OCN: RING-SW-WEST (NA)

2R: HI-RXPOWER (MN)

FAN: MEA (CR)

OCN: SD-L (NA)

2R: HI-TXPOWER (MN)

FAN: MFGMEM (CR)

OCN: SF-L (NA)

2R: LO-RXPOWER (MN)

FC: ALS (NA)

OCN: SPAN-SW-EAST (NA)

2R: LO-TXPOWER (MN)

FC: AS-CMD (NA)

OCN: SPAN-SW-WEST (NA)

2R: LOCKOUT-REQ (NA)

FC: AS-MT (NA)

OCN: SQUELCH (NA)

2R: LOS (CR)

FC: CARLOSS (MJ)

OCN: SQUELCHED (NA)

2R: MANUAL-REQ-SPAN (NA)

FC: FAILTOSW (NA)

OCN: SSM-DUS (NA)

2R: SQUELCHED (NA)

FC: FCC-NO-CREDITS (MJ)

OCN: SSM-FAIL (MN)

2R: WKSWPR (NA)

FC: FORCED-REQ-SPAN (NA)

OCN: SSM-OFF (NA)

2R: WTR (NA)

FC: GE-OOSYNC (CR)

OCN: SSM-PRS (NA)

AICI-AEP: EQPT (CR)

FC: HI-LASERBIAS (MN)

OCN: SSM-RES (NA)

AICI-AEP: MFGMEM (CR)

FC: HI-RXPOWER (MN)

OCN: SSM-SDH-TN (NA)

AICI-AIE: EQPT (CR)

FC: HI-TXPOWER (MN)

OCN: SSM-SMC (NA)

AICI-AIE: MFGMEM (CR)

FC: LO-RXPOWER (MN)

OCN: SSM-ST2 (NA)

AIP: INVMACADR (MJ)

FC: LO-TXPOWER (MN)

OCN: SSM-ST3 (NA)

AIP: MEA (CR)

FC: LOCKOUT-REQ (NA)

OCN: SSM-ST3E (NA)

AIP: MFGMEM (CR)

FC: LPBKFACILITY (NA)

OCN: SSM-ST4 (NA)

AOTS: ALS (NA)

FC: LPBKTERMINAL (NA)

OCN: SSM-STU (NA)

AOTS: AMPLI-INIT (NA)

FC: MANUAL-REQ-SPAN (NA)

OCN: STS-SQUELCH-L (NA)

AOTS: APC-CORRECTION-SKIPPED (NA)

FC: OUT-OF-SYNC (MJ)

OCN: SYNC-FREQ (NA)

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

FC: SIGLOSS (MJ)

OCN: TIM (CR)

AOTS: AS-CMD (NA)

FC: SQUELCHED (NA)

OCN: TIM-MON (MN)

AOTS: AS-MT (NA)

FC: SYNCLOSS (MJ)

OCN: TIM-S (CR)

AOTS: CASETEMP-DEG (MN)

FC: WKSWPR (NA)

OCN: VT-SQUELCH-L (NA)

AOTS: FIBERTEMP-DEG (MN)

FC: WTR (NA)

OCN: WKSWPR (NA)

AOTS: GAIN-HDEG (MN)

FCMR: AS-CMD (NA)

OCN: WTR (NA)

AOTS: GAIN-HFAIL (CR)

FCMR: AS-MT (NA)

OMS: APC-CORRECTION-SKIPPED (NA)

AOTS: GAIN-LDEG (MN)

FCMR: FC-NO-CREDITS (MJ)

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

AOTS: GAIN-LFAIL (CR)

FCMR: GFP-CSF (MJ)

OMS: AS-CMD (NA)

AOTS: LASER-APR (NA)

FCMR: GFP-DE-MISMATCH (MJ)

OMS: AS-MT (NA)

AOTS: LASERBIAS-DEG (MN)

FCMR: GFP-EX-MISMATCH (MJ)

OMS: FDI

AOTS: LASERBIAS-FAIL (MJ)

FCMR: GFP-LFD (MJ)

OMS: LOS-O (MN)

AOTS: LASERTEMP-DEG (MN)

FCMR: GFP-NO-BUFFERS (MJ)

OMS: LOS-P (CR)

AOTS: OPWR-HDEG (MN)

FCMR: GFP-UP-MISMATCH (MJ)

OMS: OPWR-HDEG (MN)

AOTS: OPWR-HFAIL (CR)

FCMR: LPBKFACILITY (NA)

OMS: OPWR-HFAIL (CR)

AOTS: OPWR-LDEG (MN)

FCMR: LPBKTERMINAL (NA)

OMS: OPWR-LDEG (MN)

AOTS: OPWR-LFAIL (CR)

FCMR: PORT-MISMATCH (NA)

OMS: OPWR-LFAIL (CR)

AOTS: OSRION (NA)

FCMR: SIGLOSS (MJ)

OMS: PARAM-MISM (NA)

AOTS: PARAM-MISM (NA)

FCMR: SYNCLOSS (MJ)

OMS: PMI (NA)

AOTS: VOA-HDEG (MN)

FCMR: TPTFAIL (MJ)

OMS: VOA-HDEG (MN)

AOTS: VOA-HFAIL (CR)

FUDC: AIS (NR)

OMS: VOA-HFAIL (CR)

AOTS: VOA-LDEG (MN)

FUDC: LOS (MN)

OMS: VOA-LDEG (MN)

AOTS: VOA-LFAIL (CR)

G1000: AS-CMD (NA)

OMS: VOA-LFAIL (CR)

BIC: MEA (CR)

G1000: AS-MT (NA)

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

BITS: AIS (NR)

G1000: CARLOSS (MJ)

OTS: APC-CORRECTION-SKIPPED (NA)

BITS: BPV (MN)

G1000: LPBKFACILITY (NA)

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

BITS: HI-CCVOLT (NA)

G1000: LPBKTERMINAL (NA)

OTS: AS-CMD (NA)

BITS: LOF (MN)

G1000: TPTFAIL (MJ)

OTS: AS-MT (NA)

BITS: LOS (MN)

GE: ALS (NA)

OTS: AWG-DEG (MN)

BITS: SSM-DUS (NA)

GE: AS-CMD (NA)

OTS: AWG-FAIL (CR)

BITS: SSM-FAIL (MN)

GE: AS-MT (NA)

OTS: AWG-OVERTEMP (CR)

BITS: SSM-LNC (NA)

GE: CARLOSS (MJ)

OTS: AWG-WARM-UP (NA)

BITS: SSM-OFF (NA)

GE: FAILTOSW (NA)

OTS: FDI

BITS: SSM-PRC (NA)

GE: FORCED-REQ-SPAN (NA)

OTS: LASERBIAS-DEG (MN)

BITS: SSM-PRS (NA)

GE: GE-OOSYNC (CR)

OTS: LOS (CR)

BITS: SSM-RES (NA)

GE: HI-LASERBIAS (MN)

OTS: LOS-O (MN)

BITS: SSM-SETS (NA)

GE: HI-RXPOWER (MN)

OTS: LOS-P (CR)

BITS: SSM-SMC (NA)

GE: HI-TXPOWER (MN)

OTS: OPWR-HDEG (MN)

BITS: SSM-ST2 (NA)

GE: LO-RXPOWER (MN)

OTS: OPWR-HFAIL (CR)

BITS: SSM-ST3 (NA)

GE: LO-TXPOWER (MN)

OTS: OPWR-LDEG (MN)

BITS: SSM-ST3E (NA)

GE: LOCKOUT-REQ (NA)

OTS: OPWR-LFAIL (CR)

BITS: SSM-ST4 (NA)

GE: LPBKFACILITY (NA)

OTS: OSRION (NA)

BITS: SSM-STU (NA)

GE: LPBKTERMINAL (NA)

OTS: PARAM-MISM (NA)

BITS: SSM-TNC (NA)

GE: MANUAL-REQ-SPAN (NA)

OTS: PMI (NA)

BITS: SYNC-FREQ (NA)

GE: OUT-OF-SYNC (MJ)

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

BPLANE: AS-CMD (NA)

GE: SIGLOSS (MJ)

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

BPLANE: MFGMEM (CR)

GE: SQUELCHED (NA)

OTS: SHUTTER-OPEN (NA)

CE1000: AS-CMD (NA)

GE: SYNCLOSS (MJ)

OTS: SPAN-NOT-MEASURED (NA)

CE1000: AS-MT (NA)

GE: WKSWPR (NA)

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

CE1000: CARLOSS (MJ)

GE: WTR (NA)

OTS: VOA-HDEG (MN)

CE1000: GFP-CSF (MJ)

GFP-FAC: AS-CMD (NA)

OTS: VOA-HFAIL (CR)

CE1000: GFP-EX-MISMATCH (MJ)

GFP-FAC: AS-MT (NA)

OTS: VOA-LDEG (MN)

CE1000: GFP-LFD (MJ)

GFP-FAC: GFP-CSF (MJ)

OTS: VOA-LFAIL (CR)

CE1000: GFP-UP-MISMATCH (MJ)

GFP-FAC: GFP-DE-MISMATCH (MJ)

PPM: AS-CMD (NA)

CE1000: LPBKFACILITY (NA)

GFP-FAC: GFP-EX-MISMATCH (MJ)

PPM: AS-MT (NA)

CE1000: LPBKTERMINAL (NA)

GFP-FAC: GFP-LFD (MJ)

PPM: EQPT (CR)

CE1000: TPTFAIL (MJ)

GFP-FAC: GFP-NO-BUFFERS (MJ)

PPM: HI-LASERBIAS (MN)

CE100T: AS-CMD (NA)

GFP-FAC: GFP-UP-MISMATCH (MJ)

PPM: HI-LASERTEMP (MN)

CE100T: AS-MT (NA)

ISC: ALS (NA)

PPM: HI-TXPOWER (MN)

CE100T: CARLOSS (MJ)

ISC: AS-CMD (NA)

PPM: IMPROPRMVL (CR)

CE100T: GFP-CSF (MJ)

ISC: AS-MT (NA)

PPM: LO-LASERBIAS (MN)

CE100T: GFP-LFD (MJ)

ISC: CARLOSS (MJ)

PPM: LO-LASERTEMP (MN)

CE100T: GFP-UP-MISMATCH (MJ)

ISC: FAILTOSW (NA)

PPM: LO-TXPOWER (MN)

CE100T: LPBKFACILITY (NA)

ISC: FORCED-REQ-SPAN (NA)

PPM: MEA (CR)

CE100T: LPBKTERMINAL (NA)

ISC: GE-OOSYNC (CR)

PPM: MFGMEM (CR)

CE100T: TPTFAIL (MJ)

ISC: HI-LASERBIAS (MN)

PPM: PROV-MISMATCH (MN)

DS1: AIS (NR)

ISC: HI-RXPOWER (MN)

PWR: AS-CMD (NA)

DS1: AS-CMD (NA)

ISC: HI-TXPOWER (MN)

PWR: BAT-FAIL (MJ)

DS1: AS-MT (NA)

ISC: LO-RXPOWER (MN)

PWR: EHIBATVG (MJ)

DS1: LOF (MJ)

ISC: LO-TXPOWER (MN)

PWR: ELWBATVG (MJ)

DS1: LOS (MJ)

ISC: LOCKOUT-REQ (NA)

PWR: HIBATVG (MJ)

DS1: LPBKDS1FEAC-CMD (NA)

ISC: LOS (CR)

PWR: LWBATVG (MJ)

DS1: LPBKFACILITY (NA)

ISC: LPBKFACILITY (NA)

PWR: VOLT-MISM (NA)

DS1: LPBKTERMINAL (NA)

ISC: LPBKTERMINAL (NA)

SHELF: AS-CMD (NA)

DS1: RAI (NA)

ISC: MANUAL-REQ-SPAN (NA)

SHELF: AS-MT (NA)

DS1: RCVR-MISS (MJ)

ISC: OUT-OF-SYNC (NA)

SHELF: DUP-SHELF-ID (MJ)

DS1: SD (NA)

ISC: SIGLOSS (MJ)

SHELF: MEA (MJ)

DS1: SF (NA)

ISC: SQUELCHED (NA)

SHELF: SHELF-COMM-FAIL (MJ)

DS1: SSM-DUS (NA)

ISC: SYNCLOSS (MJ)

STSMON: AIS-P (NR)

DS1: SSM-FAIL (MN)

ISC: WKSWPR (NA)

STSMON: AUTOSW-AIS (NR)

DS1: SSM-OFF (NA)

ISC: WTR (NA)

STSMON: AUTOSW-LOP (NA)

DS1: SSM-PRS (NA)

LOGFAC: AS-CMD (NA)

STSMON: AUTOSW-PDI (NA)

DS1: SSM-RES (NA)

LOGFAC: AS-MT (NA)

STSMON: AUTOSW-SDBER (NA)

DS1: SSM-SMC (NA)

LOGFAC: CARLOSS (MJ)

STSMON: AUTOSW-SFBER (NA)

DS1: SSM-ST2 (NA)

LOGFAC: GFP-CSF (MJ)

STSMON: AUTOSW-UNEQ (NA)

DS1: SSM-ST3 (NA)

LOGFAC: GFP-LFD (MJ)

STSMON: ERFI-P-CONN (NR)

DS1: SSM-ST3E (NA)

LOGFAC: GFP-UP-MISMATCH (MJ)

STSMON: ERFI-P-PAYLD (NR)

DS1: SSM-ST4 (NA)

LOGFAC: RPRW (NA)

STSMON: ERFI-P-SRVR (NR)

DS1: SSM-STU (NA)

LOGFAC: TPTFAIL (MJ)

STSMON: FAILTOSW-PATH (NA)

DS1: SYNC-FREQ (NA)

ML1000: AS-CMD (NA)

STSMON: FORCED-REQ (NA)

DS1: TRMT (MJ)

ML1000: AS-MT (NA)

STSMON: LOCKOUT-REQ (NA)

DS1: TRMT-MISS (MJ)

ML1000: CARLOSS (MJ)

STSMON: LOM (CR)

DS1: TX-AIS (NR)

ML1000: GFP-CSF (MJ)

STSMON: LOP-P (CR)

DS1: TX-LOF (NR)

ML1000: GFP-LFD (MJ)

STSMON: LPBKCRS (NA)

DS1: TX-RAI (NA)

ML1000: GFP-UP-MISMATCH (MJ)

STSMON: MAN-REQ (NA)

DS3: AIS (NR)

ML1000: RPRW (NA)

STSMON: PDI-P (NA)

DS3: AS-CMD (NA)

ML1000: TPTFAIL (MJ)

STSMON: PLM-P (CR)

DS3: AS-MT (NA)

ML100T: AS-CMD (NA)

STSMON: RFI-P (NR)

DS3: DS3-MISM (NA)

ML100T: AS-MT (NA)

STSMON: ROLL (NA)

DS3: FE-AIS (NA)

ML100T: CARLOSS (MJ)

STSMON: ROLL-PEND (NA)

DS3: FE-DS1-MULTLOS (NA)

ML100T: GFP-CSF (MJ)

STSMON: SD-P (NA)

DS3: FE-DS1-NSA (NA)

ML100T: GFP-LFD (MJ)

STSMON: SF-P (NA)

DS3: FE-DS1-SA (NA)

ML100T: GFP-UP-MISMATCH (MJ)

STSMON: TIM-P (MN)

DS3: FE-DS1-SNGLLOS (NA)

ML100T: RPRW (NA)

STSMON: UNEQ-P (CR)

DS3: FE-DS3-NSA (NA)

ML100T: TPTFAIL (MJ)

STSMON: WKSWPR (NA)

DS3: FE-DS3-SA (NA)

MLFX: AS-CMD (NA)

STSMON: WTR (NA)

DS3: FE-EQPT-NSA (NA)

MLFX: AS-MT (NA)

STSTRM: AIS-P (NR)

DS3: FE-IDLE (NA)

MLFX: CARLOSS (MJ)

STSTRM: AS-MT-OOG (NA)

DS3: FE-LOF (NA)

MLFX: GFP-CSF (MJ)

STSTRM: ENCAP-MISMATCH-P (CR)

DS3: FE-LOS (NA)

MLFX: GFP-LFD (MJ)

STSTRM: ERFI-P-CONN (NR)

DS3: INC-ISD (NA)

MLFX: GFP-UP-MISMATCH (MJ)

STSTRM: ERFI-P-PAYLD (NR)

DS3: LOF (CR)

MLFX: RPRW (NA)

STSTRM: ERFI-P-SRVR (NR)

DS3: LOS (CR)

MLFX: TPTFAIL (MJ)

STSTRM: LCAS-CRC (NA)

DS3: LPBKDS3FEAC (NA)

MSUDC: AIS (NR)

STSTRM: LCAS-RX-FAIL (NA)

DS3: LPBKDS3FEAC-CMD (NA)

MSUDC: LOS (MN)

STSTRM: LCAS-TX-ADD (NA)

DS3: LPBKFACILITY (NA)

NE-SREF: FRCDSWTOINT (NA)

STSTRM: LCAS-TX-DNU (NA)

DS3: LPBKTERMINAL (NA)

NE-SREF: FRCDSWTOPRI (NA)

STSTRM: LOF (CR)

DS3: RAI (NA)

NE-SREF: FRCDSWTOSEC (NA)

STSTRM: LOM (CR)

DS3: SD (NA)

NE-SREF: FRCDSWTOTHIRD (NA)

STSTRM: LOP-P (CR)

DS3: SF (NA)

NE-SREF: FRNGSYNC (NA)

STSTRM: LPBKCRS (NA)

DS3: TX-AIS (NR)

NE-SREF: FSTSYNC (NA)

STSTRM: OOU-TPT (NA)

DS3: TX-RAI (NA)

NE-SREF: HLDOVRSYNC (NA)

STSTRM: PDI-P (NA)

E1000F: AS-CMD (NA)

NE-SREF: MANSWTOINT (NA)

STSTRM: PLM-P (CR)

E1000F: CARLOSS (MJ)

NE-SREF: MANSWTOPRI (NA)

STSTRM: RFI-P (NR)

E100T: AS-CMD (NA)

NE-SREF: MANSWTOSEC (NA)

STSTRM: ROLL (NA)

E100T: CARLOSS (MJ)

NE-SREF: MANSWTOTHIRD (NA)

STSTRM: ROLL-PEND (NR)

E1: AIS (NR)

NE-SREF: SSM-LNC (NA)

STSTRM: SD-P (NA)

E1: AS-CMD (NA)

NE-SREF: SSM-PRC (NA)

STSTRM: SF-P (NA)

E1: AS-MT (NA)

NE-SREF: SSM-PRS (NA)

STSTRM: SQM (CR)

E1: LOF (MJ)

NE-SREF: SSM-RES (NA)

STSTRM: TIM-P (CR)

E1: LOS (MJ)

NE-SREF: SSM-SETS (NA)

STSTRM: UNEQ-P (CR)

E1: LPBKFACILITY (NA)

NE-SREF: SSM-SMC (NA)

TRUNK: AIS (NR)

E1: LPBKTERMINAL (NA)

NE-SREF: SSM-ST2 (NA)

TRUNK: AIS-L (NR)

E1: RAI (NA)

NE-SREF: SSM-ST3 (NA)

TRUNK: ALS (NA)

E1: RCVR-MISS (MJ)

NE-SREF: SSM-ST3E (NA)

TRUNK: AS-CMD (NA)

E1: SD (NA)

NE-SREF: SSM-ST4 (NA)

TRUNK: AS-MT (NA)

E1: SF (NA)

NE-SREF: SSM-STU (NA)

TRUNK: CARLOSS (MJ)

E1: SSM-DUS (NA)

NE-SREF: SSM-TNC (NA)

TRUNK: DSP-COMM-FAIL (MJ)

E1: SSM-FAIL (MN)

NE-SREF: SWTOPRI (NA)

TRUNK: DSP-FAIL (MJ)

E1: SSM-OFF (NA)

NE-SREF: SWTOSEC (NA)

TRUNK: EOC (MN)

E1: SSM-PRS (NA)

NE-SREF: SWTOTHIRD (NA)

TRUNK: EOC-L (MN)

E1: SSM-RES (NA)

NE-SREF: SYNCPRI (MJ)

TRUNK: FAILTOSW (NA)

E1: SSM-SMC (NA)

NE-SREF: SYNCSEC (MN)

TRUNK: FC-NO-CREDITS (MJ)

E1: SSM-ST2 (NA)

NE-SREF: SYNCTHIRD (MN)

TRUNK: FEC-MISM (NA)

E1: SSM-ST3 (NA)

NE: APC-DISABLED (NA)

TRUNK: FORCED-REQ-SPAN (NA)

E1: SSM-ST3E (NA)

NE: APC-END (NA)

TRUNK: GCC-EOC (MN)

E1: SSM-ST4 (NA)

NE: AS-CMD (NA)

TRUNK: GE-OOSYNC (CR)

E1: SSM-STU (NA)

NE: AUD-LOG-LOSS (NA)

TRUNK: HELLO (NA)

E1: SYNC-FREQ (NA)

NE: AUD-LOG-LOW (NA)

TRUNK: LOCKOUT-REQ (NA)

E1: TRMT (MJ)

NE: DATAFLT (MN)

TRUNK: LOF (CR)

E1: TRMT-MISS (MJ)

NE: DBOSYNC (MJ)

TRUNK: LOM (CR)

E1: TX-AIS (NR)

NE: DUP-IPADDR (MN)

TRUNK: LOS (CR)

E1: TX-LOF (NR)

NE: DUP-NODENAME (MN)

TRUNK: LOS-P (CR)

E1: TX-RAI (NA)

NE: ETH-LINKLOSS (NA)

TRUNK: LPBKFACILITY (NA)

EC1: AIS-L (NR)

NE: HITEMP (CR)

TRUNK: LPBKTERMINAL (NA)

EC1: AS-CMD (NA)

NE: I-HITEMP (CR)

TRUNK: MANUAL-REQ-SPAN (NA)

EC1: AS-MT (NA)

NE: INTRUSION-PSWD (NA)

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

EC1: LOF (CR)

NE: LAN-POL-REV (NA)

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

EC1: LOS (CR)

NE: OPTNTWMIS (MJ)

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

EC1: LPBKFACILITY (NA)

NE: SNTP-HOST (MN)

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

EC1: LPBKTERMINAL (NA)

NE: SYSBOOT (MJ)

TRUNK: ODUK-AIS-PM (NR)

EC1: RFI-L (NR)

NE: TEMP-MISM (NA)

TRUNK: ODUK-BDI-PM (NR)

EC1: SD-L (NA)

OCH-TERM: OCHTERM-INC (NA)

TRUNK: ODUK-LCK-PM (NR)

EC1: SF-L (NA)

OCH: APC-CORRECTION-SKIPPED (NA)

TRUNK: ODUK-OCI-PM (NR)

EC1: TIM-S (CR)

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

TRUNK: ODUK-SD-PM (NA)

ENVALRM: EXT (MN)

OCH: AS-CMD (NA)

TRUNK: ODUK-SF-PM (NA)

EQPT: AS-CMD (NA)

OCH: AS-MT (NA)

TRUNK: ODUK-TIM-PM (MJ)

EQPT: AS-MT (NA)

OCH: FDI (NA)

TRUNK: OTUK-AIS (NR)

EQPT: AUTORESET (MN)

OCH: LOS-O (MN)

TRUNK: OTUK-BDI (NR)

EQPT: BKUPMEMP (CR)

OCH: LOS-P (CR)

TRUNK: OTUK-IAE (MN)

EQPT: CARLOSS (MJ)

OCH: OPWR-HDEG (MN)

TRUNK: OTUK-LOF (CR)

EQPT: CLDRESTART (NA)

OCH: OPWR-HFAIL (CR)

TRUNK: OTUK-SD (NA)

EQPT: COMIOXC (CR)

OCH: OPWR-LDEG (MN)

TRUNK: OTUK-SF (NA)

EQPT: COMM-FAIL (MN)

OCH: OPWR-LFAIL (CR)

TRUNK: OTUK-TIM (CR)

EQPT: CONTBUS-A-18 (MN)

OCH: PARAM-MISM (NA)

TRUNK: OUT-OF-SYNC (MJ)

EQPT: CONTBUS-B-18 (MN)

OCH: PMI

TRUNK: PROV-MISMATCH (MJ)

EQPT: CONTBUS-DISABLED (CR)

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

TRUNK: PTIM (MJ)

EQPT: CONTBUS-IO-A (MN)

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

TRUNK: RFI (NR)

EQPT: CONTBUS-IO-B (MN)

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

TRUNK: RFI-L (NR)

EQPT: CTNEQPT-MISMATCH (NA)

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

TRUNK: SD (NA)

EQPT: CTNEQPT-PBPROT (CR)

OCH: PORT-FAIL (CR)

TRUNK: SD-L (NA)

EQPT: CTNEQPT-PBWORK (CR)

OCH: TRAIL-SIGNAL-FAIL (NA)

TRUNK: SF (NA)

EQPT: EQPT (CR)

OCH: UNREACHABLE-TARGET-POWER (MN)

TRUNK: SF-L (NA)

EQPT: EQPT-DIAG (CR)

OCH: VOA-HDEG (MN)

TRUNK: SIGLOSS (MJ)

EQPT: ERROR-CONFIG (MN)

OCH: VOA-HFAIL (CR)

TRUNK: SQUELCHED (NA)

EQPT: EXCCOL (MN)

OCH: VOA-LDEG (MN)

TRUNK: SSM-DUS (NA)

EQPT: FAILTOSW (NA)

OCH: VOA-LFAIL (CR)

TRUNK: SSM-FAIL (MN)

EQPT: FORCED-REQ (NA)

OCHNC-CONN: OCHNC-INC (NA)

TRUNK: SSM-LNC (NA)

EQPT: HI-LASERBIAS (MN)

OCN: AIS-L (NR)

TRUNK: SSM-OFF (NA)

EQPT: HI-LASERTEMP (MN)

OCN: ALS (NA)

TRUNK: SSM-PRC (NA)

EQPT: HI-TXPOWER (MN)

OCN: APS-INV-PRIM (MN)

TRUNK: SSM-PRS (NA)

EQPT: HITEMP (MN)

OCN: APS-PRIM-FAC (NA)

TRUNK: SSM-RES (NA)

EQPT: IMPROPRMVL (CR)

OCN: APS-PRIM-SEC-MISM (MN)

TRUNK: SSM-SDH-TN (NA)

EQPT: INHSWPR (NA)

OCN: APSB (MN)

TRUNK: SSM-SETS (NA)

EQPT: INHSWWKG (NA)

OCN: APSC-IMP (MN)

TRUNK: SSM-SMC (NA)

EQPT: IOSCFGCOPY (NA)

OCN: APSCDFLTK (MN)

TRUNK: SSM-ST2 (NA)

EQPT: LO-LASERBIAS (MN)

OCN: APSCINCON (MN)

TRUNK: SSM-ST3 (NA)

EQPT: LO-LASERTEMP (MN)

OCN: APSCM (MJ)

TRUNK: SSM-ST3E (NA)

EQPT: LO-TXPOWER (MN)

OCN: APSCNMIS (MJ)

TRUNK: SSM-ST4 (NA)

EQPT: LOCKOUT-REQ (NA)

OCN: APSIMP (MN)

TRUNK: SSM-STU (NA)

EQPT: MAN-REQ (NA)

OCN: APSMM (MN)

TRUNK: SSM-TNC (NA)

EQPT: MANRESET (NA)

OCN: AS-CMD (NA)

TRUNK: SYNC-FREQ (NA)

EQPT: MEA (CR)

OCN: AS-MT (NA)

TRUNK: SYNCLOSS (MJ)

EQPT: MEM-GONE (MJ)

OCN: AUTOLSROFF (CR)

TRUNK: TIM (CR)

EQPT: MEM-LOW (MN)

OCN: BLSR-SW-VER-MISM (MJ)

TRUNK: TIM-MON (MN)

EQPT: NO-CONFIG (NA)

OCN: BLSROSYNC (MJ)

TRUNK: TRAIL-SIGNAL-FAIL (NA)

EQPT: OPEN-SLOT (NA)

OCN: E-W-MISMATCH (MJ)

TRUNK: UNC-WORD (NA)

EQPT: PEER-NORESPONSE (MJ)

OCN: EOC (MN)

TRUNK: UT-COMM-FAIL (MJ)

EQPT: PROTNA (MN)

OCN: EOC-L (MN)

TRUNK: UT-FAIL (MJ)

EQPT: PWR-FAIL-A (MN)

OCN: EXERCISE-RING-FAIL (NA)

TRUNK: WTR (NA)

EQPT: PWR-FAIL-B (MN)

OCN: EXERCISE-SPAN-FAIL (NA)

TRUNK: WVL-MISMATCH (MJ)

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

OCN: EXTRA-TRAF-PREEMPT (MJ)

VCG: LOA (CR)

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

OCN: FAILTOSW (NA)

VCG: VCG-DEG (NA)

EQPT: RUNCFG-SAVENEED (NA)

OCN: FAILTOSWR (NA)

VCG: VCG-DOWN (NA)

EQPT: SFTWDOWN (MN)

OCN: FAILTOSWS (NA)

VT-MON: AIS-V (NR)

EQPT: SW-MISMATCH (NA)

OCN: FE-FRCDWKSWBK-SPAN (NA)

VT-MON: AUTOSW-AIS (NR)

EQPT: SWMTXMOD-PROT (CR)

OCN: FE-FRCDWKSWPR-RING (NA)

VT-MON: AUTOSW-LOP (NA)

EQPT: SWMTXMOD-WORK (CR)

OCN: FE-FRCDWKSWPR-SPAN (NA)

VT-MON: AUTOSW-UNEQ (MN)

EQPT: WKSWPR (NA)

OCN: FE-LOCKOUTOFPR-SPAN (NA)

VT-MON: FAILTOSW-PATH (NA)

EQPT: WTR (NA)

OCN: FE-MANWKSWBK-SPAN (NA)

VT-MON: FORCED-REQ (NA)

ESCON: ALS (NA)

OCN: FE-MANWKSWPR-RING (NA)

VT-MON: LOCKOUT-REQ (NA)

ESCON: AS-CMD (NA)

OCN: FE-MANWKSWPR-SPAN (NA)

VT-MON: LOP-V (MJ)

ESCON: AS-MT (NA)

OCN: FEPRLF (MN)

VT-MON: MAN-REQ (NA)

ESCON: FAILTOSW (NA)

OCN: FORCED-REQ-RING (NA)

VT-MON: RFI-V (NR)

ESCON: FORCED-REQ-SPAN (NA)

OCN: FORCED-REQ-SPAN (NA)

VT-MON: ROLL (NA)

ESCON: HI-LASERBIAS (MN)

OCN: FULLPASSTHR-BI (NA)

VT-MON: ROLL-PEND (NA)

ESCON: HI-RXPOWER (MN)

OCN: HELLO (NA)

VT-MON: SD-V (NA)

ESCON: HI-TXPOWER (MN)

OCN: HI-LASERBIAS (MN)

VT-MON: SF-V (NA)

ESCON: LO-RXPOWER (MN)

OCN: HI-LASERTEMP (MN)

VT-MON: UNEQ-V (MJ)

ESCON: LO-TXPOWER (MN)

OCN: HI-RXPOWER (MN)

VT-MON: WKSWPR (NA)

ESCON: LOCKOUT-REQ (NA)

OCN: HI-TXPOWER (MN)

VT-MON: WTR (NA)

ESCON: LOS (CR)

OCN: ISIS-ADJ-FAIL (MN)

VT-TERM: AIS-V (NR)

ESCON: LPBKFACILITY (NA)

OCN: KB-PASSTHR (NA)

VT-TERM: AS-MT-OOG (NA)

ESCON: LPBKTERMINAL (NA)

OCN: KBYTE-APS-CHANNEL-FAILURE (MN)

VT-TERM: LCAS-CRC (NA)

ESCON: MANUAL-REQ-SPAN (NA)

OCN: LASEREOL (MN)

VT-TERM: LCAS-RX-FAIL (NA)

ESCON: SIGLOSS

OCN: LKOUTPR-S (NA)

VT-TERM: LCAS-TX-ADD (NA)

ESCON: SQUELCHED (NA)

OCN: LO-LASERBIAS (MN)

VT-TERM: LCAS-TX-DNU (NA)

ESCON: WKSWPR (NA)

OCN: LO-LASERTEMP (MN)

VT-TERM: LOM (MJ)

ESCON: WTR (NA)

OCN: LO-RXPOWER (MN)

VT-TERM: LOP-V (MJ)

EXT-SREF: FRCDSWTOPRI (NA)

OCN: LO-TXPOWER (MN)

VT-TERM: OOU-TPT (NA)

EXT-SREF: FRCDSWTOSEC (NA)

OCN: LOCKOUT-REQ (NA)

VT-TERM: PLM-V (MJ)

EXT-SREF: FRCDSWTOTHIRD (NA)

OCN: LOF (CR)

VT-TERM: RFI-V (NR)

EXT-SREF: MANSWTOPRI (NA)

OCN: LOS (CR)

VT-TERM: SD-V (NA)

EXT-SREF: MANSWTOSEC (NA)

OCN: LPBKFACILITY (NA)

VT-TERM: SF-V (NA)

EXT-SREF: MANSWTOTHIRD (NA)

OCN: LPBKTERMINAL (NA)

VT-TERM: SQM (MJ)

EXT-SREF: SWTOPRI (NA)

OCN: MANUAL-REQ-RING (NA)

VT-TERM: TIM-V (MJ)

EXT-SREF: SWTOSEC (NA)

OCN: MANUAL-REQ-SPAN (NA)

VT-TERM: UNEQ-V (MJ) (CR)


2.5  Trouble Notifications

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

The ONS 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. Conditions do not necessarily require troubleshooting.

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

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


Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity and alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT value to TRUE on the NE Defaults tab. For more information about changing NE defaults, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.


2.5.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). These are described below:

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

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

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

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

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

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

2.5.4  Alarm Hierarchy

All alarm, condition, and unreported 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-CORE.

A path alarm can be demoted if a higher-ranking alarm is raised for the same object. For example, If a path trace identifier mismatch (TIM-P) is raised on a circuit path and then a loss of pointer on the path (LOP-P) is raised on the path, the LOP-P alarm stands and the TIM-P closes. The path alarm hierarchy used in the ONS 15454 system is shown in Table 2-9.

Table 2-9 Path Alarm Hierarchy 

Priority
Condition Type

Highest

AIS-P

LOP-P

UNEQ-P

Lowest

TIM-P


Facility (port) alarms also follow a hierarchy, which means that lower-ranking alarms are closed by higher-ranking alarms. The facility alarm hierarchy used in the ONS 15454 is shown in Table 2-10.

Table 2-10 Facility Alarm Hierarchy

Priority
Condition Type

Highest

LOS

LOF

AIS-L

SF-L

SD-L

RFI-L

TIM-S

AIS-P

LOP-P

SF-P

SD-P

UNEQ-P

TIM-P

Lowest

PLM-P


Near-end failures and far-end failures follow different hierarchies. Near-end failures stand according to whether they are for the entire signal (LOS, LOF), facility (AIS-L), path (AIS-P, etc.) or VT (AIS-V, etc.). The full hierarchy for near-end failures is shown in Table 2-11. This table is taken from Telcordia GR-253-CORE.

Table 2-11 Near-End Alarm Hierarchy

Priority
Condition Type

Highest

LOS

LOF

AIS-L

AIS-P1

LOP-P2

UNEQ-P

TIM-P

PLM-P

AIS-V1

LOP-V2

UNEQ-V

PLM-V

Lowest

DS-N AIS (if reported for outgoing DS-N signals)

1 Although it is not defined as a defect or failure, all-ones STS pointer relay is also higher priority than LOP-P. Similarly, all-ones VT pointer relay is higher priority than LOP-V.

2 LOP-P is also higher priority than the far-end failure RFI-P, which does not affect the detection of any near-end failures. Similarly, LOP-V is higher priority than RFI-V.


The far-end failure alarm hierarchy is shown in Table 2-12, as given in Telcordia GR-253-CORE.

Table 2-12 Far-End Alarm Hierarchy

Priority
Condition Type

Highest

RFI-L

RFI-P

Lowest

RFI-V


2.5.5  Service Effect

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

2.5.6  States

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

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

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

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

2.6  Safety Summary

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


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

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


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

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

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

Warning Class 1 laser product. Statement 1008

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

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

2.7  Alarm Procedures

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


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



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



Note When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity and alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT value to TRUE on the NE Defaults tab. For more information about changing NE defaults, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.


2.7.1  AIS

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

SONET Logical Objects: BITS, DS1, DS3, E1, FUDC, MSUDC

DWDM Logical Object: TRUNK

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

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


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


Clear the AIS Condition


Step 1 Determine whether there are alarms on the upstream nodes and equipment, especially the "LOS (OCN)" alarm on page 2-152, or if there are 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 Cisco TAC 1 800 553-2447.


2.7.2  AIS-L

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

SONET Logical Objects: EC1, OCN

DWDM Logical Object: TRUNK

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

This condition can also be raised in conjunction with the "TIM-S" alarm on page 2-223 if AIS-L is enabled.


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


Clear the AIS-L Condition


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

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


2.7.3  AIS-P

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

SONET Logical Objects: STSMON, STSTRM

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

Clear the AIS-P Condition


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

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


2.7.4  AIS-V

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

SONET Logical Objects: VT-MON, VT-TERM

The AIS VT condition means that this node is detecting AIS in the incoming VT-level path.

See the "AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits" section 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 Cisco TAC 1 800 553-2447.


2.7.5  ALS

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.6  AMPLI-INIT

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.7  APC-CORRECTION-SKIPPED

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.8  APC-DISABLED

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.9  APC-END

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.10  APC-OUT-OF-RANGE

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.11  APSB

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

SONET Logical Object: OCN

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


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

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

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


2.7.12  APSCDFLTK

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

SONET 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-53.

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-84.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide provides procedures 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 protect 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 Section DCC Terminations" procedure to ensure that section 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.7.13  APSC-IMP

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

SONET Logical Object: OCN

An Improper SONET APS Code alarm indicates three consecutive, identical frames containing:

Unused code in bits 6 through 8 of byte K2.

Codes that are irrelevant to the specific protection switching operation being requested.

Requests that are irrelevant to the ring state of the ring (such as a span protection switch request in a two-fiber ring NE).

ET code in K2 bits 6 through 8 received on the incoming span, but not sourced from the outgoing span.


Note This alarm can occur on a VT tunnel when it does not have VT circuits provisioned on it. 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.



Note The APSC-IMP alarm may be raised on a BLSR or MS-SPRing when a drop connection is part of a cross-connect loopback.



Note The APSC-IMP alarm may be momentarily raised on BLSR spans during PCA circuit creation or deletion across multiple nodes using CTC.



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

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

Clear the 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.


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.

If the K byte is invalid, the problem lies with upstream equipment and not with 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 that node's ring name 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.7.14  APSCINCON

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

SONET 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 15454, to switch the SONET signal from a working to a protect path when necessary. An inconsistent APS code occurs when three consecutive frames contain nonidentical APS bytes, which in turn 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-152, the "LOF (OCN)" alarm on page 2-138, or the "AIS" condition on page 2-34. 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.7.15  APSCM

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

SONET Logical Object: OCN

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


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

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

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

Clear the APSCM Alarm


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


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

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

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


2.7.16  APSCNMIS

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

SONET Logical Object: OCN

The APS Node ID Mismatch alarm occurs when the source node ID contained in the incoming APS channel K2 byte 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 Lockout on a BLSR Protect Span" procedure to lock out the span.

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

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


2.7.17  APSIMP

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

SONET Logical Object: OCN

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

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

Clear the APSIMP Alarm


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

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

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

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


2.7.18  APS-INV-PRIM

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

SONET 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.7.19  APSMM

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

SONET 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 at one end and unidirectional at the other. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional. APSMM can also occur if third-party equipment is provisioned as 1:N and the ONS 15454 is provisioned as 1+1.

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

Clear the APSMM Alarm


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

a. Click the Provisioning > Protection tabs.

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

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

c. Click Edit.

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

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

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

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

Step 5 Click Apply.

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


2.7.20  APS-PRIM-FAC

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

SONET Logical Object: OCN

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


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


Clear the APS-PRIM-FAC Condition


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

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


2.7.21  APS-PRIM-SEC-MISM

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

SONET Logical Object: OCN

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

Clear the APS-PRIM-SEC-MISM Alarm


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

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


2.7.22  AS-CMD

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

SONET Logical Objects: BPLANE, CE1000, CE100T, DS1, DS3, E1, E1000F, E100F, EC1, EQPT, FCMR, G1000, GFP-FAC, ML1000, ML100T, MLFX, NE, OCN, PWR

DWDM Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCH, OMS, OTS, PPM, SHELF, 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. For example, suppressing alarms on a card also suppresses alarms on its ports.


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


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 open the card view.

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

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

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

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

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

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

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

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

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

c. Click Apply.

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

a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs if you have not already done so.

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

c. Click Apply.

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


2.7.23  AS-MT

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

SONET Logical Objects: CE1000, CE100T, DS1, DS3, E1, EC1, EQPT, FCMR, G1000, GFP-FAC, ML1000, ML100T, MLFX, OCN

DWDM Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCH, OMS, OTS, PPM, SHELF, 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.

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.7.24  AS-MT-OOG

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

SONET Logical Objects: STSTRM, VT-TERM

The Alarms Suppressed on an Out-Of-Group VCAT Member condition 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 condition can be raised when a member is initially added to a group. In the IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.

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

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.7.25  AUD-LOG-LOSS

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

SONET Logical Object: NE

The Audit Trail Log Loss condition occurs when the log is 100 percent full and the oldest entries are being replaced while 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 are saved in this file. New entries 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.7.26  AUD-LOG-LOW

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

SONET 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.7.27  AUTOLSROFF

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

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

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

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

Clear the AUTOLSROFF Alarm


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

Figure 2-1 Shelf LCD Panel

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

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

Step 4 If card replacement does not clear the alarm, call Cisco TAC 1 800 553-2447 to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.


2.7.28  AUTORESET

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

SONET Logical Object: EQPT

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

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

Clear the AUTORESET Alarm


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

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

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


2.7.29  AUTOSW-AIS

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

SONET Logical Objects: STSMON, VT-MON

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


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


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

Clear the AUTOSW-AIS Condition


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

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


2.7.30  AUTOSW-LOP (STSMON)

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

SONET Logical Object: STSMON

The Automatic UPSR 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-142. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.


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


Clear the AUTOSW-LOP (STSMON) Condition


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

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


2.7.31  AUTOSW-LOP (VT-MON)

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

SONET Logical Object: VT-MON

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


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


Clear the AUTOSW-LOP (VT-MON) Condition


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 (SA) problem.


2.7.32  AUTOSW-PDI

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

SONET Logical Object: STSMON

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


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


Clear the AUTOSW-PDI Condition


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

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


2.7.33  AUTOSW-SDBER

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

Logical Object: STSMON

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


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


Clear the AUTOSW-SDBER Condition


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

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


2.7.34  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 "SF-P" condition on page 2-202 caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SF-P is resolved.


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


Clear the AUTOSW-SFBER Condition


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

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


2.7.35  AUTOSW-UNEQ (STSMON)

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

SONET Logical Object: STSMON

The Automatic UPSR Switch Caused by Unequipped condition indicates that a UNEQ alarm caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.


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


Clear the AUTOSW-UNEQ (STSMON) Condition


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

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


2.7.36  AUTOSW-UNEQ (VT-MON)

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

SONET 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. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.


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


Clear the AUTOSW-UNEQ (VT-MON) Condition


Step 1 Complete the "Clear the UNEQ-V Alarm" alarm on page 2-231 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.7.37  AWG-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.38  AWG-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.39  AWG-OVERTEMP

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.40  AWG-WARM-UP

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.41  BAT-FAIL

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

SONET Logical Object: PWR

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

Clear the BAT-FAIL Alarm


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

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

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


2.7.42  BKUPMEMP

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

SONET Logical Object: EQPT

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

Flash manager fails to format a flash partition.

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

Problem at the driver level.

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

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


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

Clear the BKUPMEMP Alarm


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

Step 2 Determine whether the active or standbyTCC2/TCC2P has the alarm.

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

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

b. Choose Reset Card from the shortcut menu.

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

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

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


2.7.43  BLSROSYNC

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

SONET Logical Object: OCN

The BLSR Out Of Synchronization alarm occurs is raised temporarily during a span upgrade, downgrade, or two-fiber to four-fiber mode upgrade and clears when the procedure is complete for all nodes on the ring. If the alarm does not clear, ensure that all maintenance procedures have completed for all nodes on the ring. If the alarm still does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 in order to report a Service-Affecting (SA) problem.

2.7.44  BLSR-SW-VER-MISM

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

SONET Logical Object: OCN

The BLSR Software Version Mismatch alarm is raised by the TCC2/TCC2P when it checks all software versions for all nodes in a ring and discovers a mismatch in versions.

Clear the BLSR-SW-VER-MISM Alarm


Step 1 Clear the alarm by loading the correct software version on the TCC2/TCC2P with the incorrect load. To download software, refer to the release-specific software download document.

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 to report a Service-Affecting (SA) condition.


2.7.45  BPV

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

SONET Logical Object: BITS

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

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


Note This alarm is not raised on the TCC2 card.


Clear the BPV Alarm


Step 1 Reestablishing a normal BITS input signal clears the alarm. Clear any alarms on the incoming signal or against the BITS timing sources.

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


2.7.46  CARLOSS (CE1000, CE100T)

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

SONET Logical Objects: CE1000, CE100T

The Carrier Loss alarm is raised on CE-Series cards in Mapper mode when the port is In-Service (IS) state and if there is no carrier signal. Circuit need not be present to raise the alarm. In releases prior to 6.01 the Carrier Loss alarm is raised on CE-100T-8 cards in Mapper mode when there is a circuit failure due to link integrity. It does not get raised when a user simply puts the port in the In-Service and Normal (IS-NR) service state.


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


Clear the CARLOSS (CE100T) Alarm


Step 1 Complete the "Clear the CARLOSS (G1000) Alarm" procedure. However, rather than checking for a TPTFAIL (G1000) at the end of the procedure, check for a "TPTFAIL (CE100T, CE1000)" alarm on page 2-224.

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


2.7.47  CARLOSS (E1000F, E100T)

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

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


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


Clear the CARLOSS (E1000F, E100T) Alarm


Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.


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

Step 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. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

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. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

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.

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.

An Ethernet manual cross-connect is used when another vendor's equipment sits between ONS 15454 nodes, and the open systems interconnect/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.

If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, complete the following steps. The reappearing alarm could be a result of mismatched STS circuit sizes in the set up of the manual cross-connect. If the Ethernet circuit is not part of a manual cross-connect, the following steps do not apply.

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 and card are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:

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 "Create Circuits and VT Tunnels" chapter in 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 (SA) problem.


2.7.48  CARLOSS (EQPT)

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

SONET 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/TCC2P or the LAN backplane pin connection. This CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the node.

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

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


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

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

Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual. For more information about MRC-12 and OC192-XFP/STM64-XFP cards, refer to the "Change Card Settings" chapter of the Cisco ONS 15454 Procedure Guide. For more information about Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.


Clear the CARLOSS (EQPT) Alarm


Step 1 If the reporting card is an MXP or TXP card in an ONS 15454 node, verify the data rate configured on the 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 Type column and compare this with the contents of the Selected PPM area Rate column for the MXP or TXP multirate port.

d. If the rate does not match the actual equipment, you must delete and recreate the selected PPM. Select the PPM, 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 by completing the procedure in the "1.9.8  Verify PC Connection to the ONS 15454 (ping)" procedure.

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

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


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

Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

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

Step 7 If you are unable to establish connectivity, replace the fiber cable with a new known-good cable. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

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

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


2.7.49  CARLOSS (FC)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.50  CARLOSS (G1000)

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

SONET 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-152. 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.


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


Clear the CARLOSS (G1000) Alarm


Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.


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

Step 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 "OC-N Card Transmit and Receive Levels" section.

Step 5 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 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. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 7 If the alarm does not clear, and link autonegotiation is enabled on the 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 raised, 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 raised, 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 Electrical Card or Ethernet 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 12.

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


Note An ONS 15454 Ethernet manual cross-connect is used when another vendor's equipment sits between ONS nodes, and the 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 are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:

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 "Create Circuits and VT Tunnels" chapter in 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.

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 (SA) problem.


2.7.51  CARLOSS (GE)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.52  CARLOSS (ISC)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.53  CARLOSS (ML1000, ML100T, MLFX)

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

SONET Logical Objects: ML1000, ML100T, MLFX

A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-152. 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 problems also occurs:

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

Autonegotiation is failing.

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


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


Clear the CARLOSS (ML1000, ML100T, MLFX) 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. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

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

Step 6 If the alarm does not clear, complete the "Create the Facility Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure 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.

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


2.7.54  CARLOSS (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.55  CASETEMP-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.56  CLDRESTART

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

SONET Logical Object: EQPT

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

Clear the CLDRESTART Condition


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

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

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

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


2.7.57  COMIOXC

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

SONET Logical Object: EQPT

The Input/Output Slot To Cross-Connect Communication Failure alarm is caused by the XC10G or XC-VXC-10G cross-connect card 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 card in which the alarm is reported. 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 Cross-Connect Cards" procedure.

Step 4 Complete the "Remove and Reinsert (Reseat) Any Card" procedure on the card in which the alarm is reported.

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 or complete the "Physically Replace a Traffic Card" procedure on the card in which the alarm is reported.

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


2.7.58  COMM-FAIL

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

SONET Logical Object: EQPT

The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2/TCC2P and the traffic 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.

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.7.59  CONTBUS-A-18

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

SONET Logical Object: EQPT

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

Clear the CONTBUS-A-18 Alarm


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

Step 2 Wait approximately 10 minutes for the TCC2/TCC2P in Slot 7 to reset as the standby TCC2/TCC2P. 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 TCC2/TCC2P in Slot 11 and complete the "Reset an Active TCC2/TCC2P Card 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 Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby 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.7.60  CONTBUS-B-18

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

SONET Logical Object: EQPT

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

Clear the CONTBUS-B-18 Alarm


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

Step 2 Wait approximately 10 minutes for the Slot 11 TCC2/TCC2P to reset as the standby TCC2/TCC2P. 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/TCC2P and complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure to return the Slot 11 TCC2/TCC2P to the active state.

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


2.7.61  CONTBUS-DISABLED

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

SONET Logical Object: EQPT

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

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

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


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

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

Clear the CONTBUS-DISABLED Alarm


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

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


2.7.62  CONTBUS-IO-A

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

SONET Logical Object: EQPT

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

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

Clear the CONTBUS-IO-A Alarm


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

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

Step 2 If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P, 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/TCC2P, 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.)

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

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

Step 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 Cisco TAC 1 800 553-2447. If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.


2.7.63  CONTBUS-IO-B

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

SONET Logical Object: EQPT

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

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

Clear the CONTBUS-IO-B Alarm


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

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

Step 2 If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P, 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/TCC2P, 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-B is raised on several cards at the same time, complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure.

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

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

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

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


2.7.64  CTNEQPT-MISMATCH

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

SONET Logical Object: EQPT

The Connection Equipment Mismatch condition is raised when there is a mismatch between the cross-connect card preprovisioned in the slot and the card actually installed in the shelf. For example, one type of cross-connect card could be preprovisioned in Slot 10, but another could be physically installed. It can also be caused by a card that is mismatched with the card. For example, CTNEQPT-MISMATCH is raised when an XCVT card is replaced with a XC10G card.

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

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


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


Clear the CTNEQPT-MISMATCH Condition


Step 1 Determine what kind of card is preprovisioned in the slot:

a. In node view, click the Inventory tab.

b. View the information for the slot in the Eqpt Type and Actual Eqpt Type columns.

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


2.7.65  CTNEQPT-PBPROT

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

SONET 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 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/TCC2P and the backplane.


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



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

Clear the CTNEQPT-PBPROT Alarm


Step 1 If all traffic cards show CTNEQPT-PBPROT alarm, complete the following steps:

a. Complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure for the standby TCC2/TCC2P.

b. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the standby TCC2/TCC2P.


Caution Do not physically reseat an active TCC2/TCC2P. 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/TCC2P 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.

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 (SA) problem.


2.7.66  CTNEQPT-PBWORK

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

SONET 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 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/TCC2P and the backplane.


Note This alarm automatically raises and clears when the ONS 15454 Slot 10 XC10G card is reseated.


Clear the CTNEQPT-PBWORK Alarm


Step 1 If all traffic cards show CTNEQPT-PBWORK alarm, complete the following steps:

a. Complete the "Reset an Active TCC2/TCC2P Card and Activate the Standby Card" procedure for the active TCC2/TCC2P and then complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure.

b. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the TCC2/TCC2P.


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.


Caution Do not physically reseat an active TCC2/TCC2P; it disrupts traffic.

Step 2 If all cards do not show the alarm, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure for the active XC10G 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 revert the traffic.

Step 11 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the OC-192 card.

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 (SA) problem.


2.7.67  DATAFLT

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

SONET Logical Object: NE

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


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

Clear the DATAFLT Alarm


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

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


2.7.68  DBOSYNC

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

SONET Logical Object: NE

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


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

Clear the DBOSYNC Alarm


Step 1 Save a backup copy of the active TCC2/TCC2P database. Refer to the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide for procedures.

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.7.69  DISCONNECTED

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

SONET Logical Object: SYSTEM

The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm clears when CTC reconnects to the node.

Clear the DISCONNECTED Alarm


Step 1 Restart CTC.

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


2.7.70  DS3-MISM

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

SONET Logical Object: DS3

The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on a signal transiting the ONS 15454 DS3XM-6, DS3XM-12, or DS3/EC1-48 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, DS3XM-12, or DS3/EC1-48 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.7.71  DSP-COMM-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.72  DSP-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.73  DUP-IPADDR

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

SONET Logical Object: NE

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

Clear the DUP-IPADDR Alarm


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

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

b. Begin a CTC session.

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

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

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

Step 4 Click Apply.

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

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


2.7.74  DUP-NODENAME

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

SONET 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/TID 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.7.75  DUP-SHELF-ID

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.76  EHIBATVG

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

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

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 (SA) problem.


2.7.77  ELWBATVG

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

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

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 (SA) problem.


2.7.78  ENCAP-MISMATCH-P

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

SONET Logical Object: STSTRM

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

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

The received C2 byte is not a PDI value.

The received C2 does not match the expected C2.

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

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

(This is in contrast to the "PLM-P" alarm on page 2-181, 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.

For example, an ENCAP-MISMATCH-P alarm is raised if a circuit created between two ML-Series or between two CE-1000 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 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 condition.


Note By default, an ENCAP-MISMATCH-P alarm causes an ML-Series card or CE-1000 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 or CE-1000 cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.


Clear the ENCAP-MISMATCH-P Alarm


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

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

b. Click the Provisioning > Card tabs.

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

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

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

b. Click the Provisioning > Card tabs.

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

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

Encapsulation

CRC size

Scrambling state

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

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


2.7.79  EOC

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

SONET Logical Object: OCN

DWDM Logical Object: TRUNK

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

The SDCC consists of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS 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 for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

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

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

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


Clear the EOC Alarm


Step 1 If the "LOS (DS1)" alarm on page 2-145 is also reported, complete the "Clear the LOS (OCN) Alarm" 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.

Step 2 If the "SF-L" condition on page 2-201 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 that the fiber-optic cables are configured to carry SDCC traffic. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

If the physical connections are correct and configured to carry DCC traffic, ensure 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 Section DCC Terminations" procedure to verify that the DCC is provisioned for the ports at both ends of the fiber span.

Step 5 Repeat Step 4 at the adjacent nodes.

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

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


Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.


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

Step 8 If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. See the "OC-N Card Transmit and Receive Levels" section for non-DWDM card levels and refer to the Cisco ONS 15454 DWDM Reference Manual for DWDM card levels.

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

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

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

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

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

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

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

c. Highlight the problematic DCC termination.

d. Click Delete.

e. Click Yes in the Confirmation Dialog box.

Step 12 Recreate the SDCC termination. Refer to the "Turn Up Network" chapter in the Cisco ONS 15454 Procedure Guide for procedures.

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

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


2.7.80  EOC-L

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

SONET Logical Object: OCN

DWDM Logical Object: TRUNK

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

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

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

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

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


Clear the EOC-L Alarm


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

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


2.7.81  EQPT

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

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

DWDM Logical Object: 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 on page 2-185 is raised. The standby path generates a path-type alarm.

Clear the EQPT Alarm


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

Step 2 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For 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.

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


2.7.82  EQPT-DIAG

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

SONET Logical Object: EQPT

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

Clear the EQPT-DIAG Alarm


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

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

Step 3 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure if it is raised against a traffic card, or complete the "Physically Replace an In-Service Cross-Connect Card" procedure if the alarm is raised against the cross-connect card.

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


2.7.83  EQPT-MISS

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

SONET 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 could also indicate that the ribbon cable connecting the AIP to the system board is bad.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 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 Fan-Tray Assembly" procedure.

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

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

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


2.7.84  ERFI-P-CONN

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

SONET Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication (ERFI) Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the "UNEQ-P" alarm on page 2-229 and the "TIM-P" alarm on page 2-222 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.7.85  ERFI-P-PAYLD

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

SONET Logical Objects: STSMON, STSTRM

The Three-Bit ERFI Path Payload condition is triggered on DS-1, DS-3, or VT circuits when the "PLM-P" alarm on page 2-181 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.7.86  ERFI-P-SRVR

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

SONET Logical Objects: STSMON, STSTRM

The Three-Bit ERFI Path Server condition is triggered on DS-1, DS-3, or VT circuits when the "AIS-P" condition on page 2-35 or the "LOP-P" alarm on page 2-142 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.7.87  ERROR-CONFIG

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

SONET 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/TCC2P:

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.7.88  ETH-LINKLOSS

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

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


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


Clear the ETH-LINKLOSS Condition


Step 1 To clear this condition, reconnect the backplane LAN cable. Refer to the "Install the Shelf and Backplane Cable" chapter in the Cisco ONS 15454 Procedure Guide for procedures 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.7.89  E-W-MISMATCH

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

SONET 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 the west slot and the higher numbered slot is labeled 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 Click the circuit and click Edit. The network map detailed view window appears. This window contains the node name, slot, and port for each end of each span.

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

Step 5 Label the span ends on the diagram with the same information. For example, with Node 1/Slot 12/Port 1—Node 2/Slot 6/Port 1 (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 "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide for more information about cabling the system.

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


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

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

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

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


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 (SA) problem.


2.7.90  EXCCOL

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

SONET 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/TCC2P. The problem causing the alarm is external to the ONS 15454.

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

Clear the EXCCOL Alarm


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

Step 2 If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the TCC2/TCC2P 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.7.91  EXERCISE-RING-FAIL

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

SONET 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 (NR).


Clear the EXERCISE-RING-FAIL Condition


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

Step 2 Complete the "Initiate an Exercise Ring Switch on a BLSR" 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.7.92  EXERCISE-SPAN-FAIL

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

SONET 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 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 span or ring, EXERCISE-SPAN-FAIL is Not Reported (NR).


Clear the EXERCISE-SPAN-FAIL Condition


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

Step 2 Complete the "Initiate an Exercise Ring Switch on a BLSR" 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.7.93  EXT

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

SONET Logical Object: ENVALRM

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

Clear the EXT Alarm


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

Step 2 Double-click the 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.7.94  EXTRA-TRAF-PREEMPT

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

SONET 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 "Protection Switching, Lock Initiation, and Clearing" section or the "Maintain the Node" chapter in 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 (SA) problem.


2.7.95  FAILTOSW

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

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

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 or optical card that is reporting the higher-priority alarm by following the "Physically Replace a Traffic Card" procedure. This card is the working electrical or optical card using the protect card and not reporting FAILTOSW.

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

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


2.7.96  FAILTOSW-PATH

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

SONET 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 protect 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-35, the "LOP-P" alarm on page 2-142, the "SD-P" condition on page 2-199, the "SF-P" condition on page 2-202, and the "UNEQ-P" alarm on page 2-229.

The "LOF (OCN)" alarm on page 2-138, the "LOS (OCN)" alarm on page 2-152, the "SD-L" condition on page 2-198, or the "SF-L" condition on page 2-201 can also occur on the failed path.

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration


Step 1 Look up and clear the higher-priority alarm. Clearing this alarm frees the standby card and clears the FAILTOSW-PATH condition. If the "AIS-P" condition on page 2-35, the "LOP-P" alarm on page 2-142, the "UNEQ-P" alarm on page 2-229, the "SF-P" condition on page 2-202, the "SD-P" condition on page 2-199, the "LOF (OCN)" alarm on page 2-138, the "LOS (OCN)" alarm on page 2-152, the "SD-L" condition on page 2-198, or the "SF-L" condition on page 2-201 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 electrical 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 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.

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.7.97  FAILTOSWR

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

SONET 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 in any of the following situations:

A physical card pull of the active TCC2/TCC2P (done under Cisco 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-195 or the "SF (DS1, DS3)" condition on page 2-200) 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 for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

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

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

Clear the 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 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 open 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.


Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.


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

Step 8 If fiber continuity to the ports is good, 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 OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure 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 "OC-N Card Transmit and Receive Levels" section 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.

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.7.98  FAILTOSWS

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

SONET 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/TCC2P done under Cisco 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-195 or the "SF (DS1, DS3)" condition on page 2-200) 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 open 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.


Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.


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

Step 8 If fiber continuity to the ports is good, 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 OC-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure 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 "OC-N Card Transmit and Receive Levels" section 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.

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.7.99  FAN

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

SONET 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 "Remove and Reinsert a Fan-Tray Assembly" procedure.

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

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


2.7.100  FC-NO-CREDITS

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

SONET Logical Object: FCMR

DWDM Logical Objects: FC, TRUNK

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 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 could 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 using the manufacturer's 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. Click Provisioning > Port > General.

c. Under Admin State, click the cell and choose OOS,MT.

d. Click Apply.

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

f. Uncheck the Autodetect Credits column check box.

g. Click Apply.

h. Click Provisioning > Port > General.

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

j. Click Apply.


Note If a port in the IS admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to OOS-AU,FLT.


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 (SA) problem.


2.7.101  FDI

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.102  FE-AIS

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

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

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

Clear the 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.7.103  FEC-MISM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.104  FE-DS1-MULTLOS

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

SONET 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.7.105  FE-DS1-NSA

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

SONET Logical Object: DS3

The Far End DS-1 Equipment Failure Non-Service-Affecting (NSA) 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.

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.7.106  FE-DS1-SA

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

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

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.7.107  FE-DS1-SNGLLOS

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

SONET 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 (within a DS3). Signal loss also causes the "LOS (OCN)" alarm on page 2-152.

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.7.108  FE-DS3-NSA

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

SONET Logical Object: DS3

The Far End DS-3 Equipment Failure Non-Service-Affecting (NSA) 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.

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.7.109  FE-DS3-SA

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

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

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.7.110  FE-EQPT-NSA

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

SONET Logical Object: DS3

The Far End Common Equipment Failure condition occurs when a Non-Service-Affecting (NSA) equipment failure is detected on far-end DS-3 equipment.

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.7.111  FE-FRCDWKSWBK-SPAN

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

SONET Logical Object: OCN

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


Note WKSWBK-type conditions apply only to revertive circuits.


Clear the FE-FRCDWKSWBK-SPAN Condition


Step 1 Complete the "Clear a 1+1 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.7.112  FE-FRCDWKSWPR-RING

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

SONET Logical Object: OCN

The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a BLSR is forced from working to protect using the Force Ring command. This condition is only visible on the network view Conditions tab.

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 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.7.113  FE-FRCDWKSWPR-SPAN

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

SONET 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. This condition is only visible on the network view Conditions tab. The port where the Force Switch occurred is indicated by an "F" on the network view detailed circuit map. This condition is accompanied by WKSWPR.

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 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.7.114  FE-IDLE

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

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

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 traffic-switching 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.7.115  FE-LOCKOUTOFPR-SPAN

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

SONET 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. This condition is only seen on the network view Conditions tab and is accompanied by LKOUTPR-S. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

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.7.116  FE-LOF

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

SONET Logical Object: DS3

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

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.7.117  FE-LOS

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

SONET 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-147.

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.7.118  FE-MANWKSWBK-SPAN

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

SONET Logical Object: OCN

The Far End Manual Switch Back to Working—Span condition occurs when a far-end span with a Manual switch reverts to working.


Note WKSWBK-type conditions apply only to nonrevertive circuits.


Clear the FE-MANWKSWBK-SPAN 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 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.7.119  FE-MANWKSWPR-RING

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

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

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.7.120  FE-MANWKSWPR-SPAN

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

SONET 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 Span command. This condition is only visible on the network view Conditions tab and is accompanied by WKSWPR. The port where the Manual Switch occurred is indicated by an "M" on the network view detailed circuit map.

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

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.7.121  FEPRLF

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

SONET Logical Object: OCN

The Far End Protection Line Failure alarm occurs when an APS channel "SF-L" condition on page 2-201 occurs on the protect card coming into the node.


Note The FEPRLF alarm occurs when bidirectional protection is used on optical cards in a 1+1 protection group 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 procedures.

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.7.122  FIBERTEMP-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.123  FORCED-REQ

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

SONET Logical Objects: EQPT, STSMON, VT-MON

The Force Switch Request on Facility or Port condition occurs when you enter the Force command on a port to force traffic from a working port to a protect port or protection span (or from a protect port to a working port or span). 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 1+1 Force or Manual Switch 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.7.124  FORCED-REQ-RING

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

SONET Logical Object: OCN

The Force Switch Request Ring condition applies to optical trunk cards when the Force Ring command is applied to BLSRs to move traffic from working to protect. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the FORCE RING command originated is marked with an "F" on the network view detailed circuit map.

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.7.125  FORCED-REQ-SPAN

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

SONET Logical Object: OCN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, 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 SPAN to force traffic from working to protect or from protect to working. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the FORCE SPAN command was applied is marked with an "F" on the network view detailed circuit map.

This condition can also be raised in 1+1 facility protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.

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.7.126  FRCDSWTOINT

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

SONET 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.7.127  FRCDSWTOPRI

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

SONET 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.7.128  FRCDSWTOSEC

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

SONET 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.7.129  FRCDSWTOTHIRD

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

SONET Logical Objects: EXT-SREF, NE-SREF

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


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


2.7.130  FRNGSYNC

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

SONET Logical Object: NE-SREF

The Free Running Synchronization Mode condition 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 Condition


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 "Timing" chapter in the Cisco ONS 15454 Reference Manual for more information.

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

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.7.131  FSTSYNC

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

SONET Logical Object: NE-SREF

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

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


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


2.7.132  FULLPASSTHR-BI

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

SONET 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.7.133  GAIN-HDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.134  GAIN-HFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.135  GAIN-LDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.136  GAIN-LFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.137  GCC-EOC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.138  GE-OOSYNC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.139  GFP-CSF

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

SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX

The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on FC_MR-4, ML100T, ML1000, ML100X-8, MXP_MR_25G, and MXPP_MR_25G GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm caused by an event such as a pulled receive cable is affecting a remote data port's transmission capability. This alarm can be demoted when a facility loopback is placed on the FC_MR-4 port.


Note For more information about provisioning MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual. For more information about Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.


Clear the GFP-CSF Alarm


Step 1 Clear the Service-Affecting (SA) alarm at the remote data port.

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


2.7.140  GFP-DE-MISMATCH

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

SONET Logical Objects: FCMR, GFP-FAC

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.


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


Clear the GFP-DE-MISMATCH Alarm


Step 1 Ensure that the distance extension protocol is configured correctly on both sides:

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

b. Click the Provisioning > Port > General tabs.

c. Under Admin State, click the cell and choose OOS,MT.

d. Click Apply.

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

f. Check the check box in the Enable Distance Extension column.

g. Click Apply.

h. Click the Provisioning > Port > General tabs.

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

j. Click Apply.


Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.


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


2.7.141  GFP-EX-MISMATCH

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

SONET Logical Objects: CE1000, FCMR, GFP-FAC

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.

Ensure 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 vendors' equipment, those need to be provisioned appropriately.


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


Clear the 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 clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.


2.7.142  GFP-LFD

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

SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX

The GFP Loss of Frame Delineation alarm applies to Fibre Channel, FICON GFP, and Ethernet ports. This alarm occurs if there is a faulty 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. This loss causes traffic stoppage.


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


Clear the 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 clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447 to report a Service-Affecting (SA) problem.


2.7.143  GFP-NO-BUFFERS

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

SONET Logical Objects: FCMR, GFP-FAC

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 could 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 could be raised at the upstream remote FC_MR-4 data port.


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


Clear the GFP-NO-BUFFERS Alarm


Step 1 Complete the "Clear the FC-NO-CREDITS Alarm" procedure.

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


2.7.144  GFP-UP-MISMATCH

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

SONET Logical Objects: CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX

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 Gbps ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL or FICON—2 Gbps ISL.


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


Clear the GFP-UP-MISMATCH Alarm


Step 1 Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps:

a. Double-click the card to open 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 steps:

a. Double-click the card to open 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 - 1Gbps ISL, Fibre Channel - 2 Gbps ISL, FICON - 1 Gbps ISL, or FICON - 2 Gbps ISL) from the drop-down list.

d. Click Apply.

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


2.7.145  HELLO

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

SONET Logical Object: 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.7.146  HIBATVG

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

SONET Logical Object: PWR

The High Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage exceeds the high power threshold. This threshold, with a default value of -52 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure 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 (SA) problem.


2.7.147  HI-CCVOLT

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

SONET Logical Object: BITS

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

Clear the HI-CCVOLT Condition


Step 1 Lower the source voltage to the clock.

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

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


2.7.148  HI-LASERBIAS

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM

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, MXP_2.5G_10G, OC192-XFP, OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, or MRC-12 card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.

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


Note When there is a HI-LASERBIAS alarm on the OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.x, or MRC-12 cards, the alarm is reported at the card equipment level, not the port equipment level. However, on cards with PPMs, the alarms are reported at the port level. So the end result is that the alarms are reported at different levels (port or card equipment), depending on if the port has a replaceable PPM or is a fixed-rate port with no PPM. Because the alarm cannot be isolated to a specific port from the alarm indication on the four cards mentioned, when the HI-LASERBIAS alarm occurs and cannot be cleared, it is recommended to change out the entire card (see the procedure in this section).

To see which port on a card is having possible performance problems that may be causing the alarm, see DLP-A507 in the DLPs A500 to A599 chapter of the Cisco ONS 15454 Procedure Guide, R7.0. To change how the performance monitoring (PM) parameters are displayed, see NTP-A253 in the Monitor Performance chapter of the Cisco ONS 15454 Procedure Guide, R7.0.



Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-LASERBIAS Alarm


Step 1 Complete the "Clear the LASEREOL Alarm" procedure, which can include replacing the card. Replacement is not urgent and can be scheduled during a maintenance window.


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

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


2.7.149  HI-LASERTEMP

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Object: PPM

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

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The "LOS (OCN)" alarm on page 2-152 is raised at the far-end node and the "DUP-IPADDR" alarm on page 2-73 is raised at the near end.


Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-LASERTEMP Alarm


Step 1 In node view, double-click the TXP or MXP card to open the card view.

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

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

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

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

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


2.7.150  HI-RXPOWER

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

SONET Logical Object: OCN

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

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, MXP_2.5G_10G, or OC192-XFP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.


Note When you upgrade a node to Software Release 6.0 or later, this enables received optical power PMs for the OC3-8, OC192-SR, OC192-IR, OC192-ITU, OC-192-XFP, MRC-12, and MRC25G-4 cards. The newly enabled HI-RXPOWER and LO-RXPOWER alarms require that you initialize a site-accepted optical power (OPR0) nominal value after the upgrade. (To do this, refer to the procedure in the "Turn Up a Node" chapter in the Cisco ONS 15454 Procedure Guide.) When you apply the value change, CTC uses the new OPR0 value to calculate PM percentage values. If you do not change the nominal value, the HI-RXPOWER or LO-RXPOWER may be raised in response to the unmodified setting.



Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.


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

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.6.1  Perform a Facility Loopback on a Source-Node FC_MR Port" procedure 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.

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.7.151  HITEMP

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

SONET Logical Objects: EQPT, NE

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

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 15454 shelf empty slots. Blank faceplates help airflow.

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

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


Note The fan should run immediately when correctly inserted.


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


2.7.152  HI-TXPOWER

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM

The Equipment High Transmit Power alarm is an indicator on the TXP_MR_E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, OC192-XFP, OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, and MRC-12 card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.


Note When there is a HI-TXPOWER alarm on the OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, or MRC-12 cards, the alarm is reported at the card equipment level, not the port equipment level. However, on cards with PPMs, the alarms are reported at the port level. So the end result is that the alarms are reported at different levels (port or card equipment), depending on if the port has a replaceable PPM or is a fixed-rate port with no PPM. Because the alarm cannot be isolated to a specific port from the alarm indication on the four cards mentioned, when the HI-TXPOWER alarm occurs and cannot be cleared, it is recommended to change out the entire card (see the procedure in this section).

To see which port on a card is having possible performance problems that may be causing the alarm, see DLP-A507 in the DLPs A500 to A599 chapter of the Cisco ONS 15454 Procedure Guide, R7.0. To change how the performance monitoring (PM) parameters are displayed, see NTP-A253 in the Monitor Performance chapter of the Cisco ONS 15454 Procedure Guide, R7.0.



Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-TXPOWER Alarm


Step 1 In node view, double-click the card view for the TXP_MR_10E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card.

Step 2 Click the Provisioning > Optics Thresholds > Current Values tabs.

Step 3 Decrease (change toward the negative direction) the OPT-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" section.

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.7.153  HLDOVRSYNC

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

SONET Logical Object: NE-SREF

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

Clear the HLDOVRSYNC Condition


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

FRNGSYNC

FSTSYNC

LOF (BITS)

LOS (BITS)

MANSWTOINT

MANSWTOPRI

MANSWTOSEC

MANSWTOTHIRD

SWTOPRI

SWTOSEC

SWTOTHIRD

SYNC-FREQ

SYNCPRI

SYNCSEC

SYNCTHIRD

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

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


2.7.154  I-HITEMP

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

SONET 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 (SA) problem.


2.7.155  INCOMPATIBLE-SEND-PDIP

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

SONET Logical Object: SYSTEM

The Incompatible Software alarm is raised when the PDIP provisioning on CTC differs from the provisioning on the host node.

Clear the INCOMPATIBLE-SEND-PDIP Alarm


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

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


2.7.156  INCOMPATIBLE-SW

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

SONET Logical Object: SYSTEM

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

Clear the INCOMPATIBLE-SW Alarm


Step 1 Restart the CTC application.

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


2.7.157  IMPROPRMVL

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

SONET Logical Object: EQPT

DWDM Logical Object: PPM

The Improper Removal equipment (IMPROPRMVL) alarm occurs under the following conditions:

A card is removed when the card was rebooting. It is recommended that after the card completely reboots, delete the card in CTC and only then remove the card physically. When you delete the card, CTC loses connection with the node view (single-shelf mode) or shelf view (multishelf mode), and goes to network view.

When a card is physically removed from its slot before it is deleted from CTC. It is recommended that any card be deleted in CTC before physically removing the card from the chassis.


Note CTC provides the user approximately 15 seconds to physically remove the card before it begins rebooting the card.
It can take up to 30 minutes for software to be updated on a standby TCC2/TCC2P card.


A card is inserted into a slot but is not fully plugged into the backplane.

A PPM (SFP) is provisioned but the physical module is not inserted into the port.

Electrical issues such as short circuit or failure of DC-DC conversion.

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, does have circuits mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.


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


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


2.7.158  INC-ISD

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

SONET 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.7.159  INHSWPR

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

SONET 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 Manual Switch Command" section.

Step 2 If the condition 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.7.160  INHSWWKG

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

SONET 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 1:N 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 Manual Switch Command" section.

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.7.161  INTRUSION-PSWD

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

SONET Logical Object: NE

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

Clear the INTRUSION-PSWD Condition


Step 1 Click the Provisioning > Security > Users tabs.

Step 2 Click Clear Security Intrusion Alarm.

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.7.162  INVMACADR

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

SONET Logical Object: AIP

The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15454 MAC address is invalid. Each ONS 15454 has a unique, permanently assigned MAC address. The address resides on an AIP EEPROM. The TCC2/TCC2P 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 see a PARTIAL circuit in the CTC circuit status column. The circuit works and is able to carry traffic, but CTC cannot logically display the circuit end-to-end information.

An invalid MAC address can be caused when:

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

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

An AIP component failure causes a read error.

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

Clear the INVMACADR Alarm


Step 1 Check for any outstanding alarms that were raised against the active and standby TCC2/TCC2P 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/TCC2P:


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


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

b. Identify the active TCC2/TCC2P.

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

c. Right-click the standby TCC2/TCC2P in CTC.

d. Choose Reset Card from the shortcut menu.

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

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

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

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

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

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

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

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

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

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

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

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

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

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


Note If the replacement TCC2/TCC2P is loaded with a different software version from the current TCC2/TCC2P, the card bootup could take up to 30 minutes. During this time, the card LEDs flicker between Fail and Act/Sby as the active TCC2/TCC2P 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.7.163  IOSCFGCOPY

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

SONET 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-202 but it applies to ML-Series Ethernet cards rather than to the TCC2/TCC2P.)

The condition clears after the copy operation is complete. (If it does not complete correctly, the "NO-CONFIG" condition on page 2-174 could 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.7.164  ISIS-ADJ-FAIL

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

SONET Logical Object: OCN

The Open System Interconnection (OSI) Intermediate System to Intermediate-System (IS-IS) Adjacency Failure alarm is raised by an intermediate system (node routing IS Level 1 or Level 1 and 2) when no IS or end system (ES) adjacency is established on a point-to-point subnet. The Intermediate-System Adjacency Failure alarm is not supported by ES. It is also not raised by IS for disabled routers.

The alarm is typically caused by a misconfigured router manual area adjacency (MAA) address. For more information about IS-IS OSI routing and MAA configuration, refer to the "Management Network Connectivity" chapter in the Cisco ONS 15454 Reference Manual. For more information about configuring OSI, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure Guide.

Clear the ISIS-ADJ-FAIL Alarm


Step 1 Ensure that both ends of the communication channel are using the correct Layer 2 protocol and settings (LAPD or PPP). To do this, complete the following steps:

a. At the local node, in node view, click the Provisioning > Comm Channels > SDCC tabs.

b. Click the row of the circuit. Click Edit.

c. In the Edit SDCC termination dialog box, view and record the following selections: Layer 2 protocol (LAPD or PPP); Mode radio button selection (AITS or UITS); Role radio button selection (Network or User); MTU value; T200 value, and T203 selections.

d. Click Cancel.

e. Login to the remote node and follow the same steps, also recording the same information for this node.

Step 2 If both nodes do not use the same Layer 2 settings, you will have to delete the incorrect termination and recreate it. To delete it, click the termination and click Delete. To recreate it, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure Guide for the procedure.

Step 3 If the nodes use PPP Layer 2, complete the "Clear the EOC Alarm" procedure. If the alarm does not clear, go to Step 7.

Step 4 If both nodes use the LAPD Layer 2 protocol but have different Mode settings, change the incorrect node's entry by clicking the correct setting radio button in the Edit SDCC termination dialog box and clicking OK.

Step 5 If the Layer 2 protocol and Mode settings are correct, ensure that one node is using the Network role and the other has the User role. If not (that is, if both have the same mode settings), correct the incorrect one by clicking the correct radio button in the Edit SDCC termination dialog box and clicking OK.

Step 6 If the Layer 2, Mode, and Role settings are correct, compare the MTU settings for each node. If one is incorrect, choose the correct value in the Edit SDCC dialog box and click OK.

Step 7 If all of the preceding settings are correct, ensure that OSI routers are enabled for the communications channels at both ends:

a. Click Provisioning > OSI > Routers > Setup tabs.

b. View the router entry under the Status column. If the status is Enabled, check the other end.

c. If the Status is Disabled, click the router entry and click Edit.

d. Check the Enabled check box and click OK.

Step 8 If the routers on both ends are enabled and the alarm still has not cleared, ensure that both ends of the communications channel have a common MAA:

a. Click the Provisioning > OSI > Routers > Setup tabs.

b. Record the primary MAA and secondary MAAs, if configured.


Tip You can record long strings of information such as the MAA address by using the CTC export and print functions. Export it by choosing File > Export > html. Print it by choosing File > Print.


c. Log into the other node and record the primary MAA and secondary MAAs, if configured.

d. Compare this information. There should be at least one common primary or secondary MAA in order to establish an adjacency.

e. If there is no common MAA, one must be added to establish an adjacency. Refer to the "Turn Up Node" chapter in the Cisco ONS 15454 Procedure Guide for procedures.

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.


2.7.165  KB-PASSTHR

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

SONET 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.7.166  KBYTE-APS-CHANNEL-FAILURE

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

SONET Logical Object: OCN

The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For example, 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 the "AIS-P" alarm on page 2-35, the "LOF (OCN)" alarm on page 2-138, the "LOS (OCN)" alarm on page 2-152 or the "SF-P" alarm on page 2-202.

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 "Turn Up Network" chapter in the Cisco ONS 15454 Procedure 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/TCC2P. In this case, complete the "Side Switch the Active and Standby 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.7.167  LAN-POL-REV

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

SONET Logical Object: NE

The LAN Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised during a software upgrade when the card detects that a connected Ethernet cable has reversed receive wire pairs. The card automatically compensates for this reversal, but LAN-POL-REV stays active.


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


Clear the 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 "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.

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


2.7.168  LASER-APR

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.169  LASERBIAS-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.170  LASERBIAS-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.171  LASEREOL

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

SONET 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-114. It is an indicator that the laser in the card must 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.


Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.For more information about MXP and TXP cards, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide.


Clear the LASEREOL Alarm


Step 1 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.7.172  LASERTEMP-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.173  LCAS-CRC

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

SONET Logical Objects: STSTRM, VT-TERM

The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against ML-Series Ethernet cards and CE-series 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.

Transmission errors would 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 does 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 persists 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 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 Circuits 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 Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.

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.7.174  LCAS-RX-FAIL

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

SONET Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Receive-Side-In Fail condition is raised against CE-series cards, FC_MR-4 cards, and ML-Series Ethernet cards with LCAS-enabled VCG. ML-Series Ethernet cards with LCAS-enabled VCG.

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.



Note ML-Series cards are LCAS-enabled. ML-Series and FC_MR-4 cards are SW-LCAS enabled.


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.7.175  LCAS-TX-ADD

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

SONET Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-Series Ethernet and CE-series cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed. The remote likely reports a path condition such as the "AIS-P" condition on page 2-35 or the "UNEQ-P" alarm on page 2-229


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.7.176  LCAS-TX-DNU

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

SONET Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Do Not Use condition is raised on FC_MR-4 cards and ML-Series Ethernet cards, and CE-series cards when the transmit side of an LCAS VCG member is in the do-not use state. For a unidirectional failure, this condition is only raised at the source node. The LCAS-TX-DNU condition is raised when the cable is unplugged.

The node reporting this condition likely reports an "RFI-P" alarm on page 2-190, and the remote node likely reports a path alarm such as the "AIS-P" alarm on page 2-35 or the "UNEQ-P" alarm on page 2-229.


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.7.177  LKOUTPR-S

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

SONET Logical Object: OCN

The Lockout of Protection Span condition occurs when span traffic is locked out of a protect span using the Lockout of Protect command. This condition is visible on the network view Alarms, Conditions, and History tabs after the lockout has occurred and accompanies the FE-LOCKOUTPR-SPAN condition. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

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.7.178  LOA

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

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

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 window, view 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 "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15454 Procedure Guide.

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


2.7.179  LOCKOUT-REQ

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

SONET Logical Objects: EQPT, OCN, STSMON, VT-MON

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an OC-N port in a 1+1 facility protection group. This can be accomplished by locking traffic onto the working port with the LOCK ON command (thus locking it off the protect port), or locking it off the protect port with the LOCK OUT command. In either case, the protect port will show "Lockout of Protection," and the Conditions window will show the LOCKOUT-REQ condition.

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

Clear the LOCKOUT-REQ Condition


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

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


2.7.180  LOF (BITS)

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

SONET Logical Object: BITS

The Loss of Frame (LOF) BITS alarm occurs when a port on theTCC2/TCC2P 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.


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


Clear the LOF (BITS) Alarm


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

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

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

c. Click the Provisioning > Timing > BITS Facilities tabs.

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

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

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

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


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


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

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


2.7.181  LOF (DS1)

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

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

Clear the LOF (DS1) Alarm


Step 1 Verify that the line framing and line coding match between the DS1 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 could need to contact your network administrator for the format information.

c. Display the card view of the reporting card.

d. Click the 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 the 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 (SA) problem.


2.7.182  LOF (DS3)

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

SONET 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 on DS3XM-6, DS3XM-12, or add DS3/EC1-48 cards. 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 (SA) problem.


2.7.183  LOF (E1)

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

SONET Logical Object: E1

The E1 LOF alarm appears on the DS1/E1-56 card when the card is placed in All E1 mode. It indicates that the receiving ONS 15454 has lost frame delineation in an incoming E1 data stream. The transmitting equipment could possibly have its framing set to a format that differs from the receiving node. For more information about the DS1/E1-56 card, refer to the "Electrical Cards" chapter in the Cisco ONS 15454 Reference Manual.


Note The DS1/E1-56 card only carries an E1 signal within an STS-3c/VT2 circuit.


Clear the LOF (E1) Alarm


Step 1 Verify that the line framing and line coding match between the DS1/E1-56 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 could need to contact your network administrator for this information.

c. Double-click the DS1/E1-56 card to open the card view.

d. Click the Provisioning > Line tabs.

e. Verify that the line type of the reporting port matches the line type (E1_MF, E1_CRCMF, AUTOFRAMED, UNFRAMED) of the signal source. 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. 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 When you replace a card with the 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 (SA) problem.


2.7.184  LOF (EC1)

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

SONET Logical Object: EC1

The EC1/EC1-12 LOF alarm occurs when a port on the reporting EC1/EC1-12 or DS3/EC1-48 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.

Clear the LOF (EC1) Alarm


Step 1 Verify cabling continuity to the port reporting the alarm. To verify cable continuity, follow site practices.


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

Step 2 If cabling continuity is good, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm does not clear, see the loopback procedures in Chapter 1 "General Troubleshooting" 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 (SA) problem 1 800 553-2447.


2.7.185  LOF (OCN)

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

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


Note For information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the LOF (OCN) Alarm


Step 1 Verify cabling continuity to the port reporting 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. To verify cable continuity, follow site practices.

Step 2 If cabling continuity is good, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm does not clear, see the loopback procedures in Chapter 1 "General Troubleshooting" 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 (SA) problem 1 800 553-2447.


2.7.186  LOF (STSTRM)

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

SONET Logical Object: STSTRM

A Loss of Frame alarm for an STS circuit termination indicates that the LOF has occurred at the terminating point of the circuit (such as an OC-N port). It is similar to the "LOF (OCN)" alarm on page 2-138.

Clear the LOF (STSTRM) Alarm


Step 1 Complete the "Clear the LOF (OCN) Alarm" alarm on page 2-138.

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


2.7.187  LOF (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.188  LOGBUFR90

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

SONET Logical Object: SYSTEM

The Log Buffer Over 90 alarm indicates that the per-NE queue of incoming alarm, event, or update capacity of 5000 entries is over 90% full. LOGBUFR90 will clear if CTC recovers. If it does not clear, the LOGBUFROVFL alarm occurs.


Note LOGBUFR90 is an informational alarm and does not require troubleshooting.


2.7.189  LOGBUFROVFL

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

SONET Logical Object: SYSTEM

The Log Buffer Overflow alarm indicates that the CTC per-NE queue of incoming alarm, event, or updates, which has a capacity of 5000 entries, has overflowed. This happens only very rarely; if the alarm does occur, you must restart the CTC session. If this alarm occurs, it is likely that some updates are missing.

Clear the LOGBUFROVFL Alarm


Step 1 Restart the CTC session.

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


2.7.190  LO-LASERBIAS

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Object: PPM

The Equipment Low Transmit Laser Bias Current alarm is raised against the TXP, MXP, OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, or MRC-12 card laser performance. The alarm indicates that the card laser has reached the minimum laser bias tolerance.

If the LO-LASERBIAS alarm threshold is set at 0 percent (the default), the laser's usability has ended. If the threshold is set at 5 percent to10 percent, the card is still usable for several weeks or months before you need to replace it.


Note When there is a LO-LASERBIAS alarm on the OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, or MRC-12 cards, the alarm is reported at the card equipment level, not the port equipment level. However, on cards with PPMs, the alarms are reported at the port level. So the end result is that the alarms are reported at different levels (port or card equipment), depending on if the port has a replaceable PPM or is a fixed-rate port with no PPM. Because the alarm cannot be isolated to a specific port from the alarm indication on the four cards mentioned, when the LO-LASERBIAS alarm occurs and cannot be cleared, it is recommended to change out the entire card (see the procedure in this section).

To see which port on a card is having possible performance problems that may be causing the alarm, see DLP-A507 in the DLPs A500 to A599 chapter of the Cisco ONS 15454 Procedure Guide, R7.0. To change how the performance monitoring (PM) parameters are displayed, see NTP-A253 in the Monitor Performance chapter of the Cisco ONS 15454 Procedure Guide, R7.0.



Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the LO-LASERBIAS Alarm


Step 1 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.7.191  LO-LASERTEMP

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Object: PPM

The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. LO-LASERTEMP occurs when the internally measured transceiver temperature falls below the card setting by35.6 degrees F or 2 degrees C. A laser temperature change affects the transmitted wavelength. (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-152 is raised at the far-end node and the "DUP-IPADDR" alarm on page 2-73 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 Values tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.


Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


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.7.192  LOM

Default Severity: Critical (CR), Service-Affecting (SA) for STSMON, STSTRM, TRUNK; Major (MJ) for VT-TERM

SONET Logical Objects: STSMON, STSTRM, VT-TERM

DWDM Logical Object: TRUNK

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 OCN ports when the Multi Frame Alignment Signal (MFAS) overhead field is errored for more than five frames and persists for more than 3 milliseconds.


Note Optical cards do not recognize the LOM. The system redirects the LOM alarm to the incoming side so that any optical card can display this alarm as a TERM alarm.


Clear the LOM Alarm

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

2.7.193  LOP-P

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

SONET 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 the FC_MR-4 card, an LOP-P is 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.)

Clear the LOP-P Alarm


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


Step 1 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 causes the alarm.

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

Refer to the manufacturer's instructions for test-set use.

Step 4 If the error is not due to an incorrectly configured test set, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit for the correct size. For procedures, refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15454 Procedure Guide.

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


2.7.194  LOP-V

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

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

Clear the LOP-V Alarm


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

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


2.7.195  LO-RXPOWER

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

SONET Logical Object: OCN

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

The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, MRC-12, MRC-4, and OC192-XFP card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls below the threshold value, which is user-provisionable.


Note When you upgrade a node to Software Release 6.0 or later, this enables received optical power PMs for the OC3-8, OC192-SR, OC192-IR, OC192-ITU, OC-192-XFP, MRC-12, and MRC25G-4 cards. The newly enabled HI-RXPOWER and LO-RXPOWER alarms require that you initialize a site-accepted optical power (OPR0) nominal value after the upgrade. (To do this, refer to the procedure in the "Turn Up a Node" chapter in the Cisco ONS 15454 Procedure Guide.) When you apply the value change, CTC uses the new OPR0 value to calculate PM percentage values. If you do not change the nominal value, the HI-RXPOWER or LO-RXPOWER may be raised in response to the unmodified setting.



Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.


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 "Maintain the Node" chapter in the Cisco ONS 15454 Procedure 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 reading you get is not as precise, but you 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 "1.4.1  Perform a Facility Loopback on a Source-Node Optical Port" procedure or the "1.4.4  Perform a Facility Loopback on an Intermediate-Node Optical Port" procedure to 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.

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.7.196  LOS (2R)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.197  LOS (BITS)

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

SONET Logical Object: BITS

The LOS (BITS) alarm indicates that the TCC2/TCC2P has an LOS from the BITS timing source. The LOS (BITS) means the BITS clock or the connection to it failed.

Clear the LOS (BITS) Alarm


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


Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 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 (SA) problem.


2.7.198  LOS (DS1)

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

SONET 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. A cabling issue or a configuration issue could cause this alarm. If an upstream equipment failure causes a transmission failure, the LOS (DS1) will likely be demoted by a card-level alarm (to the DS1/E1-56).

Clear the LOS (DS1) Alarm


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


Step 1 Verify that the fiber cable is properly connected and attached from the correct transmitting port to the correct receiving port. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 2 Clean the cable ends using site practices or, if none exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm is raised on a DS1/E1-56 card, verify that the card is placed in the correct service mode by completing the following steps:

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

b. Click the Provisioning > Card tabs.

c. Verify that the Operating Mode column says All DS1 for your errored circuit.

Step 4 For any other DS-1 or DS-3 card, consult site records to determine whether the port raising the alarm has been assigned.

Step 5 If the port is not currently assigned, place the port out of service using the following steps:

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

b. For a DS-1 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 6 For any card, if the port is assigned, verify that the correct one 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 open the card view and complete the following substeps:

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.


Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.


Step 7 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 8 Ensure that the transmit and receive outputs from the DSx patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 9 If there is a valid signal but the alarm does not clear, replace the electrical connector on the ONS 15454.

Step 10 If a valid electrical signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 11 Repeat Steps 1 to 10 for any other port on the card that reports the LOS.

Step 12 If the alarm does not clear, check for any card-level alarm that could affect this port.

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

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


2.7.199  LOS (DS3)

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

SONET Logical Object: DS3

The LOS (DS3) for a DS-3 port occurs when the port on a DS3XM-6, DS3XM-12, or DS3/EC1-48 card is in service but no signal is being received. The alarm is caused by incorrect or dirty cabling, a fiber break, or upstream equipment failure.


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


Clear the LOS (DS3) Alarm


Step 1 Check for any upstream failures in the transmitting equipment.

Step 2 Verify that the cable is properly connected from the transmitting port and attached to the correct receiving port at the node with the LOS. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.


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

Step 3 Clean the cable ends using site practices or, if none exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.

Step 4 Consult site records to determine whether the port raising the alarm has been assigned.

Step 5 If the port is not currently assigned, place the port out of service using the following steps:

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

b. Click the Maintenance > DS3 tabs.

c. Under Admin State, click OOS,DSBLD.

d. Click Apply.

Step 6 If the port is assigned, verify that the correct one 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 open the card view and complete the following substeps:

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.


Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.


Step 7 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 8 Ensure that the transmit and receive outputs from the DSx patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 9 If there is a valid signal but the alarm does not clear, replace the electrical connector on the ONS 15454.

Step 10 If the test set shows signal errors but the cabling is correctly installed and the transmitting device is operational, the existing cabling could still be faulty. Use the test set to locate the bad cable and replace it. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 11 Repeat Steps 1 to 10 for any other port on the card that reports the LOS.

Step 12 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting 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 (SA) problem.


2.7.200  LOS (E1)

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

SONET Logical Object: E1

An LOS (E1) alarm for a DS1/E1-56 card port occurs when the card is placed in All E1 mode and is in service, but the alarmed port is not receiving a signal due to a physical or provisioning problem. The physical causes for the alarm could be incorrectly connected or faulty cabling. The software causes could be improperly configured card or circuit size.

For more information about the DS1/E1-56 card, refer to the "Electrical Cards" chapter in the Cisco ONS 15454 Reference Manual.

Clear the LOS (E1) Alarm


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


Step 1 Verify that the cable is properly connected and attached to the correct port. For more information about connecting cable, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide. Also refer to site records for your specific cabling scheme.

Step 2 Ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 3 Clean the cable using your site practices. If none exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 Procedure Guide.

Step 4 Confirm that the card is properly provisioned to carry the E1 payload:

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

b. Click the Provisioning > Card tabs.

c. Under the Operating Mode column, you should see "All E1." If you see "All DS1," click the drop-down to change it and click Apply.

Step 5 Use a test set to confirm that a valid E1 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.) If the test set shows errors, the cabling could still be faulty despite being correctly installed. Use the tester to isolate the bad section of cable and replace it. Refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide for procedures.

Step 6 Repeat Steps 1 to 5 for any other port on the card that reports the LOS (E1).

Step 7 If the alarm does not clear, look for any card-level alarm that could cause this alarm.

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

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


2.7.201  LOS (EC1)

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

SONET Logical Object: EC1

LOS on an EC1/EC1-12 or DS3/EC1-48 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (EC1) most likely means that the upstream transmitter has failed. If an EC1 LOS alarm is not accompanied by additional alarms, a cabling problem (such as an incorrect attachment, fiber cut, or other fiber error) usually causes this alarm. The condition clears when the problem is corrected, allowing two consecutive valid frames to be received.


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


Clear the LOS (EC1) Alarm


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


Step 1 Check for any upstream equipment failures that could cause the LOS (EC1) in this node.

Step 2 If there is no cause upstream, verify cabling continuity from the transmitting port to the receiving port reporting LOS (EC1) To verify cable continuity, follow site practices.

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

Step 3 If the cabling is good, verify that the correct EC1-12 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 open 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.


Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.


Step 4 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 5 If the signal is valid, ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 6 If a valid signal exists but the alarm does not clear, replace the cable connector on the ONS 15454.

Step 7 Repeat Steps 2 through 6 for any other port on the card that reports the LOS (EC1).

Step 8 If the alarm does not clear, the cabling could still be faulty despite correct attachments. Use the test set to locate the bad cable and replace it using the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide.

Step 9 If the alarm does not clear, look for any card-level alarm that could cause this port alarm.

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

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 (SA) problem.


2.7.202  LOS (ESCON)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.203  LOS (FUDC)

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

SONET 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 has 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. To verify cable continuity, follow site practices.

Step 2 Verify that there is a valid input signal using a test set. For specific procedures to use the test set equipment, consult the manufacturer.

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 "Maintain the Node" chapter in the Cisco ONS 15454 Procedure 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 "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15454 Procedure 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.

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.7.204  LOS (ISC)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.205  LOS (MSUDC)

The LOS (MSUDC) alarm is not used in this platform in this release. It is reserved for future development.

2.7.206  LOS (OCN)

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

SONET 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. It clears when two consecutive valid frames are received.


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

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

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

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


Clear the LOS (OCN) Alarm


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


Step 1 Using site practices, verify fiber continuity to the port.

Step 2 If the cabling is good, 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 open 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.

f. Click Apply.


Note If ports managed into IS admin state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.


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 "Maintain the Node" chapter of the Cisco ONS 15454 Procedure 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 "OC-N Card Transmit and Receive Levels" section lists these specifications for each OC-N card. For DWDM cards, refer to the Cisco ONS 15454 DWDM Reference Manual 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 (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.

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


2.7.207  LOS (OTS)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.208  LOS (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.209  LOS-O

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.210  LOS-P (OCH)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.211  LOS-P (OMS, OTS)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.212  LOS-P (TRUNK)

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.213  LO-TXPOWER

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

SONET Logical Objects: EQPT, OCN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM

The Equipment Low Transmit Power alarm is an indicator for the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, OC192-XFP, OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 155, OC192 LR/STM64 LH ITU 15xx.xx, and MRC-12 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.


Note When there is a LO-TXPOWER alarm on the OC3 IR/STM1 SH 1310-8, OC192 SR/STM64 IO 1310, OC192 IR/STM64 SH 1550, OC192 LR/STM64 LH ITU 15xx.xx, or MRC-12 cards, the alarm is reported at the card equipment level, not the port equipment level. However, on cards with PPMs, the alarms are reported at the port level. So the end result is that the alarms are reported at different levels (port or card equipment), depending on if the port has a replaceable PPM or is a fixed-rate port with no PPM. Because the alarm cannot be isolated to a specific port from the alarm indication on the four cards mentioned, when the LO-TXPOWER alarm occurs and cannot be cleared, it is recommended to change out the entire card (see the procedure in this section).

To see which port on a card is having possible performance problems that may be causing the alarm, see DLP-A507 in the DLPs A500 to A599 chapter of the Cisco ONS 15454 Procedure Guide, R7.0. To change how the performance monitoring (PM) parameters are displayed, see NTP-A253 in the Monitor Performance chapter of the Cisco ONS 15454 Procedure Guide, R7.0.



Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponders and Muxponders" chapter of the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the LO-TXPOWER Alarm


Step 1 Display the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, or OC192-XFP card view.

Step 2 Click the Provisioning > Optics Thresholds > Current Values 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.

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.7.214  LPBKCRS

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

SONET Logical Objects: STSMON, STSTRM

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.

For more information on loopbacks, see the "Troubleshooting Optical Circuit Paths With Loopbacks" section.


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 open the card view.

Step 2 Complete the "Clear an OC-N Card Cross-Connect (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.7.215  LPBKDS1FEAC-CMD

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

SONET Logical Object: DS1

The DS-1 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-1 FEAC loopback on DS3XM-6, DS3XM-12, or DS3/EC1-48 cards. For more information about FEAC loopbacks, see the "Troubleshooting DS3XM-6 or DS3XM-12 Card Electrical Paths With FEAC Loopbacks" section.


Note LPBKDS1FEAC-CMD is an informational condition and does not require troubleshooting.



Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

2.7.216  LPBKDS3FEAC

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

SONET Logical Object