Table Of Contents

Alarm Troubleshooting

2.1  Alarm Indexes by Default Severity

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  NA Conditions

2.1.5  NR Conditions

2.2  Alarms and Conditions Listed By Alphabetical Entry

2.3  Alarm Logical Objects

2.4  Alarm List by Logical Object Type

2.5  DS3-12 E Line Alarms

2.6  Trouble Notifications

2.6.1  Alarm Characteristics

2.6.2  Condition Characteristics

2.6.3  Severities

2.6.4  Alarm Hierarchy

2.6.5  Service Effect

2.6.6  States

2.7  Safety Summary

2.8  Alarm Procedures

2.8.1  AIS

Clear the AIS Condition

2.8.2  AIS-L

Clear the AIS-L Condition

2.8.3  AIS-P

Clear the AIS-P Condition

2.8.4  AIS-V

Clear the AIS-V Condition

2.8.5  ALS

2.8.6  AMPLI-INIT

2.8.7  APC-CORRECTION-SKIPPED

2.8.8  APC-DISABLED

2.8.9  APC-END

2.8.10  APC-OUT-OF-RANGE

2.8.11  APSB

2.8.12  APSCDFLTK

Clear the APSCDFLTK Alarm

2.8.13  APSC-IMP

Clear the APSC-IMP Alarm

2.8.14  APSCINCON

Clear the APSCINCON Alarm

2.8.15  APSCM

Clear the APSCM Alarm

2.8.16  APSCNMIS

Clear the APSCNMIS Alarm

2.8.17  APSIMP

Clear the APSIMP Alarm

2.8.18  APS-INV-PRIM

2.8.19  APSMM

Clear the APSMM Alarm

2.8.20  APS-PRIM-FAC

Clear the APS-PRIM-FAC Condition

2.8.21  APS-PRIM-SEC-MISM

Clear the APS-PRIM-SEC-MISM Alarm

2.8.22  AS-CMD

Clear the AS-CMD Condition

2.8.23  AS-MT

Clear the AS-MT Condition

2.8.24  AS-MT-OOG

2.8.25  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.8.26  AUD-LOG-LOW

2.8.27  AU-LOF

2.8.28  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.8.29  AUTORESET

Clear the AUTORESET Alarm

2.8.30  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.8.31  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.8.32  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Condition

2.8.33  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.8.34  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.8.35  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.8.36  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.8.37  AWG-DEG

2.8.38  AWG-FAIL

2.8.39  AWG-OVERTEMP

2.8.40  AWG-WARM-UP

2.8.41  BAT-FAIL

Clear the BAT-FAIL Alarm

2.8.42  BKUPMEMP

Clear the BKUPMEMP Alarm

2.8.43  BLSROSYNC

Clear the BLSROSYNC Alarm

2.8.44  BLSR-SW-VER-MISM

Clear the BLSR-SW-VER-MISM Alarm

2.8.45  BPV

Clear the BPV Alarm

2.8.46  CARLOSS (CE100T)

Clear the CARLOSS (CE100T) Alarm

2.8.47  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.8.48  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.8.49  CARLOSS (FC)

2.8.50  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.8.51  CARLOSS (GE)

2.8.52  CARLOSS (ISC)

2.8.53  CARLOSS (ML100T, ML1000, MLFX)

Clear the CARLOSS (ML100T, ML1000, MLFX) Alarm

2.8.54  CARLOSS (TRUNK)

2.8.55  CASETEMP-DEG

2.8.56  CLDRESTART

Clear the CLDRESTART Condition

2.8.57  COMIOXC

Clear the COMIOXC Alarm

2.8.58  COMM-FAIL

Clear the COMM-FAIL Alarm

2.8.59  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.8.60  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.8.61  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.8.62  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.8.63  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.8.64  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.8.65  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.8.66  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.8.67  DATAFLT

Clear the DATAFLT Alarm

2.8.68  DBOSYNC

Clear the DBOSYNC Alarm

2.8.69  DS3-MISM

Clear the DS3-MISM Condition

2.8.70  DSP-COMM-FAIL

2.8.71  DSP-FAIL

2.8.72  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.8.73  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.8.74  EHIBATVG

Clear the EHIBATVG Alarm

2.8.75  ELWBATVG

Clear the ELWBATVG Alarm

2.8.76  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.8.77  EOC

Clear the EOC Alarm

2.8.78  EOC-L

Clear the EOC-L Alarm

2.8.79  EQPT

Clear the EQPT Alarm

2.8.80  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.8.81  EQPT-MISS

Clear the EQPT-MISS Alarm

2.8.82  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.8.83  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.8.84  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.8.85  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.8.86  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.8.87  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.8.88  EXCCOL

Clear the EXCCOL Alarm

2.8.89  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.8.90  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.8.91  EXT

Clear the EXT Alarm

2.8.92  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.8.93  FAILTOSW

Clear the FAILTOSW Condition

2.8.94  FAILTOSW-PATH

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration

2.8.95  FAILTOSWR

Clear the FAILTOSWR Condition in a BLSR Configuration

2.8.96  FAILTOSWS

Clear the FAILTOSWS Condition

2.8.97  FAN

Clear the FAN Alarm

2.8.98  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.8.99  FE-AIS

Clear the FE-AIS Condition

2.8.100  FEC-MISM

2.8.101  FE-DS1-MULTLOS

Clear the FE-DS1-MULTLOS Condition

2.8.102  FE-DS1-NSA

Clear the FE-DS1-NSA Condition

2.8.103  FE-DS1-SA

Clear the FE-DS1-SA Condition

2.8.104  FE-DS1-SNGLLOS

Clear the FE-DS1-SNGLLOS Condition

2.8.105  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.8.106  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.8.107  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.8.108  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.8.109  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.8.110  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.8.111  FE-IDLE

Clear the FE-IDLE Condition

2.8.112  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.8.113  FE-LOF

Clear the FE-LOF Condition

2.8.114  FE-LOS

Clear the FE-LOS Condition

2.8.115  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.8.116  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.8.117  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.8.118  FEPRLF

Clear the FEPRLF Alarm on a Four-Fiber BLSR

2.8.119  FIBERTEMP-DEG

2.8.120  FORCED-REQ

Clear the FORCED-REQ Condition

2.8.121  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.8.122  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.8.123  FRCDSWTOINT

2.8.124  FRCDSWTOPRI

2.8.125  FRCDSWTOSEC

2.8.126  FRCDSWTOTHIRD

2.8.127  FRNGSYNC

Clear the FRNGSYNC Condition

2.8.128  FSTSYNC

