Table Of Contents

Alarm Troubleshooting

2.1  Alarm Index by Default Severity

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  Not Alarmed Conditions (NA)

2.1.5  Not Reported Conditions (NR)

2.2  Alarms and Conditions Indexed By Alphabetical Entry

2.3  Alarm Logical Objects

2.4  Alarm Index 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  Service Effect

2.5.5  States

2.6  Safety Summary

2.7  Alarm Procedures

2.7.1  AIS

Clear the AIS Condition

2.7.2  ALS

2.7.3  AMPLI-INIT

2.7.4  APC-CORRECTION-SKIPPED

2.7.5  APC-DISABLED

Clear the APC-DISABLED Condition

2.7.6  APC-END

2.7.7  APC-OUT-OF-RANGE

Clear the APC-OUT-OF-RANGE Condition

2.7.8  APSB

Clear the APSB Alarm

2.7.9  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.10  APSC-IMP

Clear the APSC-IMP Alarm

2.7.11  APSCINCON

Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing

2.7.12  APSCM

Clear the APSCM Alarm

2.7.13  APSCNMIS

Clear the APSCNMIS Alarm

2.7.14  APSIMP

Clear the APSIMP Condition

2.7.15  AS-CMD

Clear the AS-CMD Condition

2.7.16  AS-MT

Clear the AS-MT Condition

2.7.17  AS-MT-OOG

2.7.18  AU-AIS

Clear the AU-AIS Condition

2.7.19  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.20  AUD-LOG-LOW

2.7.21  AU-LOF

Clear the AU-LOF Alarm

2.7.22  AU-LOP

Clear the AU-LOP Alarm

2.7.23  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.7.24  AUTORESET

Clear the AUTORESET Alarm

2.7.25  AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-SNCP Condition

2.7.26  AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.7.27  AUTOSWSW-PDI-SNCP

2.7.28  AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.7.29  AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.7.30  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

2.7.31  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

2.7.32  AWG-DEG

Clear the AWG-DEG Alarm

2.7.33  AWG-FAIL

Clear the AWG-FAIL Alarm

2.7.34  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.7.35  AWG-WARM-UP

2.7.36  BATFAIL

Clear the BATFAIL Alarm

2.7.37  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.38  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.7.39  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.40  CARLOSS (FC)

2.7.41  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.7.42  CARLOSS (GE)

Clear the CARLOSS (GE) Alarm

2.7.43  CARLOSS (ISC)

Clear the CARLOSS (ISC) Alarm

2.7.44  CARLOSS (ML100T, ML1000)

Clear the CARLOSS (ML100T, ML1000) Alarm

2.7.45  CARLOSS (TRUNK)

Clear the CARLOSS (TRUNK) Alarm

2.7.46  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.7.47  CKTDOWN

2.7.48  CLDRESTART

Clear the CLDRESTART Condition

2.7.49  COMIOXC

Clear the COMIOXC Alarm

2.7.50  COMM-FAIL

Clear the COMM-FAIL Alarm

2.7.51  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.52  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.7.53  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.54  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.55  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.7.56  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.57  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.58  DATAFLT

Clear the DATAFLT Alarm

2.7.59  DBOSYNC

Clear the DBOSYNC Alarm

2.7.60  DS3-MISM

Clear the DS3-MISM Condition

2.7.61  DSP-COMM-FAIL

2.7.62  DSP-FAIL

Clear the DSP-FAIL Alarm

2.7.63  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.64  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.65  E3-ISD

2.7.66  EHIBATVG

Clear the EHIBATVG Alarm

2.7.67  ELWBATVG

Clear the ELWBATVG Alarm

2.7.68  EOC

Clear the EOC Alarm

2.7.69  EOC-L

2.7.70  EQPT

Clear the EQPT Alarm

2.7.71  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.7.72  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.73  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.74  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.75  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.7.76  EXCCOL

Clear the EXCCOL Alarm

2.7.77  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.78  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.7.79  EXT

Clear the EXT Alarm

2.7.80  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.81  FAILTOSW

Clear the FAILTOSW Condition

2.7.82  FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.7.83  FAILTOSW-LO

Clear the FAILTOSW-LO Condition

2.7.84  FAILTOSWR

Clear the FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration

2.7.85  FAILTOSWS

Clear the FAILTOSWS Condition

2.7.86  FAN

Clear the FAN Alarm

2.7.87  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.7.88  FE-AIS

Clear the FE-AIS Condition

2.7.89  FEC-MISM

Clear the FEC-MISM Alarm

2.7.90  FE-DS1-MULTLOS

2.7.91  FE-DS1-NSA

2.7.92  FE-DS1-SA

2.7.93  FE-DS1-SNGLLOS

2.7.94  FE-DS3-NSA

2.7.95  FE-DS3-SA

2.7.96  FE-E1-MULTLOS

Clear the FE-E1-MULTLOS Condition

2.7.97  FE-E1-NSA

Clear the FE-E1-NSA Condition

2.7.98  FE-E1-SA

Clear the FE-E1-SA Condition

2.7.99  FE-E1-SNGLLOS

Clear the FE-E1-SNGLLOS Condition

2.7.100  FE-E3-NSA

Clear the FE-E3-NSA Condition

2.7.101  FE-E3-SA

Clear the FE-E3-SA Condition

2.7.102  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.103  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.7.104  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.105  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.106  FE-IDLE

Clear the FE-IDLE Condition

2.7.107  FE-LOCKOUTOFPR-ALL

2.7.108  FE-LOCKOUTOFPR-RING

2.7.109  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.110  FE-LOCKOUTOFWK-RING

2.7.111  FE-LOCKOUTOFWK-SPAN

2.7.112  FE-LOF

Clear the FE-LOF Condition

2.7.113  FE-LOS

Clear the FE-LOS Condition

2.7.114  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.7.115  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.116  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.117  FEPRLF

Clear the FEPRLF Alarm on an MS-SPRing

2.7.118  FE-SDPRLF

Clear the FE-SDPRLF Alarm on an MS-SPRing

2.7.119  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.7.120  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.121  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.122  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.123  FRCDSWTOINT

2.7.124  FRCDSWTOPRI

2.7.125  FRCDSWTOSEC

2.7.126  FRCDSWTOTHIRD

2.7.127  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.128  FSTSYNC

2.7.129  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.130  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.7.131  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.7.132  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.7.133  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.7.134  GCC-EOC

Clear the GCC-EOC Alarm

2.7.135  GE-OOSYNC

Clear the GE-OOSYNC Alarm

2.7.136  GFP-CSF

Clear the GFP-CSF Alarm

2.7.137  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.7.138  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.7.139  GFP-LFD

Clear the GFP-LFD Alarm

2.7.140  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.7.141  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.7.142  HELLO

Clear the HELLO Alarm

2.7.143  HIBATVG

Clear the HIBATVG Alarm

2.7.144  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.145  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.7.146  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.147  HITEMP

Clear the HITEMP Alarm

2.7.148  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.149  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.150  HP-ENCAP-MISMATCH

Clear the HP-ENCAP-MISMATCH Alarm

2.7.151  HP-RFI

Clear the HP-RFI Condition

2.7.152  HP-TIM

Clear the HP-TIM Alarm

2.7.153  HP-UNEQ

Clear the HP-UNEQ Alarm

2.7.154  I-HITEMP

Clear the I-HITEMP Alarm

2.7.155  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.156  INC-ISD

2.7.157  INHSWPR

Clear the INHSWPR Condition

2.7.158  INHSWWKG

Clear the INHSWWKG Condition

2.7.159  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.160  INVMACADR

2.7.161  IOSCFGCOPY

2.7.162  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.163  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.7.164  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.7.165  LASER-APR

2.7.166  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.7.167  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.7.168  LASEREOL

Clear the LASEREOL Alarm

2.7.169  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.7.170  LCAS-CRC

Clear the LCAS-CRC Condition

2.7.171  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.7.172  LCAS-TX-ADD

2.7.173  LCAS-TX-DNU

2.7.174  LKOUTPR-R

2.7.175  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.176  LKOUTWK-R

2.7.177  LKOUTWK-S

2.7.178  LMP-HELLODOWN

2.7.179  LMP-NDFAIL

2.7.180  LOA

Clear the LOA Alarm

2.7.181  LOCKOUTOFPR

2.7.182  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.183  LOCKOUT-REQ-RING

2.7.184  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.185  LOF (DS3, E1, E4, STM1E, STMN)

Clear the LOF (DS3, E1, E4, STM1E, STMN) Alarm

2.7.186  LOF (TRUNK)

Clear the LOF (TRUNK) Alarm

2.7.187  LO-LASERBIAS

2.7.188  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.7.189  LOM

Clear the LOM Alarm

2.7.190  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.191  LOS (2R)

Clear the LOS (2R) Alarm

2.7.192  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.193  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.194  LOS (E1, E3, E4)

Clear the LOS (E1, E3, E4) Alarm

2.7.195  LOS (ESCON)

2.7.196  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.197  LOS (ISC)

Clear the LOS (ISC) Alarm

2.7.198  LOS (MSUDC)

2.7.199  LOS (OTS)

Clear the LOS (OTS) Alarm

2.7.200  LOS (STM1E, STMN)

Clear the LOS (STM1E, STMN) Alarm

2.7.201  LOS (TRUNK)

Clear the LOS (TRUNK) Alarm

2.7.202  LOS-O

Clear the LOS-O Alarm

2.7.203  LOS-P (OCH)

Clear the LOS-P (OCH) Alarm

2.7.204  LOS-P (OMS, OTS)

Clear the LOS-P (OMS, OTS) Alarm

2.7.205  LOS-P (TRUNK)

Clear the LOS-P (TRUNK) Alarm

2.7.206  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.7.207  LPBKCRS

Clear the LPBKCRS Condition

2.7.208  LPBKDS1FEAC

2.7.209  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.210  LPBKDS3FEAC-CMD

2.7.211  LPBKE1FEAC

2.7.212  LPBKE3FEAC

2.7.213  LPBKE3FEAC-CMD

2.7.214  LPBKFACILITY (DS3)

Clear the LPBKFACILITY (DS3) Condition

2.7.215  LPBKFACILITY (E1, E3, E4)

Clear the LPBKFACILITY (E1, E3, E4) Condition

2.7.216  LPBKFACILITY (ESCON)

2.7.217  LPBKFACILITY (FC)

Clear the LPBKFACILITY (FC) Condition

2.7.218  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.7.219  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.7.220  LPBKFACILITY (GE)

Clear the LPBKFACILITY (GE) Condition

2.7.221  LPBKFACILITY (ISC)

Clear the LPBKFACILITY (ISC) Condition

2.7.222  LPBKFACILITY (STM1E, STMN)

Clear the LPBKFACILITY (STM1E, STMN) Condition

2.7.223  LPBKFACILITY (TRUNK)

Clear the LPBKFACILITY (TRUNK) Condition

2.7.224  LPBKTERMINAL (DS3)

Clear the LPBKTERMINAL (DS3) Condition

2.7.225  LPBKTERMINAL (E1, E3, E4)

Clear the LPBKTERMINAL (E1, E3, E4) Condition

2.7.226  LPBKTERMINAL (ESCON)

2.7.227  LPBKTERMINAL (FC)

Clear the LPBKTERMINAL (FC) Condition

2.7.228  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.7.229  LPBKTERMINAL(G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.7.230  LPBKTERMINAL (GE)

Clear the LPBKTERMINAL (GE) Condition

2.7.231  LPBKTERMINAL (ISC)

Clear the LPBKTERMINAL (ISC) Condition

2.7.232  LPBKTERMINAL (STM1E, STMN)

Clear the LPBKTERMINAL (STM1E, STMN) Condition

2.7.233  LPBKTERMINAL (TRUNK)

Clear the LPBKTERMINAL (TRUNK) Condition

2.7.234  LP-ENCAP-MISMATCH

Clear the LP-ENCAP-MISMATCH Alarm

2.7.235  LP-PLM

Clear the LP-PLM Alarm

2.7.236  LP-RFI

Clear the LP-RFI Condition

2.7.237  LP-TIM

Clear the LP-TIM Alarm

2.7.238  LP-UNEQ

Clear the LP-UNEQ Alarm

2.7.239  LWBATVG

Clear the LWBATVG Alarm

2.7.240  MAN-REQ

Clear the MAN-REQ Condition

2.7.241  MANRESET

2.7.242  MANSWTOINT

2.7.243  MANSWTOPRI

2.7.244  MANSWTOSEC

2.7.245  MANSWTOTHIRD

2.7.246  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.247  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.248  MEA (BIC)

2.7.249  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.250  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.251  MEA (PPM)

Clear the MEA (PPM) Alarm

2.7.252  MEM-GONE

2.7.253  MEM-LOW

2.7.254  MFGMEM (AICI-AEP, AICI-AIE, PPM)

Clear the MFGMEM Alarm

2.7.255  MFGMEM (BPLANE, FAN)

Clear the MFGMEM (BPLANE, FAN) Alarm

2.7.256  MS-AIS

Clear the MS-AIS Condition

2.7.257  MS-EOC

Clear the MS-EOC Alarm

2.7.258  MS-RFI

Clear the MS-RFI Condition

2.7.259  MSSP-OOSYNC

Clear the MSSP-OOSYNC Alarm

2.7.260  NO-CONFIG

Clear the NO-CONFIG Alarm

2.7.261  NOT-AUTHENTICATED

2.7.262  OCHNC-INC

2.7.263  ODUK-1-AIS-PM

Clear the ODUK-1-AIS-PM Condition

2.7.264  ODUK-2-AIS-PM

Clear the ODUK-2-AIS-PM Condition

2.7.265  ODUK-3-AIS-PM

Clear the ODUK-3-AIS-PM Condition

2.7.266  ODUK-4-AIS-PM

Clear the ODUK-4-AIS-PM Condition

2.7.267  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.7.268  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.7.269  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.7.270  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.7.271  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.7.272  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.7.273  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.7.274  OOU-TPT

Clear the OOT-TPT Condition

2.7.275  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.7.276  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.7.277  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.7.278  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.7.279  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.7.280  OSRION

Clear the OSRION Condition

2.7.281  OTUK-AIS

Clear the OTUK-AIS Condition

2.7.282  OTUK-BDI

Clear the OTUK-BDI Condition

2.7.283  OTUK-IAE

2.7.284  OTUK-LOF

Clear the OTUK-LOF Alarm

2.7.285  OTUK-SD

Clear the OTUK-SD Condition

2.7.286  OTUK-SF

Clear the OTUK-SF Condition

2.7.287  OTUK-TIM

Clear the OTUK-TIM Alarm

2.7.288  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.7.289  PARAM-MISM

2.7.290  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.291  PORT-ADD-PWR-DEG-HI

2.7.292  PORT-ADD-PWR-DEG-LOW

2.7.293  PORT-ADD-PWR-FAIL-HI

2.7.294  PORT-ADD-PWR-FAIL-LOW

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

2.7.295  PORT-CODE-MISMATCH

2.7.296  PORT-COMM-FAIL

2.7.297  PORT-FAIL

2.7.298  PORT-MISMATCH

2.7.299  PORT-MISSING

2.7.300  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.301  PROTNA

Clear the PROTNA Alarm

2.7.302  PTIM

Clear the PTIM Alarm

2.7.303  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.304  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.305  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.7.306  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.7.307  RAI

Clear the RAI Condition

2.7.308  RCVR-MISS

Clear the RCVR-MISS Alarm

2.7.309  RFI

Clear the RFI Condition

2.7.310  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.7.311  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.312  RING-SW-EAST

2.7.313  RING-SW-WEST

2.7.314  RSVP-HELLODOWN

2.7.315  RUNCFG-SAVENEED

2.7.316  SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)

Clear the SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP) Condition

2.7.317  SD (TRUNK)

Clear the SD (TRUNK) Condition

2.7.318  SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.7.319  SD-L

2.7.320  SD-V

2.7.321  SF (DS3, E1, E3, E4, STMN, VCTRM-LP)

Clear the SF (DS3, E1, E3, E4, STMN, VCTRM-LP) Condition

2.7.322  SF (TRUNK)

Clear the SF (TRUNK) Condition

2.7.323  SFBER-EXCEED-HO

Clear the SFBER-EXCEED-HO Condition

2.7.324  SF-L

2.7.325  SFTWDOWN

2.7.326  SF-V

2.7.327  SH-INS-LOSS-VAR-DEG-HIGH

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

2.7.328  SH-INS-LOSS-VAR-DEG-LOW

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

2.7.329  SHUTTER-OPEN

Clear the SHUTTER-OPEN Alarm

2.7.330  SIGLOSS

Clear the SIGLOSS Alarm

2.7.331  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.332  SPAN-SW-EAST

2.7.333  SPAN-SW-WEST

2.7.334  SQUELCH

Clear the SQUELCH Condition

2.7.335  SQUELCHED

Clear the SQUELCHED Condition

2.7.336  SQM

Clear the SQM Alarm

2.7.337  SSM-DUS

2.7.338  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.339  SSM-LNC

2.7.340  SSM-OFF

2.7.341  SSM-PRC

2.7.342  SSM-PRS

2.7.343  SSM-RES

2.7.344  SSM-SDH-TN

2.7.345  SSM-SETS

2.7.346  SSM-SMC

2.7.347  SSM-ST2S

2.7.348  SSM-ST3

2.7.349  SSM-ST3E

2.7.350  SSM-ST4

2.7.351  SSM-STU

Clear the SSM-STU Condition

2.7.352  SSM-TNC

2.7.353  SWMTXMOD

Clear the SWMTXMOD Alarm

2.7.354  SWTOPRI

2.7.355  SWTOSEC

2.7.356  SWTOTHIRD

2.7.357  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.358  SYNCLOSS

Clear the SYNCLOSS Alarm

2.7.359  SYNCPRI

Clear the SYNCPRI Alarm

2.7.360  SYNCSEC

Clear the SYNCSEC Alarm

2.7.361  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.362  SYSBOOT

2.7.363  TEMP-MISM

Clear the TEMP-MISM Condition

2.7.364  TIM

Clear the TIM Alarm

2.7.365  TIM-MON

Clear the TIM-MON Alarm

2.7.366  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.7.367  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.7.368  TPTFAIL (ML100T, ML1000)

Clear the TPTFAIL (ML100T, ML1000) Alarm

2.7.369  TRMT

Clear the TRMT Alarm

2.7.370  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.371  TU-AIS

Clear the TU-AIS Condition

2.7.372  TU-LOP

Clear the TU-LOP Alarm

2.7.373  TX-AIS

Clear the TX-AIS Condition

2.7.374  TX-RAI

Clear the TX-RAI Condition

2.7.375  UNC-WORD

Clear the UNC-WORD Condition

2.7.376  UNREACHABLE-TARGET-POWER

2.7.377  UT-COMM-FAIL

Clear the UT-COMM-FAIL Alarm

2.7.378  UT-FAIL

Clear the UT-FAIL Alarm

2.7.379  VCG-DEG

Clear the VCG-DEG Condition

2.7.380  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.381  VOA-HDEG

Clear the VOA-HDEG Alarm

2.7.382  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.7.383  VOA-LDEG

Clear the VOA-LDEG Alarm

2.7.384  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.7.385  VOLT-MISM

Clear the VOLT-MISM Condition

2.7.386  WKSWPR

Clear the WKSWPR Condition

2.7.387  WTR

2.7.388  WVL-MISMATCH

Clear the WVL-MISMATCH Alarm

2.8  DWDM Card LED Activity

2.8.1  DWDM Card LED Activity After Insertion

2.8.2  DWDM Card LED Activity During Reset

2.9  Traffic Card LED Activity

2.9.1  Typical Traffic Card LED Activity After Insertion

2.9.2  Typical Traffic Card LED Activity During Reset

2.9.3  Typical Card LED State After Successful Reset

2.9.4  Typical Cross-Connect LED Activity During Side Switch

2.10  Frequently Used Alarm Troubleshooting Procedures

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

Identify an MS-SPRing Ring Name or Node ID Number

Change an MS-SPRing Ring Name

Change an MS-SPRing Node ID Number

Verify Node Visibility for Other Nodes

2.10.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Protection Port Manual Switch Command

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

Initiate a Card or Port Lock On Command

Initiate a Card or Port Lock Out Command

Clear a Card or Port Lock On or Lock Out Command

Initiate a 1:1 Card Switch Command

Initiate a Force Switch for All Circuits on an SNCP Span

Initiate a Manual Switch for All Circuits on an SNCP Span

Initiate a Lock-Out-of-Protect Switch for All Circuits on an SNCP Span

Clear an SNCP Span External Switching Command

Initiate a Force Ring Switch on an MS-SPRing

Initiate a Force Span Switch on a Four-Fiber MS-SPRing

Initiate a Manual Ring Switch on an MS-SPRing

Initiate a Lockout on an MS-SPRing Protect Span

Initiate an Exercise Ring Switch on an MS-SPRing

Initiate an Exercise Ring Switch on a Four Fiber MS-SPRing

Clear a MS-SPRing External Switching Command

2.10.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Reset an Active TCC2/TCC2P and Activate the Standby Card

Reset the Standby TCC2/TCC2P Card

Side Switch the Active and Standby XC10G Cross-Connect Cards

2.10.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.10.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node SDCC Terminations

Clear an STM-N Card Facility or Terminal Loopback Circuit

Clear an STM-N Card XC Loopback Circuit

Clear a DS3i-N-12 Card Loopback Circuit

Clear EC Card or or G-Series Card Loopbacks

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

Clear a CE-100T-8 Ethernet Card Loopback Circuit

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

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 SDH alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15454 SDH alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all ONS 15454 SDH alarm logical objects, which are the basis of the alarm profile list in Table 2-8.

An alarm's troubleshooting procedure applies to the Cisco Transport Controller (CTC) 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

More information about alarm profile information modification and downloads is located in the Cisco ONS 15454 SDH Procedure Guide Chapter 7, "Manage Alarms."

