Cisco ONS 15454 SDH Troubleshooting Guide, Release 4.6
Chapter 2, Alarm Troubleshooting
Download this chapter
Chapter 2, Alarm TroubleshootingChapter 2, Alarm Troubleshooting
Download the complete book
Cisco ONS 15454 SDH Troubleshooting Guide, Release 4.6Cisco ONS 15454 SDH Troubleshooting Guide, Release 4.6 (PDF - 5 MB)
give_us_feedback

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  NA Conditions

2.1.5  NR Conditions

2.2  Alarms and Conditions Indexed By Alphabetical Entry

2.3  Logical Object Type Definitions

2.4  Alarm Index by Logical Object Type

2.5  Trouble Notifications

2.5.1  Conditions

2.5.2  Severities

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  AMPLI-INIT

Clear the AMPLI-INIT Condition

2.7.5  APC-DISABLED

Clear the APC-DISABLED Alarm

2.7.6  APC-FAIL

Clear the APC-FAIL Alarm

2.7.7  APSB

Clear the APSB Alarm

2.7.8  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.9  APSC-IMP

Clear the APSC-IMP Alarm

2.7.10  APSCINCON

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

2.7.11  APSCM

Clear the APSCM Alarm

2.7.12  APSCNMIS

Clear the APSCNMIS Alarm

2.7.13  APSIMP

Clear the APSIMP Condition

2.7.14  AS-CMD

Clear the AS-CMD Condition

2.7.15  AS-MT

Clear the AS-MT Condition

2.7.16  AU-AIS

Clear the AU-AIS Condition

2.7.17  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.18  AUD-LOG-LOW

2.7.19  AU-LOF

Clear the AU-LOF Alarm

2.7.20  AU-LOP

Clear the AU-LOP Alarm

2.7.21  AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.7.22  AUTORESET

Clear the AUTORESET Alarm

2.7.23  AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-SNCP Condition

2.7.24  AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.7.25  AUTOSW-PDI-SNCP

Clear the AUTOSW-PDI-SNCP Condition

2.7.26  AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.7.27  AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.7.28  AUTOSW-UNEQ-SNCP (HPMon)

Clear the AUTOSW-UNEQ-SNCP (HPMon) Condition

2.7.29  AUTOSW-UNEQ-SNCP (LPMon)

Clear the AUTOSW-UNEQ-SNCP (LPMon) Alarm

2.7.30  AWG-DEG

Clear the AWG-DEG Alarm

2.7.31  AWG-FAIL

Clear the AWG-FAIL Alarm

2.7.32  AWG-OVERTEMP

Clear the AWG-OVERTEMP Alarm

2.7.33  AWG-WARM-UP

2.7.34  BATFAIL

Clear the BATFAIL Alarm

2.7.35  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.36  CARLOSS (DWDM Client)

Clear the CARLOSS (DWDM Client) Alarm

2.7.37  CARLOSS (DWDM Trunk)

Clear the CARLOSS (DWDM Trunk) Alarm

2.7.38  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.39  CARLOSS (E-Series Ethernet)

Clear the CARLOSS (E-Series Ethernet) Alarm

2.7.40  CARLOSS (G-Series Ethernet)

Clear the CARLOSS (G-Series Ethernet) Alarm

2.7.41  CARLOSS (ML-Series Ethernet)

Clear the CARLOSS (ML-Series Ethernet) Alarm

2.7.42  CASETEMP-DEG

Clear the CASETEMP-DEG Alarm

2.7.43  CKTDOWN

Clear the CKTDOWN Alarm

2.7.44  CLDRESTART

Clear the CLDRESTART Condition

2.7.45  COMIOXC

Clear the COMIOXC Alarm

2.7.46  COMM-FAIL

Clear the COMM-FAIL Alarm

2.7.47  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.48  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm on the TCC2 Card

2.7.49  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.50  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.51  CTNEQPT-MISMATCH

Clear the CTNEQPT-MISMATCH Condition

2.7.52  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.53  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.54  DATAFLT

Clear the DATAFLT Alarm

2.7.55  DBOSYNC

Clear the DBOSYNC Alarm

2.7.56  DSP-COMM-FAIL

2.7.57  DSP-FAIL

Clear the DSP-FAIL Alarm

2.7.58  DS3-MISM

Clear the DS3-MISM Condition

2.7.59  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.60  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.61  EHIBATVG

Clear the EHIBATVG Alarm

2.7.62  ELWBATVG

Clear the ELWBATVG Alarm

2.7.63  EOC

Clear the EOC Alarm

2.7.64  EOC-L

2.7.65  EQPT

Clear the EQPT Alarm

2.7.66  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.67  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.68  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.69  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.7.70  EXCCOL

Clear the EXCCOL Alarm

2.7.71  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.72  EXERCISE-SPAN-FAIL

Clear the EXERCISE-SPAN-FAIL Condition

2.7.73  EXT

Clear the EXT Alarm

2.7.74  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.75  E3-ISD

2.7.76  FAILTOSW

Clear the FAILTOSW Condition

2.7.77  FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.7.78  FAILTOSW-LO

Clear the FAILTOSW-LO Condition

2.7.79  FAILTOSWR

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

2.7.80  FAILTOSWS

Clear the FAILTOSWS Condition

2.7.81  FAN

Clear the FAN Alarm

2.7.82  FANDEGRADE

Clear the FANDEGRADE Alarm

2.7.83  FE-AIS

Clear the FE-AIS Condition

2.7.84  FE-DS1-MULTLOS

2.7.85  FE-DS1-NSA

2.7.86  FE-DS1-SA

2.7.87  FE-DS1-SNGLLOS

2.7.88  FE-DS3-NSA

2.7.89  FE-DS3-SA

2.7.90  FEC-MISM

Clear the FEC-MISM Alarm

2.7.91  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.92  FE-E1-MULTLOS

Clear the FE-E1-MULTLOS Condition

2.7.93  FE-E1-NSA

Clear the FE-E1-NSA Condition

2.7.94  FE-E1-SA

Clear the FE-E1-SA Condition

2.7.95  FE-E1-SNGLLOS

Clear the FE-E1-SNGLLOS Condition

2.7.96  FE-E3-NSA

Clear the FE-E3-NSA Condition

2.7.97  FE-E3-SA

Clear the FE-E3-SA Condition

2.7.98  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.99  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.100  FE-IDLE

Clear the FE-IDLE Condition

2.7.101  FE-LOCKOUTOFPR-ALL

2.7.102  FE-LOCKOUTOFPR-RING

2.7.103  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.104  FE-LOCKOUTOFWK-RING

2.7.105  FE-LOCKOUTOFWK-SPAN

2.7.106  FE-LOF

Clear the FE-LOF Condition

2.7.107  FE-LOS

Clear the FE-LOS Condition

2.7.108  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.109  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.110  FEPRLF

Clear the FEPRLF Alarm on an MS-SPRing

2.7.111  FE-SDPRLF

Clear the FE-SDPRLF Alarm on an MS-SPRing

2.7.112  FIBERTEMP-DEG

Clear the FIBERTEMP-DEG Alarm

2.7.113  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.114  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.115  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.116  FRCDSWTOINT

2.7.117  FRCDSWTOPRI

2.7.118  FRCDSWTOSEC

2.7.119  FRCDSWTOTHIRD

2.7.120  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.121  FSTSYNC

2.7.122  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.123  GAIN-HDEG

Clear the GAIN-HDEG Alarm

2.7.124  GAIN-HFAIL

Clear the GAIN-HFAIL Alarm

2.7.125  GAIN-LDEG

Clear the GAIN-LDEG Alarm

2.7.126  GAIN-LFAIL

Clear the GAIN-LFAIL Alarm

2.7.127  GCC-EOC

Clear the GCC-EOC Alarm

2.7.128  GE-OOSYNC

Clear the GE-OOSYNC Alarm

2.7.129  HIBATVG

Clear the HIBATVG Alarm

2.7.130  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.131  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.132  HITEMP

Clear the HITEMP Alarm

2.7.133  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.134  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.135  HP-RFI

Clear the HP-RFI Condition

2.7.136  HP-TIM

Clear the HP-TIM Alarm

2.7.137  HP-UNEQ

Clear the HP-UNEQ Alarm

2.7.138  I-HITEMP

Clear the I-HITEMP Alarm

2.7.139  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.140  INC-GFP-OUTOFFRAME

Clear the INC-GFP-OUTOFFRAME Condition

2.7.141  INC-GFP-SIGLOSS

Clear the INC-GFP-SIGLOSS Condition

2.7.142  INC-GFP-SYNCLOSS

Clear the INC-GFP-SYNCLOSS Condition

2.7.143  INC-ISD

2.7.144  INC-SIGLOSS

Clear the INC-SIGLOSS Alarm

2.7.145  INC-SYNCLOSS

Clear the INC-SYNCLOSS Alarm

2.7.146  INHSWPR

Clear the INHSWPR Condition

2.7.147  INHSWWKG

Clear the INHSWWKG Condition

2.7.148  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.149  INVMACADR

2.7.150  IOSCFGCOPY

2.7.151  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.152  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.7.153  LAN-POL-REV

Clear the LAN-POL-REV Condition

2.7.154  LASER-APR

2.7.155  LASERBIAS-DEG

Clear the LASERBIAS-DEG Alarm

2.7.156  LASERBIAS-FAIL

Clear the LASERBIAS-FAIL Alarm

2.7.157  LASEREOL

Clear the LASEREOL Alarm

2.7.158  LASERTEMP-DEG

Clear the LASERTEMP-DEG Alarm

2.7.159  LKOUTPR-R

2.7.160  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.161  LKOUTWK-R

2.7.162  LKOUTWK-S (NA)

2.7.163  LMP-HELLODOWN

Clear the LMP-HELLODOWN Alarm

2.7.164  LMP-NDFAIL

Clear the LMP-NDFAIL Alarm

2.7.165  LOA

Clear the LOA Alarm

2.7.166  LOC

Clear the LOC Alarm

2.7.167  LOCKOUTOFPR

2.7.168  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.169  LOCKOUT-REQ-RING

2.7.170  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.171  LOF (DS-3, E-1, E-4, STM-N, STM1-E)

Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm

2.7.172  LOF (DWDM Client)

Clear the LOF (DWDM Client) Alarm

2.7.173  LOF (DWDM Trunk)

Clear the LOF (DWDM Trunk) Alarm

2.7.174  LOM

Clear the LOM Alarm

2.7.175  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.176  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.177  LOS (DS-3, E-1, E-3, STM-N, STM-1E)

Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm

2.7.178  LOS (DWDM Client)

Clear the LOS (DWDM Client) Alarm

2.7.179  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.180  LOS (OTN)

Clear the LOS (OTN) Alarm

2.7.181  LOS-P (TRUNK)

2.7.182  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.7.183  LPBKCRS

Clear the LBKCRS Condition

2.7.184  LPBKDS1FEAC

2.7.185  LPBKDS1FEAC-CMD

2.7.186  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.187  LPBKDS3FEAC-CMD

2.7.188  LPBKE1FEAC

2.7.189  LPBKE3FEAC

2.7.190  LPBKE3FEAC-CMD

2.7.191  LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

Clear the LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E) Condition

2.7.192  LPBKFACILITY (DWDM Client)

2.7.193  LPBKFACILITY (G-Series)

Clear the LPBKFACILITY (G-Series) Condition

2.7.194  LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

Clear the LPBKTERMINAL (DS-3, D-1, E-3, E-4, STM-N, STM-1E) Condition

2.7.195  LPBKTERMINAL (DWDM)

2.7.196  LPBKTERMINAL(G-Series Ethernet)

Clear the LPBKTERMINAL (G-Series) Condition

2.7.197  LP-PLM

Clear the LP-PLM Alarm

2.7.198  LP-RFI

Clear the LP-RFI Condition

2.7.199  LP-TIM

Clear the LP-TIM Alarm

2.7.200  LP-UNEQ

Clear the LP-UNEQ Alarm

2.7.201  LWBATVG

Clear the LWBATVG Alarm

2.7.202  MAN-REQ

Clear the MAN-REQ Condition

2.7.203  MANRESET

2.7.204  MANSWTOINT

2.7.205  MANSWTOPRI

2.7.206  MANSWTOSEC

2.7.207  MANSWTOTHIRD

2.7.208  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.209  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.210  MEA (BP)

Clear the MEA (BP) Alarm

2.7.211  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.212  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.213  MEM-GONE

2.7.214  MEM-LOW

2.7.215  MFGMEM (AEP, AIE)

Clear the MFGMEM Alarm

2.7.216  MFGMEM (Backplane or Fan-Tray Assembly)

Clear the MFGMEM Alarm on the Backplane or Fan-Tray Assembly

2.7.217  MS-AIS

Clear the MS-AIS Condition

2.7.218  MS-EOC

Clear the MS-EOC Alarm

2.7.219  MS-RFI

Clear the MS-RFI Condition

2.7.220  MSSP-OOSYNC

Clear the MSSP-OOSYNC Alarm

2.7.221  NO-CONFIG

Clear the NO-CONFIG Alarm

2.7.222  NOT-AUTHENTICATED

2.7.223  NTWTPINC

2.7.224  OCHNC-ACTIV-FAIL

2.7.225  OCHNC-DEACTIV-FAIL

2.7.226  OCHNC-FAIL

2.7.227  OCHNC-INC

2.7.228  ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.7.229  ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.7.230  ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.7.231  ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.7.232  ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.7.233  ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.7.234  ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.7.235  OOU-TPT

Clear the OOT-TPT Condition

2.7.236  OPTNTWMIS

Clear the OPTNTWMIS Alarm

2.7.237  OPWR-HDEG

Clear the OPWR-HDEG Alarm

2.7.238  OPWR-HFAIL

Clear the OPWR-HFAIL Alarm

2.7.239  OPWR-LDEG

Clear the OPWR-LDEG Alarm

2.7.240  OPWR-LFAIL

Clear the OPWR-LFAIL Alarm

2.7.241  OTUK-AIS

Clear the OTUK-AIS Condition

2.7.242  OTUK-BDI

Clear the OTUK-BDI Condition

2.7.243  OTUK-LOF

Clear the OTUK-LOF Alarm

2.7.244  OTUK-SD

Clear the OTUK-SD Condition

2.7.245  OTUK-SF

Clear the OTUK-SF Condition

2.7.246  OTUK-TIM

Clear the OTUK-TIM Alarm

2.7.247  OUT-OF-SYNC

Clear the OUT-OF-SYNC Condition

2.7.248  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.249  PORT-CODE-MISM

Clear the PORT-CODE-MISM Alarm

2.7.250  PORT-COMM-FAIL

Clear the PORT-COMM-FAIL Alarm

2.7.251  PORT-MISMATCH

2.7.252  PORT-MISSING

Clear the PORT-MISSING Alarm

2.7.253  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.254  PROTNA

Clear the PROTNA Alarm

2.7.255  PTIM

Clear the PTIM Alarm

2.7.256  PWR-A

2.7.257  PWR-B

2.7.258  PWR-REDUN

Clear the PWR-REDUN Alarm

2.7.259  RAI

Clear the RAI Condition

2.7.260  RCVR-MISS

Clear the RCVR-MISS Alarm

2.7.261  RFI

Clear the RFI Condition

2.7.262  RING-ID-MIS

Clear the RING-ID-MIS Alarm

2.7.263  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.264  RING-SW-EAST

2.7.265  RING-SW-WEST

2.7.266  RSVP-HELLODOWN

Clear the RSVP-HELLODOWN Alarm

2.7.267  RUNCFG-SAVENEED

2.7.268  SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition

2.7.269  SD (DWDM Client)

Clear the SD (DWDM Client) Condition

2.7.270  SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.7.271  SD-L

2.7.272  SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

Clear the SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N) Condition

2.7.273  SF (DWDM Client)

Clear the SF (DWDM Client) Condition

2.7.274  SFBER-EXCEED-HO

Clear the SFBER-EXCEED-HO Condition

2.7.275  SF-L

2.7.276  SFTWDOWN

2.7.277  SH-INS-LOSS-VAR-DEG-HIGH

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

2.7.278  SH-INS-LOSS-VAR-DEG-LOW

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

2.7.279  SHUTTER-OPEN

Clear the SHUTTER-OPEN Condition

2.7.280  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.281  SPAN-SW-EAST

2.7.282  SPAN-SW-WEST

2.7.283  SQUELCH

Clear the SQUELCH Condition

2.7.284  SQUELCHED

Clear the SQUELCHED Condition

2.7.285  SQM

Clear the SQM Alarm

2.7.286  SSM-DUS

2.7.287  SSM-FAIL

Clear the SSM-FAIL (BITS, STM-N) Alarm

2.7.288  SSM-LNC

2.7.289  SSM-OFF

2.7.290  SSM-PRC

2.7.291  SSM-PRS

2.7.292  SSM-RES

2.7.293  SSM-SDH-TN

2.7.294  SSM-SETS

2.7.295  SSM-SMC

2.7.296  SSM-STU

Clear the SSM-STU Condition

2.7.297  SSM-ST2

2.7.298  SSM-ST3

2.7.299  SSM-ST3E

2.7.300  SSM-ST4

2.7.301  SSM-TNC

2.7.302  SWMTXMOD

Clear the SWMTXMOD Alarm

2.7.303  SWTOPRI

2.7.304  SWTOSEC

2.7.305  SWTOTHIRD

2.7.306  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.307  SYNCPRI

Clear the SYNCPRI Alarm

2.7.308  SYNCSEC

Clear the SYNCSEC Alarm

2.7.309  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.310  SYSBOOT

2.7.311  TIM

Clear the TIM Alarm or Condition

2.7.312  TIM-MON

Clear the TIM-MON Alarm

2.7.313  TPTFAIL (FC_MR-4)

Clear the TPTFAIL (FC_MR-4) Alarm

2.7.314  TPTFAIL (G-Series)

Clear the TPTFAIL (G-Series) Alarm

2.7.315  TPTFAIL (ML-Series)

Clear the TPTFAIL (ML-Series) Alarm

2.7.316  TRMT

Clear the TRMT Alarm on the E1-N-14 Card

2.7.317  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.318  TU-AIS

Clear the TU-AIS Condition

2.7.319  TU-LOP

Clear the TU-LOP Alarm

2.7.320  TUNDERRUN

Clear the TUNDERRUN Alarm

2.7.321  TX-AIS

Clear the TX-AIS Condition

2.7.322  TX-RAI

Clear the TX-RAI Condition

2.7.323  UNC-WORD

Clear the UNC-WORD Condition

2.7.324  VCG-DEG

Clear the VCG-DEG Condition

2.7.325  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.326  VOA-HDEG

Clear the VOA-HDEG Alarm

2.7.327  VOA-HFAIL

Clear the VOA-HFAIL Alarm

2.7.328  VOA-LDEG

Clear the VOA-LDEG Alarm

2.7.329  VOA-LFAIL

Clear the VOA-LFAIL Alarm

2.7.330  WKSWPR

Clear the WKSWPR Condition

2.7.331  WTR

2.7.332  WVL-MISMATCH

Clear the WVL-MISMATCH alarm

2.8  DWDM and Non-DWDM Card LED Activity

2.8.1  DWDM Card LED Activity After Insertion

2.8.2  Non-DWDM Card LED Activity After Insertion

2.8.3  DWDM Card LED Activity During Reset

2.8.4  Non-DWDM Card LED Activity During Reset

2.8.5  Non-DWDM Cross-Connect LED Activity During Side Switch

2.8.6  Non-DWDM Card LED State After Successful Reset

2.9  Common Procedures in Alarm Troubleshooting

Identify a Ring Name or Node ID Number

Change a Ring Name Number

Change a Node ID Number

Verify Node Visibility for Other Nodes

Verify or Create Node DCC Terminations

Lock Out an MS-SPRing Span

Clear a Ring or Span External Switching Command

Clear an SNCP Lockout

Switch Protection Group Traffic with an External Switching Command

Side Switch the Active and Standby Cross-Connect Cards

Clear a Protection Group External Switching Command

Delete a Circuit

Clear a Loopback

Reset Active TCC2 Card and Activate Standby Card

Reset the Standby TCC2/TCC2P Card

Remove and Reinsert (Reseat) the Standby TCC2

Reset a Traffic Card in CTC

Verify BER Threshold Level

Physically Replace a Card

Remove and Reinsert (Reseat) a Card

Remove and Reinsert 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-4 provide lists of ONS 15454 SDH alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-8 provides a list of alarms organized by alarm type.

The troubleshooting procedure for an alarm applies to the Cisco Transport Controller (CTC) version of that alarm. If the troubleshooting procedure does not clear the 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 Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.

For alarm profile information, refer to the Cisco ONS 15454 SDH Procedure Guide.

2.1  Alarm Index by Default Severity

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.

2.1.1  Critical Alarms (CR)