2.8.129  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.8.130  GAIN-HDEG

2.8.131  GAIN-HFAIL

2.8.132  GAIN-LDEG

2.8.133  GAIN-LFAIL

2.8.134  GCC-EOC

2.8.135  GE-OOSYNC

2.8.136  GFP-CSF

Clear the GFP-CSF Alarm

2.8.137  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.8.138  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.8.139  GFP-LFD

Clear the GFP-LFD Alarm

2.8.140  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.8.141  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.8.142  HELLO

Clear the HELLO Alarm

2.8.143  HIBATVG

Clear the HIBATVG Alarm

2.8.144  HI-CCVOLT

Clear the HI-CCVOLT Condition

2.8.145  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.8.146  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.8.147  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.8.148  HITEMP

Clear the HITEMP Alarm

2.8.149  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.8.150  HLDOVRSYNC

Clear the HLDOVRSYNC Condition

2.8.151  I-HITEMP

Clear the I-HITEMP Alarm

2.8.152  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.8.153  INC-ISD

2.8.154  INHSWPR

Clear the INHSWPR Condition

2.8.155  INHSWWKG

Clear the INHSWWKG Condition

2.8.156  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.8.157  INVMACADR

Clear the INVMACADR Alarm

2.8.158  IOSCFGCOPY

2.8.159  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.8.160  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.8.161  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.8.162  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.8.163  LASER-APR

2.8.164  LASERBIAS-DEG

2.8.165  LASERBIAS-FAIL

2.8.166  LASEREOL

Clear the LASEREOL Alarm

2.8.167  LASERTEMP-DEG

2.8.168  LCAS-CRC

Clear the LCAS-CRC Condition

2.8.169  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.8.170  LCAS-TX-ADD

2.8.171  LCAS-TX-DNU

2.8.172  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.8.173  LOA

Clear the LOA Alarm

2.8.174  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.8.175  LOF (BITS)

Clear the LOF (BITS) Alarm

2.8.176  LOF (DS1)

Clear the LOF (DS1) Alarm

2.8.177  LOF (DS3)

Clear the LOF (DS3) Alarm

2.8.178  LOF (E1)

Clear the LOF (E1) Alarm

2.8.179  LOF (EC1)

Clear the LOF (EC1) Alarm

2.8.180  LOF (OCN)

Clear the LOF (OCN) Alarm

2.8.181  LOF (STSTRM)

Clear the LOF (STSTRM) Alarm

2.8.182  LOF (TRUNK)

2.8.183  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.8.184  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.8.185  LOM

Clear the LOM Alarm

2.8.186  LOP-P

Clear the LOP-P Alarm

2.8.187  LOP-V

Clear the LOP-V Alarm

2.8.188  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.8.189  LOS (2R)

2.8.190  LOS (BITS)

Clear the LOS (BITS) Alarm

2.8.191  LOS (DS1)

Clear the LOS (DS1) Alarm

2.8.192  LOS (DS3)

Clear the LOS (DS3) Alarm

2.8.193  LOS (E1)

Clear the LOS (E1) Alarm

2.8.194  LOS (EC1)

Clear the LOS (EC1) Alarm

2.8.195  LOS (ESCON)

2.8.196  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.8.197  LOS (ISC)

2.8.198  LOS (MSUDC)

2.8.199  LOS (OCN)

Clear the LOS (OCN) Alarm

2.8.200  LOS (OTS)

2.8.201  LOS (TRUNK)

2.8.202  LOS-O

2.8.203  LOS-P

2.8.204  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.8.205  LPBKCRS

Clear the LPBKCRS Condition

2.8.206  LPBKDS1FEAC-CMD

2.8.207  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.8.208  LPBKDS3FEAC-CMD

2.8.209  LPBKFACILITY (CE100T)

Clear the LPBKFACILITY (CE100T) Condition

2.8.210  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.8.211  LPBKFACILITY (E1)

Clear the LPBKFACILITY (E1) Condition

2.8.212  LPBKFACILITY (EC1)

Clear the LPBKFACILITY (EC1) Condition

2.8.213  LPBKFACILITY (ESCON)

2.8.214  LPBKFACILITY (FC)

2.8.215  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.8.216  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.8.217  LPBKFACILITY (GE)

2.8.218  LPBKFACILITY (ISC)

2.8.219  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.8.220  LPBKFACILITY (TRUNK)

2.8.221  LPBKTERMINAL (CE100T)

Clear the LPBKTERMINAL (CE100T) Condition

2.8.222  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.8.223  LPBKTERMINAL (E1)

Clear the LPBKTERMINAL (E1) Condition

2.8.224  LPBKTERMINAL (EC1)

Clear the LPBKTERMINAL (EC1) Condition

2.8.225  LPBKTERMINAL (ESCON)

2.8.226  LPBKTERMINAL (FC)

2.8.227  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.8.228  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.8.229  LPBKTERMINAL (GE)

2.8.230  LPBKTERMINAL (ISC)

2.8.231  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.8.232  LPBKTERMINAL (TRUNK)

2.8.233  LWBATVG

Clear the LWBATVG Alarm

2.8.234  MAN-REQ

Clear the MAN-REQ Condition

2.8.235  MANRESET

2.8.236  MANSWTOINT

2.8.237  MANSWTOPRI

2.8.238  MANSWTOSEC

2.8.239  MANSWTOTHIRD

2.8.240  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.8.241  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.8.242  MEA (AIP)

Clear the MEA (AIP) Alarm

2.8.243  MEA (BIC)

Clear the MEA (BIC) Alarm

2.8.244  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.8.245  MEA (FAN)

Clear the MEA (FAN) Alarm

2.8.246  MEA (PPM)

2.8.247  MEM-GONE

2.8.248  MEM-LOW

2.8.249  MFGMEM

Clear the MFGMEM Alarm

2.8.250  NO-CONFIG

Clear the NO-CONFIG Condition

2.8.251  NOT-AUTHENTICATED

2.8.252  OCHNC-INC

2.8.253  ODUK-1-AIS-PM

2.8.254  ODUK-2-AIS-PM

2.8.255  ODUK-3-AIS-PM

2.8.256  ODUK-4-AIS-PM

2.8.257  ODUK-AIS-PM

2.8.258  ODUK-BDI-PM

2.8.259  ODUK-LCK-PM

2.8.260  ODUK-OCI-PM

2.8.261  ODUK-SD-PM

2.8.262  ODUK-SF-PM

2.8.263  ODUK-TIM-PM

2.8.264  OOU-TPT

Clear the OOT-TPT Condition