2.1  Alarm Index by Default Severity

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

---

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

---

The following tables group alarms and conditions by the severity displayed in the CTC Alarms window in the severity (SEV) column. All severities listed in this manual are the default profile settings. Alarm severities can be altered from default settings for individual alarms or groups of alarms by creating a nondefault alarm profile and applying it on a port, card, or shelf basis. All settings (default or user-defined) that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in situations that do not affect service.

---

Note The CTC default alarm profile in some cases contains two severities for one alarm (for example, MJ/MN). The ONS 15454 SDH 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 when there is no effect on service.

---

2.1.1  Critical Alarms (CR)

Table 2-1 alphabetically lists ONS 15454 SDH Critical alarms.

Table 2-1 ONS 15454 SDH Critical Alarm Index 

AU-LOP	HP-TIM	LOS-P (OMS, OTS)
AUTOLSROFF	HP-UNEQ	LOS-P (TRUNK)
AWG-FAIL	I-HITEMP	MEA (EQPT)
AWG-OVERTEMP	IMPROPRMVL	MEA (FAN)
BKUPMEMP	LOA	MEA (PPM)
COMIOXC	LOF (DS3, E1, E4, STM1E, STMN)	MFGMEM (AICI-AEP, AICI-AIE, PPM)
CTNEQPT-PBPROT	LOF (TRUNK)	MFGMEM (BPLANE, FAN)
CTNEQPT-PBWORK	LOM	OPWR-HFAIL
EQPT	LOS (2R)	OPWR-LFAIL
EQPT-DIAG	LOS (DS3)	OTUK-LOF
EQPT-MISS	LOS (E1, E3, E4)	SQM
FAN	LOS (ISC)	SWMTXMOD
GAIN-HFAIL	LOS (OTS)	TIM
GAIN-LFAIL	LOS (STM1E, STMN)	VOA-HFAIL
GE-OOSYNC	LOS (TRUNK)	VOA-LFAIL
HITEMP	LOS-P (OCH)

2.1.2  Major Alarms (MJ)

Table 2-2 alphabetically lists ONS 15454 SDH Major alarms.

Table 2-2 ONS 15454 SDH Major Alarm Index 

APSCM	EXTRA-TRAF-PREEMPT	LWBATVG
APSCNMIS	FC-NO-CREDITS	MEM-GONE
AU-LOF	FEC-MISM	MS-EOC
BATFAIL	GFP-CSF	MSSP-OOSYNC
CARLOSS (E100T, E1000F)	GFP-DE-MISMATCH	OOU-TPT
CARLOSS (EQPT)	GFP-EX-MISMATCH	PEER-NORESPONSE
CARLOSS (FC)	GFP-LFD	PRC-DUPID
CARLOSS (G1000)	GFP-NO-BUFFERS	RCVR-MISS
CARLOSS (GE)	GFP-UP-MISMATCH	RING-ID-MIS
CARLOSS (ISC)	HIBATVG	RING-MISMATCH
CARLOSS (ML100T, ML1000)	HLDOVRSYNC	SIGLOSS
CARLOSS (TRUNK)	HP-ENCAP-MISMATCH	SQM
CONTBUS-A-18	INVMACADR	SYNCLOSS
CONTBUS-B-18	LASERBIAS-FAIL	SYSBOOT
CONTBUS-IO-A	LOF (BITS)	TPTFAIL (FCMR)
CONTBUS-IO-B	LOF (DS3, E1, E4, STM1E, STMN)	TPTFAIL (G1000)
DBOSYNC	LOS (BITS)	TPTFAIL (ML100T, ML1000)
DSP-COMM-FAIL	LOS (DS3)	TRMT
DSP-FAIL	LOS (E1, E3, E4)	TRMT-MISS
DUP-IPADDR	LP-ENCAP-MISMATCH	TU-LOP
DUP-NODENAME	LP-PLM	UT-COMM-FAIL
EHIBATVG	LP-TIM	UT-FAIL
ELWBATVG	LP-UNEQ	WVL-MISMATCH
E-W-MISMATCH

2.1.3  Minor Alarms (MN)

Table 2-3 alphabetically lists ONS 15454 SDH Minor alarms.

Table 2-3 ONS 15454 SDH Minor Alarm Index 

APSB	HELLO	OPWR-LDEG
APSCDFLTK	HI-LASERBIAS	PORT-ADD-PWR-FAIL-LOW
APSC-IMP	HI-LASERTEMP	PROTNA
APSCINCON	HI-RXPOWER	PTIM
AUTORESET	HITEMP	PWR-FAIL-A
AUTOSW-LOP-SNCP	HI-TXPOWER	PWR-FAIL-B
AWG-DEG	HP-TIM	PWR-FAIL-RET-A
CASETEMP-DEG	HP-UNEQ	PWR-FAIL-RET-B
COMM-FAIL	KBYTE-APS-CHANNEL-FAILURE	SFTWDOWN
DATAFLT	LASERBIAS-DEG	SH-INS-LOSS-VAR-DEG-HIGH
EOC	LASEREOL	SH-INS-LOSS-VAR-DEG-LOW
ERROR-CONFIG	LASERTEMP-DEG	SNTP-HOST
EXCCOL	LCAS-CRC	SSM-FAIL
EXT	LO-LASERTEMP	SYNCPRI
FEPRLF	LO-RXPOWER	SYNCSEC
FE-SDPRLF	LOS (FUDC)	SYNCSEC
FIBERTEMP-DEG	LOS-O	TIM-MON
FSTSYNC	LO-TXPOWER	UNREACHABLE-TARGET-POWER
GAIN-HDEG	MEM-LOW	VOA-HDEG
GAIN-LDEG	NOT-AUTHENTICATED	VOA-HFAIL
GCC-EOC	OPWR-HDEG

2.1.4  Not Alarmed Conditions (NA)

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

Table 2-4 ONS 15454 SDH Not Alarmed Conditions Index 

ALS	FORCED-REQ-SPAN	MANSWTOSEC
APC-CORRECTION-SKIPPED	FRCDSWTOINT	MANSWTOTHIRD
APC-DISABLED	FRCDSWTOPRI	MANUAL-REQ-RING
APC-END	FRCDSWTOSEC	MANUAL-REQ-SPAN
APC-OUT-OF-RANGE	FRCDSWTOTHIRD	NO-CONFIG
APSIMP	FRNGSYNC	ODUK-SD-PM
AS-CMD	FULLPASSTHR-BI	ODUK-SF-PM
AS-MT	HI-LASERBIAS	ODUK-TIM-PM
AUD-LOG-LOSS	HI-LASERTEMP	OOU-TPT
AUD-LOG-LOW	INC-ISD	OSRION
AUTOSW-LOP-SNCP	INHSWPR	OTUK-SD
AUTOSW-SDBER-SNCP	INHSWWKG	OTUK-SF
AUTOSW-SFBER-SNCP	INTRUSION-PSWD	OTUK-TIM
AUTOSW-UNEQ-SNCP (VCMON-HP)	IOSCFGCOPY	PARAM-MISM
AUTOSW-UNEQ-SNCP (VCMON-LP)	KB-PASSTHR	PORT-MISMATCH
AWG-WARM-UP	LAN-POL-REV	RAI
CLDRESTART	LASER-APR	RING-SW-EAST
CTNEQPT-MISMATCH	LCAS-RX-FAIL	RING-SW-WEST
DS3-MISM	LCAS-TX-ADD	RUNCFG-SAVENEED
E3-ISD	LCAS-TX-DNU	SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)
ETH-LINKLOSS	LKOUTPR-S	SD (TRUNK)
EXERCISE-RING-FAIL	LOCKOUT-REQ	SDBER-EXCEED-HO
EXERCISE-SPAN-FAIL	LPBKCRS	SF (DS3, E1, E3, E4, STMN, VCTRM-LP)
FAILTOSW	LPBKDS3FEAC	SF (TRUNK)
FAILTOSW-HO	LPBKDS3FEAC-CMD	SFBER-EXCEED-HO
FAILTOSW-LO	LPBKFACILITY (DS3)	SHUTTER-OPEN
FAILTOSWR	LPBKFACILITY (E1, E3, E4)	SPAN-SW-EAST
FAILTOSWS	LPBKFACILITY (ESCON)	SPAN-SW-WEST
FE-AIS	LPBKFACILITY (FC)	SQUELCH
FE-E1-MULTLOS	LPBKFACILITY (FCMR)	SQUELCHED
FE-E1-NSA	LPBKFACILITY (G1000)	SSM-DUS
FE-E1-SA	LPBKFACILITY (GE)	SSM-LNC
FE-E1-SNGLLOS	LPBKFACILITY (ISC)	SSM-OFF
FE-E3-NSA	LPBKFACILITY (STM1E, STMN)	SSM-PRC
FE-E3-SA	LPBKFACILITY (TRUNK)	SSM-SETS
FE-EQPT-NSA	LPBKTERMINAL (DS3)	SSM-STU
FE-FRCDWKSWBK-SPAN	LPBKTERMINAL (E1, E3, E4)	SSM-TNC
FE-FRCDWKSWPR-RING	LPBKTERMINAL (FC)	SWTOPRI
FE-FRCDWKSWPR-SPAN	LPBKTERMINAL (FCMR)	SWTOSEC
FE-IDLE	LPBKTERMINAL(G1000)	SWTOTHIRD
FE-LOCKOUTOFPR-SPAN	LPBKTERMINAL (GE)	SYNC-FREQ
FE-LOF	LPBKTERMINAL (ISC)	TX-RAI
FE-LOS	LPBKTERMINAL (STM1E, STMN)	UNC-WORD
FE-MANWKSWBK-SPAN	LPBKTERMINAL (TRUNK)	VCG-DEG
FE-MANWKSWPR-RING	MAN-REQ	VCG-DOWN
FE-MANWKSWPR-SPAN	MANRESET	VOLT-MISM
FORCED-REQ	MANSWTOINT	WKSWPR
FORCED-REQ-RING	MANSWTOPRI	WTR

2.1.5  Not Reported Conditions (NR)

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

Table 2-5 ONS 15454 SDH Not Reported Conditions Index 

AIS	ODUK-1-AIS-PM	ODUK-OCI-PM
AU-AIS	ODUK-2-AIS-PM	OTUK-AIS
AUTOSW-AIS-SNCP	ODUK-3-AIS-PM	OTUK-BDI
HP-RFI	ODUK-4-AIS-PM	RFI
LP-RFI	ODUK-AIS-PM	TU-AIS
MS-AIS	ODUK-BDI-PM	TX-AIS
MS-RFI	ODUK-LCK-PM

2.2  Alarms and Conditions Indexed By Alphabetical Entry

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

Table 2-6 ONS 15454 SDH Alarm and Condition Alphabetical Index 

AIS	GAIN-HDEG	MS-RFI
ALS	GAIN-HFAIL	MSSP-OOSYNC
AMPLI-INIT	GAIN-LDEG	NO-CONFIG
APC-CORRECTION-SKIPPED	GAIN-LFAIL	NOT-AUTHENTICATED
APC-DISABLED	GCC-EOC	OCHNC-INC
APC-END	GE-OOSYNC	ODUK-1-AIS-PM
APC-OUT-OF-RANGE	GFP-CSF	ODUK-2-AIS-PM
APSB	GFP-DE-MISMATCH	ODUK-3-AIS-PM
APSCDFLTK	GFP-EX-MISMATCH	ODUK-4-AIS-PM
APSC-IMP	GFP-LFD	ODUK-AIS-PM
APSCINCON	GFP-NO-BUFFERS	ODUK-BDI-PM
APSCM	GFP-UP-MISMATCH	ODUK-LCK-PM
APSCNMIS	HELLO	ODUK-OCI-PM
APSIMP	HIBATVG	ODUK-SD-PM
AS-CMD	HI-LASERBIAS	ODUK-SF-PM
AS-MT	HI-LASERTEMP	ODUK-TIM-PM
AU-AIS	HI-RXPOWER	OOU-TPT
AUD-LOG-LOSS	HITEMP	OPTNTWMIS
AUD-LOG-LOW	HI-TXPOWER	OPWR-HDEG
AU-LOF	HLDOVRSYNC	OPWR-HFAIL
AU-LOP	HP-ENCAP-MISMATCH	OPWR-LDEG
AUTOLSROFF	HP-RFI	OPWR-LFAIL
AUTORESET	HP-TIM	OSRION
AUTOSW-AIS-SNCP	HP-UNEQ	OTUK-AIS
AUTOSW-LOP-SNCP	I-HITEMP	OTUK-BDI
AUTOSW-SDBER-SNCP	IMPROPRMVL	OTUK-IAE
AUTOSW-SFBER-SNCP	INC-ISD	OTUK-LOF
AUTOSW-UNEQ-SNCP (VCMON-HP)	INHSWPR	OTUK-SD
AUTOSW-UNEQ-SNCP (VCMON-LP)	INHSWWKG	OTUK-SF
AWG-DEG	INTRUSION-PSWD	OTUK-TIM
AWG-FAIL	INVMACADR	OUT-OF-SYNC
AWG-OVERTEMP	IOSCFGCOPY	PARAM-MISM
AWG-WARM-UP	KB-PASSTHR	PEER-NORESPONSE
BATFAIL	KBYTE-APS-CHANNEL-FAILURE	PORT-ADD-PWR-DEG-HI
BKUPMEMP	LAN-POL-REV	PORT-ADD-PWR-DEG-LOW
CARLOSS (E100T, E1000F)	LASER-APR	PORT-ADD-PWR-FAIL-HI
CARLOSS (EQPT)	LASERBIAS-DEG	PORT-ADD-PWR-FAIL-LOW
CARLOSS (FC)	LASERBIAS-FAIL	PORT-MISMATCH
CARLOSS (G1000)	LASEREOL	PRC-DUPID
CARLOSS (GE)	LASERTEMP-DEG	PROTNA
CARLOSS (ISC)	LCAS-CRC	PTIM
CARLOSS (ML100T, ML1000)	LCAS-RX-FAIL	PWR-FAIL-A
CARLOSS (TRUNK)	LCAS-TX-ADD	PWR-FAIL-B
CASETEMP-DEG	LCAS-TX-DNU	PWR-FAIL-RET-A
CKTDOWN	LKOUTPR-R	PWR-FAIL-RET-B
CLDRESTART	LKOUTPR-S	RAI
COMIOXC	LKOUTWK-R	RCVR-MISS
COMM-FAIL	LKOUTWK-S	RFI
CONTBUS-A-18	LMP-HELLODOWN	RING-ID-MIS
CONTBUS-B-18	LMP-NDFAIL	RING-MISMATCH
CONTBUS-IO-A	LOA	RING-SW-EAST
CONTBUS-IO-B	LOCKOUTOFPR	RING-SW-WEST
CTNEQPT-MISMATCH	LOCKOUT-REQ	RSVP-HELLODOWN
CTNEQPT-PBPROT	LOCKOUT-REQ-RING	RUNCFG-SAVENEED
CTNEQPT-PBWORK	LOF (BITS)	SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)
DATAFLT	LOF (DS3, E1, E4, STM1E, STMN)	SD (TRUNK)
DBOSYNC	LOF (TRUNK)	SDBER-EXCEED-HO
DS3-MISM	LO-LASERTEMP	SD-L
DSP-COMM-FAIL	LOM	SD-V
DSP-FAIL	LO-RXPOWER	SF (DS3, E1, E3, E4, STMN, VCTRM-LP)
DUP-IPADDR	LOS (2R)	SF (TRUNK)
DUP-NODENAME	LOS (BITS)	SFBER-EXCEED-HO
E3-ISD	LOS (DS3)	SF-L
EHIBATVG	LOS (E1, E3, E4)	SFTWDOWN
ELWBATVG	LOS (ESCON)	SF-V
EOC	LOS (FUDC)	SH-INS-LOSS-VAR-DEG-HIGH
EOC-L	LOS (ISC)	SH-INS-LOSS-VAR-DEG-LOW
EQPT	LOS (MSUDC)	SHUTTER-OPEN
EQPT-DIAG	LOS (OTS)	SIGLOSS
EQPT-MISS	LOS (STM1E, STMN)	SNTP-HOST
ERROR-CONFIG	LOS (TRUNK)	SPAN-SW-EAST
ETH-LINKLOSS	LOS-O	SPAN-SW-WEST
E-W-MISMATCH	LOS-P (OCH)	SQUELCH
EXCCOL	LOS-P (OMS, OTS)	SQUELCHED
EXERCISE-RING-FAIL	LOS-P (TRUNK)	SQM
EXERCISE-SPAN-FAIL	LO-TXPOWER	SSM-DUS
EXT	LPBKCRS	SSM-FAIL
EXTRA-TRAF-PREEMPT	LPBKDS1FEAC	SSM-LNC
FAILTOSW	LPBKDS3FEAC	SSM-OFF
FAILTOSW-HO	LPBKDS3FEAC-CMD	SSM-PRC
FAILTOSW-LO	LPBKE1FEAC	SSM-PRS
FAILTOSWR	LPBKE3FEAC	SSM-RES
FAILTOSWS	LPBKE3FEAC-CMD	SSM-SDH-TN
FAN	LPBKFACILITY (DS3)	SSM-SETS
FC-NO-CREDITS	LPBKFACILITY (E1, E3, E4)	SSM-SMC
FE-AIS	LPBKFACILITY (ESCON)	SSM-ST2S
FEC-MISM	LPBKFACILITY (FC)	SSM-ST3
FE-DS1-MULTLOS	LPBKFACILITY (FCMR)	SSM-ST3E
FE-DS1-NSA	LPBKFACILITY (G1000)	SSM-ST4
FE-DS1-SA	LPBKFACILITY (GE)	SSM-STU
FE-DS1-SNGLLOS	LPBKFACILITY (ISC)	SSM-TNC
FE-DS3-NSA	LPBKFACILITY (STM1E, STMN)	SWMTXMOD
FE-DS3-SA	LPBKFACILITY (TRUNK)	SWTOPRI
FE-E1-MULTLOS	LPBKTERMINAL (DS3)	SWTOSEC
FE-E1-NSA	LPBKTERMINAL (E1, E3, E4)	SWTOTHIRD
FE-E1-SA	LPBKTERMINAL (ESCON)	SYNC-FREQ
FE-E1-SNGLLOS	LPBKTERMINAL (FC)	SYNCLOSS
FE-E3-NSA	LPBKTERMINAL (FCMR)	SYNCPRI
FE-E3-SA	LPBKTERMINAL(G1000)	SYNCSEC
FE-EQPT-NSA	LPBKTERMINAL (GE)	SYNCTHIRD
FE-FRCDWKSWBK-SPAN	LPBKTERMINAL (ISC)	SYSBOOT
FE-FRCDWKSWPR-RING	LPBKTERMINAL (STM1E, STMN)	TEMP-MISM
FE-FRCDWKSWPR-SPAN	LPBKTERMINAL (TRUNK)	TIM
FE-IDLE	LP-ENCAP-MISMATCH	TIM-MON
FE-LOCKOUTOFPR-ALL	LP-PLM	TPTFAIL (FCMR)
FE-LOCKOUTOFPR-RING	LP-RFI	TPTFAIL (G1000)
FE-LOCKOUTOFPR-SPAN	LP-TIM	TPTFAIL (ML100T, ML1000)
FE-LOCKOUTOFWK-RING	LP-UNEQ	TRMT
FE-LOCKOUTOFWK-SPAN	LWBATVG	TRMT-MISS
FE-LOF	MAN-REQ	TU-AIS
FE-LOS	MANRESET	TU-LOP
FE-MANWKSWBK-SPAN	MANSWTOINT	TX-AIS
FE-MANWKSWPR-RING	MANSWTOPRI	TX-RAI
FE-MANWKSWPR-SPAN	MANSWTOSEC	UNC-WORD
FEPRLF	MANSWTOTHIRD	UNREACHABLE-TARGET-POWER
FE-SDPRLF	MANUAL-REQ-RING	UT-COMM-FAIL
FIBERTEMP-DEG	MANUAL-REQ-SPAN	UT-FAIL
FORCED-REQ	MEA (BIC)	VCG-DEG
FORCED-REQ-RING	MEA (EQPT)	VCG-DOWN
FORCED-REQ-SPAN	MEA (FAN)	VOA-HDEG
FRCDSWTOINT	MEA (PPM)	VOA-HFAIL
FRCDSWTOPRI	MEM-GONE	VOA-LDEG
FRCDSWTOSEC	MEM-LOW	VOA-LFAIL
FRCDSWTOTHIRD	MFGMEM (AICI-AEP, AICI-AIE, PPM)	VOLT-MISM
FRNGSYNC	MFGMEM (BPLANE, FAN)	WKSWPR
FSTSYNC	MS-AIS	WTR
FULLPASSTHR-BI	MS-EOC	WVL-MISMATCH

2.3  Alarm Logical Objects