Table 2-1 lists critical alarms.


2.1.2  Major Alarms (MJ)

Table 2-2 lists major alarms.

Table 2-2 Major Alarm Index 

APC-DISABLED

ELWBATVG

LWBATVG

APC-FAIL

EOC

MEM-GONE

APSCM

E-W-MISMATCH

MS-EOC

APSCNMIS

EXTRA-TRAF-PREEMPT

MSSP-OOSYNC

AU-LOF

FANDEGRADE

OPTNTWMIS

BATFAIL

FEC-MISM

PEER-NORESPONSE

CARLOSS (DWDM Client)

GCC-EOC

PRC-DUPID

CARLOSS (DWDM Trunk)

HIBATVG

RCVR-MISS

CARLOSS (EQPT)

HLDOVRSYNC

RING-ID-MIS (for OSCRing only)

CARLOSS (E-Series Ethernet)

INC-SIGLOSS

RING-MISMATCH

CARLOSS (G-Series Ethernet)

INC-SYNCLOSS

SQM (for LPTerm)

CARLOSS (ML-Series Ethernet)

INVMACADR

SYSBOOT

CONTBUS-A-18

LASERBIAS-FAIL

TIM (for STM-1E only)

CONTBUS-A-18

LOF (BITS)

TPTFAIL (FC_MR-4)

CONTBUS-IO-B

LOF (DS-3, E-1, E-4, STM-N, STM1-E) (for E-1 only)

TPTFAIL (G-Series)

CONTBUS-B-18

LOM (for LPTerm only)

TPTFAIL (ML-Series)

DBOSYNC

LOS (BITS)

TRMT

DSP-COMM-FAIL

LOS (DS-3, E-1, E-3, STM-N, STM-1E) (for E-1 only)

TRMT-MISS

DSP-FAIL

LP-PLM

TU-LOP

DUP-IPADDR

LP-TIM

TUNDERRUN

DUP-NODENAME

LP-UNEQ

WVL-MISMATCH

EHIBATVG

   

2.1.3  Minor Alarms (MN)

Table 2-3 lists minor alarms.


2.1.4  NA Conditions

Table 2-4 lists not alarmed conditions.

Table 2-4 NA Conditions Index 

ALS

FORCED-REQ-RING

OOU-TPT

AMPLI-INIT

FORCED-REQ-SPAN

OUT-OF-SYNC

AS-CMD

FRCDSWTOPRI

OTUK-SD

AS-MT

FRCDSWTOSEC

OTUK-SF

AUD-LOG-LOSS

FRCDSWTOTHIRD

OTUK-TIM

AUD-LOG-LOW

FRNGSYNC

PORT-MISMATCH (for FC_MR-4 only)

AUTOSW-LOP-SNCP (for HPMon)

FULLPASSTHR-BI

RAI

AUTOSW-SDBER-SNCP

INC-GFP-OUTOFFRAME

RING-ID-MIS (for STM-N only)

AUTOSW-SFBER-SNCP

INC-GFP-SIGLOSS

RING-SW-EAST

AUTOSW-UNEQ-SNCP (HPMon)

INC-GFP-SYNCLOSS

RING-SW-WEST

AWG-WARM-UP

INC-ISD

RUNCFG-SAVENEED

CLDRESTART

INHSWPR

SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

CTNEQPT-MISMATCH

INHSWWKG

SD (DWDM Client)

DS3-MISM

INTRUSION-PSWD

SDBER-EXCEED-HO

ETH-LINKLOSS

IOSCFGCOPY

SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

EXERCISE-RING-FAIL

KB-PASSTHR

SF (DWDM Client)

EXERCISE-SPAN-FAIL

LASER-APR

SFBER-EXCEED-HO

E3-ISD

LKOUTPR-S

SHUTTER-OPEN

FAILTOSW

LOCKOUT-REQ

SPAN-SW-EAST

FAILTOSW-HO

LPBKCRS

SPAN-SW-WEST

FAILTOSW-LO

LPBKDS3FEAC

SQUELCH

FAILTOSWR

LPBKDS3FEAC-CMD

SQUELCHED

FAILTOSWS

LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

SSM-DUS

FE-AIS

LPBKFACILITY (DWDM Client)

SSM-LNC

FE-EQPT-NSA

LPBKFACILITY (G-Series)

SSM-OFF

FE-E1-MULTLOS

LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

SSM-PRC

FE-E1-NSA

LPBKTERMINAL (DWDM)

SSM-SETS

FE-E1-SA

LPBKTERMINAL(G-Series Ethernet)

SSM-STU

FE-E1-SNGLLOS

MAN-REQ

SSM-TNC

FE-E3-NSA

MANRESET

SWTOPRI

FE-E3-SA

MANSWTOINT

SWTOSEC

FE-FRCDWKSWPR-RING

MANSWTOPRI

SWTOTHIRD

FE-FRCDWKSWPR-SPAN

MANSWTOSEC

SYNC-FREQ

FE-IDLE

MANSWTOTHIRD

TIM (for STM-N only)

FE-LOCKOUTOFPR-SPAN

MANUAL-REQ-RING

TX-RAI

FE-LOF

MANUAL-REQ-SPAN

UNC-WORD

FE-LOS

NO-CONFIG

VCG-DEG

FE-MANWKSWPR-RING

ODUK-SD-PM

VCG-DOWN

FE-MANWKSWPR-SPAN

ODUK-SF-PM

WKSWPR

FORCED-REQ

ODUK-TIM-PM

WTR


2.1.5  NR Conditions

Table 2-4 lists not reported conditions.


2.2  Alarms and Conditions Indexed By Alphabetical Entry

Table 2-6 lists alarms and conditions by the name displayed on the CTC Alarms window or Conditions window.

Table 2-6 Alphabetical Alarm Index 

AIS

FIBERTEMP-DEG

NO-CONFIG

ALS

FORCED-REQ

NOT-AUTHENTICATED

AMPLI-INIT

FORCED-REQ-RING

ODUK-AIS-PM

APC-DISABLED

FORCED-REQ-SPAN

ODUK-BDI-PM

APC-FAIL

FRCDSWTOINT

ODUK-LCK-PM

APSB

FRCDSWTOPRI

ODUK-OCI-PM

APSCDFLTK

FRCDSWTOSEC

ODUK-SD-PM

APSC-IMP

FRCDSWTOTHIRD

ODUK-SF-PM

APSCINCON

FRNGSYNC

ODUK-TIM-PM

APSCM

FSTSYNC

OOU-TPT

APSCNMIS

FULLPASSTHR-BI

OPTNTWMIS

AS-CMD

GAIN-HDEG

OPWR-HDEG

AS-MT

GAIN-HFAIL

OPWR-HFAIL

AU-AIS

GAIN-LDEG

OPWR-LDEG

AUD-LOG-LOSS

GAIN-LFAIL

OPWR-LFAIL

AUD-LOG-LOW

GCC-EOC

OTUK-AIS

AU-LOF

GE-OOSYNC

OTUK-BDI

AU-LOP

HIBATVG

OTUK-LOF

AUTOLSROFF

HI-LASERBIAS

OTUK-SD

AUTORESET

HI-RXPOWER

OTUK-SF

AUTOSW-AIS-SNCP

HITEMP

OTUK-TIM

AUTOSW-LOP-SNCP

HI-TXPOWER

OUT-OF-SYNC

AUTOSW-SDBER-SNCP

HLDOVRSYNC

PEER-NORESPONSE

AUTOSW-SFBER-SNCP

HP-RFI

PORT-CODE-MISM

AUTOSW-UNEQ-SNCP (HPMon)

HP-TIM

PORT-COMM-FAIL

AUTOSW-UNEQ-SNCP (LPMon)

HP-UNEQ

PORT-MISMATCH

AWG-DEG

IMPROPRMVL

PORT-MISSING

AWG-FAIL

INC-GFP-OUTOFFRAME

PRC-DUPID

AWG-OVERTEMP

INC-GFP-SIGLOSS

PROTNA

AWG-WARM-UP

INC-GFP-SYNCLOSS

PTIM

BATFAIL

INC-ISD

PWR-REDUN

BKUPMEMP

INC-SIGLOSS

RAI

CARLOSS (DWDM Client)

INC-SYNCLOSS

RCVR-MISS

CARLOSS (DWDM Trunk)

INHSWPR

RFI

CARLOSS (EQPT)

INHSWWKG

RING-ID-MIS

CARLOSS (E-Series Ethernet)

INTRUSION-PSWD

RING-MISMATCH

CARLOSS (G-Series Ethernet)

INVMACADR

RING-SW-EAST

CARLOSS (ML-Series Ethernet)

IOSCFGCOPY

RING-SW-WEST

CASETEMP-DEG

KB-PASSTHR

RSVP-HELLODOWN

CKTDOWN

KBYTE-APS-CHANNEL-FAILURE

RUNCFG-SAVENEED

CLDRESTART

LASER-APR

SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

COMIOXC

LASERBIAS-DEG

SD (DWDM Client)

COMM-FAIL

LASERBIAS-FAIL

SDBER-EXCEED-HO

CONTBUS-A-18

LASEREOL

SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

CONTBUS-A-18

LASERTEMP-DEG

SF (DWDM Client)

CONTBUS-IO-B

LKOUTPR-S

SFBER-EXCEED-HO

CONTBUS-B-18

LMP-HELLODOWN

SFTWDOWN

CTNEQPT-MISMATCH

LMP-NDFAIL

SH-INS-LOSS-VAR-DEG-HIGH

CTNEQPT-PBPROT

LOA

SH-INS-LOSS-VAR-DEG-LOW

CTNEQPT-PBWORK

LOC

SHUTTER-OPEN

DATAFLT

LOCKOUT-REQ

SNTP-HOST

DBOSYNC

LOF (BITS)

SPAN-SW-EAST

DSP-COMM-FAIL

LOF (DS-3, E-1, E-4, STM-N, STM1-E)

SPAN-SW-WEST

DSP-FAIL

LOF (DWDM Client)

SQUELCH

DS3-MISM

LOF (DWDM Trunk)

SQUELCHED

DUP-IPADDR

LOM

SQM

DUP-NODENAME

LO-RXPOWER

SSM-DUS

EHIBATVG

LOS (BITS)

SSM-FAIL

ELWBATVG

LOS (DS-3, E-1, E-3, STM-N, STM-1E)

SSM-LNC

EOC

LOS (DWDM Client)

SSM-OFF

EQPT

LOS (FUDC)

SSM-PRC

EQPT-MISS

LOS (OTN)

