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

2.2.1  Alarm Logical Objects

2.3  Alarm List by Logical Object Type

2.4  Trouble Notifications

2.4.1  Alarm Characteristics

2.4.2  Condition Characteristics

2.4.3  Severities

2.4.4  Alarm Hierarchy

2.4.5  Service Effect

2.4.6  States

2.5  Safety Summary

2.6  Alarm Procedures

2.6.1  AIS

Clear the AIS Condition

2.6.2  AIS-L

2.6.3  ALS

2.6.4  ALS-DISABLED

2.6.5  AMPLI-INIT

2.6.6  APC-CORRECTION-SKIPPED

2.6.7  APC-DISABLED

2.6.8  APC-END

2.6.9  APC-OUT-OF-RANGE

2.6.10  APSB

Clear the APSB Alarm

2.6.11  APSCDFLTK

Clear the APSCDFLTK Alarm

2.6.12  APSC-IMP

Clear the APSC-IMP Alarm

2.6.13  APSCINCON

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

2.6.14  APSCM

Clear the APSCM Alarm

2.6.15  APSCNMIS

Clear the APSCNMIS Alarm

2.6.16  APS-INV-PRIM

2.6.17  APS-PRIM-FAC

2.6.18  APS-PRIM-SEC-MISM

2.6.19  AS-CMD

Clear the AS-CMD Condition

2.6.20  AS-MT

Clear the AS-MT Condition

2.6.21  AS-MT-OOG

Clear the AS-MT-OOG Condition

2.6.22  AU-AIS

Clear the AU-AIS Condition

2.6.23  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.6.24  AUD-LOG-LOW

2.6.25  AU-LOF

Clear the AU-LOF Alarm

2.6.26  AU-LOP

Clear the AU-LOP Alarm

2.6.27  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.6.28  AUTORESET

Clear the AUTORESET Alarm

2.6.29  AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-SNCP Condition

2.6.30  AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.6.31  AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.6.32  AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.6.33  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

2.6.34  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

2.6.35  AWG-DEG

2.6.36  AWG-FAIL

2.6.37  AWG-OVERTEMP

2.6.38  AWG-WARM-UP

2.6.39  BAT-FAIL

Clear the BATFAIL Alarm

2.6.40  BKUPMEMP

Clear the BKUPMEMP Alarm

2.6.41  CARLOSS (CE100T, CE10000)

Clear the CARLOSS (CE100T, CE10000) Alarm

2.6.42  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.6.43  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.6.44  CARLOSS (FC)

2.6.45  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.6.46  CARLOSS (GE)

2.6.47  CARLOSS (ISC)

2.6.48  CARLOSS (LOGFAC)

2.6.49  CARLOSS (ML100T, ML1000, MLFX)

Clear the CARLOSS (ML100T, ML1000, MLFX) Alarm

2.6.50  CARLOSS (TRUNK)

2.6.51  CASETEMP-DEG

2.6.52  CLDRESTART

Clear the CLDRESTART Condition

2.6.53  COMIOXC

Clear the COMIOXC Alarm

2.6.54  COMM-FAIL

Clear the COMM-FAIL Alarm

2.6.55  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.6.56  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.6.57  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.6.58  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.6.59  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.6.60  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.6.61  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.6.62  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.6.63  DATAFLT

Clear the DATAFLT Alarm

2.6.64  DBOSYNC

Clear the DBOSYNC Alarm

2.6.65  DISCONNECTED

Clear the DISCONNECTED Alarm

2.6.66  DS3-MISM

Clear the DS3-MISM Condition

2.6.67  DSP-COMM-FAIL

2.6.68  DSP-FAIL

2.6.69  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.6.70  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.6.71  DUP-SHELF-ID

2.6.72  EHIBATVG

Clear the EHIBATVG Alarm

2.6.73  ELWBATVG

Clear the ELWBATVG Alarm

2.6.74  EOC-L

2.6.75  EQPT

Clear the EQPT Alarm

2.6.76  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.6.77  EQPT-MISS

Clear the EQPT-MISS Alarm

2.6.78  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.6.79  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.6.80  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.6.81  EXCCOL

Clear the EXCCOL Alarm

2.6.82  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.6.83  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.6.84  EXT

Clear the EXT Alarm

2.6.85  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.6.86  FAILTOSW

Clear the FAILTOSW Condition

2.6.87  FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.6.88  FAILTOSW-LO

Clear the FAILTOSW-LO Condition

2.6.89  FAILTOSWR

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

2.6.90  FAILTOSWS

Clear the FAILTOSWS Condition

2.6.91  FAN

Clear the FAN Alarm

2.6.92  FFC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.6.93  FDI

2.6.94  FE-AIS

Clear the FE-AIS Condition

2.6.95  FEC-MISM

2.6.96  FE-E1-MULTLOS

Clear the FE-E1-MULTLOS Condition

2.6.97  FE-E1-NSA

Clear the FE-E1-NSA Condition

2.6.98  FE-E1-SA

Clear the FE-E1-SA Condition

2.6.99  FE-E1-SNGLLOS

Clear the FE-E1-SNGLLOS Condition

2.6.100  FE-E3-NSA

Clear the FE-E3-NSA Condition

2.6.101  FE-E3-SA

Clear the FE-E3-SA Condition

2.6.102  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.6.103  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.6.104  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.6.105  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.6.106  FE-IDLE

2.6.107  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.6.108  FE-LOF

Clear the FE-LOF Condition

2.6.109  FE-LOS

Clear the FE-LOS Condition

2.6.110  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.6.111  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.6.112  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.6.113  FEPRLF

Clear the FEPRLF Alarm on an MS-SPRing

2.6.114  FIBERTEMP-DEG

2.6.115  FORCED-REQ

Clear the FORCED-REQ Condition

2.6.116  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.6.117  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.6.118  FRCDSWTOINT

2.6.119  FRCDSWTOPRI

2.6.120  FRCDSWTOSEC

2.6.121  FRCDSWTOTHIRD

2.6.122  FRNGSYNC

Clear the FRNGSYNC Condition

2.6.123  FSTSYNC

2.6.124  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.6.125  GAIN-HDEG

2.6.126  GAIN-HFAIL

2.6.127  GAIN-LDEG

2.6.128  GAIN-LFAIL

2.6.129  GCC-EOC

2.6.130  GE-OOSYNC

2.6.131  GFP-CSF

Clear the GFP-CSF Alarm

2.6.132  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.6.133  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.6.134  GFP-LFD

Clear the GFP-LFD Alarm

2.6.135  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.6.136  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.6.137  HELLO

Clear the HELLO Alarm

2.6.138  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.6.139  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.6.140  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.6.141  HITEMP

Clear the HITEMP Alarm

2.6.142  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.6.143  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.6.144  HP-ENCAP-MISMATCH

Clear the HP-ENCAP-MISMATCH Alarm

2.6.145  HP-RFI

Clear the HP-RFI Condition

2.6.146  HP-SQUELCH-L

2.6.147  HP-TIM

Clear the HP-TIM Alarm

2.6.148  HP-UNEQ

Clear the HP-UNEQ Alarm

2.6.149  I-HITEMP

Clear the I-HITEMP Alarm

2.6.150  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.6.151  INC-ISD

2.6.152  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.6.153  INHSWPR

Clear the INHSWPR Condition

2.6.154  INHSWWKG

Clear the INHSWWKG Condition

2.6.155  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.6.156  INVMACADR

2.6.157  IOSCFGCOPY

2.6.158  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.6.159  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.6.160  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.6.161  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.6.162  LASER-APR

2.6.163  LASERBIAS-DEG

2.6.164  LASERBIAS-FAIL

2.6.165  LASERTEMP-DEG

2.6.166  LCAS-CRC

Clear the LCAS-CRC Condition

2.6.167  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.6.168  LCAS-TX-ADD

2.6.169  LCAS-TX-DNU

2.6.170  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.6.171  LOA

Clear the LOA Alarm

2.6.172  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.6.173  LOF (BITS)

Clear the LOF (BITS) Alarm

2.6.174  LOF (DS1, DS3, E1, E4, STM1E, STMN)

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

2.6.175  LOF (TRUNK)

2.6.176  LOGBUFR90

2.6.177  LOGBUFROVFL

Clear the LOGBUFROVFL Alarm

2.6.178  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.6.179  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.6.180  LOM

Clear the LOM Alarm

2.6.181  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.6.182  LOS (2R)

2.6.183  LOS (BITS)

Clear the LOS (BITS) Alarm

