Cisco ONS 15454 SDH Troubleshooting Guide, Release 8.5.x
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 2.18MB) The complete bookPDF (PDF - 9.94MB) | Feedback

Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Index by Default Severity

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  Not Alarmed Conditions (NA)

2.1.5  Not Reported Conditions (NR)

2.2  Alarms and Conditions Listed By Alphabetical Entry

2.3  Alarm Logical Objects

2.4  Alarm List by Logical Object Type

2.5  Trouble Notifications

2.5.1  Alarm Characteristics

2.5.2  Condition Characteristics

2.5.3  Severities

2.5.4  Alarm Hierarchy

2.5.5  Service Effect

2.5.6  States

2.6  Safety Summary

2.7  Alarm Procedures

2.7.1  AIS

Clear the AIS Condition

2.7.2  AIS-L

2.7.3  ALS

2.7.4  ALS-DISABLED

2.7.5  AMPLI-INIT

2.7.6  APC-CORR-SKIPPED

2.7.7  APC-DISABLED

2.7.8  APC-END

2.7.9  APC-OUT-OF-RANGE

2.7.10  APC-WRONG-GAIN

2.7.11  APSB

Clear the APSB Alarm

2.7.12  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.13  APSC-IMP

Clear the APSC-IMP Alarm

2.7.14  APSCINCON

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

2.7.15  APSCM

Clear the APSCM Alarm

2.7.16  APSCNMIS

Clear the APSCNMIS Alarm

2.7.17  APS-INV-PRIM

2.7.18  APS-PRIM-FAC

2.7.19  APS-PRIM-SEC-MISM

2.7.20  AS-CMD

Clear the AS-CMD Condition

2.7.21  AS-MT

Clear the AS-MT Condition

2.7.22  AS-MT-OOG

Clear the AS-MT-OOG Condition

2.7.23  AU-AIS

Clear the AU-AIS Condition

2.7.24  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.25  AUD-LOG-LOW

2.7.26  AU-LOF

Clear the AU-LOF Alarm

2.7.27  AU-LOP

Clear the AU-LOP Alarm

2.7.28  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.7.29  AUTONEG-RFI

Clear the AUTONEG-RFI Alarm

2.7.30  AUTORESET

Clear the AUTORESET Alarm

2.7.31  AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-SNCP Condition

2.7.32  AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.7.33  AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.7.34  AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.7.35  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

2.7.36  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

2.7.37  AWG-DEG

2.7.38  AWG-FAIL

2.7.39  AWG-OVERTEMP

2.7.40  AWG-WARM-UP

2.7.41  BAT-FAIL

Clear the BATFAIL Alarm

2.7.42  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.43  CARLOSS (CEMR, CE100T, CE1000)

Clear the CARLOSS (CEMR, CE100T, CE1000) Alarm

2.7.44  CARLOSS (E100T, E1000F)

Clear the CARLOSS (E100T, E1000F) Alarm

2.7.45  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.46  CARLOSS (FC)

2.7.47  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.7.48  CARLOSS (GE)

2.7.49  CARLOSS (ISC)

2.7.50  CARLOSS (ML100T, ML1000, MLFX)

Clear the CARLOSS (ML100T, ML1000, MLFX) Alarm

2.7.51  CARLOSS (TRUNK)

2.7.52  CASETEMP-DEG

2.7.53  CLDRESTART

Clear the CLDRESTART Condition

2.7.54  COMIOXC

Clear the COMIOXC Alarm

2.7.55  COMM-FAIL

Clear the COMM-FAIL Alarm

2.7.56  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.57  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.7.58  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.7.59  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.60  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.61  CPP-INCAPABLE

Clear the CPP-INCAPABLE Alarm

2.7.62  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.7.63  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.64  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.65  DATA-CRC

Clear the DATA-CRC Alarm

2.7.66  DATAFLT

Clear the DATAFLT Alarm

2.7.67  DBOSYNC

Clear the DBOSYNC Alarm

2.7.68  DCU-LOSS-FAIL

2.7.69  DISCONNECTED

Clear the DISCONNECTED Alarm

2.7.70  DS3-MISM

Clear the DS3-MISM Condition

2.7.71  DSP-COMM-FAIL

2.7.72  DSP-FAIL

2.7.73  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.74  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.75  DUP-SHELF-ID

2.7.76  EHIBATVG

Clear the EHIBATVG Alarm

2.7.77  ELWBATVG

Clear the ELWBATVG Alarm

2.7.78  RS-EOC

Clear the RS-EOC Alarm

2.7.79  EQPT

Clear the EQPT Alarm

2.7.80  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.7.81  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.82  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.83  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.84  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.7.85  EXCCOL

Clear the EXCCOL Alarm

2.7.86  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.87  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.7.88  EXT

Clear the EXT Alarm

2.7.89  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.90  FAILTOSW

Clear the FAILTOSW Condition

2.7.91  FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.7.92  FAILTOSW-LO

Clear the FAILTOSW-LO Condition

2.7.93  FAILTOSWR

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

2.7.94  FAILTOSWS

Clear the FAILTOSWS Condition

2.7.95  FAN

Clear the FAN Alarm

2.7.96  FAPS

Clear the FAPS Alarm

2.7.97  FAPS-CONFIG-MISMATCH

2.7.98  FC-DE-NES

Clear the FC-DE-NES Alarm

2.7.99  FC-NO-CREDITS

Clear the FC-NO-CREDITS Alarm

2.7.100  FDI

2.7.101  FE-AIS

Clear the FE-AIS Condition

2.7.102  FEC-MISM

2.7.103  FE-E1-MULTLOS

Clear the FE-E1-MULTLOS Condition

2.7.104  FE-E1-NSA

Clear the FE-E1-NSA Condition

2.7.105  FE-E1-SA

Clear the FE-E1-SA Condition

2.7.106  FE-E1-SNGLLOS

Clear the FE-E1-SNGLLOS Condition

2.7.107  FE-E3-NSA

Clear the FE-E3-NSA Condition

2.7.108  FE-E3-SA

Clear the FE-E3-SA Condition

2.7.109  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.110  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.7.111  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.112  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.113  FE-IDLE

2.7.114  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.115  FE-LOF

Clear the FE-LOF Condition

2.7.116  FE-LOS

Clear the FE-LOS Condition

2.7.117  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.7.118  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.119  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.120  FEPRLF

Clear the FEPRLF Alarm on an MS-SPRing

2.7.121  FIBERTEMP-DEG

2.7.122  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.123  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.124  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.125  FP-LINK-LOSS

Clear the FP-LINK-LOSS Condition

2.7.126  FRCDSWTOINT

2.7.127  FRCDSWTOPRI

2.7.128  FRCDSWTOSEC

2.7.129  FRCDSWTOTHIRD

2.7.130  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.131  FSTSYNC

2.7.132  FTA-MISMATCH

2.7.133  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.134  GAIN-HDEG

2.7.135  GAIN-HFAIL

2.7.136  GAIN-LDEG

2.7.137  GAIN-LFAIL

2.7.138  GCC-EOC

2.7.139  GE-OOSYNC

2.7.140  GFP-CSF

Clear the GFP-CSF Alarm

2.7.141  GFP-DE-MISMATCH

Clear the GFP-DE-MISMATCH Alarm

2.7.142  GFP-EX-MISMATCH

Clear the GFP-EX-MISMATCH Alarm

2.7.143  GFP-LFD

Clear the GFP-LFD Alarm

2.7.144  GFP-NO-BUFFERS

Clear the GFP-NO-BUFFERS Alarm

2.7.145  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.7.146  HELLO

Clear the HELLO Alarm

2.7.147  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.148  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.7.149  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.150  HITEMP

Clear the HITEMP Alarm

2.7.151  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.152  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.153  HP-DEG

Clear the HP-DEG Condition

2.7.154  HP-ENCAP-MISMATCH

Clear the HP-ENCAP-MISMATCH Alarm

2.7.155  HP-EXC

Clear the HP-EXC Condition

2.7.156  HP-RFI

Clear the HP-RFI Condition

2.7.157  HP-TIM

Clear the HP-TIM Alarm

2.7.158  HP-UNEQ

Clear the HP-UNEQ Alarm

2.7.159  I-HITEMP

Clear the I-HITEMP Alarm

2.7.160  ILK-FAIL

2.7.161  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.162  INC-ISD

2.7.163  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.7.164  INHSWPR

Clear the INHSWPR Condition

2.7.165  INHSWWKG

Clear the INHSWWKG Condition

2.7.166  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.167  INVMACADR

2.7.168  IOSCFGCOPY

2.7.169  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.7.170  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.171  KBYTE-APS-CHAN-FAIL

Clear the KBYTE-APS-CHAN-FAIL Alarm

2.7.172  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.7.173  LASER-APR

2.7.174  LASERBIAS-DEG

2.7.175  LASERBIAS-FAIL

2.7.176  LASERTEMP-DEG

2.7.177  LCAS-CRC

Clear the LCAS-CRC Condition

2.7.178  LCAS-RX-DNU

Clear the LCAS-RX-DNU Condition

2.7.179  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.7.180  LCAS-RX-GRP-ERR

Clear the LCAS-RX-GRP-ERR Condition

2.7.181  LCAS-TX-ADD

2.7.182  LCAS-TX-DNU

2.7.183  LINK-KEEPALIVE

Clear the LINK-KEEPALIVE Alarm

2.7.184  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.185  LMP-FAIL

Clear the LMP-FAIL Alarm

2.7.186  LMP-SD

Clear the LMP-SD Condition

2.7.187  LMP-SF

Clear the LMP-SF Condition

2.7.188  LMP-UNALLOC

2.7.189  LOA

Clear the LOA Alarm

2.7.190  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.191  LOF (BITS)

Clear the LOF (BITS) Alarm

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

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

2.7.193  LOF (TRUNK)

2.7.194  LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.7.195  LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.7.196  LOM

Clear the LOM Alarm

2.7.197  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.198  LOS (2R)

2.7.199  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.200  LOS (DS1, DS3)

Clear the LOS (DS1, DS3) Alarm

2.7.201  LOS (E1, E3, E4)

Clear the LOS (E1, E3, E4) Alarm

2.7.202  LOS (ESCON)

2.7.203  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.204  LOS (ISC)

2.7.205  LOS (MSUDC)

2.7.206  LOS (OTS)

2.7.207  LOS (STM1E, STMN)

Clear the LOS (STM1E, STMN) Alarm

2.7.208  LOS (TRUNK)

2.7.209  LOS-O

2.7.210  LOS-P (OCH)

2.7.211  LOS-P (OMS, OTS)

2.7.212  LOS-P (TRUNK)

2.7.213  LO-TXPOWER

2.7.214  LPBKCRS

Clear the LPBKCRS Condition

2.7.215  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.216  LPBKDS3FEAC-CMD

2.7.217  LPBKE1FEAC

2.7.218  LPBKE3FEAC

2.7.219  LPBKFACILITY (CEMR, CE100T, CE1000)

Clear the LPBKFACILITY (CEMR, CE100T, CE1000) Condition

2.7.220  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.221  LPBKFACILITY (E1, E3, E4)

Clear the LPBKFACILITY (E1, E3, E4) Condition

2.7.222  LPBKFACILITY (ESCON)

2.7.223  LPBKFACILITY (FC)

2.7.224  LPBKFACILITY (FCMR)

Clear the LPBKFACILITY (FCMR) Condition

2.7.225  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.7.226  LPBKFACILITY (GE)

2.7.227  LPBKFACILITY (ISC)

Clear the LPBKFACILITY Condition

2.7.228  LPBKFACILITY (STM1E, STMN)

Clear the LPBKFACILITY (STM1E, STMN) Condition

2.7.229  LPBKFACILITY (TRUNK)

2.7.230  LPBKTERMINAL (CEMR, CE100T, CE1000)

Clear the LPBKTERMINAL (CEMR, CE100T, CE1000) Condition

2.7.231  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS3) Condition

2.7.232  LPBKTERMINAL (E1, E3, E4)

Clear the LPBKTERMINAL (E1, E3, E4) Condition

2.7.233  LPBKTERMINAL (ESCON)

2.7.234  LPBKTERMINAL (FC)

2.7.235  LPBKTERMINAL (FCMR)

Clear the LPBKTERMINAL (FCMR) Condition

2.7.236  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.7.237  LPBKTERMINAL (GE)

2.7.238  LPBKTERMINAL (ISC)

Clear the LPBKTERMINAL Condition

2.7.239  LPBKTERMINAL (STM1E, STMN)

Clear the LPBKTERMINAL (STM1E, STMN) Condition

2.7.240  LPBKTERMINAL (TRUNK)

2.7.241  LP-DEG

Clear the LP-DEG Condition

2.7.242  LP-ENCAP-MISMATCH

Clear the LP-ENCAP-MISMATCH Alarm

2.7.243  LP-EXC

Clear the LP-EXC Condition

2.7.244  LP-PLM

Clear the LP-PLM Alarm

2.7.245  LP-RFI

Clear the LP-RFI Condition

2.7.246  LP-TIM

Clear the LP-TIM Alarm

2.7.247  LP-UNEQ

Clear the LP-UNEQ Alarm

2.7.248  MAN-REQ

Clear the MAN-REQ Condition

2.7.249  MANRESET

2.7.250  MANSWTOINT

2.7.251  MANSWTOPRI

2.7.252  MANSWTOSEC

2.7.253  MANSWTOTHIRD

2.7.254  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.255  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.256  MAX-STATIONS

Clear the MAX-STATIONS Alarm

2.7.257  MEA (BIC)

2.7.258  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.259  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.260  MEA (PPM)

2.7.261  MEA (SHELF)

2.7.262  MEM-GONE

2.7.263  MEM-LOW

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

Clear the MFGMEM Alarm

2.7.265  MFGMEM (BPLANE, FAN)

Clear the MFGMEM (BPLANE, FAN) Alarm

2.7.266  MS-AIS

Clear the MS-AIS Condition

2.7.267  MS-DEG

Clear the MS-DEG Condition

2.7.268  MS-EOC

Clear the MS-EOC Alarm

2.7.269  MS-EXC

Clear the MS-EXC Condition

2.7.270  MS-RFI

Clear the MS-RFI Condition

2.7.271  MSSP-OOSYNC

Clear the MSSP-OOSYNC Alarm

2.7.272  MSSP-SW-VER-MISM

Clear the MSSP-SW-VER-MISM Alarm

2.7.273  MS-SQUELCH-HP

2.7.274  MS-SQUELCH-LP

2.7.275  MT-OCHNC

2.7.276  NO-CONFIG

Clear the NO-CONFIG Alarm

2.7.277  NON-CISCO-PPM

Clear the NON-CISCO-PPM Condition

2.7.278  NOT-AUTHENTICATED

2.7.279  OCHNC-INC

2.7.280  OCH-TERM-INC

2.7.281  ODUK-1-AIS-PM

2.7.282  ODUK-2-AIS-PM

2.7.283  ODUK-3-AIS-PM

2.7.284  ODUK-4-AIS-PM

2.7.285  ODUK-AIS-PM

2.7.286  ODUK-BDI-PM

2.7.287  ODUK-LCK-PM

2.7.288  ODUK-OCI-PM

2.7.289  ODUK-SD-PM

2.7.290  ODUK-SF-PM

2.7.291  ODUK-TIM-PM

2.7.292  OOU-TPT

Clear the OOT-TPT Condition

2.7.293  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.7.294  OPWR-HDEG

2.7.295  OPWR-HFAIL

2.7.296  OPWR-LDEG

2.7.297  OPWR-LFAIL

2.7.298  OSRION

2.7.299  OTUK-AIS

2.7.300  OTUK-BDI

2.7.301  OTUK-IAE

2.7.302  OTUK-LOF

2.7.303  OTUK-SD

2.7.304  OTUK-SF

2.7.305  OTUK-TIM

2.7.306  OUT-OF-SYNC

2.7.307  PARAM-MISM

2.7.308  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.309  PMI

2.7.310  PORT-FAIL

2.7.311  PORT-MISMATCH

Clear the PORT-MISMATCH Alarm

2.7.312  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.313  PROTNA

Clear the PROTNA Alarm

2.7.314  PROV-MISMATCH

2.7.315  PTIM

2.7.316  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.317  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.318  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.7.319  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-A Alarm

2.7.320  RAI

Clear the RAI Condition

2.7.321  RCVR-MISS

Clear the RCVR-MISS Alarm

2.7.322  RSV-RT-EXCD-RINGLET0

Clear the RSV-RT-EXCD-RINGLET0 Alarm

2.7.323  RSV-RT-EXCD-RINGLET1

Clear the RSV-RT-EXCD-RINGLET1 Alarm

2.7.324  RFI

2.7.325  RFI-L

2.7.326  RFI-V

2.7.327  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.7.328  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.329  RING-SW-EAST

2.7.330  RING-SW-WEST

2.7.331  ROLL

2.7.332  ROLL-PEND

2.7.333  ROUTE-OVERFLOW

Clear the ROUTE-OVERFLOW Condition

2.7.334  RPR-PASSTHR

Clear the RPR-PASSTHR Condition

2.7.335  RPR-PEER-MISS

Clear the RPR-PEER-MISS Condition

2.7.336  RPR-PROT-ACTIVE

Clear the RPR-PROT-ACTIVE Condition

2.7.337  RPR-PROT-CONFIG-MISM

Clear the RPR-PROT-CONFIG-MISM Alarm

2.7.338  RPR-RI-FAIL

Clear the RPR-RI-FAIL Condition

2.7.339  RPR-SD

Clear the RPR-SD Condition

2.7.340  RPR-SF

Clear the RPR-SF Condition

2.7.341  RPR-SPAN-MISMATCH

Clear the RPR-SPAN-MISMATCH Alarm

2.7.342  RPRW

Clear the RPRW Condition

2.7.343  RS-TIM

Clear the RS-TIM Alarm

2.7.344  RUNCFG-SAVENEED

2.7.345  SD (DS1, DS3, E1, E3, E4, STMN)

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

2.7.346  SD (TRUNK)

2.7.347  SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.7.348  SDBER-EXCEED-LO

Clear the SDBER-EXCEED-LO Condition

2.7.349  SD-L

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

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

2.7.351  SF (TRUNK)

2.7.352  SFBER-EXCEED-HO

Clear the SFBER-EXCEED-HO Condition

2.7.353  SFBER-EXCEED-LO

Clear the SFBER-EXCEED-HO Condition

2.7.354  SF-L

2.7.355  SFTWDOWN

2.7.356  SHELF-COMM-FAIL

2.7.357  SH-IL-VAR-DEG-HIGH

2.7.358  SH-IL-VAR-DEG-LOW

2.7.359  SHUTTER-OPEN

2.7.360  SIGLOSS

Clear the SIGLOSS Alarm

2.7.361  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.362  SPANLEN-OUT-OF-RANGE

2.7.363  SPAN-SW-EAST

2.7.364  SPAN-SW-WEST

2.7.365  SQUELCH

Clear the SQUELCH Condition

2.7.366  SQUELCHED

Clear the SQUELCHED Condition

2.7.367  SQM

Clear the SQM Alarm

2.7.368  SSM-DUS

2.7.369  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.370  SSM-LNC

2.7.371  SSM-OFF

2.7.372  SSM-PRC

2.7.373  SSM-PRS

2.7.374  SSM-RES

2.7.375  SSM-SDH-TN

2.7.376  SSM-SETS

2.7.377  SSM-SMC

2.7.378  SSM-ST2

2.7.379  SSM-ST3

2.7.380  SSM-ST3E

2.7.381  SSM-ST4

2.7.382  SSM-STU

Clear the SSM-STU Condition

2.7.383  SSM-TNC

2.7.384  SW-MISMATCH

2.7.385  SWMTXMOD-PROT

Clear the SWMTXMOD-PROT Alarm

2.7.386  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.7.387  SWTOPRI

2.7.388  SWTOSEC

2.7.389  SWTOTHIRD

2.7.390  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.391  SYNCLOSS

Clear the SYNCLOSS Alarm

2.7.392  SYNCPRI

Clear the SYNCPRI Alarm

2.7.393  SYNCSEC

Clear the SYNCSEC Alarm

2.7.394  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.395  SYSBOOT

2.7.396  TEMP-MISM

Clear the TEMP-MISM Condition

2.7.397  TIM

Clear the TIM Alarm

2.7.398  TIM-MON

Clear the TIM-MON Alarm

2.7.399  TPTFAIL (CEMR, CE100T, CE1000)

Clear the TPTFAIL (CEMR, CE100T, CE1000) Alarm

2.7.400  TPTFAIL (FCMR)

Clear the TPTFAIL (FCMR) Alarm

2.7.401  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.7.402  TPTFAIL (ML100T, ML1000, MLFX)

Clear the TPTFAIL (ML100T, ML1000, MLFX) Alarm

2.7.403  TRAIL-SIGNAL-FAIL

2.7.404  TRMT

Clear the TRMT Alarm

2.7.405  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.406  TU-AIS

Clear the TU-AIS Condition

2.7.407  TU-LOP

Clear the TU-LOP Alarm

2.7.408  TX-AIS

Clear the TX-AIS Condition

2.7.409  TX-LOF

Clear the TX-LOF Condition

2.7.410  TX-RAI

Clear the TX-RAI Condition

2.7.411  UNC-WORD

2.7.412  UNQUAL-PPM

Clear the UNQUAL-PPM Condition

2.7.413  UT-COMM-FAIL

2.7.414  UT-FAIL

2.7.415  VCG-DEG

Clear the VCG-DEG Condition

2.7.416  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.417  VOA-HDEG

2.7.418  VOA-HFAIL

2.7.419  VOA-LDEG

2.7.420  VOA-LFAIL

2.7.421  VOLT-MISM

Clear the VOLT-MISM Condition

2.7.422  WKSWPR

Clear the WKSWPR Condition

2.7.423  WTR

2.7.424  WVL-MISMATCH

2.8  Traffic Card LED Activity

2.8.1  Typical Traffic Card LED Activity After Insertion

2.8.2  Typical Traffic Card LED Activity During Reset

2.8.3  Typical Card LED State After Successful Reset

2.8.4  Typical Cross-Connect LED Activity During Side Switch

2.9  Frequently Used Alarm Troubleshooting Procedures

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

Identify an MS-SPRing Ring Name or Node ID Number

Change an MS-SPRing Ring Name

Change an MS-SPRing Node ID Number

Verify Node Visibility for Other Nodes

2.9.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Protection Port Manual Switch Command

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

Initiate a Card or Port Lock On Command

Initiate a Card or Port Lock Out Command

Clear a Card or Port Lock On or Lock Out Command

Initiate a 1:1 Card Switch Command

Initiate a Force Switch for All Circuits on an SNCP Span

Initiate a Manual Switch for All Circuits on an SNCP Span

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

Clear an SNCP Span External Switching Command

Initiate a Force Ring Switch on an MS-SPRing

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

Initiate a Manual Ring Switch on an MS-SPRing

Initiate a Lockout on an MS-SPRing Protect Span

Initiate an Exercise Ring Switch on an MS-SPRing

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

Clear an MS-SPRing External Switching Command

2.9.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Reset an ActiveTCC2/TCC2P Card and Activate the Standby Card

Reset the Standby TCC2/TCC2P Card

Side Switch the Active and Standby Cross-Connect Cards

2.9.4  Physical Card Reseating, Resetting, and Replacement

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

Remove and Reinsert (Reseat) Any Card

Physically Replace a Traffic Card

Physically Replace an In-Service Cross-Connect Card

2.9.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node RS-DCC Terminations

Clear an STM-N Card Facility or Terminal Loopback Circuit

Clear an STM-N Card XC Loopback Circuit

Clear a Non-STM Card Facility or Terminal Loopback Circuit

2.9.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly


Alarm Troubleshooting


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

An alarm's troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

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

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

2.1  Alarm Index by Default Severity

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


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


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


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


2.1.1  Critical Alarms (CR)

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

Table 2-1 ONS 15454 SDH Critical Alarm List 

ILK-FAIL (TRUNK)

MFGMEM (AICI-AEP)

IMPROPRMVL (EQPT)

MFGMEM (AICI-AIE)

AU-LOF (VCTRM-HP)

IMPROPRMVL (PPM)

MFGMEM (BPLANE)

AU-LOP (VCMON-HP)

LINK-KEEPALIVE (ML1000)

MFGMEM (FAN)

AU-LOP (VCTRM-HP)

LINK-KEEPALIVE (ML100T)

MFGMEM (PPM)

AUTOLSROFF (STMN)

LINK-KEEPALIVE (MLFX)

OPWR-HFAIL (AOTS)

AWG-FAIL (OTS)

LINK-KEEPALIVE (MLMR)

OPWR-HFAIL (OCH)

AWG-OVERTEMP (OTS)

LOA (VCG)

OPWR-HFAIL (OMS)

BKUPMEMP (EQPT)

LOF (DS3)

OPWR-HFAIL (OTS)

COMIOXC (EQPT)

LOF (E4)

OPWR-LFAIL (AOTS)

CONTBUS-DISABLED (EQPT)

LOF (STM1E)

OPWR-LFAIL (OCH-TERM)

CTNEQPT-PBPROT (EQPT)

LOF (STMN)

OPWR-LFAIL (OCH)

CTNEQPT-PBWORK (EQPT)

LOF (TRUNK)

OPWR-LFAIL (OMS)

EQPT (AICI-AEP)

LOM (TRUNK)

OPWR-LFAIL (OTS)

EQPT (AICI-AIE)

LOM (VCMON-HP)

OTUK-LOF (TRUNK)

EQPT (EQPT)

LOS (2R)

OTUK-TIM (TRUNK)

EQPT (PPM)

LOS (DS3)

PORT-FAIL (OCH)

EQPT-DIAG (EQPT)

LOS (E3)

EQPT-MISS (FAN)

LOS (E4)

FAN (FAN)

LOS (ESCON)

RS-TIM (STMN)

GAIN-HFAIL (AOTS)

LOS (ISC)

SQM (VCTRM-HP)

GAIN-LFAIL (AOTS)

LOS (OTS)

SWMTXMOD-PROT (EQPT)

GE-OOSYNC (FC)

LOS (STM1E)

SWMTXMOD-WORK (EQPT)

GE-OOSYNC (GE)

LOS (STMN)

TIM (STMN)

GE-OOSYNC (ISC)

LOS (TRUNK)

TIM (TRUNK)

GE-OOSYNC (TRUNK)

LOS-P (OCH)

VOA-HFAIL (AOTS)

HITEMP (NE)

LOS-P (OMS)

VOA-HFAIL (OCH)

HP-ENCAP-MISMATCH (VCTRM-HP)

LOS-P (OTS)

VOA-HFAIL (OMS)

HP-PLM (VCMON-HP)

LOS-P (TRUNK)

VOA-HFAIL (OTS)

HP-PLM (VCTRM-HP)

LP-ENCAP-MISMATCH (VCTRM-LP)

VOA-LFAIL (AOTS)

HP-TIM (VCTRM-HP)

MEA (BIC)

VOA-LFAIL (OCH)

HP-UNEQ (VCMON-HP)

MEA (EQPT)

VOA-LFAIL (OMS)

HP-UNEQ (VCTRM-HP)

MEA (FAN)

VOA-LFAIL (OTS)

I-HITEMP (NE)

MEA (PPM)


2.1.2  Major Alarms (MJ)

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

Table 2-2 ONS 15454 SDH Major Alarm List 

APSCNMIS (STMN)

GFP-EX-MISMATCH (FCMR)

RCVR-MISS (DS1)

AUTONEG-RFI (ML1000)

GFP-EX-MISMATCH (GFP-FAC)

RCVR-MISS (E1)

BAT-FAIL (PWR)