The CTC alarm profile list organizes all alarms and conditions according to the logical objects they are raised against. These logical objects represent physical objects such as cards, logical objects such as circuits, or transport and signal monitoring entities such as the SDH or ITU-T G.709 optical overhead bits. One alarm might appear in multiple entries when it can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (STM-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both STM-N: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 "STMN" logical object refers to the STM-N signal. Logical object names or industry-standard terms are used within the entries as appropriate.

---

Table 2-7 Alarm Logical Object Type Definition 

Object Type	Definition
2R	Reshape and retransmit (used for transponder [TXP] cards).
AICI-AEP	Alarm Interface Controller-International—Alarm expansion panel.
AIP	Alarm Interface Panel.
AOTS	Amplified optical transport section.
BIC	Backplane interface connector.
BITS	Building integration timing supply incoming references (BITS-1, BITS-2).
BPLANE	The backplane.
DS3	A DS-3 signal on a DS3i-N-12 card.
E1	E1-42 card.
E3	E3-12 card.
E4	Line type supported by the STM1E card.
E1000F	An E1000-2-G card.
E100T	An E100T-G card.
ENVALRM	An environmental alarm port.
EQPT	A card, its physical objects, and 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, STS, and VT.
ESCON	Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G.
EXT-SREF	BITS outgoing references (SYNC-BITS1, SYNC-BITS2).
FAN	Fan-tray assembly.
FC	Fibre Channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E.
FCMR	An FC_MR-4 Fibre Channel card.
FUDC	SDH F1 byte user data channel for ONS 15454 SDH ML-Series Ethernet cards.
G1000	The ONS 15454 SDH G1000-4 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 MXP and TXP cards.
ML1000	The ONS 15454 SDH ML1000-2 card.
ML100T	The ONS 15454 SDH ML100T-2 or ML100T-8 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 a dense wavelength division multiplexing (DWDM) cards.
OCHNC-CONN	The optical channel connection, referring to DWDM cards.
OMS	Optical multiplex section.
OTS	Optical transport section.
PWR	Power equipment.
PPM	Pluggable port module, referring to all MXP and TXP cards.
STM1E	Synchronous transfer mode 1 (speed) electrical interface
STMN	An STM-N line on an STM-N card.
VCTRM-HP	STS alarm detection at termination (downstream from the cross-connect).
TRUNK	The optical or DWDM card carrying the high-speed signal; referring to MXP, TXP, or ML-Series cards.
UCP-CKT	Unified control plane circuit.
UCP-IPCC	Unified control plane IP control channel.
UCP-NBR	Unified control plane neighbor.
VCG	ONS 15454 SDH virtual concatenation group of virtual tributaries (VT).
VCMON-HP	High-order path virtual concatenation monitoring.
VCMON-LP	VT1 alarm detection at the monitor point (upstream from the cross-connect).
VCTRM-HP	Low-order path virtual concatenation monitoring.
VCTRM-LP	VT1 alarm detection at termination (downstream from the cross-connect).

2.4  Alarm Index by Logical Object Type

Table 2-8 lists all ONS 15454 SDH Release 5.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. Each entry contains a page number that refers to an alarm description in this chapter. Where appropriate, the alarm entries also contain troubleshooting procedures.

---

Note In a mixed network containing different types of nodes (such as ONS 15310, ONS 15454 SDH, and ONS 15600), the initially displayed alarm list in the Provisioning > Alarm Profiles > Alarm Profile Editor tab lists all conditions 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 Index by Logical Object Type 

2R:ALS	FCMR:GFP-EX-MISMATCH	STMN:APSCINCON
2R:AS-CMD	FCMR:GFP-LFD	STMN:APSCM
2R:AS-MT	FCMR:GFP-NO-BUFFERS	STMN:APSCNMIS
2R:FAILTOSW	FCMR:GFP-UP-MISMATCH	STMN:APSIMP
2R:FORCED-REQ-SPAN	FC:LPBKFACILITY (FC)	STMN:AS-CMD
2R:HI-LASERBIAS	FC:LPBKTERMINAL (FC)	STMN:AS-MT
2R:HI-RXPOWER	FC:MANUAL-REQ-SPAN	STMN:AUTOLSROFF
2R:HI-TXPOWER	FC:OUT-OF-SYNC	STMN:E-W-MISMATCH
2R:LOCKOUT-REQ	FC:SIGLOSS	STMN:EOC
2R:LO-RXPOWER	FC:SYNCLOSS	STMN:EXERCISE-RING-FAIL
2R:LOS (2R)	FC:WKSWPR	STMN:EXERCISE-SPAN-FAIL
2R:LO-TXPOWER	FC:WTR	STMN:EXTRA-TRAF-PREEMPT
2R:MANUAL-REQ-SPAN	FCMR:AS-CMD	STMN:FAILTOSW
2R:SQUELCHED	FCMR:AS-MT	STMN:FAILTOSWR
2R:WKSWPR	FCMR:FC-NO-CREDITS	STMN:FAILTOSWS
2R:WTR	FCMR:LPBKFACILITY (FCMR)	STMN:FE-FRCDWKSWBK-SPAN
AICI-AEP: EQPT	FCMR:LPBKTERMINAL (FCMR)	STMN:FE-FRCDWKSWPR-RING
AICI-AEP:MFGMEM (AICI-AEP, AICI-AIE, PPM)	FCMR:PORT-MISMATCH	STMN:FE-FRCDWKSWPR-SPAN
AICI-AIE:EQPT	FCMR:SIGLOSS	STMN:FE-LOCKOUTOFPR-ALL
AICI-AIE:MFGMEM (AICI-AEP, AICI-AIE, PPM)	FCMR:SYNCLOSS	STMN:FE-LOCKOUTOFPR-RING
AOTS:ALS	FCMR:TPTFAIL (FCMR)	STMN:FE-LOCKOUTOFPR-SPAN
AOTS:AMPLI-INIT	FUDC:AIS	STMN:FE-LOCKOUTOFWK-RING
AOTS:APC-CORRECTION-SKIPPED	FUDC:LOS (FUDC)	STMN:FE-LOCKOUTOFWK-SPAN
AOTS:APC-OUT-OF-RANGE	G1000:AS-CMD	STMN:FE-MANWKSWBK-SPAN
AOTS:AS-CMD	G1000:AS-MT	STMN:FE-MANWKSWPR-RING
AOTS:AS-MT	G1000:CARLOSS (G1000)	STMN:FE-MANWKSWPR-SPAN
AOTS:CASETEMP-DEG	G1000:LPBKFACILITY (G1000)	STMN:FE-SDPRLF
AOTS:FIBERTEMP-DEG	G1000:LPBKTERMINAL(G1000)	STMN:FEPRLF
AOTS:GAIN-HDEG	G1000:TPTFAIL (G1000)	STMN:FORCED-REQ-RING
AOTS:GAIN-HFAIL	GE:ALS	STMN:FORCED-REQ-SPAN
AOTS:GAIN-LDEG	GE:AS-CMD	STMN:FULLPASSTHR-BI
AOTS:GAIN-LFAIL	GE:AS-MT	STMN:HELLO
AOTS:LASER-APR	GE:CARLOSS (GE)	STMN:HI-LASERBIAS
AOTS:LASERBIAS-DEG	GE:FAILTOSW	STMN:HI-LASERTEMP
AOTS:LASERBIAS-FAIL	GE:FORCED-REQ-SPAN	STMN:HI-RXPOWER
AOTS:LASERTEMP-DEG	GE:GE-OOSYNC	STMN:HI-TXPOWER
AOTS:OPWR-HDEG	GE:HI-LASERBIAS	STMN:KB-PASSTHR
AOTS:OPWR-HFAIL	GE:HI-RXPOWER	STMN:KBYTE-APS-CHANNEL-FAILURE
AOTS:OPWR-LDEG	GE:HI-TXPOWER	STMN:LASEREOL
AOTS:OPWR-LFAIL	GE:LOCKOUT-REQ	STMN:LKOUTPR-R
AOTS:OSRION	GE:LO-RXPOWER	STMN:LKOUTPR-S
AOTS:PARAM-MISM	GE:LO-TXPOWER	STMN:LKOUTWK-R
AOTS:VOA-HDEG	GE:LPBKFACILITY (GE)	STMN:LKOUTWK-S
AOTS:VOA-HFAIL	GE:LPBKTERMINAL (GE)	STMN:LO-LASERTEMP
AOTS:VOA-LDEG	GE:MANUAL-REQ-SPAN	STMN:LO-RXPOWER
AOTS:VOA-LFAIL	GE:OUT-OF-SYNC	STMN:LO-TXPOWER
BIC:MEA (BIC)	GE:SIGLOSS	STMN:LOCKOUT-REQ
BITS:AIS	GE:SQUELCHED	STMN:LOCKOUT-REQ-RING
BITS:LOF (BITS)	GE:SYNCLOSS	STMN:LOCKOUTOFPR
BITS:LOS (BITS)	GE:WKSWPR	STMN:LOF (DS3, E1, E4, STM1E, STMN)
BITS:SSM-DUS	GE:WTR	STMN:LOS (STM1E, STMN)
BITS:SSM-FAIL	GE:AS-CMD	STMN:LPBKFACILITY (STM1E, STMN)
BITS:SSM-LNC	GE:AS-MT	STMN:LPBKTERMINAL (STM1E, STMN)
BITS:SSM-OFF	GFP-FAC:GFP-CSF	STMN:MANUAL-REQ-RING
BITS:SSM-PRC	GFP-FAC:GFP-DE-MISMATCH	STMN:MANUAL-REQ-SPAN
BITS:SSM-SETS	GFP-FAC:GFP-EX-MISMATCH	STMN:MS-AIS
BITS:SSM-STU	GFP-FAC:GFP-LFD	STMN:MS-EOC
BITS:SSM-TNC	GFP-FAC:GFP-NO-BUFFERS	STMN:MS-RFI
BITS:SYNC-FREQ	GFP-FAC:GFP-UP-MISMATCH	STMN:MSSP-OOSYNC
BPLANE: AS-CMD	ISC:ALS	STMN:PRC-DUPID
BPLANE: INVMACADR	ISC:AS-CMD	STMN:RING-ID-MIS
BPLANE: MFGMEM (BPLANE, FAN)	ISC:AS-MT	STMN:RING-MISMATCH
DS3:AIS	ISC: CARLOSS (ISC)	STMN:RING-SW-EAST
DS3:AS-CMD	ISC:FAILTOSW	STMN:RING-SW-WEST
DS3:AS-MT	ISC:FORCED-REQ-SPAN	STMN:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)
DS3:DS3-MISM	ISC:GE-OOSYNC	STMN:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)
DS3:FE-AIS	ISC:HI-LASERBIAS	STMN:SPAN-SW-EAST
DS3:FE-DS1-MULTLOS	ISC:HI-RXPOWER	STMN:SPAN-SW-WEST
DS3:FE-DS1-NSA	ISC:HI-TXPOWER	STMN:SQUELCH
DS3:FE-DS1-SA	ISC:LO-RXPOWER	STMN:SQUELCHED
DS3:FE-DS1-SNGLLOS	ISC:LO-TXPOWER	STMN:SSM-DUS
DS3:FE-DS3-NSA	ISC:LOCKOUT-REQ	STMN:SSM-FAIL
DS3:FE-DS3-SA	ISC:LOS (ISC)	STMN:SSM-LNC
DS3:FE-EQPT-NSA	ISC:LPBKFACILITY (ISC)	STMN:SSM-OFF
DS3:FE-IDLE	ISC:LPBKTERMINAL (ISC)	STMN:SSM-PRC
DS3:FE-LOF	ISC:MANUAL-REQ-SPAN	STMN:SSM-SETS
DS3:FE-LOS	ISC:OUT-OF-SYNC	STMN:SSM-STU
DS3:INC-ISD	ISC:SIGLOSS	STMN:SSM-TNC
DS3:LOF (DS3, E1, E4, STM1E, STMN)	ISC:SQUELCHED	STMN:SYNC-FREQ
DS3:LOS (DS3)	ISC:SYNCLOSS	STMN:TIM
DS3:LPBKDS1FEAC	ISC:WKSWPR	STMN:TIM-MON
DS3:LPBKDS3FEAC	ISC:WTR	STMN:WKSWPR
DS3:LPBKDS3FEAC-CMD	ML1000:AS-CMD	STMN:WTR
DS3:LPBKFACILITY (DS3)	ML1000:AS-MT	TRUNK:AIS
DS3:LPBKTERMINAL (DS3)	ML1000:CARLOSS (ML100T, ML1000)	TRUNK:ALS
DS3:RAI	ML1000:GFP-CSF	TRUNK:AS-CMD
DS3:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)	ML1000:GFP-DE-MISMATCH	TRUNK:AS-MT
DS3:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)	ML1000:GFP-EX-MISMATCH	TRUNK:CARLOSS (TRUNK)
DS3:TX-AIS	ML1000:GFP-LFD	TRUNK:DSP-COMM-FAIL
TX-RAI	ML1000:GFP-NO-BUFFERS	TRUNK:DSP-FAIL
E1000F: AS-CMD	ML1000:GFP-UP-MISMATCH	TRUNK:EOC
E1000F: CARLOSS (E100T, E1000F)	ML1000:TPTFAIL (ML100T, ML1000)	TRUNK:EOC-L
E100T: AS-MT	ML100T:AS-CMD	TRUNK:FAILTOSW
E100T: CARLOSS (E100T, E1000F)	ML100T:AS-MT	TRUNK:FEC-MISM
E1:AIS	ML100T:CARLOSS (ML100T, ML1000)	TRUNK:FORCED-REQ-SPAN
E1:AS-CMD	ML100T:GFP-CSF	TRUNK:GCC-EOC
E1:AS-MT	ML100T:GFP-DE-MISMATCH	TRUNK:GE-OOSYNC
E1:LOF (DS3, E1, E4, STM1E, STMN)	ML100T:GFP-EX-MISMATCH	TRUNK:HI-LASERBIAS
E1:LOS (E1, E3, E4)	ML100T:GFP-LFD	TRUNK:HI-RXPOWER
E1:LPBKFACILITY (E1, E3, E4)	ML100T:GFP-NO-BUFFERS	TRUNK:HI-TXPOWER
E1:LPBKTERMINAL (E1, E3, E4)	ML100T:GFP-UP-MISMATCH	TRUNK:LO-RXPOWER
E1:RAI	ML100T:TPTFAIL (ML100T, ML1000)	TRUNK:LO-TXPOWER
E1:RCVR-MISS	MSUDC:AIS	TRUNK:LOCKOUT-REQ
E1:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)	MSUDC:LOS (MSUDC)	TRUNK:LOF (TRUNK)
E1:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)	NE-SREF:FRCDSWTOINT	TRUNK:LOM
E1:TRMT	NE-SREF:FRCDSWTOPRI	TRUNK:LOS (TRUNK)
E1:TRMT-MISS	NE-SREF:FRCDSWTOSEC	TRUNK:LOS-P (TRUNK)
E1:TX-AIS	NE-SREF:FFRCDSWTOTHIRD	TRUNK:LPBKFACILITY (TRUNK)
E1:TX-RAI	NE-SREF:FRNGSYNC	TRUNK:LPBKTERMINAL (TRUNK)
E3:AIS	NE-SREF:FSTSYNC	TRUNK:MANUAL-REQ-SPAN
E3:AS-CMD	NE-SREF:HLDOVRSYNC	TRUNK:ODUK-1-AIS-PM
E3:AS-MT	NE-SREF:MANSWTOINT	TRUNK:ODUK-2-AIS-PM
E3:DS3-MISM	NE-SREF:MANSWTOPRI	TRUNK:ODUK-3-AIS-PM
E3:E3-ISD	NE-SREF:MANSWTOSEC	TRUNK:ODUK-4-AIS-PM
E3:FE-AIS	NE-SREF:MANSWTOTHIRD	TRUNK:ODUK-AIS-PM
E3:FE-E1-MULTLOS	NE-SREF:SSM-LNC	TRUNK:ODUK-BDI-PM
E3:FE-E1-NSA	NE-SREF:SSM-PRC	TRUNK:ODUK-LCK-PM
E3:FE-E1-SA	NE-SREF:SSM-SETS	TRUNK:ODUK-OCI-PM
E3:FE-E1-SNGLLOS	NE-SREF:SSM-STU	TRUNK:ODUK-SD-PM
E3:FE-E3-NSA	NE-SREF:SSM-TNC	TRUNK:ODUK-SF-PM
E3:FE-E3-SA	NE-SREF:SWTOPRI	TRUNK:ODUK-TIM-PM
E3:FE-EQPT-NSA	NE-SREF:SWTOSEC	TRUNK:OTUK-AIS
E3:FE-IDLE	NE-SREF:SWTOTHIRD	TRUNK:OTUK-BDI
E3:FE-LOF	NE-SREF:SYNCPRI	TRUNK:OTUK-IAE
E3:FE-LOS	NE-SREF:SYNCSEC	TRUNK:OTUK-LOF
E3:LOS (E1, E3, E4)	NE-SREF:SYNCTHIRD	TRUNK:OTUK-SD
E3:LPBKE1FEAC	NE:APC-DISABLED	TRUNK:OTUK-SF
E3:LPBKE3FEAC	NE:APC-END	TRUNK:OTUK-TIM
E3:LPBKE3FEAC-CMD	NE:AS-CMD	TRUNK:OUT-OF-SYNC
E3:LPBKFACILITY (E1, E3, E4)	NE:AUD-LOG-LOSS	TRUNK:PTIM
E3:LPBKTERMINAL (E1, E3, E4)	NE:AUD-LOG-LOW	TRUNK:RFI
E3:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)	NE:DATAFLT	TRUNK:SD (TRUNK)
E3:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)	NE:DBOSYNC	TRUNK:SF (TRUNK)
E3:TX-AIS	NE:DUP-IPADDR	TRUNK:SIGLOSS
E3:TX-RAI	NE:DUP-NODENAME	TRUNK:SQUELCHED
E4:AIS	NE:ETH-LINKLOSS	TRUNK:SSM-DUS
E4:AS-CMD	NE:HITEMP	TRUNK:SSM-FAIL
E4:AS-MT	NE:I-HITEMP	TRUNK:SSM-LNC
E4:LOF (DS3, E1, E4, STM1E, STMN)	NE:INTRUSION-PSWD	TRUNK:SSM-OFF
E4:LOS (E1, E3, E4)	NE:LAN-POL-REV	TRUNK:SSM-PRC
E4:LPBKFACILITY (E1, E3, E4)	NE:OPTNTWMIS	TRUNKSSM-PRS
E4:LPBKTERMINAL (E1, E3, E4)	NE:SNTP-HOST	TRUNK:SSM-RES
E4:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)	NE:SYSBOOT	TRUNKSSM-SDH-TN
E4:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)	NE: TEMP-MISM	TRUNK:SSM-SETS
EQPT:AUTORESET	OCH:APC-CORRECTION-SKIPPED	TRUNK:SSM-SMC
EQPT:BKUPMEMP	OCH:APC-OUT-OF-RANGE	TRUNK:SSM-ST2S
EQPT:CARLOSS (EQPT)	OCH:AS-CMD	TRUNK:SSM-ST3
EQPT:CLDRESTART	OCH:AS-MT	TRUNK:SSM-ST3E
EQPT:COMIOXC	OCH:LOS-O	TRUNK:SSM-ST4
EQPT:COMM-FAIL	OCH:LOS-P (OCH)	TRUNK:SSM-STU
EQPT:CONTBUS-A-18	OCH:OPWR-HDEG	TRUNK:SSM-TNC
EQPT:CONTBUS-B-18	OCH:OPWR-HFAIL	TRUNK:SYNC-FREQ
EQPT:CONTBUS-IO-A	OCH:OPWR-LDEG	TRUNK:SYNCLOSS
EQPT:CONTBUS-IO-B	OCH:OPWR-LFAIL	TRUNK:TIM
EQPT:CTNEQPT-MISMATCH	OCH:PARAM-MISM	TRUNK:TIM-MON
EQPT:CTNEQPT-PBPROT	OCH:PORT-ADD-PWR-DEG-HI	TRUNK:UNC-WORD
EQPT:CTNEQPT-PBWORK	OCH:PORT-ADD-PWR-DEG-LOW	TRUNK:UT-COMM-FAIL
EQPT:EQPT	OCH:PORT-ADD-PWR-FAIL-HI	TRUNK:UT-FAIL
EQPT:ERROR-CONFIG	OCH:PORT-ADD-PWR-FAIL-LOW	TRUNK:WKSWPR
EQPT:EXCCOL	OCH: PORT-FAIL	TRUNK:WTR
EQPT:FAILTOSW	OCH:UNREACHABLE-TARGET-POWER	TRUNK:WVL-MISMATCH
EQPT:FORCED-REQ	OCH:VOA-HDEG	UCP-CKT:CKTDOWN
EQPT:HITEMP	OCH:VOA-HFAIL	UCP-IPCC:LMP-HELLODOWN
EQPT:IMPROPRMVL	OCH:VOA-LDEG	UCP-IPCC:LMP-NDFAIL
EQPT:INHSWPR	OCH:VOA-LFAIL	UCP-NBR:RSVP-HELLODOWN
EQPT:INHSWWKG	OCHNC-CONN:OCHNC-INC	VCG:LOA
EQPT:IOSCFGCOPY	OMS:APC-CORRECTION-SKIPPED	VCG:VCG-DEG
EQPT:LOCKOUT-REQ	OMS:APC-OUT-OF-RANGE	VCG:VCG-DOWN
EQPT:MAN-REQ	OMS:AS-CMD	VCMON-HP:AU-AIS
EQPT:MANRESET	OMS:AS-MT	VCMON-HP:AU-LOP
EQPT:MEA (EQPT)	OMS:LOS-O	VCMON-HP:AUTOSW-AIS-SNCP
EQPT:MEM-GONE	OMS:LOS-P (OMS, OTS)	VCMON-HP:AUTOSW-LOP-SNCP
EQPT:MEM-LOW	OMS:OPWR-HDEG	VCMON-HP:AUTOSWSW-PDI-SNCP
EQPT:NO-CONFIG	OMS:OPWR-HFAIL	VCMON-HP:AUTOSW-SDBER-SNCP
EQPT:PEER-NORESPONSE	OMS:OPWR-LDEG	VCMON-HP:AUTOSW-SFBER-SNCP
EQPT:PROTNA	OMS:OPWR-LFAIL	VCMON-HP:AUTOSW-UNEQ-SNCP (VCMON-HP)
EQPT:PWR-FAIL-A	OMS:PARAM-MISM	VCMON-HP:FAILTOSW-HO
EQPT:PWR-FAIL-B	OMS:VOA-HDEG	VCMON-HP:FORCED-REQ
EQPT:PWR-FAIL-RET-A	OMS:VOA-HFAIL	VCMON-HP:HP-RFI
EQPT:PWR-FAIL-RET-B	OMS:VOA-LDEG	VCMON-HP:HP-TIM
EQPT:RUNCFG-SAVENEED	OMS:VOA-LFAIL	VCMON-HP:HP-UNEQ
EQPT:SFTWDOWN	OSC-RING:RING-ID-MIS	VCMON-HP:LOCKOUT-REQ
EQPT:SWMTXMOD	OTS:APC-CORRECTION-SKIPPED	VCMON-HP:LPBKCRS
EQPT:WKSWPR	OTS:APC-OUT-OF-RANGE	VCMON-HP:MAN-REQ
EQPT:WTR	OTS:AS-CMD	VCMON-HP:SDBER-EXCEED-HO
ESCON: ALS	OTS:AS-MT	VCMON-HP:SFBER-EXCEED-HO
ESCON: AS-CMD	OTS:AWG-DEG	VCMON-HP:WKSWPR
ESCON: AS-MT	OTS:AWG-FAIL	VCMON-HP:WTR
ESCON: FAILTOSW	OTS:AWG-OVERTEMP	VCMON-LP:AUTOSW-AIS-SNCP
ESCON:FORCED-REQ-SPAN	OTS:AWG-WARM-UP	VCMON-LP:AUTOSW-LOP-SNCP
ESCON:HI-LASERBIAS	OTS:LASERBIAS-DEG	VCMON-LP:AUTOSW-UNEQ-SNCP (VCMON-LP)
ESCON:HI-RXPOWER	OTS:LOS (OTS)	VCMON-LP:FAILTOSW-LO
ESCON:HI-TXPOWER	OTS:LOS-O	VCMON-LP:FORCED-REQ
ESCON:LOCKOUT-REQ	OTS:LOS-P (OMS, OTS)	VCMON-LP:LOCKOUT-REQ
ESCON:LO-RXPOWER	OTS:OPWR-HDEG	VCMON-LP:LP-UNEQ
ESCON:LOS (ESCON)	OTS:OPWR-HFAIL	VCMON-LP:MAN-REQ
ESCON:LO-TXPOWER	OTS:OPWR-LDEG	VCMON-LP:SD-V
ESCON:LPBKFACILITY (ESCON)	OTS:OPWR-LFAIL	VCMON-LPSF-V
ESCON:LPBKTERMINAL (ESCON)	OTS:OSRION	VCMON-LP:TU-AIS
ESCON:MANUAL-REQ-SPAN	OTS:PARAM-MISM	VCMON-LP:TU-LOP
ESCON:PORT-CODE-MISMATCH	OTS:SH-INS-LOSS-VAR-DEG-HIGH	VCMON-LP:WKSWPR
ESCON:PORT-COMM-FAIL	OTS:SH-INS-LOSS-VAR-DEG-LOW	VCMON-LP:WTR
ESCON:PORT-MISMATCH	OTS:SHUTTER-OPEN	VCTRM-HP:AS-MT-OOG
ESCON:PORT-MISSING	OTS:VOA-HDEG	VCTRM-HP:AU-AIS
ESCON:SQUELCH	OTS:VOA-HFAIL	VCTRM-HP:AU-LOF
ESCON:SQUELCHED	OTS:VOA-LDEG	VCTRM-HP:AU-LOP
ESCON:WKSWPR	OTS:VOA-LFAIL	VCTRM-HP:HP-ENCAP-MISMATCH
ESCON:WTR	PPM:AS-CMD	VCTRM-HP:HP-TIM
EXT-SREF:FRCDSWTOPRI	PPM:AS-MT	VCTRM-HP:HP-UNEQ
EXT-SREF:FRCDSWTOSEC	PPM:EQPT	VCTRM-HP:LCAS-CRC
EXT-SREF:FRCDSWTOTHIRD	PPM:HI-LASERBIAS	VCTRM-HP:LCAS-RX-FAIL
EXT-SREF:MANSWTOPRI	PPM:HI-LASERTEMP	VCTRM-HP:LCAS-TX-ADD
EXT-SREF:MANSWTOSEC	PPM:HI-TXPOWER	VCTRM-HP:LCAS-TX-DNU
EXT-SREF:MANSWTOTHIRD	PPM:IMPROPRMVL	VCTRM-HP:LOM
EXT-SREF:SWTOPRI	PPM:LO-TXPOWER	VCTRM-HP:OOU-TPT
EXT-SREF:SWTOSEC	PPM:MEA (PPM)	VCTRM-HP:SDBER-EXCEED-HO
EXT-SREF:SWTOTHIRD	PPM:MFGMEM (AICI-AEP, AICI-AIE, PPM)	VCTRM-HP:SFBER-EXCEED-HO
EXT-SREF:SYNCPRI	PWR:AS-CMD	VCTRM-HP:SQM
EXT-SREF:SYNCSEC	PWR:BATFAIL	VCTRM-LP:AS-MT-OOG
EXT-SREF:SYNCTHIRD	PWR:EHIBATVG	VCTRM-LP:LCAS-CRC
FAN:EQPT-MISS	PWR:ELWBATVG	VCTRM-LP:LCAS-RX-FAIL
FAN:FAN	PWR:HIBATVG	VCTRM-LP:LCAS-TX-ADD
FAN:MEA (FAN)	PWR:LWBATVG	VCTRM-LP:LCAS-TX-DNU
FAN:MFGMEM (BPLANE, FAN)	PWR:VOLT-MISM	VCTRM-LP:LOM
FC:ALS	STM1E:AS-CMD	VCTRM-LP:LP-ENCAP-MISMATCH
FC:AS-CMD	STM1E:AS-MT	VCTRM-LP:LP-PLM
FC:AS-MT	STM1E:LOF (DS3, E1, E4, STM1E, STMN)	VCTRM-LP:LP-RFI
FC:CARLOSS (FC)	STM1E:LOS (STM1E, STMN)	VCTRM-LP:LP-TIM
FC:FAILTOSW	STM1E:LPBKFACILITY (STM1E, STMN)	VCTRM-LP:LP-UNEQ
FC:FC-NO-CREDITS	STM1E:LPBKTERMINAL (STM1E, STMN)	VCTRM-LP:OOU-TPT
FC:FORCED-REQ-SPAN	STM1E:MS-AIS	VCTRM-LP:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)
FC:GE-OOSYNC	STM1E:MS-RFI	VCTRM-LP:SF (DS3, E1, E3, E4, STMN, VCTRM-LP)
FC:HI-LASERBIAS	STM1E:SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)	VCTRM-LP:SQM
FC:HI-RXPOWER	STM1ESD-L	VCTRM-LP:TU-AIS
FC:HI-TXPOWER	STM1E:SF-L	VCTRM-LP:TU-LOP
FC:LOCKOUT-REQ	STM1E:TIM
FC:LO-LASERBIAS	STMN:ALS
FC:LO-RXPOWER	STMN:APSB
FC:LO-TXPOWER	STMN:APSC-IMP
FCMR:GFP-DE-MISMATCH	STMN:APSCDFLTK