2.8.265  OPEN-SLOT

Clear the OPEN-SLOT Condition

2.8.266  OPTNTWMIS

2.8.267  OPWR-HDEG

2.8.268  OPWR-HFAIL

2.8.269  OPWR-LDEG

2.8.270  OPWR-LFAIL

2.8.271  OSRION

2.8.272  OTUK-AIS

2.8.273  OTUK-BDI

2.8.274  OTUK-IAE

2.8.275  OTUK-LOF

2.8.276  OTUK-SD

2.8.277  OTUK-SF

2.8.278  OTUK-TIM

2.8.279  OUT-OF-SYNC

2.8.280  PARAM-MISM

2.8.281  PDI-P

Clear the PDI-P Condition

2.8.282  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.8.283  PLM-P

Clear the PLM-P Alarm

2.8.284  PLM-V

Clear the PLM-V Alarm

2.8.285  PORT-ADD-PWR-DEG-HI

2.8.286  PORT-ADD-PWR-DEG-LOW

2.8.287  PORT-ADD-PWR-FAIL-HIGH

2.8.288  PORT-ADD-PWR-FAIL-LOW

2.8.289  PORT-FAIL

2.8.290  PORT-MISMATCH

Clear the PORT-MISMATCH Alarm

2.8.291  PRC-DUPID

Clear the PRC-DUPID Alarm

2.8.292  PROTNA

Clear the PROTNA Alarm

2.8.293  PROV-MISMATCH

2.8.294  PTIM

2.8.295  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.8.296  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.8.297  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.8.298  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.8.299  RAI

Clear the RAI Condition

2.8.300  RCVR-MISS

Clear the RCVR-MISS Alarm

2.8.301  RFI

2.8.302  RFI-L

Clear the RFI-L Condition

2.8.303  RFI-P

Clear the RFI-P Condition

2.8.304  RFI-V

Clear the RFI-V Condition

2.8.305  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.8.306  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.8.307  RING-SW-EAST

2.8.308  RING-SW-WEST

2.8.309  ROLL

2.8.310  ROLL-PEND

2.8.311  RPRW

Clear the RPRW Condition

2.8.312  RUNCFG-SAVENEED

2.8.313  SD (DS1, DS3)

Clear the SD (DS1, DS3) Condition

2.8.314  SD (E1)

Clear the SD (E1) Condition

2.8.315  SD (TRUNK)

2.8.316  SD-L

Clear the SD-L Condition

2.8.317  SD-P

Clear the SD-P Condition

2.8.318  SD-V

Clear the SD-V Condition

2.8.319  SF (DS1, DS3)

Clear the SF (DS1, DS3) Condition

2.8.320  SF (E1)

Clear the SF (E1) Condition

2.8.321  SF (TRUNK)

2.8.322  SF-L

Clear the SF-L Condition

2.8.323  SF-P

Clear the SF-P Condition

2.8.324  SFTWDOWN

2.8.325  SF-V

Clear the SF-V Condition

2.8.326  SH-INS-LOSS-VAR-DEG-HIGH

2.8.327  SH-INS-LOSS-VAR-DEG-LOW

2.8.328  SHUTTER-OPEN

2.8.329  SIGLOSS

Clear the SIGLOSS Alarm

2.8.330  SNTP-HOST

Clear the SNTP-HOST Alarm

2.8.331  SPAN-SW-EAST

2.8.332  SPAN-SW-WEST

2.8.333  SQUELCH

Clear the SQUELCH Condition

2.8.334  SQUELCHED

Clear the SQUELCHED Condition

2.8.335  SQM

Clear the SQM Alarm

2.8.336  SSM-DUS

2.8.337  SSM-FAIL

Clear the SSM-FAIL Alarm

2.8.338  SSM-LNC

2.8.339  SSM-OFF

Clear the SSM-OFF Condition

2.8.340  SSM-PRC

2.8.341  SSM-PRS

2.8.342  SSM-RES

2.8.343  SSM-SDN-TN

2.8.344  SSM-SETS

2.8.345  SSM-SMC

2.8.346  SSM-ST2

2.8.347  SSM-ST3

2.8.348  SSM-ST3E

2.8.349  SSM-ST4

2.8.350  SSM-STU

Clear the SSM-STU Condition

2.8.351  SSM-TNC

2.8.352  SWMTXMOD-PROT

Clear the SWMTXMOD-PROT Alarm

2.8.353  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.8.354  SWTOPRI

2.8.355  SWTOSEC

Clear the SWTOSEC Condition

2.8.356  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.8.357  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.8.358  SYNCLOSS

Clear the SYNCLOSS Alarm

2.8.359  SYNCPRI

Clear the SYNCPRI Alarm

2.8.360  SYNCSEC

Clear the SYNCSEC Alarm

2.8.361  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.8.362  SYSBOOT

2.8.363  TEMP-MISM

Clear the TEMP-MISM Condition

2.8.364  TIM

Clear the TIM Alarm

2.8.365  TIM-MON

Clear the TIM-MON Alarm

2.8.366  TIM-P

Clear the TIM-P Alarm

2.8.367  TIM-S

Clear the TIM-S Alarm

2.8.368  TIM-V

Clear the TIM-V Alarm

2.8.369  TPTFAIL (CE100T)

Clear the TPTFAIL (CE100T) Alarm

2.8.370  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.8.371  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.8.372  TPTFAIL (ML100T, ML1000, MLFX)

Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm

2.8.373  TRMT

Clear the TRMT Alarm

2.8.374  TRMT-MISS

Clear the TRMT-MISS Alarm

2.8.375  TX-AIS

Clear the TX-AIS Condition

2.8.376  TX-LOF

Clear the TX-LOF Condition

2.8.377  TX-RAI

Clear the TX-RAI Condition

2.8.378  UNC-WORD

2.8.379  UNEQ-P

Clear the UNEQ-P Alarm

2.8.380  UNEQ-V

Clear the UNEQ-V Alarm

2.8.381  UNREACHABLE-TARGET-POWER

2.8.382  UT-COMM-FAIL

2.8.383  UT-FAIL

2.8.384  VCG-DEG

Clear the VCG-DEG Condition

2.8.385  VCG-DOWN

Clear the VCG-DOWN Condition

2.8.386  VOA-HDEG

2.8.387  VOA-HFAIL

2.8.388  VOA-LDEG

2.8.389  VOA-LFAIL

2.8.390  VOLT-MISM

Clear the VOLT-MISM Condition

2.8.391  WKSWPR

Clear the WKSWPR Condition

2.8.392  WTR

2.8.393  WVL-MISMATCH