GFP-LFD (CE1000)

RSV-RT-EXCD-RINGLET0 (RPRIF)

CARLOSS (CE1000)

GFP-LFD (CE100T)

RSV-RT-EXCD-RINGLET1 (RPRIF)

CARLOSS (CE100T)

GFP-LFD (CEMR)

RING-ID-MIS (OSC-RING)

CARLOSS (CEMR)

GFP-LFD (FCMR)

RING-ID-MIS (STMN)

CARLOSS (E1000F)

GFP-LFD (GFP-FAC)

RING-MISMATCH (STMN)

CARLOSS (E100T)

GFP-LFD (ML1000)

RPR-PEER-MISS (RPRIF)

CARLOSS (EQPT)

GFP-LFD (ML100T)

RPR-PROT-CONFIG-MISM (RPRIF)

CARLOSS (FC)

GFP-LFD (MLFX)

RPR-RI-FAIL (RPRIF)

CARLOSS (G1000)

GFP-LFD (MLMR)

RPR-SPAN-MISMATCH (ML1000)

CARLOSS (GE)

GFP-NO-BUFFERS (FCMR)

RPR-SPAN-MISMATCH (ML100T)

CARLOSS (ISC)

GFP-NO-BUFFERS (GFP-FAC)

RPR-SPAN-MISMATCH (MLFX)

CARLOSS (ML1000)

GFP-UP-MISMATCH (CE1000)

RPR-SPAN-MISMATCH (MLMR)

CARLOSS (ML100T)

GFP-UP-MISMATCH (CE100T)

SHELF-COMM-FAIL (SHELF)

CARLOSS (MLFX)

GFP-UP-MISMATCH (CEMR)

SIGLOSS (ESCON)

CARLOSS (MLMR)

GFP-UP-MISMATCH (FCMR)

SIGLOSS (FC)

CARLOSS (TRUNK)

GFP-UP-MISMATCH (GFP-FAC)

SIGLOSS (FCMR)

DATA-CRC (CE100T)

GFP-UP-MISMATCH (ML1000)

SIGLOSS (GE)

DATA-CRC (ML1000)

GFP-UP-MISMATCH (ML100T)

SIGLOSS (ISC)

DATA-CRC (ML100T)

GFP-UP-MISMATCH (MLFX)

SIGLOSS (TRUNK)

DATA-CRC (MLFX)

GFP-UP-MISMATCH (MLMR)

SQM (VCTRM-LP)

DBOSYNC (NE)

INVMACADR (BPLANE)

SYNCLOSS (FC)

DSP-COMM-FAIL (TRUNK)

LASERBIAS-FAIL (AOTS)

SYNCLOSS (FCMR)

DSP-FAIL (TRUNK)

LOF (DS1)

SYNCLOSS (GE)

DUP-SHELF-ID (SHELF)

LOF (E1)

SYNCLOSS (ISC)

EHIBATVG (PWR)

LOM (VCTRM-HP)

SYNCLOSS (TRUNK)

ELWBATVG (PWR)

LOM (VCTRM-LP)

SYNCPRI (NE-SREF)

E-W-MISMATCH (STMN)

LOS (DS1)

SYSBOOT (NE)

EXTRA-TRAF-PREEMPT (STMN)

LOS (E1)

TIM (STM1E)

FC-DE-NES (FC)

LP-PLM (VCMON-LP)

TPTFAIL (CE1000)

FC-DE-NES (FCMR)

LP-PLM (VCTRM-LP)

TPTFAIL (CE100T)

FC-DE-NES (TRUNK)

LP-TIM (VCMON-LP)

TPTFAIL (CEMR)

FC-NO-CREDITS (FC)

LP-TIM (VCTRM-LP)

TPTFAIL (FCMR)

FC-NO-CREDITS (FCMR)

LP-UNEQ (VCMON-LP)

TPTFAIL (G1000)

FC-NO-CREDITS (TRUNK)

LP-UNEQ (VCTRM-LP)

TPTFAIL (ML1000)

FEC-MISM (TRUNK)

MAX-STATIONS (RPRIF)

TPTFAIL (ML100T)

GFP-CSF (CE1000)

MEA (SHELF)

TPTFAIL (MLFX)

GFP-CSF (CE100T)

MEM-GONE (EQPT)

TPTFAIL (MLMR)

GFP-CSF (CEMR)

MSSP-OOSYNC (STMN)

TRMT (DS1)

GFP-CSF (FCMR)

ODUK-TIM-PM (TRUNK)

TRMT (E1)

GFP-CSF (GFP-FAC)

OUT-OF-SYNC (FC)

TRMT-MISS (DS1)

GFP-CSF (ML1000)

OUT-OF-SYNC (GE)

TRMT-MISS (E1)

GFP-CSF (ML100T)

OUT-OF-SYNC (TRUNK)

TU-LOP (VCMON-LP)

GFP-CSF (MLFX)

PORT-MISMATCH (CEMR)

TU-LOP (VCTRM-LP)

GFP-CSF (MLMR)

PORT-MISMATCH (MLMR)

UT-COMM-FAIL (TRUNK)

GFP-DE-MISMATCH (FCMR)

PRC-DUPID (STMN)

UT-FAIL (TRUNK)

GFP-DE-MISMATCH (GFP-FAC)

PROV-MISMATCH (TRUNK)

WVL-MISMATCH (TRUNK)

GFP-EX-MISMATCH (CE1000)

PTIM (TRUNK)


2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15454 SDH Minor Alarm List 

HI-LASERTEMP (STMN)

LO-TXPOWER (ESCON)

HI-RXPOWER (2R)

LO-TXPOWER (FC)

APC-CORR-SKIPPED (AOTS)

HI-RXPOWER (ESCON)

LO-TXPOWER (GE)

APC-CORR-SKIPPED (OCH)

HI-RXPOWER (FC)

LO-TXPOWER (ISC)

APC-CORR-SKIPPED (OMS)

HI-RXPOWER (GE)

LO-TXPOWER (PPM)

APC-CORR-SKIPPED (OTS)

HI-RXPOWER (ISC)

LO-TXPOWER (STMN)

APC-OUT-OF-RANGE (AOTS)

HI-RXPOWER (STMN)

LO-TXPOWER (TRUNK)

APC-OUT-OF-RANGE (OCH)

HI-RXPOWER (TRUNK)

MEM-LOW (EQPT)

APC-OUT-OF-RANGE (OMS)

HITEMP (EQPT)

MS-EOC (STMN)

APC-OUT-OF-RANGE (OTS)

HI-TXPOWER (2R)

MSSP-SW-VER-MISM (STMN)

APSB (STMN)

HI-TXPOWER (EQPT)

OPWR-HDEG (AOTS)

APSCDFLTK (STMN)

HI-TXPOWER (ESCON)

OPWR-HDEG (OCH-TERM)

APSC-IMP (STMN)

HI-TXPOWER (FC)

OPWR-HDEG (OCH)

APSCINCON (STMN)

HI-TXPOWER (GE)

OPWR-HDEG (OMS)

APSCM (STMN)

HI-TXPOWER (ISC)

OPWR-HDEG (OTS)

APSIMP (STMN)

HI-TXPOWER (PPM)

OPWR-LDEG (AOTS)

APS-INV-PRIM (STMN)

HI-TXPOWER (STMN)

OPWR-LDEG (OCH-TERM)

APS-PRIM-SEC-MISM (STMN)

HI-TXPOWER (TRUNK)

OPWR-LDEG (OCH)

AUTORESET (EQPT)

HP-TIM (VCMON-HP)

OPWR-LDEG (OMS)

AWG-DEG (OTS)

ISIS-ADJ-FAIL (STMN)

OPWR-LDEG (OTS)

CASETEMP-DEG (AOTS)

ISIS-ADJ-FAIL (TRUNK)

OTUK-IAE (TRUNK)

COMM-FAIL (EQPT)

KBYTE-APS-CHAN-FAIL (STMN)

PEER-NORESPONSE (MLMR)

CONTBUS-A-18 (EQPT)

LASERBIAS-DEG (AOTS)

PROTNA (EQPT)

CONTBUS-B-18 (EQPT)

LASERBIAS-DEG (OTS)

PROV-MISMATCH (PPM)

CONTBUS-IO-A (EQPT)

LASERTEMP-DEG (AOTS)

PWR-FAIL-A (EQPT)

CONTBUS-IO-B (EQPT)

LMP-FAIL (CTRL)

PWR-FAIL-B (EQPT)

DATAFLT (NE)

LMP-FAIL (GE)

PWR-FAIL-RET-A (EQPT)

DCU-LOSS-FAIL (OTS)

LMP-FAIL (STMN)

PWR-FAIL-RET-B (EQPT)

DUP-IPADDR (NE)

LMP-FAIL (TLINK)

ROUTE-OVERFLOW (NSA)

DUP-NODENAME (NE)

LMP-SD (GE)

RS-EOC (STMN)

RS-EOC (TRUNK)

LMP-SD (STMN)

SFTWDOWN (EQPT)

EOC-L (TRUNK)

LMP-SF (GE)

SH-IL-VAR-DEG-HIGH (OTS)

ERROR-CONFIG (EQPT)

LMP-SF (STMN)

SH-IL-VAR-DEG-LOW (OTS)

EXCCOL (EQPT)

LOF (BITS)

SNTP-HOST (NE)

EXT (ENVALRM)

LO-LASERBIAS (EQPT)

SPANLEN-OUT-OF-RANGE (OTS)

FAPS-CONFIG-MISMATCH (EQPT)

LO-LASERBIAS (PPM)

SSM-FAIL (BITS)

FEPRLF (STMN)

LO-LASERBIAS (STMN)

SSM-FAIL (E1)

FIBERTEMP-DEG (AOTS)

LO-LASERTEMP (EQPT)

SSM-FAIL (STMN)

FP-LINK-LOSS (EQPT)

LO-LASERTEMP (PPM)

SSM-FAIL (TRUNK)

GAIN-HDEG (AOTS)

LO-LASERTEMP (STMN)

SYNCPRI (EXT-SREF)

GAIN-LDEG (AOTS)

LO-RXPOWER (2R)

SYNCSEC (EXT-SREF)

GCC-EOC (TRUNK)

LO-RXPOWER (ESCON)

SYNCSEC (NE-SREF)

HELLO (STMN)

LO-RXPOWER (FC)

SYNCTHIRD (EXT-SREF)

HELLO (TRUNK)

LO-RXPOWER (GE)

SYNCTHIRD (NE-SREF)

HI-LASERBIAS (2R)

LO-RXPOWER (ISC)

TIM-MON (STMN)

HI-LASERBIAS (EQPT)

LO-RXPOWER (STMN)

TIM-MON (TRUNK)

HI-LASERBIAS (ESCON)

LO-RXPOWER (TRUNK)

VOA-HDEG (AOTS)

HI-LASERBIAS (FC)

LOS (BITS)

VOA-HDEG (OCH)

HI-LASERBIAS (GE)

LOS (FUDC)

VOA-HDEG (OMS)

HI-LASERBIAS (ISC)

LOS (MSUDC)

VOA-HDEG (OTS)

HI-LASERBIAS (PPM)

LOS-O (OCH)

VOA-LDEG (AOTS)

HI-LASERBIAS (STMN)

LOS-O (OMS)

VOA-LDEG (OCH)

HI-LASERBIAS (TRUNK)

LOS-O (OTS)

VOA-LDEG (OMS)

HI-LASERTEMP (EQPT)

LO-TXPOWER (2R)

VOA-LDEG (OTS)

HI-LASERTEMP (PPM)

LO-TXPOWER (EQPT)


2.1.4  Not Alarmed Conditions (NA)

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

Table 2-4 ONS 15454 SDH Not Alarmed Conditions List 

ALS (2R)

FORCED-REQ-SPAN (GE)

PARAM-MISM (OCH-TERM)

ALS (AOTS)

FORCED-REQ-SPAN (ISC)

PARAM-MISM (OCH)

ALS (ESCON)

LPBKFACILITY (DS1)

PARAM-MISM (OMS)

ALS (FC)

FORCED-REQ-SPAN (STMN)

PARAM-MISM (OTS)

ALS (GE)

FORCED-REQ-SPAN (TRUNK)

PMI (OMS)

ALS (ISC)

FRCDSWTOINT (NE-SREF)

PMI (OTS)

ALS (STMN)

FRCDSWTOPRI (EXT-SREF)

PORT-MISMATCH (FCMR)

ALS (TRUNK)

FRCDSWTOPRI (NE-SREF)

RAI (DS1)

ALS-DISABLED (EQPT)

FRCDSWTOSEC (EXT-SREF)

RAI (DS3)

AMPLI-INIT (AOTS)

FRCDSWTOSEC (NE-SREF)

RAI (E1)

APC-DISABLED (AOTS)

FRCDSWTOTHIRD (EXT-SREF)

RING-SW-EAST (STMN)

APC-DISABLED (EQPT)

FRCDSWTOTHIRD (NE-SREF)

RING-SW-WEST (STMN)

APC-DISABLED (NE)

FRNGSYNC (NE-SREF)

ROLL (VCMON-HP)

APC-DISABLED (OCH)

FSTSYNC (NE-SREF)

ROLL (VCMON-LP)

APC-DISABLED (OMS)

FTA-MISMATCH (EQPT)

ROLL (VCTRM-HP)

APC-DISABLED (OTS)

FULLPASSTHR-BI (STMN)

ROLL (VCTRM-LP)

APC-DISABLED (SHELF)

HLDOVRSYNC (NE-SREF)

ROLL-PEND (VCMON-HP)

APC-END (NE)

HP-DEG (VCMON-HP)

ROLL-PEND (VCMON-LP)

APC-WRONG-GAIN (AOTS)

HP-DEG (VCTRM-HP)

ROLL-PEND (VCTRM-LP)

APS-PRIM-FAC (STMN)

HP-EXC (VCMON-HP)

RPR-PASSTHR (RPRIF)

AS-CMD (2R)

HP-EXC (VCTRM-HP)

RPR-PROT-ACTIVE (RPRIF)

AS-CMD (AOTS)

IDLE (DS1)

RPR-SD (ML1000)

AS-CMD (BPLANE)

INC-ISD (DS3)

RPR-SD (ML100T)

AS-CMD (CE1000)

INC-ISD (E3)

RPR-SD (MLFX)

AS-CMD (CE100T)

INHSWPR (EQPT)

RPR-SD (MLMR)

AS-CMD (CEMR)

INHSWWKG (EQPT)

RPR-SF (ML1000)

AS-CMD (DS1)

INTRUSION-PSWD (NE)

RPR-SF (ML100T)

AS-CMD (DS3)

IOSCFGCOPY (EQPT)

RPR-SF (MLFX)

AS-CMD (E1000F)

KB-PASSTHR (STMN)

RPR-SF (MLMR)

AS-CMD (E100T)

LAN-POL-REV (NE)

RPRW (ML1000)

AS-CMD (E1)

LASER-APR (AOTS)

RPRW (ML100T)

AS-CMD (E3)

LCAS-CRC (VCTRM-HP)

RPRW (MLFX)

AS-CMD (E4)

LCAS-CRC (VCTRM-LP)

RUNCFG-SAVENEED (EQPT)

AS-CMD (EQPT)

LCAS-RX-DNU (VCTRM-HP)

SD (DS1)

AS-CMD (ESCON)

LCAS-RX-DNU (VCTRM-LP)

SD (DS3)

AS-CMD (FC)

LCAS-RX-FAIL (VCTRM-HP)

SD (STM1E)

AS-CMD (FCMR)

LCAS-RX-FAIL (VCTRM-LP)

SD (TRUNK)

AS-CMD (G1000)

LCAS-RX-GRP-ERR (VCTRM-HP)

SD-L (TRUNK)

AS-CMD (GE)

LCAS-RX-GRP-ERR (VCTRM-LP)

SF (DS1)

AS-CMD (GFP-FAC)

LCAS-TX-ADD (VCTRM-HP)

SF (DS3)

AS-CMD (ISC)

LCAS-TX-ADD (VCTRM-LP)

SF (TRUNK)

AS-CMD (ML1000)

LCAS-TX-DNU (VCTRM-HP)

SF-L (TRUNK)

AS-CMD (ML100T)

LCAS-TX-DNU (VCTRM-LP)

SHUTTER-OPEN (OTS)

AS-CMD (MLFX)

LKOUTPR-S (STMN)

SPAN-NOT-MEASURED (OTS)

AS-CMD (MLMR)

LMP-UNALLOC (GE)

SPAN-SW-EAST (STMN)

AS-CMD (NE)

LMP-UNALLOC (STMN)

SPAN-SW-WEST (STMN)

AS-CMD (OCH)

LOCKOUT-REQ (2R)

SQUELCH (STMN)

AS-CMD (OMS)

LOCKOUT-REQ (EQPT)

SQUELCHED (2R)

AS-CMD (OTS)

LOCKOUT-REQ (ESCON)

SQUELCHED (ESCON)

AS-CMD (PPM)

LOCKOUT-REQ (FC)

SQUELCHED (FC)

AS-CMD (PWR)

LOCKOUT-REQ (GE)

SQUELCHED (GE)

AS-CMD (SHELF)

LOCKOUT-REQ (ISC)

SQUELCHED (ISC)

AS-CMD (STM1E)

LOCKOUT-REQ (STMN)

SQUELCHED (STMN)

AS-CMD (STMN)

LOCKOUT-REQ (TRUNK)

SQUELCHED (TRUNK)

AS-CMD (TRUNK)

LOCKOUT-REQ (VCMON-HP)

SSM-DUS (BITS)

AS-MT (2R)

LOCKOUT-REQ (VCMON-LP)

SSM-DUS (DS1)

AS-MT (AOTS)

LPBKCRS (VCMON-HP)

SSM-DUS (E1)

AS-MT (CE1000)

LPBKCRS (VCTRM-HP)

SSM-DUS (STMN)

AS-MT (CE100T)

LPBKDS1FE-CMD (DS1)

SSM-DUS (TRUNK)

AS-MT (CEMR)

LPBKDS3FEAC (DS3)

SSM-LNC (BITS)

AS-MT (DS1)

LPBKDS3FEAC-CMD (DS3)

SSM-LNC (NE-SREF)

AS-MT (DS3)

LPBKDS3FEAC-CMD (E3)

SSM-LNC (STMN)

AS-MT (E1)

LPBKE1FEAC (E3)

SSM-LNC (TRUNK)

AS-MT (E3)

LPBKE3FEAC (E3)

SSM-OFF (BITS)

AS-MT (E4)

LPBKFACILITY (CE1000)

SSM-OFF (DS1)

AS-MT (EQPT)

LPBKFACILITY (CE100T)

SSM-OFF (E1)

AS-MT (ESCON)

LPBKFACILITY (CEMR)

SSM-OFF (STMN)

AS-MT (FC)

LPBKFACILITY (DS3)

SSM-OFF (TRUNK)

AS-MT (FCMR)

LPBKFACILITY (E1)

SSM-PRC (BITS)

AS-MT (G1000)

LPBKFACILITY (E3)

SSM-PRC (NE-SREF)

AS-MT (GE)

LPBKFACILITY (E4)

SSM-PRC (STMN)

AS-MT (GFP-FAC)

LPBKFACILITY (ESCON)

SSM-PRC (TRUNK)

AS-MT (ISC)

LPBKFACILITY (FC)

SSM-PRS (E1)

AS-MT (ML1000)

LPBKFACILITY (FCMR)

SSM-PRS (TRUNK)

AS-MT (ML100T)

LPBKFACILITY (G1000)

SSM-RES (DS1)

AS-MT (MLFX)

LPBKFACILITY (GE)

SSM-RES (E1)

AS-MT (MLMR)

LPBKFACILITY (ISC)

SSM-RES (TRUNK)

AS-MT (OCH)

LPBKFACILITY (MLMR)

SSM-SDH-TN (BITS)

AS-MT (OMS)

LPBKFACILITY (STM1E)

SSM-SDH-TN (NE-SREF)

AS-MT (OTS)

LPBKFACILITY (STMN)

SSM-SDH-TN (STMN)

AS-MT (PPM)

LPBKFACILITY (TRUNK)

SSM-SDH-TN (TRUNK)

AS-MT (SHELF)

LPBKTERMINAL (CE1000)

SSM-SETS (BITS)

AS-MT (STM1E)

LPBKTERMINAL (CE100T)

SSM-SETS (NE-SREF)

AS-MT (STMN)

LPBKTERMINAL (CEMR)

SSM-SETS (STMN)

AS-MT (TRUNK)

LPBKTERMINAL (DS1)

SSM-SETS (TRUNK)

AS-MT-OOG (VCTRM-HP)

LPBKTERMINAL (DS3)

SSM-SMC (E1)

AS-MT-OOG (VCTRM-LP)

LPBKTERMINAL (E1)

SSM-SMC (TRUNK)

AUD-LOG-LOSS (NE)

LPBKTERMINAL (E3)

SSM-ST2 (E1)

AUD-LOG-LOW (NE)

LPBKTERMINAL (E4)

SSM-ST2 (TRUNK)

AUTOSW-LOP-SNCP (VCMON-HP)

LPBKTERMINAL (ESCON)

SSM-ST3 (E1)

AUTOSW-LOP-SNCP (VCMON-LP)

LPBKTERMINAL (FC)

SSM-ST3 (TRUNK)

LPBKTERMINAL (FCMR)

SSM-ST3E (E1)

LPBKTERMINAL (G1000)

SSM-ST3E (TRUNK)

AUTOSW-SDBER-SNCP (VCMON-HP)

LPBKTERMINAL (GE)

SSM-ST4 (DS1)

AUTOSW-SDBER-SNCP (VCMON-LP)

LPBKTERMINAL (ISC)

SSM-ST4 (E1)

AUTOSW-SFBER-SNCP (VCMON-HP)

LPBKTERMINAL (MLMR)

SSM-ST4 (STMN)

AUTOSW-SFBER-SNCP (VCMON-LP)

LPBKTERMINAL (STM1E)

SSM-ST4 (TRUNK)

AUTOSW-UNEQ-SNCP (VCMON-HP)

LPBKTERMINAL (STMN)

SSM-STU (BITS)

AUTOSW-UNEQ-SNCP (VCMON-LP)

LPBKTERMINAL (TRUNK)

SSM-STU (E1)

AWG-WARM-UP (OTS)

LP-DEG (VCMON-LP)

SSM-STU (NE-SREF)

CLDRESTART (EQPT)

LP-DEG (VCTRM-LP)

SSM-STU (STMN)

CPP-INCAPABLE (MLMR)

LP-EXC (VCMON-LP)

SSM-STU (TRUNK)

CTNEQPT-MISMATCH (EQPT)

LP-EXC (VCTRM-LP)

SSM-TNC (NE-SREF)

DS3-MISM (DS3)

MAN-REQ (EQPT)

SSM-TNC (STMN)

ETH-LINKLOSS (NE)

MAN-REQ (ML1000)

SSM-TNC (TRUNK)

EXERCISE-RING-FAIL (STMN)

MAN-REQ (ML100T)

SW-MISMATCH (EQPT)

EXERCISE-SPAN-FAIL (STMN)

MAN-REQ (MLFX)

SWTOPRI (EXT-SREF)

FAILTOSW (2R)

MAN-REQ (MLMR)

SWTOPRI (NE-SREF)

FAILTOSW (EQPT)

MAN-REQ (VCMON-HP)

SWTOSEC (EXT-SREF)

FAILTOSW (ESCON)

MAN-REQ (VCMON-LP)

SWTOSEC (NE-SREF)

FAILTOSW (FC)

MANRESET (EQPT)

SWTOTHIRD (EXT-SREF)

FAILTOSW (GE)

MANSWTOINT (NE-SREF)

SWTOTHIRD (NE-SREF)

FAILTOSW (ISC)

MANSWTOPRI (EXT-SREF)

SYNC-FREQ (DS1)

FAILTOSW (STMN)

MANSWTOPRI (NE-SREF)

SYNC-FREQ (E1)

FAILTOSW (TRUNK)

MANSWTOSEC (EXT-SREF)

SYNC-FREQ (STMN)

FAILTOSW-PATH (VCMON-HP)

MANSWTOSEC (NE-SREF)

SYNC-FREQ (TRUNK)

FAILTOSW-PATH (VCMON-LP)

MANSWTOTHIRD (EXT-SREF)

TEMP-MISM (NE)

FAILTOSWR (STMN)

MANSWTOTHIRD (NE-SREF)

TRAIL-SIGNAL-FAIL (OCH)

FAILTOSWS (STMN)

MANUAL-REQ-RING (STMN)

TRAIL-SIGNAL-FAIL (TRUNK)

FAPS (FCMR)

MANUAL-REQ-SPAN (2R)

TX-IDLE (DS1)

FAPS (TRUNK)

MANUAL-REQ-SPAN (ESCON)

TX-RAI (DS1)

FDI (OCH-TERM)

MANUAL-REQ-SPAN (FC)

TX-RAI (E1)

FDI (OCH)

MANUAL-REQ-SPAN (GE)

TX-RAI (E3)

FE-AIS (E3)

MANUAL-REQ-SPAN (ISC)

UNC-WORD (TRUNK)

FE-E1-MULTLOS (E3)

MANUAL-REQ-SPAN (STMN)

VCG-DEG (VCG)

FE-E1-NSA (E3)

MANUAL-REQ-SPAN (TRUNK)

VCG-DOWN (VCG)

FE-E1-SA (E3)

MS-DEG (E1)

VOLT-MISM (PWR)

FE-E1-SNGLLOS (E3)

MS-DEG (E3)

WKSWPR (2R)

FE-E3-NSA (E3)

MS-DEG (E4)

WKSWPR (EQPT)

FE-E3-SA (E3)

MS-DEG (STM1E)

WKSWPR (ESCON)

FE-EQPT-NSA (E3)

MS-DEG (STMN)

WKSWPR (FC)

FE-FRCDWKSWBK-SPAN (STMN)

MS-EXC (E1)

WKSWPR (GE)

FE-FRCDWKSWPR-RING (STMN)

MS-EXC (E3)

WKSWPR (ISC)

FE-FRCDWKSWPR-SPAN (STMN)

MS-EXC (E4)

WKSWPR (STMN)

FE-IDLE (E3)

MS-EXC (STM1E)

WKSWPR (VCMON-HP)

FE-LOCKOUTOFPR-SPAN (STMN)

MS-EXC (STMN)

WKSWPR (VCMON-LP)

FE-LOF (E3)

MS-SQUELCH-HP (STMN)

WTR (2R)

FE-LOS (E3)

MS-SQUELCH-LP (STMN)

WTR (EQPT)

FE-MANWKSWBK-SPAN (STMN)

MT-OCHNC (OTS)

WTR (ESCON)

FE-MANWKSWPR-RING (STMN)

NO-CONFIG (EQPT)

WTR (FC)

FE-MANWKSWPR-SPAN (STMN)

OCHNC-INC (OCHNC-CONN)

WTR (GE)

FORCED-REQ (EQPT)

OCHTERM-INC (OCH-TERM)

WTR (ISC)

FORCED-REQ (ML1000)

ODUK-SD-PM (TRUNK)

WTR (ML1000)

FORCED-REQ (ML100T)

ODUK-SF-PM (TRUNK)

WTR (ML100T)

FORCED-REQ (MLFX)

OOU-TPT (VCTRM-HP)

WTR (MLFX)

FORCED-REQ (MLMR)

OOU-TPT (VCTRM-LP)

WTR (MLMR)

FORCED-REQ (VCMON-HP)

OSRION (AOTS)

WTR (STMN)

FORCED-REQ (VCMON-LP)

OSRION (OTS)

WTR (TRUNK)

FORCED-REQ-RING (STMN)