2.5  Trouble Notifications

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

The ONS 15454 SDH uses standard 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 SDH 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 SDH shelf. They might 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.)

---

Note ONS 15454 SDH condition reporting is not ITU-compliant.

---

2.5.3  Severities

The ONS 15454 SDH uses ITU-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 trouble that needs immediate correction, such as an LOS on a trunk port or STM signal.

•A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, an APS channel mismatch (APSCNMIS) alarm occurs when working and protect channels have been inadvertently switched so that a working channel is expected at the receive end, but a protect channel is received instead.

•Minor (MN) alarms generally are those that do not affect service. For example, the APS byte failure (APSB) alarm indicates that line terminating equipment 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 a free-running synchronization (FRNGSYNC) state or a forced-switch to primary timing (FRCSWTOPRI) event. They might or might not require troubleshooting, as indicated in the entries.

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

All alarm, condition, and 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) when they do not affect service.

Severities can also 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. Procedures for customizing alarm severities are located in Chapter 7, "Manage Alarms," in the Cisco ONS 15454 SDH Procedure Guide.

2.5.4  Service Effect

The ITU also provides service effect standards. Service-Affecting (SA) alarms—those that interrupt service—might be Critical (CR), Major (MJ), or Minor (MN) severity alarms. Non-Service Affecting (NSA) alarms always have a Minor (MN) default severity.

2.5.5  States

The Alarms and 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.

---

Note Transient events are not defined in this documentation release.

---

2.6  Safety Summary

This section covers safety considerations designed to ensure safe operation of the ONS 15454 SDH. Do not perform any procedures in this chapter unless you understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances 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 STM-64 cards. In these instances, pay close attention to the following warnings.

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

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

---

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

---

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

---

2.7.1  AIS

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

•Logical Objects: BITS, DS3, E1, E3, E4, FUDC, MSUDC, TRUNK

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

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

---

Note DS3i-N-12 card DS3 facility and terminal loopbacks do not transmit DS3 AIS in the direction away from the loopback. Instead of DS3 AIS, a continuance of the signal transmitted to the loopback is provided.

---

Clear the AIS Condition

---

Step 1 Determine whether there are alarms on the upstream nodes and equipment, especially the "LOS (STM1E, STMN)" alarm on page 2-146, or locked (Locked, maintenance or Locked, disabled) ports.

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

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

---

2.7.2  ALS

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

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

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

---

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

---

2.7.3  AMPLI-INIT

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

2.7.4  APC-CORRECTION-SKIPPED

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

•Logical Objects: AOTS, OCH, OMS, OTS

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

There is no operator action to resolve this condition. It stays raised until the power level problem is resolved and APC takes a normal reading. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

---

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

---

2.7.5  APC-DISABLED

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

•Logical Object: NE

The Automatic Power Control (APC) Disabled condition occurs when the information related to the number of channels is not reliable. The condition can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-71, the "IMPROPRMVL" alarm on page 2-122, or the "MEA (EQPT)" alarm on page 2-177. If the alarm occurs with the creation of the first circuit, delete and recreate the circuit. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Clear the APC-DISABLED Condition

---

Step 1 Complete the appropriate procedure to clear the primary cause alarm:

•Clear the EQPT Alarm

•Clear the IMPROPRMVL Alarm

•Clear the MEA (FAN) Alarm

Step 2 If the APC-DISABLED condition does not clear, complete the "Delete a Circuit" procedure and then recreate it.

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

---

2.7.6  APC-END

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

•Logical Object: NE

The APC Terminated on Manual Request condition is raised when the APC application terminates after being manually launched from CTC or TL1. It is an informational condition. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

---

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

---

2.7.7  APC-OUT-OF-RANGE

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

•Logical Objects: AOTS, OCH, OMS, OTS

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

For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Clear the APC-OUT-OF-RANGE Condition

---

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

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

---

2.7.8  APSB

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

•Logical Object: STMN

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

Clear the APSB Alarm

---

Step 1 Use an optical test set to examine the incoming SDH 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 SDH.

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

---

Caution For the ONS 15454 SDH, removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used alarm troubleshooting procedures.

---

---

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

---

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

---

2.7.9  APSCDFLTK

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

•Logical Object: STMN

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

Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "MSSP-OOSYNC" alarm on page 2-184.

Clear the APSCDFLTK Alarm

---

Step 1 Complete the "Identify an MS-SPRing 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 an MS-SPRing 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 "EXCCOL" alarm on page 2-77.) West port fibers must connect to east port fibers and vice versa. The Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," provides a procedure for fibering MS-SPRings.

Step 5 If the alarm does not clear and if the network is a four-fiber MS-SPRing, 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 SDCC Terminations" procedure to ensure that section data communications channel (DCC) 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.10  APSC-IMP

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

•Logical Object: STM-N

An Improper SDH APS Code alarm indicates bad or invalid K bytes. The APSC-IMP alarm occurs on STM-N cards in a MS-SPRing configuration and can occur during MS-SPRing configuration.

The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.

---

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

---

---

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

---

Clear the 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 SDH. Plug the wristband cable into the ESD jack located on the on the middle-right outside edge of the shelf assembly.

---

If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454 SDH. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454 SDHs, 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 an MS-SPRing 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 an MS-SPRing Ring Name" procedure.

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

---

2.7.11  APSCINCON

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

•Logical Object: STMN

An Inconsistent APS Code alarm indicates that the APS code contained in the SDH overhead is inconsistent. The SDH overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454 SDH, to switch the SDH signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.

Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing

---

Step 1 Look for other alarms, especially the "LOS (STM1E, STMN)" alarm on page 2-146, the "LOF (DS3, E1, E4, STM1E, STMN)" alarm on page 2-135, or the "APSB" alarm on page 2-26. Clearing these alarms clears the APSCINCON alarm.

Step 2 If an APSINCON alarm occurs with no other alarms, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.12  APSCM

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

•Logical Object: STMN

An Improper SDH 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.

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

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

---

Clear the APSCM Alarm

---

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

---

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

---

Step 2 If the alarm does not clear, 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.13  APSCNMIS

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

•Logical Object: STMN

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. APSCNMIS could occur and clear when an MS-SPRing is being provisioned. If so, the user can disregard the temporary occurrence. If the APSCNMIS occurs and stays, the alarm clears when a K byte with a valid source node ID is received.

Clear the APSCNMIS Alarm

---

Step 1 Complete the "Identify an MS-SPRing Ring Name or Node ID Number" procedure for each node 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 an MS-SPRing 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 > MS-SPRing tabs. The MS-SPRing 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 an MS-SPRing Protect Span" procedure to lock out the span.

Step 6 Complete the "Clear a MS-SPRing 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.14  APSIMP

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

•Logical Object: STMN

The APS Invalid Mode condition occurs if a 1+1 protection group is not properly configured at both nodes to send or receive the correct APS byte. A node that is either configured for no protection or is configured for SNCP or MS-SPRing 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 condition is superseded by an APS or APSCM. It is not superseded by AIS or remote defect indication (RDI) line alarms. It clears when the port receives a valid code for 10 ms.

Clear the APSIMP Condition

---

Step 1 Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group.

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

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

---

2.7.15  AS-CMD

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

•Logical Objects: 2R, AOTS, BPLANE, DS3, E1,E100T, E1000F, E3, E4, EQPT, ESCON, FC, FCMR, G1000, GE, GFP-FAC, ISC, ML100T, ML1000, NE, OCH, OMS, OTS, PPM, PWR, STM1E, STMN,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; that is, For example, suppressing alarms on a card also suppresses alarms on its ports.

Clear the AS-CMD Condition

---

Step 1 For all nodes, in node view, click the Conditions tab.

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

If the condition is reported against an STM-N card and slot, 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 8.

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

Step 3 If the AS-CMD condition is reported for an STM-N card, determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:

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

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

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

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

Step 4 If the AS-CMD condition is reported for an amplifier, combiner, or other DWDM card, determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:

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

b. Click the Provisioning > Optical Line > Alarm Profiles tabs.

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

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

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

Step 6 Locate the row for the reported card slot.

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

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

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

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

c. Click Apply.

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

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

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

c. Click Apply.

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

---

2.7.16  AS-MT

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

•Logical Objects: 2R, AOTS, DS3, E1, E100T, E1000F, E3, E4, EQPT, ESCON, FC, FCMR, G1000, GE, GFP-FAC, ISC, ML100T, ML1000, NE, OCH, OMS, OTS, PPM, STM1E, STMN, TRUNK

The Alarms Suppressed for Maintenance Command condition applies to STM-N and electrical cards and occurs when a port is placed in the Locked-Enabled, loopback & maintenance service state for loopback testing operations.

Clear the AS-MT Condition

---

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

---

2.7.17  AS-MT-OOG

The AS-MT-OOG alarm is not used in this platform in this release. It is reserved for future development.

2.7.18  AU-AIS

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

•Logical Objects: VCMON-HP, VCTRM-HP

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

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

Clear the AU-AIS Condition

---

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

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

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

---

2.7.19  AUD-LOG-LOSS

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

•Logical Object: NE

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

Clear the AUD-LOG-LOSS Condition

---

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

Step 2 Click Retrieve.

Step 3 Click Archive.

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

Step 5 Enter a name in the File Name field.

You do not need to assign an extension to the file. The file 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 condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.20  AUD-LOG-LOW

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

•Logical Object: NE

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

---

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

---

2.7.21  AU-LOF

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

•Logical Object: VCTRM-HP

The Administrative Unit (AU) Loss of Frame (LOF) alarm indicates that the ONS 15454 SDH detects frame loss in the regenerator section of the SDH overhead.

Clear the AU-LOF Alarm

---

Step 1 Complete the "Clear the LOF (TRUNK) Alarm" procedure.

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

---

2.7.22  AU-LOP

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

•Logical Objects: VCMON-HP, VCTRM-HP

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

---

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

---

---

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

---

Clear the AU-LOP Alarm

---

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

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

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

For instructions to use the optical test set, consult the manufacturer.

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

Step 5 Recreate the circuit for the correct size. For instructions, see the Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels."

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

---

2.7.23  AUTOLSROFF

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

•Logical Object: STMN

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

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293.

---

---

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

---

---

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

---

Clear the AUTOLSROFF Alarm

---

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

Figure 2-1 shows the shelf LCD panel.

Figure 2-1 Shelf LCD Panel

Step 2 If the temperature of the shelf exceeds 194 degrees F (90 degrees C), the alarm should clear if you solve the ONS 15454 SDH 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 STM-64 card.

---

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used troubleshooting procedures.

---

---

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

---

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

---

2.7.24  AUTORESET

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

•Logical Object: EQPT

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

Clear the AUTORESET Alarm

---

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

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

---

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

---

---

Caution For the ONS 15454 SDH, removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

---

---

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

---

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

---

2.7.25  AUTOSW-AIS-SNCP

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

•Logical Objects: VCMON-HP, VCMON-LP

The Automatic SNCP Switch Caused by AIS condition indicates that automatic SNCP protection switching occurred because of the "TU-AIS" condition on page 2-241. The SNCP ring is configured for revertive switching and witches back to the working path after the fault clears. The AUTOSW-AIS-SNCP clears when you clear the primary alarm on the upstream node.

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

Clear the AUTOSW-AIS-SNCP Condition

---

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

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

---

2.7.26  AUTOSW-LOP-SNCP

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

•Logical Objects: VCMON-HP, VCMON-LP

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

Clear the AUTOSW-LOP-SNCP Alarm

---

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

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

---

2.7.27  AUTOSWSW-PDI-SNCP

The AUTOSW-PDI-SNCP alarm is not used in this platform in this release. It is reserved for future development.

2.7.28  AUTOSW-SDBER-SNCP

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

•Logical Objects: VCMON-HP

The Automatic SNCP Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade [see the "SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)" condition on page 2-212] caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SD is resolved.

Clear the AUTOSW-SDBER-SNCP Condition

---

Step 1 Complete the "Clear the SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP) Condition" procedure.

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

---

2.7.29  AUTOSW-SFBER-SNCP

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

•Logical Objects: VCMON-HP

The Automatic SNCP Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail [see the "SF (DS3, E1, E3, E4, STMN, VCTRM-LP)" condition on page 2-216] caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SF is resolved.

Clear the AUTOSW-SFBER-SNCP Condition

---

Step 1 Complete the "Clear the SF (DS3, E1, E3, E4, STMN, VCTRM-LP) Condition" procedure.

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

---

2.7.30  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

•Logical Object: VCMON-HP

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

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

---

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

---

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

---

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

---

2.7.31  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

•Logical Object: VCMON-LP

AUTOSW-UNEQ-SNCP for VCMON-LP indicates that the "LP-UNEQ" alarm on page 2-172 caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path after the fault clears.

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

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

---

Step 1 Display the CTC network view and right-click the span reporting AUTOSW-UNEQ. Select Circuits from the shortcut menu.

Step 2 If the specified circuit is a low-order path tunnel, determine whether low-order paths are assigned to the tunnel.

Step 3 If the low-order path tunnel does not have assigned low-order paths, delete the low-order path tunnel from the list of circuits.

Step 4 If you have complete visibility to all nodes, determine whether there are incomplete circuits such as stranded bandwidth from circuits that were not completely deleted.

Step 5 If you find incomplete circuits, determine whether they are working circuits and if they are still passing traffic.

Step 6 If the incomplete circuits are not needed or are not passing traffic, delete them and log out of CTC. Log back in and search for incomplete circuits again. Recreate any needed circuits.

Step 7 If the alarm does not clear, verify that all circuits terminating in the reporting card are active:

a. In node view, click the Circuits tab.

b. Verify that the Status column lists the port as active.

c. If the Status column lists the port as incomplete, and the incomplete does not change after a full initialization, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

Step 8 After you determine that the port is active, verify the signal source received by the card reporting the alarm.

Step 9 If the alarm does not clear, verify that the far-end STM-N card providing payload to the card is working properly.

Step 10 If the alarm does not clear, verify the far-end cross-connect between the STM-N card and the E-N card.

Step 11 If the alarm does not clear, clean the far-end optical fiber cable ends according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

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

---

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

---

2.7.32  AWG-DEG

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

•Logical Object: OTS

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

Clear the AWG-DEG Alarm

---

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

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

---

2.7.33  AWG-FAIL

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

•Logical Object: OTS

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

Clear the AWG-FAIL Alarm

---

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

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

---

2.7.34  AWG-OVERTEMP

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

•Logical Object: OTS

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

Clear the AWG-OVERTEMP Alarm

---

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

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

---

2.7.35  AWG-WARM-UP

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

•Logical Object: OTS

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

---

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

---

2.7.36  BATFAIL

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

•Logical Object: PWR

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

Clear the BATFAIL Alarm

---

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

Step 2 Remove the power cable from the faulty supply.

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

---

2.7.37  BKUPMEMP

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

---

Note The severity is Minor (MN), Non-Service-Affecting (NSA) for SBY TCC2/TCC2P card.

---

SDH Logical Object: EQPT

The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P flash memory. This alarm is raised on ACT/SBY TCC2/TCC2P cards. The alarm occurs when the TCC2/TCC2P is in active or standby state and has one of four problems:

•Failure to format a flash partition.

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

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 standby TCC2/TCC2P has the alarm.