2.6.184  LOS (DS1, DS3)

Clear the LOS (DS1, DS3) Alarm

2.6.185  LOS (E1, E3, E4)

Clear the LOS (E1, E3, E4) Alarm

2.6.186  LOS (ESCON)

2.6.187  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.6.188  LOS (ISC)

2.6.189  LOS (MSUDC)

2.6.190  LOS (OTS)

2.6.191  LOS (STM1E, STMN)

Clear the LOS (STM1E, STMN) Alarm

2.6.192  LOS (TRUNK)

2.6.193  LOS-O

2.6.194  LOS-P (OCH)

2.6.195  LOS-P (OMS, OTS)

2.6.196  LOS-P (TRUNK)

2.6.197  LO-TXPOWER

2.6.198  LPBKCRS

Clear the LPBKCRS Condition

2.6.199  LPBKDS1FEAC-CMD

2.6.200  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.6.201  LPBKDS3FEAC-CMD

2.6.202  LPBKE1FEAC

2.6.203  LPBKE3FEAC

2.6.204  LPBKFACILITY (CE100T, CE1000)

Clear the LPBKFACILITY (CE100T, CE1000) Condition

2.6.205  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.6.206  LPBKFACILITY (E1, E3, E4)

Clear the LPBKFACILITY (E1, E3, E4) Condition

2.6.207  LPBKFACILITY (ESCON)

2.6.208  LPBKFACILITY (FC)

2.6.209  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.6.210  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.6.211  LPBKFACILITY (GE)

2.6.212  LPBKFACILITY (ISC)

2.6.213  LPBKFACILITY (STM1E, STMN)

Clear the LPBKFACILITY (STM1E, STMN) Condition

2.6.214  LPBKFACILITY (TRUNK)

2.6.215  LPBKTERMINAL (CE100T, CE1000)

Clear the LPBKTERMINAL (CE100T, CE1000) Condition

2.6.216  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS3) Condition

2.6.217  LPBKTERMINAL (E1, E3, E4)

Clear the LPBKTERMINAL (E1, E3, E4) Condition

2.6.218  LPBKTERMINAL (ESCON)

2.6.219  LPBKTERMINAL (FC)

2.6.220  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.6.221  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.6.222  LPBKTERMINAL (GE)

2.6.223  LPBKTERMINAL (ISC)

2.6.224  LPBKTERMINAL (STM1E, STMN)

Clear the LPBKTERMINAL (STM1E, STMN) Condition

2.6.225  LPBKTERMINAL (TRUNK)

2.6.226  LP-ENCAP-MISMATCH

Clear the LP-ENCAP-MISMATCH Alarm

2.6.227  LP-PLM

Clear the LP-PLM Alarm

2.6.228  LP-RFI

Clear the LP-RFI Condition

2.6.229  LP-TIM

Clear the LP-TIM Alarm

2.6.230  LP-UNEQ

Clear the LP-UNEQ Alarm

2.6.231  MAN-REQ

Clear the MAN-REQ Condition

2.6.232  MANRESET

2.6.233  MANSWTOINT

2.6.234  MANSWTOPRI

2.6.235  MANSWTOSEC

2.6.236  MANSWTOTHIRD

2.6.237  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.6.238  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.6.239  MEA (BIC)

2.6.240  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.6.241  MEA (FAN)

Clear the MEA (FAN) Alarm

2.6.242  MEA (PPM)

2.6.243  MEM-GONE

2.6.244  MEM-LOW

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

Clear the MFGMEM Alarm

2.6.246  MFGMEM (BPLANE, FAN)

Clear the MFGMEM (BPLANE, FAN) Alarm

2.6.247  MS-AIS

Clear the MS-AIS Condition

2.6.248  MS-EOC

Clear the MS-EOC Alarm

2.6.249  MS-RFI

Clear the MS-RFI Condition

2.6.250  MSSP-OOSYNC

Clear the MSSP-OOSYNC Alarm

2.6.251  MSSP-SW-VER-MISM

Clear the MSSP-SW-VER-MISM Alarm

2.6.252  MS-SQUELCH-HP

2.6.253  MS-SQUELCH-LP

2.6.254  NO-CONFIG

Clear the NO-CONFIG Alarm

2.6.255  NOT-AUTHENTICATED

2.6.256  OCHNC-INC

2.6.257  OCH-TERM-INC

2.6.258  ODUK-1-AIS-PM

2.6.259  ODUK-2-AIS-PM

2.6.260  ODUK-3-AIS-PM

2.6.261  ODUK-4-AIS-PM

2.6.262  ODUK-AIS-PM

2.6.263  ODUK-BDI-PM

2.6.264  ODUK-LCK-PM

2.6.265  ODUK-OCI-PM

2.6.266  ODUK-SD-PM

2.6.267  ODUK-SF-PM

2.6.268  ODUK-TIM-PM

2.6.269  OOU-TPT

Clear the OOT-TPT Condition

2.6.270  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.6.271  OPWR-HDEG

2.6.272  OPWR-HFAIL

2.6.273  OPWR-LDEG

2.6.274  OPWR-LFAIL

2.6.275  OSRION

2.6.276  OTUK-AIS

2.6.277  OTUK-BDI

2.6.278  OTUK-IAE

2.6.279  OTUK-LOF

2.6.280  OTUK-SD

2.6.281  OTUK-SF

2.6.282  OTUK-TIM

2.6.283  OUT-OF-SYNC

2.6.284  PARAM-MISM

2.6.285  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.6.286  PMI

2.6.287  PORT-ADD-PWR-DEG-HI

2.6.288  PORT-ADD-PWR-DEG-LOW

2.6.289  PORT-ADD-PWR-FAIL-HI

2.6.290  PORT-ADD-PWR-FAIL-LOW

2.6.291  PORT-FAIL

2.6.292  PORT-MISMATCH

Clear the PORT-MISMATCH Alarm

2.6.293  PRC-DUPID

Clear the PRC-DUPID Alarm

2.6.294  PROTNA

Clear the PROTNA Alarm

2.6.295  PROV-MISMATCH

2.6.296  PTIM

2.6.297  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.6.298  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.6.299  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.6.300  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.6.301  RAI

Clear the RAI Condition

2.6.302  RCVR-MISS

Clear the RCVR-MISS Alarm

2.6.303  RFI

2.6.304  RFI-L

2.6.305  RFI-V

2.6.306  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.6.307  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.6.308  RING-SW-EAST

2.6.309  RING-SW-WEST

2.6.310  ROLL

2.6.311  ROLL-PEND

2.6.312  RPRW

Clear the RPRW Condition

2.6.313  RS-EOC

Clear the RS-EOC Alarm

2.6.314  RS-TIM

Clear the RS-TIM Alarm

2.6.315  RUNCFG-SAVENEED

2.6.316  SD (DS1, DS3, E1, E3, E4, STM1E, STMN)

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

2.6.317  SD (TRUNK)

2.6.318  SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.6.319  SDBER-EXCEED-LO

Clear the SDBER-EXCEED-LO Condition

2.6.320  SD-L

2.6.321  SF (DS1, DS3, E1, E3, E4, STMN)

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

2.6.322  SF (TRUNK)

2.6.323  SFBER-EXCEED-HO

Clear the SFBER-EXCEED-HO Condition

2.6.324  SFBER-EXCEED-LO

Clear the SFBER-EXCEED-HO Condition

2.6.325  SF-L

2.6.326  SFTWDOWN

2.6.327  SHELF-COMM-FAIL

2.6.328  SH-INS-LOSS-VAR-DEG-HIGH

2.6.329  SH-INS-LOSS-VAR-DEG-LOW

2.6.330  SHUTTER-OPEN

2.6.331  SIGLOSS

Clear the SIGLOSS Alarm

2.6.332  SNTP-HOST

Clear the SNTP-HOST Alarm

2.6.333  SPAN-LENGTH-OUT-OF-RANGE

2.6.334  SPAN-SW-EAST

2.6.335  SPAN-SW-WEST

2.6.336  SQUELCH

Clear the SQUELCH Condition

2.6.337  SQUELCHED

Clear the SQUELCHED Condition

2.6.338  SQM

Clear the SQM Alarm

2.6.339  SSM-DUS

2.6.340  SSM-FAIL

Clear the SSM-FAIL Alarm

2.6.341  SSM-LNC

2.6.342  SSM-OFF

2.6.343  SSM-PRC

2.6.344  SSM-PRS

2.6.345  SSM-RES

2.6.346  SSM-SDH-TN

2.6.347  SSM-SETS