2.9  Traffic Card LED Activity

2.9.1  Typical Traffic Card LED Activity After Insertion

2.9.2  Typical Traffic Card LED Activity During Reset

2.9.3  Typical Card LED State After Successful Reset

2.9.4  Typical Cross-Connect LED Activity During Side Switch

2.10  Frequently Used Alarm Troubleshooting Procedures

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

Identify a BLSR Ring Name or Node ID Number

Change a BLSR Ring Name

Change a BLSR Node ID Number

Verify Node Visibility for Other Nodes

2.10.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Manual Switch Command

Clear a 1+1 Force or Manual Switch Command

Initiate a Lock-On Command

Initiate a Card or Port Lockout Command

Clear a Lock-On or Lockout Command

Initiate a 1:1 Card Switch Command

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

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

Initiate a Lockout for All Circuits on a Protect Path Protection Span

Clear an External Switching Command on a Path Protection Span

Initiate a Force Ring Switch on a BLSR

Initiate a Force Span Switch on a Four-Fiber BLSR

Initiate a Manual Span Switch on a BLSR

Initiate a Manual Ring Switch on a BLSR

Initiate a Lockout on a BLSR Protect Span

Initiate an Exercise Ring Switch on a BLSR

Initiate an Exercise Ring Switch on a Four Fiber BLSR

Clear a BLSR External Switching Command

2.10.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

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

Side Switch the Active and Standby Cross-Connect Cards

2.10.4  Physical Card Reseating, Resetting, and Replacement

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

Remove and Reinsert (Reseat) Any Card

Physically Replace a Traffic Card

Physically Replace an In-Service Cross-Connect Card

2.10.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node Section DCC Terminations

Clear an OC-N Card Facility or Terminal Loopback Circuit

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

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

Clear Other Electrical Card, CE-100T-8, or Ethernet Card Loopbacks

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

2.10.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly

2.10.7  Interface Procedures

Replace the Electrical Interface Assembly

Replace the Alarm Interface Panel

Alarm Troubleshooting

---

---

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

---

This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15454 alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in Table 2-8. For a comprehensive list of all conditions and instructions for using TL1 commands, refer to the Cisco SONET TL1 Command Guide .

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

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

2.1  Alarm Indexes by Default Severity

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

---

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

---

---

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

---

2.1.1  Critical Alarms (CR)

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

Table 2-1 ONS 15454 Critical Alarm List 

AUTOLSROFF (OCN)	LOF (TRUNK)	OPWR-HFAIL (OTS)
AUTOLSROFF (TRUNK)	LOM (STSMON)	OPWR-LFAIL (AOTS)
AWG-FAIL (OTS)	LOM (TRUNK)	OPWR-LFAIL (OCH)
AWG-OVERTEMP (OTS)	LOP-P (STSMON)	OPWR-LFAIL (OMS)
BKUPMEMP (EQPT)	LOP-P (STSTRM)	OPWR-LFAIL (OTS)
COMIOXC (EQPT)	LOS (2R)	OTUK-LOF (TRUNK)
CONTBUS-DISABLED (EQPT)	LOS (DS3)	OTUK-TIM (TRUNK)
CTNEQPT-PBPROT (EQPT)	LOS (EC1)	PLM-P (STSMON)
CTNEQPT-PBWORK (EQPT)	LOS (ESCON)	PLM-P (STSTRM)
ENCAP-MISMATCH-P (STSTRM)	LOS (ISC)	PORT-ADD-PWR-FAIL-HIGH (OCH)
EQPT (AICI-AEP)	LOS (OCN)	PORT-ADD-PWR-FAIL-LOW (OCH)
EQPT (AICI-AIE)	LOS (OTS)	PORT-FAIL (OCH)
EQPT (EQPT)	LOS (TRUNK)	SQM (STSTRM)
EQPT (PPM)	LOS-P (OCH)	SWMTXMOD-PROT (EQPT)
EQPT-MISS (FAN)	LOS-P (OMS)	SWMTXMOD-WORK (EQPT)
FAN (FAN)	LOS-P (OTS)	TIM (OCN)
GAIN-HFAIL (AOTS)	LOS-P (TRUNK)	TIM (TRUNK)
GAIN-LFAIL (AOTS)	MEA (AIP)	TIM-P (STSTRM)
GE-OOSYNC (FC)	MEA (BIC)	TIM-S (EC1)
GE-OOSYNC (GE)	MEA (EQPT)	TIM-S (OCN)
GE-OOSYNC (ISC)	MEA (FAN)	UNEQ-P (STSMON)
GE-OOSYNC (TRUNK)	MEA (PPM)	UNEQ-P (STSTRM)
HITEMP (NE)	MFGMEM (AICI-AEP)	VOA-HFAIL (AOTS)
I-HITEMP (NE)	MFGMEM (AICI-AIE)	VOA-HFAIL (OCH)
IMPROPRMVL (EQPT)	MFGMEM (AIP)	VOA-HFAIL (OMS)
IMPROPRMVL (PPM)	MFGMEM (BPLANE)	VOA-HFAIL (OTS)
LOA (VCG)	MFGMEM (FAN)	VOA-LFAIL (AOTS)
LOF (DS3)	MFGMEM (PPM)	VOA-LFAIL (OCH)
LOF (EC1)	OPWR-HFAIL (AOTS)	VOA-LFAIL (OMS)
LOF (OCN)	OPWR-HFAIL (OCH)	VOA-LFAIL (OTS)
LOF (STSTRM)	OPWR-HFAIL (OMS)	—

2.1.2  Major Alarms (MJ)

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

Table 2-2 ONS 15454 Major Alarm List 

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

2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15454 Minor Alarm List 