SSM-SETS

ERROR-CONFIG

LO-TXPOWER

SSM-STU

ETH-LINKLOSS

LPBKCRS

SSM-TNC

E-W-MISMATCH

LPBKDS3FEAC

SWMTXMOD

EXCCOL

LPBKDS3FEAC-CMD

SWTOPRI

EXERCISE-RING-FAIL

LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

SWTOSEC

EXERCISE-SPAN-FAIL

LPBKFACILITY (DWDM Client)

SWTOTHIRD

EXT

LPBKFACILITY (G-Series)

SYNC-FREQ

EXTRA-TRAF-PREEMPT

LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

SYNCPRI

E3-ISD

LPBKTERMINAL (DWDM)

SYNCSEC

FAILTOSW

LPBKTERMINAL(G-Series Ethernet)

SYNCTHIRD

FAILTOSW-HO

LP-PLM

SYSBOOT

FAILTOSW-LO

LP-RFI

TIM

FAILTOSWR

LP-TIM

TIM-MON

FAILTOSWS

LP-UNEQ

TPTFAIL (FC_MR-4)

FAN

LWBATVG

TPTFAIL (G-Series)

FANDEGRADE

MAN-REQ

TPTFAIL (ML-Series)

FE-AIS

MANRESET

TRMT

FEC-MISM

MANSWTOINT

TRMT-MISS

FE-EQPT-NSA

MANSWTOPRI

TU-AIS

FE-E1-MULTLOS

MANSWTOSEC

TU-LOP

FE-E1-NSA

MANSWTOTHIRD

TUNDERRUN

FE-E1-SA

MANUAL-REQ-RING

TX-AIS

FE-E1-SNGLLOS

MANUAL-REQ-SPAN

TX-RAI

FE-E3-NSA

MEA (BP)

UNC-WORD

FE-E3-SA

MEA (EQPT)

VCG-DEG

FE-FRCDWKSWPR-RING

MEA (FAN)

VCG-DOWN

FE-FRCDWKSWPR-SPAN

MEM-GONE

VOA-HDEG

FE-IDLE

MEM-LOW

VOA-HFAIL

FE-LOCKOUTOFPR-SPAN

MFGMEM (AEP, AIE)

VOA-LDEG

FE-LOF

MFGMEM (Backplane or Fan-Tray Assembly)

VOA-LFAIL

FE-LOS

MS-AIS

WKSWPR

FE-MANWKSWPR-RING

MS-EOC

WTR

FE-MANWKSWPR-SPAN

MS-RFI

WVL-MISMATCH

FEPRLF

MSSP-OOSYNC

 

2.3  Logical Object Type Definitions

ONS 15454 SDH alarms are grouped according to their logical object types in alarm profile listings (for example: L2SC: CARLOSS). Each alarm entry in this chapter lists its type. These are defined in Table 2-7.

Table 2-7 Alarm Type/Object Definition 

AIE1

Alarm interface extension

BITS

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

BP

Backplane

CC

Unified control plane (UCP) communication channel

CTK

UCP circuit

DS-3

A DS-3 line on a DS-3 card

DWDM Client

The low-speed port, such as a TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G where the optical signal is dropped

DWDM Trunk

The optical or DWDM card carrying the high-speed signal

E1

E1-42 card

E3

E3-12 card

EQPT

A card in any of the 17 card slots. This object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, and VC

ETHER

Ethernet, such as for LAN cables

EXTSYNC

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

FAN

Fan-tray assembly

FCMR

Fiber channel

FUDC

SDH F1 User Data Channel

HDGE

High-density Gigabit Ethernet

L2SC

Layer 2 switching card (and Layer 3 for ML-Series) switching device

NE

The entire network element (node)

NERING

SDH NE2 ring

NESYNCH

SDH NE synchronization

PWR

Power equipment

STM-1E

Synchronous transfer mode 1 (speed) electrical interface

STM-N

Synchronous transfer mode (speed)

VCatGROUP

Virtual concatenation group

1 The AIE is referenced in some software windows, but is not used in this release.

2 Network element


2.4  Alarm Index by Logical Object Type

Table 2-8 gives the name and page number of every alarm in the chapter, organized by logical object type.

Table 2-8 Alarm Index by Alarm Type 

AIE: EQPT

AIE: MFGMEM (AEP, AIE)

BITS: AIS

BITS: LOF (BITS)

BITS: LOS (BITS)

BITS: SSM-DUS

BITS: SSM-FAIL

BITS: SSM-LNC

BITS: SSM-OFF

BITS: SSM-PRC

BITS: SSM-SETS

BITS: SSM-STU

BITS: SSM-TNC

BITS: SYNC-FREQ

BP: AS-CMD

BP: INVMACADR

BP: MEA (BP)

BP: MFGMEM (Backplane or Fan-Tray Assembly)

CC: LMP-HELLODOWN

CC: LMP-NDFAIL

CKT: CKTDOWN

DS3: AIS

DS3: AS-CMD

DS3: AS-MT

DS3: DS3-MISM

DS3: FE-AIS

DS3: FE-EQPT-NSA

DS3: FE-IDLE

DS3: FE-LOF

DS3: FE-LOS

DS3: INC-ISD

DS3: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

DS3: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

DS3: LPBKDS3FEAC

DS3: LPBKDS3FEAC-CMD

DS3: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

DS3: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

DS3: RAI

DS3: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

DS3: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

DWDM Client: AIS

DWDM Client: ALS

DWDM Client: AS-CMD

DWDM Client: AS-MT

DWDM Client: CARLOSS (DWDM Client)

DWDM Client: EOC

DWDM Client: FAILTOSW

DWDM Client: FORCED-REQ-SPAN

DWDM Client: GE-OOSYNC

DWDM Client: HI-LASERBIAS

DWDM Client: HI-RXPOWER

DWDM Client: HI-TXPOWER

DWDM Client: LOCKOUT-REQ

DWDM Client: LOF (DWDM Client)

DWDM Client: LO-RXPOWER

DWDM Client: LOS (DWDM Client)

DWDM Client: LO-TXPOWER

DWDM Client: LPBKFACILITY (DWDM Client)

DWDM Client: LPBKTERMINAL (DWDM)

DWDM Client: MANUAL-REQ-SPAN

DWDM Client: OUT-OF-SYNC

DWDM Client: PORT-CODE-MISM

DWDM Client: PORT-COMM-FAIL

DWDM Client: PORT-MISMATCH

DWDM Client: PORT-MISSING

DWDM Client: RFI

DWDM Client: SD (DWDM Client)

DWDM Client: SF (DWDM Client)

DWDM Client: SQUELCHED

DWDM Client: SSM-DUS

DWDM Client: SSM-FAIL

DWDM Client: SSM-LNC

DWDM Client: SSM-OFF

DWDM Client: SSM-PRC

DWDM Client: SSM-SETS

DWDM Client: SSM-STU

DWDM Client: SSM-TNC

DWDM Client: SYNC-FREQ

DWDM Client: TIM

DWDM Client: TIM-MON

DWDM Client: WKSWPR

DWDM Client: WTR

DWDM Trunk: AIS

DWDM Trunk: ALS

DWDM Trunk: AS-CMD

DWDM Trunk: AS-MT

DWDM Trunk: CARLOSS (DWDM Trunk)

DWDM Trunk: DSP-COMM-FAIL

DWDM Trunk: DSP-FAIL

DWDM Trunk: EOC

DWDM Trunk: FAILTOSW

DWDM Trunk: FEC-MISM

DWDM Trunk: FORCED-REQ-SPAN

DWDM Trunk: GCC-EOC

DWDM Trunk: GE-OOSYNC

DWDM Trunk: HI-LASERBIAS

DWDM Trunk: HI-RXPOWER

DWDM Trunk: HI-TXPOWER

DWDM Trunk: LOC

DWDM Trunk: LOCKOUT-REQ

DWDM Trunk: LOF (DWDM Trunk)

DWDM Trunk: LOM

DWDM Trunk: LO-RXPOWER

DWDM Trunk: LO-TXPOWER

DWDM Trunk: MANUAL-REQ-SPAN

DWDM Trunk: ODUK-AIS-PM

DWDM Trunk: ODUK-BDI-PM

DWDM Trunk: ODUK-LCK-PM

DWDM Trunk: ODUK-OCI-PM

DWDM Trunk: ODUK-SD-PM

DWDM Trunk: ODUK-SF-PM

DWDM Trunk: ODUK-TIM-PM

DWDM Trunk: OTUK-AIS

DWDM Trunk: OTUK-BDI

DWDM Trunk: OTUK-LOF

DWDM Trunk: OTUK-SD

DWDM Trunk: OTUK-SF

DWDM Trunk: OTUK-TIM

DWDM Trunk: OUT-OF-SYNC

DWDM Trunk: PTIM

DWDM Trunk: RFI

DWDM Trunk: SSM-DUS

DWDM Trunk: SSM-FAIL

DWDM Trunk: SSM-LNC

DWDM Trunk: SSM-OFF

DWDM Trunk: SSM-PRC

DWDM Trunk: SSM-SETS

DWDM Trunk: SSM-STU

DWDM Trunk: SSM-TNC

DWDM Trunk: SYNC-FREQ

DWDM Trunk: TIM

DWDM Trunk: TIM-MON

DWDM Trunk: UNC-WORD

DWDM Trunk: WKSWPR

DWDM Trunk: WTR

DWDM Trunk: WVL-MISMATCH

ECN: AS-CMD

ECN: AS-MT

ECN: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

ECN: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

ECN: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

ECN: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

ENV: EXT

EQPT: AS-CMD

EQPT: AUTORESET

EQPT: BKUPMEMP

EQPT: CARLOSS (EQPT)

EQPT: CLDRESTART

EQPT: COMIOXC

EQPT: COMM-FAIL

EQPT: CONTBUS-A-18

EQPT: CONTBUS-A-18

EQPT: CONTBUS-IO-B

EQPT: CONTBUS-B-18

EQPT: CTNEQPT-MISMATCH

EQPT: CTNEQPT-PBPROT

EQPT: CTNEQPT-PBWORK

EQPT: EQPT

EQPT: ERROR-CONFIG

EQPT: EXCCOL

EQPT: FAILTOSW

EQPT: FORCED-REQ

EQPT: HITEMP

EQPT: IMPROPRMVL

EQPT: INHSWPR

EQPT: INHSWWKG

EQPT: IOSCFGCOPY

EQPT: LOCKOUT-REQ

EQPT: MAN-REQ

EQPT: MANRESET