2.6.348  SSM-SMC

2.6.349  SSM-ST2

2.6.350  SSM-ST3

2.6.351  SSM-ST3E

2.6.352  SSM-ST4

2.6.353  SSM-STU

Clear the SSM-STU Condition

2.6.354  SSM-TNC

2.6.355  SW-MISMATCH

2.6.356  SWMTXMOD-PROT

Clear the SWMTXMOD-PROT Alarm

2.6.357  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.6.358  SWTOPRI

2.6.359  SWTOSEC

2.6.360  SWTOTHIRD

2.6.361  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.6.362  SYNCLOSS

Clear the SYNCLOSS Alarm

2.6.363  SYNCPRI

Clear the SYNCPRI Alarm

2.6.364  SYNCSEC

Clear the SYNCSEC Alarm

2.6.365  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.6.366  SYSBOOT

2.6.367  TEMP-MISM

Clear the TEMP-MISM Condition

2.6.368  TIM

Clear the TIM Alarm

2.6.369  TIM-MON

Clear the TIM-MON Alarm

2.6.370  TPTFAIL (CE100T, 1000)

Clear the TPTFAIL (CE100T, CE1000) Alarm

2.6.371  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.6.372  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.6.373  TPTFAIL (LOGFAC)

2.6.374  TPTFAIL (ML100T, ML1000, MLFX)

Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm

2.6.375  TRMT

Clear the TRMT Alarm

2.6.376  TRMT-MISS

Clear the TRMT-MISS Alarm

2.6.377  TU-AIS

Clear the TU-AIS Condition

2.6.378  TU-LOP

Clear the TU-LOP Alarm

2.6.379  TX-AIS

Clear the TX-AIS Condition

2.6.380  TX-LOF

Clear the TX-LOF Condition

2.6.381  TX-RAI

Clear the TX-RAI Condition

2.6.382  UNC-WORD

2.6.383  UNREACHABLE-TARGET-POWER

2.6.384  UT-COMM-FAIL

2.6.385  UT-FAIL

2.6.386  VCG-DEG

Clear the VCG-DEG Condition

2.6.387  VCG-DOWN

Clear the VCG-DOWN Condition

2.6.388  VOA-HDEG

2.6.389  VOA-HFAIL

2.6.390  VOA-LDEG

2.6.391  VOA-LFAIL

2.6.392  VOLT-MISM

Clear the VOLT-MISM Condition

2.6.393  WKSWPR

Clear the WKSWPR Condition

2.6.394  WTR

2.6.395  WVL-MISMATCH

2.7  Traffic Card LED Activity

2.7.1  Typical Traffic Card LED Activity After Insertion

2.7.2  Typical Traffic Card LED Activity During Reset

2.7.3  Typical Card LED State After Successful Reset

2.7.4  Typical Cross-Connect LED Activity During Side Switch

2.8  Frequently Used Alarm Troubleshooting Procedures

2.8.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.8.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 an MS-SPRing External Switching Command

2.8.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card

Reset the Standby TCC2/TCC2P Card

Side Switch the Active and Standby Cross-Connect Cards

2.8.4  Physical Card Reseating, Resetting, and Replacement

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

Remove and Reinsert (Reseat) Any Card

Physically Replace a Traffic Card

Physically Replace an In-Service Cross-Connect Card

2.8.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node RS-DCC Terminations

Clear an STM-N Card Facility or Terminal Loopback Circuit

Clear an STM-N Card XC Loopback Circuit

Clear a Non-STM Card Facility or Terminal Loopback Circuit

2.8.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly

Alarm Troubleshooting

---

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. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 SDH TL1 Reference Guide. For instructions on using Transaction Language One (TL1) commands, refer to the Cisco ONS 15454 SDH TL1 Command Guide.

An alarm's troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm log into the Technical Support Website at http://www.cisco.com/techsupport for more information or 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 "Manage Alarms" chapter of the Cisco ONS 15454 SDH Procedure Guide.

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.

---

2.1.1  Critical Alarms (CR)

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

Table 2-1 ONS 15454 SDH Critical Alarm List 

AU-LOF (VCTRM-HP)	IMPROPRMVL (EQPT)	MFGMEM (BPLANE)
AU-LOP (VCMON-HP)	IMPROPRMVL (PPM)	MFGMEM (FAN)
AU-LOP (VCTRM-HP)	LOA (VCG)	MFGMEM (PPM)
AUTOLSROFF (STMN)	LOF (DS3)	OPWR-HFAIL (AOTS)
AUTOLSROFF (TRUNK)	LOF (E4)	OPWR-HFAIL (OCH)
AWG-FAIL (OTS)	LOF (STM1E)	OPWR-HFAIL (OMS)
AWG-OVERTEMP (OTS)	LOF (STMN)	OPWR-HFAIL (OTS)
BKUPMEMP (EQPT)	LOF (TRUNK)	OPWR-LFAIL (AOTS)
COMIOXC (EQPT)	LOM (TRUNK)	OPWR-LFAIL (OCH)
CONTBUS-DISABLED (EQPT)	LOM (VCMON-HP)	OPWR-LFAIL (OMS)
CTNEQPT-PBPROT (EQPT)	LOS (DS3)	OPWR-LFAIL (OTS)
CTNEQPT-PBWORK (EQPT)	LOS (E3)	OTUK-LOF (TRUNK)
EQPT (AICI-AEP)	LOS (E4)	OTUK-TIM (TRUNK)
EQPT (AICI-AIE)	LOS (ESCON)	PORT-ADD-PWR-FAIL-HIGH (OCH)
EQPT (EQPT)	LOS (ISC)	PORT-ADD-PWR-FAIL-LOW (OCH)
EQPT (PPM)	LOS (OTS)	PORT-FAIL (OCH)
EQPT-MISS (FAN)	LOS (STM1E)	RS-TIM (STMN)
FAN (FAN)	LOS (STMN)	SQM (VCTRM-HP)
GAIN-HFAIL (AOTS)	LOS (TRUNK)	SWMTXMOD-PROT (EQPT)
GAIN-LFAIL (AOTS)	LOS-P (OCH)	SWMTXMOD-WORK (EQPT)
GE-OOSYNC (FC)	LOS-P (OMS)	TIM (STMN)
GE-OOSYNC (GE)	LOS-P (OTS)	TIM (TRUNK)
GE-OOSYNC (ISC)	LOS-P (TRUNK)	VOA-HFAIL (AOTS)
GE-OOSYNC (TRUNK)	LP-ENCAP-MISMATCH (VCTRM-LP)	VOA-HFAIL (OCH)
HITEMP (NE)	MEA (BIC)	VOA-HFAIL (OMS)
HP-ENCAP-MISMATCH (VCTRM-HP)	MEA (EQPT)	VOA-HFAIL (OTS)
HP-TIM (VCTRM-HP)	MEA (FAN)	VOA-LFAIL (AOTS)
HP-UNEQ (VCMON-HP)	MEA (PPM)	VOA-LFAIL (OCH)
HP-UNEQ (VCTRM-HP)	MFGMEM (AICI-AEP)	VOA-LFAIL (OMS)
I-HITEMP (NE)	MFGMEM (AICI-AIE)	VOA-LFAIL (OTS)

2.1.2  Major Alarms (MJ)

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

Table 2-2 ONS 15454 SDH Major Alarm List 