APSB (OCN)	HI-RXPOWER (FC)	LO-TXPOWER (OCN)
APSCDFLTK (OCN)	HI-RXPOWER (GE)	LO-TXPOWER (PPM)
APSC-IMP (OCN)	HI-RXPOWER (ISC)	LO-TXPOWER (TRUNK)
APSCINCON (OCN)	HI-RXPOWER (OCN)	MEM-LOW (EQPT)
APSIMP (OCN)	HI-RXPOWER (TRUNK)	OPWR-HDEG (AOTS)
APS-INV-PRIM (OCN)	HITEMP (EQPT)	OPWR-HDEG (OCH)
APSMM (OCN)	HI-TXPOWER (2R)	OPWR-HDEG (OMS)
APS-PRIM-SEC-MISM (OCN)	HI-TXPOWER (EQPT)	OPWR-HDEG (OTS)
AUTORESET (EQPT)	HI-TXPOWER (ESCON)	OPWR-LDEG (AOTS)
AUTOSW-UNEQ (VT-MON)	HI-TXPOWER (FC)	OPWR-LDEG (OCH)
AWG-DEG (OTS)	HI-TXPOWER (GE)	OPWR-LDEG (OMS)
BPV (BITS)	HI-TXPOWER (ISC)	OPWR-LDEG (OTS)
CASETEMP-DEG (AOTS)	HI-TXPOWER (OCN)	OTUK-IAE (TRUNK)
COMM-FAIL (EQPT)	HI-TXPOWER (PPM)	PORT-ADD-PWR-DEG-HI (OCH)
CONTBUS-A-18 (EQPT)	HI-TXPOWER (TRUNK)	PORT-ADD-PWR-DEG-LOW (OCH)
CONTBUS-B-18 (EQPT)	ISIS-ADJ-FAIL (OCN)	PROTNA (EQPT)
CONTBUS-IO-A (EQPT)	KBYTE-APS-CHANNEL-FAILURE (OCN)	PROV-MISMATCH (PPM)
CONTBUS-IO-B (EQPT)	LASERBIAS-DEG (AOTS)	PWR-FAIL-A (EQPT)
DATAFLT (NE)	LASERBIAS-DEG (OTS)	PWR-FAIL-B (EQPT)
DUP-IPADDR (NE)	LASEREOL (OCN)	PWR-FAIL-RET-A (EQPT)
DUP-NODENAME (NE)	LASERTEMP-DEG (AOTS)	PWR-FAIL-RET-B (EQPT)
ENVALRM)EXT	LOF (BITS)	SFTWDOWN (EQPT)
EOC (OCN)	LO-LASERBIAS (EQPT)	SH-INS-LOSS-VAR-DEG-HIGH (OTS)
EOC (TRUNK)	LO-LASERBIAS (OCN)	SH-INS-LOSS-VAR-DEG-LOW (OTS)
EOC-L (OCN)	LO-LASERBIAS (PPM)	SNTP-HOST (NE)
EOC-L (TRUNK)	LO-LASERTEMP (EQPT)	SSM-FAIL (BITS)
ERROR-CONFIG (EQPT)	LO-LASERTEMP (OCN)	SSM-FAIL (DS1)
EXCCOL (EQPT)	LO-LASERTEMP (PPM)	SSM-FAIL (E1)
FEPRLF (OCN)	LO-RXPOWER (2R)	SSM-FAIL (OCN)
FIBERTEMP-DEG (AOTS)	LO-RXPOWER (ESCON)	SSM-FAIL (TRUNK)
GAIN-HDEG (AOTS)	LO-RXPOWER (FC)	SYNCPRI (EXT-SREF)
GAIN-LDEG (AOTS)	LO-RXPOWER (GE)	SYNCSEC (EXT-SREF)
GCC-EOC (TRUNK)	LO-RXPOWER (ISC)	SYNCSEC (NE-SREF)
HELLO (OCN)	LO-RXPOWER (OCN)	SYNCTHIRD (EXT-SREF)
HI-LASERBIAS (2R)	LO-RXPOWER (TRUNK)	SYNCTHIRD (NE-SREF)
HI-LASERBIAS (EQPT)	LOS (BITS)	TIM-MON (OCN)
HI-LASERBIAS (ESCON)	LOS (FUDC)	TIM-MON (TRUNK)
HI-LASERBIAS (FC)	LOS (MSUDC)	TIM-P (STSMON)
HI-LASERBIAS (GE)	LOS-O (OCH)	UNREACHABLE-TARGET-POWER (OCH)
HI-LASERBIAS (ISC)	LOS-O (OMS)	VOA-HDEG (AOTS)
HI-LASERBIAS (OCN)	LOS-O (OTS)	VOA-HDEG (OCH)
HI-LASERBIAS (PPM)	LO-TXPOWER (2R)	VOA-HDEG (OMS)
HI-LASERBIAS (TRUNK)	LO-TXPOWER (EQPT)	VOA-HDEG (OTS)
HI-LASERTEMP (EQPT)	LO-TXPOWER (ESCON)	VOA-LDEG (AOTS)
HI-LASERTEMP (OCN)	LO-TXPOWER (FC)	VOA-LDEG (OCH)
HI-LASERTEMP (PPM)	LO-TXPOWER (GE)	VOA-LDEG (OMS)
HI-RXPOWER (2R)	LO-TXPOWER (ISC)	VOA-LDEG (OTS)
HI-RXPOWER (ESCON)	—	—

2.1.4  NA Conditions

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

Table 2-4 ONS 15454 NA Conditions List 

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

2.1.5  NR Conditions

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

Table 2-5 ONS 15454 NR Conditions List 

AIS (BITS)	ERFI-P-CONN (STSMON)	OTUK-AIS (TRUNK)
AIS (DS1)	ERFI-P-CONN (STSTRM)	OTUK-BDI (TRUNK)
AIS (DS3)	ERFI-P-PAYLD (STSMON)	RFI (TRUNK)
AIS (E1)	ERFI-P-PAYLD (STSTRM)	RFI-L (EC1)
AIS (FUDC)	ERFI-P-SRVR (STSMON)	RFI-L (OCN)
AIS (MSUDC)	ERFI-P-SRVR (STSTRM)	RFI-P (STSMON)
AIS (TRUNK)	ODUK-1-AIS-PM (TRUNK)	RFI-P (STSTRM)
AIS-L (EC1)	ODUK-2-AIS-PM (TRUNK)	RFI-V (VT-TERM)
AIS-L (OCN)	ODUK-3-AIS-PM (TRUNK)	ROLL-PEND (STSTRM)
AIS-P (STSMON)	ODUK-4-AIS-PM (TRUNK)	TX-AIS (DS1)
AIS-P (STSTRM)	ODUK-AIS-PM (TRUNK)	TX-AIS (DS3)
AIS-V (VT-MON)	ODUK-BDI-PM (TRUNK)	TX-AIS (E1)
AIS-V (VT-TERM)	ODUK-LCK-PM (TRUNK)	TX-LOF (DS1)
AUTOSW-AIS (STSMON)	ODUK-OCI-PM (TRUNK)	TX-LOF (E1)
AUTOSW-AIS (VT-MON)	—	—

2.2  Alarms and Conditions Listed By Alphabetical Entry

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

Table 2-6 ONS 15454 Alarm and Condition Alphabetical List 

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

2.3  Alarm Logical Objects

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

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

---

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

---

Table 2-7 Alarm Logical Object Type Definitions 