OTUK-SD (TRUNK)

WTR (VCMON-HP)

FORCED-REQ-SPAN (2R)

OTUK-SF (TRUNK)

WTR (VCMON-LP)

FORCED-REQ-SPAN (ESCON)

OUT-OF-SYNC (ISC)

FORCED-REQ-SPAN (FC)

PARAM-MISM (AOTS)


2.1.5  Not Reported Conditions (NR)

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

Table 2-5 ONS 15454 SDH Not Reported Conditions List 

AIS (BITS)

HP-RFI (VCTRM-HP)

ODUK-OCI-PM (TRUNK)

AIS (DS1)

LP-RFI (VCMON-LP)

OTUK-AIS (TRUNK)

AIS (DS3)

LP-RFI (VCTRM-LP)

OTUK-BDI (TRUNK)

AIS (E1)

MS-AIS (STM1E)

RFI (TRUNK)

AIS (E3)

MS-AIS (STMN)

RFI-L (TRUNK)

AIS (E4)

MS-RFI (STM1E)

ROLL-PEND (VCTRM-HP)

AIS (FUDC)

MS-RFI (STMN)

TU-AIS (VCMON-LP)

AIS (MSUDC)

NON-CISCO-PPM (PPM)

TU-AIS (VCTRM-LP)

AIS (TRUNK)

ODUK-1-AIS-PM (TRUNK)

TX-AIS (DS1)

AIS-L (TRUNK)

ODUK-2-AIS-PM (TRUNK)

TX-AIS (DS3)

AU-AIS (VCMON-HP)

ODUK-3-AIS-PM (TRUNK)

TX-AIS (E1)

AU-AIS (VCTRM-HP)

ODUK-4-AIS-PM (TRUNK)

TX-AIS (E3)

AUTOSW-AIS-SNCP (VCMON-HP)

ODUK-AIS-PM (TRUNK)

TX-LOF (DS1)

AUTOSW-AIS-SNCP (VCMON-LP)

ODUK-BDI-PM (TRUNK)

TX-LOF (E1)

HP-RFI (VCMON-HP)

ODUK-LCK-PM (TRUNK)

UNQUAL-PPM (PPM)


2.2  Alarms and Conditions Listed By Alphabetical Entry

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

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

GFP-LFD (FCMR)

ODUK-OCI-PM (TRUNK)

GFP-LFD (GFP-FAC)

ODUK-SD-PM (TRUNK)

GFP-LFD (ML1000)

ODUK-SF-PM (TRUNK)

GFP-LFD (ML100T)

ODUK-TIM-PM (TRUNK)

AIS (BITS)

GFP-LFD (MLFX)

OOU-TPT (VCTRM-HP)

AIS (DS1)

GFP-LFD (MLMR)

OOU-TPT (VCTRM-LP)

AIS (DS3)

GFP-NO-BUFFERS (FCMR)

OPWR-HDEG (AOTS)

AIS (E1)

GFP-NO-BUFFERS (GFP-FAC)

OPWR-HDEG (OCH)

AIS (E3)

GFP-UP-MISMATCH (CE1000)

OPWR-HDEG (OCH-TERM)

AIS (E4)

GFP-UP-MISMATCH (CE100T)

OPWR-HDEG (OMS)

AIS (FUDC)

GFP-UP-MISMATCH (CEMR)

OPWR-HDEG (OTS)

AIS (MSUDC)

GFP-UP-MISMATCH (FCMR)

OPWR-HFAIL (AOTS)

AIS (TRUNK)

GFP-UP-MISMATCH (GFP-FAC)

OPWR-HFAIL (OCH)

AIS-L (TRUNK)

GFP-UP-MISMATCH (ML1000)

OPWR-HFAIL (OMS)

ALS (2R)

GFP-UP-MISMATCH (ML100T)

OPWR-HFAIL (OTS)

ALS (AOTS)

GFP-UP-MISMATCH (MLFX)

OPWR-LDEG (AOTS)

ALS (ESCON)

GFP-UP-MISMATCH (MLMR)

OPWR-LDEG (OCH)

ALS (FC)

HELLO (STMN)

OPWR-LDEG (OCH-TERM)

ALS (GE)

HELLO (TRUNK)

OPWR-LDEG (OMS)

ALS (ISC)

HI-LASERBIAS (2R)

OPWR-LDEG (OTS)

ALS (STMN)

HI-LASERBIAS (EQPT)

OPWR-LFAIL (AOTS)

ALS (TRUNK)

HI-LASERBIAS (ESCON)

OPWR-LFAIL (OCH)

ALS-DISABLED (EQPT)

HI-LASERBIAS (FC)

OPWR-LFAIL (OCH-TERM)

AMPLI-INIT (AOTS)

HI-LASERBIAS (GE)

OPWR-LFAIL (OMS)

APC-CORR-SKIPPED (AOTS)

HI-LASERBIAS (ISC)

OPWR-LFAIL (OTS)

APC-CORR-SKIPPED (OCH)

HI-LASERBIAS (PPM)

OSRION (AOTS)

APC-CORR-SKIPPED (OMS)

HI-LASERBIAS (STMN)

OSRION (OTS)

APC-CORR-SKIPPED (OTS)

HI-LASERBIAS (TRUNK)

OTUK-AIS (TRUNK)

APC-DISABLED (AOTS)

HI-LASERTEMP (EQPT)

OTUK-BDI (TRUNK)

APC-DISABLED (EQPT)

HI-LASERTEMP (PPM)

OTUK-IAE (TRUNK)

APC-DISABLED (NE)

HI-LASERTEMP (STMN)

OTUK-LOF (TRUNK)

APC-DISABLED (OCH)

HI-RXPOWER (2R)

OTUK-SD (TRUNK)

APC-DISABLED (OMS)

HI-RXPOWER (ESCON)

OTUK-SF (TRUNK)

APC-DISABLED (OTS)

HI-RXPOWER (FC)

OTUK-TIM (TRUNK)

APC-DISABLED (SHELF)

HI-RXPOWER (GE)

OUT-OF-SYNC (FC)

APC-END (NE)

HI-RXPOWER (ISC)

OUT-OF-SYNC (GE)

APC-OUT-OF-RANGE (AOTS)

HI-RXPOWER (STMN)

OUT-OF-SYNC (ISC)

APC-OUT-OF-RANGE (OCH)

HI-RXPOWER (TRUNK)

OUT-OF-SYNC (TRUNK)

APC-OUT-OF-RANGE (OMS)

HITEMP (EQPT)

PARAM-MISM (AOTS)

APC-OUT-OF-RANGE (OTS)

HITEMP (NE)

PARAM-MISM (OCH)

APC-WRONG-GAIN (AOTS)

HI-TXPOWER (2R)

PARAM-MISM (OCH-TERM)

APSB (STMN)

HI-TXPOWER (EQPT)

PARAM-MISM (OMS)

APSCDFLTK (STMN)

HI-TXPOWER (ESCON)

PARAM-MISM (OTS)

APSC-IMP (STMN)

HI-TXPOWER (FC)

PEER-NORESPONSE (MLMR)

APSCINCON (STMN)

HI-TXPOWER (GE)

APSCM (STMN)

HI-TXPOWER (ISC)

APSCNMIS (STMN)

HI-TXPOWER (PPM)

PMI (OMS)

APSIMP (STMN)

HI-TXPOWER (STMN)

PMI (OTS)

APS-INV-PRIM (STMN)

HI-TXPOWER (TRUNK)

PORT-FAIL (OCH)

APS-PRIM-FAC (STMN)

HLDOVRSYNC (NE-SREF)

PORT-MISMATCH (CEMR)

APS-PRIM-SEC-MISM (STMN)

HP-DEG (VCMON-HP)

PORT-MISMATCH (FCMR)

AS-CMD (2R)

HP-DEG (VCTRM-HP)

PORT-MISMATCH (MLMR)

AS-CMD (AOTS)

HP-ENCAP-MISMATCH (VCTRM-HP)

PRC-DUPID (STMN)

AS-CMD (BPLANE)

HP-EXC (VCMON-HP)

PROTNA (EQPT)

AS-CMD (CE1000)

HP-EXC (VCTRM-HP)

PROV-MISMATCH (PPM)

AS-CMD (CE100T)

HP-PLM (VCMON-HP)

PROV-MISMATCH (TRUNK)

AS-CMD (CEMR)

HP-PLM (VCTRM-HP)

PTIM (TRUNK)

AS-CMD (DS1)

HP-RFI (VCMON-HP)

PWR-FAIL-A (EQPT)

AS-CMD (DS3)

HP-RFI (VCTRM-HP)

PWR-FAIL-B (EQPT)

AS-CMD (E1)

HP-TIM (VCMON-HP)

PWR-FAIL-RET-A (EQPT)

AS-CMD (E1000F)

HP-TIM (VCTRM-HP)

PWR-FAIL-RET-B (EQPT)

AS-CMD (E100T)

HP-UNEQ (VCMON-HP)

RAI (DS1)

AS-CMD (E3)

HP-UNEQ (VCTRM-HP)

RAI (DS3)

AS-CMD (E4)

IDLE (DS1)

RAI (E1)

AS-CMD (EQPT)

I-HITEMP (NE)

RCVR-MISS (DS1)

AS-CMD (ESCON)

ILK-FAIL (TRUNK)

RCVR-MISS (E1)

AS-CMD (FC)

IMPROPRMVL (EQPT)

RSV-RT-EXCD-RINGLET0 (RPRIF)

AS-CMD (FCMR)

IMPROPRMVL (PPM)

RSV-RT-EXCD-RINGLET1 (RPRIF)

AS-CMD (G1000)

INC-ISD (DS3)

RFI (TRUNK)

AS-CMD (GE)

INC-ISD (E3)

RFI-L (TRUNK)

AS-CMD (GFP-FAC)

INHSWPR (EQPT)

RING-ID-MIS (OSC-RING)

AS-CMD (ISC)

INHSWWKG (EQPT)

RING-ID-MIS (STMN)

AS-CMD (ML1000)

INTRUSION-PSWD (NE)

RING-MISMATCH (STMN)

AS-CMD (ML100T)

INVMACADR (BPLANE)

RING-SW-EAST (STMN)

AS-CMD (MLFX)

IOSCFGCOPY (EQPT)

RING-SW-WEST (STMN)

AS-CMD (MLMR)

ISIS-ADJ-FAIL (STMN)

ROLL (VCMON-HP)

AS-CMD (NE)

ISIS-ADJ-FAIL (TRUNK)

ROLL (VCMON-LP)

AS-CMD (OCH)

KB-PASSTHR (STMN)

ROLL (VCTRM-HP)

AS-CMD (OMS)

KBYTE-APS-CHAN-FAIL (STMN)

ROLL (VCTRM-LP)

AS-CMD (OTS)

LAN-POL-REV (NE)

ROLL-PEND (VCMON-HP)

AS-CMD (PPM)

LASER-APR (AOTS)

ROLL-PEND (VCMON-LP)

AS-CMD (PWR)

LASERBIAS-DEG (AOTS)

ROLL-PEND (VCTRM-HP)

AS-CMD (SHELF)

LASERBIAS-DEG (OTS)

ROLL-PEND (VCTRM-LP)

AS-CMD (STM1E)

LASERBIAS-FAIL (AOTS)

RPR-PASSTHR (RPRIF)

AS-CMD (STMN)

LASERTEMP-DEG (AOTS)

RPR-PEER-MISS (RPRIF)

AS-CMD (TRUNK)

LCAS-CRC (VCTRM-HP)

RPR-PROT-ACTIVE (RPRIF)

AS-MT (2R)

LCAS-CRC (VCTRM-LP)

RPR-PROT-CONFIG-MISM (RPRIF)

AS-MT (AOTS)

LCAS-RX-DNU (VCTRM-HP)

RPR-RI-FAIL (RPRIF)

AS-MT (CE1000)

LCAS-RX-DNU (VCTRM-LP)

RPR-SD (ML1000)

AS-MT (CE100T)

LCAS-RX-FAIL (VCTRM-HP)

RPR-SD (ML100T)

AS-MT (CEMR)

LCAS-RX-FAIL (VCTRM-LP)

RPR-SD (MLFX)

AS-MT (DS1)

LCAS-RX-GRP-ERR (VCTRM-HP)

RPR-SD (MLMR)

AS-MT (DS3)

LCAS-RX-GRP-ERR (VCTRM-LP)

RPR-SF (ML1000)

AS-MT (E1)

LCAS-TX-ADD (VCTRM-HP)

RPR-SF (ML100T)

AS-MT (E3)

LCAS-TX-ADD (VCTRM-LP)

RPR-SF (MLFX)

AS-MT (E4)

LCAS-TX-DNU (VCTRM-HP)

RPR-SF (MLMR)

AS-MT (EQPT)

LCAS-TX-DNU (VCTRM-LP)

RPR-SPAN-MISMATCH (ML1000)

AS-MT (ESCON)

LINK-KEEPALIVE (ML1000)

RPR-SPAN-MISMATCH (ML100T)

AS-MT (FC)

LINK-KEEPALIVE (ML100T)

RPR-SPAN-MISMATCH (MLFX)

AS-MT (FCMR)

LINK-KEEPALIVE (MLFX)

RPR-SPAN-MISMATCH (MLMR)

AS-MT (G1000)

LINK-KEEPALIVE (MLMR)

RPRW (ML1000)

AS-MT (GE)

LKOUTPR-S (STMN)

RPRW (ML100T)

AS-MT (GFP-FAC)

LMP-FAIL (CTRL)

RPRW (MLFX)

AS-MT (ISC)

LMP-FAIL (GE)

RS-EOC (STMN)

AS-MT (ML1000)

LMP-FAIL (STMN)

RS-TIM (STMN)

AS-MT (ML100T)

LMP-FAIL (TLINK)

RUNCFG-SAVENEED (EQPT)

AS-MT (MLFX)

LMP-SD (GE)

SD (DS1)

AS-MT (MLMR)

LMP-SD (STMN)

SD (DS3)

AS-MT (OCH)

LMP-SF (GE)

SD (STM1E)

AS-MT (OMS)

LMP-SF (STMN)

SD (TRUNK)

AS-MT (OTS)

LMP-UNALLOC (GE)

SD-L (TRUNK)

AS-MT (PPM)

LMP-UNALLOC (STMN)

SF (DS1)

AS-MT (SHELF)

LOA (VCG)

SF (DS3)

AS-MT (STM1E)

LOCKOUT-REQ (2R)

SF (TRUNK)

AS-MT (STMN)

LOCKOUT-REQ (EQPT)

SF-L (TRUNK)

AS-MT (TRUNK)

LOCKOUT-REQ (ESCON)

SFTWDOWN (EQPT)

AS-MT-OOG (VCTRM-HP)

LOCKOUT-REQ (FC)

SHELF-COMM-FAIL (SHELF)

AS-MT-OOG (VCTRM-LP)

LOCKOUT-REQ (GE)

SH-IL-VAR-DEG-HIGH (OTS)

AU-AIS (VCMON-HP)

LOCKOUT-REQ (ISC)

SH-IL-VAR-DEG-LOW (OTS)

AU-AIS (VCTRM-HP)

LOCKOUT-REQ (STMN)

SHUTTER-OPEN (OTS)

AUD-LOG-LOSS (NE)

LOCKOUT-REQ (TRUNK)

SIGLOSS (ESCON)

AUD-LOG-LOW (NE)

LOCKOUT-REQ (VCMON-HP)

SIGLOSS (FC)

AU-LOF (VCTRM-HP)

LOCKOUT-REQ (VCMON-LP)

SIGLOSS (FCMR)

AU-LOP (VCMON-HP)

LOF (BITS)

SIGLOSS (GE)

AU-LOP (VCTRM-HP)

LOF (DS1)

SIGLOSS (ISC)

AUTOLSROFF (STMN)

LOF (DS3)

SIGLOSS (TRUNK)

AUTONEG-RFI (ML1000)

LOF (E1)

SNTP-HOST (NE)

AUTORESET (EQPT)

LOF (E4)

SPANLEN-OUT-OF-RANGE (OTS)

AUTOSW-AIS-SNCP (VCMON-HP)

LOF (STM1E)

SPAN-NOT-MEASURED (OTS)

AUTOSW-AIS-SNCP (VCMON-LP)

LOF (STMN)

SPAN-SW-EAST (STMN)

AUTOSW-LOP-SNCP (VCMON-HP)

LOF (TRUNK)

SPAN-SW-WEST (STMN)

AUTOSW-LOP-SNCP (VCMON-LP)

LO-LASERBIAS (EQPT)

SQM (VCTRM-HP)

LO-LASERBIAS (PPM)

SQM (VCTRM-LP)

LO-LASERBIAS (STMN)

SQUELCH (STMN)

AUTOSW-SDBER-SNCP (VCMON-HP)

LO-LASERTEMP (EQPT)

SQUELCHED (2R)

AUTOSW-SDBER-SNCP (VCMON-LP)

LO-LASERTEMP (PPM)

SQUELCHED (ESCON)

AUTOSW-SFBER-SNCP (VCMON-HP)

LO-LASERTEMP (STMN)

SQUELCHED (FC)

AUTOSW-SFBER-SNCP (VCMON-LP)

LOM (TRUNK)

SQUELCHED (GE)

AUTOSW-UNEQ-SNCP (VCMON-HP)

LOM (VCMON-HP)

SQUELCHED (ISC)

AUTOSW-UNEQ-SNCP (VCMON-LP)

LOM (VCTRM-HP)

SQUELCHED (STMN)

AWG-DEG (OTS)

LOM (VCTRM-LP)

SQUELCHED (TRUNK)

AWG-FAIL (OTS)

LO-RXPOWER (2R)

SSM-DUS (BITS)

AWG-OVERTEMP (OTS)

LO-RXPOWER (ESCON)

SSM-DUS (DS1)

AWG-WARM-UP (OTS)

LO-RXPOWER (FC)

SSM-DUS (E1)

BAT-FAIL (PWR)

LO-RXPOWER (GE)

SSM-DUS (STMN)

BKUPMEMP (EQPT)

LO-RXPOWER (ISC)

SSM-DUS (TRUNK)

CARLOSS (CE1000)

LO-RXPOWER (STMN)

SSM-FAIL (BITS)

CARLOSS (CE100T)

LO-RXPOWER (TRUNK)

SSM-FAIL (E1)

CARLOSS (CEMR)

LOS (2R)

SSM-FAIL (STMN)

CARLOSS (E1000F)

LOS (BITS)

SSM-FAIL (TRUNK)

CARLOSS (E100T)

LOS (DS1)

SSM-LNC (BITS)

CARLOSS (EQPT)

LOS (DS3)

SSM-LNC (NE-SREF)

CARLOSS (FC)

LOS (E1)

SSM-LNC (STMN)

CARLOSS (G1000)

LOS (E3)

SSM-LNC (TRUNK)

CARLOSS (GE)

LOS (E4)

SSM-OFF (BITS)

CARLOSS (ISC)

LOS (ESCON)

SSM-OFF (DS1)

CARLOSS (ML1000)

LOS (FUDC)

SSM-OFF (E1)

CARLOSS (ML100T)

LOS (ISC)

SSM-OFF (STMN)

CARLOSS (MLFX)

LOS (MSUDC)

SSM-OFF (TRUNK)

CARLOSS (MLMR)

LOS (OTS)

SSM-PRC (BITS)

CARLOSS (TRUNK)

LOS (STM1E)

SSM-PRC (NE-SREF)

CASETEMP-DEG (AOTS)

LOS (STMN)

SSM-PRC (STMN)

CLDRESTART (EQPT)

LOS (TRUNK)

SSM-PRC (TRUNK)

COMIOXC (EQPT)

LOS-O (OCH)

SSM-PRS (E1)

COMM-FAIL (EQPT)

LOS-O (OMS)

SSM-PRS (TRUNK)

CONTBUS-A-18 (EQPT)

LOS-O (OTS)

SSM-RES (DS1)

CONTBUS-B-18 (EQPT)

LOS-P (OCH)

SSM-RES (E1)

CONTBUS-DISABLED (EQPT)

LOS-P (OMS)

SSM-RES (TRUNK)

CONTBUS-IO-A (EQPT)

LOS-P (OTS)

SSM-SDH-TN (BITS)

CONTBUS-IO-B (EQPT)

LOS-P (TRUNK)

SSM-SDH-TN (NE-SREF)

CPP-INCAPABLE (MLMR)

LO-TXPOWER (2R)

SSM-SDH-TN (STMN)

CTNEQPT-MISMATCH (EQPT)

LO-TXPOWER (EQPT)

SSM-SDH-TN (TRUNK)

CTNEQPT-PBPROT (EQPT)

LO-TXPOWER (ESCON)

SSM-SETS (BITS)

CTNEQPT-PBWORK (EQPT)

LO-TXPOWER (FC)

SSM-SETS (NE-SREF)

DATA-CRC (CE100T)

LO-TXPOWER (GE)

SSM-SETS (STMN)

DATA-CRC (ML1000)

LO-TXPOWER (ISC)

SSM-SETS (TRUNK)

DATA-CRC (ML100T)

LO-TXPOWER (PPM)

SSM-SMC (E1)

DATA-CRC (MLFX)

LO-TXPOWER (STMN)

SSM-SMC (TRUNK)

DATAFLT (NE)

LO-TXPOWER (TRUNK)

SSM-ST2 (E1)

DBOSYNC (NE)

LPBKCRS (VCMON-HP)

SSM-ST2 (TRUNK)

DCU-LOSS-FAIL (OTS)

LPBKCRS (VCTRM-HP)

SSM-ST3 (E1)

DS3-MISM (DS3)

LPBKDS1FE-CMD (DS1)

SSM-ST3 (TRUNK)

DSP-COMM-FAIL (TRUNK)

LPBKDS3FEAC (DS3)

SSM-ST3E (E1)

DSP-FAIL (TRUNK)

LPBKDS3FEAC-CMD (DS3)

SSM-ST3E (TRUNK)

DUP-IPADDR (NE)

LPBKDS3FEAC-CMD (E3)

SSM-ST4 (DS1)

DUP-NODENAME (NE)

LPBKE1FEAC (E3)

SSM-ST4 (E1)

DUP-SHELF-ID (SHELF)

LPBKE3FEAC (E3)

SSM-ST4 (STMN)

EHIBATVG (PWR)

LPBKFACILITY (CE1000)

SSM-ST4 (TRUNK)

ELWBATVG (PWR)

LPBKFACILITY (CE100T)

SSM-STU (BITS)

RS-EOC (TRUNK)

LPBKFACILITY (CEMR)

SSM-STU (E1)

EOC-L (TRUNK)

LPBKFACILITY (DS1)

SSM-STU (NE-SREF)

EQPT (AICI-AEP)

LPBKFACILITY (DS3)

SSM-STU (STMN)

EQPT (AICI-AIE)

LPBKFACILITY (E1)

SSM-STU (TRUNK)

EQPT (EQPT)

LPBKFACILITY (E3)

SSM-TNC (NE-SREF)

EQPT (PPM)

LPBKFACILITY (E4)

SSM-TNC (STMN)

EQPT-DIAG (EQPT)

LPBKFACILITY (ESCON)

SSM-TNC (TRUNK)

EQPT-MISS (FAN)

LPBKFACILITY (FC)

SW-MISMATCH (EQPT)

ERROR-CONFIG (EQPT)

LPBKFACILITY (FCMR)

SWMTXMOD-PROT (EQPT)

ETH-LINKLOSS (NE)

LPBKFACILITY (G1000)

SWMTXMOD-WORK (EQPT)

E-W-MISMATCH (STMN)

LPBKFACILITY (GE)

SWTOPRI (EXT-SREF)

EXCCOL (EQPT)

LPBKFACILITY (ISC)

SWTOPRI (NE-SREF)

EXERCISE-RING-FAIL (STMN)

LPBKFACILITY (MLMR)

SWTOSEC (EXT-SREF)

EXERCISE-SPAN-FAIL (STMN)

LPBKFACILITY (STM1E)

SWTOSEC (NE-SREF)

EXT (ENVALRM)

LPBKFACILITY (STMN)

SWTOTHIRD (EXT-SREF)

EXTRA-TRAF-PREEMPT (STMN)

LPBKFACILITY (TRUNK)

SWTOTHIRD (NE-SREF)

FAILTOSW (2R)

LPBKTERMINAL (CE1000)

SYNC-FREQ (DS1)

FAILTOSW (EQPT)

LPBKTERMINAL (CE100T)

SYNC-FREQ (E1)

FAILTOSW (ESCON)

LPBKTERMINAL (CEMR)

SYNC-FREQ (STMN)

FAILTOSW (FC)

LPBKTERMINAL (DS1)

SYNC-FREQ (TRUNK)

FAILTOSW (GE)

LPBKTERMINAL (DS3)

SYNCLOSS (FC)

FAILTOSW (ISC)

LPBKTERMINAL (E1)

SYNCLOSS (FCMR)

FAILTOSW (STMN)

LPBKTERMINAL (E3)

SYNCLOSS (GE)

FAILTOSW (TRUNK)

LPBKTERMINAL (E4)

SYNCLOSS (ISC)

FAILTOSW-PATH (VCMON-HP)

LPBKTERMINAL (ESCON)

SYNCLOSS (TRUNK)

FAILTOSW-PATH (VCMON-LP)

LPBKTERMINAL (FC)

SYNCPRI (EXT-SREF)

FAILTOSWR (STMN)

LPBKTERMINAL (FCMR)

SYNCPRI (NE-SREF)

FAILTOSWS (STMN)

LPBKTERMINAL (G1000)

SYNCSEC (EXT-SREF)

FAN (FAN)

LPBKTERMINAL (GE)

SYNCSEC (NE-SREF)

FAPS (FCMR)

LPBKTERMINAL (ISC)

SYNCTHIRD (EXT-SREF)

FAPS (TRUNK)

LPBKTERMINAL (MLMR)

SYNCTHIRD (NE-SREF)

FAPS-CONFIG-MISMATCH (EQPT)

LPBKTERMINAL (STM1E)

SYSBOOT (NE)

FC-DE-NES (FC)

LPBKTERMINAL (STMN)

TEMP-MISM (NE)

FC-DE-NES (FCMR)

LPBKTERMINAL (TRUNK)

TIM (STM1E)

FC-DE-NES (TRUNK)

LP-DEG (VCMON-LP)

TIM (STMN)

FC-NO-CREDITS (FC)

LP-DEG (VCTRM-LP)

TIM (TRUNK)

FC-NO-CREDITS (FCMR)

LP-ENCAP-MISMATCH (VCTRM-LP)

TIM-MON (STMN)

FC-NO-CREDITS (TRUNK)

LP-EXC (VCMON-LP)

TIM-MON (TRUNK)

FDI (OCH)

LP-EXC (VCTRM-LP)

TPTFAIL (CE1000)

FDI (OCH-TERM)

LP-PLM (VCMON-LP)

TPTFAIL (CE100T)

FE-AIS (E3)

LP-PLM (VCTRM-LP)

TPTFAIL (CEMR)

FEC-MISM (TRUNK)

LP-RFI (VCMON-LP)

TPTFAIL (FCMR)

FE-E1-MULTLOS (E3)

LP-RFI (VCTRM-LP)

TPTFAIL (G1000)

FE-E1-NSA (E3)

LP-TIM (VCMON-LP)

TPTFAIL (ML1000)

FE-E1-SA (E3)

LP-TIM (VCTRM-LP)

TPTFAIL (ML100T)

FE-E1-SNGLLOS (E3)

LP-UNEQ (VCMON-LP)

TPTFAIL (MLFX)

FE-E3-NSA (E3)

LP-UNEQ (VCTRM-LP)

TPTFAIL (MLMR)