EQPT: MEA (EQPT)

EQPT: MEM-GONE

EQPT: MEM-LOW

EQPT: NO-CONFIG

EQPT: PEER-NORESPONSE

EQPT: PROTNA

EQPT: PWR-REDUN

EQPT: RUNCFG-SAVENEED

EQPT: SFTWDOWN

EQPT: SWMTXMOD

EQPT: WKSWPR

EQPT: WTR

ETHER: AS-CMD

ETHER: CARLOSS (E-Series Ethernet)

EXTSYNCH: FRCDSWTOPRI

EXTSYNCH: FRCDSWTOSEC

EXTSYNCH: FRCDSWTOTHIRD

EXTSYNCH: MANSWTOPRI

EXTSYNCH: MANSWTOSEC

EXTSYNCH: MANSWTOTHIRD

EXTSYNCH: SWTOPRI

EXTSYNCH: SWTOSEC

EXTSYNCH: SWTOTHIRD

EXTSYNCH: SYNCPRI

EXTSYNCH: SYNCSEC

EXTSYNCH: SYNCTHIRD

E1: AIS

E1: AS-CMD

E1: AS-MT

E1: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

E1: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

E1: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E1: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E1: RAI

E1: RCVR-MISS

E1: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

E1: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

E1: TRMT

E1: TRMT-MISS

E1: TX-AIS

E1: TX-RAI

E3: AIS

E3: AS-CMD

E3: AS-MT

E3: DS3-MISM

E3: E3-ISD

E3: FE-AIS

E3: FE-EQPT-NSA

E3: FE-E1-MULTLOS

E3: FE-E1-NSA

E3: FE-E1-SA

E3: FE-E1-SNGLLOS

E3: FE-E3-NSA

E3: FE-E3-SA

E3: FE-IDLE

E3: FE-LOF

E3: FE-LOS

E3: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

E3: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E3: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E3: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

E3: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

E4: AIS

E4: AMPLI-INIT

E4: AS-CMD

E4: AS-MT

E4: AWG-DEG

E4: AWG-OVERTEMP

E4: AWG-WARM-UP

E4: CASETEMP-DEG

E4: FIBERTEMP-DEG

E4: GAIN-HDEG

E4: GAIN-HFAIL

E4: GAIN-LDEG

E4: GAIN-LFAIL

E4: LASER-APR

E4: LASERBIAS-DEG

E4: LASERBIAS-FAIL

E4: LASERTEMP-DEG

E4: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

E4: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

E4: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E4: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

E4: OPWR-HDEG

E4: OPWR-HFAIL

E4: OPWR-LDEG

E4: OPWR-LFAIL

E4: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

E4: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

E4: SH-INS-LOSS-VAR-DEG-HIGH

E4: SH-INS-LOSS-VAR-DEG-LOW

E4: SHUTTER-OPEN

E4: VOA-HDEG

E4: VOA-HFAIL

E4: VOA-LDEG

E4: VOA-LFAIL

FAN: EQPT-MISS

FAN: FAN

FAN: FANDEGRADE

FAN: MEA (FAN)

FAN: MFGMEM (Backplane or Fan-Tray Assembly)

FCMR: AS-CMD

FCMR: AS-MT

FCMR: INC-GFP-OUTOFFRAME

FCMR: INC-GFP-SIGLOSS

FCMR: INC-GFP-SYNCLOSS

FCMR: INC-SIGLOSS

FCMR: INC-SYNCLOSS

FCMR: PORT-MISMATCH

FCMR: TPTFAIL (FC_MR-4)

FUDC: AIS

FUDC: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

HDGE [G1000]: AS-CMD

HDGE [G1000]: AS-MT

HDGE [G1000]: CARLOSS (G-Series Ethernet)

HDGE [G1000]: LPBKFACILITY (G-Series)

HDGE [G1000]: LPBKTERMINAL(G-Series Ethernet)

HDGE [G1000]: TPTFAIL (G-Series)

HDGE [G1000]: TUNDERRUN

HPMON: AU-AIS

HPMON: AU-LOP

HPMON: AUTOSW-AIS-SNCP

HPMON: AUTOSW-LOP-SNCP

HPMON: AUTOSW-SDBER-SNCP

HPMON: AUTOSW-SFBER-SNCP

HPMON: AUTOSW-UNEQ-SNCP (HPMon)

HPMON: FAILTOSW-HO

HPMON: FORCED-REQ

HPMON: HP-RFI

HPMON: HP-TIM

HPMON: HP-UNEQ

HPMON: LOCKOUT-REQ

HPMON: LPBKCRS

HPMON: MAN-REQ

HPMON: SDBER-EXCEED-HO

HPMON: SFBER-EXCEED-HO

HPMON: WKSWPR

HPMON: WTR

HPTERM: AU-AIS

HPTERM: AU-LOF

HPTERM: AU-LOP

HPTERM: HP-TIM

HPTERM: HP-UNEQ

HPTERM: LOM

HPTERM: OOU-TPT

HPTERM: SDBER-EXCEED-HO

HPTERM: SFBER-EXCEED-HO

HPTERM: SQM

LPMON: AUTOSW-AIS-SNCP

LPMON: AUTOSW-LOP-SNCP

LPMON: AUTOSW-SDBER-SNCP

LPMON: AUTOSW-SFBER-SNCP

LPMON: AUTOSW-UNEQ-SNCP (LPMon)

LPMON: FAILTOSW-LO

LPMON: FORCED-REQ

LPMON: LOCKOUT-REQ

LPMON: LOM

LPMON: LP-UNEQ

LPMON: MAN-REQ

LPMON: SQM

LPMON: TU-AIS

LPMON: TU-LOP

LPMON: WKSWPR

LPMON: WTR

LPTERM: LOM

LPTERM: LP-PLM

LPTERM: LP-RFI

LPTERM: LP-TIM

LPTERM: LP-UNEQ

LPTERM: OOU-TPT

LPTERM: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

LPTERM: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

LPTERM: TU-LOP

L2SC: AS-CMD

L2SC: CARLOSS (ML-Series Ethernet)

L2SC: TPTFAIL (ML-Series)

NBR: RSVP-HELLODOWN

NE: APC-DISABLED

NE: APC-FAIL

NE: AS-CMD

NE: AUD-LOG-LOSS

NE: AUD-LOG-LOW

NE: AWG-FAIL

NE: DATAFLT

NE: DBOSYNC

NE: DUP-IPADDR

NE: DUP-NODENAME

NE: ETH-LINKLOSS

NE: HITEMP

NE: INTRUSION-PSWD

NE: OPTNTWMIS

NE: SNTP-HOST

NE: SYSBOOT

NESYNCH: FRCDSWTOINT

NESYNCH: FRCDSWTOPRI

NESYNCH: FRCDSWTOSEC

NESYNCH: FRCDSWTOTHIRD

NESYNCH: FRNGSYNC

NESYNCH: FSTSYNC

NESYNCH: HLDOVRSYNC

NESYNCH: MANSWTOINT

NESYNCH: MANSWTOPRI

NESYNCH: MANSWTOSEC

NESYNCH: MANSWTOTHIRD

NESYNCH: SSM-LNC

NESYNCH: SSM-PRC

NESYNCH: SSM-SETS

NESYNCH: SSM-STU

NESYNCH: SSM-TNC

NESYNCH: SWTOPRI

NESYNCH: SWTOSEC

NESYNCH: SWTOTHIRD

NESYNCH: SYNC-FREQ

NESYNCH: SYNCPRI

NESYNCH: SYNCSEC

NESYNCH: SYNCTHIRD

OSCRING: RING-ID-MIS

PWR: AS-CMD

PWR: BATFAIL

PWR: EHIBATVG

PWR: ELWBATVG

PWR: HIBATVG

PWR: LWBATVG

STM-N: ALS

STM-N: APSB

STM-N: APSCDFLTK

STM-N: APSC-IMP

STM-N: APSCNMIS

STM-N: APSCINCON

STM-N: APSCM

STM-N: AS-CMD

STM-N: APSCNMIS

STM-N: AS-MT

STM-N: AUTOLSROFF

STM-N: EOC

STM-N: E-W-MISMATCH

STM-N: EXERCISE-RING-FAIL

STM-N: EXERCISE-SPAN-FAIL

STM-N: EXTRA-TRAF-PREEMPT

STM-N: FAILTOSW

STM-N: FAILTOSWR

STM-N: FAILTOSWS

STM-N: FE-FRCDWKSWPR-RING

STM-N: FE-FRCDWKSWPR-SPAN

STM-N: FE-LOCKOUTOFPR-SPAN

STM-N: FE-MANWKSWPR-RING

STM-N: FE-MANWKSWPR-SPAN

STM-N: FEPRLF

STM-N: FORCED-REQ-RING

STM-N: FORCED-REQ-SPAN

STM-N: FULLPASSTHR-BI

STM-N: HI-LASERBIAS

STM-N: HI-RXPOWER

STM-N: HI-TXPOWER

STM-N: KB-PASSTHR

STM-N: KBYTE-APS-CHANNEL-FAILURE

STM-N: LASEREOL

STM-N: LKOUTPR-S

STM-N: LOCKOUT-REQ

STM-N: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

STM-N: LO-RXPOWER

STM-N: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

STM-N: LO-TXPOWER

STM-N: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

STM-N: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

STM-N: MANUAL-REQ-RING

STM-N: MANUAL-REQ-SPAN

STM-N: MS-AIS

STM-N: MS-EOC

STM-N: MS-RFI

STM-N: MSSP-OOSYNC

STM-N: PRC-DUPID

STM-N: RING-ID-MIS

STM-N: RING-MISMATCH

STM-N: RING-SW-EAST

STM-N: RING-SW-WEST

STM-N: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

STM-N: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)

STM-N: SPAN-SW-EAST

STM-N: SPAN-SW-WEST

STM-N: SQUELCH

STM-N: SSM-DUS

STM-N: SSM-FAIL

STM-N: SSM-LNC

STM-N: SSM-OFF

STM-N: SSM-PRC

STM-N: SSM-SETS

STM-N: SSM-STU

STM-N: SSM-TNC

STM-N: SYNC-FREQ

STM-N: TIM

STM-N: WKSWPR

STM-N: WTR

STM1E: AS-CMD

STM1E: AS-MT

STM1E: LOF (DS-3, E-1, E-4, STM-N, STM1-E)

STM1E: LOS (DS-3, E-1, E-3, STM-N, STM-1E)

STM1E: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

STM1E: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)

STM1E: MS-AIS