Step 3 If both cards 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 and Activate the Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2/TCC2P LED should be green.
If the card is the standby TCC2/TCC2P, complete the "Reset the Standby TCC2/TCC2P Card" procedure.

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

---

2.7.38  CARLOSS (E100T, E1000F)

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

•Logical Objects: E100T, E1000F

A Carrier Loss alarm on the LAN E-Series Ethernet card is the data equivalent of the "LOS (STM1E, STMN)" alarm on page 2-146. 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.

CARLOSS also occurs after the restoration of a node database. In this instance, the alarm clears approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP). Reestablishment applies to the E-Series Ethernet cards but not to the G1000-4 card. The G1000-4 card does not use STP and is not affected by STP reestablishment.

Clear the CARLOSS (E100T, E1000F) 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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

---

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside 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 STM-N card. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

Step 3 If no misconnection to an STM-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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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

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

---

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

---

---

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

---

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

An Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454 SDHs, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 SDH 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.

Step 9 If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm may 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 SDH node and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

•Log into the ONS 15454 SDH 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 STM-N card at the same node.

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

If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. For more information, refer to the
Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels."

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

---

2.7.39  CARLOSS (EQPT)

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

•Logical Object: EQPT

The Carrier Loss Equipment alarm occurs when the ONS 15454 SDH and the workstation hosting CTC do not have a TCP/IP connection. CARLOSS is a problem involving the LAN or data circuit used by the RJ-45 connector on the TCC2/TCC2P card or the LAN backplane pin connection on the back of the ONS 15454 SDH. The alarm does not involve an Ethernet circuit connected to a port on an Ethernet (traffic) card. The problem is in the connection (usually a LAN problem) and not the CTC or the ONS 15454 SDH.

On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, and MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 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 type.

Clear the CARLOSS (EQPT) Alarm

---

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

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

b. Click the Provisioning > Pluggable Port Modules tabs.

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

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 STM-N card, verify connectivity by pinging the ONS 15454 SDH that is reporting the alarm:

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

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

c. For both the Sun and Microsoft operating systems, at the prompt type:

ping ONS-15454SDH-IP-address

For example:

ping 198.168.10.10

If the workstation has connectivity to the ONS 15454 SDH, it shows a "reply from IP-Address" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

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

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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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 STM-N card. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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

---

Note To verify cable continuity, follow site practices.

---

Step 9 If you are unable to establish connectivity, perform standard network/LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a service-affecting problem.

---

2.7.40  CARLOSS (FC)

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

2.7.41  CARLOSS (G1000)

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

•Logical Object: G1000

A Carrier Loss alarm on the LAN G-Series Ethernet card is the data equivalent of the "LOS (STM1E, STMN)" alarm on page 2-146. The Ethernet card has lost its link and is not receiving a valid signal.

CARLOSS on the G1000-4 card can be 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), the problem causes the reporting G1000-4 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, it is normally accompanied by a "TPTFAIL (G1000)" alarm on page 2-238 or STM-N alarms or conditions on the end-to-end path.

Refer to the Cisco ONS 15454 SDH 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-239 for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.

Ethernet card ports must be unlocked for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

---

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside 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 STM-N card.

Step 3 If no misconnection to the STM-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. These are listed in the "1.12.3  Optical Card Transmit and Receive Levels" section on page 1-143.

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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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

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

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

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

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

---

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

---

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

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

b. Click the Maintenance > Loopback tabs.

c. If the port Admin State is listed as Locked, maintenance, a loopback might be provisioned. Go to Step 11.

Step 11 If a loopback was provisioned, complete the "Clear EC Card or or G-Series 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 looped-back G1000-4 port detects the termination.

If the card 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 SDH Ethernet manual cross-connect is used when another vendors' equipment sits between ONS nodes, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 SDH 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 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect by completing the following steps:

•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 STM-N card at the same node.

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

f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels," for detailed procedures to create circuits.

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

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

---

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

---

---

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

---

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

---

2.7.42  CARLOSS (GE)

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

•Logical Object: GE

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

Clear the CARLOSS (GE) Alarm

---

Step 1 Ensure that the GE client is correctly configured:

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

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment column for the MXP or TXP MR card and compare this with the client equipment. If no PPM is provisioned, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," for provisioning instructions.

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

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

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

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

---

2.7.43  CARLOSS (ISC)

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

•Logical Object: ISC

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

Clear the CARLOSS (ISC) Alarm

---

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

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

---

2.7.44  CARLOSS (ML100T, ML1000)

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

•Logical Objects: ML100T, ML1000

A Carrier Loss alarm on the ML-Series Ethernet card is the data equivalent of the "LOS (STM1E, STMN)" alarm on page 2-146. 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 (ML100T, ML1000) Alarm

---

Step 1 Verify that the LAN cable is properly connected and attached to the correct port on the ML-Series card and on the peer Ethernet port. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

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 problem persists with the loopback installed, complete the "Remove and Reinsert (Reseat) Any Card" procedure.

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

---

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

---

---

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

---

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

---

2.7.45  CARLOSS (TRUNK)

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

•Logical Object: TRUNK

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

Clear the CARLOSS (TRUNK) Alarm

---

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

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

---

2.7.46  CASETEMP-DEG

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

•Logical Object: AOTS

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

Clear the CASETEMP-DEG Alarm

---

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

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

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

---

2.7.47  CKTDOWN

The CKTDOWN alarm is not used in this platform in this release. It is reserved for future development.

2.7.48  CLDRESTART

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

•Logical Object: EQPT

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

Clear the CLDRESTART Condition

---

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

---

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

---

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

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

---

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

---

---

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

---

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

---

2.7.49  COMIOXC

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

•Logical Object: EQPT

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

Clear the COMIOXC Alarm

---

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

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

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

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

Step 5 If the alarm does not clear, complete the "Physically Replace an In-Service Cross-Connect Card" procedure for the reporting cross-connect card.

---

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

---

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

---

2.7.50  COMM-FAIL

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

•Logical Object: EQPT

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

Clear the COMM-FAIL Alarm

---

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

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

---

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "CTC Card Resetting and Switching" section for commonly used traffic-switching procedures.

---

---

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

---

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

---

2.7.51  CONTBUS-A-18

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

•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 Slot 7 TCC2/TCC2P.

Clear the CONTBUS-A-18 Alarm

---

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

---

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

---

Step 2 Wait approximately 10 minutes for the Slot 7 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 11 TCC2/TCC2P and complete the "Reset an Active TCC2/TCC2P 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, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) Any Card" procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.

---

2.7.52  CONTBUS-B-18

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

•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 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 and Activate the Standby Card" procedure to return the Slot 11 TCC2/TCC2P card to the active state.

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

---

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

---

---

2.7.53  CONTBUS-IO-A

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

•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 SDH 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 is with the physical path of communication from the TCC2/TCC2P card 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-177 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.)

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

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

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

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

---

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

---

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

---

2.7.54  CONTBUS-IO-B

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

•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 might appear briefly when the ONS 15454 SDH 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 is with the physical path of communication from the TCC2/TCC2P card 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-177 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 once, complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure.

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

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

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

---

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

---

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

---

2.7.55  CTNEQPT-MISMATCH

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

•Logical Object: EQPT

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

---

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

---

---

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

---

If you upgrade a node to R5.0 and replace an XCVLX with an XC10G, the CTNEQPT-MISMATCH condition is raised but it is cleared when the upgrade process ends.

---

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

---

Clear the CTNEQPT-MISMATCH Condition

---

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

a. In node view, click the Inventory tab.

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

The Eqpt Type column contains the equipment that is provisioned in the slot. The Actual Eqpt Type contains the equipment that is physically present in the slot. For example, Slot 8 might be provisioned for an XCVT card, which is shown in the Eqpt Type column, but an XC10G card could be physically present in the slot. The XC10G would be shown in the Actual Eqpt Type column.)

Step 2 Complete the "Physically Replace a Traffic Card" procedure for the mismatched card.

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

---

2.7.56  CTNEQPT-PBPROT

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

•Logical Object: EQPT

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the protect ONS 15454 SDH Slot 10 XC10G cross-connect card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card and the reporting traffic card, or the TCC2/TCC2P and the backplane.

---

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

---

---

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

---

Clear the CTNEQPT-PBPROT Alarm

---

Step 1 If all traffic cards show CTNEQPT-PBPROT alarm:

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

---

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

---

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 STM-64 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, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.

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

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

Step 6 If the reporting traffic card is the active card in the protection group, complete the "Initiate a 1:1 Card Switch Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.

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

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

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

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

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

---

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" procedure for commonly used traffic-switching procedures.

---

---

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

---

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

---

2.7.57  CTNEQPT-PBWORK

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

•Logical Object: EQPT

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

---

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

---

Clear the CTNEQPT-PBWORK Alarm

---

Step 1 If all traffic cards show CTNEEQPT-PBWORK alarm:

a. Complete the "Reset an Active TCC2/TCC2P 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 card.

---

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

---

---

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

---

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

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

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

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

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

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

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

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

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

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

---

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

---

Step 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.58  DATAFLT

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

•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 "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.59  DBOSYNC

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

•Logical Object: NE

The standby Database Out Of Synchronization alarm occurs when the standbyTCC2/TCC2P "To be Active" database does not synchronize with the active database on the active TCC2/TCC2P.

---

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

---

Clear the DBOSYNC Alarm

---

Step 1 Save a backup copy of the active TCC2/TCC2P database. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node," for instructions.

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

a. In node view, click the Provisioning > General > General tabs.

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

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

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

---

2.7.60  DS3-MISM

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

•Logical Objects: DS3, E3

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

Clear the DS3-MISM Condition

---

Step 1 Display the CTC card view for the reporting DS3i-N-12 card.

Step 2 Click the Provisioning > Line tabs.

Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal (C Bit or M13).

Step 4 If the Line Type drop-down list 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 SDH 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.61  DSP-COMM-FAIL

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

•Logical Object: TRUNK

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

The alarm is temporary and does not require user action. The MXP or TXP card microprocessor attempts to restore communication with the DSP chip until the alarm is cleared.

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

---

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

---

2.7.62  DSP-FAIL

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

•Logical Object: TRUNK

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

Clear the DSP-FAIL Alarm

---

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

---

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

---

---

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

---

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

---

2.7.63  DUP-IPADDR

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

•Logical Object: NE

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

Clear the DUP-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 ONS 15454 SDH chassis.

b. Begin a CTC session.

c. On 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 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.64  DUP-NODENAME

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

•Logical Object: NE

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

Clear the DUP-NODENAME Alarm

---

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

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

Step 3 Click Apply.

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

---

2.7.65  E3-ISD

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

•Logical Object: E3

The E3 Idle condition indicates that the E3-12 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. E3-ISD occurs when the transmitting card is Locked, maintenance state. E3-ISD is resolved when the lock condition ends.

---

Note E3-ISD is an informational condition. The condition does not require troubleshooting.

---

2.7.66  EHIBATVG

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

•Logical Object: PWR

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

Clear the EHIBATVG Alarm

---

Step 1 The problem is external to the ONS 15454 SDH. 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a service-affecting problem.

---

2.7.67  ELWBATVG

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

•Logical Object: PWR

The Extreme Low Voltage Battery alarm occurs in a -48 VDC environment when the voltage on the battery feeds is extremely low or has been lost, and power redundancy is no longer guaranteed. The threshold for this alarm is -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage remains above -40.5 VDC for 120 seconds.

Clear the ELWBATVG Alarm

---

Step 1 The problem is external to the ONS 15454 SDH. 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a service-affecting problem.

---

2.7.68  EOC

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

•Logical Objects: STMN, TRUNK

The SDH Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 SDH loses its data communications channel. Although this alarm is primarily SDH, it can apply to DWDM. For example, the OSCM card can raise this alarm on its STM-1 section overhead.

The SDCCs consist of three bytes, D1 through D3, in the SDH overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the SDH section layer to communicate network management information.

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

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

---

---

Note If a circuit shows an incomplete 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 (DS3)" alarm on page 2-140 is also reported, complete the "Clear the LOS (DS3) Alarm" procedure.

Step 2 If the "SFTWDOWN" condition on page 2-219 is reported, complete the "Clear the SF (DS3, E1, E3, E4, STMN, VCTRM-LP) Condition" procedure.

Step 3 If the alarm does not clear on the reporting node, verify the physical connections between the cards and the fiber-optic cables are configured to carry SDCC traffic. If they are not, correct them. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

---

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

---

If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have unlocked ports. Verify that the ACT/SBY LED on each STM-N card is green.

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

Step 5 Repeat Step 4 at the adjacent nodes.

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

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

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

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

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and click Unlocked from the drop-down list. Click Apply.

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

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

---

Caution Using an optical test set disrupts service on the STM-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 "1.12.3  Optical Card Transmit and Receive Levels" section on page 1-143 for non-DWDM card levels and refer to the Cisco ONS 15454 SDH 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 Chapter 2, "Install Cards and Fiber-Optic Cables," in the Cisco ONS 15454 SDH Procedure Guide.

Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset an Active TCC2/TCC2P 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 SDH 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 card view, click View > Go to Previous View if you have not already done so.

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

b. Highlight the problematic DCC termination.

c. Click Delete.

d. Click Yes in the Confirmation Dialog box.

Step 12 Recreate the SDCC termination. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 5, "Turn Up Network," for instructions.

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

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

---

2.7.69  EOC-L

The SDCC Termination Failure Line alarm is not used in this platform in this release. It is reserved for future development.

2.7.70  EQPT

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

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

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

If the EQPT alarm occurs with a BKUPMEMP alarm, see the "BKUPMEMP" section. The BKUPMEMP procedure also clears the EQPT alarm.

Clear the EQPT Alarm

---

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

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

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

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

---

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

---

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

---

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

---

---

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

---

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

---

2.7.71  EQPT-DIAG

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

•Logical Object: EQPT

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

Clear the EQPT-DIAG Alarm

---

Step 1 If traffic is active on the alarmed card, you might need to switch traffic away from it. Refer to the "Generic Signal and Circuit Procedures" section for procedures.

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

---

Caution If the card carries live traffic, reseating it can affect this traffic.

---

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

---

2.7.72  EQPT-MISS

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

•Logical Object: FAN

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

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.

---

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

---

Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and install it using the "Install the Fan-Tray Assembly," procedure in the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

Step 4 If the alarm does not clear, replace the ribbon cable from the AIE 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.73  ERROR-CONFIG

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

•Logical Object: EQPT

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

The typical reasons for an errored startup file are:

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

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

---

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

---

Clear the ERROR-CONFIG Alarm

---

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

Follow the card provisioning instructions in the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.

Step 2 Upload the configuration file to the TCC2/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 an 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 following 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.74  ETH-LINKLOSS

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

•Logical Object: NE

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

•The node.network.general.AlarmMissingBackplane LAN field in NE defaults is enabled.

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

•The backplane LAN cable is removed.

Clear the ETH-LINKLOSS Condition

---

Step 1 To clear this alarm, reconnect the backplane cable. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 1, "Install the Shelf and FMECS," for instructions to install this cable.

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

---

2.7.75  E-W-MISMATCH

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

•Logical Object: STMN

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

---

Note The E-W-MISMATCH alarm also appears during the initial setup of a ring with its east-west slots and ports configured correctly. In this instance, the alarm clears itself shortly after the ring setup is complete.

---

---

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

---

---

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

---

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