FE-E3-SA (E3)

MAN-REQ (EQPT)

TRAIL-SIGNAL-FAIL (OCH)

FE-EQPT-NSA (E3)

MAN-REQ (ML1000)

TRAIL-SIGNAL-FAIL (TRUNK)

FE-FRCDWKSWBK-SPAN (STMN)

MAN-REQ (ML100T)

TRMT (DS1)

FE-FRCDWKSWPR-RING (STMN)

MAN-REQ (MLFX)

TRMT (E1)

FE-FRCDWKSWPR-SPAN (STMN)

MAN-REQ (MLMR)

TRMT-MISS (DS1)

FE-IDLE (E3)

MAN-REQ (VCMON-HP)

TRMT-MISS (E1)

FE-LOCKOUTOFPR-SPAN (STMN)

MAN-REQ (VCMON-LP)

TU-AIS (VCMON-LP)

FE-LOF (E3)

MANRESET (EQPT)

TU-AIS (VCTRM-LP)

FE-LOS (E3)

MANSWTOINT (NE-SREF)

TU-LOP (VCMON-LP)

FE-MANWKSWBK-SPAN (STMN)

MANSWTOPRI (EXT-SREF)

TU-LOP (VCTRM-LP)

FE-MANWKSWPR-RING (STMN)

MANSWTOPRI (NE-SREF)

TX-AIS (DS1)

FE-MANWKSWPR-SPAN (STMN)

MANSWTOSEC (EXT-SREF)

TX-AIS (DS3)

FEPRLF (STMN)

MANSWTOSEC (NE-SREF)

TX-AIS (E1)

FIBERTEMP-DEG (AOTS)

MANSWTOTHIRD (EXT-SREF)

TX-AIS (E3)

FORCED-REQ (EQPT)

MANSWTOTHIRD (NE-SREF)

TX-IDLE (DS1)

FORCED-REQ (ML1000)

MANUAL-REQ-RING (STMN)

TX-LOF (DS1)

FORCED-REQ (ML100T)

MANUAL-REQ-SPAN (2R)

TX-LOF (E1)

FORCED-REQ (MLFX)

MANUAL-REQ-SPAN (ESCON)

TX-RAI (DS1)

FORCED-REQ (MLMR)

MANUAL-REQ-SPAN (FC)

TX-RAI (E1)

FORCED-REQ (VCMON-HP)

MANUAL-REQ-SPAN (GE)

TX-RAI (E3)

FORCED-REQ (VCMON-LP)

MANUAL-REQ-SPAN (ISC)

UNC-WORD (TRUNK)

FORCED-REQ-RING (STMN)

MANUAL-REQ-SPAN (STMN)

UNQUAL-PPM (PPM)

FORCED-REQ-SPAN (2R)

MANUAL-REQ-SPAN (TRUNK)

UT-COMM-FAIL (TRUNK)

FORCED-REQ-SPAN (ESCON)

MAX-STATIONS (RPRIF)

UT-FAIL (TRUNK)

FORCED-REQ-SPAN (FC)

MEA (BIC)

VCG-DEG (VCG)

FORCED-REQ-SPAN (GE)

MEA (EQPT)

VCG-DOWN (VCG)

FORCED-REQ-SPAN (ISC)

MEA (FAN)

VOA-HDEG (AOTS)

FORCED-REQ-SPAN (STMN)

MEA (PPM)

VOA-HDEG (OCH)

FORCED-REQ-SPAN (TRUNK)

MEA (SHELF)

VOA-HDEG (OMS)

FP-LINK-LOSS (EQPT)

MEM-GONE (EQPT)

VOA-HDEG (OTS)

FRCDSWTOINT (NE-SREF)

MEM-LOW (EQPT)

VOA-HFAIL (AOTS)

FRCDSWTOPRI (EXT-SREF)

MFGMEM (AICI-AEP)

VOA-HFAIL (OCH)

FRCDSWTOPRI (NE-SREF)

MFGMEM (AICI-AIE)

VOA-HFAIL (OMS)

FRCDSWTOSEC (EXT-SREF)

MFGMEM (BPLANE)

VOA-HFAIL (OTS)

FRCDSWTOSEC (NE-SREF)

MFGMEM (FAN)

VOA-LDEG (AOTS)

FRCDSWTOTHIRD (EXT-SREF)

MFGMEM (PPM)

VOA-LDEG (OCH)

FRCDSWTOTHIRD (NE-SREF)

MS-AIS (STM1E)

VOA-LDEG (OMS)

FRNGSYNC (NE-SREF)

MS-AIS (STMN)

VOA-LDEG (OTS)

FSTSYNC (NE-SREF)

MS-DEG (E1)

VOA-LFAIL (AOTS)

FTA-MISMATCH (EQPT)

MS-DEG (E3)

VOA-LFAIL (OCH)

FULLPASSTHR-BI (STMN)

MS-DEG (E4)

VOA-LFAIL (OMS)

GAIN-HDEG (AOTS)

MS-DEG (STM1E)

VOA-LFAIL (OTS)

GAIN-HFAIL (AOTS)

MS-DEG (STMN)

VOLT-MISM (PWR)

GAIN-LDEG (AOTS)

MS-EOC (STMN)

WKSWPR (2R)

GAIN-LFAIL (AOTS)

MS-EXC (E1)

WKSWPR (EQPT)

GCC-EOC (TRUNK)

MS-EXC (E3)

WKSWPR (ESCON)

GE-OOSYNC (FC)

MS-EXC (E4)

WKSWPR (FC)

GE-OOSYNC (GE)

MS-EXC (STM1E)

WKSWPR (GE)

GE-OOSYNC (ISC)

MS-EXC (STMN)

WKSWPR (ISC)

GE-OOSYNC (TRUNK)

MS-RFI (STM1E)

WKSWPR (STMN)

GFP-CSF (CE1000)

MS-RFI (STMN)

WKSWPR (VCMON-HP)

GFP-CSF (CE100T)

MSSP-OOSYNC (STMN)

WKSWPR (VCMON-LP)

GFP-CSF (CEMR)

MSSP-SW-VER-MISM (STMN)

WTR (2R)

GFP-CSF (FCMR)

MS-SQUELCH-HP (STMN)

WTR (EQPT)

GFP-CSF (GFP-FAC)

MS-SQUELCH-LP (STMN)

WTR (ESCON)

GFP-CSF (ML1000)

MT-OCHNC (OTS)

WTR (FC)

GFP-CSF (ML100T)

NO-CONFIG (EQPT)

WTR (GE)

GFP-CSF (MLFX)

NON-CISCO-PPM (PPM)

WTR (ISC)

GFP-CSF (MLMR)

OCHNC-INC (OCHNC-CONN)

WTR (ML1000)

GFP-DE-MISMATCH (FCMR)

OCHTERM-INC (OCH-TERM)

WTR (ML100T)

GFP-DE-MISMATCH (GFP-FAC)

ODUK-1-AIS-PM (TRUNK)

WTR (MLFX)

GFP-EX-MISMATCH (CE1000)

ODUK-2-AIS-PM (TRUNK)

WTR (MLMR)

GFP-EX-MISMATCH (FCMR)

ODUK-3-AIS-PM (TRUNK)

WTR (STMN)

GFP-EX-MISMATCH (GFP-FAC)

ODUK-4-AIS-PM (TRUNK)

WTR (TRUNK)

GFP-LFD (CE1000)

ODUK-AIS-PM (TRUNK)

WTR (VCMON-HP)

GFP-LFD (CE100T)

ODUK-BDI-PM (TRUNK)

WTR (VCMON-LP)

GFP-LFD (CEMR)

ODUK-LCK-PM (TRUNK)

WVL-MISMATCH (TRUNK)


2.3  Alarm Logical Objects

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

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


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


Table 2-7 Alarm Logical Object Type Definitions 

Object Type
Definition

2R

Reshape and retransmit (used for transponder [TXP] cards). For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

AICI-AEP

Alarm Interface Controller-International—Alarm expansion panel.

AICI-AIE

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

AIP

Alarm Interface Panel.

AOTS

Amplified optical transport section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

BIC

Backplane interface connector.

BITS

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

BPLANE

The backplane.

CE1000

CE-1000-4 card.

CE100T

CE-100T-8 card.

CEMR

CE-MR-10 card.

CTRL

Control channel.

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 signal on a DS3i-N-12 card.

E1

E1-42 card.

E3

E3-12 card.

E4

Line type supported by the STM1E card.

E1000F

An E1000-2-G card.

E100T

An E100T-G card.

ENVALRM

An environmental alarm port.

EQPT

A card, its physical objects, and logical objects as they are located in any of the
eight noncommon card slots. The EQPT object is used for alarms that refer to the
card itself and all other objects on the card including ports, lines, STM, and VC.

ESCON

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

EXT-SREF

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

FAN

Fan-tray assembly.

FC

Fibre Channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E.  For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

FCMR

An FC_MR-4 Fibre Channel card. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

FUDC

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

G1000

The ONS 15454 SDH G-Series card.

GE

Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10G. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

GFP-FAC

Generic framing procedure facility port, referring to all MXP and TXP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

ISC

Inter-service channel referring to MXP and TXP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

ML1000

The ONS 15454 SDH ML1000-2 card.

ML100T

The ONS 15454 SDH ML100T-2 or ML100T-8 card.

MLFX

An MLFX Ethernet card.

MLMR

ML-MR-10 Ethernet card.

MSUDC

Multiplex section user data channel.

NE

The entire network element.

NE-SREF

The timing status of the NE.

OCH

The optical channel, referring to dense wavelength division multiplexing (DWDM) cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

OCH-TERM

The optical channel termination node, referring to DWDM cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

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

OCHNC-CONN

The optical channel network connection, referring to DWDM cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

OMS

Optical multiplex section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

OSC-RING

Optical service channel ring. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

OTS

Optical transport section. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

PWR

Power equipment.

PPM

Pluggable port module (PPM), referring to all MXP and TXP cards, MRC-12 cards, and OC192-XFP/STM64-XFP cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

RPRIF

Resilient Packet Ring (RPR) Interface.

SHELF

The shelf assembly. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

STM1E

Synchronous transfer mode 1 (speed) electrical interface

STMN

An STM-N line on an STM-N card.

TLINK

Traffic engineering (TE) link correlation.

VCTRM-HP

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

TRUNK

The optical or DWDM card carrying the high-speed signal; referring to MXP, TXP, or ML-Series cards. For more information about most of the alarms on this object, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

UCP-CKT

Unified control plane circuit.

UCP-IPCC

Unified control plane IP control channel.

UCP-NBR

Unified control plane neighbor.

VCG

ONS 15454 SDH virtual concatenation group of virtual tributaries (VT).

VCMON-HP

High-order path virtual concatenation monitoring.

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

VCMON-LP

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

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

VCTRM-HP

High-order path concatenation termination monitoring.

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

VCTRM-LP

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

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


2.4  Alarm List by Logical Object Type

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


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



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


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

2R: ALS (NA)

FC: HI-TXPOWER (MN)

PWR: VOLT-MISM (NA)

2R: AS-CMD (NA)

FC: LO-RXPOWER (MN)

RPRIF: MAX-STATIONS (MJ)

2R: AS-MT (NA)

FC: LO-TXPOWER (MN)

RPRIF: RSV-RT-EXCD-RINGLET0 (MJ)

2R: FAILTOSW (NA)

FC: LOCKOUT-REQ (NA)

RPRIF: RSV-RT-EXCD-RINGLET1 (MJ)

2R: FORCED-REQ-SPAN (NA)

FC: LPBKFACILITY (NA)

RPRIF: RPR-PASSTHR (NA)

2R: HI-LASERBIAS (MN)

FC: LPBKTERMINAL (NA)

RPRIF: RPR-PEER-MISS (MJ)

2R: HI-RXPOWER (MN)

FC: MANUAL-REQ-SPAN (NA)

RPRIF: RPR-PROT-ACTIVE (NA)

2R: HI-TXPOWER (MN)

FC: OUT-OF-SYNC (MJ)

RPRIF: RPR-PROT-CONFIG-MISM (MJ)

2R: LO-RXPOWER (MN)

FC: SIGLOSS (MJ)

RPRIF: RPR-RI-FAIL (MJ)

2R: LO-TXPOWER (MN)

FC: SQUELCHED (NA)

SHELF: APC-DISABLED (NA)

2R: LOCKOUT-REQ (NA)

FC: SYNCLOSS (MJ)

SHELF: AS-CMD (NA)

2R: LOS (CR)

FC: WKSWPR (NA)

SHELF: AS-MT (NA)

2R: MANUAL-REQ-SPAN (NA)

FC: WTR (NA)

SHELF: DUP-SHELF-ID (MJ)

2R: SQUELCHED (NA)

FCMR: AS-CMD (NA)

SHELF: MEA (MJ)

2R: WKSWPR (NA)

FCMR: AS-MT (NA)

SHELF: SHELF-COMM-FAIL (MJ)

2R: WTR (NA)

FCMR: FAPS (NA)

STM1E: AS-CMD (NA)

AICI-AEP: EQPT (CR)

FCMR: FC-DE-NES (MJ)

STM1E: AS-MT (NA)

AICI-AEP: MFGMEM (CR)

FCMR: FC-NO-CREDITS (MJ)

STM1E: LOF (CR)

AICI-AIE: EQPT (CR)

FCMR: GFP-CSF (MJ)

STM1E: LOS (CR)

AICI-AIE: MFGMEM (CR)

FCMR: GFP-DE-MISMATCH (MJ)

STM1E: LPBKFACILITY (NA)

AOTS: ALS (NA)

FCMR: GFP-EX-MISMATCH (MJ)

STM1E: LPBKTERMINAL (NA)

AOTS: AMPLI-INIT (NA)

FCMR: GFP-LFD (MJ)

STM1E: MS-AIS (NR)

AOTS: APC-CORR-SKIPPED (MN)

FCMR: GFP-NO-BUFFERS (MJ)

STM1E: MS-DEG (NA)

AOTS: APC-DISABLED (NA)

FCMR: GFP-UP-MISMATCH (MJ)

STM1E: MS-EXC (NA)

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

FCMR: LPBKFACILITY (NA)

STM1E: MS-RFI (NR)

AOTS: APC-WRONG-GAIN (NA)

FCMR: LPBKTERMINAL (NA)

STM1E: SD (NA)

AOTS: AS-CMD (NA)

FCMR: PORT-MISMATCH (NA)

STM1E: TIM (MJ)

AOTS: AS-MT (NA)

FCMR: SIGLOSS (MJ)

STMN: ALS (NA)

AOTS: CASETEMP-DEG (MN)

FCMR: SYNCLOSS (MJ)

STMN: APS-INV-PRIM (MN)

AOTS: FIBERTEMP-DEG (MN)

FCMR: TPTFAIL (MJ)

STMN: APS-PRIM-FAC (NA)

AOTS: GAIN-HDEG (MN)

FUDC: AIS (NR)

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

AOTS: GAIN-HFAIL (CR)

FUDC: LOS (MN)

STMN: APSB (MN)

AOTS: GAIN-LDEG (MN)

G1000: AS-CMD (NA)

STMN: APSC-IMP (MN)

AOTS: GAIN-LFAIL (CR)

G1000: AS-MT (NA)

STMN: APSCDFLTK (MN)

AOTS: LASER-APR (NA)

G1000: CARLOSS (MJ)

STMN: APSCINCON (MN)

AOTS: LASERBIAS-DEG (MN)

G1000: LPBKFACILITY (NA)

STMN: APSCM (MN)

AOTS: LASERBIAS-FAIL (MJ)

G1000: LPBKTERMINAL (NA)

STMN: APSCNMIS (MJ)

AOTS: LASERTEMP-DEG (MN)

G1000: TPTFAIL (MJ)

STMN: APSIMP (MN)

AOTS: OPWR-HDEG (MN)

GE: ALS (NA)

STMN: AS-CMD (NA)

AOTS: OPWR-HFAIL (CR)

GE: AS-CMD (NA)

STMN: AS-MT (NA)

AOTS: OPWR-LDEG (MN)

GE: AS-MT (NA)

STMN: AUTOLSROFF (CR)

AOTS: OPWR-LFAIL (CR)

GE: CARLOSS (MJ)

STMN: E-W-MISMATCH (MJ)

AOTS: OSRION (NA)

GE: FAILTOSW (NA)

STMN: EXERCISE-RING-FAIL (NA)

AOTS: PARAM-MISM (NA)

GE: FORCED-REQ-SPAN (NA)

STMN: EXERCISE-SPAN-FAIL (NA)

AOTS: VOA-HDEG (MN)

GE: GE-OOSYNC (CR)

STMN: EXTRA-TRAF-PREEMPT (MJ)

AOTS: VOA-HFAIL (CR)

GE: HI-LASERBIAS (MN)

STMN: FAILTOSW (NA)

AOTS: VOA-LDEG (MN)

GE: HI-RXPOWER (MN)

STMN: FAILTOSWR (NA)

AOTS: VOA-LFAIL (CR)

GE: HI-TXPOWER (MN)

STMN: FAILTOSWS (NA)

BIC: MEA (CR)

GE: LMP-FAIL (MN)

STMN: FE-FRCDWKSWBK-SPAN (NA)

BITS: AIS (NR)

GE: LMP-SD (MN)

STMN: FE-FRCDWKSWPR-RING (NA)

BITS: LOF (MN)

GE: LMP-SF (MN)

STMN: FE-FRCDWKSWPR-SPAN (NA)

BITS: LOS (MN)

GE: LMP-UNALLOC (NA)

STMN: FE-LOCKOUTOFPR-SPAN (NA)

BITS: SSM-DUS (NA)

GE: LO-RXPOWER (MN)

STMN: FE-MANWKSWBK-SPAN (NA)

BITS: SSM-FAIL (MN)

GE: LO-TXPOWER (MN)

STMN: FE-MANWKSWPR-RING (NA)

BITS: SSM-LNC (NA)

GE: LOCKOUT-REQ (NA)

STMN: FE-MANWKSWPR-SPAN (NA)

BITS: SSM-OFF (NA)

GE: LPBKFACILITY (NA)

STMN: FEPRLF (MN)

BITS: SSM-PRC (NA)

GE: LPBKTERMINAL (NA)

STMN: FORCED-REQ-RING (NA)

BITS: SSM-SDH-TN (NA)

GE: MANUAL-REQ-SPAN (NA)

STMN: FORCED-REQ-SPAN (NA)

BITS: SSM-SETS (NA)

GE: OUT-OF-SYNC (MJ)

STMN: FULLPASSTHR-BI (NA)

BITS: SSM-STU (NA)

GE: SIGLOSS (MJ)

STMN: HELLO (MN)

BPLANE: AS-CMD (NA)

GE: SQUELCHED (NA)

STMN: HI-LASERBIAS (MN)

BPLANE: INVMACADR (MJ)

GE: SYNCLOSS (MJ)

STMN: HI-LASERTEMP (MN)

BPLANE: MFGMEM (CR)

GE: WKSWPR (NA)

STMN: HI-RXPOWER (MN)

CE1000: AS-CMD (NA)

GE: WTR (NA)

STMN: HI-TXPOWER (MN)

CE1000: AS-MT (NA)

GFP-FAC: AS-CMD (NA)

STMN: ISIS-ADJ-FAIL (MN)

CE1000: CARLOSS (MJ)

GFP-FAC: AS-MT (NA)

STMN: KB-PASSTHR (NA)

CE1000: GFP-CSF (MJ)

GFP-FAC: GFP-CSF (MJ)

STMN: KBYTE-APS-CHAN-FAIL (MN)

CE1000: GFP-EX-MISMATCH (MJ)

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

STMN: LKOUTPR-S (NA)

CE1000: GFP-LFD (MJ)

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

STMN: LMP-FAIL (MN)

CE1000: GFP-UP-MISMATCH (MJ)

GFP-FAC: GFP-LFD (MJ)

STMN: LMP-SD (MN)

CE1000: LPBKFACILITY (NA)

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

STMN: LMP-SF (MN)

CE1000: LPBKTERMINAL (NA)

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

STMN: LMP-UNALLOC (NA)

CE1000: TPTFAIL (MJ)

ISC: ALS (NA)

STMN: LO-LASERBIAS (MN)

CE100T: AS-CMD (NA)

ISC: AS-CMD (NA)

STMN: LO-LASERTEMP (MN)

CE100T: AS-MT (NA)

ISC: AS-MT (NA)

STMN: LO-RXPOWER (MN)

CE100T: CARLOSS (MJ)

ISC: CARLOSS (MJ)

STMN: LO-TXPOWER (MN)

CE100T: DATA-CRC (MJ)

ISC: FAILTOSW (NA)

STMN: LOCKOUT-REQ (NA)

CE100T: GFP-CSF (MJ)

ISC: FORCED-REQ-SPAN (NA)

STMN: LOF (CR)

CE100T: GFP-LFD (MJ)

ISC: GE-OOSYNC (CR)

STMN: LOS (CR)

CE100T: GFP-UP-MISMATCH (MJ)

ISC: HI-LASERBIAS (MN)

STMN: LPBKFACILITY (NA)

CE100T: LPBKFACILITY (NA)

ISC: HI-RXPOWER (MN)

STMN: LPBKTERMINAL (NA)

CE100T: LPBKTERMINAL (NA)

ISC: HI-TXPOWER (MN)

STMN: MANUAL-REQ-RING (NA)

CE100T: TPTFAIL (MJ)

ISC: LO-RXPOWER (MN)

STMN: MANUAL-REQ-SPAN (NA)

CEMR: AS-CMD (NA)

ISC: LO-TXPOWER (MN)

STMN: MS-AIS (NR)

CEMR: AS-MT (NA)

ISC: LOCKOUT-REQ (NA)

STMN: MS-DEG (NA)

CEMR: CARLOSS (MJ)

ISC: LOS (CR)

STMN: MS-EOC (MN)

CEMR: GFP-CSF (MJ)

ISC: LPBKFACILITY (NA)

STMN: MS-EXC (NA)

CEMR: GFP-LFD (MJ)

ISC: LPBKTERMINAL (NA)

STMN: MS-RFI (NR)

CEMR: GFP-UP-MISMATCH (MJ)

ISC: MANUAL-REQ-SPAN (NA)

STMN: MS-SQUELCH-HP (NA)

CEMR: LPBKFACILITY (NA)

ISC: OUT-OF-SYNC (NA)

STMN: MS-SQUELCH-LP (NA)

CEMR: LPBKTERMINAL (NA)

ISC: SIGLOSS (MJ)

STMN: MSSP-OOSYNC (MJ)

CEMR: PORT-MISMATCH (MJ)

ISC: SQUELCHED (NA)

STMN: MSSP-SW-VER-MISM (MN)

CEMR: TPTFAIL (MJ)

ISC: SYNCLOSS (MJ)

STMN: PRC-DUPID (MJ)

CTRL: LMP-FAIL (MN)

ISC: WKSWPR (NA)

STMN: RING-ID-MIS (MJ)

DS1: AIS (NR)

ISC: WTR (NA)

STMN: RING-MISMATCH (MJ)

DS1: AS-CMD (NA)

ML1000: AS-CMD (NA)

STMN: RING-SW-EAST (NA)

DS1: AS-MT (NA)

ML1000: AS-MT (NA)

STMN: RING-SW-WEST (NA)

DS1: IDLE (NA)

ML1000: AUTONEG-RFI (MJ)

STMN: RS-EOC (MN)

DS1: LOF (MJ)

ML1000: CARLOSS (MJ)

STMN: RS-TIM (CR)

DS1: LOS (MJ)

ML1000: DATA-CRC (MJ)

STMN: SPAN-SW-EAST (NA)

DS1: LPBKDS1FE-CMD (NA)

ML1000: FORCED-REQ (NA)

STMN: SPAN-SW-WEST (NA)

DS1: LPBKFACILITY (NA)

ML1000: GFP-CSF (MJ)

STMN: SQUELCH (NA)

DS1: LPBKTERMINAL (NA)

ML1000: GFP-LFD (MJ)

STMN: SQUELCHED (NA)

DS1: RAI (NA)

ML1000: GFP-UP-MISMATCH (MJ)

STMN: SSM-DUS (NA)

DS1: RCVR-MISS (MJ)

ML1000: LINK-KEEPALIVE (CR)

STMN: SSM-FAIL (MN)

DS1: SD (NA)

ML1000: MAN-REQ (NA)

STMN: SSM-LNC (NA)

DS1: SF (NA)

ML1000: RPR-SD (NA)

STMN: SSM-OFF (NA)

DS1: SSM-DUS (NA)

ML1000: RPR-SF (NA)

STMN: SSM-PRC (NA)

DS1: SSM-OFF (NA)

ML1000: RPR-SPAN-MISMATCH (MJ)

STMN: SSM-SDH-TN (NA)

DS1: SSM-RES (NA)

ML1000: RPRW (NA)

STMN: SSM-SETS (NA)

DS1: SSM-ST4 (NA)

ML1000: TPTFAIL (MJ)

STMN: SSM-ST4 (NA)

DS1: SYNC-FREQ (NA)

ML1000: WTR (NA)

STMN: SSM-STU (NA)

DS1: TRMT (MJ)

ML100T: AS-CMD (NA)

STMN: SSM-TNC (NA)

DS1: TRMT-MISS (MJ)

ML100T: AS-MT (NA)

STMN: SYNC-FREQ (NA)

DS1: TX-AIS (NR)

ML100T: CARLOSS (MJ)

STMN: TIM (CR)

DS1: TX-IDLE (NA)

ML100T: DATA-CRC (MJ)

STMN: TIM-MON (MN)

DS1: TX-LOF (NR)

ML100T: FORCED-REQ (NA)

STMN: WKSWPR (NA)

DS1: TX-RAI (NA)

ML100T: GFP-CSF (MJ)

STMN: WTR (NA)

DS3: AIS (NR)

ML100T: GFP-LFD (MJ)

DS3: AS-CMD (NA)

ML100T: GFP-UP-MISMATCH (MJ)

DS3: AS-MT (NA)

ML100T: LINK-KEEPALIVE (CR)

TLINK: LMP-FAIL (MN)

DS3: DS3-MISM (NA)

ML100T: MAN-REQ (NA)

TRUNK: AIS (NR)

DS3: INC-ISD (NA)

ML100T: RPR-SD (NA)

TRUNK: AIS-L (NR)

DS3: LOF (CR)

ML100T: RPR-SF (NA)

TRUNK: ALS (NA)

DS3: LOS (CR)

ML100T: RPR-SPAN-MISMATCH (MJ)

TRUNK: AS-CMD (NA)

DS3: LPBKDS3FEAC (NA)

ML100T: RPRW (NA)

TRUNK: AS-MT (NA)

DS3: LPBKDS3FEAC-CMD (NA)

ML100T: TPTFAIL (MJ)

TRUNK: CARLOSS (MJ)

DS3: LPBKFACILITY (NA)

ML100T: WTR (NA)

TRUNK: DSP-COMM-FAIL (MJ)

DS3: LPBKTERMINAL (NA)

MLFX: AS-CMD (NA)

TRUNK: DSP-FAIL (MJ)

DS3: RAI (NA)

MLFX: AS-MT (NA)

TRUNK: RS-EOC (MN)

DS3: SD (NA)

MLFX: CARLOSS (MJ)

TRUNK: EOC-L (MN)

DS3: SF (NA)

MLFX: DATA-CRC (MJ)

TRUNK: FAILTOSW (NA)

DS3: TX-AIS (NR)

MLFX: FORCED-REQ (NA)

TRUNK: FAPS (NA)

E1000F: AS-CMD (NA)

MLFX: GFP-CSF (MJ)

TRUNK: FC-DE-NES (MJ)