STM1E: MS-RFI

STM1E: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)

STM1E: TIM

VCatGROUP: LOA

VCatGROUP: VCG-DEG

VCatGROUP: VCG-DOWN


2.5  Trouble Notifications

The ONS 15454 SDH uses standard ITU-T x.733 categories to characterize levels of trouble. The ONS 15454 SDH reports alarmed trouble notifications and Not-Alarmed (NA) notifications, if selected, in the CTC Alarms window. Alarms typically signify a problem that the user needs to fix, such as the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, while Not-Alarmed (NA) notifications do not necessarily need immediate troubleshooting.

The ITU further divides alarms into Service-Affecting (SA) and NSA status. A Service-Affecting (SA) failure affects a provided service or the network's ability to provide service. For example, the "TRMT-MISS" alarm on page 2-206 is characterized by default as an SA failure. TRMT-MISS occurs when a cable connector is removed from an active E-1 card port. The default severity assumes that service has been interrupted or moved. If the E-1 card is in a protection group and the traffic is on the protect card rather than the working card, or if the port with the TRMT-MISS alarm has no circuits provisioned, TRMT-MISS would be raised as NSA because traffic was not interrupted or moved.

2.5.1  Conditions

The term "Condition" refers to any problem detected on an ONS 15454 SDH shelf whether or not the problem is reported (that is, whether or not it generates a trouble notification). Reported conditions include alarms, Not-Alarmed conditions, and Not-Reported (NR) conditions. A snapshot of all current raised conditions on a node, whether they are reported or not, can be retrieved using the CTC Conditions window. You can see the actual reporting messages for alarms and NAs in the CTC History tab. ONS 15454 SDH condition reporting is not ITU-compliant.

2.5.2  Severities

The ONS 15454 SDH uses the following ITU severities: Critical (CR), Major (MJ), and Minor (MN). Non-Service Affecting (NSA) alarms always have a Minor (MN) severity. Service-Affecting (SA) alarms could be Critical (CR), Major (MJ), or Minor (MN). Critical alarms generally indicate severe, service-affecting trouble that needs immediate correction. A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network.

An example of a Non-Service Affecting (NSA) alarm is the "FSTSYNC" condition on page 2-104 (Fast Start Synchronization Mode), which indicates the ONS 15454 SDH is choosing a new timing reference because the previously used reference has failed. The user needs to troubleshoot the loss of the prior timing source, but the loss is not immediately disruptive to service.

ITU standard severities are the default settings for the ONS 15454 SDH. A user can customize ONS 15454 SDH alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the Cisco ONS 15454 SDH Procedure Guide.

This chapter lists the default profile alarm severity for the Service-Affecting (SA) case of each alarm when it is applicable. Any alarm with a profile value of Critical (CR) or Major (MJ) will—if reported as Non-Service Affecting (NSA) because no traffic is lost—be reported with a Minor (MN) severity instead.

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

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

Warning Class 1 laser product.

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

2.7  Alarm Procedures

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

Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner is not indented. If it is, click it to turn it off. When you're done checking for alarms, click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, see 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, see the Cisco ONS 15454 SDH Procedure Guide.

2.7.1  AIS

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

•Logical Objects: BITS, DS-3, DWDM Client, DWDM Trunk, E-1, E-3, E-4, and FUDC

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

Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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 DS-3 facility and terminal loopbacks do not transmit DS-3 AIS in the direction away from the loopback. Instead of DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.

Clear the AIS Condition

Step 1 Determine whether the upstream nodes and equipment have alarms, especially the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, or out-of-service (OOS) 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 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 TAC 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 future development.

2.7.3  ALS

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

•Logical Objects: DWDM Client, DWDM Trunk, STM-N

The Automatic Laser Shutdown condition occurs when an amplifier (OPT-BST or OPT-PRE) is switched on. The turn-on process lasts approximately nine seconds, and the condition clears after approximately 10 seconds.

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

2.7.4  AMPLI-INIT

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

•Logical Object: E-4

The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition is typically raised with the "APC-DISABLED" alarm on page 2-26.

Clear the AMPLI-INIT Condition

Step 1 Complete the "Delete a Circuit" procedure on the most recently created circuit.

Step 2 Recreate this circuit using the procedures in the Cisco ONS 15454 SDH Procedure Guide.

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 TAC numbers for your country.

2.7.5  APC-DISABLED

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The Automatic Power Control (APC) Disabled alarm occurs when the information related to the number of channels is not reliable. The alarm can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-74, the "IMPROPRMVL" alarm on page 2-116, or the "MEA (EQPT)" alarm on page 2-152. If the alarm occurs with the creation of the first circuit, delete and recreate it.

Clear the APC-DISABLED Alarm

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

•Clear the EQPT Alarm

•Clear the IMPROPRMVL Alarm

•Clear the MEA (FAN) Alarm

Step 2 If the alarm does not clear, complete the "Delete a Circuit" procedure and then recreate it.

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 TAC numbers for your country.

2.7.6  APC-FAIL

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

The APC Failure alarm occurs when APC has not been able to create a setpoint on a node because it has consumed all allocated power margins. These power margins (from 0 dB to 3 dB) are allocated when the network is installed. Margins can be consumed due to fiber aging or the insertion of unexpected extra loss in the span after a fiber cut.

Clear the APC-FAIL Alarm

Step 1 Isolate the cause of increased margin use:

•If it is due to fiber aging, replace the indicated fiber. (You can test the integrity of the fiber using optical testing equipment.)

•If it is due to a fiber cut, resolve this issue to resolve this alarm.

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

2.7.7  APSB

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: STM-N

The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure or an invalid code in the incoming APS signal. Some older, non-Cisco SDH nodes send invalid APS codes if configured in a 1+1 protection scheme with newer SDH nodes, such as the ONS 15454 SDH. These invalid codes cause an APSB alarm on an ONS 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 may 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 may need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Card" procedure.

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

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

Step 3 If the alarm does not clear, log into 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 TAC numbers for your country.

2.7.8  APSCDFLTK

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: STM-N

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

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

Clear the APSCDFLTK Alarm

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

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

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

Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" section.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 SDH Procedure Guide provides information 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 protection fiber.

Step 6 If the alarm does not clear, complete the "Verify Node Visibility for Other Nodes" procedure to verify that each node is visible to the other nodes while in network view.

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

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 TAC numbers for your country.

2.7.9  APSC-IMP

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: STM-N

An Improper APS Code alarm indicates bad or invalid K bytes. APSC-IMP occurs on STM-N cards in an MS-SPRing configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.

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 This alarm can occur when the exercise command or a Lock Out is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.

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.

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

Step 2 If the K byte is valid, complete the "Identify a 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 number that does not match the other nodes, complete the "Change a Ring Name Number" procedure to make the ring names identical.

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

2.7.10  APSCINCON

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: STM-N

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

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

Step 1 Look for other alarms, especially a "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, an "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131, or the "AIS" alarm on page 2-25. If they are present, complete the troubleshooting procedures for the alarm(s). Clearing the other alarm 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 TAC numbers for your country.

2.7.11  APSCM

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

•Logical Object: STM-N

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

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

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

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.

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.

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 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.12  APSCNMIS

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

•Logical Object: STM-N

The Node ID Mismatch alarm occurs when the source node ID contained in the K2 byte of the incoming APS channel 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 a Ring Name or Node ID Number" procedure to verify that each node has a unique node ID number.

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

Step 3 Click Close in the Ring Map dialog box.

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

Note If the node names shown on 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 displays the node ID of the login node.

Note Applying and removing a Lock Out on a span causes the ONS 15454 SDH 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 "Lock Out an MS-SPRing Span" procedure to lock out the span.

Step 6 Complete the "Clear a Ring or Span External Switching Command" procedure to clear the Lock Out.

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

2.7.13  APSIMP

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

•Logical Object: STMN

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

The condition is superseded by an APS or APSCM. It is not superseded by AIS or RDI line alarms. It clears when the port receives a valid code for 10 ms.

Clear the APSIMP Condition

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

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

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

Step 4 If the condition does not clear, log into the 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 TAC numbers for your country.

2.7.14  AS-CMD

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

•Logical Objects: BP, DS-3, DWDM Client, DWDM Trunk, EQPT, ETHER, E-1, E-3, E-4, FCMR, HDGE, L2SC, NE, PWR, STM-N, STM-1E

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

Clear the AS-CMD Condition

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Step 6 Locate the row for the reported card slot.

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

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

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

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

c. Click Apply.

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

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

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

c. Click Apply.

Step 10 If the condition does not clear, log into the 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 TAC numbers for your country.

2.7.15  AS-MT

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

•Logical Objects: DS-3, DWDM Client, DWDM Trunk, E-1, E-3, E-4, FCMR, HDGE, STM-N, STM-1E

The Alarms Suppressed for Maintenance Command condition applies to STM-N and electrical (traffic) cards and occurs when a port is placed in the out-of-service maintenance (OOS-MT) state for loopback testing operations.

Clear the AS-MT Condition

Step 1 Complete the "Clear a Loopback" 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 TAC numbers for your country.

2.7.16  AU-AIS

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

•Logical Objects: HPMon, HPTerm

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

Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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 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 TAC numbers for your country.

2.7.17  AUD-LOG-LOSS

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

•Logical Object: NE

The Audit Trail Log Loss condition occurs when the log is 100 percent full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries. You will have to 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 will continue with the next number in the sequence, rather than starting over.

Step 7 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 TAC numbers for your country.

2.7.18  AUD-LOG-LOW

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

•Logical Object: NE

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

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

2.7.19  AU-LOF

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

•Logical Object: HPTerm

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

Clear the AU-LOF Alarm

Step 1 Complete the "Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm" procedure.

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

2.7.20  AU-LOP

•Critical (CR), Service-Affecting (SA)

•Logical Objects: HPMon, HPTerm

An AU Loss of Pointer (LOP) alarm indicates that the SDH high order path overhead section of the administration unit has detected a loss of path. AU-LOP occurs when there is a mismatch between the expected and provisioned circuit size.

Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.

Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.

Clear the AU-LOP Alarm

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

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

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

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

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

Step 5 Recreate the circuit for the correct size. For instructions, see the Cisco ONS 15454 SDH Procedure Guide.

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 TAC numbers for your country in order to report a service-affecting problem.

2.7.21  AUTOLSROFF

•Critical (CR), Service-Affecting (SA)

•Logical Object: STM-N

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

Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

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 Determine whether there is a HITEMP alarm present. If the temperature of the shelf exceeds 90 degrees C (194 degrees F), 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 90 degrees C (194 degrees F), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Card" procedure for the STM-64 card.

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

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