---

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

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

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

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

Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1—Node2/Slot6/Port1 (2F MS-SPRing STM-16, Ring Name=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.

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

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

Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," for more information about configuring the system.

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

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

Warning Use of controls, adjustments, or performing procedures other than those specified may 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting 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 > MS-SPRing tabs.

Step 3 From the row of information for the fiber span, complete the "Identify an MS-SPRing 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 MS-SPRing:

a. Click the Provisioning > MS-SPRing 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 > MS-SPRing tabs.

Step 7 Change the West Line drop-down list to the slot you recorded for the East Line in Step 3.

Step 8 Change the East Line drop-down list 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.76  EXCCOL

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

•Logical Object: EQPT

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

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

Clear the EXCCOL Alarm

---

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

Step 2 If the alarm does not clear, troubleshoot the network device connected to the TCC2/TCC2P card and the network management LAN.

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

---

2.7.77  EXERCISE-RING-FAIL

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

•Logical Object: STMN

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

---

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

---

Clear the EXERCISE-RING-FAIL Condition

---

Step 1 Look for and clear, if present, the "LOF (DS3, E1, E4, STM1E, STMN)" alarm on page 2-135, the "LOS (STM1E, STMN)" alarm on page 2-146, or MS-SPRing alarms.

Step 2 Reissue the Exercise Ring command:

a. Click the Maintenance > MS-SPRing tabs.

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

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

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

---

2.7.78  EXERCISE-SPAN-FAIL

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

•Logical Object: STMN

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

---

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

---

Clear the EXERCISE-SPAN-FAIL Condition

---

Step 1 Look for and clear, if present, the "LOF (DS3, E1, E4, STM1E, STMN)" alarm on page 2-135, the "LOS (STM1E, STMN)" alarm on page 2-146, or a MS-SPRing alarm.

Step 2 Reissue the Exercise Span command:

a. Click the Maintenance > MS-SPRing tabs.

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

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

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

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

---

2.7.79  EXT

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

•Logical Object: ENVALRM

An External Facility alarm is detected externally from the node because an environmental alarm is present. For example, an open door or flooding can cause the alarm.

Clear the EXT Alarm

---

Step 1 In node view, double-click the MIC-A/P card to display the card view.

Step 2 Click the Maintenance tab to gather further information about the EXT alarm.

Step 3 Perform your standard operating procedure for this environmental condition.

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

---

2.7.80  EXTRA-TRAF-PREEMPT

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

•Logical Object: STMN

An Extra Traffic Preempted alarm occurs on STM-N cards in two-fiber and four-fiber MS-SPRings because 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 verifying that the Conditions window shows the switch.

Step 2 If a ring switch has occurred, clear the alarm on the working system by following the appropriate alarm procedure in this chapter. For more information about protection switches, refer to the "Protection Switching, Lock Initiation, and Clearing" section.

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

---

2.7.81  FAILTOSW

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

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

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

Clear the FAILTOSW Condition

---

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

---

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

---

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

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

---

Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

---

---

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

---

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

---

2.7.82  FAILTOSW-HO

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

•Logical Object: VCMON-HP

The Failure to Switch to Protection High Order Path condition occurs when an active STM-N card carrying high-order (VC-4) traffic cannot switch to the standby card because another electrical (traffic) card with a higher priority alarm is switched over and is monopolizing the card.

Clear the FAILTOSW-HO Condition

---

Step 1 Look up and clear the higher priority alarm. Clearing this alarm frees the standby card and clears the FAILTOSW-HO condition.

---

Note A higher priority alarm is an alarm raised on the active STM-N card using the protection group. The active STM-N card is reporting an alarm, but not reporting a FAILTOSW-HO condition.

---

Step 2 If the condition does not clear, replace the active STM-N card that is reporting the higher priority alarm. Complete the "Physically Replace a Traffic Card" procedure. Replacing the active STM-N card that is reporting the higher priority alarm allows traffic to revert to the active slot. The standby card is freed to take over traffic from the card that reported the lower priority alarm and the FAILTOSW-HO condition.

---

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

---

---

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

---

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

---

2.7.83  FAILTOSW-LO

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

•Logical Object: VCMON-LP

The Failure to Switch to Protection Low-Order Path condition occurs when a working (or protect) STM-N card carrying low-order (VC-12 or VC-3) traffic cannot switch to the protect (or working) card because another working STM-N card with a higher priority alarm is switched over and is monopolizing the protect card.

Clear the FAILTOSW-LO Condition

---

Step 1 Complete the "Clear the FAILTOSW-HO Condition" procedure.

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

---

2.7.84  FAILTOSWR

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

•Logical Object: STMN

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 card (done under the supervision of Cisco Technical Support).

•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 (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)" condition on page 2-212 or the "SF (DS3, E1, E3, E4, STMN, VCTRM-LP)" condition on page 2-216 clears.

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

Warning Use of controls, adjustments, or performing procedures other than those specified may 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 FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration

---

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

a. Click the Maintenance > MS-SPRing 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 STM-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 > MS-SPRing tabs.

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

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

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

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked. Click Apply.

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

---

Note To verify fiber continuity, follow site practices.

---

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

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

---

Caution Using an optical test set disrupts service on the STM-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 for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH 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 STM-N card receiver specifications. The "1.12.3  Optical Card Transmit and Receive Levels" section on page 1-143 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 STM-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby STM-N card.

---

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

---

---

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

---

Step 13 If the condition does not clear after you replace the MS-SPRing 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.85  FAILTOSWS

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

•Logical Object: STMN

The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber MS-SPRing, 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 card (done under the supervision of Cisco Technical Support).

•A node power cycle.

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

•The next span switch succeeds.

•The cause of the APS switch such as the "SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP)" condition on page 2-212 or the "SF (DS3, E1, E3, E4, STMN, VCTRM-LP)" condition on page 2-216 clears.

Clear the FAILTOSWS Condition

---

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

a. Click the Maintenance > MS-SPRing tabs.

b. Determine whether the card you would like to exercise is the east card or the west 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 STM-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 > MS-SPRing tabs.

Step 6 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-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 STM-N port is in service, double-click the card in CTC to display the card view.

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked. Click Apply.

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

---

Note To verify fiber continuity, follow site practices.

---

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

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

---

Caution Using an optical test set disrupts service on the STM-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 for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 DH 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 STM-N card receiver specifications. The "1.12.3  Optical Card Transmit and Receive Levels" section on page 1-143 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 STM-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby STM-N card.

---

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

---

---

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

---

Step 13 If the condition does not clear after you replace the MS-SPRing 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.86  FAN

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

•Logical Object: FAN

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15454 SDH 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 ONS 15454 SDH. 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.

Clear the FAN Alarm

---

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

---

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

---

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

---

Note The fan-tray assembly should run immediately when correctly inserted.

---

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

Step 4 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.87  FC-NO-CREDITS

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

•Logical Objects: FC, FCMR

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

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

Clear the FC-NO-CREDITS Alarm

---

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

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

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

b. Click Provisioning > Port > General.

c. Under Admin State, click the cell and choose Locked, maintenance.

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

e. Uncheck the Autodetect Credits column check box.

f. Click Apply.

g. Click Provisioning > Port > General.

h. Under Admin State, click the cell and choose Unlocked.

i. Click Apply.

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

---

Note 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 to display the card view.

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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.

---

2.7.88  FE-AIS

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

•Logical Objects: DS3, E3

The Far-End AIS condition accompanies the "AIS" condition on page 2-23 at the far-end node. An AIS usually occurs in conjunction with a downstream "LOS (STM1E, STMN)" alarm on page 2-146.

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

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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.89  FEC-MISM

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

•Logical Object: TRUNK

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

Clear the FEC-MISM Alarm

---

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

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

Step 3 In the FEC column, click Standard or Enhanced if you desire to enable the monitoring, or Disable if you do not.

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

Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.90  FE-DS1-MULTLOS

The FE-DS1-MULTLOS alarm is not used in this platform in this release. It is reserved for future development.

2.7.91  FE-DS1-NSA

The FE-DS1-NSA alarm is not used in this platform in this release. It is reserved for future development.

2.7.92  FE-DS1-SA

The FE-DS1-SA alarm is not used in this platform in this release. It is reserved for future development.

2.7.93  FE-DS1-SNGLLOS

The FE-DS1-SNGLLOS alarm is not used in this platform in this release. It is reserved for future development.

2.7.94  FE-DS3-NSA

The FE-DS3-NSA alarm is not used in this platform in this release. It is reserved for future development.

2.7.95  FE-DS3-SA

The FE-DS3-SA alarm is not used in this platform in this release. It is reserved for future development.

2.7.96  FE-E1-MULTLOS

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

•Logical Object: E3

The Far End Multiple E-1 LOS Detected on an E1-42 card condition occurs when multiple E1 inputs detect signal loss on a far-end E1-42 port at the far-end node.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-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-E1-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 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.97  FE-E1-NSA

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

•Logical Object: E3

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

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

Clear the FE-E1-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 FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.98  FE-E1-SA

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

•Logical Object: E3

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

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

Clear the FE-E1-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 FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.99  FE-E1-SNGLLOS

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

•Logical Object: E3

The Far End Single E-1 LOS on the E-3 condition occurs when one of the E3-12 ports on the far end detects an LOS.

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

Clear the FE-E1-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 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.100  FE-E3-NSA

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

•Logical Object: E3

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

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

Clear the FE-E3-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 FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.101  FE-E3-SA

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

•Logical Object: E3

The Far End E3 Equipment Failure Service Affecting condition occurs when a far-end E-3 equipment failure occurs and affects service because traffic is unable to switch to the protect port.

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

Clear the FE-E3-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 FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.102  FE-EQPT-NSA

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

•Logical Objects: DS3, E3

The Far End Common Equipment Failure condition occurs when a non-service affecting equipment failure is detected on the far-end DS3i-N-12 or the E-N card.

The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-EQPT-NSA 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-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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.103  FE-FRCDWKSWBK-SPAN

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

•Logical Object: STMN

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.

---

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

Clear the FE-FRCDWKSWBK-SPAN Condition

---

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

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

---

2.7.104  FE-FRCDWKSWPR-RING

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

•Logical Object: STMN

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

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

Clear the FE-FRCDWKSWPR-RING Condition

---

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

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

Step 3 Clear the main alarm.

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

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

---

2.7.105  FE-FRCDWKSWPR-SPAN

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

•Logical Object: STMN

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 MS-SPRing is forced from working to protect using the FORCE SPAN command.

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

Clear the FE-FRCDWKSWPR-SPAN Condition

---

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

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

Step 3 Clear the main alarm.

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

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

---

2.7.106  FE-IDLE

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

•Logical Objects: DS3, E3

The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal on a DS3i-N-12 card or an idle E-N signal.

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

Clear the FE-IDLE Condition

---

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

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

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

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

---

2.7.107  FE-LOCKOUTOFPR-ALL

The Far-End Lockout of Protection All condition is not supported in this release. It is reserved for future development.

2.7.108  FE-LOCKOUTOFPR-RING

The Far-End Lockout of Protection Ring condition is not supported in this release. It is reserved for future development.

2.7.109  FE-LOCKOUTOFPR-SPAN

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

•Logical Object: STMN

The Far-End Lockout of Protection Span condition occurs when an MS-SPRing span is locked out of the protection system from a far-end node using the LOCKOUT SPAN command.

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

Clear the FE-LOCKOUTOFPR-SPAN Condition

---

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 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 MS-SPRing External Switching Command" procedure.

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

---

2.7.110  FE-LOCKOUTOFWK-RING

The Far-End Lockout of Working Ring condition is not supported in this release. It is reserved for future development.

2.7.111  FE-LOCKOUTOFWK-SPAN

The Far-End Lockout of Working Span condition is not supported in this release. It is reserved for future development.

2.7.112  FE-LOF

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

•Logical Objects: DS3, E3

The Far End LOF condition occurs when a far-end node reports a DS-3 LOF on a DS3i-N-12 card or an LOF on an E-N card.

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

Clear the FE-LOF Condition

---

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

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

Step 3 Complete the "LOF (TRUNK)" procedure. The procedure also applies to FE-LOF.

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

---

2.7.113  FE-LOS

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

•Logical Objects: DS3, E3

The Far End LOS condition occurs when a far-end node reports a DS-3 LOS on a DS3i-N-12 card or an E-N LOS.

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

Clear the FE-LOS Condition

---

Step 1 To troubleshoot the FE condition, determine which node and card is linked 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 is linked directly to the card reporting the FE condition.

Step 3 Complete the "Clear the LOS (STM1E, STMN) Alarm" procedure.

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

---

2.7.114  FE-MANWKSWBK-SPAN

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

•Logical Object: STMN

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

---

Note WKSWBK-type conditions apply only to nonrevertive circuits.

---

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

Clear the FE-MANWKSWBK-SPAN Condition

---

Step 1 To troubleshoot the FE condition, determine which node and card is linked 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 is linked directly to the card reporting the FE condition.

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

---

2.7.115  FE-MANWKSWPR-RING

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

•Logical Object: STMN

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

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

Clear the FE-MANWKSWPR-RING Condition

---

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could link to the main condition 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 MS-SPRing External Switching Command" procedure.

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

---

2.7.116  FE-MANWKSWPR-SPAN

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

•Logical Object: STMN

The Far-End Span Manual Switch Working Facility to Protect condition occurs when an MS-SPRing span is switched from working to protect at the far-end node using the MANUAL SPAN command.

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

Clear the FE-MANWKSWPR-SPAN Condition

---

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could link to the main condition 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 MS-SPRing External Switching Command" alarm on page 2-259.

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

---

2.7.117  FEPRLF

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

•Logical Object: STMN

The Far-End Protection Line Failure alarm occurs when there was an APS channel SF (DS3, E1, E3, E4, STMN, VCTRM-LP) condition on the protect card coming into the node.

---

Note The FEPRLF alarm occurs on the ONS 15454 SDH only when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration.

---

Clear the FEPRLF Alarm on an MS-SPRing

---

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

Step 2 Log into the node that is linked directly to the card reporting the FE alarm.

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

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

---

2.7.118  FE-SDPRLF

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

•Logical Object: STMN

The Far-End Protection Signal Degrade Line Failure alarm occurs when there was an APS channel SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP) condition on the protect card coming into the node.

---

Note The FE-SDPRLF alarm occurs on the ONS 15454 SDH only when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration.

---

Clear the FE-SDPRLF Alarm on an MS-SPRing

---

Step 1 Complete the "Clear the SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP) Condition" procedure for the reporting node.

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

---

2.7.119  FIBERTEMP-DEG

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

•Logical Object: AOTS

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

Clear the FIBERTEMP-DEG Alarm

---

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

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

---

2.7.120  FORCED-REQ

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

•Logical Objects: EQPT, VCMON-HP, VCMON-LP

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 vice versa). You do not need to clear the condition if you want the Force switch to remain.

Clear the FORCED-REQ Condition

---

Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure.

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

---

2.7.121  FORCED-REQ-RING

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

•Logical Object: STMN

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

Clear the FORCED-REQ-RING Condition

---

Step 1 Complete the "Clear a MS-SPRing External Switching Command" procedure.

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

---

2.7.122  FORCED-REQ-SPAN

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

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

The Force Switch Request Span condition applies to optical trunk (span) cards in four-fiber MS-SPRings when the FORCE SPAN command is applied to an MS-SPRing to force traffic from working to protect or from protect to working.

Clear the FORCED-REQ-SPAN Condition

---

Step 1 Complete the "Clear a MS-SPRing External Switching Command" procedure.

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

---

2.7.123  FRCDSWTOINT

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

•Logical Object: NE-SREF

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

---

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

---

2.7.124  FRCDSWTOPRI

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

•Logical Objects: EXT-SREF, NE-SREF

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

---

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

---

2.7.125  FRCDSWTOSEC

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

•Logical Objects: EXT-SREF, NE-SREF

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

---

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

---

2.7.126  FRCDSWTOTHIRD

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

•Logical Objects: EXT-SREF, NE-SREF

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

---

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

---

2.7.127  FRNGSYNC

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

•Logical Object: NE-SREF

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

---

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

---

Clear the FRNGSYNC Condition

---

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

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

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

---

2.7.128  FSTSYNC

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

•Logical Object: NE-SREF

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

The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

Note FSTSYNC is an informational alarm. The condition does not require troubleshooting.

---

2.7.129  FULLPASSTHR-BI

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

•Logical Object: STMN

The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node for an MS-SPRing 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 MS-SPRing External Switching Command" procedure.

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

---

2.7.130  GAIN-HDEG

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

•Logical Object: AOTS

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

---

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

---

Clear the GAIN-HDEG Alarm

---

Step 1 Verify fiber continuity to the port.

---

Note To verify fiber continuity, follow site practices.

---

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

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

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

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

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

Step 5 If the signal source is in Locked, disabled Admin State, put it in Unlocked state.

Step 6 If the port is in Unlocked Admin State but its output power is outside of specifications, complete the "Clear the LOS-P (OCH) Alarm" procedure.

Step 7 If the signal source is Unlocked and the power is within the expected range, come back to the card reporting the alarm and clean the fiber connected to the amplifier's COM-RX port according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH Procedure Guide.

---

Note Unplugging fiber from the COM-RX port can cause a traffic hit. To avoid this, perform a traffic switch, if possible, using the procedures outlined in the "Protection Switching, Lock Initiation, and Clearing" section. For more in-depth information about protection switches, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

---

Step 8 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem. To do this, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for acceptance testing procedures that can be used for troubleshooting purposes.

Step 9 If no other alarms exist that could be the source of the GAIN-HDEG, or if clearing an alarm did not clear the GAIN-HDEG, place all of the card ports in Locked, disabled Admin State.

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

---

Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform a traffic switch if possible.

---

---

Note When you replace a card with an identical type of card, you do not need to make any changes to the database besides restoring the card's port to the Unlocked, automaticInService service state.

---

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

---

2.7.131  GAIN-HFAIL

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

•Logical Object: AOTS

The Gain High Fail alarm is raised on DWDM OPT-BST and OPT-PRE amplifier cards when the gain crosses the high failure point threshold. The card must be replaced.

---

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

---

Clear the GAIN-HFAIL Alarm

---

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

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

---

2.7.132  GAIN-LDEG

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

•Logical Object: AOTS

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

---

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

---

Clear the GAIN-LDEG Alarm

---

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

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

---

2.7.133  GAIN-LFAIL

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

•Logical Object: AOTS

The Gain Low Fail alarm is raised on DWDM OPT-BST and OPT-PRE amplifier cards when the gain crosses the low failure point threshold. The card must be replaced.

---

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

---

Clear the GAIN-LFAIL Alarm

---

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

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

---

2.7.134  GCC-EOC

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

•Logical Object: TRUNK

The GCC Embedded Operation Channel Failure alarm applies to the OTN communication channel for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, or MXP_2.5G_10G cards. The GCC-EOC is raised when the channel cannot operate.

Clear the GCC-EOC Alarm

---

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

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

---

2.7.135  GE-OOSYNC

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

•Logical Objects: FC, GE, ISC, TRUNK

The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, and TXPP_MR_2.5G cards when the Gigabit Ethernet signal is out of synchronization and is very similar to the SDH LOS alarm. This alarm can occur when you try to input an SDH signal to the TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, or TXPP_MR_2.5G card. A signal is present, so there is no CARLOSS alarm, but it is not correctly formatted for the card and so raises the GE-OOSYNC alarm.

Clear the GE-OOSYNC Alarm

---

Step 1 Ensure that the incoming signal is provisioned with the correct physical-layer protocol.

Step 2 Ensure that the line is provisioned with the correct line speed (10 Gbps).

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

---

2.7.136  GFP-CSF

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

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

Clear the GFP-CSF Alarm

---

Step 1 Clear the service-affecting alarm at the remote data port.

Step 2 If the GFP-CSF alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.137  GFP-DE-MISMATCH

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

The GFP Fibre Channel Distance Extension (DE) Mismatch alarm indicates that a port configured for distance extension is connected to a port not operating in Cisco's proprietary Distance Extension mode. It is raised on Fibre Channel and FICON card GFP ports supporting distance extension. The alarm occurs when distance extension is enabled on one side of the transport but not on the other. To clear, distance extension must be enabled on both ports connected by a circuit.

Clear the GFP-DE-MISMATCH Alarm

---

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

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

b. Click the Provisioning > Port > General tabs.

c. Under Admin State, click the cell and choose Locked, maintenance.

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

j. Click Apply.

Step 2 If the GFP-DE-MISMATCH alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.138  GFP-EX-MISMATCH

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

The GFP Extension Header Mismatch alarm is raised on Fibre Channel/FICON cards when it receives frames with an extension header that is not null. The alarm occurs when a provisioning error causes all GFP frames to be dropped for 2.5 seconds.

The user needs to ensure both end ports are sending null extension headers for a GFP frame. An 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.

Clear the GFP-EX-MISMATCH Alarm

---

Step 1 Ensure that the vendor equipment is provisioned to send a null extension header in order to interoperate with the FC_MR-4 card. (The FC_MR-4 card always sends a null extension header.)

Step 2 If the GFP-EX-MISMATCH alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.139  GFP-LFD

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

The GFP Loss of Frame Delineation alarm applies to Fibre Channel/FICON GFP ports and occurs if there is a bad SDH connection, if SDH path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. The loss causes traffic stoppage.

Clear the GFP-LFD Alarm

---

Step 1 Look for and clear any associated SDH path errors such as LOS originating at the transmit node.

Step 2 If the GFP-LFD alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.140  GFP-NO-BUFFERS

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

The GFP Fibre Channel Distance Extension Buffer Starvation alarm is raised on Fibre Channel/FICON card ports supporting GFP and the distance extension protocol when the GFP transmitter cannot send GFP frames due to lack of remote GFP receiver buffers. This occurs when the remote GFP-T receiver experiences congestion and is unable to send frames over the Fibre Channel/FICON link.

This alarm might be raised in conjunction with the FC-NO-CREDITS alarm. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm might be raised at the upstream remote FC_MR-4 data port.

Clear the GFP-NO-BUFFERS Alarm

---

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

Step 2 If the GFP-CSF alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.141  GFP-UP-MISMATCH

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

•Logical Objects: FCMR, GFP-FAC, ML100T, ML1000

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

Clear the GFP-UP-MISMATCH Alarm

---

Step 1 Ensure that the transmit port and receive port are provisioned the same way for distance extension:

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

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

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

d. Click Apply.

Step 2 Ensure that both ports are set for the correct media type. For each port, complete the following:

a. Double-click the card to display the card view (if you are not already in card view).

b. Click the Provisioning > Port> General tabs.

c. Choose the correct media type (Fibre Channel 1Gbps, Fibre Channel 2 Gbps, FICON 1 Gbps, or FICON 2 Gbps) from the drop-down list.

d. Click Apply.

Step 3 If the GFP-UP-MISMATCH alarm does not also clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.142  HELLO

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

•Logical Object: STMN

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

---

2.7.143  HIBATVG

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

•Logical Object: PWR

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

Clear the HIBATVG Alarm

---

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

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

---

2.7.144  HI-LASERBIAS

•Default Severity: Minor (MN), Non-Service Affecting (NSA) for 2R, ESCON, FC, GE, ISC, STMN, TRUNK; Not Alarmed (NA), Non-Service Affecting (NSA) for PPM

•Logical Objects: 2R, ESCON, FC, GE, ISC, PPM, STMN, TRUNK

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

The laser bias ratio 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 can no longer be used. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.

Clear the HI-LASERBIAS Alarm

---

Step 1 Complete the "Clear the LASEREOL Alarm" procedure. Replacement is not urgent and can be scheduled during a maintenance window.

---

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

---

---

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

---

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

---

2.7.145  HI-LASERTEMP

•Default Severity: Minor (MN), Non-Service Affecting (NSA) for STMN; Not Alarmed (NA), Non-Service Affecting (NSA) for PPM

•Logical Objects: PPM, STMN

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 (STM1E, STMN)" alarm on page 2-146 is raised at the far-end node and the "DSP-FAIL" alarm on page 2-66 is raised at the near end.

Clear the HI-LASERTEMP Alarm

---

Step 1 In node view, double-click the card to display the card view.

Step 2 Click the Performance > Optics PM 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 reporting 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.146  HI-RXPOWER

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

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

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

Clear the HI-RXPOWER Alarm

---

Step 1 Find out whether the gain (the amplification power) of any amplifiers has been changed. The 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 caused 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 once 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.5.1  Perform a Facility (Line) Loopback on a Source-Node MXP/TXP/FC_MR Port" procedure on page 1-81 and test the loopback.

Step 7 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Traffic Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.

---

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

---

---

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

---

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

---

2.7.147  HITEMP

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

•Logical Objects: EQPT, NE

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

Clear the HITEMP Alarm

---

Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, refer to Figure 2-1.

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

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

---

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

---

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

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

---

Note The fan-tray assembly should run immediately when correctly inserted.

---

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

Step 8 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information. If the alarm does not clear, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service affecting problem.

---

2.7.148  HI-TXPOWER

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

•Logical Objects: 2R, ESCON, FC, GE, ISC, PPM, STMN, TRUNK

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

Clear the HI-TXPOWER Alarm

---

Step 1 In node view, display the card view for the TXP_MR_10E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Decrease (change toward the negative direction) the 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" procedure.

---

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

---

---

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

---

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

---

2.7.149  HLDOVRSYNC

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

•Logical Object: NE-SREF

The Holdover Synchronization Mode alarm indicates a loss of the primary or secondary timing reference. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS 15454 SDH. HLDOVRSYNC also usually occurs during the selection of a new node reference clock. The HLDOVRSYNC alarm indicates that the ONS 15454 SDH has gone into holdover and is using the ONS 15454 SDH internal reference clock, which is a Stratum 3-level timing device. The alarm clears when primary or secondary timing is reestablished.

Clear the HLDOVRSYNC Alarm

---

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

•FRNGSYNC

•FSTSYNC

•HLDOVRSYNC

•LOF (DS3, E1, E4, STM1E, STMN)

•LOS (STM1E, STMN)

•MANSWTOINT

•MANSWTOPRI

•MANSWTOSEC

•MANSWTOTHIRD

•SYSBOOT

•SWTOSEC

•SWTOTHIRD

•SYNC-FREQ

•SYNCPRI

•SYSBOOT

Step 2 Reestablish a primary and secondary timing source according to local site practice. If none exists, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 10, "Change Node Settings."

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

---

2.7.150  HP-ENCAP-MISMATCH

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

•Logical Object: VCTRM-HP

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

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

•The received C2 byte is not a PDI value.

•The received C2 does not match the expected C2.

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

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

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

An example situation that would raise HP-ENCAP-MISMATCH is if a circuit created between two ML-Series cards has 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 path label mismatch (PLM) such as LP-PLM.

---

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

---

---

Note For more information about the ML-Series Ethernet card, 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 HP-ENCAP-MISMATCH Alarm

---

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

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

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the correct 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 framing mode used on the receiving card:

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

b. Click the Provisioning > Card tabs.

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

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

•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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.151  HP-RFI

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

•Logical Object: VCMON-HP

The High-Order Remote Failure Indication (RFI) condition indicates that there is a remote failure indication in the high-order (VC-4 or VC-3) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The HP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the HP-RFI condition in the reporting node.

Clear the HP-RFI Condition

---

Step 1 Log into the node at the far end of the reporting ONS 15454 SDH.

Step 2 Determine whether there are any related alarms, especially the "LOS (STM1E, STMN)" alarm on page 2-146.

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

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

---

2.7.152  HP-TIM

•Default Severities: Critical (CR), Service-Affecting (SA) for VCTRM-HP; Minor (MN), Non-Service Affecting (NSA) for VCMON-HP

•Logical Objects: VCMON-HP, VCTRM-HP

The TIM High-Order TIM Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. HP-TIM occurs when there is a mismatch between the transmitted and received J1 identifier byte in the SDH path overhead. The error can originate at the transmit end or the receive end.

Clear the HP-TIM Alarm

---

Step 1 Use an optical test set capable of viewing SDH path overhead to determine the validity of the J1 byte. For specific procedures to use the test equipment, consult the manufacturer.

•Examine the signal as near to the reporting card as possible.

•Examine the signal as close as possible to the output card.

Step 2 If the output card signal is valid, complete the "Clear the SYNCPRI Alarm" 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the alarm applies to VCTRM-HP, it is a service-affecting problem.

---

2.7.153  HP-UNEQ

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

•Logical Objects: VCMON-HP, VCTRM-HP