E1000F: CARLOSS (MJ)

MLFX: GFP-LFD (MJ)

TRUNK: FC-NO-CREDITS (MJ)

E100T: AS-CMD (NA)

MLFX: GFP-UP-MISMATCH (MJ)

TRUNK: FEC-MISM (MJ)

E100T: CARLOSS (MJ)

MLFX: LINK-KEEPALIVE (CR)

TRUNK: FORCED-REQ-SPAN (NA)

E1: AIS (NR)

MLFX: MAN-REQ (NA)

TRUNK: GCC-EOC (MN)

E1: AS-CMD (NA)

MLFX: RPR-SD (NA)

TRUNK: GE-OOSYNC (CR)

E1: AS-MT (NA)

MLFX: RPR-SF (NA)

TRUNK: HELLO (MN)

E1: LOF (MJ)

MLFX: RPR-SPAN-MISMATCH (MJ)

TRUNK: HI-LASERBIAS (MN)

E1: LOS (MJ)

MLFX: RPRW (NA)

TRUNK: HI-RXPOWER (MN)

E1: LPBKFACILITY (NA)

MLFX: TPTFAIL (MJ)

TRUNK: HI-TXPOWER (MN)

E1: LPBKTERMINAL (NA)

MLFX: WTR (NA)

TRUNK: ILK-FAIL (CR)

E1: MS-DEG (NA)

MLMR: AS-CMD (NA)

TRUNK: ISIS-ADJ-FAIL (MN)

E1: MS-EXC (NA)

MLMR: AS-MT (NA)

TRUNK: LO-RXPOWER (MN)

E1: RAI (NA)

MLMR: CARLOSS (MJ)

TRUNK: LO-TXPOWER (MN)

E1: RCVR-MISS (MJ)

MLMR: CPP-INCAPABLE (NA)

TRUNK: LOCKOUT-REQ (NA)

E1: SSM-DUS (NA)

MLMR: FORCED-REQ (NA)

TRUNK: LOF (CR)

E1: SSM-FAIL (MN)

MLMR: GFP-CSF (MJ)

TRUNK: LOM (CR)

E1: SSM-OFF (NA)

MLMR: GFP-LFD (MJ)

TRUNK: LOS (CR)

E1: SSM-PRS (NA)

MLMR: GFP-UP-MISMATCH (MJ)

TRUNK: LOS-P (CR)

E1: SSM-RES (NA)

MLMR: LINK-KEEPALIVE (CR)

TRUNK: LPBKFACILITY (NA)

E1: SSM-SMC (NA)

MLMR: LPBKFACILITY (NA)

TRUNK: LPBKTERMINAL (NA)

E1: SSM-ST2 (NA)

MLMR: LPBKTERMINAL (NA)

TRUNK: MANUAL-REQ-SPAN (NA)

E1: SSM-ST3 (NA)

MLMR: MAN-REQ (NA)

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

E1: SSM-ST3E (NA)

MLMR: PEER-NORESPONSE (MN)

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

E1: SSM-ST4 (NA)

MLMR: PORT-MISMATCH (MJ)

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

E1: SSM-STU (NA)

MLMR: RPR-SD (NA)

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

E1: SYNC-FREQ (NA)

MLMR: RPR-SF (NA)

TRUNK: ODUK-AIS-PM (NR)

E1: TRMT (MJ)

MLMR: RPR-SPAN-MISMATCH (MJ)

TRUNK: ODUK-BDI-PM (NR)

E1: TRMT-MISS (MJ)

MLMR: TPTFAIL (MJ)

TRUNK: ODUK-LCK-PM (NR)

E1: TX-AIS (NR)

MLMR: WTR (NA)

TRUNK: ODUK-OCI-PM (NR)

E1: TX-LOF (NR)

MSUDC: AIS (NR)

TRUNK: ODUK-SD-PM (NA)

E1: TX-RAI (NA)

MSUDC: LOS (MN)

TRUNK: ODUK-SF-PM (NA)

E3: AIS (NR)

NE-SREF: FRCDSWTOINT (NA)

TRUNK: ODUK-TIM-PM (MJ)

E3: AS-CMD (NA)

NE-SREF: FRCDSWTOPRI (NA)

TRUNK: OTUK-AIS (NR)

E3: AS-MT (NA)

NE-SREF: FRCDSWTOSEC (NA)

TRUNK: OTUK-BDI (NR)

E3: FE-AIS (NA)

NE-SREF: FRCDSWTOTHIRD (NA)

TRUNK: OTUK-IAE (MN)

E3: FE-E1-MULTLOS (NA)

NE-SREF: FRNGSYNC (NA)

TRUNK: OTUK-LOF (CR)

E3: FE-E1-NSA (NA)

NE-SREF: FSTSYNC (NA)

TRUNK: OTUK-SD (NA)

E3: FE-E1-SA (NA)

NE-SREF: HLDOVRSYNC (NA)

TRUNK: OTUK-SF (NA)

E3: FE-E1-SNGLLOS (NA)

NE-SREF: MANSWTOINT (NA)

TRUNK: OTUK-TIM (CR)

E3: FE-E3-NSA (NA)

NE-SREF: MANSWTOPRI (NA)

TRUNK: OUT-OF-SYNC (MJ)

E3: FE-E3-SA (NA)

NE-SREF: MANSWTOSEC (NA)

TRUNK: PROV-MISMATCH (MJ)

E3: FE-EQPT-NSA (NA)

NE-SREF: MANSWTOTHIRD (NA)

TRUNK: PTIM (MJ)

E3: FE-IDLE (NA)

NE-SREF: SSM-LNC (NA)

TRUNK: RFI (NR)

E3: FE-LOF (NA)

NE-SREF: SSM-PRC (NA)

TRUNK: RFI-L (NR)

E3: FE-LOS (NA)

NE-SREF: SSM-SDH-TN (NA)

TRUNK: SD (NA)

E3: INC-ISD (NA)

NE-SREF: SSM-SETS (NA)

TRUNK: SD-L (NA)

E3: LOS (CR)

NE-SREF: SSM-STU (NA)

TRUNK: SF (NA)

E3: LPBKDS3FEAC-CMD (NA)

NE-SREF: SSM-TNC (NA)

TRUNK: SF-L (NA)

E3: LPBKE1FEAC (NA)

NE-SREF: SWTOPRI (NA)

TRUNK: SIGLOSS (MJ)

E3: LPBKE3FEAC (NA)

NE-SREF: SWTOSEC (NA)

TRUNK: SQUELCHED (NA)

E3: LPBKFACILITY (NA)

NE-SREF: SWTOTHIRD (NA)

TRUNK: SSM-DUS (NA)

E3: LPBKTERMINAL (NA)

NE-SREF: SYNCPRI (MJ)

TRUNK: SSM-FAIL (MN)

E3: MS-DEG (NA)

NE-SREF: SYNCSEC (MN)

TRUNK: SSM-LNC (NA)

E3: MS-EXC (NA)

NE-SREF: SYNCTHIRD (MN)

TRUNK: SSM-OFF (NA)

E3: TX-AIS (NR)

NE: APC-DISABLED (NA)

TRUNK: SSM-PRC (NA)

E3: TX-RAI (NA)

NE: APC-END (NA)

TRUNK: SSM-PRS (NA)

E4: AIS (NR)

NE: AS-CMD (NA)

TRUNK: SSM-RES (NA)

E4: AS-CMD (NA)

NE: AUD-LOG-LOSS (NA)

TRUNK: SSM-SDH-TN (NA)

E4: AS-MT (NA)

NE: AUD-LOG-LOW (NA)

TRUNK: SSM-SETS (NA)

E4: LOF (CR)

NE: DATAFLT (MN)

TRUNK: SSM-SMC (NA)

E4: LOS (CR)

NE: DBOSYNC (MJ)

TRUNK: SSM-ST2 (NA)

E4: LPBKFACILITY (NA)

NE: DUP-IPADDR (MN)

TRUNK: SSM-ST3 (NA)

E4: LPBKTERMINAL (NA)

NE: DUP-NODENAME (MN)

TRUNK: SSM-ST3E (NA)

E4: MS-DEG (NA)

NE: ETH-LINKLOSS (NA)

TRUNK: SSM-ST4 (NA)

E4: MS-EXC (NA)

NE: HITEMP (CR)

TRUNK: SSM-STU (NA)

ENVALRM: EXT (MN)

NE: I-HITEMP (CR)

TRUNK: SSM-TNC (NA)

EQPT: ALS-DISABLED (NA)

NE: INTRUSION-PSWD (NA)

TRUNK: SYNC-FREQ (NA)

EQPT: APC-DISABLED (NA)

NE: LAN-POL-REV (NA)

TRUNK: SYNCLOSS (MJ)

EQPT: AS-CMD (NA)

NE: SNTP-HOST (MN)

TRUNK: TIM (CR)

EQPT: AS-MT (NA)

NE: SYSBOOT (MJ)

TRUNK: TIM-MON (MN)

EQPT: AUTORESET (MN)

NE: TEMP-MISM (NA)

TRUNK: TRAIL-SIGNAL-FAIL (NA)

EQPT: BKUPMEMP (CR)

OCH: APC-DISABLED (NA)

TRUNK: UNC-WORD (NA)

EQPT: CARLOSS (MJ)

OCH-TERM: FDI (NA)

TRUNK: UT-COMM-FAIL (MJ)

EQPT: CLDRESTART (NA)

OCH-TERM: OCHTERM-INC (NA)

TRUNK: UT-FAIL (MJ)

EQPT: COMIOXC (CR)

OCH-TERM: OPWR-HDEG (MN)

TRUNK: WTR (NA)

EQPT: COMM-FAIL (MN)

OCH-TERM: OPWR-LDEG (MN)

TRUNK: WVL-MISMATCH (MJ)

EQPT: CONTBUS-A-18 (MN)

OCH-TERM: OPWR-LFAIL (CR)

VCG: LOA (CR)

EQPT: CONTBUS-B-18 (MN)

OCH-TERM: PARAM-MISM (NA)

VCG: VCG-DEG (NA)

EQPT: CONTBUS-DISABLED (CR)

VCG: VCG-DOWN (NA)

EQPT: CONTBUS-IO-A (MN)

VCMON-HP: AU-AIS (NR)

EQPT: CONTBUS-IO-B (MN)

VCMON-HP: AU-LOP (CR)

EQPT: CTNEQPT-MISMATCH (NA)

VCMON-HP: AUTOSW-AIS-SNCP (NR)

EQPT: CTNEQPT-PBPROT (CR)

OCH: APC-CORR-SKIPPED (MN)

VCMON-HP: AUTOSW-LOP-SNCP (NA)

EQPT: CTNEQPT-PBWORK (CR)

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

EQPT: EQPT (CR)

OCH: AS-CMD (NA)

VCMON-HP: AUTOSW-SDBER-SNCP (NA)

EQPT: EQPT-DIAG (CR)

OCH: AS-MT (NA)

VCMON-HP: AUTOSW-SFBER-SNCP (NA)

EQPT: ERROR-CONFIG (MN)

OCH: FDI (NA)

VCMON-HP: AUTOSW-UNEQ-SNCP (NA)

EQPT: EXCCOL (MN)

OCH: LOS-O (MN)

VCMON-HP: FAILTOSW-PATH (NA)

EQPT: FAILTOSW (NA)

OCH: LOS-P (CR)

VCMON-HP: FORCED-REQ (NA)

EQPT: FAPS-CONFIG-MISMATCH (MN)

OCH: OPWR-HDEG (MN)

VCMON-HP: HP-DEG (NA)

EQPT: FORCED-REQ (NA)

OCH: OPWR-HFAIL (CR)

VCMON-HP: HP-EXC (NA)

EQPT: FP-LINK-LOSS (MN)

OCH: OPWR-LDEG (MN)

VCMON-HP: HP-PLM (CR)

EQPT: FTA-MISMATCH (NA)

OCH: OPWR-LFAIL (CR)

VCMON-HP: HP-RFI (NR)

EQPT: HI-LASERBIAS (MN)

OCH: PARAM-MISM (NA)

VCMON-HP: HP-TIM (MN)

EQPT: HI-LASERTEMP (MN)

OCH: PORT-FAIL (CR)

VCMON-HP: HP-UNEQ (CR)

EQPT: HI-TXPOWER (MN)

OCH: TRAIL-SIGNAL-FAIL (NA)

VCMON-HP: LOCKOUT-REQ (NA)

EQPT: HITEMP (MN)

OCH: VOA-HDEG (MN)

VCMON-HP: LOM (CR)

EQPT: IMPROPRMVL (CR)

OCH: VOA-HFAIL (CR)

VCMON-HP: LPBKCRS (NA)

EQPT: INHSWPR (NA)

OCH: VOA-LDEG (MN)

VCMON-HP: MAN-REQ (NA)

EQPT: INHSWWKG (NA)

OCH: VOA-LFAIL (CR)

VCMON-HP: ROLL (NA)

EQPT: IOSCFGCOPY (NA)

OCHNC-CONN: OCHNC-INC (NA)

VCMON-HP: ROLL-PEND (NA)

EQPT: LO-LASERBIAS (MN)

OMS: APC-CORR-SKIPPED (MN)

VCMON-HP: WKSWPR (NA)

EQPT: LO-LASERTEMP (MN)

OMS: APC-DISABLED (NA)

VCMON-HP: WTR (NA)

EQPT: LO-TXPOWER (MN)

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

VCMON-LP: AUTOSW-AIS-SNCP (NR)

EQPT: LOCKOUT-REQ (NA)

OMS: AS-CMD (NA)

VCMON-LP: AUTOSW-LOP-SNCP (NA)

EQPT: MAN-REQ (NA)

OMS: AS-MT (NA)

EQPT: MANRESET (NA)

OMS: LOS-O (MN)

VCMON-LP: AUTOSW-SDBER-SNCP (NA)

EQPT: MEA (CR)

OMS: LOS-P (CR)

VCMON-LP: AUTOSW-SFBER-SNCP (NA)

EQPT: MEM-GONE (MJ)

OMS: OPWR-HDEG (MN)

VCMON-LP: AUTOSW-UNEQ-SNCP (NA)

EQPT: MEM-LOW (MN)

OMS: OPWR-HFAIL (CR)

VCMON-LP: FAILTOSW-PATH (NA)

EQPT: NO-CONFIG (NA)

OMS: OPWR-LDEG (MN)

VCMON-LP: FORCED-REQ (NA)

EQPT: PROTNA (MN)

OMS: OPWR-LFAIL (CR)

VCMON-LP: LOCKOUT-REQ (NA)

EQPT: PWR-FAIL-A (MN)

OMS: PARAM-MISM (NA)

VCMON-LP: LP-DEG (NA)

EQPT: PWR-FAIL-B (MN)

OMS: PMI (NA)

VCMON-LP: LP-EXC (NA)

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

OMS: VOA-HDEG (MN)

VCMON-LP: LP-PLM (MJ)

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

OMS: VOA-HFAIL (CR)

VCMON-LP: LP-RFI (NR)

EQPT: RUNCFG-SAVENEED (NA)

OMS: VOA-LDEG (MN)

VCMON-LP: LP-TIM (MJ)

EQPT: SFTWDOWN (MN)

OMS: VOA-LFAIL (CR)

VCMON-LP: LP-UNEQ (MJ)

EQPT: SW-MISMATCH (NA)

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

VCMON-LP: MAN-REQ (NA)

EQPT: SWMTXMOD-PROT (CR)

OTS: APC-CORR-SKIPPED (MN)

VCMON-LP: ROLL (NA)

EQPT: SWMTXMOD-WORK (CR)

OTS: APC-DISABLED (NA)

VCMON-LP: ROLL-PEND (NA)

EQPT: WKSWPR (NA)

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

VCMON-LP: TU-AIS (NR)

EQPT: WTR (NA)

OTS: AS-CMD (NA)

VCMON-LP: TU-LOP (MJ)

ESCON: ALS (NA)

OTS: AS-MT (NA)

VCMON-LP: WKSWPR (NA)

ESCON: AS-CMD (NA)

OTS: AWG-DEG (MN)

VCMON-LP: WTR (NA)

ESCON: AS-MT (NA)

OTS: AWG-FAIL (CR)

VCTRM-HP: AS-MT-OOG (NA)

ESCON: FAILTOSW (NA)

OTS: AWG-OVERTEMP (CR)

VCTRM-HP: AU-AIS (NR)

ESCON: FORCED-REQ-SPAN (NA)

OTS: AWG-WARM-UP (NA)

VCTRM-HP: AU-LOF (CR)

ESCON: HI-LASERBIAS (MN)

OTS: DCU-LOSS-FAIL (MN)

VCTRM-HP: AU-LOP (CR)

ESCON: HI-RXPOWER (MN)

OTS: LASERBIAS-DEG (MN)

VCTRM-HP: HP-DEG (NA)

ESCON: HI-TXPOWER (MN)

OTS: LOS (CR)

VCTRM-HP: HP-ENCAP-MISMATCH (CR)

ESCON: LO-RXPOWER (MN)

OTS: LOS-O (MN)

VCTRM-HP: HP-EXC (NA)

ESCON: LO-TXPOWER (MN)

OTS: LOS-P (CR)

VCTRM-HP: HP-PLM (CR)

ESCON: LOCKOUT-REQ (NA)

OTS: MT-OCHNC (NA)

VCTRM-HP: HP-RFI (NR)

ESCON: LOS (CR)

OTS: OPWR-HDEG (MN)

VCTRM-HP: HP-TIM (CR)

ESCON: LPBKFACILITY (NA)

OTS: OPWR-HFAIL (CR)

VCTRM-HP: HP-UNEQ (CR)

ESCON: LPBKTERMINAL (NA)

OTS: OPWR-LDEG (MN)

VCTRM-HP: LCAS-CRC (NA)

ESCON: MANUAL-REQ-SPAN (NA)

OTS: OPWR-LFAIL (CR)

VCTRM-HP: LCAS-RX-DNU (NA)

ESCON: SIGLOSS (MJ)

OTS: OSRION (NA)

VCTRM-HP: LCAS-RX-FAIL (NA)

ESCON: SQUELCHED (NA)

OTS: PARAM-MISM (NA)

VCTRM-HP: LCAS-RX-GRP-ERR (NA)

ESCON: WKSWPR (NA)

OTS: PMI (NA)

VCTRM-HP: LCAS-TX-ADD (NA)

ESCON: WTR (NA)

OTS: SH-IL-VAR-DEG-HIGH (MN)

VCTRM-HP: LCAS-TX-DNU (NA)

EXT-SREF: FRCDSWTOPRI (NA)

OTS: SH-IL-VAR-DEG-LOW (MN)

VCTRM-HP: LOM (MJ)

EXT-SREF: FRCDSWTOSEC (NA)

OTS: SHUTTER-OPEN (NA)

VCTRM-HP: LPBKCRS (NA)

EXT-SREF: FRCDSWTOTHIRD (NA)

OTS: SPAN-NOT-MEASURED (NA)

VCTRM-HP: OOU-TPT (NA)

EXT-SREF: MANSWTOPRI (NA)

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

VCTRM-HP: ROLL (NA)

EXT-SREF: MANSWTOSEC (NA)

OTS: VOA-HDEG (MN)

VCTRM-HP: ROLL-PEND (NR)

EXT-SREF: MANSWTOTHIRD (NA)

OTS: VOA-HFAIL (CR)

VCTRM-HP: SQM (CR)

EXT-SREF: SWTOPRI (NA)

OTS: VOA-LDEG (MN)

VCTRM-LP: AS-MT-OOG (NA)

EXT-SREF: SWTOSEC (NA)

OTS: VOA-LFAIL (CR)

VCTRM-LP: LCAS-CRC (NA)

EXT-SREF: SWTOTHIRD (NA)

PPM: AS-CMD (NA)

VCTRM-LP: LCAS-RX-DNU (NA)

EXT-SREF: SYNCPRI (MN)

PPM: AS-MT (NA)

VCTRM-LP: LCAS-RX-FAIL (NA)

EXT-SREF: SYNCSEC (MN)

PPM: EQPT (CR)

VCTRM-LP: LCAS-RX-GRP-ERR (NA)

EXT-SREF: SYNCTHIRD (MN)

PPM: HI-LASERBIAS (MN)

VCTRM-LP: LCAS-TX-ADD (NA)

FAN: EQPT-MISS (CR)

PPM: HI-LASERTEMP (MN)

VCTRM-LP: LCAS-TX-DNU (NA)

FAN: FAN (CR)

PPM: HI-TXPOWER (MN)

VCTRM-LP: LOM (MJ)

FAN: MEA (CR)

PPM: IMPROPRMVL (CR)

VCTRM-LP: LP-DEG (NA)

FAN: MFGMEM (CR)

PPM: LO-LASERBIAS (MN)

VCTRM-LP: LP-ENCAP-MISMATCH (CR)

FC: ALS (NA)

PPM: LO-LASERTEMP (MN)

VCTRM-LP: LP-EXC (NA)

FC: AS-CMD (NA)

PPM: LO-TXPOWER (MN)

VCTRM-LP: LP-PLM (MJ)

FC: AS-MT (NA)

PPM: MEA (CR)

VCTRM-LP: LP-RFI (NR)

FC: CARLOSS (MJ)

PPM: MFGMEM (CR)

VCTRM-LP: LP-TIM (MJ)

FC: FAILTOSW (NA)

PPM: NON-CISCO-PPM (NR)

VCTRM-LP: LP-UNEQ (MJ)

FC: FC-DE-NES (MJ)

PPM: PROV-MISMATCH (MN)

VCTRM-LP: OOU-TPT (NA)

FC: FC-NO-CREDITS (MJ)

PPM: UNQUAL-PPM (NR)

VCTRM-LP: ROLL (NA)

FC: FORCED-REQ-SPAN (NA)

PWR: AS-CMD (NA)

VCTRM-LP: ROLL-PEND (NA)

FC: GE-OOSYNC (CR)

PWR: BAT-FAIL (MJ)

VCTRM-LP: SQM (MJ)

FC: HI-LASERBIAS (MN)

PWR: EHIBATVG (MJ)

VCTRM-LP: TU-AIS (NR)

FC: HI-RXPOWER (MN)

PWR: ELWBATVG (MJ)

VCTRM-LP: TU-LOP (MJ)


2.5  Trouble Notifications

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

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

2.5.1  Alarm Characteristics

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

2.5.2  Condition Characteristics

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

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


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


2.5.3  Severities

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

A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs immediate correction, such as an LOS on a trunk port or STM signal.

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

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

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

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

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

2.5.4  Alarm Hierarchy

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

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

Table 2-9 Path Alarm Hierarchy

Priority
Condition Type

Highest

AU-AIS

AU-LOP

HP-UNEQ

Lowest

HP-TIM


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

Table 2-10 Facility Alarm Hierarchy

Priority
Condition Type

Highest

LOS

LOF

MS-AIS

MS-EXC1

MS-DEG1

MS-RDI1

RS-TIM

AU-AIS

AU-LOP

HP-EXC1

HP-DEG1

HP-UNEQ

HP-TIM

HP-PLM1

1 This alarm is not currently used in the platform.


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

Table 2-11 Near-End Alarm Hierarchy

Priority
Condition Type

Highest

LOS

LOF

MS-AIS

AU-AIS1

AU-LOP2

HP-UNEQ

HP-TIM

HP-PLM

TU-AIS1

TU-LOP2

LP-UNEQ3

LP-PLM3

Lowest

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

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

2 AU-LOP is also higher priority than the far-end failure MS-RFI, which does not affect the detection of any near-end failures. Similarly, TU-LOP is higher priority than LP-RF.

3 This alarm is not used in this platform in this release.


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

Table 2-12 Far-End Alarm Hierarchy

Priority
Condition Type

Highest

MS-RDI1

HP-RFI

Lowest

LP-RFI1

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


2.5.5  Service Effect

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

2.5.6  States

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

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

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

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

2.6  Safety Summary

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


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

Some troubleshooting procedures require installation or removal of STM-64 cards. In these instances, pay close attention to the following warnings.


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

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

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

Warning Class 1 laser product. Statement 1008

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

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

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

2.7  Alarm Procedures

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


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



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



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


2.7.1  AIS

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

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

DWDM Logical Object: TRUNK

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

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


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


Clear the AIS Condition


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

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

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


2.7.2  AIS-L

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

2.7.3  ALS

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

2.7.4  ALS-DISABLED

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

2.7.5  AMPLI-INIT

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

2.7.6  APC-CORR-SKIPPED

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

2.7.7  APC-DISABLED

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

2.7.8  APC-END

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

2.7.9  APC-OUT-OF-RANGE

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

2.7.10  APC-WRONG-GAIN

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

2.7.11  APSB

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

SDH Logical Object: STMN

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

Clear the APSB Alarm


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

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


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


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


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


2.7.12  APSCDFLTK

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

SDH Logical Object: STMN

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

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

Clear the APSCDFLTK Alarm


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

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

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

Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "EXCCOL" alarm on page 2-92.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide provides a procedure for fibering MS-SPRings.

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

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

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

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


2.7.13  APSC-IMP

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

SDH Logical Object: STMN

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

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


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



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



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



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

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

Clear the APSC-IMP Alarm


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


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

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

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

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

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

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


2.7.14  APSCINCON

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

SDH Logical Object: STMN

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

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


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

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


2.7.15  APSCM

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

SDH Logical Object: STMN

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

Unused code in bits 6 through 8 of byte K2.

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

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

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


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

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

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

Clear the APSCM Alarm


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


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

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

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


2.7.16  APSCNMIS

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

SDH Logical Object: STMN

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

Clear the APSCNMIS Alarm


Step 1 Complete the "Identify an MS-SPRing Ring Name or Node ID Number" procedure for each node to verify that each node has a unique node ID number.

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

Step 3 Click Close in the Ring Map dialog box.

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


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



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


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

Step 6 Complete the "Clear an MS-SPRing External Switching Command" procedure to clear the lockout.

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


2.7.17  APS-INV-PRIM

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

2.7.18  APS-PRIM-FAC

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

2.7.19  APS-PRIM-SEC-MISM

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

2.7.20  AS-CMD

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

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

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

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


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


Clear the AS-CMD Condition


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Step 6 Locate the row for the reported card slot.

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

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

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

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

c. Click Apply.

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

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

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

c. Click Apply.

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


2.7.21  AS-MT

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

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

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

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

Clear the AS-MT Condition


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

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


2.7.22  AS-MT-OOG

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

SDH Logical Objects: VCTRM-HP, VCTRM-LP

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

Clear the AS-MT-OOG Condition


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

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


2.7.23  AU-AIS

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

SDH Logical Objects: VCMON-HP, VCTRM-HP

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

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

Clear the AU-AIS Condition


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

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

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


2.7.24  AUD-LOG-LOSS

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

SDH Logical Object: NE

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

Clear the AUD-LOG-LOSS Condition


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

Step 2 Click Retrieve.

Step 3 Click Archive.

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

Step 5 Enter a name in the File Name field.

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

Step 6 Click Save.

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

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


2.7.25  AUD-LOG-LOW

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

SDH Logical Object: NE

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


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


2.7.26  AU-LOF

Critical (CR), Service-Affecting (SA)

SDH Logical Object: VCTRM-HP

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

Clear the AU-LOF Alarm


Step 1 Complete the "Clear the LOF (TRUNK) Alarm" procedure, which is located in the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

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


2.7.27  AU-LOP

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

SDH Logical Objects: VCMON-HP, VCTRM-HP

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


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

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

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


Clear the AU-LOP Alarm


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

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

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

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

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

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


2.7.28  AUTOLSROFF

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

SDH Logical Object: STMN

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


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

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

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

Clear the AUTOLSROFF Alarm


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