APSCM (STMN)	GFP-EX-MISMATCH (GFP-FAC)	PRC-DUPID (STMN)
APSCNMIS (STMN)	GFP-LFD (CE100T)	PTIM (TRUNK)
BAT-FAIL (PWR)	GFP-LFD (FCMR)	RCVR-MISS (DS1)
CARLOSS (CE100T)	GFP-LFD (GFP-FAC)	RCVR-MISS (E1)
CARLOSS (E1000F)	GFP-LFD (LOGFAC)	RING-ID-MIS (OSC-RING)
CARLOSS (E100T)	GFP-LFD (ML1000)	RING-ID-MIS (STMN)
CARLOSS (EQPT)	GFP-LFD (ML100T)	RING-MISMATCH (STMN)
CARLOSS (FC)	GFP-LFD (MLFX)	SIGLOSS (FC)
CARLOSS (G1000)	GFP-NO-BUFFERS (FCMR)	SIGLOSS (FCMR)
CARLOSS (GE)	GFP-NO-BUFFERS (GFP-FAC)	SIGLOSS (GE)
CARLOSS (ISC)	GFP-UP-MISMATCH (CE100T)	SIGLOSS (ISC)
CARLOSS (LOGFAC)	GFP-UP-MISMATCH (FCMR)	SIGLOSS (TRUNK)
CARLOSS (ML1000)	GFP-UP-MISMATCH (GFP-FAC)	SQM (VCTRM-LP)
CARLOSS (ML100T)	GFP-UP-MISMATCH (LOGFAC)	SYNCLOSS (FC)
CARLOSS (MLFX)	GFP-UP-MISMATCH (ML1000)	SYNCLOSS (FCMR)
CARLOSS (TRUNK)	GFP-UP-MISMATCH (ML100T)	SYNCLOSS (GE)
DBOSYNC (NE)	GFP-UP-MISMATCH (MLFX)	SYNCLOSS (ISC)
DSP-COMM-FAIL (TRUNK)	INVMACADR (BPLANE)	SYNCLOSS (TRUNK)
DSP-FAIL (TRUNK)	LASERBIAS-FAIL (AOTS)	SYNCPRI (NE-SREF)
EHIBATVG (PWR)	LOF (DS1)	SYSBOOT (NE)
ELWBATVG (PWR)	LOF (E1)	TIM (STM1E)
E-W-MISMATCH (STMN)	LOM (VCTRM-HP)	TPTFAIL (CE100T)
EXTRA-TRAF-PREEMPT (STMN)	LOS (DS1)	TPTFAIL (FCMR)
FC-NO-CREDITS (FC)	LOS (E1)	TPTFAIL (G1000)
FC-NO-CREDITS (FCMR)	LP-PLM (VCTRM-LP)	TPTFAIL (LOGFAC)
FC-NO-CREDITS (TRUNK)	LP-TIM (VCTRM-LP)	TPTFAIL (ML1000)
FEC-MISM (TRUNK)	LP-UNEQ (VCMON-LP)	TPTFAIL (ML100T)
GFP-CSF (CE100T)	LP-UNEQ (VCTRM-LP)	TPTFAIL (MLFX)
GFP-CSF (FCMR)	MEM-GONE (EQPT)	TRMT (DS1)
GFP-CSF (GFP-FAC)	MSSP-OOSYNC (STMN)	TRMT (E1)
GFP-CSF (LOGFAC)	MSSP-SW-VER-MISM (STMN)	TRMT-MISS (DS1)
GFP-CSF (ML1000)	ODUK-TIM-PM (TRUNK)	TRMT-MISS (E1)
GFP-CSF (ML100T)	OPTNTWMIS (NE)	TU-LOP (VCMON-LP)
GFP-CSF (MLFX)	OUT-OF-SYNC (FC)	TU-LOP (VCTRM-LP)
GFP-DE-MISMATCH (FCMR)	OUT-OF-SYNC (GE)	UT-COMM-FAIL (TRUNK)
GFP-DE-MISMATCH (GFP-FAC)	OUT-OF-SYNC (TRUNK)	UT-FAIL (TRUNK)
GFP-EX-MISMATCH (FCMR)	PEER-NORESPONSE (EQPT)	WVL-MISMATCH (TRUNK)

2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15454 SDH Minor Alarm List 

APSB (STMN)	HITEMP (EQPT)	MEM-LOW (EQPT)
APSCDFLTK (STMN)	HI-TXPOWER (EQPT)	MS-EOC (STMN)
APSC-IMP (STMN)	HI-TXPOWER (ESCON)	NOT-AUTHENTICATED (SYSTEM)
APSCINCON (STMN)	HI-TXPOWER (FC)	OPWR-HDEG (OCH)
APS-INV-PRIM (STMN)	HI-TXPOWER (GE)	OPWR-HDEG (OMS)
APS-PRIM-SEC-MISM (STMN)	HI-TXPOWER (ISC)	OPWR-HDEG (OTS)
AUTORESET (EQPT)	HI-TXPOWER (PPM)	OPWR-LDEG (AOTS)
AUTOSW-UNEQ-SNCP (VCMON-LP)	HI-TXPOWER (STMN)	OPWR-LDEG (OCH)
AWG-DEG (OTS)	HI-TXPOWER (TRUNK)	OPWR-LDEG (OMS)
CASETEMP-DEG (AOTS)	HP-TIM (VCMON-HP)	OPWR-LDEG (OTS)
COMM-FAIL (EQPT)	INCOMPATIBLE-SW (SYSTEM)	OTUK-IAE (TRUNK)
CONTBUS-A-18 (EQPT)	ISIS-ADJ-FAIL (STMN)	PORT-ADD-PWR-DEG-HI (OCH)
CONTBUS-B-18 (EQPT)	KBYTE-APS-CHANNEL-FAILURE (STMN)	PORT-ADD-PWR-DEG-LOW (OCH)
CONTBUS-IO-A (EQPT)	LASERBIAS-DEG (AOTS)	PROTNA (EQPT)
CONTBUS-IO-B (EQPT)	LASERBIAS-DEG (OTS)	PROV-MISMATCH (PPM)
DATAFLT (NE)	LASERTEMP-DEG (AOTS)	PWR-FAIL-A (EQPT)
DISCONNECTED (SYSTEM)	LOF (BITS)	PWR-FAIL-B (EQPT)
DUP-IPADDR (NE)	LOGBUFR90 (SYSTEM)	PWR-FAIL-RET-A (EQPT)
DUP-NODENAME (NE)	LOGBUFROVFL (SYSTEM)	PWR-FAIL-RET-B (EQPT)
EOC-L (TRUNK)	LO-LASERBIAS (EQPT)	RS-EOC (STMN)
ERROR-CONFIG (EQPT)	LO-LASERBIAS (PPM)	RS-EOC (TRUNK)
EXCCOL (EQPT)	LO-LASERBIAS (STMN)	SFTWDOWN (EQPT)
EXT (ENVALRM)	LO-LASERTEMP (EQPT)	SH-INS-LOSS-VAR-DEG-HIGH (OTS)
FEPRLF (STMN)	LO-LASERTEMP (PPM)	SH-INS-LOSS-VAR-DEG-LOW (OTS)
FIBERTEMP-DEG (AOTS)	LO-LASERTEMP (STMN)	SNTP-HOST (NE)
GAIN-HDEG (AOTS)	LOM (VCTRM-LP)	SSM-FAIL (BITS)
GAIN-LDEG (AOTS)	LO-RXPOWER (ESCON)	SSM-FAIL (E1)
GCC-EOC (TRUNK)	LO-RXPOWER (FC)	SSM-FAIL (TRUNK)
HELLO (STMN)	LO-RXPOWER (GE)	SYNCPRI (EXT-SREF)
HI-LASERBIAS (EQPT)	LO-RXPOWER (ISC)	SYNCSEC (EXT-SREF)
HI-LASERBIAS (ESCON)	LO-RXPOWER (STMN)	SYNCSEC (NE-SREF)
HI-LASERBIAS (FC)	LO-RXPOWER (TRUNK)	SYNCTHIRD (EXT-SREF)
HI-LASERBIAS (GE)	LOS (BITS)	SYNCTHIRD (NE-SREF)
HI-LASERBIAS (ISC)	LOS (FUDC)	TIM-MON (STMN)
HI-LASERBIAS (PPM)	LOS (MSUDC)	TIM-MON (TRUNK)
HI-LASERBIAS (STMN)	LOS-O (OCH)	UNREACHABLE-TARGET-POWER (OCH)
HI-LASERBIAS (TRUNK)	LOS-O (OMS)	VOA-HDEG (AOTS)
HI-LASERTEMP (EQPT)	LOS-O (OTS)	VOA-HDEG (OCH)
HI-LASERTEMP (PPM)	LO-TXPOWER (EQPT)	VOA-HDEG (OMS)
HI-LASERTEMP (STMN)	LO-TXPOWER (ESCON)	VOA-HDEG (OTS)
HI-RXPOWER (ESCON)	LO-TXPOWER (FC)	VOA-LDEG (AOTS)
HI-RXPOWER (FC)	LO-TXPOWER (GE)	VOA-LDEG (OCH)
HI-RXPOWER (GE)	LO-TXPOWER (ISC)	VOA-LDEG (OMS)
HI-RXPOWER (ISC)	LO-TXPOWER (PPM)	VOA-LDEG (OTS)
HI-RXPOWER (STMN)	LO-TXPOWER (STMN)	OPWR-HDEG (AOTS)
HI-RXPOWER (TRUNK)	LO-TXPOWER (TRUNK)	—

2.1.4  Not Alarmed Conditions (NA)

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