Logical Object	Definition
2R	Reshape and retransmit (used for transponder [TXP] cards).
AICI-AEP	Alarm Interface Controller-International/alarm expansion panel. A combination term that refers to this platform's AIC-I card.
AICI-AIE	Alarm Interface Controller-International/Alarm Interface Extension. A combination term that refers to this platform's AIC-I card.
AOTS	Amplified optical transport section.
BIC	Backplane interface connector.
BITS	Building integrated timing supply incoming references (BITS-1, BITS-2).
BPLANE	The backplane.
CE100T	CE-100T-8 card.
DS1	A DS-1 line on a DS-1 or DS-3 electrical card (DS1-14, DS3N-12E, DS3XM-6, DS3XM-12).
DS3	A DS-3 line on a DS3-12, DS3N-12, DS3-12E, DS3XM-6, DS3XM-12, DS3/EC1-48 card.
E1	An E1 line on a DS1/E1-56 card.
E1000F	An E1000 Ethernet card (E1000-2, E1000-2G).
E100T	An E100 Ethernet card (E100T-12, E100T-G).
EC1	Any EC-1 port (including EC1-12 card ports).
ENVALRM	An environmental alarm port.
EQPT	A card, its physical objects, and its logical objects as they are located in any of the eight noncommon card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signals (STS), and virtual tributaries (VT).
ESCON	Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G.
EXT-SREF	BITS outgoing references (SYNC-BITS1, SYNC-BITS2).
FAN	Fan-tray assembly.
FC	Fibre channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E.
FCMR	An FC_MR-4 Fibre Channel card.
FUDC	SONET F1 byte user data channel for ONS 15454 ML-Series Ethernet cards.
G1000	A G-Series Ethernet card.
GE	Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10G.
GFP-FAC	Generic framing procedure facility port, referring to all MXP and TXP cards.
ISC	Inter-service channel, referring to TXPP_MR_2.5G or TXP_MR_2.5G cards.
ML1000	An ML1000 Ethernet card (ML1000-2).
ML100T	An ML100 Ethernet card (ML100T-12).
MLFX	An ML100X-8 Ethernet card.
MSUDC	Multiplex section user data channel.
NE	The entire network element.
NE-SREF	The timing status of the NE.
OCH	The optical channel, referring to dense wavelength division multiplexing (DWDM) cards.
OCHNC-CONN	The optical channel network connection, referring to DWDM cards.
OCN	An OC-N line on any OC-N card.
OMS	Optical multiplex section.
OSC-RING	Optical service channel ring.
OTS	Optical transport section.
PPM	Pluggable port module (PPM), referring to MXP and TXP cards.
PWR	Power equipment.
STSMON	STS alarm detection at the monitor point (upstream from the cross-connect).
STSTRM	STS alarm detection at termination (downstream from the cross-connect).
TRUNK	The optical or DWDM card carrying the high-speed signal; referring to MXP or TXP cards.
VCG	A virtual concatenation group of VTs.
VT-MON	VT1 alarm detection at the monitor point (upstream from the cross-connect).
VT-TERM	VT1 alarm detection at termination (downstream from the cross-connect).

2.4  Alarm List by Logical Object Type

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

---

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

---

---

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

---

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

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

2.5  DS3-12 E Line Alarms

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

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

Table 2-9 DS3-12E Line Alarms 

Alarm	UNFRAMED	M13	CBIT
LOS (DS1 or DS3)	Yes	Yes	Yes
AIS	Yes	Yes	Yes
LOF (DS1 or DS3)	No	Yes	Yes
FE-IDLE	No	Yes	Yes
RAI	No	Yes	Yes
Terminal Lpbk (LPBKTERMINAL for DS1 or DS3)	Yes	Yes	Yes
Facility Lpbk (LPBKFACILITY for DS1 or DS3)	Yes	Yes	Yes
LPBKDS1FEAC or LPBKDS3FEAC	No	No	Yes
FE Common Equipment Failure-NSA (FE-DS1-NSA or FE-DS3-NSA)	No	No	Yes
FE Equipment Failure-SA (FE-DS3-SA)	No	No	Yes
FE-LOS	No	No	Yes
FE-LOF	No	No	Yes
FE-AIS	No	No	Yes
FE-IDLE	No	No	Yes
FE Equipment Failure-NSA (FE-EQPT-NSA)	No	No	Yes

2.6  Trouble Notifications

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

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

2.6.1  Alarm Characteristics

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

2.6.2  Condition Characteristics

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

For a comprehensive list of all conditions, refer to the Cisco SONET TL1 Command Guide .

2.6.3  Severities

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

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

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

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

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

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

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

2.6.4  Alarm Hierarchy

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

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

Table 2-10 Path Alarm Hierarchy 

Priority	Condition Type
Highest	AIS-P
—	LOP-P
—	UNEQ-P
Lowest	TIM-P

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

Table 2-11 Facility Alarm Hierarchy

Priority	Condition Type
Highest	LOS
—	LOF
—	AIS-L
—	SF-L
—	SD-L
—	RFI-L
—	TIM-S
—	AIS-P
—	LOP-P
—	SF-P
—	SD-P
—	UNEQ-P
—	TIM-P
Lowest	PLM-P

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

Table 2-12 Near-End Alarm Hierarchy

Priority	Condition Type
Highest	LOS
—	LOF
—	AIS-L
—	AIS-P1
—	LOP-P2
—	UNEQ-P
—	TIM-P
—	PLM-P
—	AIS-V1
—	LOP-V2
—	UNEQ-V
—	PLM-V
Lowest	DS-N AIS (if reported for outgoing DS-N signals)

1 Although it is not defined as a defect or failure, all-ones STS pointer relay is also higher priority than LOP-P. Similarly, all-ones VT pointer relay is higher priority than LOP-V. 2 LOP-P is also higher priority than the far-end failure RFI-P, which does not affect the detection of any near-end failures. Similarly, LOP-V is higher priority than RFI-V.

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

Table 2-13 Far-End Alarm Hierarchy

Priority	Condition Type
Highest	RFI-L
—	RFI-P
Lowest	RFI-V

2.6.5  Service Effect

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

2.6.6  States

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

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

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

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

2.7  Safety Summary

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

---

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

---

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

---

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

---

---

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

---

---

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

---

---

Warning Class 1 laser product. Statement 1008

---

---

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

---

---

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

---

2.8  Alarm Procedures

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

---

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

---

---

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

---

2.8.1  AIS

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

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

DWDM Logical Object: TRUNK

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

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

---

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

---

Clear the AIS Condition