Figure 2-1 shows the shelf LCD panel.

Figure 2-1 Shelf LCD Panel

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

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


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


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


2.7.29  AUTONEG-RFI

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

SDH Logical Object: ML1000

The autonegotiation remote fault indication (RFI) indicates that an ML1000 Gigabit Ethernet port cannot detect its far-end link partner. This is typically caused by a far-end port shutdown or a unidirectional fiber cut. The partner node is likely raising a CARLOSS alarm.

AUTONEG-RFI may also be caused by misconfigured autonegotiation parameters. This causes more of a soft failure as opposed to CARLOSS, which is typically caused by a failure like a loss of light or optical fiber. The alarm clears the partner node is detected.


Note The far end of an Ethernet link is usually a switch or router that does not use an ONS management system.


Clear the AUTONEG-RFI Alarm


Step 1 Check for a "CARLOSS (EQPT)" alarm on page 2-62, or "CARLOSS (ML100T, ML1000, MLFX)" alarm on page 2-66, at the partner node. If the alarm exists there, follow the appropriate clearing procedure in this chapter.

Step 2 If the alarm does not clear or if there is no far-end CARLOSS, check the near-end Gigabit Ethernet port autonegotiation settings:

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

b. Click the IOS tab, then click Open IOS Connection.

c. In Privileged Executive mode, enter the following command:

router# show interface gigabitethernet 0
 
   

d. View the command output and record the autonegotiation setting, such as the following example:

Full-duplex, 1000Mb/s, Gbic not connected, Auto-negotiation
output flow-control is off, input flow-control is on
 
   

Step 3 View the autonegotiation configuration for the partner node. If it is ONS equipment, follow the previous step for this node. If the node is different vendor client equipment, follow that equipment documentation to obtain the information.

Step 4 If the alarm does not clear, check for any fiber breaks such as on the transmit cable from the partner node to the near-end node.

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


2.7.30  AUTORESET

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

SDH Logical Object: EQPT

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

Resets performed during a software upgrade also prompt the condition. This condition clears automatically when the card finishes resetting.

Clear the AUTORESET Alarm


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

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


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


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


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


2.7.31  AUTOSW-AIS-SNCP

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

SDH Logical Objects: VCMON-HP, VCMON-LP

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


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


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

Clear the AUTOSW-AIS-SNCP Condition


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

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


2.7.32  AUTOSW-LOP-SNCP

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

SDH Logical Objects: VCMON-HP, VCMON-LP

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


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


Clear the AUTOSW-LOP-SNCP Alarm


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

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


2.7.33  AUTOSW-SDBER-SNCP

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

SDH Logical Object: VCMON-HP, VCMON-LP

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


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


Clear the AUTOSW-SDBER-SNCP Condition


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

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


2.7.34  AUTOSW-SFBER-SNCP

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

SDH Logical Object: VCMON-HP, VCMON-LP

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


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


Clear the AUTOSW-SFBER-SNCP Condition


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

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


2.7.35  AUTOSW-UNEQ-SNCP (VCMON-HP)

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

SDH Logical Object: VCMON-HP

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


Warning Class 1 laser product. Statement 1008

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

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

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

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


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


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

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


2.7.36  AUTOSW-UNEQ-SNCP (VCMON-LP)

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

SDH Logical Object: VCMON-LP

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


Warning Class 1 laser product. Statement 1008

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

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

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


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


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

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

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

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

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

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

Step 7 If the condition does not clear, verify that all circuits terminating in the reporting card are active by completing the following steps:

a. In node view, click the Circuits tab.

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

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

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

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

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

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


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

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

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

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


2.7.37  AWG-DEG

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

2.7.38  AWG-FAIL

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

2.7.39  AWG-OVERTEMP

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

2.7.40  AWG-WARM-UP

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

2.7.41  BAT-FAIL

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

SDH Logical Object: PWR

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

Clear the BATFAIL Alarm


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

Step 2 Remove the power cable from the faulty supply.

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


2.7.42  BKUPMEMP

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


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


SDH Logical Object: EQPT

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

Failure to format a flash partition.

Failure to write a file to a flash partition.

Problem at the driver level.

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

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

Clear the BKUPMEMP Alarm


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

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

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

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


2.7.43  CARLOSS (CEMR, CE100T, CE1000)

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

SDH Logical Objects: CEMR, CE100T, CE1000

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


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


Clear the CARLOSS (CEMR, CE100T, CE1000) 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 (CEMR, CE100T, CE1000)" alarm on page 2-244.

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


2.7.44  CARLOSS (E100T, E1000F)

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

SDH Logical Objects: E100T, E1000F

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

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


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


Clear the CARLOSS (E100T, E1000F) Alarm


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


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

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

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

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

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

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

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


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


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

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

If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm could be a result of mismatched circuit sizes in the set up of the manual cross-connect. Determine this by completing the following steps. If the Ethernet circuit is not part of a manual cross-connect, the following steps do not apply.

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

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

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

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

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

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

Click the Circuits tab.

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

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

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

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


2.7.45  CARLOSS (EQPT)

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

SDH Logical Object: EQPT

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

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

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


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


Clear the CARLOSS (EQPT) Alarm


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

a. Double-click the reporting card.

b. Click the Provisioning > Pluggable Port Modules tabs.

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

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


Note For more information about provisioning PPMs, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.


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

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

Step 4 Using optical test equipment, verify that proper receive levels are achieved. (For specific procedures to use the test set equipment, consult the manufacturer.)

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

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

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

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

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


2.7.46  CARLOSS (FC)

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

2.7.47  CARLOSS (G1000)

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

SDH Logical Object: G1000

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

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

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

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

Refer to the Cisco ONS 15454 SDH Reference Manual for a description of the G-Series card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-246 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 Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the CARLOSS (G1000) Alarm


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


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

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

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

Step 4 Verify that optical receive levels are within the normal range. The correct specifications are listed in the "Optical Card Transmit and Receive Levels" section.

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

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

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

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

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

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

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


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


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

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

b. Click the Maintenance > Loopback tabs.

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

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

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

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

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


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


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

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

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

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

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

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

Click the Circuits tab.

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

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

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

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

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

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


2.7.48  CARLOSS (GE)

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

2.7.49  CARLOSS (ISC)

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

2.7.50  CARLOSS (ML100T, ML1000, MLFX)

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

SDH Logical Objects: ML100T, ML1000, MLFX

A Carrier Loss alarm on the ML-Series Ethernet card is the data equivalent of the "LOS (STM1E, STMN)" alarm on page 2-162. 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 Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the CARLOSS (ML100T, ML1000, MLFX) Alarm


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

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

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

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

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

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

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


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


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


2.7.51  CARLOSS (TRUNK)

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

2.7.52  CASETEMP-DEG

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

2.7.53  CLDRESTART

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

SDH Logical Object: EQPT

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

Clear the CLDRESTART Condition


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


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

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

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


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


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


2.7.54  COMIOXC

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

SDH Logical Object: EQPT

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

Clear the COMIOXC Alarm


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

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

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

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

Step 5 If the alarm does not clear, complete the "Physically Replace an In-Service Cross-Connect Card" procedure for the reporting cross-connect card or complete the "Physically Replace a Traffic Card" procedure on the card in which the alarm is reported.


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


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


2.7.55  COMM-FAIL

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

SDH Logical Object: EQPT

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

Clear the COMM-FAIL Alarm


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

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


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


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


2.7.56  CONTBUS-A-18

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

SDH Logical Object: EQPT

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

Clear the CONTBUS-A-18 Alarm


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


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

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

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

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


2.7.57  CONTBUS-B-18

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

SDH Logical Object: EQPT

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

Clear the CONTBUS-B-18 Alarm


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

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

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

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


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

2.7.58  CONTBUS-DISABLED

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

SDH Logical Object: EQPT

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

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

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


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

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

Clear the CONTBUS-DISABLED Alarm


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

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


2.7.59  CONTBUS-IO-A

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

SDH Logical Object: EQPT

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

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

Clear the CONTBUS-IO-A Alarm


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

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

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

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

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

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

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

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

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


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

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


2.7.60  CONTBUS-IO-B

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

SDH Logical Object: EQPT

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

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

Clear the CONTBUS-IO-B Alarm


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

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

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

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

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

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

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

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

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


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

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


2.7.61  CPP-INCAPABLE

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

SDH Logical Object: MLMR

The Card Port Protection Incapable alarm indicates that the ML-MR-10 card or port is unable to provide protection. This condition occurs when the Resilient Packet Ring (RPR) interface on the ML-MR-10 card is down, or when the CPP peer slot number is not configured from the Cisco IOS command line interface or the protection group is disabled.


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


Clear the CPP-INCAPABLE Alarm


Step 1 Ensure that the RPR interface is not in the administratively shutdown state.

Step 2 Ensure that the RPR interface is in the line protocol UP state.

Step 3 Ensure that the CPP peer slot is configured in Cisco IOS under the protection group configuration.

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


2.7.62  CTNEQPT-MISMATCH

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

SDH Logical Object: EQPT

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


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



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



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


Clear the CTNEQPT-MISMATCH Condition


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

a. In node view, click the Inventory tab.

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

The Eqpt Type column contains the equipment that is provisioned in the slot. The Actual Eqpt Type contains the equipment that is physically present in the slot. For example, Slot 8 could be provisioned for an XCVT card, which is shown in the Eqpt Type column, but a different cross-connect card could be physically present in the slot. (This card would be shown in the Actual Eqpt Type column.)

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

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


2.7.63  CTNEQPT-PBPROT

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

SDH Logical Object: EQPT

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


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



Caution Software update on a standby TCC2/TCC2P card 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 card.


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

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


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

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

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

If the cross-connect reset is not complete and error-free or if the TCC2/TCC2P card reboots automatically, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.

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

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

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

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

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

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

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

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


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


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


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


2.7.64  CTNEQPT-PBWORK

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

SDH Logical Object: EQPT

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


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


Clear the CTNEQPT-PBWORK Alarm


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

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

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


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


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

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

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

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

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

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

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

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

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

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

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


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


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

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


2.7.65  DATA-CRC

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

SDH Logical Objects: CE100T, ML100T, ML1000, MLFX

The data cyclic redundancy check (CRC) Bad Packet Count Exceeds Threshold alarm indicates that Cisco proprietary ring-wrapping (RPR) has been triggered for an ML-Series card in HDLC mode, but no SDH- or data-level alarm is raised along with the "RPRW" alarm on page 2-217 to indicate the failure.

In a typical scenario that triggers Cisco proprietary RPR, the errored node raises the "RPRW" alarm on page 2-217 and SDH or data errors (such as TPTFAIL). If, however, a POS port is placed in down administrative state, the card will raise an RPRW without raising any SDH B3 bit alarms or data alarms. The DATA-CRC alarm accompanies this instance of RPRW to indicate the signal interruption.

Clear the DATA-CRC Alarm


Step 1 Determine whether the "RPRW" alarm on page 2-217 is raised on the ring. If so, clear it using the appropriate trouble-clearing procedure in this chapter.

Step 2 If the DATA-CRC alarm does not clear, check whether the alarmed card POS port is in the Down administrative state:

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

b. Click the Provisioning > POS Ports tabs.

c. View the port's setting in the Admin State column. If it is Down, verify that both POS ports are properly configured. Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide for configuration information.

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


2.7.66  DATAFLT

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

SDH Logical Object: NE

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


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

Clear the DATAFLT Alarm


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

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


2.7.67  DBOSYNC

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

SDH Logical Object: NE

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


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

Clear the DBOSYNC Alarm


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

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

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

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

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

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


2.7.68  DCU-LOSS-FAIL

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

2.7.69  DISCONNECTED

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

SDH Logical Object: SYSTEM

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

Clear the DISCONNECTED Alarm


Step 1 Restart the CTC application.

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


2.7.70  DS3-MISM

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

SDH Logical Object: DS3

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

Clear the DS3-MISM Condition


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

Step 2 Click the Provisioning > Line tabs.

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

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

Step 5 Click Apply.

Step 6 If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 SDH matches the expected incoming signal. For specific procedures to use the test set equipment, consult the manufacturer.

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


2.7.71  DSP-COMM-FAIL

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

2.7.72  DSP-FAIL

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

2.7.73  DUP-IPADDR

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

SDH Logical Object: NE

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

Clear the DUP-IPADDR Alarm


Step 1 Isolate the alarmed node from the other node having the same address by completing the following steps:

a. Connect to the alarmed node using the Craft port on the ONS 15454 SDH chassis.

b. Begin a CTC session.

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

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

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

Step 4 Click Apply.

Step 5 Restart any CTC sessions that are logged into either of the formerly duplicated node IDs. (For procedures to log in or log out, refer to the "Set Up PC and Log Into the GUI" chapter in the Cisco ONS 15454 SDH Procedure Guide.)

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


2.7.74  DUP-NODENAME

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

SDH Logical Object: NE

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

Clear the DUP-NODENAME Alarm


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

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

Step 3 Click Apply.

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


2.7.75  DUP-SHELF-ID

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

2.7.76  EHIBATVG

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

SDH Logical Object: PWR

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

Clear the EHIBATVG Alarm


Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying the battery leads.

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


2.7.77  ELWBATVG

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

SDH Logical Object: PWR

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

Clear the ELWBATVG Alarm


Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying the battery leads.

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


2.7.78  RS-EOC

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

SDH Logical Objects: STMN

DWDM Logical Object: TRUNK

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

The RS-DCC consists of three bytes, D1 through D3, in the SDH overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the SDH section overhead to communicate network management information.


Warning Class 1 laser product. Statement 1008

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

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

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

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

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



Note For information about DWDM cards, refer to the Cisco ONS 15454 DWDM Reference Manual.


Clear the RS-EOC Alarm


Step 1 If the "LOS (DS1, DS3)" alarm on page 2-158 is also reported, complete the "Clear the LOS (STM1E, STMN) Alarm" procedure.

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

Step 3 If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry RS-DCC traffic. If they are not, correct them. For more information about STM-N fiber connections and terminations, refer to the "Install Cards and Fiber-Optic Cable" chapter in the Cisco ONS 15454 SDH Procedure Guide. For more information about OSCM fiber connections and terminations, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide.


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

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

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

Step 5 Repeat Step 4 at the adjacent nodes.

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

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

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

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

c. For an STM-N card, click the Provisioning > Line tabs. For the OSCM card, click the Provisioning > STM-1 Line tabs.

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

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


Note If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.


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


Caution Using an optical test set disrupts service on an STM-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

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

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

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

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

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

Step 11 If the TCC2/TCC2P card reset does not clear the alarm, delete the problematic RS-DCC termination by completing the following steps:

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

b. Click the Provisioning > Comm Channels > RS-DCC tabs.

c. Highlight the problematic DCC termination.

d. Click Delete.

e. Click Yes in the Confirmation Dialog box.

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

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

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


2.7.79  EQPT

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

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

DWDM Logical Object: PPM

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

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

Clear the EQPT Alarm


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

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

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

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


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

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


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


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


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


2.7.80  EQPT-DIAG

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

SDH Logical Object: EQPT

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

Clear the EQPT-DIAG Alarm


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

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


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

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

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


2.7.81  EQPT-MISS

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

SDH Logical Object: FAN

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

Clear the EQPT-MISS Alarm


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

Step 2 If the fan-tray assembly is present, complete the "Replace the Fan-Tray Assembly" procedure.


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

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

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

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


2.7.82  ERROR-CONFIG

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

SDH Logical Object: EQPT

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

The typical reasons for an errored startup file are:

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

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

The user stored the configuration for the ML-Series card and then changed the card mode from RPR-IEEE mode to another mode, or vice versa.


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


Clear the ERROR-CONFIG Alarm


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

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

Step 2 Upload the configuration file to the TCC2/TCC2P card by completing the following steps:

a. In node view, right-click the ML-Series card graphic.

b. Choose IOS Startup Config from the shortcut menu.

c. Click Local > TCC and navigate to the file location in the Open dialog box.

Step 3 Complete the "Reset a Traffic Card in CTC" procedure.

Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start an Cisco IOS CLI for the card by completing the following steps:

a. Right click the ML-Series card graphic in node view.

b. Choose Open IOS Connection from the shortcut menu.


Note Open IOS Connection is not available unless the ML-Series card is physically installed in the shelf.


Follow the card provisioning instructions in the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.

Step 5 Execute the following CLI command:

copy run start
 
   

The command copies the new card configuration into the database and clears the alarm.

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


2.7.83  ETH-LINKLOSS

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

SDH Logical Object: NE

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

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

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

The backplane LAN cable is removed.

Clear the ETH-LINKLOSS Condition


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

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


2.7.84  E-W-MISMATCH

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

SDH Logical Object: STMN

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


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



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



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


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


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

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

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

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

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

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

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

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

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


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

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

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

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


Clear the E-W-MISMATCH Alarm in CTC


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

Step 2 Click the Maintenance > MS-SPRing tabs.

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

Step 4 Click View > Go to Network View.

Step 5 Delete and recreate the MS-SPRing by completing the following steps:

a. Click the Provisioning > MS-SPRing tabs.

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

c. Click Create.

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

e. Click Finish.

Step 6 Display node view and click the Maintenance > MS-SPRing tabs.

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

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

Step 9 Click OK.

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


2.7.85  EXCCOL

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

SDH Logical Object: EQPT

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

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

Clear the EXCCOL Alarm


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

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

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


2.7.86  EXERCISE-RING-FAIL

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

SDH Logical Object: STMN

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


Note If the exercise command gets rejected due to the existence of a higher priority condition in the ring, EXERCISE-RING-FAIL is Not Reported (NR).


Clear the EXERCISE-RING-FAIL Condition


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

Step 2 Reissue the Exercise Ring command by completing the following steps:

a. Click the Maintenance > MS-SPRing tabs.

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

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

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


2.7.87  EXERCISE-SPAN-FAIL

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

SDH Logical Object: STMN

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


Note If the exercise command gets rejected due to the existence of a higher priority condition in the span or ring, EXERCISE-SPAN-FAIL is Not Reported (NR).


Clear the EXERCISE-SPAN-FAIL Condition


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

Step 2 Complete the "Initiate an Exercise Ring Switch on an MS-SPRing" procedure.

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


2.7.88  EXT

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

SDH Logical Object: ENVALRM

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

Clear the EXT Alarm


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

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

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

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


2.7.89  EXTRA-TRAF-PREEMPT

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

SDH Logical Object: STMN

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

Clear the EXTRA-TRAF-PREEMPT Alarm


Step 1 Verify that the protection switch has occurred by verifying that the Conditions window shows the switch.

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

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


2.7.90  FAILTOSW

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

SDH Logical Objects: EQPT, STMN

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

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

Clear the FAILTOSW Condition


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


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


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

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


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



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


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


2.7.91  FAILTOSW-HO

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

SDH Logical Objects: VCMON-HP

The High-Order Path Failure to Switch to Protection condition occurs when a high-order path circuit fails to switch to the working or protect electrical circuit using the MANUAL command.

Clear the FAILTOSW-HO Condition


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

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


2.7.92  FAILTOSW-LO

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

SDH Logical Objects: VCMON-LP

The Low-Order Failure to Switch to Protection condition occurs when a low-order path circuit fails to switch to the working or protect electrical circuit using the MANUAL command.

Clear the FAILTOSW-LO Condition


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

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


2.7.93  FAILTOSWR

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

SDH Logical Object: STMN

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

FAILTOSWR clears in any of the following situations:

A physical card pull of the active TCC2/TCC2P card (done under the supervision of Cisco Technical Support).

A node power cycle.

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

The next ring switch succeeds.