Table 2-4 ONS 15454 SDH Not Alarmed Conditions List 

ALS (AOTS)	FORCED-REQ-RING (STMN)	RING-SW-WEST (STMN)
ALS (ESCON)	FORCED-REQ-SPAN (ESCON)	ROLL (VCMON-HP)
ALS (FC)	FORCED-REQ-SPAN (FC)	ROLL (VCMON-LP)
ALS (GE)	FORCED-REQ-SPAN (GE)	ROLL (VCTRM-HP)
ALS (ISC)	FORCED-REQ-SPAN (ISC)	ROLL-PEND (VCMON-HP)
ALS (TRUNK)	FORCED-REQ-SPAN (STMN)	ROLL-PEND (VCMON-LP)
ALS-DISABLED (EQPT)	FORCED-REQ-SPAN (TRUNK)	RPRW (LOGFAC)
AMPLI-INIT (AOTS)	FRCDSWTOINT (NE-SREF)	RPRW (ML1000)
APC-CORRECTION-SKIPPED (AOTS)	FRCDSWTOPRI (EXT-SREF)	RPRW (ML100T)
APC-CORRECTION-SKIPPED (OCH)	FRCDSWTOPRI (NE-SREF)	RPRW (MLFX)
APC-CORRECTION-SKIPPED (OMS)	FRCDSWTOSEC (EXT-SREF)	RUNCFG-SAVENEED (EQPT)
APC-CORRECTION-SKIPPED (OTS)	FRCDSWTOSEC (NE-SREF)	SD (DS1)
APC-DISABLED (NE)	FRCDSWTOTHIRD (EXT-SREF)	SD (DS3)
APC-END (NE)	FRCDSWTOTHIRD (NE-SREF)	SD (E1)
APC-OUT-OF-RANGE (AOTS)	FRNGSYNC (NE-SREF)	SD (E3)
APC-OUT-OF-RANGE (OCH)	FSTSYNC (NE-SREF)	SD (E4)
APC-OUT-OF-RANGE (OMS)	FULLPASSTHR-BI (STMN)	SD (STM1E)
APC-OUT-OF-RANGE (OTS)	HELLO (TRUNK)	SD (STMN)
APS-PRIM-FAC (STMN)	HLDOVRSYNC (NE-SREF)	SD (TRUNK)
AS-CMD (AOTS)	INC-ISD (DS3)	SDBER-EXCEED-HO (VCMON-HP)
AS-CMD (BPLANE)	INC-ISD (E3)	SDBER-EXCEED-HO (VCTRM-HP)
AS-CMD (CE100T)	INHSWPR (EQPT)	SDBER-EXCEED-LO (VCMON-LP)
AS-CMD (DS1)	INHSWWKG (EQPT)	SDBER-EXCEED-LO (VCTRM-LP)
AS-CMD (DS3)	INTRUSION-PSWD (NE)	SD-L (STM1E)
AS-CMD (E1)	IOSCFGCOPY (EQPT)	SF (DS1)
AS-CMD (E1000F)	KB-PASSTHR (STMN)	SF (DS3)
AS-CMD (E100T)	LAN-POL-REV (NE)	SF (E1)
AS-CMD (E3)	LASER-APR (AOTS)	SF (E3)
AS-CMD (E4)	LCAS-CRC (VCTRM-HP)	SF (E4)
AS-CMD (EQPT)	LCAS-CRC (VCTRM-LP)	SF (STMN)
AS-CMD (ESCON)	LCAS-RX-FAIL (VCTRM-HP)	SF (TRUNK)
AS-CMD (FC)	LCAS-RX-FAIL (VCTRM-LP)	SFBER-EXCEED-HO (VCMON-HP)
AS-CMD (FCMR)	LCAS-TX-ADD (VCTRM-HP)	SFBER-EXCEED-HO (VCTRM-HP)
AS-CMD (G1000)	LCAS-TX-ADD (VCTRM-LP)	SFBER-EXCEED-LO (VCMON-LP)
AS-CMD (GE)	LCAS-TX-DNU (VCTRM-HP)	SFBER-EXCEED-LO (VCTRM-LP)
AS-CMD (GFP-FAC)	LCAS-TX-DNU (VCTRM-LP)	SF-L (STM1E)
AS-CMD (ISC)	LKOUTPR-S (STMN)	SHUTTER-OPEN (OTS)
AS-CMD (LOGFAC)	LOCKOUT-REQ (EQPT)	SPAN-SW-EAST (STMN)
AS-CMD (ML1000)	LOCKOUT-REQ (ESCON)	SPAN-SW-WEST (STMN)
AS-CMD (ML100T)	LOCKOUT-REQ (FC)	SQUELCH (STMN)
AS-CMD (MLFX)	LOCKOUT-REQ (GE)	SQUELCHED (ESCON)
AS-CMD (NE)	LOCKOUT-REQ (ISC)	SQUELCHED (FC)
AS-CMD (OCH)	LOCKOUT-REQ (STMN)	SQUELCHED (GE)
AS-CMD (OMS)	LOCKOUT-REQ (TRUNK)	SQUELCHED (ISC)
AS-CMD (OTS)	LOCKOUT-REQ (VCMON-HP)	SQUELCHED (STMN)
AS-CMD (PPM)	LOCKOUT-REQ (VCMON-LP)	SQUELCHED (TRUNK)
AS-CMD (PWR)	LPBKCRS (VCMON-HP)	SSM-DUS (BITS)
AS-CMD (STM1E)	LPBKCRS (VCTRM-HP)	SSM-DUS (E1)
AS-CMD (STMN)	LPBKDS1FEAC-CMD (DS1)	SSM-DUS (STMN)
AS-CMD (TRUNK)	LPBKDS3FEAC (DS3)	SSM-LNC (BITS)
AS-MT (AOTS)	LPBKDS3FEAC-CMD (DS3)	SSM-LNC (NE-SREF)
AS-MT (CE100T)	LPBKDS3FEAC-CMD (E3)	SSM-LNC (STMN)
AS-MT (DS1)	LPBKE1FEAC (E3)	SSM-LNC (TRUNK)
AS-MT (DS3)	LPBKE3FEAC (E3)	SSM-OFF (BITS)
AS-MT (E1)	LPBKFACILITY (CE100T)	SSM-OFF (E1)
AS-MT (E3)	LPBKFACILITY (DS1)	SSM-OFF (TRUNK)
AS-MT (E4)	LPBKFACILITY (DS3)	SSM-PRC (BITS)
AS-MT (EQPT)	LPBKFACILITY (E1)	SSM-PRC (NE-SREF)
AS-MT (ESCON)	LPBKFACILITY (E3)	SSM-PRC (STMN)
AS-MT (FC)	LPBKFACILITY (E4)	SSM-PRC (TRUNK)
AS-MT (FCMR)	LPBKFACILITY (ESCON)	SSM-PRS (E1)
AS-MT (G1000)	LPBKFACILITY (FC)	SSM-PRS (TRUNK)
AS-MT (GE)	LPBKFACILITY (FCMR)	SSM-RES (E1)
AS-MT (GFP-FAC)	LPBKFACILITY (G1000)	SSM-RES (TRUNK)
AS-MT (ISC)	LPBKFACILITY (GE)	SSM-SDH-TN (BITS)
AS-MT (LOGFAC)	LPBKFACILITY (ISC)	SSM-SDH-TN (NE-SREF)
AS-MT (ML1000)	LPBKFACILITY (STM1E)	SSM-SDH-TN (TRUNK)
AS-MT (ML100T)	LPBKFACILITY (STMN)	SSM-SETS (BITS)
AS-MT (MLFX)	LPBKFACILITY (TRUNK)	SSM-SETS (NE-SREF)
AS-MT (OCH)	LPBKTERMINAL (CE100T)	SSM-SETS (STMN)
AS-MT (OMS)	LPBKTERMINAL (DS1)	SSM-SETS (TRUNK)
AS-MT (OTS)	LPBKTERMINAL (DS3)	SSM-SMC (E1)
AS-MT (PPM)	LPBKTERMINAL (E1)	SSM-SMC (TRUNK)
AS-MT (STM1E)	LPBKTERMINAL (E3)	SSM-ST2 (E1)
AS-MT (STMN)	LPBKTERMINAL (E4)	SSM-ST2 (TRUNK)
AS-MT (TRUNK)	LPBKTERMINAL (ESCON)	SSM-ST3 (E1)
AS-MT-OOG (VCTRM-HP)	LPBKTERMINAL (FC)	SSM-ST3 (TRUNK)
AS-MT-OOG (VCTRM-LP)	LPBKTERMINAL (FCMR)	SSM-ST3E (E1)
AUD-LOG-LOSS (NE)	LPBKTERMINAL (G1000)	SSM-ST3E (TRUNK)
AUD-LOG-LOW (NE)	LPBKTERMINAL (GE)	SSM-ST4 (E1)
AUTOSW-LOP-SNCP (VCMON-HP)	LPBKTERMINAL (ISC)	SSM-ST4 (STMN)
AUTOSW-LOP-SNCP (VCMON-LP)	LPBKTERMINAL (STM1E)	SSM-ST4 (TRUNK)
—	LPBKTERMINAL (STMN)	SSM-STU (BITS)
AUTOSW-SDBER-SNCP (VCMON-HP)	LPBKTERMINAL (TRUNK)	SSM-STU (E1)
AUTOSW-SFBER-SNCP (VCMON-HP)	MAN-REQ (EQPT)	SSM-STU (NE-SREF)
AUTOSW-UNEQ-SNCP (VCMON-HP)	MAN-REQ (VCMON-HP)	SSM-STU (STMN)
AWG-WARM-UP (OTS)	MAN-REQ (VCMON-LP)	SSM-STU (TRUNK)
CLDRESTART (EQPT)	MANRESET (EQPT)	SSM-TNC (STMN)
CTNEQPT-MISMATCH (EQPT)	MANSWTOINT (NE-SREF)	SSM-TNC (TRUNK)
DS3-MISM (DS3)	MANSWTOPRI (EXT-SREF)	SW-MISMATCH (EQPT)
ETH-LINKLOSS (NE)	MANSWTOPRI (NE-SREF)	SWTOPRI (EXT-SREF)
EXERCISE-RING-FAIL (STMN)	MANSWTOSEC (EXT-SREF)	SWTOPRI (NE-SREF)
EXERCISE-SPAN-FAIL (STMN)	MANSWTOSEC (NE-SREF)	SWTOSEC (EXT-SREF)
FAILTOSW (EQPT)	MANSWTOTHIRD (EXT-SREF)	SWTOSEC (NE-SREF)
FAILTOSW (ESCON)	MANSWTOTHIRD (NE-SREF)	SWTOTHIRD (EXT-SREF)
FAILTOSW (FC)	MANUAL-REQ-RING (STMN)	SWTOTHIRD (NE-SREF)
FAILTOSW (GE)	MANUAL-REQ-SPAN (ESCON)	SYNC-FREQ (E1)
FAILTOSW (ISC)	MANUAL-REQ-SPAN (FC)	SYNC-FREQ (STMN)
FAILTOSW (STMN)	MANUAL-REQ-SPAN (GE)	SYNC-FREQ (TRUNK)
FAILTOSW (TRUNK)	MANUAL-REQ-SPAN (ISC)	TEMP-MISM (NE)
FAILTOSW-HO (VCMON-HP)	MANUAL-REQ-SPAN (STMN)	TX-RAI (DS1)
FAILTOSW-LO (VCMON-LP)	MANUAL-REQ-SPAN (TRUNK)	TX-RAI (E1)
FAILTOSWR (STMN)	MS-SQUELCH-HP (STMN)	TX-RAI (E3)
FAILTOSWS (STMN)	MS-SQUELCH-LP (STMN)	UNC-WORD (TRUNK)
FE-AIS (E3)	NO-CONFIG (EQPT)	VCG-DEG (VCG)
FE-E1-MULTLOS (E3)	OCHNC-INC (OCHNC-CONN)	VCG-DOWN (VCG)
FE-E1-NSA (E3)	ODUK-SD-PM (TRUNK)	VOLT-MISM (PWR)
FE-E1-SA (E3)	ODUK-SF-PM (TRUNK)	WKSWPR (EQPT)
FE-E1-SNGLLOS (E3)	OOU-TPT (VCTRM-HP)	WKSWPR (ESCON)
FE-E3-NSA (E3)	OOU-TPT (VCTRM-LP)	WKSWPR (FC)
FE-E3-SA (E3)	OSRION (AOTS)	WKSWPR (GE)
FE-EQPT-NSA (E3)	OSRION (OTS)	WKSWPR (ISC)
FE-FRCDWKSWBK-SPAN (STMN)	OTUK-SD (TRUNK)	WKSWPR (STMN)
FE-FRCDWKSWPR-RING (STMN)	OTUK-SF (TRUNK)	WKSWPR (TRUNK)
FE-FRCDWKSWPR-SPAN (STMN)	OUT-OF-SYNC (ISC)	WKSWPR (VCMON-HP)
FE-IDLE (E3)	PARAM-MISM (OCH)	WKSWPR (VCMON-LP)
FE-LOCKOUTOFPR-SPAN (STMN)	PARAM-MISM (OMS)	WTR (EQPT)
FE-LOF (E3)	PARAM-MISM (OTS)	WTR (ESCON)
FE-LOS (E3)	—	WTR (FC)
FE-MANWKSWBK-SPAN (STMN)	PORT-MISMATCH (FCMR)	WTR (GE)
FE-MANWKSWPR-RING (STMN)	RAI (DS1)	WTR (ISC)
FE-MANWKSWPR-SPAN (STMN)	RAI (DS3)	WTR (STMN)
FORCED-REQ (EQPT)	RAI (E1)	WTR (TRUNK)
FORCED-REQ (VCMON-HP)	RFI-V (VCMON-LP)	WTR (VCMON-HP)
FORCED-REQ (VCMON-LP)	RING-SW-EAST (STMN)	WTR (VCMON-LP)