---

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

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

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

---

2.8.2  AIS-L

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

SONET Logical Objects: EC1, OCN

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

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

---

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

---

Clear the AIS-L Condition

---

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

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

---

2.8.3  AIS-P

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

SONET Logical Objects: STSMON, STSTRM

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

Clear the AIS-P Condition

---

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

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

---

2.8.4  AIS-V

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

SONET Logical Objects: VT-MON, VT-TERM

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

See the "1.13.2  AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits" section on page 1-141 for more information.

Clear the AIS-V Condition

---

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

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

---

2.8.5  ALS

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

2.8.6  AMPLI-INIT

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

2.8.7  APC-CORRECTION-SKIPPED

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

2.8.8  APC-DISABLED

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

2.8.9  APC-END

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

2.8.10  APC-OUT-OF-RANGE

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

2.8.11  APSB

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

SONET Logical Object: OCN

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

---

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

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

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

---

2.8.12  APSCDFLTK

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

SONET Logical Object: OCN

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

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

Clear the APSCDFLTK Alarm

---

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

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

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

Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" alarm on page 2-81.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide provides procedures for fibering BLSRs.

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

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

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

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

---

2.8.13  APSC-IMP

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

SONET Logical Object: OCN

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

•Unused code in bits 6 through 8 of byte K2.

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

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

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

---

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

---

---

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

---

---

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

---

---

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

---

---

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

---

Clear the APSC-IMP Alarm

---

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

---

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

---

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

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

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

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

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

---

2.8.14  APSCINCON

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

SONET Logical Object: OCN

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

Clear the APSCINCON Alarm

---

Step 1 Look for other alarms, especially the "LOS (OCN)" alarm on page 2-146, the "LOF (OCN)" alarm on page 2-134, or the "AIS" condition on page 2-32. Clearing these alarms clears the APSCINCON alarm.

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

---

2.8.15  APSCM

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

SONET Logical Object: OCN

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

---

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

---

---

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

---

---

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

---

Clear the APSCM Alarm

---

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

---

---

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

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

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

---

2.8.16  APSCNMIS

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

SONET Logical Object: OCN

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

Clear the APSCNMIS Alarm

---

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

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

Step 3 Click Close in the Ring Map dialog box.

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

---

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

---

---

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

---

Step 5 If the alarm does not clear, use the "Initiate a Lockout on a BLSR Protect Span" procedure to lock out the span.

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

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

---

2.8.17  APSIMP

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

SONET Logical Object: OCN

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

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

Clear the APSIMP Alarm

---

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

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

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

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

---

2.8.18  APS-INV-PRIM

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

SONET Logical Object: OCN

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

---

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

---

2.8.19  APSMM

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

SONET Logical Object: OCN

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

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

Clear the APSMM Alarm

---

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

a. Click the Provisioning > Protection tabs.

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

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

c. Click Edit.

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

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

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

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

Step 5 Click Apply.

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

---

2.8.20  APS-PRIM-FAC

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

SONET Logical Object: OCN

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

---

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

---

Clear the APS-PRIM-FAC Condition

---

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

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

---

2.8.21  APS-PRIM-SEC-MISM

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

SONET Logical Object: OCN

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

Clear the APS-PRIM-SEC-MISM Alarm

---

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

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

---

2.8.22  AS-CMD

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

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

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

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

---

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

---

Clear the AS-CMD Condition

---

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

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

•If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with Step 3.

•If the condition is reported against the backplane, go to Step 7.

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

Step 3 Determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:

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

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

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

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

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

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

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

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

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

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

c. Click Apply.

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

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

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

c. Click Apply.

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

---

2.8.23  AS-MT

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

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

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

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

Clear the AS-MT Condition

---

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

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

---

2.8.24  AS-MT-OOG

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

SONET Logical Objects: STSTRM, VT-TERM

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

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

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

2.8.25  AUD-LOG-LOSS

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

SONET Logical Object: NE

The Audit Trail Log Loss condition occurs when the log is 100 percent full and the oldest entries are being replaced while new entries are generated. The log capacity is 640 entries. The log must be off-loaded using the following procedure to make room for more entries.

Clear the AUD-LOG-LOSS Condition

---

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

Step 2 Click Retrieve.

Step 3 Click Archive.

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

Step 5 Enter a name in the File Name field.

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

Step 6 Click Save.

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

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

---

2.8.26  AUD-LOG-LOW

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

SONET Logical Object: NE

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

---

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

---

2.8.27  AU-LOF

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

2.8.28  AUTOLSROFF

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

SONET Logical Object: OCN

DWDM Logical Object: TRUNK

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

---

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

---

---

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

---

---

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

---

Clear the AUTOLSROFF Alarm

---

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

Figure 2-1 Shelf LCD Panel

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

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

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

---

2.8.29  AUTORESET

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

SONET Logical Object: EQPT

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

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

Clear the AUTORESET Alarm

---

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

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

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

---

2.8.30  AUTOSW-AIS

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

SONET Logical Objects: STSMON, VT-MON

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

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

Clear the AUTOSW-AIS Condition

---

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

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

---

2.8.31  AUTOSW-LOP (STSMON)

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

SONET Logical Object: STSMON

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

Clear the AUTOSW-LOP (STSMON) Condition

---

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

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

---

2.8.32  AUTOSW-LOP (VT-MON)

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

SONET Logical Object: VT-MON

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

Clear the AUTOSW-LOP (VT-MON) Condition

---

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

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

---

2.8.33  AUTOSW-PDI

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

SONET Logical Object: STSMON

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

Clear the AUTOSW-PDI Condition

---

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

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

---

2.8.34  AUTOSW-SDBER

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

SONET Logical Object: STSMON

The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade (SD) caused automatic path protection switching to occur. (See the "SD-L" condition on page 2-192.) If the path protection is configured for revertive switching, it reverts to the working path when the SD is resolved.

Clear the AUTOSW-SDBER Condition

---

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

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

---

2.8.35  AUTOSW-SFBER

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

SONET Logical Object: STSMON

The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal failure (SF) caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path when the SF is resolved.

Clear the AUTOSW-SFBER Condition

---

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

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

---

2.8.36  AUTOSW-UNEQ (STSMON)

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

SONET Logical Object: STSMON

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

Clear the AUTOSW-UNEQ (STSMON) Condition

---

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

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

---

2.8.37  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.8.38  AWG-FAIL

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

2.8.39  AWG-OVERTEMP

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

2.8.40  AWG-WARM-UP

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

2.8.41  BAT-FAIL

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

SONET Logical Object: PWR

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