The signal label mismatch fault (SLMF) Unequipped High-Order Path alarm applies to the C2 path signal label byte in the high-order (VC-4) path overhead. HP-UNEQ occurs when no C2 byte is received in the SDH path overhead.

Clear the HP-UNEQ Alarm

---

Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the alarm to display the Select Affected Circuits shortcut menu.

Step 3 Click Select Affected Circuits.

Step 4 When the affected circuits appear, look in the Type column for a virtual circuit (VC).

Step 5 If the Type column does not contain a VC, there are no VCs. Go to Step 7.

Step 6 If the Type column does contain a VC, attempt to delete these row(s):

---

Note The node does not allow you to delete a valid VC.

---

a. Click the VC row to highlight it. Complete the "Delete a Circuit" procedure.

b. If an error message dialog box appears, the VC is valid and not the cause of the alarm.

c. If any other rows contain VT, repeat Steps a through b.

Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the Status column of any circuits.

Step 8 If you find circuits listed as incomplete, verify that these circuits are not working circuits that continue to pass traffic, using an appropriate optical test set and site-specific procedures.

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

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels," for circuit procedures.

Step 11 Log back in and verify that all circuits terminating in the reporting card are active:

a. Click the Circuits tab.

b. Verify that the Status column lists all circuits as active.

Step 12 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

---

Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

---

---

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

---

---

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

---

Step 13 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the optical and/or electrical cards.

---

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

---

---

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

---

Step 14 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.154  I-HITEMP

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

•Logical Object: NE

The Industrial High Temperature alarm occurs when the temperature of the ONS 15454 SDH 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a service-affecting problem.

---

2.7.155  IMPROPRMVL

•Default Severity: Critical (CR), Service-Affecting (SA for active card)

•Logical Objects: EQPT, PPM

The Improper Removal alarm for equipment occurs when a card is physically removed from its slot before being deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm; CTC only has to recognize that the card is not present. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node. For PPM, the alarm occurs if you provision a PPM but no physical module is inserted on the port.

---

Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove it, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot.

---

---

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

---

---

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

---

---

Note When a MIC-A/P card is removed from the shelf, no IMPROPRMVL alarm is reported for that card. The FMEC to the left side of the MIC-A/P also may also disappear from view in CTC. This functions as designed. The MIC-A/P card provides a communication channel to the other FMEC. When the MIC card is removed, the communication channel is no longer available and consequently, the other FMEC is assumed not to be present. The disappeared FMEC is rediscovered when the MIC-A/P is reinserted.

---

Clear the IMPROPRMVL Alarm

---

Step 1 In node view, right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.

---

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

---

Step 3 If any ports on the card are in service, lock them (Locked, maintenance):

---

Caution Before locking a port (Locked, maintenance or Locked, disabled), ensure that no live traffic is present.

---

a. In node view, double-click the reporting card to display the card view.

b. Click the Provisioning > Line tab.

c. Click the Admin State column of any unlocked ports.

d. Choose Locked, maintenance to take the ports out of service.

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

---

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

---

Step 5 If the card is paired in a protection scheme, delete the protection group:

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 SDH 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 to delete all of the selected terminations.

Step 7 If the card is used as a timing reference, change the timing reference:

a. Click the Provisioning > Timing tabs.

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

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

d. Click Apply.

Step 8 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.

Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.156  INC-ISD

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

•Logical Object: DS3

The DS-3 Idle condition indicates that the DS3i-N-12 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 a Locked, maintenance Admin State. It is resolved when the Locked, maintenance state ends.

---

Note INC-ISD is an informational condition. The condition does not require troubleshooting.

---

2.7.157  INHSWPR

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

•Logical Object: EQPT

The Inhibit Switch To Protect Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.

Clear the INHSWPR Condition

---

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

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

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

---

2.7.158  INHSWWKG

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

•Logical Object: EQPT

The Inhibit Switch To Working Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) 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 on to 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 Protection Port Manual Switch Command" procedure.

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

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

---

2.7.159  INTRUSION-PSWD

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

•Logical Object: NE

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

Clear the INTRUSION-PSWD Condition

---

Step 1 Click the Provisioning > Security tabs.

Step 2 Click Clear Security Intrusion Password Alarm.

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

---

2.7.160  INVMACADR

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

•Logical Object: BPLANE

The Equipment Failure Invalid Media Access Control (MAC) Layer address alarm occurs when the ONS 15454 SDH MAC address is invalid. The MAC address is permanently assigned to the ONS 15454 SDH chassis during manufacture. Do not attempt to troubleshoot an INVMACADR. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

2.7.161  IOSCFGCOPY

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

•Logical Object: EQPT

The Cisco IOS Configuration Copy in Progress condition occurs on ML-Series Ethernet cards when a Cisco IOS startup configuration file is being uploaded to or downloaded from an ML-Series card. (This condition is very similar to the SFTWDOWN condition 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 could be raised.)

---

Note IOSCFGCOPY is an informational condition.

---

---

Note For more information about the ML-Series Ethernet card, 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.162  KB-PASSTHR

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

•Logical Object: STMN

The K Bytes Pass Through Active condition occurs on a nonswitching node in an MS-SPRing when the protect channels on the node are not active and the node is in K Byte pass-through state.

Clear the KB-PASSTHR Condition

---

Step 1 Complete the "Clear a MS-SPRing External Switching Command" procedure.

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

---

2.7.163  KBYTE-APS-CHANNEL-FAILURE

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

•Logical Object: STMN

The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For instance, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.

This alarm is also raised during checksum. Failure occurs 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 MS-AIS, "LOF (DS3, E1, E4, STM1E, STMN)" alarm on page 2-135, "LOS (STM1E, STMN)" alarm on page 2-146, or SFBER-EXCEED-HO alarms.

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

---

Step 1 The alarm most frequently is raised due to mismatched span provisioning. In this case, reprovision one side of the span to match the parameters of the other side. To do this, refer to the Cisco ONS 15454 SDH Procedure Guide Channel 5, "Turn Up Network."

Step 2 If the error is not caused by misprovisioning, it is due to checksum errors within an STM-N, cross-connect, or TCC2/TCC2P card. In this case, complete the "Side Switch the Active and Standby XC10G Cross-Connect Cards" procedure to allow CTC to resolve the issue.

Step 3 If third-party equipment is involved, ensure that it is configured for the same APS channel as the Cisco ONS equipment.

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

---

2.7.164  LAN-POL-REV

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

•Logical Object: NE

The Lan Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised during 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.

Clear the LAN-POL-REV Condition

---

Step 1 Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

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

---

2.7.165  LASER-APR

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

•Logical Object: AOTS

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

---

Note LASER-APR is an informational condition and does not require troubleshooting.

---

2.7.166  LASERBIAS-DEG

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

•Logical Objects: AOTS, OTS

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

Clear the LASERBIAS-DEG Alarm

---

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

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

---

2.7.167  LASERBIAS-FAIL

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

•Logical Object: AOTS

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

Clear the LASERBIAS-FAIL Alarm

---

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

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

---

2.7.168  LASEREOL

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

•Logical Object: STMN

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

Clear the LASEREOL Alarm

---

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

---

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

---

---

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

---

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

---

2.7.169  LASERTEMP-DEG

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

•Logical Object: AOTS

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

Clear the LASERTEMP-DEG Alarm

---

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

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

---

2.7.170  LCAS-CRC

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

•Logical Objects: VCTRM-HP, VCTRM-LP

The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against ML-Series Ethernet cards. It occurs when there is an equipment, path, or provisioning error on the virtual concatenation group (VCG) that causes consecutive 2.5 second CRC failures in the LCAS control word.

The condition can occur if an LCAS-enabled node (containing ML-Series cards) transmitting to another LCAS-enabled node delivers faulty traffic due to an equipment or SDH path failure. Transmission errors would also be reflected in CV-P, ES-P, or SES-P performance monitoring statistics. If these errors do not exist, an equipment failure is indicated.

If LCAS is not supported on the peer node, the condition 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.

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 SDH path errors exist, ensure that the remote node has LCAS enabled on the circuit:

Step 4 In node view, click the Circuit tab.

Step 5 Choose the VCAT circuit and click Edit.

Step 6 In the Edit Circuit window, click the General tab.

Step 7 Verify that the Mode column says LCAS.

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

---

2.7.171  LCAS-RX-FAIL

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

•Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Receive-Side-In Fail condition is raised against FC_MR-4 cards and ML-Series Ethernet cards with LCAS-enabled VCG.

---

Note ML-Series cards are LCAS-enabled. ML-Series and FC_MR-4 cards are SW-LCAS enabled.

---

LCAS VCGs treat failures unidirectionally, meaning that failures of the transmit or receive points occur independently of each other. The LCAS-RX-FAIL condition can occur on the receive side of an LCAS VCG member for the following reasons:

•SDH 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 SDH path failure.

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

---

2.7.172  LCAS-TX-ADD

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

•Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-Series Ethernet cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed.

---

Note LCAS-TX-ADD is an informational condition and does not require troubleshooting.

---

2.7.173  LCAS-TX-DNU

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

•Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Tx Side In Do Not Use condition is raised on FC_MR-4 cards and ML-Series Ethernet cards when the Tx 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 node reporting this condition likely reports an HP-RFI alarm, and the remote node likely reports a path alarm such as MS-AIS or "HP-UNEQ" alarm on page 2-120.

---

Note LCAS-TX-DNU is an informational condition and does not require troubleshooting.

---

2.7.174  LKOUTPR-R

The Lockout of Protection Ring condition is not used in this platform in this release. It is reserved for future development.

2.7.175  LKOUTPR-S

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

•Logical Object: STMN

The Lockout of Protection Span condition occurs on an MS-SPRing node when traffic is locked out of a protect span using the LOCKOUT SPAN command.

Clear the LKOUTPR-S Condition

---

Step 1 Complete the "Clear a MS-SPRing External Switching Command" procedure.

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

---

2.7.176  LKOUTWK-R

The LKOUTWK-R alarm is not used in this platform in this release. It is reserved for future development.

2.7.177  LKOUTWK-S

The LKOUTWK-S alarm is not used in this platform in this release. It is reserved for future development.

2.7.178  LMP-HELLODOWN

The LMP-HELLODOWN alarm is not used in this platform in this release. It is reserved for future development.

2.7.179  LMP-NDFAIL

The LMP-NDFAIL alarm is not used in this platform in this release. It is reserved for future development.

2.7.180  LOA

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

•Logical Object: VCG

The Loss of Alignment on a VCG is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.

---

Note This alarm occurs only if you provision circuits outside of CTC, such as by using TL1.

---

Clear the LOA Alarm

---

Step 1 In network view, click the Circuits tab.

Step 2 Click the alarmed VCG and then click Edit.

Step 3 In the Edit Circuit dialog box, click Show Detailed Map to see the source and destination circuit slots, ports, and STSs.

Step 4 Identify whether the STS travels across different fibers. If it does, complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit using the procedure in the Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels."

Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.181  LOCKOUTOFPR

The Lockout of Protection condition is not supported in this release. It is reserved for future development.

2.7.182  LOCKOUT-REQ

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

•Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, STMN, TRUNK, VCMON-HP, VCMON-LP

The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an STM-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 Card or Port Lock On or Lock Out Command" procedure.

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

---

2.7.183  LOCKOUT-REQ-RING

The Lockout Request Ring condition is not supported in this release. It is reserved for future development.

2.7.184  LOF (BITS)

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

•Logical Object: BITS

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

---

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

---

Clear the LOF (BITS) Alarm

---

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

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

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

c. Click the Provisioning > Timing tabs to display the General Timing window.

d. Verify that the value listed in Coding matches the coding of the BITS timing source (either B8ZS or AMI).

e. If the coding does not match, click the BITS-1 or BITS2 Coding field and choose the appropriate coding from the drop-down list.

f. Verify that the value listed in the Framing field matches the framing of the BITS timing source (either ESF or SF).

g. If the framing does not match, click the BITS-1 or BITS-2 Framing field and choose the appropriate framing from the drop-down list.

---

Note On the timing subtab, the binary 8-zero substitution (B8ZS) coding field is normally paired with Extended Superframe (ESF) in the Framing field and the alternate mark inversion (AMI) coding field is normally paired with SF (D4) in the Framing field.

---

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

---

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

---

---

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

---

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

---

2.7.185  LOF (DS3, E1, E4, STM1E, STMN)

•Default Severity: Critical (CR), Service-Affecting (SA) for DS3, E4, STMN, STM1E

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

•Logical Objects: DS3, E1, E4, STM1E, STMN

An LOF alarm on DS3i-N-12, E1-N-14, or E1-42 card for these objects means that the receiving ONS 15454 SDH has lost frame delineation in the incoming data. LOF occurs when the SDH overhead loses a valid framing pattern for three seconds. Receiving two consecutive valid patterns clears the alarm.

Clear the LOF (DS3, E1, E4, STM1E, STMN) Alarm

---

Step 1 Verify that the line framing and line coding match between the port and the signal source:

a. In CTC, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the signal source for the card reporting the alarm. You might need to contact your network administrator for the format information.

c. Display the card view of the reporting 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.

f. If the signal source line type does not match the reporting port, click Line Type and choose the appropriate type from the drop-down list.

g. Verify that the reporting Line Coding matches the signal source's line type.

h. If the signal source line coding does not match the reporting port, click Line Coding and choose the appropriate type from the drop-down list.

i. Click Apply.

Step 2 If the alarm does not clear when the coding and framing of the ONS 15454 SDH match the coding and framing of the signal source, replace the card.

---

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

---

---

Note When replacing a card with an identical type of card, you do not need to change the CTC database.

---

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

---

2.7.186  LOF (TRUNK)

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

•Logical Object: TRUNK

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

Clear the LOF (TRUNK) Alarm

---

Step 1 Complete the "Clear the LOF (DS3, E1, E4, STM1E, STMN) Alarm" procedure.

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

---

2.7.187  LO-LASERBIAS

The LO-LASERBIAS alarm is not used in this platform in this release. It is reserved for future development.

2.7.188  LO-LASERTEMP

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

•Logical Object: STMN