2.1.5  Not Reported Conditions (NR)

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

Table 2-5 ONS 15454 SDH Not Reported Conditions List 

AIS (BITS)	HP-RFI (VCMON-HP)	ODUK-OCI-PM (TRUNK)
AIS (DS1)	HP-RFI (VCTRM-HP)	OTUK-AIS (TRUNK)
AIS (DS3)	LP-RFI (VCMON-LP)	OTUK-BDI (TRUNK)
AIS (E1)	LP-RFI (VCTRM-LP)	RFI (TRUNK)
AIS (E3)	MS-AIS (STM1E)	ROLL-PEND (VCTRM-HP)
AIS (E4)	MS-AIS (STMN)	TU-AIS (VCMON-LP)
AIS (FUDC)	MS-RFI (STM1E)	TU-AIS (VCTRM-LP)
AIS (MSUDC)	ODUK-1-AIS-PM (TRUNK)	TX-AIS (DS1)
AIS (TRUNK)	ODUK-2-AIS-PM (TRUNK)	TX-AIS (DS3)
AIS-L (TRUNK)	ODUK-3-AIS-PM (TRUNK)	TX-AIS (E1)
AU-AIS (VCMON-HP)	ODUK-4-AIS-PM (TRUNK)	TX-AIS (E3)
AU-AIS (VCTRM-HP)	ODUK-AIS-PM (TRUNK)	TX-LOF (DS1)
AUTOSW-AIS-SNCP (VCMON-HP)	ODUK-BDI-PM (TRUNK)	TX-LOF (E1)
AUTOSW-AIS-SNCP (VCMON-LP)	ODUK-LCK-PM (TRUNK)	—

2.2  Alarms and Conditions Listed 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 List 

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