Step 4 If card replacement does not clear the 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.22  AUTORESET

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: EQPT

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

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.

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 one time per month with no apparent cause, complete the "Physically Replace a Card" procedure.

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

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

Step 3 If the 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 TAC numbers for your country.

2.7.23  AUTOSW-AIS-SNCP

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

•Logical Objects: HPMon, LPMon

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

Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input when it sees the signal 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 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 TAC numbers for your country.

2.7.24  AUTOSW-LOP-SNCP

•Minor (MN), Non-Service Affecting (NSA) for LPMon

•Not Alarmed (NA), Non-Service Affecting (NSA) for HPMon

•Logical Objects: HPMon, LPMon

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-36. The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears.

Clear the AUTOSW-LOP-SNCP Alarm

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

Step 2 If the alarm does not clear, log into the 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.25  AUTOSW-PDI-SNCP

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

•Logical Object: VCSMON-HP

The Automatic SNCP Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic SNCP protection switching occurred because of a PDI. The SNCP is configured for revertive switching and reverts to the working path after the fault clears.

Clear the AUTOSW-PDI-SNCP Condition

Step 1 Verify that all circuits terminating in the reporting card are DISCOVERED:

a. Click the Circuits tab.

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

c. If the Status column lists the circuit as PARTIAL, wait 10 minutes for the ONS 15454 to initialize fully. If the PARTIAL status does not change after full initialization, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a service-affecting problem (1-800-553-2447).

Step 2 After determining that the circuit is DISCOVERED, ensure that the signal source to the card reporting the alarm is working.

Step 3 If traffic is affected, complete the "Delete a Circuit" procedure.

Caution Deleting a circuit can affect existing traffic.

Step 4 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.

Step 5 If circuit deletion and recreation does not clear the condition, verify that there is no problem stemming from the far-end STM-N card providing STS payload to the reporting card.

Step 6 If the condition does not clear, confirm the cross-connect between the STM-N card and the reporting card.

Step 7 If the condition does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 Procedure Guide.

Step 8 If the condition does not clear, complete the "Physically Replace a Card" procedure for the optical/electrical cards.

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 "Verify or Create Node DCC Terminations" section for commonly used procedures.

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

Step 9 If the 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.26  AUTOSW-SDBER-SNCP

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

•Logical Objects: HPMon, LPMon

The Automatic SNCP Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade [see the "SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)" condition on page 2-182] caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SD is resolved.

Clear the AUTOSW-SDBER-SNCP Condition

Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) 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 TAC numbers for your country.

2.7.27  AUTOSW-SFBER-SNCP

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

•Logical Objects: HPMon, LPMon

The Automatic SNCP Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail (see the "SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)" condition on page 2-185) caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SF is resolved.

Clear the AUTOSW-SFBER-SNCP Condition

Step 1 Complete the "Clear the SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N) 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 TAC numbers for your country.

2.7.28  AUTOSW-UNEQ-SNCP (HPMon)

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

•Logical Object: HPMon

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

Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.

Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.

Clear the AUTOSW-UNEQ-SNCP (HPMon) Condition

Step 1 Complete the "Clear the HP-UNEQ Alarm" 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 TAC numbers for your country.

2.7.29  AUTOSW-UNEQ-SNCP (LPMon)

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: LPMon

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

Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.

Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.

Clear the AUTOSW-UNEQ-SNCP (LPMon) Alarm

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 for incomplete circuits again. Recreate any needed circuits.

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

a. In node view, click the Circuits tab.

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

c. If the Status column lists the port as incomplete, and the incomplete does not change after a full initialization, log into the 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 TAC numbers for your country.

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

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

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

Step 11 If the alarm does not clear, clean the far-end optical fiber cable ends according to site practice. If no site practice exists, complete the procedure 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 (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).

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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.

Step 12 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 TAC numbers for your country.

2.7.30  AWG-DEG

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: E-4

The AWG Temperature Degrade alarm indicates that an internal failure on the multiplexer or demultiplexer heater control circuit causes the AWG temperature to rise above or fall below the degrade threshold.

Clear the AWG-DEG Alarm

Step 1 This alarm does not immediately affect traffic. But eventually, you will need to complete the "Physically Replace a Card" procedure on the reporting card to clear the alarm.

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

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

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

2.7.31  AWG-FAIL

•Critical (CR), Service-Affecting (SA)

•Logical Object: NE

The AWG Temperature Fail alarm indicates that a heater control circuit on the multiplexer or demultiplexer card has failed.

Clear the AWG-FAIL Alarm

Step 1 Complete the "Physically Replace a Card" procedure.

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

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

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

2.7.32  AWG-OVERTEMP

•Critical (CR), Service-Affecting (SA)

•Logical Object: E-4

The AWG Over Temperature alarm occurs in conjunction with the "AWG-FAIL" alarm on page 2-44 when the AWG temperature exceeds 100 degrees C (212 degrees F). The multiplexer or demultiplexer goes into protection mode, disabling the AWG chip heater.

Clear the AWG-OVERTEMP Alarm

Step 1 Complete the "Physically Replace a Card" procedure.

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

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

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

2.7.33  AWG-WARM-UP

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

•Logical Object: E-4

The AWG Warm-up condition occurs during AWG startup. The length of time needed for the condition to clear varies, depending upon environmental conditions. It can last up to approximately 10 minutes.

Note AWG-WARM-UP is an informational condition, and does not require troubleshooting unless it does not clear.

2.7.34  BATFAIL

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

•Logical Object: PWR

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

Clear the BATFAIL Alarm

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

Step 2 Remove the power cable from the faulty supply.

If the alarm does not clear, log into the 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 TAC numbers for your country to report a service-affecting problem.

2.7.35  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-74. 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 Active TCC2 Card and Activate 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) a Card" procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.36  CARLOSS (DWDM Client)

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

•Logical Object: DWDM Client

A Carrier Loss alarm on the transponder (TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G) or muxponder (MXP_2.5G_10G) card occurs when ITU-T G.709 monitoring is turned off at the client port. It is similar to the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.

Clear the CARLOSS (DWDM Client) Alarm

Step 1 From node view, double-click the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card to display card view.

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

Step 3 Check the check box under the G.709 OTN column.

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 TAC numbers for your country in order to report a service-affecting problem.

2.7.37  CARLOSS (DWDM Trunk)

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

•Logical Object: DWDM Trunk

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

Clear the CARLOSS (DWDM Trunk) Alarm

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

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

2.7.38  CARLOSS (EQPT)

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

•Logical Object: EQPT

The Carrier Loss Equipment alarm occurs when the ONS 15454 SDH and the workstation hosting CTC do not have a TCP/IP connection. CARLOSS is a problem involving the LAN or data circuit used by the RJ-45 connector on the TCC2 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 or MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 monitoring is turned off.

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

Clear the CARLOSS (EQPT) Alarm

Step 1 If the reporting card is a TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card, verify the type of payload configured:

a. Double-click the reporting TXP card.

b. Click the Provisioning > Card tabs.

c. From the Payload Data Type list, choose the correct payload for the card and click Apply.

Step 2 Verify connectivity by pinging the ONS 15454 SDH that is reporting the alarm:

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

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

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

ping ONS-15454-SDH-IP-address

For example, ping 192.1.0.2.

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

Step 3 Verify that the straight-through (Category 5) LAN cable is properly connected and attached to the correct port.

Step 4 If the straight-through (Category 5) LAN 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.

Step 5 If you are unable to establish connectivity, replace the straight-through cable with a new known-good cable.

Step 6 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 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 TAC numbers for your country to report a service-affecting problem.

2.7.39  CARLOSS (E-Series Ethernet)

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

•Logical Object: ETHER

A Carrier Loss on the LAN alarm is the data equivalent of the SDH "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135. The Ethernet (traffic) card has lost its link and is not receiving a valid signal. The most common causes of this alarm are a disconnected straight-through (Category 5) LAN cable or an improperly installed Ethernet card. Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

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

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.

Clear the CARLOSS (E-Series Ethernet) Alarm

Step 1 Verify that the straight-through (Category 5) LAN cable is properly connected and attached to the correct port.

Step 2 If the straight-through (Category 5) LAN 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.

Step 3 If there is no misconnection to an STM-N card, 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 straight-through (Category 5) LAN cable connecting the transmitting device to the Ethernet port.

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