The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. HI-LASERTEMP occurs when the internally measured transceiver temperature falls below the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength. (Two degrees temperature 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 (STM1E, STMN)" alarm on page 2-146 is raised at the far-end node and the "DSP-FAIL" alarm on page 2-66 is raised at the near end. To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM > Current PM tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Clear the LO-LASERTEMP Alarm

---

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

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

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

---

2.7.189  LOM

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

•Logical Objects: TRUNK, VCTRM-HP, VCTRM-LP

The optical transport unit (OTU) Loss of Multiframe is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, or TXPP_MR_2.5G cards when the Multi Frame Alignment Signal (MFAS) overhead field is errored for more than five frames and persists for more than three milliseconds.

Clear the LOM Alarm

---

Step 1 Complete the "Clear the SD (DS3, E1, E3, E4, STM1E, STMN, VCTRM-LP) Condition" procedure.

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

---

2.7.190  LO-RXPOWER

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

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

The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable.

Clear the LO-RXPOWER Alarm

---

Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits.

Step 2 Find out whether new channels have been added to the fiber. Up to 32 channels can be transmitted on the same fiber, but the number of channels affects power. If channels have been added, the 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 the gain (amplification power) of any amplifiers has been changed. Changing amplification also causes channel power to need adjustment.

Step 4 If the alarm does not clear, remove any receive fiber attenuators or replace them with lower-resistance attenuators.

Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide Chapter 15, "Maintain the Node."

Step 6 If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility (line) loopback on a known-good port. The error readings you get 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 ports of the transmit or receive card, do a facility loopback on the transmit and receive ports with known-good loopback cable. Complete the Create the Facility (Line) Loopback on the Source Optical Port, page 1-40 and test the loopback.

Step 8 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Traffic Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.

---

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

---

---

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

---

Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.191  LOS (2R)

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

•Logical Object: 2R

The Loss of Signal for a 2R client applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.

Clear the LOS (2R) Alarm

---

Step 1 Complete the "LOS (STM1E, STMN)" alarm on page 2-146.

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

---

2.7.192  LOS (BITS)

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

•Logical Object: BITS

The LOS (BITS) alarm indicates that the TCC2/TCC2P card has an LOS from the BITS timing source. An LOS (BITS) occurs when an SDH receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (BITS) means the BITS clock or the connection to the BITS clock failed.

Clear the LOS (BITS) Alarm

---

Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15454 SDH backplane to the timing source.

---

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

---

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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.193  LOS (DS3)

•Default Severities: Critical (CR), Service-Affecting (SA) for DS3

•Logical Objects: DS3

A LOS (DS3) alarm for a DS3i-N-12 port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line.

Clear the LOS (DS3) 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 Cisco ONS 15454 SDH Procedure Guide, Chapter 2, "Install Cards and Fiber-Optic Cables."

---

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

---

Step 2 Consult site records to determine whether the port raising the alarm has been assigned.

Step 3 If the port is not currently assigned, place the port out of service using the following steps:

a. Double-click the DS3i-N-12 card to display the card view.

b. Click the Maintenance > DS3 tabs.

c. Under Admin State, click Locked, disabled.

d. Click Apply.

Step 4 If the port is assigned, verify that the correct port is in service:

a. To confirm this physically, confirm that the LED is correctly illuminated on the physical card.

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

b. To determine this virtually, double-click the card in CTC to display the card view.

•Click the Provisioning > Line tabs.

•Verify that the Admin State column lists the port as Unlocked.

•If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked. Click Apply.

Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. For specific procedures to use the test set equipment, consult the manufacturer.

Step 6 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide.

Step 7 If there is a valid signal, replace the electrical connector on the ONS 15454 SDH.

Step 8 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."

Step 9 Repeat Steps 1 to 8 for any other port on the card that reports the LOS.

Step 10 If no other alarms are present that could be the source of the LOS (DS-1), or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic Card" procedure for the reporting card.

---

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

---

---

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

---

Step 11 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.194  LOS (E1, E3, E4)

•Default Severity: Critical (CR), Service-Affecting (SA) for E3, E4, STMN, STM1E; Major (MJ), Service-Affecting (SA) for E1

•Logical Objects: E1, E3, E4

LOS on an EC-N port occurs when a SDH receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (EC-N) means that the upstream transmitter has failed. If an EC-N LOS alarm is not accompanied by additional alarms, a cabling problem is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.

---

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 (E1, E3, E4) 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 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.

---

---

Note To verify cable continuity, follow site practices.

---

Step 2 If the cabling is okay, verify that the correct port is in service:

a. Confirm that the LED is correctly lit on the physical card.

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

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

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked. Click Apply.

Step 3 If the correct port is in service, use an optical test set to confirm that a valid signal exists on the line.

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

Step 4 If the signal is valid, ensure that the transmit and receive outputs from the electrical panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cables."

Step 5 If a valid signal exists, replace the cable connector on the ONS 15454 SDH.

Step 6 Repeat Steps 1 through 5 for any other port on the card that reports the LOS (EC-N).

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

Step 8 If no other alarms exist that could be the source of the LOS (EC-N), or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Traffic Card" procedure for the reporting card.

---

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

---

---

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

---

Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.195  LOS (ESCON)

The LOS alarm for ESCON is not used in this platform in this release. It is reserved for future development.

2.7.196  LOS (FUDC)

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

•Logical Object: FUDC

The LOS (FUDC) alarm is raised if there is a UDC circuit created on the AIC-I DCC port but the port is not receiving signal input. The downstream node has an AIS condition raised against AIC-I DCC port transmitting the UDC.

Clear the LOS (FUDC) Alarm

---

Step 1 Verify cable continuity to the AIC-I UDC port.

---

Note To verify cable continuity, follow site practices.

---

Step 2 Verify that there is a valid input signal using a test set.

Step 3 If there is a valid signal, clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH 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 Cisco ONS 15454 SDH Procedure Guide Chapter 6, "Create Circuits and Low-Order Tunnels."

c. If a user data circuit exists (shown as User Data F1 under the Type column), check the source and destination ports. These must be located on AIC-I cards to function.

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

Step 6 If no other alarms exist that could be the source of the LOS (FUDC), or if clearing another alarm did not clear the LOS, complete the "Physically Replace a Traffic Card" procedure for the reporting card.

---

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

---

---

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

---

Step 7 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.197  LOS (ISC)

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

•Logical Object: ISC

The LOS alarm for the ISC port applies to TXP_MR_2.5G client PPMs provisioned at the ISC port rate. Troubleshooting is similar to the LOS (2R) alarm.

Clear the LOS (ISC) Alarm

---

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

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

---

2.7.198  LOS (MSUDC)

The LOS (MSUDC) alarm is not supported in this release. It is reserved for future development.

2.7.199  LOS (OTS)

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

•Logical Object: OTS

The Loss of Signal for the OTS applies to the LINE-3-RX port of the OPT-BST amplifier and the LINE-2-RX port of the OSC-CSM card. It indicates that a fiber cut has occurred and no power is being received from the span. Troubleshooting for this alarm is similar to "LOS (STM1E, STMN)" alarm on page 2-146.

Clear the LOS (OTS) Alarm

---

Step 1 Verify fiber continuity to the port.

---

Note To verify fiber continuity, follow site practices.

---

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

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

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

b. Click the Provisioning > Opt. Ampli. Line > Optics Thresholds tabs.

c. Compare the opwrMin (dBm) column value with the MetroPlanner-generated value. (For more information about using MetroPlanner, refer to the Cisco MetroPlanner DWDM Operations Guide).

Step 4 If the optical power level is within specifications, check and modify the channel LOS and OSC LOS thresholds, then run automatic node setup (ANS) to execute the changes. (For more information about ANS, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.)

a. In node view, click the Provisioning > WDM-ANS > Provisioning tabs.

b. Consult the Cisco MetroPlanner DWDM Operations Guide to decide what values to use, then modify the following items:

•West Side Rx. Channel OSC LOS Threshold

•West Side Rx. Channel LOS Threshold

c. Click the WDM-ANS > Port Status tabs.

d. Click Launch ANS and click Yes in the confirmation dialog box.

Step 5 If the optical power is outside of the expected range, check the power level transmitted at the other side of the span using CTC:

a. On the transmitting node, double-click the transmitting MXP or TXP to display the card view.

b. Click the Provisioning > Optics Thresholds tab.

c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.

Step 6 If the transmitted power value is within the expected range, clean the receiving node (where the LOS is raised) and clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH Procedure Guide.

Step 7 If the transmitted power value is outside of the expected range, troubleshoot using the DWDM acceptance tests in the Cisco ONS 15454 DWDM Installation and Operations Guide.

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

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

---

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

---

---

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

---

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

---

2.7.200  LOS (STM1E, STMN)

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

•Logical Objects: STM1E, STMN

A LOS alarm for an STM1E or STM-N port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure.

---

Note If a circuit shows an incomplete 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 LOS (STM1E, STMN) 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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cables."

---

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

---

If an optical time-division multiplexing (TDM) signal such as an STM-1 or STM-4 is plugged into an E1000-2-G or G1000-4 card GBIC connector, this can trigger an LOS.

Step 2 Consult site records to determine whether the port raising the alarm has been assigned.

Step 3 If the port is assigned, verify that the correct port is in service:

a. To confirm this physically, confirm that the card shows a green LED on the physical card.

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

b. To determine this virtually, double-click the card in CTC to display the card view.

•Click the Provisioning > Line tabs.

•Verify that the Admin State column lists the port as Unlocked.

c. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked.

d. Click Apply.

Step 4 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 5 Ensure that the transmit and receive outputs from the electrical panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 SDH Procedure Guide.

Step 6 If there is a valid signal, replace the electrical connector on the ONS 15454 SDH.

Step 7 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 Cisco ONS 15454 SDH Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cables."

Step 8 Repeat Steps 1 to 7 for any other port on the card that reports the LOS.

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

---

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

---

---

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

---

Step 10 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.201  LOS (TRUNK)

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

•Logical Object: TRUNK

The Loss of Signal for a TRUNK applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.

Clear the LOS (TRUNK) Alarm

---

Step 1 Verify fiber continuity to the port.

---

Note To verify fiber continuity, follow site practices.

---

Step 2 If the cabling is okay, verify that the correct port is in service:

a. Confirm that the LED is correctly illuminated on the physical card.

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

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

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as Locked, maintenance or Locked, disabled, click the column and choose Unlocked. Click Apply.

Step 3 If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH Procedure Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the TXP or MXP card receiver specifications. Refer to the Cisco ONS 15454 SDH 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 (TRUNK) alarm.

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

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

---

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

---

---

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

---

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

---

2.7.202  LOS-O

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

•Logical Objects: OCH, OMS, OTS

The Incoming Overhead Loss of Signal alarm applies to the OSC-RX port of the OPT-BST card (LINE-2-RX), the OSC-RX port of the OSCM card (LINE-1-RX), and the internal optical port of OSC-CSM card (LINE-3-RX Port 3). It is raised when the monitored input power crosses the FAIL-LOW threshold and the OSC signal is lost. The is alarm is demoted if another LOS alarm is also present.

Clear the LOS-O Alarm

---

Step 1 Verify fiber continuity to the port.

---

Note To verify fiber continuity, follow site practices.

---

Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.

Step 3 Verify that the received power (opwrMin) is within the expected range shown in Cisco MetroPlanner. To check the level:

a. Double-click the amplifier card to display the card view.

b. Display the optical thresholds by clicking the following tabs:

•OPT-BST card Provisioning > Opt. Ampli. Line > Optics Thresholds tabs

•OSCM card Provisioning > Optical Line > Optics Thresholds tabs

Step 4 If the optical power level is within specifications, check and modify the OSC LOS threshold, then run ANS to execute the changes. (For more information about ANS, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.)

a. In node view, click the Provisioning > WDM-ANS > Provisioning tabs.

b. Consult the Cisco MetroPlanner DWDM Operations Guide to decide upon values, then modify the West Side Rx. Channel OSC LOS Threshold.

c. Click the WDM-ANS > Port Status tabs.

d. Click Launch ANS and click Yes in the confirmation dialog box.

Step 5 If the port power is outside of the expected range, verify that OSC connections have been created on the other side of the span. If the connections are not present, refer to the Cisco ONS 15454 SDH Procedure Guide Chapter 4, "Turn Up Node," chapter for procedures.

Step 6 If OSC connections are present, check the OSC transmitted power using CTC:

a. On the transmitting node, double-click the transmitting OSC-CSM to display the card view.

b. Click the Provisioning > Optics Thresholds tab.

c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.

Step 7 If the transmitted OSC value is out of range, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for DWDM acceptance test procedures that aid in troubleshooting the problem.

Step 8 If the OSC value is within range, come back to the port reporting the LOS-O alarm and clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in Chapter 15, "Maintain the Node," of the Cisco ONS 15454 SDH Procedure Guide.

Step 9 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.

Step 10 If no other alarms exist that could be the source of the LOS-O, or if clearing an alarm did not clear the LOS-O, place all of the card ports in Locked, disabled Admin State.

Step 11 Complete the "Physically Replace a Traffic Card" procedure for the reporting card.

---

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

---

---

Note When you replace a card with an identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the Unlocked, automaticInService Admin State.

---

Step 12 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.203  LOS-P (OCH)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: OCH

The Loss of Signal for Optical Channel alarm on the OCH layer applies to the channel ADD or pass-through ports on the AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, 32MUX-O and 32WSS-O DWDM cards.

---

Note For 32WSS-O cards, this alarm also applies to pass-through ports. If the LOS-P (OCH) alarm is raised against this kind of port, it means that the port does not have an optical power source directly connected to it. Follow the general troubleshooting rules stated in the chapter Network Level (inter-nodes) Troubleshooting to identify upstream alarms in the logical signal flow that could cause an LOS-P.

---

LOS-P (OCH) indicates a loss of receive signal when the monitored input power value has crossed the Power Failure Low threshold associated with the port. This threshold value is relative to the specific variable optical attenuation (VOA) power reference setpoint provisioned on VOA along the path.

Clear the LOS-P (OCH) Alarm

---

Step 1 Check the LED behavior on the physical card. A green ACT/SBY LED indicates an active card, and a red ACT/SBY LED indicates a failed card. If the LED is red, complete the "Physically Replace a Traffic Card" procedure and continue to Step 9.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS, AINS admin state.

---

Step 2 Verify that there truly is a loss of received signal by completing the following steps:

a. Double-click the card to display the card view.

b. View the proper input power values by clicking one of the following tabs as appropriate:

•AD-xC Provisioning > Optical Chn > Parameters

•32MUX-O Provisioning > Optical Chn > Parameters

•32WSS-O Provisioning > Optical Chn: Optical Connector x > Parameters

c. Display the proper Power Failure Low threshold by clicking one of the following tabs as appropriate:

•AD-xC Provisioning > Optical Chn > Optics Thresholds

•32MUX-O Provisioning > Optical Chn > Optics Thresholds

•32WSS-O Provisioning > Optical Chn: Optical Connector x > Optics Thresholds

---

Tip To view the alarm thresholds (as opposed to the warning thresholds), check the Alarm check box on the Optics Thresholds tab and click Reset.

---

d. Compare the actual assigned Power value with the Alarm Threshold value and complete one of the following actions:

•If the Power value is less than the Fail Low threshold, go to Step 3.

•If the Power value is greater than the Fail Low threshold plus the alarm allowance value (default 1 dBm), complete the "Reset a Traffic Card in CTC" procedure for the card.

If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure and continue to Step 9.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS, AINS admin state.

---

Step 3 Verify the fiber continuity to the port. To verify fiber continuity, follow site practices.

Step 4 In MetroPlanner, obtain the "Internal Connections" file for the node where the errored card is located. If necessary, correct the node cabling in accordance with the MP file connections list. For procedures to cable a DWDM node, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 5 If the cabling is good, verify that each involved optical signal source, including TXP, MXP or ITU-T line card trunk transmit ports, is in the IS admin state. To do this, click the following tabs as appropriate:

•TXP_MR_10G Provisioning > Line > SDH

•TXP_MR_10E Provisioning > Line > SDH

•TXP_MR_2.5G Provisioning > Line > SDH

•TXPP_MR_2.5G Provisioning > Line > STM16

•MXP_MR_2.5G Provisioning > Line > STM16

•MXPP_MR_2.5G Provisioning > Line > STM16

•MXP_2.5G_10E Provisioning > Line > Trunk

•MXP_2.5G_10G Provisioning > Line > SDH

If the port admin state is not IS, choose IS from the Admin state drop-down list. If the alarm does not clear, continue with Step 6.

Step 6 If the signal source is in IS admin state, use an optical test set to verify that the transmit laser is active. For specific procedures to use the test set equipment, consult the manufacturer.

Step 7 If the laser is active, compare the card's provisioned transmit optical power value with the expected range in the "Hardware Specifications" appendix of the Cisco ONS 15454 SDH Procedure Guide. To display the provisioned transmit optical power values, click the following tabs as appropriate:

•TXP_MR_10G Performance > Optics PM > Current Values > Trunk Port

•TXP_MR_10E Performance > Optics PM > Current Values > Trunk Port

•MXP_2.5G_10E Performance > Optics PM > Current Values > Trunk Port

•MXP_2.5G_10G Performance > Optics PM > Current Values > Trunk Port

Step 8 Use an optical test set to measure actual transmit optical power for the following cards as applicable:

•TXP_MR_2.5G

•TXPP_MR_2.5G

•MXP_MR_2.5G

•MXPP_MR_2.5G

•Each ITU-T line card

If the tested optical transmit optical power is comparable to the correctly provisioned value and the expected value, go to Step 9. If the tested, actual power value is outside the specification range, complete the "Physically Replace a Traffic Card" procedure. When the newly installed card becomes active, verify that the LOS-P (OCH) alarm clears. If it does not, continue with Step 9.

---

Tip If a spare cards is unavailable and the transmit power still functions, you can temporarily clear the LOS-P alarm by following the general procedure to add path VOAs during startup failure located in the Cisco ONS 15454 DWDM Installation and Operations Guide.

---

Step 9 If the power is within the expected range, clean the alarmed port's fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.

---

Note Unplugging the fiber can cause a traffic hit. To avoid this, perform a traffic switch if possible. See the "Protection Switching, Lock Initiation, and Clearing" section for basic instructions, or refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for more detailed information.

---

Step 10 If the alarm does not clear, follow the general procedure for adding path VOAs during startup failure in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 11 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.

---

2.7.204  LOS-P (OMS, OTS)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: OMS, OTS

The Loss of Signal for Optical Channel alarm (OMS or OTS layer) applies to all input ports of the following DWDM cards: AD-1B-xx.x, AD-4B-xx.x, 32 DMX, 32DMX-O, OPT-PRE, OPT-BST, and OSC-CSM.

For AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, 32MUX-O and 32WSS cards, this alarm applies only to the COM-RX, EXP-RX, xxBAND-RX input ports where an aggregate signal is managed. (These ports are solely used for the OMS and OTS layers.)

LOS-P (OMS or OTS) indicates a loss of receive signal when the monitored input power value has crossed the Power Failure Low Threshold associated to the port.

---

Note When LOS-P alarm is raised on the LINE-RX port of the OPT-BST or OSC-CSM card; please refer directly to the Cisco ONS 15454 DWDM Installation and Operations Guide for a fiber cut detection troubleshooting procedure.

---

Clear the LOS-P (OMS, OTS) Alarm

---

Step 1 Check the LED behavior on the physical card. A green ACT/SBY LED indicates an active card, and a red ACT/SBY LED indicates a failed card. If the LED is red, complete the "Physically Replace a Traffic Card" procedure and continue to Step 7.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the Unlocked admin state.

---

Step 2 Verify that there truly is a loss of input signal by completing the following steps:

a. Double-click the card to display the card view.

b. Verify the proper input power values by clicking one of the following tabs as appropriate:

•OPT-BST Provisioning > Optical Line > Parameters

•OPT-PRE Provisioning > Optical Line > Parameters

•AD-xC Provisioning > Optical Line > Parameters

•AD-xB Provisioning > Optical Line > Parameters

•AD-xB Provisioning > Optical Line > Parameters

•32MUX-O Provisioning > Optical Line > Parameters

•32WSS Provisioning > Optical Line > Parameters

•32DMX-O Provisioning > Optical Line > Parameters

•32DMX Provisioning > Optical Line > Parameters

•OSC-CSM Provisioning > Optical Line > Parameters

c. Display the proper Power Failure Low threshold by clicking one of the following tabs as appropriate:

•OPT-BST Provisioning > Optical Line > Optics Thresholds

•OPT-PRE Provisioning > Optical Line > Optics Thresholds

•AD-xC Provisioning > Optical Line > Optics Thresholds

•AD-xB Provisioning > Optical Line > Optics Thresholds

•AD-xB Provisioning > Optical Line > Optics Thresholds

•32MUX-O Provisioning > Optical Line > Optics Thresholds

•32WSS Provisioning > Optical Line > Optics Thresholds

•32DMX-O Provisioning > Optical Line > Optics Thresholds

•32DMX Provisioning > Optical Line > Optics Thresholds

•OSC-CSM Provisioning > Optical Line > Optics Thresholds

---

Tip To view the alarm thresholds (as opposed to the warning thresholds), check the Alarm check box on the Optics Thresholds tab and click Reset.

---

d. Compare the actual assigned Power value with the Alarm Threshold value and complete one of the following actions:

•If the Power value is less than the Fail Low threshold, go to Step 3.

•If the Power value is greater than the Fail Low threshold plus the alarm allowance value (default is 1 dBm), complete the "Reset a Traffic Card in CTC" procedure for the card.

Step 3 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure and continue to Step 7.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the Unlocked admin state.

---

Step 4 Verify the fiber continuity to the port. To verify fiber continuity, follow site practices.

Step 5 In MetroPlanner, obtain the "Internal Connections" file for the node where the errored card is located. If necessary, correct the node cabling in accordance with the MP file connections list. For procedures to cable a DWDM node, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 6 If the cabling is good, use an optical test set to measure the power value on the output port connected to the alarmed card. For specific procedures to use the test set equipment, consult the manufacturer. If the power difference reported is greater than 1 dBm (standard fiber jumper insertion loss is 0.3 dBm), 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 SDH Procedure Guide.

---

Note Unplugging the fiber can cause a traffic hit. To avoid this, perform a traffic switch if possible. See the "Protection Switching, Lock Initiation, and Clearing" section for basic instructions, or to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for more detailed information.

---

Step 7 If the alarm does not clear, follow the general troubleshooting procedures for identifying upstream alarms in the logical signal flow (that could cause an LOS-P) located in the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 8 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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

---

2.7.205  LOS-P (TRUNK)

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: TRUNK

The Loss of Signal for Optical Channel alarm indicates that no optical power is detected at the input trunk port for the following cards:

•TXP_MR_10G

•TXP_MR_10E

•MXP_2.5G_10E

•MXP_2.5G_10G

•TXP_MR_2.5G

•TXPP_MR_2.5G

•MXP_MR_2.5G

•MXPP_MR_2.5G

•All ITU-T line cards

Clear the LOS-P (TRUNK) Alarm

---

Step 1 Check the LED behavior on the physical card. A green ACT/SBY LED indicates an active card, and a red ACT/SBY LED indicates a failed card. If the LED is red, complete the "Physically Replace a Traffic Card" procedure and continue to Step 7.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS, AINS admin state.

---

Step 2 Verify that there truly is a loss of received optical power by completing the following steps:

a. Double-click the alarmed card to display the card view.

b. Click the Performance > Optics PM > Current Values > Trunk Port tab.

c. Compare the actual received power levels with the expected power range given in the Cisco ONS 15454 DWDM Installation and Operations Guide. Then take one of the following actions:

•If power is less than -40 dBm, go to Step 6.

•If power is greater than -40 dBm and within the expected range, complete the "Reset a Traffic Card in CTC" procedure for the card.

Step 3 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting card and then go to Step 9.

---

Note When you replace a card with the identical type of card, you do not need to make any changes to the database apart from restoring the card's port to the IS, AINS admin state.

---

Step 4 Verify the fiber continuity to the port. To verify fiber continuity, follow site practices.

Step 5 In MetroPlanner, obtain the "Internal Connections" file for the node containing the alarmed card. If necessary, correct the node cabling in accordance with the MP file connections list. For procedures to cable a DWDM node, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.

Step 6 If the cabling is good, use a test set to verify the power value on the DWDM CH_DROP-TX port on the AD-xC, 32DMX-O, or 32DMX.

Step 7 If the power difference reported is greater than 1 dBm (standard fiber jumper insertion loss is 0.3 dBm), 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 SDH Procedure Guide.

---

Note Unplugging the fiber can cause a traffic hit. To avoid this, perform a traffic switch if possible. See the "Protection Switching, Lock Initiation, and Clearing" section for basic instructions, or refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for more detailed information.

---

Step 8 If the alarm does not clear, follow the general troubleshooting rules in the Cisco ONS 15454 DWDM Installation and Operations Guide that are given for identifying upstream alarms in the logical signal flow that could cause an LOS-P.

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 log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

---

2.7.206  LO-TXPOWER

•Default Severity: Minor (MN), Non-Service Affecting (NSA)

•Logical Objects: 2R, ESCON, FC, GE, ISC, PPM, STMN, TRUNK

The Equipment Low Transmit Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, and MXP_2.5G_10G card transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.

Clear the LO-TXPOWER Alarm

---

Step 1 Display the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, or MXP_2.5G_10G card view.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Increase the TX Power Low column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be increased without affecting the signal, complete the "Physically Replace a Traffic Card" procedure.

---

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

---

---

Note When you replace a card with an identical type of card, you do not need to make any changes to the database.

---

Step 5 If no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a service-affecting problem.

---

2.7.207  LPBKCRS

•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: VCMON-HP

The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between an optical card and an STM-64 card. A cross-connect loopback test occurs below line speed and does not affect traffic.

For more information on loopbacks, see the "1.2  Troubleshooting Electrical Circuit Paths With Loopbacks" section on page 1-9.

---

Note Cross-connect loopbacks occur below line speed. They do not affect traffic.

---

Clear the LPBKCRS Condition

---

Step 1 To remove the loopback cross-connect condition, double-click the optical card in CTC to display the card view.

Step 2 Complete the "Clear an STM-N Card XC Loopback Circuit" procedure.

Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.208  LPBKDS1FEAC

The LPBKDS1FEAC alarm is not used in this platform in this release. It is reserved for future development.

2.7.209  LPBKDS3FEAC

•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: DS3

A Loopback Due to FEAC Command DS-3 condition occurs when a DS3i-N-12 card loopback signal is received from the far-end node because of a FEAC command. An FEAC command is often used with loopbacks. LPBKDS3FEAC is only reported by DS3i-N-12 cards. A DS3i-N-12 card generates and reports FEAC alarms or conditions.

---

Caution CTC permits loopbacks on an unlocked circuit. Loopbacks are service-affecting.

---

---

Note LPBKDS3FEAC is an informational condition. It does not require troubleshooting.

---

Clear the LPBKDS3FEAC Condition

---

Step 1 In node view, double-click the DS3i-N-12 card to display the card view.

Step 2 Click the Maintenance > Loopback tabs.

Step 3 Click the Loopback Type column, cell for the port and click None from the drop-down list.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.210  LPBKDS3FEAC-CMD

•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: DS3

The DS-3 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-3 FEAC loopback to a DS3i-N-12 card. For more information about FEAC loopbacks, see the "1.2  Troubleshooting Electrical Circuit Paths With Loopbacks" section on page 1-9.

---

Note LPBKDS3FEAC-CMD is an informational condition. It does not require troubleshooting.

---

2.7.211  LPBKE1FEAC

The LPBKE1FEAC condition is not used in this platform in this release. It is reserved for future development.

2.7.212  LPBKE3FEAC

The LPBKE3FEAC condition is not used in this platform in this release. It is reserved for future development.

2.7.213  LPBKE3FEAC-CMD

The LPBKE3FEAC-CMD condition is not used in this platform in this release. It is reserved for future development.

2.7.214  LPBKFACILITY (DS3)

•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Object: DS3

A Loopback Facility condition occurs when a software facility (line) loopback is active for a DS3 port on the reporting DS3i-N-12 card.

For information about troubleshooting optical circuits, refer to the "1.2  Troubleshooting Electrical Circuit Paths With Loopbacks" section on page 1-9. Facility loopbacks are described in the "1.1  Troubleshooting Non-DWDM Circuit Paths with Loopbacks" section on page 1-2.

---

Note CTC permits loopbacks to be performed on an unlocked circuit. Performing a loopback is service-affecting. If you did not perform a lockout or Force switch to protect traffic, the LPBKFACILITY condition can be accompanied by a more serious alarms such as LOS.

---

---

Note DS-3 facility (line) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted to the loopback is provided.

---

Clear the LPBKFACILITY (DS3) Condition

---

Step 1 Complete the "Clear a DS3i-N-12 Card Loopback Circuit" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

---

2.7.215  LPBKFACILITY (E1, E3, E4)

•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)

•Logical Objects: E1, E3, E4

A Loopback Facility condition occurs when a software facility loopback is active for a port on the reporting E-N card.

For more information on loopbacks, see the "1.1  Troubleshooting Non-DWDM Circuit Paths with Loopbacks" section on page 1-2 or the "1.2  Troubleshooting Electrical Circuit Paths With Loopbacks" section on page 1-9.

---

Caution CTC permits loopbacks to be performed on an unlocked circuit. Loopbacks are service-affecting.

---

Clear the LPBKFACILITY (E1, E3, E4) Condition

---

Step 1 In node view, double-click the reporting card to display the card view.

Step 2 Complete the "Clear an STM-N Card Facility or Terminal Loopback Circuit" procedure.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into htt