Clear the BAT-FAIL Alarm

---

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

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

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

---

2.8.42  BKUPMEMP

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

SONET Logical Object: EQPT

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

•Flash manager fails to format a flash partition.

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

•Problem at the driver level.

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

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

---

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

---

Clear the BKUPMEMP Alarm

---

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

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

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

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

b. Choose Reset Card from the shortcut menu.

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

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

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

---

2.8.43  BLSROSYNC

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

SONET Logical Object: OCN

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

---

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

---

---

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

---

---

Note This alarm can also be expected when upgrading to Release 6.0 if the ring identifier is updated.

---

Clear the BLSROSYNC Alarm

---

Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 Procedure Guide for cabling information to reestablish the DCC. To verify cable continuity, follow site practices.

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

Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" alarm on page 2-73.

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

---

2.8.44  BLSR-SW-VER-MISM

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

SONET Logical Object: OCN

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

Clear the BLSR-SW-VER-MISM Alarm

---

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

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

---

2.8.45  BPV

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

SONET Logical Object: BITS

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

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

---

Note This alarm is not raised on the TCC2 card.

---

Clear the BPV Alarm

---

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

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

---

2.8.46  CARLOSS (CE100T)

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

SONET Logical Objects: CE100T

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) state. It has to be IS-NR with a circuit or loopback.

---

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

---

Clear the CARLOSS (CE100T) Alarm

---

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

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

---

2.8.47  CARLOSS (E100T, E1000F)

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

SONET Logical Objects: E100T, E1000F

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

The CARLOSS alarm also occurs after a node database is restored. After restoration, the alarm clears in approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP).

---

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

---

Clear the CARLOSS (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 Procedure Guide.

---

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

---

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

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

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

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

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

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

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

An Ethernet manual cross-connect is used when another vendor's equipment sits between ONS 15454 nodes, and the open systems interconnect/target identifier address resolution protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.

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

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

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

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

d. From the examination of the layout of your network, determine which ONS 15454 and card and card are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:

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

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

•Click the Circuits tab.

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

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

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

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

---

2.8.48  CARLOSS (EQPT)

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

SONET Logical Object: EQPT

A Carrier Loss on the LAN Equipment alarm generally occurs on OC-N cards when the ONS 15454 and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the TCC2/TCC2P or the LAN backplane pin connection. This CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the node.

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

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

---

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

---

---

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

---

---

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

---

Clear the CARLOSS (EQPT) Alarm

---

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

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

b. Click the Provisioning > Pluggable Port Modules tabs.

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

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

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

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

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

---

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

---

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

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

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

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

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

---

2.8.49  CARLOSS (FC)

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

2.8.50  CARLOSS (G1000)

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

SONET Logical Object: G1000

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

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

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

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

Refer to the Cisco ONS 15454 Reference Manual for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-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 Procedure Guide.

---

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

---

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

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

Step 4 Verify that optical receive levels are within the normal range. The correct specifications are listed in the "1.14.3  OC-N Card Transmit and Receive Levels" section on page 1-154.

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

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

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

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

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

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

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

---

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

---

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

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

b. Click the Maintenance > Loopback tabs.

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

Step 11 If a loopback was provisioned, complete the "Clear Other Electrical Card, CE-100T-8, or Ethernet Card Loopbacks" procedure.

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

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

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

---

Note An ONS 15454 Ethernet manual cross-connect is used when another vendor's equipment sits between ONS nodes, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.

---

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

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

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

d. Examine the layout of your network and determine which ONS 15454 and card are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect and complete the following substeps:

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

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

•Click the Circuits tab.

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

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

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

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

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

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

---

2.8.51  CARLOSS (GE)

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

2.8.52  CARLOSS (ISC)

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

2.8.53  CARLOSS (ML100T, ML1000, MLFX)

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

SONET Logical Objects: ML100T, ML1000, MLFX

A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-146. The Ethernet port has lost its link and is not receiving a valid signal.

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

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

•Autonegotiation is failing.

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

---

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

---

Clear the CARLOSS (ML100T, ML1000, MLFX) Alarm

---

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

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

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

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

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

Step 6 If the alarm does not clear, complete the "Create the Facility (Line) Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port" procedure on page 1-11 and test the loopback.

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

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

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

---

2.8.54  CARLOSS (TRUNK)

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

2.8.55  CASETEMP-DEG

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

2.8.56  CLDRESTART

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

SONET Logical Object: EQPT

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

Clear the CLDRESTART Condition

---

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

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

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

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

---

2.8.57  COMIOXC

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

SONET Logical Object: EQPT

The Input/Output Slot To Cross-Connect Communication Failure alarm is caused by the XC10G or XC-VXC-10G cross-connect card when there is a communication failure for a traffic slot.

Clear the COMIOXC Alarm

---

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

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

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

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

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

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

---

2.8.58  COMM-FAIL

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

SONET Logical Object: EQPT

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

Clear the COMM-FAIL Alarm

---

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

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

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

---

2.8.59  CONTBUS-A-18

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

SONET Logical Object: EQPT

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

Clear the CONTBUS-A-18 Alarm

---

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

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

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

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

---

2.8.60  CONTBUS-B-18

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

SONET Logical Object: EQPT

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

Clear the CONTBUS-B-18 Alarm

---

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

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

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

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

---

2.8.61  CONTBUS-DISABLED

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

SONET Logical Object: EQPT

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

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

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

---

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

---

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

Clear the CONTBUS-DISABLED Alarm

---

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

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

---

2.8.62  CONTBUS-IO-A

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

SONET Logical Object: EQPT

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

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

Clear the CONTBUS-IO-A Alarm

---

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

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

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

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

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

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

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

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

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

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

---

2.8.63  CONTBUS-IO-B

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

SONET Logical Object: EQPT

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

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

Clear the CONTBUS-IO-B Alarm

---

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

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

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

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

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

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

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

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

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

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

---

2.8.64  CTNEQPT-MISMATCH

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

SONET Logical Object: EQPT

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

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

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

---

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

---

Clear the CTNEQPT-MISMATCH Condition

---

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

a. In node view, click the Inventory tab.

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

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

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

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

---

2.8.65  CTNEQPT-PBPROT

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

SONET Logical Object: EQPT

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

---

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

---

---

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

---

Clear the CTNEQPT-PBPROT Alarm

---

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

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

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

---

Caution Do not physically reseat an active TCC2/TCC2P. Doing so disrupts traffic.

---

Step 2 If not all cards show the alarm, perform a CTC reset on the standby XC10G card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.

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

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

Step 4 If the alarm does not clear, complete the