The cause of the APS switch such as the "SD (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-218 or the "SF (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-222 clears.


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

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

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

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


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


Step 1 Perform the EXERCISE RING command on the reporting card by completing the following steps:

a. Click the Maintenance > MS-SPRing tabs.

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

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

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

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

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

Step 5 Click the Maintenance > MS-SPRing tabs.

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

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

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

c. Click the Provisioning > Line tabs.

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

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


Note If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.


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

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


Caution Using an optical test set disrupts service on the STM-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.

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

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

Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby STM-N card.


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


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

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


2.7.94  FAILTOSWS

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

SDH Logical Object: STMN

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

A physical card pull of the active TCC2/TCC2P card (done under the supervision of Cisco Technical Support).

A node power cycle.

A higher priority event such as an external switch command.

The next span switch succeeds.

The cause of the APS switch such as the "SD (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-218 or the "SF (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-222 clears.

Clear the FAILTOSWS Condition


Step 1 Perform the EXERCISE SPAN command on the reporting card by completing the following steps:

a. Click the Maintenance > MS-SPRing tabs.

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

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

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

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

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

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

Step 5 Click the Maintenance > MS-SPRing tabs.

Step 6 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-N cards are active and in service by completing the following steps:

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

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

c. Click the Provisioning > Line tabs.

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

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


Note If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.


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

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


Caution Using an optical test set disrupts service on the STM-N card. It could be necessary to manually switch traffic carrying circuits over to a protection path. Refer to the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure for cleaning optical connectors in the "Maintain the Node" chapter of the Cisco ONS 15454 SDH Procedure Guide.

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

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

Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Traffic Card" procedure for the protect standby STM-N card.


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


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


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

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


2.7.95  FAN

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

SDH Logical Object: FAN

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15454 SDH can rise above its normal operating range. The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the ONS 15454 SDH. However, even with five working fans, the fan-tray assembly could need replacement because a sixth working fan is required for extra protection against overheating.

Clear the FAN Alarm


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


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

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


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


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

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


2.7.96  FAPS

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

SDH Logical Object: FCMR

DWDM Logical Objects: TRUNK

The Fast Automatic Protection Switching condition is applicable to GEXP or 10GEXP cards. This condition occurs when the protection port, on the master card, switches from blocking to forwarding state.

Clear the FAPS Alarm


Step 1 When the cause of switching disappears, the protection port switches from the forwarding to the blocking state, and the FAPS alarm clears.

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


2.7.97  FAPS-CONFIG-MISMATCH

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

2.7.98  FC-DE-NES

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

SDH Logical Object: FCMR

DWDM Logical Objects: FC, TRUNK

The Fiber Channel Distance Extension Function Not Established condition occurs when the Fiber Channel client setup or distance extension configuration is incorrect.

Clear the FC-DE-NES Alarm


Step 1 Ensure that the FC client setup and distance extension configuration is correct.

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


2.7.99  FC-NO-CREDITS

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

SDH Logical Object: FCMR

DWDM Logical Objects: FC, TRUNK

The Fibre Channel Distance Extension Credit Starvation alarm occurs on storage access networking (SAN) Fibre Channel/Fiber Connectivity (FICON) FC_MR-4 cards when the congestion prevents the GFP transmitter from sending frames to the FC_MR-4 card port. For example, the alarm can be raised when an operator configures a card to autodetect framing credits but the card is not connected to an interoperable FC-SW-standards-based Fibre Channel/FICON port.

FC-NO-CREDITS is raised only if transmission is completely prevented. (If traffic is slowed but still passing, this alarm is not raised.) The alarm is raised in conjunction with the GFP-NO-BUFFERS alarm. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm could be raised at the upstream remote FC_MR-4 data port.

Clear the FC-NO-CREDITS Alarm


Step 1 If the port is connected to a Fibre Channel/FICON switch, make sure it is configured for interoperation mode using the manufacturer's instructions.

Step 2 If the port is not connected to a switch, turn off Autodetect Credits:

a. Double-click the FC_MR-4 card.

b. Click Provisioning > Port > General.

c. Under Admin State, click the cell and choose Locked,maintenance.

d. Click Apply.

e. Click the Provisioning > Port > Distance Extension tabs.

f. Uncheck the Autodetect Credits column check box.

g. Click Apply.

h. Click Provisioning > Port > General.

i. Under Admin State, click the cell and choose Unlocked.

j. Click Apply.


Note If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.


Step 3 Program the Credits Available value based on the buffers available on the connected equipment:


Note The NumCredits must be provisioned to a value smaller than or equal to the receive buffers or credits available on the connected equipment.


a. Double-click the FC_MR-4 card.

b. Click the Provisioning > Port > Distance Extension tabs.

c. Enter a new value in the Credits Available column.

d. Click Apply.

Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.100  FDI

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.101  FE-AIS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far-End AIS condition accompanies the "AIS" condition on page 2-37 at the far-end node. An AIS usually occurs in conjunction with a downstream "LOS (STM1E, STMN)" alarm on page 2-162.

Generally, any AIS is a special SDH signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.

Clear the FE-AIS Condition


Step 1 Complete the "Clear the AIS Condition" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.102  FEC-MISM

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.103  FE-E1-MULTLOS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End Multiple E-1 LOS Detected on an E1-42 card condition occurs when multiple E1 inputs detect signal loss on a far-end E1-42 port at the far-end node.

The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-MULTLOS condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

Clear the FE-E1-MULTLOS Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.104  FE-E1-NSA

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End E1 Equipment Failure Non-Service-Affecting (NSA) condition occurs when a far-end E-1 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.

Clear the FE-E1-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.105  FE-E1-SA

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End E-1 Equipment Failure Service-Affecting (SA) condition occurs when a far-end E-1 equipment failure occurs and affects service because traffic is unable to switch to the protect port.

Clear the FE-E1-SA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.106  FE-E1-SNGLLOS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End Single E-1 LOS on the E-3 condition occurs when one of the E3-12 ports on the far end detects an LOS.

Clear the FE-E1-SNGLLOS Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.107  FE-E3-NSA

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End E3 Equipment Failure Non-Service-Affecting (NSA) condition occurs when a far-end E-3 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.

Clear the FE-E3-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.108  FE-E3-SA

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End E3 Equipment Failure Service Affecting condition occurs when a far-end E-3 equipment failure occurs and affects service because traffic is unable to switch to the protect port.

Clear the FE-E3-SA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.109  FE-EQPT-NSA

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End Common Equipment Failure condition occurs when a Non-Service-Affecting (NSA) equipment failure is detected on a far-end DS1i-N-14, DS3i-N-12, or E-N card.

Clear the FE-EQPT-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.110  FE-FRCDWKSWBK-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far End Forced Switch Back to Working-Span condition is raised on a far-end 1+1 protect port when it is Force switched to the working port.


Note WKSWBK-type conditions apply only to nonrevertive circuits.


Clear the FE-FRCDWKSWBK-SPAN Condition


Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure for the far-end port.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.111  FE-FRCDWKSWPR-RING

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a MS-SPRing is forced from working to protect using the Force Ring command. This condition is only visible on the network view Conditions tab.

Clear the FE-FRCDWKSWPR-RING Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-RING condition does not clear, complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 5 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.112  FE-FRCDWKSWPR-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber MS-SPRing is forced from working to protect using the Force Span command. This condition is only visible on the network view Conditions tab. The port where the Force Switch occurred is indicated by an "F" on the network view detailed circuit map. This condition is accompanied by WKSWPR.

Clear the FE-FRCDWKSWPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-SPAN condition does not clear, complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 5 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.113  FE-IDLE

The FE-IDLE condition is not used in this platform in this release. It is reserved for development.

2.7.114  FE-LOCKOUTOFPR-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far-End Lock Out of Protection Span condition occurs when an MS-SPRing span is locked out of the protection system from a far-end node using the Lockout Protect Span command. This condition is only seen on the network view Conditions tab and is accompanied by LKOUTPR-S. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

Clear the FE-LOCKOUTOFPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Ensure there is no lockout set. Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.115  FE-LOF

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End LOF condition occurs when a far-end node reports a DS-1 LOF on a DS1i-N-14 card, a DS-3 LOF on a DS3i-N-12 card, or an LOF on an E-N card.

Clear the FE-LOF Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "2.7.193  LOF (TRUNK)" procedure. The procedure also applies to FE-LOF.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.116  FE-LOS

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: E3

The Far End LOS condition occurs when a far-end node reports a DS-1 LOF on a DS1i-N-14 card, a DS-3 LOS on a DS3i-N-12 card, or an E-N LOS.

Clear the FE-LOS Condition


Step 1 To troubleshoot the FE condition, determine which node and card is linked directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that is linked directly to the card reporting the FE condition.

Step 3 Complete the "Clear the LOS (STM1E, STMN) Alarm" procedure.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.117  FE-MANWKSWBK-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far End Manual Switch Back to Working—Span condition occurs when a far-end span is Manual switches back to working.


Note WKSWBK-type conditions apply only to nonrevertive circuits.


Clear the FE-MANWKSWBK-SPAN Condition


Step 1 To troubleshoot the FE condition, determine which node and card is linked directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

Step 2 Log into the node that is linked directly to the card reporting the FE condition.

Step 3 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.118  FE-MANWKSWPR-RING

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far End Ring Manual Switch of Working Facility to Protect condition occurs when an MS-SPRing working ring is switched from working to protect at a far-end node using the Manual Ring command.

Clear the FE-MANWKSWPR-RING Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could link to the main condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.119  FE-MANWKSWPR-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far-End Span Manual Switch Working Facility to Protect condition occurs when a four-fiber MS-SPRing span is switched from working to protect at the far-end node using the Manual Span command. This condition is only visible on the network view Conditions tab and is accompanied by WKSWPR. The port where the Manual Switch occurred is indicated by an "M" on the network view detailed circuit map.

Clear the FE-MANWKSWPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could link to the main condition from a card in Slot 6 of Node 2.

Step 2 Log into the node that links directly to the card reporting the FE condition.

Step 3 Complete the "Clear an MS-SPRing External Switching Command" alarm on page 2-264.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.120  FEPRLF

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Far-End Protection Line Failure alarm occurs when there was an "SF (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-222 condition on the protect card's APS channel coming into the node.


Note The FEPRLF alarm occurs on the ONS 15454 SDH only when bidirectional protection is used on optical (traffic) cards in a 1+1 protection group configuration.


Clear the FEPRLF Alarm on an MS-SPRing


Step 1 To troubleshoot the FE alarm, determine which node and card is linked directly to the card reporting the FE alarm. For example, an FE alarm or condition on a card in Slot 16 of Node 1 could relate to a main alarm from a card in Slot 16 in Node 2.

Step 2 Log into the node that is linked directly to the card reporting the FE alarm.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for procedures.

Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.121  FIBERTEMP-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.122  FORCED-REQ

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: EQPT, ML1000, ML100T, MLFX, VCMON-HP, VCMON-LP

The Force Switch Request on Facility or Port condition occurs when you enter the Force command on a port to force traffic from a working port to a protect port or protection span (or from a protect port to a working port or span). You do not need to clear the condition if you want the Force switch to remain.

FORCED-REQ is raised for an IEEE 802.17b-based RPR span if the force was requested in the Cisco IOS CLI using the "rpr-ieee protection request force-switch {east | west}" command. It clears from the RPR-IEEE span when you remove the switch in the CLI. For the IEEE 802.17b-based RPR interface, FORCED-REQ is suppressed by the "RPR-PASSTHR" alarm on page 2-210. It also suppresses the following alarms:

MAN-REQ (for an ML-Series object)

RPR-SF

RPR-SD

WTR (for an ML-Series object)

Clear the FORCED-REQ Condition


Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure.

Step 2 If the condition is raised on an IEEE 802.17b-based RPR span, enter the following command in the CLI in RPR-IEEE interface configuration mode:

router(config-if)#no rpr-ieee protection request force-switch {east | west}
 
   

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.123  FORCED-REQ-RING

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Force Switch Request Ring condition applies to optical trunk cards when the Force Ring command is applied to MS-SPRings to move traffic from working to protect. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the FORCE RING command originated is marked with an "F" on the network view detailed circuit map.

Clear the FORCED-REQ-RING Condition


Step 1 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.124  FORCED-REQ-SPAN

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Force Switch Request Span condition applies to optical trunk cards in two-fiber or four-fiber MS-SPRings when the Force Span command is applied to a MS-SPRing SPAN to force traffic from working to protect or from protect to working. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the FORCE SPAN command was applied is marked with an "F" on the network view detailed circuit map.

This condition can also be raised in 1+1 facility protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting both the facility and the span.

Clear the FORCED-REQ-SPAN Condition


Step 1 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.125  FP-LINK-LOSS

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: EQPT

The Front Port Link Loss condition occurs when a LAN cable is not connected to the front port of the TCC2/TCC2P card.

Clear the FP-LINK-LOSS Condition


Step 1 Connect a LAN cable to the front port of the TCC2/TCC2P card.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.7.126  FRCDSWTOINT

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE-SREF

The Force Switch to Internal Timing condition occurs when the user issues a FORCE command to switch to an internal timing source.


Note FRCDSWTOINT is an informational condition. The condition does not require troubleshooting.


2.7.127  FRCDSWTOPRI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Primary Timing Source condition occurs when the user issues a FORCE command to switch to the primary timing source.


Note FRCDSWTOPRI is an informational condition. The condition does not require troubleshooting.


2.7.128  FRCDSWTOSEC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Second Timing Source condition occurs when the user issues a FORCE command to switch to the second timing source.


Note FRCDSWTOSEC is an informational condition. The condition does not require troubleshooting.


2.7.129  FRCDSWTOTHIRD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: EXT-SREF, NE-SREF

The Force Switch to Third Timing Source condition occurs when the user issues a FORCE command to switch to a third timing source.


Note FRCDSWTOTHIRD is an informational condition. The condition does not require troubleshooting.


2.7.130  FRNGSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE-SREF

The Free Running Synchronization Mode condition occurs when the reporting ONS 15454 SDH is in free-run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the ONS 15454 SDH has lost its designated BITS timing source. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15454 SDH relying on an internal clock.


Note If the ONS 15454 SDH is configured to operate from its internal clock, disregard the FRNGSYNC condition.


Clear the FRNGSYNC Condition


Step 1 If the ONS 15454 SDH is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the "Timing" chapter in the Cisco ONS 15454 SDH Reference Manual for more information about it.

Step 2 If the BITS source is valid, clear alarms related to the failures of the primary and secondary reference sources, such as the "SYNCPRI" alarm on page 2-239 and the "SYSBOOT" alarm on page 2-241.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.131  FSTSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE-SREF

A Fast Start Synchronization Mode condition occurs when the ONS 15454 SDH is choosing a new timing reference. The previous timing reference has failed.

The FSTSYNC condition disappears after approximately 30 seconds. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


Note FSTSYNC is an informational condition. The condition does not require troubleshooting.


2.7.132  FTA-MISMATCH

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.133  FULLPASSTHR-BI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node for an MS-SPRing when the protect channels on the node are active and carrying traffic and there is a change in the receive K byte from No Request.

Clear the FULLPASSTHR-BI Condition


Step 1 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.134  GAIN-HDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.135  GAIN-HFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.136  GAIN-LDEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.137  GAIN-LFAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.138  GCC-EOC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.139  GE-OOSYNC

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.140  GFP-CSF

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: CEMR, CE100T, CE1000, FCMR, GFP-FAC, ML100T, ML1000, MLFX

The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on CE-100T-8, CE-1000-4, CE-MR-10, FC_MR-4, ML100T, ML1000, ML100X-8, ML-MR-10, MXP_MR_25G, and MXPP_MR_25G GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm caused by an event such as a pulled receive cable is affecting a remote data port's transmission capability. This alarm can be demoted when a facility loopback is placed on the FC_MR-4 port.


Note For more information about provisioning MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual. For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-CSF Alarm


Step 1 Clear the Service-Affecting (SA) alarm at the remote data port.

Step 2 If the GFP-CSF alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.


2.7.141  GFP-DE-MISMATCH

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: FCMR, GFP-FAC

The GFP Fibre Channel Distance Extension Mismatch alarm indicates that a port configured for Distance Extension is connected to a port that is not operating in Cisco's proprietary Distance Extension mode. It is raised on Fibre Channel and FICON card GFP ports supporting distance extension. The alarm occurs when distance extension is enabled on one side of the transport but not on the other. To clear, distance extension must be enabled on both ports connected by a circuit.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-DE-MISMATCH Alarm


Step 1 Ensure that the distance extension protocol is configured correctly on both sides:

a. Double-click the card to open the card view.

b. Click the Provisioning > Port > General tabs.

c. Under Admin State, click the cell and choose Locked,maintenance.

d. Click Apply.

e. Click the Provisioning > Port > Distance Extension tabs.

f. Check the check box in the Enable Distance Extension column.

g. Click Apply.

h. Click the Provisioning > Port > General tabs.

i. Under Admin State, click the cell and choose Unlocked.

j. Click Apply.


Note If a port in the unlocked admin state does not receive a signal, the LOS alarm is raised and the port service state transitions to Locked-disabled, automaticInService & failed.


Step 2 If the GFP-DE-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.


2.7.142  GFP-EX-MISMATCH

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: CE1000, FCMR, GFP-FAC

The GFP Extension Header Mismatch alarm is raised on Fibre Channel/FICON cards when it receives frames with an extension header that is not null. The alarm occurs when a provisioning error causes all GFP frames to be dropped for 2.5 seconds.

Ensure that both end ports are sending a null extension header for a GFP frame. The FC_MR-4 card always sends a null extension header, so if the equipment is connected to other vendors' equipment, those need to be provisioned appropriately.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-EX-MISMATCH Alarm


Step 1 Ensure that the vendor equipment is provisioned to send a null extension header in order to interoperate with the FC_MR-4 card. (The FC_MR-4 card always sends a null extension header.)

Step 2 If the GFP-EX-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.


2.7.143  GFP-LFD

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: CEMR, CE100T, CE1000, FCMR, GFP-FAC, ML100T, ML1000, MLFX

The GFP Loss of Frame Delineation alarm applies to Fibre Channel, FICON GFP, and Ethernet ports. This alarm occurs if there is a faulty SONET connection, if SONET path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. This loss causes traffic stoppage.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-LFD Alarm


Step 1 Look for and clear any associated SDH path errors such as LOS or the "AU-AIS" alarm on page 2-47 that originate at the transmit node.

Step 2 If the GFP-LFD alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.


2.7.144  GFP-NO-BUFFERS

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: FCMR, GFP-FAC

The GFP Fibre Channel Distance Extension Buffer Starvation alarm is raised on Fibre Channel/FICON card ports supporting GFP and the distance extension protocol when the GFP transmitter cannot send GFP frames due to lack of remote GFP receiver buffers. This occurs when the remote GFP-T receiver experiences congestion and is unable to send frames over the Fibre Channel/FICON link.

This alarm could be raised in conjunction with the FC-NO-CREDITS alarm. For example, if the FC-NO-CREDITS alarm is generated at an FC_MR-4 data port, a GFP-NO-BUFFERS alarm could be raised at the upstream remote FC_MR-4 data port.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-NO-BUFFERS Alarm


Step 1 Complete the "Clear the FC-NO-CREDITS Alarm" procedure.

Step 2 If the GFP-CSF alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.145  GFP-UP-MISMATCH

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: CEMR, CE100T, CE1000, FCMR, GFP-FAC, ML100T, ML1000, MLFX

The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type. For example, the local port media type could be set to Fibre Channel—1 Gbps ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL or FICON—2 Gbps ISL.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-UP-MISMATCH Alarm


Step 1 Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps:

a. Double-click the card to open the card view.

b. Click the Provisioning > Port > Distance Extension tabs.

c. Check the check box in the Enable Distance Extension column.

d. Click Apply.

Step 2 Ensure that both ports are set for the correct media type. For each port, complete the following steps:

a. Double-click the card to open the card view (if you are not already in card view).

b. Click the Provisioning > Port > General tabs.

c. Choose the correct media type (Fibre Channel - 1Gbps ISL, Fibre Channel - 2 Gbps ISL, FICON - 1 Gbps ISL, or FICON - 2 Gbps ISL) from the drop-down list.

d. Click Apply.

Step 3 If the GFP-UP-MISMATCH alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.


2.7.146  HELLO

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Object: TRUNK

The Open Shortest Path First (OSPF) Hello alarm is raised when the two end nodes cannot bring an OSPF neighbor up to the full state. Typically, this problem is caused by an area ID mismatch, and/or OSPF HELLO packet loss over the DCC.

Clear the HELLO Alarm


Step 1 Ensure that the area ID is correct on the missing neighbor by completing the following steps:

a. In node view, click the Provisioning > Network > OSPF tabs.

b. Ensure that the IP address in the Area ID column matches the other nodes.

c. If the address does not match, click the incorrect cell and correct it.

d. Click Apply.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.147  HI-LASERBIAS

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Objects: EQPT, STMN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM, TRUNK

The Equipment High Transmit Laser Bias Current alarm is raised against TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, and OC192-XFP card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.

Laser bias typically starts at about 30 percent of the manufacturer maximum laser bias specification and increases as the laser ages. If the HI-LASERBIAS alarm threshold is set at 100 percent of the maximum, the laser usability has ended. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.


Note For more information about provisioning MXP or TXP PPMs, refer to the "Provision Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide. For more information about the cards themselves, refer to the "Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-LASERBIAS Alarm


Step 1 Complete the "Physically Replace a Traffic Card" procedure. Replacement is not urgent and can be scheduled during a maintenance window.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.148  HI-LASERTEMP

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Objects: EQPT, STMN

DWDM Logical Object: PPM

The Equipment High Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength.

When the TXP or MXP card raises this alarm, the laser is automatically shut off. The "LOS (STM1E, STMN)" alarm on page 2-162 is raised at the far-end node and the "DUP-IPADDR" alarm on page 2-81 is raised at the near end.


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 Procedure Guide. For more information about the cards themselves, refer to the "Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-LASERTEMP Alarm


Step 1 In node view, double-click the TXP or MXP card to open the card view.

Step 2 Click the Performance > Optics PM > Current Values tabs.

Step 3 Verify the card laser temperature levels. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Step 4 Complete the "Reset a Traffic Card in CTC" procedure for the MXP or TXP card.

Step 5 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting MXP or TXP card.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.149  HI-RXPOWER

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, MXP_2.5G_10G, or OC192-XFP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.


Note For more information about MXP or TXP cards, refer to the Cisco ONS 15454 DWDM Reference Manual.



Note When you upgrade a node to Software Release 6.0 or later, this enables received optical power PMs for the STM1-8, STM64-SR, STM64-IR, STM64-ITU, STM64-XFP, MRC-12, and MRC25G-4 cards. The newly enabled HI-RXPOWER and LO-RXPOWER alarms require that you initialize a site-accepted optical power (OPR0) nominal value after the upgrade. (To do this, refer to the procedure in the "Turn Up a Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.) When you apply the value change, CTC uses the new OPR0 value to calculate PM percentage values. If you do not change the nominal value, the HI-RXPOWER or LO-RXPOWER may be raised in response to the unmodified setting.


Clear the HI-RXPOWER Alarm


Step 1 Find out whether gain (the amplification power) of any amplifiers has been changed. This change also causes channel power to need adjustment.

Step 2 Find out whether channels have been dropped from the fiber. Increasing or decreasing channels can affect power. If channels have been dropped, the power levels of all channels have to be adjusted.


Note If the card is part of an amplified DWDM system, dropping channels on the fiber affects the transmission power of each channel more than it would in an unamplified system.


Step 3 At the transmit end of the errored circuit, decrease the transmit power level within safe limits.

Step 4 If neither of these problems cause the HI-RXPOWER alarm, there is a slight possibility that another wavelength is drifting on top of the alarmed signal. In this case, the receiver gets signals from two transmitters at the same time and data alarms would be present. If wavelengths are drifting, the data is garbled and receive power increases by about +3 dBm.

Step 5 If the alarm does not clear, add fiber attenuators to the receive ports. Start with low-resistance attenuators and use stronger ones as needed, depending on factors such as the transmission distance, according to standard practice.

Step 6 If the alarm does not clear and no faults are present on the other port(s) of the transmit or receive card, use a known-good loopback cable to complete the "1.3.1  Perform a Facility Loopback on a Source-Node Optical Port" procedure and test the loopback.

Step 7 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Traffic Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.150  HITEMP

Default Severity: Critical (CR), Service-Affecting (SA) for NE; Minor (MN), Non-Service-Affecting (NSA) for EQPT

SDH Logical Objects: EQPT, NE

The High Temperature alarm occurs when the temperature of the ONS 15454 SDH is above 50 degrees C (122 degrees F).

Clear the HITEMP Alarm


Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, see Figure 2-1.

Step 2 Verify that the environmental temperature of the room is not abnormally high.

Step 3 If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454 SDH.

Step 4 If airflow is not blocked, physically ensure that blank faceplates fill the ONS 15454 SDH empty slots. Blank faceplates help airflow.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.

Step 5 If faceplates fill the empty slots, determine whether the air filter needs replacement. Complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Step 6 If the filter is clean, complete the "Remove and Reinsert a Fan-Tray Assembly" procedure.


Note The fan-tray assembly should run immediately when correctly inserted.


Step 7 If the fan does not run or the alarm persists, complete the "Replace the Fan-Tray Assembly" procedure.

Step 8 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information. If the alarm does not clear, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.151  HI-TXPOWER

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Objects: EQPT, STMN

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, PPM, TRUNK

The Equipment High Transmit Power alarm is an indicator on the TXP_MR_E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.


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 Procedure Guide. For more information about the cards themselves, refer to the "Transponder and Muxponder Cards" chapter in the Cisco ONS 15454 DWDM Reference Manual.


Clear the HI-TXPOWER Alarm


Step 1 In node view, double-click the card view for the TXP_MR_10E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card.

Step 2 Click the Provisioning > Optics Thresholds > Current Values tabs.

Step 3 Decrease (change toward the negative direction) the OPT-HIGH column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the "Physically Replace a Traffic Card" section.

Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.152  HLDOVRSYNC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE-SREF

The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15454 SDH relying on an internal clock.

Clear the HLDOVRSYNC Alarm


Step 1 Clear additional events that relate to timing, such as:

FRNGSYNC

FSTSYNC

HLDOVRSYNC

LOF (DS1, DS3, E1, E4, STM1E, STMN)

LOS (STM1E, STMN)

MANSWTOINT

MANSWTOPRI

MANSWTOSEC

MANSWTOTHIRD

SYSBOOT

SWTOSEC

SWTOTHIRD

SYNC-FREQ

SYNCPRI

SYSBOOT

Step 2 Reestablish primary and secondary timing sources according to local site practice. If none exists, refer to the "Change Node Settings" chapter in the Cisco ONS 15454 SDH Procedure Guide for procedures.

Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.

2.7.153  HP-DEG

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VMMON-HP, VCTRM-HP

An HP-DEG condition is similar to the "SD (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-218, but it applies to the HP layer of the SDH overhead. A HP-DEG alarm travels on the B3 byte of the SDH overhead.

For path protection protected circuits, the BER threshold is user-provisionable and has a range for HP-DEG from 1E-9 dBm to 1E-5 dBm. For MS-SPRing 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E-6 dBm.

On path protection configurations, an HP-DEG condition causes a switch from the working card to the protect card at the path level. On MS-SPRing, 1+1, and on unprotected circuits, an HP-DEG condition does not cause switching.

The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

HP-DEG clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.

Clear the HP-DEG Condition


Step 1 Complete the "Clear the SD (DS3, E1, E3, E4, STMN) Condition" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.7.154  HP-ENCAP-MISMATCH

Default Severity: Critical (CR), Service-Affecting (SA)

SDH Logical Object: VCTRM-HP

The High-Order Path Encapsulation C2 Byte Mismatch alarm applies to ML-Series Ethernet cards. It occurs when the first three following conditions are met and one of the last two is false:

The received C2 byte is not 0x00 (unequipped).

The received C2 byte is not a PDI value.

The received C2 does not match the expected C2.

The expected C2 byte is not 0x01 (equipped unspecified).

The received C2 byte is not 0x01 (equipped unspecified).

(This is in contrast to LP-PLM, which must meet all five criteria.) For an HP-ENCAP-MISMATCH to be raised, there is a mismatch between the received and expected C2 byte, with either the expected byte or received byte value being 0x01.

An example situation that would raise an HP-ENCAP-MISMATCH alarm is if a circuit created between two ML-Series cards has GFP framing provisioned on one end and high-level data link control (HDLC) framing with LEX encapsulation provisioned on the other. The GFP framing card transmits and expects a C2 byte of 0x1B, while the HDLC framing card transmits and expects a C2 byte of 0x01.

A mismatch between the transmit and receive cards on any of the following parameters can cause the alarm:

Mode (HDLC, GFP-F)

Encapsulation (LEX, HDLC, PPP)

CRC size (16 or 32)

Scrambling state (on or off)

This alarm is demoted by a path label mismatch (PLM) such as LP-PLM.


Note By default, an HP-ENCAP-MISMATCH alarm causes an ML-Series card data link to go down. This behavior can be modified using the command-line interface (CLI) command no pos trigger defect encap.



Note For more information about the ML-Series Ethernet card, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the HP-ENCAP-MISMATCH Alarm


Step 1 Ensure that the correct framing mode is in use on the receiving card by completing the following steps:

a. In node view, double-click the ML-Series card to display the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the correct mode (GFP-F or HDLC) is selected. If it is not, choose it and click Apply.

Step 2 Ensure that the correct framing mode is in use on the transmit card, and that it is identical to the framing mode used on the receiving card by completing the following steps:

a. In node view, double-click the ML-Series card to display the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the same mode (GFP-F or HDLC) is selected. If it is not, choose it and click Apply.

Step 3 If the alarm does not clear, use the ML-Series card CLI to ensure that the remaining settings are correctly configured:

Encapsulation

CRC size

Scrambling state

To open the interface, click the card view IOS tab and click Open IOS Connection. Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide entries on all three of these topics to obtain the full configuration command sequences.

Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

2.7.155  HP-EXC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VCMON-HP, VCTRM-HP

An HP-EXC condition is similar to the "SF (DS1, DS3, E1, E3, E4, STMN)" condition on page 2-222, but it applies to the path layer B3 byte of the SDH overhead. It can trigger a protection switch.

The HP-EXC condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

Clear the HP-EXC Condition


Step 1 Complete the "Clear the SF (DS3, E1, E3, E4, STMN) Condition" procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.7.156  HP-RFI

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)

SDH Logical Object: VCMON-HP

The High-Order Remote Failure Indication (RFI) condition indicates that there is a remote failure indication in the high-order (VC-4 or VC-3) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The HP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the HP-RFI condition in the reporting node.

Clear the HP-RFI Condition


Step 1 Log into the node at the far end of the reporting ONS 15454 SDH.

Step 2 Determine whether there are any related alarms, especially the "LOS (STM1E, STMN)" alarm on page 2-162.

Step 3 Clear the main alarm. See the appropriate alarm section in this chapter for procedures.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.157  HP-TIM

Default Severities: Critical (CR), Service-Affecting (SA) for VCTRM-HP; Minor (MN), Non-Service-Affecting (NSA) for VCMON-HP

SDH Logical Objects: VCMON-HP, VCTRM-HP

The TIM High-Order TIM Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. HP-TIM occurs when there is a mismatch between the transmitted and received J1 identifier byte in the SDH path overhead. The error can originate at the transmit end or the receive end.

Clear the HP-TIM Alarm


Step 1 Use an optical test set capable of viewing SDH path overhead to determine the validity of the J1 byte. For specific procedures to use the test set equipment, consult the manufacturer. Examine the signal as near to the reporting card as possible.

Examine the signal as close as possible to the output card.

Step 2 If the output card signal is valid, complete the "Clear the SYNCPRI Alarm" procedure.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the alarm applies to VCTRM-HP, it is a service-affecting problem.


2.7.158  HP-UNEQ

Default Severity: Critical (CR), Service-Affecting (SA)

SDH Logical ObjectS: VCMON-HP, VCTRM-HP

The signal label mismatch fault (SLMF) Unequipped High-Order Path alarm applies to the C2 path signal label byte in the high-order (VC-4) path overhead. HP-UNEQ occurs when no C2 byte is received in the SDH path overhead.

Clear the HP-UNEQ Alarm


Step 1 From the View menu, choose Go to Network View.

Step 2 Right-click the alarm to display the Select Affected Circuits shortcut menu.

Step 3 Click Select Affected Circuits.

Step 4 When the affected circuits appear, look in the Type column for a virtual circuit (VC).

Step 5 If the Type column does not contain a VC, there are no VCs. Go to Step 7.

Step 6 If the Type column does contain a VC, attempt to delete these row(s) by completing the following steps:


Note The node does not allow you to delete a valid VC.


a. Click the VC row to highlight it. Complete the "Delete a Circuit" procedure.

b. If an error message dialog box appears, the VC is valid and not the cause of the alarm.

c. If any other rows contain VT, repeat Steps a through b.

Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete by completing the following steps:

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the Status column of any circuits.

Step 8 If you find circuits listed as incomplete, verify that these circuits are not working circuits that continue to pass traffic, using an appropriate optical test set and site-specific procedures. For specific procedures to use the test set equipment, consult the manufacturer.

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits and Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.

Step 11 Log back in and verify that all circuits terminating in the reporting card are active by completing the following steps:

a. Click the Circuits tab.

b. Verify that the Status column lists all circuits as active.

Step 12 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.


Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Step 13 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the optical and/or electrical cards.


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for information.


Note When you replace a card with the identical type of card, you do not need to make any changes to the database.


Step 14 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.159  I-HITEMP

Default Severity: Critical (CR), Service-Affecting (SA)

SDH Logical Object: NE

The Industrial High Temperature alarm occurs when the temperature of the ONS 15454 SDH is above 149 degrees F (65 degrees C) or below -40 degrees F (-40 degrees C). This alarm is similar to the HITEMP alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.

Clear the I-HITEMP Alarm


Step 1 Complete the "Clear the HITEMP Alarm" procedure.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country to report a Service-Affecting (SA) problem.


2.7.160  ILK-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.161  IMPROPRMVL

Default Severity: Critical (CR), Service-Affecting (SA) for active card

SDH Logical Object: EQPT

DWDM Logical Object: PPM

The Improper Removal equipment (IMPROPRMVL) alarm occurs under the following conditions:

A card is removed when the card was rebooting. It is recommended that after the card completely reboots, delete the card in CTC and only then remove the card physically. When you delete the card, CTC loses connection with the node view (single-shelf mode) or shelf view (multishelf mode), and goes to network view.

When a card is physically removed from its slot before it is deleted from CTC. It is recommended that any card be deleted in CTC before physically removing the card from the chassis.


Note CTC provides the user approximately 15 seconds to physically remove the card before it begins rebooting the card.
It can take up to 30 minutes for software to be updated on a standby TCC2/TCC2P card.


A card is inserted into a slot but is not fully plugged into the backplane.

A PPM (SFP) is provisioned but the physical module is not inserted into the port.

Electrical issues such as short circuit or failure of DC-DC conversion.


Note When a MIC-A/P card is removed from the shelf, no IMPROPRMVL alarm is reported for that card. The FMEC to the left side of the MIC-A/P also could also disappear from view in CTC. This functions as designed. The MIC-A/P card provides a communication channel to the other FMEC. When the MIC card is removed, the communication channel is no longer available and consequently, the other FMEC is assumed not to be present. The disappeared FMEC is rediscovered when the MIC-A/P is reinserted.


Clear the IMPROPRMVL Alarm


Step 1 In node view, right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.


Note CTC does not allow you to delete the reporting card if the card is in service, does have circuits mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.


Step 3 If any ports on the card are in service, lock them (Locked, maintenance) by completing the following steps:


Caution Before locking a port (Locked,maintenance or Locked,disabled), ensure that no live traffic is present.

a. In node view, double-click the reporting card to display the card view.

b. Click the Provisioning > Line tab or the Provisioning > Line > SDH tab as appropriate to the reporting card.

c. Click the Admin State column of any Unlocked ports.

d. Choose Locked, maintenance to take the ports out of service.

Step 4 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.


Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.

Step 5 If the card is paired in a protection scheme, delete the protection group by completing the following steps:

a. Click View > Go to Previous View to return to node view.

b. If you are already in node view, click the Provisioning > Protection tabs.

c. Click the protection group of the reporting card.

d. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning by completing the following steps:

a. Click the ONS 15454 SDH Provisioning > Comm Channels > RS-DCC tabs.

b. Click the slots and ports listed in DCC terminations.

c. Click Delete and click Yes in the dialog box that appears to delete all of the selected terminations.

Step 7 If the card is used as a timing reference, change the timing reference by completing the following steps:

a. Click the Provisioning > Timing > General tabs.

b. Under NE Reference, click the drop-down list for Ref-1.

c. Change Ref-1 from the listed STM-N card to Internal Clock.

d. Click Apply.

Step 8 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.162  INC-ISD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: DS3, E3

The DS-3 Idle condition indicates that the DS3i-N-12 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has a Locked, maintenance Admin State. It is resolved when the Locked, maintenance state ends.


Note INC-ISD is an informational condition. The condition does not require troubleshooting.


2.7.163  INCOMPATIBLE-SW

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: SYSTEM

The Incompatible Software alarm is raised when CTC cannot connect to the NE due to incompatible versions of software between CTC and the NE. The alarm is cleared by restarting CTC in order to redownload the CTC jar files from the NE.

Clear the INCOMPATIBLE-SW Alarm


Step 1 Restart the CTC application.

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1-800-553-2447).


2.7.164  INHSWPR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: EQPT

The Inhibit Switch To Protect Request on Equipment condition occurs on traffic cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.

Clear the INHSWPR Condition


Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.165  INHSWWKG

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: EQPT

The Inhibit Switch To Working Request on Equipment condition occurs on traffic cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the protect system. If the card is part of a 1:N protection scheme, traffic can be switched between protect cards when the switch to working is disabled.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the INHSWWKG Condition


Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

Step 2 If it is raised against a 1:1 card, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.166  INTRUSION-PSWD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE

The Security Intrusion Incorrect Password condition occurs after a user attempts a provisionable (by Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not in login sessions for lower-level users. The INTRUSION-PSWD condition is automatically cleared when a provisionable lockout timeout expires, or it can be manually cleared in CTC by the Superuser if lockout is permanent.

Clear the INTRUSION-PSWD Condition


Step 1 Click the Provisioning > Security > Users tabs.

Step 2 Click Clear Security Intrusion Alarm.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.167  INVMACADR

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Object: BPLANE

The Equipment Failure Invalid MAC Layer address alarm occurs when the ONS 15454 SDH MAC address is invalid. The MAC address is permanently assigned to the ONS 15454 SDH chassis during manufacture. Do not attempt to troubleshoot an INVMACADR alarm. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

2.7.168  IOSCFGCOPY

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: EQPT

The Cisco IOS Configuration Copy in Progress condition occurs on ML-Series Ethernet cards when a Cisco IOS startup configuration file is being uploaded to or downloaded from an ML-Series card. (This condition is very similar to the "SFTWDOWN" condition on page 2-225 but it applies to ML-Series Ethernet cards rather than to the TCC2/TCC2P card.)

The condition clears after the copy operation is complete. (If it does not complete correctly, the "NO-CONFIG" condition on page 2-193 could be raised.)


Note IOSCFGCOPY is an informational condition.



Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


2.7.169  ISIS-ADJ-FAIL

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Object: TRUNK

The Open System Interconnection (OSI) Intermediate System to Intermediate-System (IS-IS) Adjacency Failure alarm is raised by an intermediate system (node routing IS Level 1 or Level 1 and 2) when no IS or end system (ES) adjacency is established on a point-to-point subnet. The Intermediate-System Adjacency Failure alarm is not supported by ES. It is also not raised by IS for disabled routers.

The alarm is typically caused by a misconfigured router manual area adjacency (MAA) address. For more information about IS-IS OSI routing and MAA configuration, refer to the "Management Network Connectivity" chapter in the Cisco ONS 15454 SDH Reference Manual. For more information about configuring OSI, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for procedures.

Clear the ISIS-ADJ-FAIL Alarm


Step 1 Ensure that both ends of the communication channel are using the correct Layer 2 protocol and settings (LAPD or PPP). To do this, complete the following steps:

a. At the local node, in node view, click the Provisioning > Comm Channels >MSDCC tabs.

b. Click the row of the circuit. Click Edit.

c. In the Edit MSDCC termination dialog box, view and record the following selections: Layer 2 protocol (LAPD or PPP); Mode radio button selection (AITS or UITS); Role radio button selection (Network or User); MTU value; T200 value, and T203 selections.

d. Click Cancel.

e. Log in to the remote node and follow the same steps, also recording the same information for this node.

Step 2 If both nodes do not use the same Layer 2 settings, you will have to delete the incorrect termination and recreate it. To delete it, click the termination and click Delete. To recreate it, refer to the "Turn Up Node" chapter in the Cisco ONS 15454 SDH Procedure Guide for the procedure.

Step 3 If the nodes use PPP Layer 2, complete the "Clear the RS-EOC Alarm" procedure. If the alarm does not clear, go to Step 7.

Step 4 If both nodes use the LAPD Layer 2 protocol but have different Mode settings, change the incorrect node's entry by clicking the correct setting radio button in the Edit MSDCC termination dialog box and clicking OK.

Step 5 If the Layer 2 protocol and Mode settings are correct, ensure that one node is using the Network role and the other has the User role. If not (that is, if both have the same mode settings), correct the incorrect one by clicking the correct radio button in the Edit MSDCC termination dialog box and clicking OK.

Step 6 If the Layer 2, Mode, and Role settings are correct, compare the MTU settings for each node. If one is incorrect, choose the correct value in the Edit MSDCC dialog box and click OK.

Step 7 If all of the preceding settings are correct, ensure that OSI routers are enabled for the communications channels at both ends by completing the following steps:

a. Click Provisioning > OSI > Routers > Setup.

b. View the router entry under the Status column. If the status is Enabled, check the other end.

c. If the Status is Disabled, click the router entry and click Edit.

d. Check the Enabled check box and click OK.

Step 8 If the routers on both ends are enabled and the alarm still has not cleared, ensure that both ends of the communications channel have a common MAA by completing the following steps:

a. Click the Provisioning > OSI > Routers > Setup tabs.

b. Record the primary MAA and secondary MAAs, if configured.


Tip You can record long strings of information such as the MAA address by using the CTC export and print functions. Export it by choosing File > Export > html. Print it by choosing File > Print.


c. Log into the other node and record the primary MAA and secondary MAAs, if configured.

d. Compare this information. There should be at least one common primary or secondary MAA in order to establish an adjacency.

e. If there is no common MAA, one must be added to establish an adjacency. Refer to the "Turn Up Node" chapter of the Cisco ONS 15454 SDH Procedure Guide for procedures to do this.

Step 9 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.170  KB-PASSTHR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The K Bytes Pass Through Active condition occurs on a nonswitching node in an MS-SPRing when the protect channels on the node are not active and the node is in K Byte pass-through state.

Clear the KB-PASSTHR Condition


Step 1 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.171  KBYTE-APS-CHAN-FAIL

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For example, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.

This alarm is also raised during checksum. Failure occurs if the K1 and K2 bytes are overwritten by test equipment. It is not raised in bidirectional full pass-through or K byte pass-through states. The alarm is overridden by MS-AIS, "LOF (DS1, DS3, E1, E4, STM1E, STMN)" alarm on page 2-153, "LOS (STM1E, STMN)" alarm on page 2-162, or SFBER-EXCEED-HO alarms.

Clear the KBYTE-APS-CHAN-FAIL Alarm


Step 1 The alarm is most frequently raised due to mismatched span provisioning. In this case, reprovision one side of the span to match the parameters of the other side. To do this, refer to the "Turn Up Network" chapter in the Cisco ONS 15454 SDH Procedure Guide for procedures.

Step 2 If the error is not caused by misprovisioning, it is due to checksum errors within an STM-N, cross-connect, or TCC2/TCC2P card. In this case, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to allow CTC to resolve the issue.

Step 3 If third-party equipment is involved, ensure that it is configured for the same APS channel as the Cisco ONS equipment.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.172  LAN-POL-REV

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: NE

The LAN Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised during software upgrade when the card detects that a connected Ethernet cable has reversed receive wire pairs. The card automatically compensates for this reversal, but LAN-POL-REV stays active.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the LAN-POL-REV Condition


Step 1 Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the "Maintain the Node" chapter in the Cisco ONS 15454 SDH Procedure Guide.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.173  LASER-APR

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.174  LASERBIAS-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.175  LASERBIAS-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.176  LASERTEMP-DEG

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide. This guide discusses all DWDM alarms.

2.7.177  LCAS-CRC

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against ML-Series Ethernet and and CE-series cards. It occurs when there is an equipment, path, or provisioning error on the virtual concatenation group (VCG) that causes consecutive 2.5 second CRC failures in the LCAS control word.

The condition can occur if an LCAS-enabled node (containing ML-Series cards) transmitting to another LCAS-enabled node delivers faulty traffic due to an equipment or SDH path failure. Transmission errors would also be reflected in CV-P, ES-P, or SES-P performance monitoring statistics. If these errors do not exist, an equipment failure is indicated.

If LCAS is not supported on the peer node, the condition does not clear.

LCAS-CRC can also occur if the VCG source node is not LCAS-enabled, but the receiving node does have the capability enabled. Both source and destination nodes must have LCAS enabled. Otherwise, the LCAS-CRC condition persists on the VCG.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the LCAS-CRC Condition


Step 1 Look for and clear any associated equipment failures, such as the EQPT alarm, on the receive node or transmit node.

Step 2 Look for and clear any bit error rate alarms at the transmit node.

Step 3 If no equipment or SDH path errors exist, ensure that the remote node has LCAS enabled on the circuit:

Step 4 In node view, click the Circuits tab.

Step 5 Choose the VCAT circuit and click Edit.

Step 6 In the Edit Circuit window, click the General tab.

Step 7 Verify that the Mode column says LCAS.

Step 8 If the column does not say LCAS, complete the "Delete a Circuit" procedure and recreate it in LCAS mode using the instructions in the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Step 9 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.178  LCAS-RX-DNU

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Receive-Side-In Do Not Use condition is raised on CE-MR-10 cards and ML-MR-10 Ethernet cards when the receive side of an LCAS VCG member is in the do-not use state. For a unidirectional failure, this condition is only raised at the source node.

The node reporting this condition likely reports an "MS-RFI" alarm on page 2-191 and "RFI-V" alarm on page 2-207 for CE-MR-10, and "MS-RFI" alarm on page 2-191 for ML-MR-10.


Note For more information about the CE-MR-10 and ML-MR-10 Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


Clear the LCAS-RX-DNU Condition


Step 1 Look for any SDH failures on the source node. If any alarms are present, clear them using the relevant procedures in this chapter.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.7.179  LCAS-RX-FAIL

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Receive-Side-In Fail condition is raised against FC_MR-4 cards, CE-series and ML-Series Ethernet cards with LCAS-enabled VCG.

LCAS VCGs treat failures unidirectionally, meaning that failures of the transmit or receive points occur independently of each other. The LCAS-RX-FAIL condition can occur on the receive side of an LCAS VCG member for the following reasons:

SDH path failure (a unidirectional failure as seen by the receive side).

VCAT member is set out of group at the transmit side, but is set in group at the receive side.

VCAT member does not exist at the transmit side but does exist and is in group at the receive side.

The condition can be raised during provisioning operations on LCAS VCGs but should clear when the provisioning is completed.

Software-enabled LCAS VCGs treat failure bidirectionally, meaning that both directions of a VCG member are considered failed if either transmit or receive fails. The LCAS-RX-FAIL condition is raised on these VCG members when a member receive side fails due to a SDH path failure.


Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.



Note ML-Series cards are LCAS-enabled. ML-Series and FC_MR-4 cards are SW-LCAS enabled.


Clear the LCAS-RX-FAIL Condition


Step 1 Check for and clear any line or path alarms.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.180  LCAS-RX-GRP-ERR

Default Severity: Major (MJ), Service-Affecting (SA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS Sink Group Error condition is raised against ML-MR-10 and CE-MR-10 Ethernet cards. This condition is raised if the LCAS member sink has a group error.

Clear the LCAS-RX-GRP-ERR Condition


Step 1 Clear any LCAS member sink group errors.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).


2.7.181  LCAS-TX-ADD

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-Series Ethernet and CE-series cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed. The condition clears after provisioning is completed.


Note LCAS-TX-ADD is an informational condition and does not require troubleshooting.



Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


2.7.182  LCAS-TX-DNU

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: VCTRM-HP, VCTRM-LP

The LCAS VCG Member Transmit Side In Do Not Use condition is raised on FC_MR-4 cards, ML-Series Ethernet, and CE-series cards when the transmit side of an LCAS VCG member is in the do-not use state. For a unidirectional failure, this condition is only raised at the source node. The LCAS-TX-DNU condition is raised when the cable is unplugged.

The node reporting this condition likely reports an HP-RFI alarm, and the remote node likely reports a path alarm such as MS-AIS or "HP-UNEQ" alarm on page 2-131.


Note LCAS-TX-DNU is an informational condition and does not require troubleshooting.



Note For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.


2.7.183  LINK-KEEPALIVE

Default Severity: Critical (CR), Non-Service-Affecting (NSA)

SDH Logical Objects: ML1000, ML100T, MLFX, STMN

The LINK-KEEPALIVE alarm indicates that a span is not receiving a defined number of keep-alive messages on the ML card's IEEE 802.17 interface or Cisco proprietary RPR interface within allotted keep-alive timeout period. Although this alarm defaults to a Critical (CR) severity, it can be downgraded if the span is protected.

A LINK-KEEPALIVE alarm causes the "RPR-SF" alarm on page 2-215 to also be raised. LINK-KEEPALIVE is suppressed by the "RPR-PASSTHR" alarm on page 2-210. This alarm clears when a defined number of consecutive keep-alive messages is received on the interface.


Note In the Cisco IOS CLI, this alarm is also called KEEP-ALIVE-FAIL.



Note The GFP-UP-MISMATCH, GFP-CSF, GFP-LFD, and TPTFAIL alarms suppress the LINK-KEEPALIVE alarm even though the LINK-KEEPALIVE alarm has higher severity than the other alarms. The GFP alarms are promoted because the LINK-KEEPALIVE alarm information is contained within a GFP frame. The TPTFAIL alarm is promoted because it is a layer 1 alarm while LINK-KEEPALIVE is a layer 2 alarm.


Clear the LINK-KEEPALIVE Alarm


Step 1 Verify that no SDH or GFP circuit alarms that could impact Ethernet data traffic are present. If any are present, clear them using the relevant procedures in this chapter.

Step 2 Verify that the "DATA-CRC" alarm on page 2-78 is not present. If it is present, complete the trouble-clearing procedure.

Step 3 Verify that the keep-alive on this IEEE 802.17b-based RPR station has the same value as its neighboring RPR-IEEE stations.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.184  LKOUTPR-S

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

The Lockout of Protection Span condition occurs when span traffic is locked out of a protect span using the Lockout of Protect command. This condition is visible on the Alarms, Conditions, and History tabs in network view after the lockout has occurred and accompanies the FE-LOCKOUTPR-SPAN condition. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

Clear the LKOUTPR-S Condition


Step 1 Complete the "Clear an MS-SPRing External Switching Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.185  LMP-FAIL

Default Severity:Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Objects: CTRL, TLINK, STMN

SDH Logical Objects: GE

The Link Management Protocol Fail alarm is raised by the TCC2/TCC2P card when an LMP control channel fails or when there is a traffic engineering (TE) link correlation error. When the alarm is raised against a control channel, it uses a control channel (CTRLx) AID. When the alarm is raised against a TE link, a TE link AID (TLINKx) is used.

The alarm clears when the control channel or TE link is restored.


Note LMP-FAIL occurs independently of the condition hierarchy between the "LMP-SD" alarm on page 2-148, the "LMP-SF" alarm on page 2-149, or the "LMP-UNALLOC" alarm on page 2-150.



Note When the LMP-FAIL alarm is reported against a control channel (CTRLx) AID, it only refers to control channel failure. It does not directly indicate data link or traffic engineering link status.



Note When the LMP-FAIL alarm is reported against a TE link AID (TLINKx), it refers only to TE link status, not to control channel or data link status.


Clear the LMP-FAIL Alarm


Step 1 Verify the AID (CTRLx or TLINKx) of the alarm.

Step 2 If the alarm is against the control channel AID, this is caused by mismatched control channel parameters between the near-end ONS 15454 SDH and the far-end node (which may be another vendor's equipment). Complete the following steps:

a. Determine whether both near-end and far-end sides of the control channel are in the Unlocked administrative state:

Click the Provisioning > Comm Channels > LMP > Control Channel tabs and view the Admin State column content for the channel.

If the status does not say Unlocked, change it and click Apply.


Note You can also view the TE link operational status on the LMP > TE link tab.


b. Determine whether the near-end node LMP configuration contains the far-end node's IP address as its remote node IP. Also verify that the near-end node's LMP configuration uses the LMP node ID as its own remote node ID. If one or more of these values is incorrect, enter it correctly.

c. Determine whether the far-end node LMP configuration contains the near-end node's IP address as its remote node IP. Also verify that the far-end node's LMP configuration uses the LMP node ID as its own remote node ID. If one or more of these values is incorrect, enter it correctly.

d. Verify that the far-end node is using the near-end node's IP address as its remote node IP address, and that the far end is also using the LMP node ID as its remote node ID. Update the far end's values if they are incorrect.

Step 3 If instead the alarm is raised against the TE link AID, complete the following steps:

a. Determine whether both near-end and far-end sides of the TE link are in the Unlocked administrative state. If either end is currently down, update its administrative state to Unlocked:

Click the Provisioning > Comm Channels > LMP > TE link tab.

If the status does not say Unlocked, change it and click Apply.

b. Determine whether the near-end node's remote TE link ID matches the far-end node's local TE link ID. If the near-end node's remote value is incorrect, enter it correctly.

c. Determine whether the far-end node's remote TE link ID corresponds to the near-end node's local TE link ID. If the far-end node's remote value is incorrect, enter it correctly.

Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.186  LMP-SD

Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Object: GE

The LMP Data Link Signal Degrade condition occurs for when the TCC2/TCC2P receives an LMP link summary or channel status message that the control channel is not available from the far end, so the data link level of service is not guaranteed. The degrade range is provisionable.

LMP-SD clears when the TCC2/TCC2P receives a link summary or channel status message reporting that the data link is in the Signal Okay (OK) state.

LMP-SD is part of an alarm hierarchy that includes the "LMP-SF" alarm on page 2-149 and the "LMP-UNALLOC" alarm on page 2-150. The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end LOS alarms for the DWDM client. LMP-SD, however, does not suppress LOS.

This condition clears when the far-end trouble has been cleared.

Clear the LMP-SD Condition


Step 1 Look for and clear any of the following alarms in Table 2-13 and Table 2-14 occurring on the far-end port. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide, R7.x for DWDM trunk (Table 2-13) and client (Table 2-14) alarm trouble-clearing procedures.

Table 2-13 Transponder Trunk Alarms that Cause LMP-SD 

Trunk Port Alarm
LMP Failure
Direction

SD

SD

Tx

OTUK-SD

SD

Tx

ODUK-SD-PM

SD

Tx

ODUK-SD-TCM1

SD

Tx

ODUK-SD-TCM2

SD

Tx


Table 2-14 Transponder Client Alarm that Causes LMP-SD 

Client Port Alarm
LMP Failure
Direction

SD

SD

Rx


Step 2 If the LMP-SD condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.187  LMP-SF

Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Object: GE

The LMP Data Link Signal Fail condition notifies the near-end user of a far-end problem (and thus is NSA for the near end). The near-end's TCC2/TCC2P receives an LMP link summary or channel status message that the data link service has failed. The signal fail threshold provisionable.

LMP-SF clears when the TCC2/TCC2P receives a link summary or channel status message reporting that the data link is in the Signal Okay (OK) state.

LMP-SF is part of an alarm hierarchy that includes the "LMP-SD" alarm on page 2-148 and the "LMP-UNALLOC" alarm on page 2-150. The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end LOS for the DWDM client, but LMP-SD does not.

This condition clears when the far-end trouble has been cleared.

Clear the LMP-SF Condition


Step 1 Look for and clear any of the following alarms in Table 2-15, Table 2-16, or Table 2-17 occurring on the far-end port. The card alarms are located in this chapter. The Cisco ONS 15454 DWDM Troubleshooting Guide, R7.x contains trouble-clearing procedures for DWDM trunk (Table 2-16) and client (Table 2-17) alarms.

Table 2-15 Transponder Card Alarms that Cause LMP-SF 

Card Alarm
LMP Failure
Direction

EQPT

SF

Tx

IMPROPRMVL

SF

Tx


Table 2-16 Transponder Trunk Alarms that Cause LMP-SF 

Trunk Port Alarm
LMP Failure
Direction

LOS

SF

Tx

OTUK-LOF

SF

Tx

OTUK-AIS

SF

Tx

LOM

SF

Tx

OTUK-SF

SF

Tx

ODUK-SF-PM

SF

Tx

ODUK-SF-TCM1

SF

Tx

ODUK-SF-TCM2 SF

SF

Tx

FEC-MISM

SF

Tx


Table 2-17 Transponder Client Alarms that Cause LMP-SF 

Client Alarm
LMP Failure
Direction

LOS

SF

Rx

SIGLOSS

SF

Rx

SYNCLOSS

SF

Rx

CARLOSS

SF

Rx

LOF

SF

Rx


Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.188  LMP-UNALLOC

Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Object: STMN

DWDM Logical Object: GE

The LMP Data Link Unallocated condition is raised when the TCC2/TCC2P receives an LMP link summary or channel status message reporting that the data link as unallocated for data traffic. The condition clears when the data link is allocated and sends an LMP link summary or channel status message to this effect. If a data link has the LMP-UNALLOC alarm raised against it, this should suppress all other alarms on the client port, since the far-end node is not using the errored port. (Consequently you do not have to clear any alarms on the far-end node's unused port.)

LMP-UNALLOC is part of an alarm hierarchy that includes the "LMP-SD" alarm on page 2-148 and the "LMP-SF" alarm on page 2-149. The hierarchy is as follows: If LMP-UNALLOC is raised, LMP-SF and LMP-SD are suppressed. If LMP-SF is raised, it suppresses LMP-SD. LMP-SF and LMP-UNALLOC both suppress near-end DWDM client alarms, but LMP-SD does not.

In most cases, this condition is an informational notice at the near-end node that the far-end port is not being utilized. If, however, the far-end port should be allocated for traffic, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.

2.7.189  LOA

Default Severity: Critical (CR), Service-Affecting (SA)

SDH Logical Object: VCG

The Loss of Alignment on a VCG is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.


Note This alarm occurs only if you provision circuits outside of CTC, such as by using TL1.


Clear the LOA Alarm


Step 1 In network view, click the Circuits tab.

Step 2 Click the alarmed VCG and then click Edit.

Step 3 In the Edit Circuit dialog box, view the source and destination circuit slots, ports, and VC4s.

Step 4 Identify whether the circuit travels across different fibers. If it does, complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit using the procedure in the "Create Circuits and Tunnels" chapter in the Cisco ONS 15454 SDH Procedure Guide.

Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.190  LOCKOUT-REQ

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

SDH Logical Objects: EQPT, STMN, VCMON-HP, VCMON-LP

DWDM Logical Objects: 2R, ESCON, FC, GE, ISC, TRUNK

The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an STM-N port in a 1+1 facility protection group. This can be accomplished by locking traffic onto the working port with the LOCK ON command (thus locking it off the protect port), or locking it off the protect port with the LOCK OUT command. In either case, the protect port will show "Lockout of Protection," and the Conditions window will show the LOCKOUT-REQ condition.

A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Clear the LOCKOUT-REQ Condition


Step 1 Complete the "Clear a Card or Port Lock On or Lock Out Command" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country.


2.7.191  LOF (BITS)

Default Severity: Minor (MN), Non-Service-Affecting (NSA)

SDH Logical Object: BITS

The Loss of Frame (LOF) BITS alarm occurs when a port on the TCC2/TCC2P card BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 SDH has lost frame delineation in the incoming data.


Note The procedure assumes that the BITS timing reference signal is functioning properly and that the alarm is not appearing during node turn-up.


Clear the LOF (BITS) Alarm


Step 1 Verify that the line framing and line coding match between the BITS input and the TCC2/TCC2P card by completing the following steps:

a. In node view or card view, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.

c. Click the Provisioning > Timing > BITS Facilities tabs to display the General Timing window.

d. Verify that the value listed in Coding matches the coding of the BITS timing source (either B8ZS or AMI).

e. If the coding does not match, click the BITS-1 or BITS2 Coding field and choose the appropriate coding from the drop-down list.

f. Verify that the value listed in the Framing field matches the framing of the BITS timing source (either ESF or SF).

g. If the framing does not match, click the BITS-1 or BITS-2 Framing field and choose the appropriate framing from the drop-down list.


Note On the timing subtab, the binary 8-zero substitution (B8ZS) coding field is normally paired with Extended Superframe (ESF) in the Framing field and the alternate mark inversion (AMI) coding field is normally paired with SF (D4) in the Framing field.


Step 2 If the alarm does not clear when the line framing and line coding match between the BITS input and the TCC2/TCC2P card, replace the TCC2/TCC2P card by using the "Physically Replace a Traffic Card" procedure.


Caution Always use the supplied ESD wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.


Note When you replace a card with the identical type of card, you do not need to make any changes to the database.


Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.


2.7.192  LOF (DS1, DS3, E1, E4, STM1E, STMN)

Default Severity: Critical (CR), Service-Affecting (SA) for DS3, E4, STMN, STM1E; Default Severity: Major (MJ), Service-Affecting (SA) for DS1, E1

SDH Logical Objects: DS1, DS3, E1, E4, STM1E, STMN

An LOF alarm on a DS1i-N-14, DS3i-N-12, E1-N-14, or E1-42 card for these objects means that the receiving ONS 15454 SDH has lost frame delineation in the incoming data. LOF occurs when the SDH overhead loses a valid framing pattern for three seconds. Receiving two consecutive valid patterns clears the alarm.

Clear the LOF (DS1, DS3, E1, E4, STM1E, STMN) Alarm


Step 1 Verify that the line framing and line coding match between the port and the signal source by completing the following steps:

a. In CTC, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the signal source for the card reporting the alarm. You could need to contact your network administrator for the format information.

c. Display the card view of the reporting card.

d. Click the Provisioning > Line tabs.

e. Verify that the line type of the reporting port matches the line type of the signal source.

f. If the signal source line type does not match the reporting port, click Line Type and choose the appropriate type from the drop-down list.

g. Verify that the reporting Line Coding matches the signal source's line type.

h. If the signal source line coding does not match the reporting port, click Line Coding and choose the appropriate type from the drop-down list.

i. Click Apply.

Step 2 If the alarm does not clear when the coding and framing of the ONS 15454 SDH match the coding and framing of the signal source, replace the card.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.


Note When replacing a card with the identical type of card, you do not need to change the CTC database.


Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country in order to report a Service-Affecting (SA) problem.