Step 7 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the Ethernet (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. Refer to the Cisco ONS 15454 SDH Procedure Guide for information.

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

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

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 setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:

a. Right-click anywhere on 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. Examine the layout of your network and determine which ONS 15454 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

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

•Double-click the Ethernet (traffic) 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 will connect the Ethernet card to an STM-N card on the same node.

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

f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.

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

2.7.40  CARLOSS (G-Series Ethernet)

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

•Logical Object: HDGE

A Carrier Loss on the LAN alarm is the data equivalent of the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135. The Ethernet (traffic) card has lost its link and is not receiving a valid signal.

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

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

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

Refer to the Cisco ONS 15454 SDH Reference Guide for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. See also the "TRMT" alarm on page 2-205 for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.

Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

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 at the lower-right outside edge of the shelf assembly.

Clear the CARLOSS (G-Series Ethernet) Alarm

Step 1 Verify that the fiber cable is properly connected and attached to the correct port.

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.

Step 5 If the alarm does not clear, use an Ethernet test set to determine that 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.

Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the G1000-4 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 G1000-4 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. Autonegotiation restarts.

Step 9 If the TPTFAIL is also reported, complete the "Clear the TPTFAIL (G-Series) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.

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

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

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

b. Click the Conditions tab and then click Retrieve Conditions.

c. If LPBKTERMINAL is listed for the port, a loopback is provisioned. Go to Step 11. If IS is listed, go to Step 12.

Step 11 If a loopback was provisioned, clear the loopback by following the "Clear a Loopback" procedure.

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

If the port is not set in LPBKTERMINAL, 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 A Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454 SDHs, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 SDH TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.

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

b. Click Select Affected Circuits from the shortcut menu.

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

d. Examine the layout of your network and determine which ONS 15454 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

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

•Double-click the Ethernet (traffic) 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 will connect the Ethernet card to an STM-N card on the same node.

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

f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.

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

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

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

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

Step 15 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.41  CARLOSS (ML-Series Ethernet)

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

•Logical Object: L2SC

A CARLOSS alarm on the ML-Series Ethernet (traffic) card is the data equivalent of the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131. The Ethernet port has lost its link and is not receiving a valid signal.

CARLOSS for an ML-Series card occurs when the Ethernet port has been configured from the IOS command line interface (CLI) as a no-shutdown port and one of the following items 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

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

Clear the CARLOSS (ML-Series Ethernet) 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.

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 IOS CLI. Autonegotiation restarts.

Step 6 If the alarm does not clear, perform a facility loopback on the ML-Series card using the "Create a Facility (Line) Loopback Circuit on a Destination DS-N or E-N Port" procedure on page 1-21.

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

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

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

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

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

2.7.42  CASETEMP-DEG

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: E-4

The Case Temperature Degrade alarm occurs when a card detects a case temperature value outside the desired range (-5 to 65 degrees C or 23 to 149 degrees F).

Clear the CASETEMP-DEG Alarm

Step 1 If a FAN alarm is also reported, complete the "Clear the FAN Alarm" procedure.

Step 2 If no FAN alarm is reported, complete the "3.2.1  Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.

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 TAC numbers for your country.

2.7.43  CKTDOWN

•Critical (CR), Service-Affecting (SA)

•Logical Object: CKT

The Unified Control Plane (UCP) Circuit Down alarm applies to logical circuits created within the UCP between devices. CKTDOWN occurs when the there is signaling failure across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 SDH edge device.

Clear the CKTDOWN Alarm

Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:

a. In node view, click the Provisioning > UCP > Neighbor tabs.

b. View the entries to find out whether the node you are trying to contact is listed.

c. The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that physical and logical accessibility.

d. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.

e. At the command prompt (C:\>), type: 

ping {node-DNS-name | node-IP-address}

If you typed the domain name services (DNS) name and the ping was successful, you will see: 

pinging node-dns-name.domain-name.com. node-IP-address with 32 bytes of data:


Reply from IP-address: bytes=32 time=10ms TTL=60

Reply from IP-address: bytes=32 time=10ms TTL=60

Reply from IP-address: bytes=32 time=10ms TTL=60

Reply from IP-address: bytes=32 time=10ms TTL=60


Ping statistics for IP-address:

	Packets sent = 4 Received = 4 Lost = 0 (0% lost),

Approximate round trip time in milli-seconds:

	Minimum = minimum-ms, Maximum = maximum-ms, Average = average-ms

If you typed the IP address and the ping command is successful, the result looks similar but does not include the DNS name in the first line.


f. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.

g. If the ping was unsuccessful, you the following reply is repeated for each try: 

Request timed out.

A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.

Step 2 If the channel to neighbor has not been provisioned, or if you had to delete the channel, create one:

a. Click the Provisioning > UCP > Neighbor tabs.

b. Click Create.

c. In the Neighbor Discovery window, enter the node's DNS node name in the Neighbor Name field. Leave the Enable Discovery check box checked (default setting) if you want the neighbor to be discovered through the network.

d. Click OK.

The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If discovery is not successful, the column lists 0.0.0.0.

Step 3 If neighbor discovery is enabled, ensure that the neighbor node ID and remote Internet protocol (IP) control channel (IPCC) have been discovered correctly.

Step 4 Click the Provisioning > UCP > IPCC tabs and view the IPCC listing. If the IPCC has been created correctly, the Remote IP column contains the neighbor's IP address.

Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.

a. Click the entry to select the neighbor IP address and click Delete.

b. If you get an error that does not allow you to delete the IPCC, you need to delete the neighbor and recreate it. Click the Neighbor tab.

c. Click to select the neighbor and click Delete.

d. Go back to Step 2 to recreate the neighbor.

Step 6 If remote IPCC has not been discovered, or if IPCC had to be deleted, create the connection:

a. In the Provisioning > UCP > IPCC tabs, click Create.

b. In the Unified Control Plane Provisioning window, click Next.

c. If no IPCCs are listed, click Create.

d. In the Create New IPCC window, click one of the Regenerator Section DCC (SDCC) terminations in the SDCC list.

Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.

e. Click OK. The IPCC is listed as CCID 1 in the Unified Control Plane Provisioning window.

f. Click the neighbor to select it, and click Next.

g. Choose a UCP interface (for example Slot 5 for an STM-16 card, port 1) from the pull-down menu. The field default is the node where you are logged in.

h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.

i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab contains the neighbor's IP address.

Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:

a. Click the Interface tab. View the slot and port listed in the Interface column (for example, Slot 5 for an STM-16 card, port 1).

b. Compare the listed interface listed with the IPCC tab SDCC column entry.

Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.

Step 9 Click Next.

Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.

The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.

Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.

Step 12 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 TAC numbers for your country to report a service-affecting problem.

2.7.44  CLDRESTART

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

•Logical Object: EQPT

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

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 lower-right outside edge of the shelf assembly.

Clear the CLDRESTART Condition

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

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

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

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

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

2.7.45  COMIOXC

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

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

Clear the COMIOXC Alarm

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

Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

Step 3 If the CTC reset does not clear the alarm, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure.

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

Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting cross-connect 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. Refer to the Cisco ONS 15454 SDH Procedure Guide for information.

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

Step 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.46  COMM-FAIL

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: EQPT

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

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

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

Step 3 If the 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 TAC numbers for your country.

2.7.47  CONTBUS-A-18

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 7 (termed TCC-A) loses communication with the coprocessor on the same 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.

Clear the CONTBUS-A-18 Alarm

Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 11 active.

Step 2 Wait approximately 10 minutes for theTCC2 in Slot 7 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.

Step 3 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 7 active.

Step 4 If the reset 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 TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.48  CONTBUS-B-18

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 11 (termed TCC-B) loses communication with the coprocessor on the same 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.

Clear the CONTBUS-B-18 Alarm on the TCC2 Card

Step 1 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 7 active.

Step 2 Wait approximately 10 minutes for the TCC2 in Slot 11 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.

Step 3 Position the cursor over the TCC2 card in Slot 7 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 11 active.

Step 4 If the reset 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 TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.49  CONTBUS-IO-A

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Controller A To Shelf Slot Communication Failure alarm occurs when the TCC2 card in Slot 7 has lost communication with a traffic (electrical, optical, or Ethernet) card.

The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 SDH switches to the standby TCC2 card. In the case of a switch, the alarm clears after the cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 to the reporting card. The physical path of communication includes the TCC2 card, the traffic card, and the backplane.

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.

Clear the CONTBUS-IO-A Alarm

Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. In node view, click the Inventory tab to reveal the provisioned type.

If the actual card type and the provisioned card type do not match, complete the "Clear the MEA (EQPT) Alarm" procedure.

Step 2 If only one card slot (other than TCC2 card) is reporting the alarm, complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

Step 4 If the CTC reset does not clear the alarm, complete the "Physically Replace a 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. Refer to the Cisco ONS 15454 SDH Procedure Guide for information.

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

Step 5 If all traffic (electrical, optical, or Ethernet) cards report this alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC2 card does not reset itself.

Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.

Step 6 If 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 TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.50  CONTBUS-IO-B

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: EQPT

A Controller B To Shelf Slot Communication Failure alarm occurs when the TCC2 card in Slot 11 loses communication with a traffic (electrical, optical, or Ethernet) card.

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

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.

Clear the CONTBUS-IO-B Alarm

Step 1 Ensure that the reporting card is physically present in the shelf and that the card matches the type of card identified in that slot on CTC.

Step 2 If the reporting slot is the only one reporting the alarm, perform a CTC reset of the traffic (electrical, optical, or Ethernet) card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

Step 5 If all cards—with the exception of the active TCC2—report the CONTBUS-B alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.

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

Step 6 If the reset 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 the Cisco Technical Support Website at http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.51  CTNEQPT-MISMATCH

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

•Logical Object: EQPT

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

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

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

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

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

Clear the CTNEQPT-MISMATCH Condition

Step 1 Verify what card is preprovisioned in the slot:

a. In node view, click the Inventory tab.

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

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

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

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 TAC numbers for your country.

2.7.52  CTNEQPT-PBPROT

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the 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, the reporting traffic card, the TCC2 card, or the backplane.

Note If all traffic cards show the CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the standby TCC2 card. Do not physically reseat an active TCC2 card. Reseating the TCC2 disrupts traffic.

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 This alarm automatically raises and clears when the Slot 10 cross-connect card is reseated.

Note It can take up to 30 minutes for software to be updated on a standby TCC2 card.

Clear the CTNEQPT-PBPROT Alarm

Step 1 Perform a CTC reset on the standby cross-connect card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

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

Step 4 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 5 If the reporting traffic (electrical, optical, or Ethernet) card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.

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

•While the card resets, the FAIL LED blinks on the physical card and then all LEDs turn off.

•While the card resets, a white LED with the letters "LDG" appears on the reset card in CTC.

Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

Step 9 Complete the "Clear a Protection Group External Switching Command" procedure.

Step 10 If the alarm does not clear, complete the "Physically Replace a 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. Refer to the Cisco ONS 15454 SDH Procedure Guide for information.

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

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

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

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

Step 13 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.53  CTNEQPT-PBWORK

•Critical (CR), Service-Affecting (SA)

•Logical Object: EQPT

The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the Slot 8 cross-connect card 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, the reporting traffic card, or the backplane.

Note If all traffic cards show the CTNEEQPT-PBWORK alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure for the active TCC2 card and then complete the "Remove and Reinsert (Reseat) a Card" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card. Do not physically reseat an active TCC2 card; reseating disrupts traffic.

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 This alarm automatically raises and clears when the Slot 8 cross-connect card is reseated.

Clear the CTNEQPT-PBWORK Alarm

Step 1 Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to move traffic from the active card to the standby cross-connect card.

Step 2 Complete the "Reset a Traffic Card in CTC" procedure for the reporting traffic (electrical, optical, or Ethernet) card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

Note The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is amber.

Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.

Step 6 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.

Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.

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

Step 9 If you switched traffic, complete the "Clear a Protection Group External Switching Command" procedure.

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

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

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

Step 12 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 TAC numbers for your country in order to report a service-affecting problem.

2.7.54  DATAFLT

•Minor (MN), Non-Service Affecting (NSA)

•Logical Object: NE

The Software Data Integrity Fault alarm occurs when the TCC2 exceeds its Flash memory capacity.

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

Clear the DATAFLT Alarm

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

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

2.7.55  DBOSYNC

•Major (MJ), Non-Service Affecting (NSA)

•Logical Object: NE

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

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

Clear the DBOSYNC Alarm

Step 1 Save a backup copy of the active TCC2 database. Complete the "Back Up the Database" procedure in the Cisco ONS 15454 SDH Procedure Guide.

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

a. In node view, click the Pr