2.2.1  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 can appear in multiple entries. It can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (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 Definitions 

Object Type	Definition
2R	Reshape and retransmit (used for transponder [TXP] cards). For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
AICI-AEP	Alarm Interface Controller-International—Alarm expansion panel.
AIP	Alarm Interface Panel.
AOTS	Amplified optical transport section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
BIC	Backplane interface connector.
BITS	Building integrated timing supply incoming references (BITS-1, BITS-2).
BPLANE	The backplane.
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, STM, and VC.
ESCON	Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
EXT-SREF	BITS outgoing references (SYNC-BITS1, SYNC-BITS2).
FAN	Fan-tray assembly.
FC	Fibre Channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E.  For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
FCMR	An FC_MR-4 Fibre Channel card. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
FUDC	SDH F1 byte user data channel for ONS 15454 SDH ML-Series Ethernet cards.
G1000	The ONS 15454 SDH G-Series 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. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
GFP-FAC	Generic framing procedure facility port, referring to all MXP and TXP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
ISC	Inter-service channel referring to MXP and TXP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
LOGFAC	The LOGFAC object is not used in this platform in this release. It is reserved for development.
ML1000	The ONS 15454 SDH ML1000-2 card.
ML100T	The ONS 15454 SDH ML100T-2 or ML100T-8 card.
MLFX	An MLFX Ethernet card.
MSUDC	Multiplex section user data channel.
NE	The entire network element.
NE-SREF	The timing status of the NE.
OCH	The optical channel, referring to a dense wavelength division multiplexing (DWDM) cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
OCHNC-CONN	The optical channel network connection, referring to DWDM cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
OMS	Optical multiplex section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
OTS	Optical transport section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
PWR	Power equipment.
PPM	Pluggable port module (PPM), referring to all MXP and TXP cards, MRC-12 cards, and OC192-XFP/STM64-XFP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
STM1E	Synchronous transfer mode 1 (speed) electrical interface
STMN	An STM-N line on an STM-N card.
VCTRM-HP	VT 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. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.
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	VC alarm detection at termination (downstream from the cross-connect).

2.3  Alarm List by Logical Object Type

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

---

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

---

---

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

---

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

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

2.4  Trouble Notifications

The ONS 15454 SDH system reports trouble by utilizing standard alarm and condition characteristics, and 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 address, such as a loss of signal. Conditions do not necessarily require troubleshooting.

2.4.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.4.2  Condition Characteristics

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

For more information about transient conditions, see Chapter 3, "Transient Conditions."

---

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

---

2.4.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 (SA) 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 automatic protection switching (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 (LTE) detects a byte failure on the signal that could prevent traffic from properly executing a traffic switch.

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

•Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (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.

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

2.4.4  Alarm Hierarchy

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

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

Table 2-9 Path Alarm Hierarchy

Priority	Condition Type
Highest	AU-AIS
—	AU-LOP
—	HP-UNEQ
Lowest	HP-TIM

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

Table 2-10 Facility Alarm Hierarchy

Priority	Condition Type
Highest	LOS
—	LOF
—	MS-AIS
—	MS-EXC1
—	MS-DEG1
—	MS-RDI1
—	RS-TIM
—	AU-AIS
—	AU-LOP
—	HP-EXC1
—	HP-DEG1
—	HP-UNEQ
—	HP-TIM
Lowest	HP-PLM1

1 This alarm is not currently used in the platform.

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

Table 2-11 Near-End Alarm Hierarchy

Priority	Condition Type
Highest	LOS
—	LOF
—	MS-AIS
—	AU-AIS1
—	AU-LOP2
—	HP-UNEQ
—	HP-TIM
—	HP-PLM
—	TU-AIS1
—	TU-LOP2
—	LP-UNEQ3
—	LP-PLM3
Lowest	DS-N AIS (if reported for outgoing DS-N signals)

1 Although it is not defined as a defect or failure, all-ones VT pointer relay is also higher priority than AU-LOP. Similarly, all-ones VC pointer relay is higher priority than TU-LOP. 2 AU-LOP is also higher priority than the far-end failure MS-RFI, which does not affect the detection of any near-end failures. Similarly, TU-LOP is higher priority than LP-RF. 3 This alarm is not used in this platform in this release.

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

Table 2-12 Far-End Alarm Hierarchy

Priority	Condition Type
Highest	MS-RDI1
—	HP-RFI
Lowest	LP-RFI1

1 This condition is not used in this platform in this release.

2.4.5  Service Effect

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

2.4.6  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. These are listed in Chapter 3, "Transient Conditions."

2.5  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 could 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.6  Alarm Procedures

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

---

Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner of the GUI is not indented. If it is, click it to turn it off. When you'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 "Manage Alarms" chapter of 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 "Manage Alarms" chapter in the Cisco ONS 15454 SDH Procedure Guide.

---

---

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

---

2.6.1  AIS

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

SDH Logical Objects: BITS, DS1, DS3, E1, E3, E4, FUDC, MSUDC

DWDM Logical Object: TRUNK

The Alarm Indication Signal (AIS) condition indicates that this node is detecting an alarm indication signal in the incoming signal 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 detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

---

Note 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-144, or if there are 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.6.2  AIS-L

The AIS-L condition is not used in this platform in this release. It is reserved for development.

2.6.3  ALS

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

2.6.4  ALS-DISABLED

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

2.6.5  AMPLI-INIT

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

2.6.6  APC-CORRECTION-SKIPPED

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

2.6.7  APC-DISABLED

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

2.6.8  APC-END

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

2.6.9  APC-OUT-OF-RANGE

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

2.6.10  APSB

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

SDH Logical Object: STMN

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

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 could 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 the 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.6.11  APSCDFLTK

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

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

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-82.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide 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 RS-DCC Terminations" procedure to ensure that regenerator section data communications channel (RS-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.6.12  APSC-IMP

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

SDH Logical Object: STMN

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 from the protect card to the working one. 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.

---

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

---

---

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

---

---

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

---

---

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

---

---

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

---

Clear the APSC-IMP Alarm

---

Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal. For specific procedures to use the test set equipment, consult the manufacturer.

---

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 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 lies with upstream equipment and not with 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.6.13  APSCINCON

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

SDH 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 when necessary. An inconsistent APS code occurs when three consecutive frames contain nonidentical APS bytes, which in turn give the receiving equipment conflicting commands about switching.

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

---

Step 1 Look for other alarms, especially the "LOS (STM1E, STMN)" alarm, page 2-144, the "LOF (DS1, DS3, E1, E4, STM1E, STMN)" alarm on page 2-134, or the "APSB" alarm on page 2-33. 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.6.14  APSCM

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

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

---

2.6.15  APSCNMIS

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

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

---

2.6.16  APS-INV-PRIM

The APS-INV-PRIM alarm is not used in this platform in this release. It is reserved for development.

2.6.17  APS-PRIM-FAC

The APS-PRIM-FAC condition is not used in this platform in this release. It is reserved for development.

2.6.18  APS-PRIM-SEC-MISM

The APS-PRIM-SEC-MISM condition is not used in this platform in this release. It is reserved for development.

2.6.19  AS-CMD

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

SDH Logical Objects: BPLANE, CE100T, CE1000, DS1, DS3, E1, E100T, E1000F, E3, E4, EQPT, FCMR, G1000 GFP-FAC, LOGFAC, ML100T, ML1000, MLFX, NE, PWR, STM1E, STMN

DWDM Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCH, OMS, OTS, PPM, SHELF, TRUNK

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

---

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

---

Clear the AS-CMD Condition

---

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

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

If the condition is reported against 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 by completing the following steps:

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

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

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

•If the Suppress Alarms column check box is not checked for a port row, 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 by completing the following steps:

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

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

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

•If the Suppress Alarms column check box is not checked for a port row, 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, complete the following steps:

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

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

c. Click Apply.

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

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

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.6.20  AS-MT

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

SDH Logical Objects: CE100T, CE1000, DS1, DS3, E1, E3, E4, EQPT, FCMR, G1000, GFP-FAC, LOGFAC, ML100T, ML1000, MLFX, STM1E, STMN

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

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

SDH Logical Objects: VCTRM-HP, VCTRM-LP

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

Clear the AS-MT-OOG Condition

---

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

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.6.22  AU-AIS

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

SDH Logical Objects: VCMON-HP, VCTRM-HP

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

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

Clear the AU-AIS Condition

---

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

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

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

---

2.6.23  AUD-LOG-LOSS

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

SDH 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.6.24  AUD-LOG-LOW

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

SDH 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.6.25  AU-LOF

Critical (CR), Service-Affecting (SA)

SDH Logical Object: VCTRM-HP

The 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, which is located in the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or 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 (SA) problem.

---

2.6.26  AU-LOP

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

SDH Logical Objects: VCMON-HP, VCTRM-HP

An AU-LOP alarm indicates that the SDH high order path overhead section of the administration unit has detected a loss of path. AU-LOP occurs when there is a mismatch between the expected and provisioned circuit size. For the TXP card, an AU-LOP is raised if a port is configured for an SDH signal but receives a 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 could result in hazardous radiation exposure. Statement 1057

---

---

Note For more information about MXP and TXP cards, refer to the Cisco ONS 15454 SDH Reference Manual.

---

Clear the AU-LOP Alarm

---

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

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

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

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

Step 5 Recreate the circuit for the correct size. For procedures, refer to the "Create Circuits and Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide.

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

---

2.6.27  AUTOLSROFF

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

SDH Logical Object: STMN

DWDM Logical Object: TRUNK

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

---

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

---

---

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

---

---

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

---

Clear the AUTOLSROFF Alarm

---

Step 1 View the temperature displayed on the ONS 15454 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.

---

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

---

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

---

2.6.28  AUTORESET

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

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

---

---

Note When you replace a card with the 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.6.29  AUTOSW-AIS-SNCP

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

SDH Logical Objects: VCMON-HP, VCMON-LP

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

---

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

---

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

Clear the 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.6.30  AUTOSW-LOP-SNCP

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

SDH 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-43. If the SNCP ring is configured for revertive switching, it switches back to the working path after the fault clears.

---

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

---

Clear the AUTOSW-LOP-SNCP Alarm

---

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

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

---

2.6.31  AUTOSW-SDBER-SNCP

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

SDH Logical Object: VCMON-HP

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

---

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

---

Clear the AUTOSW-SDBER-SNCP Condition

---

Step 1 Complete the "Clear the SD (DS3, E1, E3, E4, STM1E, STMN) 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.6.32  AUTOSW-SFBER-SNCP

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

SDH Logical Object: VCMON-HP

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

---

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

---

Clear the AUTOSW-SFBER-SNCP Condition

---

Step 1 Complete the "Clear the SF (DS3, E1, E3, E4, STMN) 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.6.33  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

SDH 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-119). If the SNCP ring is configured for revertive switching, it reverts to the working path after the fault clears.

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

---

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

---

---

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

---

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

---

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

Step 2 If the 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.6.34  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

SDH Logical Object: VCMON-LP

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

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

---

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

---

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 condition does not clear, verify that all circuits terminating in the reporting card are active by completing the following steps:

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 condition does not clear, verify that the far-end STM-N card providing payload to the card is working properly.

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

Step 11 If the condition 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 the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.

---

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

---

---

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

---

---

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

---

Step 12 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.6.35  AWG-DEG

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

2.6.36  AWG-FAIL

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

2.6.37  AWG-OVERTEMP

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

2.6.38  AWG-WARM-UP

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

2.6.39  BAT-FAIL

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

SDH Logical Object: PWR

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

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

---

2.6.40  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 card flash memory. This alarm is raised on ACT/SBY TCC2/TCC2P cards. The alarm occurs when the TCC2/TCC2P card 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 card).

The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-76. 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/TCC2P cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2/TCC2P cards.

Step 2 Determine whether the active or standby TCC2/TCC2P card has the alarm.

Step 3 If both cards are powered and enabled, reset the TCC2/TCC2P card where the alarm is raised. If the card is the active TCC2/TCC2P card, complete the "Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2/TCC2P card LED should be green.
If the card is the standby TCC2/TCC2P card, complete the "Reset the Standby TCC2/TCC2P Card" procedure.

Step 4 If the reset TCC2/TCC2P card 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.6.41  CARLOSS (CE100T, CE10000)

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

SDH Logical Objects: CE100T, CE1000

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

---

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

---

Clear the CARLOSS (CE100T, CE10000) Alarm

---

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

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

---

2.6.42  CARLOSS (E100T, E1000F)

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

SDH 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, page 2-144. 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 G-Series card. The G-Series card does not use STP and is not affected by STP reestablishment.

---

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

---

Clear the CARLOSS (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 "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide.

---

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 "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide.

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 "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide.

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

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

---

Note When you replace a card with the 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 vendor's equipment sits between ONS 15454 SDHs, and the open systems interconnect/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 a channel riding through the non-ONS network.

If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm could be a result of mismatched circuit sizes in the set up of the manual cross-connect. Determine this by completing the following steps. 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 are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:

•Log into the ONS 15454 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 procedures, refer to the "Create Circuits and Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide.

Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or 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.6.43  CARLOSS (EQPT)

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

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

---

Note For more information about MXP and TXP cards, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide. For more information about MRC-12 cards and OC192-XFP/STM64-XFP cards, refer to the "Change Card Settings of the Cisco ONS 15454 SDH Procedure Guide.

---

Clear the CARLOSS (EQPT) Alarm

---

Step 1 If the reporting card is an MXP, TXP, MRC-12, or OC192-XVP/STM64-XFP card in an ONS 15454 SDH node, verify the data rate configured on the PPM by completing the following steps:

a. Double-click the reporting card.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Equipment Type column for the 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.

---

Note For more information about provisioning PPMs, refer to the Cisco ONS 15454 DWDM Procedure Guide.

---

Step 2 If the reporting card is an STM-N card, verify connectivity by pinging the ONS 15454 SDH that is reporting the alarm by completing the procedure in the "1.8.8  Verify PC Connection to the ONS 15454 SDH (ping)" section on page 1-100.

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

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 specific procedures to use the test set equipment, consult the manufacturer.)

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

Step 6 If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card. For more information about fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide.

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

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

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

---

2.6.44  CARLOSS (FC)

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

2.6.45  CARLOSS (G1000)

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

SDH 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-144. The Ethernet card has lost its link and is not receiving a valid signal.

CARLOSS on the G-Series card is caused by one of two situations:

•The G-Series 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 G-Series port.

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

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

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

---

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

---

Clear the CARLOSS (G1000) Alarm

---

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

---

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.

---

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. The correct specifications are listed in the "1.11.3  Optical Card Transmit and Receive Levels" section on page 1-126.

Step 5 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port. For specific procedures to use the test set equipment, consult the manufacturer.

Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide.

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

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

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

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

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

---

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

---

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

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

b. Click the Maintenance > Loopback tabs.

c. If the service state is listed as Locked-disabled, loopback & maintenance, a loopback is provisioned. Go to Step 11.

Step 11 If a loopback was provisioned, complete the "Clear a Non-STM Card Facility or Terminal Loopback Circuit" procedure.

On the G-Series, 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 G-Series card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G-Series port detects the termination.

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

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

---

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

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

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

•Click the Circuits tab.

•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit connects the Ethernet card to an 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 "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide for detailed procedures to create circuits.

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

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

Step 15 If the alarm does not clear, log into 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 (SA) problem.

---

2.6.46  CARLOSS (GE)

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

2.6.47  CARLOSS (ISC)

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

2.6.48  CARLOSS (LOGFAC)

This alarm is not used in this platform in this release. It is reserved for development.

2.6.49  CARLOSS (ML100T, ML1000, MLFX)

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

SDH Logical Objects: ML100T, ML1000, MLFX

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

---

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

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

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

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

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

Step 6 If the 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.

---

Note When you replace a card with the 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 (SA) problem.

---

2.6.50  CARLOSS (TRUNK)

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

2.6.51  CASETEMP-DEG

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

2.6.52  CLDRESTART

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

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

---

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

---

Step 4 If 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.6.53  COMIOXC

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

SDH Logical Object: EQPT

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

Clear the COMIOXC Alarm

---

Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the card in which the alarm is reported. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

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

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

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

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

---

Note When you replace a card with the 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 (SA) problem.

---

2.6.54  COMM-FAIL

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

SDH Logical Object: EQPT

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

---

Note When you replace a card with the 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.6.55  CONTBUS-A-18

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

SDH Logical Object: EQPT

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

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 card 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 card to reset as the standby TCC2/TCC2P card. 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 card and complete the "Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card" procedure to return the card to the active state.

Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, 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.6.56  CONTBUS-B-18

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

SDH Logical Object: EQPT

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

Clear the CONTBUS-B-18 Alarm

---

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

Step 2 Wait approximately 10 minutes for the Slot 11 TCC2/TCC2P card to reset as the standby TCC2/TCC2P card. 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 card and complete the "Reset an ActiveTCC2/TCC2P Card 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.6.57  CONTBUS-DISABLED

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

SDH Logical Object: EQPT

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

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

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

---

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

---

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

Clear the CONTBUS-DISABLED Alarm

---

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

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

---

2.6.58  CONTBUS-IO-A

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

SDH Logical Object: EQPT

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

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

Clear the CONTBUS-IO-A Alarm

---

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

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

Step 2 If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P card, perform a CTC reset of the object card. Complete the "Reset a 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 card, 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 ActiveTCC2/TCC2P Card and Activate the Standby Card" procedure.

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

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

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

---

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 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.6.59  CONTBUS-IO-B

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

SDH Logical Object: EQPT

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

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

Clear the CONTBUS-IO-B Alarm

---

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

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

Step 2 If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P card, perform a CTC reset of the object card. Complete the "Reset a 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 card, 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 ActiveTCC2/TCC2P Card and Activate the Standby Card" procedure.

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

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

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

---

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 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.6.60  CTNEQPT-MISMATCH

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

SDH Logical Object: EQPT

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

---

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

---

---

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

---

---

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

---

Clear the CTNEQPT-MISMATCH Condition

---

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