Cisco ONS 15454 SDH Troubleshooting Guide, Release 4.0
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 1.79MB) The complete bookPDF (PDF - 3.66MB) | Feedback

Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

2.1 Alarm Index by Default Severity

2.1.1 Critical Alarms (CR)

2.1.2 Major Alarms (MJ)

2.1.3 Minor Alarms (MN)

2.1.4 Conditions (NA or NR)

2.2 Alarms and Conditions Indexed By Alphabetical Entry

2.3 Alarm Index by Alarm Type

2.3.1 Alarm Type/Object Definition

2.4 Trouble Notifications

2.4.1 Conditions

2.4.2 Severities

2.5 Safety Summary

2.6 Alarm Procedures

2.6.1 AIS

Clear the AIS Condition

2.6.2 APSB

Clear the APSB Alarm

2.6.3 APSCDFLTK

Clear the APSCDFLTK Alarm

2.6.4 APSC-IMP

Clear the APSC-IMP Alarm

2.6.5 APSCINCON

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

2.6.6 APSCM

Clear the APSCM Alarm

2.6.7 APSCNMIS

Clear the APSCNMIS Alarm

2.6.8 AS-CMD

Clear the AS-CMD Condition

2.6.9 AS-MT

Clear the AS-MT Condition

2.6.10 AU-AIS

Clear the AU-AIS Condition

2.6.11 AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.6.12 AUD-LOG-LOW

2.6.13 AU-LOF

Clear the AU-LOF Alarm

2.6.14 AU-LOP

Clear the AU-LOP Alarm

2.6.15 AUTOLSROFF

Clear the AUTOLSROFF Alarm

2.6.16 AUTORESET

Clear the AUTORESET Alarm

2.6.17 AUTOSW-AIS-SNCP

Clear the AUTOSW-AIS-SNCP Condition

2.6.18 AUTOSW-LOP-SNCP

Clear the AUTOSW-LOP-SNCP Alarm

2.6.19 AUTOSW-SDBER-SNCP

Clear the AUTOSW-SDBER-SNCP Condition

2.6.20 AUTOSW-SFBER-SNCP

Clear the AUTOSW-SFBER-SNCP Condition

2.6.21 AUTOSW-UNEQ-SNCP (HPMON)

Clear the AUTOSW-UNEQ-SNCP (HPMON) Alarm

2.6.22 AUTOSW-UNEQ-SNCP (VCMON)

Clear the AUTOSW-UNEQ-SNCP (VCMON) Alarm

2.6.23 BAT-A-HGH-VLT

Clear the BAT-A-HGH-VLT Condition

2.6.24 BAT-A-LOW-VLT

Clear the BAT-A-LOW-VLT Condition

2.6.25 BAT-B-HGH-VLT

Clear the BAT-B-HGH-VLT Condition

2.6.26 BAT-B-LOW-VLT

Clear the BAT-B-LOW-VLT Condition

2.6.27 BKUPMEMP

Clear the BKUPMEMP Alarm

2.6.28 CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.6.29 CARLOSS (E-Series)

Clear the CARLOSS (E-Series) Alarm

2.6.30 CARLOSS (G-Series)

Clear the CARLOSS (G-Series) Alarm

2.6.31 CARLOSS (ML-Series)

Clear the CARLOSS (ML-Series) Alarm

2.6.32 CKTDOWN

Clear the CKTDOWN Alarm

2.6.33 CLDRESTART

Clear the CLDRESTART Condition

2.6.34 COMIOXC

Clear the COMIOXC Alarm

2.6.35 CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.6.36 CONTBUS-B-18

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

2.6.37 CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.6.38 CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.6.39 CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.6.40 CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.6.41 DATAFLT

Clear the DATAFLT Alarm

2.6.42 DBOSYNC

Clear the DBOSYNC Alarm

2.6.43 DS3-MISM

Clear the DS3-MISM Condition

2.6.44 DSP-COMM-FAIL

2.6.45 DSP-FAIL

Clear the DSP-FAIL Alarm

2.6.46 EHIBATVG-A

Clear the EHIBATVG-A Alarm

2.6.47 EHIBATVG-B

Clear the EHIBATVG-B Alarm

2.6.48 ELWBATVG-A

Clear the ELWBATVG-A Alarm

2.6.49 ELWBATVG-B

Clear the ELWBATVG-B Alarm

2.6.50 EOC

Clear the EOC Alarm

2.6.51 EQPT

Clear the EQPT Alarm

2.6.52 EQPT-MISS

Clear the EQPT-MISS Alarm

2.6.53 ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.6.54 E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.6.55 EXCCOL

Clear the EXCCOL Alarm

2.6.56 EXERCISE-RING-REQ

2.6.57 EXERCISE-SPAN-REQ

2.6.58 EXT

Clear the EXT Alarm

2.6.59 EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.6.60 E3-ISD

2.6.61 FAILTOSW

Clear the FAILTOSW Condition

2.6.62 FAILTOSW-HO

Clear the FAILTOSW-HO Condition

2.6.63 FAILTOSW-LO

Clear the FAILTOSW-LO Condition

2.6.64 FAILTOSWR

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

2.6.65 FAILTOSWS

Clear the FAILTOSWS Condition

2.6.66 FAN

Clear the FAN Alarm

2.6.67 FE-AIS

Clear the FE-AIS Condition

2.6.68 FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.6.69 FE-DS3-SA

Clear the FE-DS3-SA Condition

2.6.70 FE-E1-MULTLOS

Clear the FE-E1-MULTLOS Condition

2.6.71 FE-E1-NSA

Clear the FE-E1-NSA Condition

2.6.72 FE-E1-SA

Clear the FE-E1-SA Condition

2.6.73 FE-E1-SNGLLOS

Clear the FE-E1-SNGLLOS Condition

2.6.74 FE-E3-NSA

Clear the FE-E3-NSA Condition

2.6.75 FE-E3-SA

Clear the FE-E3-SA Condition

2.6.76 FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.6.77 FE-EXERCISING-RING

2.6.78 FE-EXERCISING-SPAN

2.6.79 FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.6.80 FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.6.81 FE-IDLE

Clear the FE-IDLE Condition

2.6.82 FE-LOCKOUTOFPR-ALL

Clear the FE-LOCKOUTOFPR-ALL Condition

2.6.83 FE-LOCKOUTOFPR-RING

Clear the FE-LOCKOUTOFPR-RING Condition

2.6.84 FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.6.85 FE-LOCKOUTOFWK-RING

Clear the FE-LOCKOUTOFWK-RING Condition

2.6.86 FE-LOCKOUTOFWK-SPAN

Clear the FE-LOCKOUTOFWK-SPAN Condition

2.6.87 FE-LOF

Clear the FE-LOF Condition

2.6.88 FE-LOS

Clear the FE-LOS Condition

2.6.89 FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.6.90 FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.6.91 FEPRLF

Clear the FEPRLF Alarm on an MS-SPRing

2.6.92 FE-SDPRLF

Clear the FE-SDPRLF Alarm on an MS-SPRing

2.6.93 FORCED-REQ

Clear the FORCED-REQ Condition

2.6.94 FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.6.95 FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.6.96 FRCDSWTOINT

2.6.97 FRCDSWTOPRI

2.6.98 FRCDSWTOSEC

2.6.99 FRCDSWTOTHIRD

2.6.100 FRNGSYNC

Clear the FRNGSYNC Condition

2.6.101 FSTSYNC

2.6.102 FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.6.103 GCC-EOC

Clear the GCC-EOC Alarm

2.6.104 HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.6.105 HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.6.106 HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.6.107 HI-RXTEMP

Clear the HI-RXTEMP Alarm

2.6.108 HITEMP

Clear the HITEMP Alarm

2.6.109 HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.6.110 HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.6.111 HP-RFI

Clear the HP-RFI Condition

2.6.112 HP-TIM

Clear the HP-TIM Alarm

2.6.113 HP-UNEQ

Clear the HP-UNEQ Alarm

2.6.114 IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.6.115 INC-ISD

2.6.116 INHSWPR

Clear the INHSWPR Condition

2.6.117 INHSWWKG

Clear the INHSWWKG Condition

2.6.118 INVMACADR

2.6.119 KB-PASSTHR

Clear the KB-PASSTHR Condition

2.6.120 LAN-POL-REV

Clear the LAN-POL-REV Condition

2.6.121 LASEREOL

Clear the LASEREOL Alarm

2.6.122 LKOUTPR-R

Clear the LKOUTPR-R Condition

2.6.123 LKOUTPR-S

Clear the LKOUTPR-S Condition

2.6.124 LKOUTWK-R

Clear the LKOUTWK-R Condition

2.6.125 LKOUTWK-S

Clear the LKOUTWK-S Condition

2.6.126 LMP-HELLODOWN

Clear the LMP-HELLODOWN Alarm

2.6.127 LMP-NDFAIL

Clear the LMP-NDFAIL Alarm

2.6.128 LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.6.129 LOCKOUT-REQ-RING

Clear the LOCKOUT-REQ-RING Condition

2.6.130 LOF (BITS)

Clear the LOF (BITS) Alarm

2.6.131 LOF

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

2.6.132 LO-LASERBIAS

Clear the LO-LASERBIAS Alarm

2.6.133 LO-LASERTEMP

Clear the LO-LASERTEMP Alarm

2.6.134 LOM

Clear the LOM Alarm

2.6.135 LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.6.136 LO-RXTEMP

Clear the LO-RXTEMP Alarm

2.6.137 LOS (BITS)

Clear the LOS (BITS) Alarm

2.6.138 LOS

Clear the LOS Alarm

2.6.139 LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.6.140 LPBKCRS

Clear the LBKCRS Condition

2.6.141 LPBKFACILITY (DS-3, E-N, STM-N)

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

2.6.142 LPBKTERMINAL (DS-3, E-N, STM-N)

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

2.6.143 LPBKTERMINAL(G1000-4)

Clear the LPBKTERMINAL (G-Series) Condition

2.6.144 LP-PLM

Clear the LP-PLM Alarm

2.6.145 LP-RFI

Clear the LP-RFI Condition

2.6.146 LP-TIM

Clear the LP-TIM Alarm

2.6.147 LP-UNEQ

Clear the LP-UNEQ Alarm

2.6.148 MAN-REQ

Clear the MAN-REQ Condition

2.6.149 MANRESET

2.6.150 MANSWTOINT

2.6.151 MANSWTOPRI

2.6.152 MANSWTOSEC

2.6.153 MANSWTOTHIRD

2.6.154 MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.6.155 MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.6.156 MEA (BP)

Clear the MEA (BP) Alarm

2.6.157 MEA (EQPT)

Clear the MEA Alarm

2.6.158 MEA (FAN)

Clear the MEA Alarm

2.6.159 MEM-GONE

2.6.160 MEM-LOW

2.6.161 MFGMEM

Clear the MFGMEM Alarm

2.6.162 MFGMEM (Backplane or Fan)

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

2.6.163 MS-AIS

Clear the MS-AIS Condition

2.6.164 MS-RFI

Clear the MS-RFI Condition

2.6.165 MSSP-OOSYNC

Clear the MSSP-OOSYNC Alarm

2.6.166 NO-CONFIG

Clear the NO-CONFIG Alarm

2.6.167  NOT-AUTHENTICATED

2.6.168 ODUK-AIS-PM

Clear the ODUK-AIS-PM Condition

2.6.169 ODUK-BDI-PM

Clear the ODUK-BDI-PM Condition

2.6.170 ODUK-LCK-PM

Clear the ODUK-LCK-PM Condition

2.6.171 ODUK-OCI-PM

Clear the ODUK-OCI-PM Condition

2.6.172 ODUK-SD-PM

Clear the ODUK-SD-PM Condition

2.6.173 ODUK-SF-PM

Clear the ODUK-SF-PM Condition

2.6.174 ODUK-TIM-PM

Clear the ODUK-TIM-PM Condition

2.6.175 OTUK-AIS

Clear the OTUK-AIS Condition

2.6.176 OTUK-BDI

Clear the OTUK-BDI Condition

2.6.177 OTUK-IAE

Clear the OTUK-IAE Alarm

2.6.178 OTUK-LOF

Clear the OTUK-LOF Alarm

2.6.179 OTUK-SD

Clear the OTUK-SD Condition

2.6.180 OTUK-SF

Clear the OTUK-SF Condition

2.6.181 OTUK-TIM

Clear the OTUK-TIM Alarm

2.6.182 PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.6.183 PORT-CODE-MISM

Clear the PORT-CODE-MISM Alarm

2.6.184 PORT-COMM-FAIL

Clear the PORT-COMM-FAIL Alarm

2.6.185 PORT-MISMATCH

2.6.186 PORT-MISSING

Clear the PORT-MISSING Alarm

2.6.187 PRC-DUPID

Clear the PRC-DUPID Alarm

2.6.188 PROTNA

Clear the PROTNA Alarm

2.6.189 PWR-A

Clear the PWR-A Alarm

2.6.190 PWR-B

Clear the PWR-B Alarm

2.6.191 PWR-REDUN

Clear the PWR-REDUN Alarm

2.6.192 RAI

Clear the RAI Condition

2.6.193 RCVR-MISS

Clear the RCVR-MISS Alarm

2.6.194 RFI

Clear the RFI Condition

2.6.195 RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.6.196 RING-SW-EAST

2.6.197 RING-SW-WEST

2.6.198 RSVP-HELLODOWN

Clear the RSVP-HELLODOWN Alarm

2.6.199 RUNCFG-SAVENEED

2.6.200 SD

Clear the SD Condition

2.6.201 SDBER-EXCEED-HO

Clear the SDBER-EXCEED-HO Condition

2.6.202 SF

Clear the SF Condition

2.6.203 SFBER-EXCEED-HO

Clear the SFBER-EXCEED-HO Condition

2.6.204 SFTWDOWN

2.6.205 SNTP-HOST

Clear the SNTP-HOST Alarm

2.6.206 SPAN-SW-EAST

2.6.207 SPAN-SW-WEST

2.6.208 SQUELCH

Clear the SQUELCH Condition

2.6.209 SQUELCHED

Clear the SQUELCHED Alarm

2.6.210 SQUELCH-PATH

Clear the SQUELCH-PATH Alarm

2.6.211 SSM-DUS

2.6.212 SSM-FAIL (BITS)

Clear the SSM-FAIL (BITS) Alarm

2.6.213 SSM-FAIL (STM-N)

Clear the SSM-FAIL (STM-N) Alarm

2.6.214 SSM-LNC

2.6.215 SSM-OFF (BITS)

2.6.216 SSM-OFF (STM-N)

2.6.217 SSM-PRC

2.6.218 SSM-SETS

2.6.219 SSM-STU (BITS)

Clear the SSM-STU (BITS) Condition

2.6.220 SSM-STU (STM-N)

Clear the SSM-STU (STM-N) Condition

2.6.221 SSM-TNC (BITS)

2.6.222 SSM-TNC (STM-N)

2.6.223 SWMTXMOD

Clear the SWMTXMOD Alarm

2.6.224 SWTOPRI

2.6.225 SWTOSEC

2.6.226 SWTOTHIRD

2.6.227 SYNC-FREQ (BITS, STM-N)

Clear the SYNC-FREQ (BITS, STM-N) Condition

2.6.228 SYNCPRI

Clear the SYNCPRI Condition

2.6.229 SYNCSEC

Clear the SYNCSEC Alarm

2.6.230 SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.6.231 SYSBOOT

2.6.232 TIM

Clear the TIM Condition

2.6.233 TPTFAIL (G-Series)

Clear the TPTFAIL (G-Series) Alarm

2.6.234 TPTFAIL (ML-Series)

Clear the TPTFAIL (ML-Series) Alarm

2.6.235 TRMT

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

2.6.236 TRMT-MISS

Clear the TRMT-MISS Alarm

2.6.237 TU-AIS

Clear the TU-AIS Condition

2.6.238 TU-LOP

Clear the TU-LOP Alarm

2.6.239 UNC-WORD

Clear the UNC-WORD Condition

2.6.240 WVL-MISMATCH

Clear the WVL-MISMATCH alarm

2.6.241 WKSWPR

Clear the WKSWPR Condition

2.6.242 WTR

2.7 Common Procedures in Alarm Troubleshooting

Identify a Ring ID or Node ID Number

Change a Ring ID 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 an MS-SPRing Span Lock Out

Clear an SNCP Lockout

Switch Protection Group Traffic with an External Switching Command

Side Switch the Active and Standby Cross-Connect Cards

Clear an External Switching Command

Delete a Circuit

Clear a Loopback

Reset Active TCC2 Card and Activate Standby 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 the Fan-Tray Assembly


Alarm Troubleshooting


This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 SDH alarm and condition. Table 2-1 through Table 2-4 give lists of ONS 15454 SDH alarms organized by severity. Table 2-5 gives a list of alarm organized alphabetically. Table 2-6 gives 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 http://www.cisco.com/tac 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 alarm index by severity tables group alarms and conditions by the severity displayed in the CTC Alarms window in the severity (SEV) column. The default standby severity for all ONS 15454 SDH alarms on unprovisioned card ports is Minor, Non-Service Affecting. All severities listed in the alarm entry are the default for the active card, if applicable. Alarm severities can be altered from default settings for individual alarms or groups of alarms on a card, node, or network basis.

2.1.1 Critical Alarms (CR)

Table 2-1 lists Critical alarms.


2.1.2 Major Alarms (MJ)

Table 2-2 lists Major alarms.


2.1.3 Minor Alarms (MN)

Table 2-3 lists Minor alarms.


2.1.4 Conditions (NA or NR)

Table 2-4 lists Not Alarmed or Not Reported conditions.

Table 2-4 Conditions Index 

AIS

FE-LOCKOUTOFWK-RING

ODUK-AIS-PM

AS-CMD

FE-LOCKOUTOFWK-SPAN

ODUK-BDI-PM

AS-MT

FE-LOF

ODUK-LCK-PM

AU-AIS

FE-LOS

ODUK-OCI-PM

AUD-LOG-LOSS

FE-MANWKSWPR-RING

ODUK-SD-PM

AUD-LOG-LOW

FE-MANWKSWPR-SPAN

ODUK-SF-PM

AUTOSW-AIS-SNCP

FORCED-REQ

ODUK-TIM-PM

AUTOSW-LOP-SNCP

FORCED-REQ-RING

OTUK-AIS

AUTOSW-LOP-SNCP

FORCED-REQ-SPAN

OTUK-BDI

AUTOSW-SDBER-SNCP

FRCDSWTOINT

OTUK-SD

AUTOSW-SFBER-SNCP

FRCDSWTOPRI

OTUK-SF

AUTOSW-UNEQ-SNCP (HPMON)

FRCDSWTOSEC

RAI

BAT-A-HGH-VLT

FRCDSWTOTHIRD

RFI

BAT-A-LOW-VLT

FRNGSYNC

RING-SW-EAST

BAT-B-HGH-VLT

FULLPASSTHR-BI

RING-SW-WEST

BAT-B-LOW-VLT

HLDOVRSYNC

RUNCFG-SAVENEED

CLDRESTART

INC-ISD

SD

DS3-MISM

INHSWPR

SDBER-EXCEED-HO

EXERCISE-RING-REQ

INHSWWKG

SF

EXERCISE-SPAN-REQ

KB-PASSTHR

SFBER-EXCEED-HO

E3-ISD

LAN-POL-REV

SPAN-SW-EAST

FAILTOSW

LKOUTPR-R

SPAN-SW-WEST

FAILTOSW-HO

LKOUTPR-S

SQUELCH

FAILTOSW-LO

LKOUTWK-R

SSM-DUS

FAILTOSWR

LKOUTWK-S

SSM-FAIL (BITS)

FAILTOSWS

LOCKOUT-REQ

SSM-FAIL (STM-N)

FE-AIS

LOCKOUT-REQ-RING

SSM-LNC

FE-DS3-NSA

LPBKCRS

SSM-OFF (BITS)

FE-DS3-SA

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

SSM-OFF (STM-N)

FE-E1-MULTLOS

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

SSM-PRC

FE-E1-NSA

LPBKTERMINAL(G1000-4)

SSM-SETS

FE-E1-SA

LP-RFI

SSM-TNC (BITS)

FE-E1-SNGLLOS

MAN-REQ

SSM-TNC (STM-N)

FE-E3-NSA

MANRESET

SWTOPRI

FE-E3-SA

MANSWTOINT

SWTOSEC

FE-EXERCISING-RING

MANSWTOPRI

SWTOTHIRD

FE-EXERCISING-SPAN

MANSWTOSEC

SYNC-FREQ (BITS, STM-N)

FE-FRCDWKSWPR-RING

MANSWTOTHIRD

TIM

FE-FRCDWKSWPR-SPAN

MANUAL-REQ-RING

TU-AIS

FE-IDLE

MANUAL-REQ-SPAN

UNC-WORD

FE-LOCKOUTOFPR-ALL

MS-AIS

WKSWPR

FE-LOCKOUTOFPR-RING

MS-RFI

WTR

FE-LOCKOUTOFPR-SPAN

NO-CONFIG

 

2.2 Alarms and Conditions Indexed By Alphabetical Entry

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

Table 2-5 Alphabetical Alarm Index 

AIS

FE-LOCKOUTOFPR-ALL

MFGMEM (Backplane or Fan)

APSB

FE-LOCKOUTOFPR-RING

MS-AIS

APSCDFLTK

FE-LOCKOUTOFPR-SPAN

MS-RFI

APSC-IMP

FE-LOCKOUTOFWK-RING

MSSP-OOSYNC

APSCINCON

FE-LOCKOUTOFWK-SPAN

NO-CONFIG

APSCM

FE-LOF

ODUK-AIS-PM

APSCNMIS

FE-LOS

ODUK-BDI-PM

AS-CMD

FE-MANWKSWPR-RING

ODUK-LCK-PM

AS-MT

FE-MANWKSWPR-SPAN

ODUK-OCI-PM

AU-AIS

FEPRLF

ODUK-SD-PM

AUD-LOG-LOSS

FE-SDPRLF

ODUK-SF-PM

AUD-LOG-LOW

FORCED-REQ

ODUK-TIM-PM

AU-LOF

FORCED-REQ-RING

OTUK-AIS

AU-LOP

FORCED-REQ-SPAN

OTUK-BDI

AUTOLSROFF

FRCDSWTOINT

OTUK-IAE

AUTORESET

FRCDSWTOPRI

OTUK-LOF

AUTOSW-AIS-SNCP

FRCDSWTOSEC

OTUK-SD

AUTOSW-LOP-SNCP

FRCDSWTOTHIRD

OTUK-SF

AUTOSW-SDBER-SNCP

FRNGSYNC

OTUK-TIM

AUTOSW-SFBER-SNCP

FSTSYNC

PEER-NORESPONSE

AUTOSW-UNEQ-SNCP (HPMON)

FULLPASSTHR-BI

PORT-CODE-MISM

AUTOSW-UNEQ-SNCP (VCMON)

GCC-EOC

PORT-COMM-FAIL

BAT-A-HGH-VLT

HI-LASERBIAS

PORT-MISMATCH

BAT-A-LOW-VLT

HI-LASERTEMP

PORT-MISSING

BAT-B-HGH-VLT

HI-RXPOWER

PRC-DUPID

BAT-B-LOW-VLT

HI-RXTEMP

PROTNA

BKUPMEMP

HITEMP

PWR-A

CARLOSS (EQPT)

HI-TXPOWER

PWR-B

CARLOSS (E-Series)

HLDOVRSYNC

PWR-REDUN

CARLOSS (G-Series)

HP-RFI

RAI

CARLOSS (ML-Series)

HP-TIM

RCVR-MISS

CKTDOWN

HP-UNEQ

RFI

CLDRESTART

IMPROPRMVL

RING-MISMATCH

COMIOXC

INC-ISD

RING-SW-EAST

CONTBUS-A-18

INHSWPR

RING-SW-WEST

CONTBUS-B-18

INHSWWKG

RSVP-HELLODOWN

CONTBUS-IO-A

INVMACADR

RUNCFG-SAVENEED

CONTBUS-IO-B

KB-PASSTHR

SD

CTNEQPT-PBPROT

LAN-POL-REV

SDBER-EXCEED-HO

CTNEQPT-PBWORK

LASEREOL

SF

DATAFLT

LKOUTPR-R

SFBER-EXCEED-HO

DBOSYNC

LKOUTPR-S

SFTWDOWN

DS3-MISM

LKOUTWK-R

SNTP-HOST

DSP-COMM-FAIL

LKOUTWK-S

SPAN-SW-EAST

DSP-FAIL

LMP-HELLODOWN

SPAN-SW-WEST

E3-ISD

LMP-NDFAIL

SQUELCH

EHIBATVG-A

LOCKOUT-REQ

SQUELCHED

EHIBATVG-B

LOCKOUT-REQ-RING

SQUELCH-PATH

ELWBATVG-A

LOF (BITS)

SSM-DUS

ELWBATVG-B

LOF

SSM-FAIL (BITS)

EOC

LO-LASERBIAS

SSM-FAIL (STM-N)

EQPT

LO-LASERTEMP

SSM-LNC

EQPT-MISS

LOM

SSM-OFF (BITS)

ERROR-CONFIG

LO-RXPOWER

SSM-OFF (STM-N)

E-W-MISMATCH

LO-RXTEMP

SSM-PRC

EXCCOL

LOS (BITS)

SSM-SETS

EXERCISE-RING-REQ

LOS

SSM-STU (BITS)

EXERCISE-SPAN-REQ

LO-TXPOWER

SSM-STU (STM-N)

EXT

LPBKCRS

SSM-TNC (BITS)

EXTRA-TRAF-PREEMPT

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

SSM-TNC (STM-N)

FAILTOSW

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

SWMTXMOD

FAILTOSW-HO

LPBKTERMINAL(G1000-4)

SWTOPRI

FAILTOSW-LO

LP-PLM

SWTOSEC

FAILTOSWR

LP-RFI

SWTOTHIRD

FAILTOSWS

LP-TIM

SYNC-FREQ (BITS, STM-N)

FAN

LP-UNEQ

SYNCPRI

FE-AIS

MAN-REQ

SYNCSEC

FE-DS3-NSA

MANRESET

SYNCTHIRD

FE-DS3-SA

MANSWTOINT

SYSBOOT

FE-E1-MULTLOS

MANSWTOPRI

TIM

FE-E1-NSA

MANSWTOSEC

TPTFAIL (G-Series)

FE-E1-SA

MANSWTOTHIRD

TPTFAIL (ML-Series)

FE-E1-SNGLLOS

MANUAL-REQ-RING

TRMT

FE-E3-NSA

MANUAL-REQ-SPAN

TRMT-MISS

FE-E3-SA

MEA (BP)

TU-AIS

FE-EQPT-NSA

MEA (EQPT)

TU-LOP

FE-EXERCISING-RING

MEA (FAN)

UNC-WORD

FE-EXERCISING-SPAN

MEM-GONE

WVL-MISMATCH

FE-FRCDWKSWPR-RING

MEM-LOW

WKSWPR

FE-FRCDWKSWPR-SPAN

MFGMEM

WTR

FE-IDLE

   

2.3 Alarm Index by Alarm Type

Table 2-6 gives the name and page number of every alarm in the chapter organized by alarm type.

Table 2-6 Alarm Index by Alarm Type 

BITS: AIS

BITS: LOF (BITS)

BITS: LOS (BITS)

BITS: SSM-DUS

BITS: SSM-FAIL (BITS)

BITS: SSM-LNC

BITS: SSM-OFF (STM-N)

BITS: SSM-PRC

BITS: SSM-SETS

BITS: SSM-STU (BITS)

BITS: SSM-TNC (STM-N)

BP: AS-CMD

BP: INVMACADR

BP: MEA (BP)

BP: MFGMEM (Backplane or Fan)

CC: LMP-HELLODOWN

CC: LMP-NDFAIL

CKT: CKTDOWN

DS3: AIS

DS3: AS-CMD

DS3: AS-MT

DS3: DS3-MISM

DS3: FE-AIS

DS3: FE-DS3-NSA

DS3: FE-DS3-SA

DS3: FE-EQPT-NSA

DS3: FE-IDLE

DS3: FE-LOF

DS3: FE-LOS

DS3: INC-ISD

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

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

DS3: LOS

DS3: LOF

DS3: RAI

DWDM Client: AIS

DWDM Client: AS-CMD

DWDM Client: AS-MT

DWDM Client: AUTOLSROFF

DWDM Client: CARLOSS (ML-Series)

DWDM Client: EOC

DWDM Client: FAILTOSW

DWDM Client: FORCED-REQ-SPAN

DWDM Client: HI-LASERBIAS

DWDM Client: HI-LASERTEMP

DWDM Client: HI-RXPOWER

DWDM Client: HI-TXPOWER

DWDM Client: LOCKOUT-REQ

DWDM Client: LOF

DWDM Client: LO-LASERBIAS

DWDM Client: LO-LASERTEMP

DWDM Client: LO-RXPOWER

DWDM Client: LOS

DWDM Client: LO-TXPOWER

DWDM Client: LPBKFACILITY (DS-3, E-N, STM-N)

DWDM Client: LPBKTERMINAL (DS-3, E-N, STM-N)

DWDM Client: MANUAL-REQ-SPAN

DWDM Client: PORT-CODE-MISM

DWDM Client: PORT-COMM-FAIL

DWDM Client: PORT-MISSING

DWDM Client: PORT-MISMATCH

DWDM Client: RFI

DWDM Client: SF

DWDM Client: SD

DWDM Client: SQUELCHED

DWDM Client: SSM-DUS

DWDM Client: SSM-FAIL (STM-N)

DWDM Client: SSM-LNC

DWDM Client: SSM-OFF (STM-N)

DWDM Client: SSM-PRC

DWDM Client: SSM-SETS

DWDM Client: SSM-STU (STM-N)

DWDM Client: SSM-TNC (STM-N)

DWDM Client: TIM

DWDM Client: WKSWPR

DWDM Trunk: AIS

DWDM Trunk: AS-CMD

DWDM Trunk: AS-MT

DWDM Trunk: AUTOLSROFF

DWDM Trunk: CARLOSS (ML-Series)

DWDM Trunk: DSP-COMM-FAIL

DWDM Trunk: DSP-FAIL

DWDM Trunk: EOC

DWDM Trunk: GCC-EOC

DWDM Trunk: HI-LASERBIAS

DWDM Trunk: HI-LASERTEMP

DWDM Trunk: HI-RXPOWER

DWDM Trunk: HI-RXTEMP

DWDM Trunk: HI-TXPOWER

DWDM Trunk: LOF

DWDM Trunk: LO-LASERBIAS

DWDM Trunk: LO-LASERTEMP

DWDM Trunk: LO-RXPOWER

DWDM Trunk: LO-RXTEMP

DWDM Trunk: LO-TXPOWER

DWDM Trunk: LOM

DWDM Trunk: LOS

DWDM Trunk: LPBKFACILITY (DS-3, E-N, STM-N)

DWDM Trunk: LPBKTERMINAL (DS-3, E-N, STM-N)

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-IAE

DWDM Trunk: OTUK-LOF

DWDM Trunk: OTUK-SD

DWDM Trunk: OTUK-SF

DWDM Trunk: OTUK-TIM

DWDM Trunk: RFI

DWDM Trunk: SD

DWDM Trunk: SF

DWDM Trunk: SQUELCHED

DWDM Trunk: SSM-DUS

DWDM Trunk: SSM-FAIL (STM-N)

DWDM Trunk: SSM-LNC

DWDM Trunk: SSM-OFF (STM-N)

DWDM Trunk: SSM-PRC

DWDM Trunk: SSM-SETS

DWDM Trunk: SSM-STU (STM-N)

DWDM Trunk: SSM-TNC (STM-N)

DWDM Trunk: TIM

DWDM Trunk: UNC-WORD

DWDM Trunk: WVL-MISMATCH

E1: AIS

E1: AS-CMD

E1: AS-MT

E1: LOF

E1: LOS

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

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

E1: RAI

E1: RCVR-MISS

E1: SD

E1: SF

E1: TRMT-MISS

E1: TRMT

E3: AIS

E3: AS-CMD

E3: AS-MT

E3: DS3-MISM

E3: E3-ISD

E3: FE-AIS

E3: FE-EQPT-NSA

E3: FE-E1-NSA

E3: FE-E1-SA

E3: FE-E3-NSA

E3: FE-E3-SA

E3: FE-IDLE

E3: FE-LOF

E3: FE-LOS

E3: LOS

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

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

E4: AIS

E4: AS-CMD

E4: AS-MT

E4: LOF

E4: LOS

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

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

E4: SD

E4: SF

ECN: AIS

ECN: AS-CMD

ECN: AS-MT

EQPT: AUTORESET

ECN: LOF

ECN: LOS

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

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

ECN: RFI

ENV: EXT

EQPT: AS-CMD

EQPT: BKUPMEMP

EQPT: CARLOSS (EQPT)

EQPT: CLDRESTART

EQPT: COMIOXC

EQPT: CONTBUS-A-18

EQPT: CONTBUS-B-18

EQPT: CONTBUS-IO-A

EQPT: CONTBUS-IO-B

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: 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 (EQPT)

ETHER: CARLOSS (G-Series)

EXTSYNCH: FRCDSWTOPRI

EXTSYNCH: FRCDSWTOSEC

EXTSYNCH: FRCDSWTOTHIRD

EXTSYNCH: MANSWTOPRI

EXTSYNCH: MANSWTOSEC

EXTSYNCH: MANSWTOTHIRD

EXTSYNCH: SWTOPRI

EXTSYNCH: SWTOSEC

EXTSYNCH: SWTOTHIRD

EXTSYNCH: SYNCPRI

EXTSYNCH: SYNCSEC

EXTSYNCH: SYNCTHIRD

FAN: EQPT-MISS

FAN: FAN

FAN: MEA (FAN)

FAN: MFGMEM (Backplane or Fan)

FUDC: AIS

FUDC: LOS

HDGE [G1000]: AS-CMD

HDGE [G1000]: AS-MT

HDGE [G1000]: CARLOSS (G-Series)

HDGE [G1000]: LPBKTERMINAL(G1000-4)

HDGE [G1000]: TPTFAIL (G-Series)

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: SDBER-EXCEED-HO

HPTERM: SFBER-EXCEED-HO

LPMON: AUTOSW-AIS-SNCP

LPMON: AUTOSW-LOP-SNCP

LPMON: AUTOSW-SDBER-SNCP

LPMON: AUTOSW-SFBER-SNCP

LPMON: AUTOSW-UNEQ-SNCP (VCMON)

LPMON: FAILTOSW-LO

LPMON: FORCED-REQ

LPMON: LOCKOUT-REQ

LPMON: LP-UNEQ

LPMON: MAN-REQ

LPMON: TU-AIS

LPMON: TU-LOP

LPMON: WKSWPR

LPMON: WTR

LPTERM: LP-PLM

LPTERM: LP-RFI

LPTERM: LP-TIM

LPTERM: LP-UNEQ

LPTERM: SD

LPTERM: SF

LPTERM: TU-AIS

LPTERM: TU-LOP

ML1000: AS-CMD

ML1000: CARLOSS (ML-Series)

ML1000: TPTFAIL (ML-Series)

MSUDC: APSB

MSUDC: LOS

NBR: RSVP-HELLODOWN

NE: AS-CMD

NE: AUD-LOG-LOSS

NE: AUD-LOG-LOW

NE: BAT-A-HGH-VLT

NE: BAT-A-LOW-VLT

NE: BAT-B-HGH-VLT

NE: BAT-B-LOW-VLT

NE: DATAFLT

NE: DBOSYNC

NE: EHIBATVG-A

NE: EHIBATVG-B

NE: ELWBATVG-A

NE: ELWBATVG-B

NE: HITEMP

NE: LAN-POL-REV

NE: PRC-DUPID

NE: PWR-A

NE: PWR-B

NE: SNTP-HOST

NE: SYSBOOT

NERING: FULLPASSTHR-BI

NERING: KB-PASSTHR

NERING: PRC-DUPID

NERING: MSSP-OOSYNC

NERING: RING-MISMATCH

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 (STM-N)

NESYNCH: SSM-TNC (STM-N)

NESYNCH: SWTOPRI

NESYNCH: SWTOSEC

NESYNCH: SWTOTHIRD

NESYNCH: SYNCPRI

NESYNCH: SYNCSEC

NESYNCH: SYNCTHIRD

STM1E: AS-CMD

STM1E: AS-MT

STM1E: LOS

STM1E: LOF

STM1E: SD

STM1E: TIM

STM1E: MS-AIS

STM1E: SF

STM1E: SD

STM1E: MS-RFI

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

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

STM1E: SSM-DUS

STM1E: SSM-FAIL (STM-N)

STM1E: SSM-LNC

STM1E: SSM-OFF (STM-N)

STM1E: SSM-PRC

STM1E: SSM-STU (STM-N)

STM1E: SSM-SETS

STMN: APSB

STMN: APSCDFLTK

STMN: APSC-IMP

STMN: APSCINCON

STMN: APSCM

STMN: AS-CMD

STMN: APSCNMIS

STMN: AS-MT

STMN: AUTOLSROFF

STMN: EOC

STMN: EXERCISE-RING-REQ

STMN: EXERCISE-SPAN-REQ

STMN: EXTRA-TRAF-PREEMPT

STMN: FAILTOSWR

STMN: FAILTOSWS

STMN: FE-EXERCISING-RING

STMN: FE-EXERCISING-SPAN

STMN: FE-FRCDWKSWPR-RING

STMN: FE-FRCDWKSWPR-SPAN

STMN: FE-LOCKOUTOFPR-RING

STMN: FE-LOCKOUTOFPR-SPAN

STMN: FE-LOCKOUTOFWK-RING

STMN: FE-LOCKOUTOFWK-SPAN

STMN: FE-MANWKSWPR-RING

STMN: FE-MANWKSWPR-SPAN

STMN: FEPRLF

STMN: FE-SDPRLF

STMN: FORCED-REQ-RING

STMN: LASEREOL

STMN: LKOUTPR-R

STMN: LKOUTPR-S

STMN: LKOUTWK-R

STMN: LKOUTWK-S

STMN: LOCKOUT-REQ

STMN: LOCKOUT-REQ-RING

STMN: LOF

STMN: LOS

STMN: LPBKFACILITY (DS-3, E-N, STM-N)

STMN: LPBKTERMINAL (DS-3, E-N, STM-N)

STMN: MANUAL-REQ-RING

STMN: MANUAL-REQ-SPAN

STMN: MS-AIS

STMN: MS-RFI

STMN: RING-SW-EAST

STMN: RING-SW-WEST

STMN: SD

STMN: SF

STMN: SPAN-SW-EAST

STMN: SPAN-SW-WEST

STMN: SQUELCH

STMN: SQUELCH-PATH

STMN: SSM-DUS

STMN: SSM-FAIL (STM-N)

STMN: SSM-LNC

STMN: SSM-OFF (STM-N)

STMN: SSM-STU (STM-N)

STMN: SSM-PRC

STMN: SSM-TNC (STM-N)

STMN: SSM-SETS

STMN: SYNC-FREQ (BITS, STM-N)

STMN: TIM

STMN: WTR


2.3.1 Alarm Type/Object Definition

Table 2-7 defines abbreviations used in the alarm troubleshooting procedures.

Table 2-7 Alarm Type/Object Definition 

AIE

Alarm expansion panel

BITS

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

BP

Backplane

DWDM
Client

The port (such as STM-N) where the client signal is plugged in

DWDM
Trunk

The main span of the link; from the card point of view, it is the port operating in the 100-GHz spacing frequency grid

E1

E1-42 card

E3

E3-12 card

E-N

E-1 or E-3

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

FAN

Fan-tray assembly

NE

The entire network element (node)

NERINGSDH

SDH NE1 ring

NESYNCHSDH

SDH NE synchronization

STM-1E

Synchronous Transfer Mode 1 (speed) Electrical Interface

STMN

Synchronous Transfer Mode (speed)

1 Network element


2.4 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 in the CTC Alarms window and Not Alarmed (NA) trouble notifications in the Conditions window. Alarms signify a problem that the user needs to fix, such as anLOS alarm (see page 2-107). Conditions notify the user of an event which does not require action, such as a SWTOSEC condition (see page 2-154) or a MANRESET condition (see page 2-115).

The ITU further divides alarms into Service-Affecting (SA) and NSA status. An SA failure affects a provided service or the network's ability to provide service. For example, a TRMT-MISS alarm (see page 2-161) is characterized as an SA failure. TRMT-MISS occurs when the cable connector leading to a port on an active E1-N-14 card is removed. This affects a provided service because traffic switches to the protect card. The HITEMP alarm (see page 2-91) means that the alarm object is hotter than 50 degrees Celsius (122 degrees Fahrenheit). HITEMP is an NSA failure for a single piece of equipment, or an SA failure for the NE. For example, if the HITEMP alarm is raised against a port with an EQPT object, the alarm is NSA because port and card traffic is protected. If the HITEMP alarm is raised against the NE (shelf), however, it is an SA alarm because a high temperature affects the network's ability to provide service.

2.4.1 Conditions

When an SA failure is detected, the ONS 15454 also sends an AIS condition (see page 2-21) downstream. When it receives the AIS, the receiving node sends an HP-RFI condition (see page 2-93) or LP-RFI condition (see page 2-112) upstream. AIS-L and RFI belong in the conditions category and show in the Conditions window of CTC. However, unlike most conditions which are Not Alarmed (NA), Telcordia classifies these conditions as Not Reported (NR).

CTC reports NRs and NAs as conditions when conditions are retrieved. NAs are also reported in the History window of CTC. The condition reporting is not ITU-compliant.

2.4.2 Severities

The ONS 15454 SDH uses these ITU severities: Critical (CR), Major (MJ), and Minor (MN). Critical indicates a severe, service-affecting alarm that needs immediate correction. Major is still a serious alarm, but the failure has less of an impact on the network.

Minor alarms, such as the FSTSYNC alarm (see page 2-87), do not have a serious effect on service. FSTSYNC lets you know that the ONS 15454 SDH is choosing a new timing reference because the old reference failed. The loss of the prior timing source is something a user needs to troubleshoot, but this minor alarm should not disrupt service.

ITU severities are the default settings for the ONS 15454 SDH. A user may customize ONS 15454 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 alarm severity for the active reporting card, if applicable. The default severity for alarms reported by standby cards is always Minor, Non-Service-Affecting.

2.5 Safety Summary

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


Caution Hazardous voltage or energy might 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-16 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 might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might 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.6 Alarm Procedures

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


Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner 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.



Note When checking alarms, make sure 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.6.1 AIS

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

The Alarm Indication Signal (AIS) condition in the SDH overhead is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AIS, for example, when the port on the reporting node is in service but the DS-3 or STM-N port on a node upstream on the circuit is not in service. The upstream node often reports a loss of service or has an out-of-service (OOS) port. The AIS clears when you clear the primary alarm on the upstream node. However, the primary alarm node might not report any alarms that indicate there is a fault.

Procedure: Clear the AIS Condition


Step 1 Verify whether the upstream nodes and equipment have alarms, especially an LOS alarm (see page 2-107) or OOS ports.

Step 2 Clear the upstream alarms using the applicable procedure(s) in this chapter.

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


2.6.2 APSB

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

The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming APS signal. The failure occurs when an inconsistent APS byte or invalid code is detected. 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.

Procedure: Clear the APSB Alarm


Step 1 Use an optical test set to examine the incoming SDH overhead to confirm inconsistent or invalid K bytes.

For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15454 SDH.

Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you might need to replace the upstream cards for protection switching to operate properly.


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

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


2.6.3 APSCDFLTK

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

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. 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 an MSSP-OOSYNC alarm (see page 2-123).

Procedure: Clear the APSCDFLTK Alarm


Step 1 Complete the "Identify a Ring ID 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 "EXCCOL" 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, make sure 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 DCC terminations exist on each node.

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


2.6.4 APSC-IMP

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

An Improper APS Code alarm indicates 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. APSC-IMP occurs when these bits indicate a bad or invalid K byte. 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.

Procedure: 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 ID or Node ID Number" procedure.

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

Step 4 If a node has a ring ID number that does not match the other nodes, complete the "Change a Ring ID Number" procedure to make the ring ID numbers identical.

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


2.6.5 APSCINCON

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

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.

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


Step 1 Look for other alarms, especially an LOS alarm (see page 2-107), a LOF alarm (see page 2-103), or an AIS condition (see page 2-21). If they are present, complete the troubleshooting procedure(s) 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.6 APSCM

Major (MJ), Service Affecting (SA)

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 might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might 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.

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


2.6.7 APSCNMIS

Major (MJ), Service Affecting (SA)

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

Procedure: Clear the APSCNMIS Alarm


Step 1 Complete the "Identify a Ring ID 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 on 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 lockout 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 an MS-SPRing Span Lock Out" procedure to clear the lock out.

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


2.6.8 AS-CMD

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

The Alarms Suppressed by User Command condition applies to the node, backplane, and cards. AS-CMD occurs when alarms are suppressed for one or more cards or for the entire shelf.

Procedure: Clear the AS-CMD Condition


Step 1 In the 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, note what entity the condition is reported against, such as a port, slot, or shelf.

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

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

If the condition is reported against a "system," go to Step 8.

Step 3 If the AS-CMD condition is reported for a 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 Behavior tabs.

If the Suppress Alarms column check box is checked for a port row, deselect the check box 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 In node view, if the AS-CMD condition is reported for a card and not an individual port, click the Provisioning > Alarm Behavior tabs.

Step 5 Locate the row for the reported card slot. (The slot number information was in the Object column in the Conditions tab that you noted in Step 2.)

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

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

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

b. In the Backplane row, click the Suppress Alarms column check box to deselect the check box and click Apply.

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

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

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

c. Click Apply.

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


2.6.9 AS-MT

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

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

Procedure: Clear the AS-MT Condition


Step 1 Complete the "Clear a Loopback" procedure.

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


2.6.10 AU-AIS

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

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. AU-AIS is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AU-AIS, for example, when the port on the reporting node is in service (IS) but the DS-3 or STM-N port on a node upstream on the circuit is not in service. The upstream node often reports a loss of service, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an OOS port. The AU-AIS clears when you clear the primary alarm on the upstream node. However, the primary alarm node might not report any alarms that indicate there is a fault.

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


2.6.11 AUD-LOG-LOSS

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

The Audit Trail Log Loss condition occurs when the log is 100% full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries.

Procedure: Clear the AUD-LOG-LOSS Condition


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

Step 2 Click Retrieve.

Step 3 Click Archive.

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

Step 5 Enter a name in the File Name field.

You do not have to assign an extension to the file. 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 will be 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.12 AUD-LOG-LOW

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

The Audit Trail Log Loss condition occurs when the audit trail log is 80% full.


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


2.6.13 AU-LOF

Major (MJ), Service Affecting (SA)

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.

Procedure: Clear the AU-LOF Alarm


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

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


2.6.14 AU-LOP

Critical (CR), Service Affecting (SA)

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


Procedure: Clear the AU-LOP Alarm


Step 1 In the 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 will cause 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.15 AUTOLSROFF

Critical (CR), Service Affecting (SA)

The Automatic Laser Off alarm occurs when the STM-64 card temperature exceeds 90° C (194° F). The internal equipment automatically shuts down the STM-64 card 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 might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Procedure: Clear the AUTOLSROFF Alarm


Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, refer to "View Alarm Counts on the LCD for a Slot or Port" procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 2 Verify whether there is a HITEMP alarm (see page 2-91) present. If the temperature of the shelf exceeds 90° C (194° 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° C (194° 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, no additional CTC provisioning is required.


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


2.6.16 AUTORESET

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

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.

Procedure: Clear the AUTORESET Alarm


Step 1 Verify whether there are additional alarms that might have triggered an automatic reset.

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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, you do not need to change the CTC database.


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


2.6.17 AUTOSW-AIS-SNCP

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

The Automatic SNCP Switch Caused by AIS condition indicates that automatic SNCP protection switching occurred because of a TU-AIS condition (see page 2-161). The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears.

The AIS condition that caused the switch is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an AIS, for example, when the port on the reporting node is in service (IS) but a node upstream on the circuit does not have its STM-N port in service.The upstream node often reports a loss of service, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an OOS port. The AUTOSW-AIS-SNCP clears when you clear the primary alarm on the upstream node.

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


2.6.18 AUTOSW-LOP-SNCP

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

An Automatic SNCP Switch Caused by LOP alarm indicates that an automatic SNCP protection switching occurred because of an AU-LOP alarm (see page 2-28). The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears.

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


2.6.19 AUTOSW-SDBER-SNCP

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

The Automatic SNCP Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade [SD condition (see page 2-140)] 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.

Procedure: Clear the AUTOSW-SDBER-SNCP Condition


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

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


2.6.20 AUTOSW-SFBER-SNCP

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

The Automatic SNCP Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail [SF condition (see page 2-142)] 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.

Procedure: Clear the AUTOSW-SFBER-SNCP Condition


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

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


2.6.21 AUTOSW-UNEQ-SNCP (HPMON)

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

The Automatic SNCP Switch Caused by an Unequipped indicates that an HP-UNEQ alarm caused automatic SNCP protection switching to occur (see HP-UNEQ). 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 might 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.


Procedure: Clear the AUTOSW-UNEQ-SNCP (HPMON) Alarm


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

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


2.6.22 AUTOSW-UNEQ-SNCP (VCMON)

Minor (MN), Service Affecting (SA)

AUTOSW-UNEQ indicates that an LP-UNEQ alarm (see page 2-113) 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 might 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.


Procedure: Clear the AUTOSW-UNEQ-SNCP (VCMON) 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, verify 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, Verify whether there are incomplete circuits such as stranded bandwidth from circuits that were not completely deleted.

Step 5 If you find incomplete circuits, verify 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 the node view, click the Circuits tab.

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

c. If the State column lists the port as incomplete, and the incomplete does not change after a full initialization, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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 might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.

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


2.6.23 BAT-A-HGH-VLT

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

The High Volt Battery A condition occurs when the voltage level on battery lead A is between -68 VDC and -72 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains below this range for 120 seconds.

Procedure: Clear the BAT-A-HGH-VLT Condition


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

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


2.6.24 BAT-A-LOW-VLT

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

The Low Volt Battery A condition occurs when the voltage on battery feed A is low. The low voltage battery A condition occurs when the voltage on battery feed A is between -50 VDC and -55 VDC. The condition clears when voltage remains above this range for 120 seconds.

Procedure: Clear the BAT-A-LOW-VLT Condition


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

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


2.6.25 BAT-B-HGH-VLT

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

The High Volt Battery B condition occurs when the voltage level on battery lead B is between -68 VDC and -72 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains below this range for 120 seconds.

Procedure: Clear the BAT-B-HGH-VLT Condition


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

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


2.6.26 BAT-B-LOW-VLT

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

The Low Volt Battery B condition occurs when the voltage level on battery lead B is between -50 VDC and -55 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains below this range for 120 seconds.

Procedure: Clear the BAT-B-LOW-VLT Condition


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

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


2.6.27 BKUPMEMP

Critical (CR), Non-Service Affecting (NSA)

The BKUPMEMP alarm refers to a problem with the Timing Communications and Control-2 (TCC2) card Flash memory. The alarm occurs when the TCC2 card is in use and has one of four problems: the Flash manager fails to format a Flash partition, the Flash manager fails to write a file to a Flash partition, there is a problem at the driver level, or the code volume fails cyclic redundancy checking (CRC). CRC is a method to verify that no errors are in data transmitted to the TCC2 card. The BKUPMEMP alarm can also cause the EQPT alarm. In this instance, use the following procedure to clear the BKUPMEMP and the EQPT alarm.

Procedure: Clear the BKUPMEMP Alarm


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

Step 2 If both TCC2 cards are powered and enabled, reset the active TCC2 card to make the standby TCC2 card active. 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 3 If the reset TCC2 card has not rebooted successfully, or the alarm has not cleared, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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.


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


2.6.28 CARLOSS (EQPT)

Major (MJ), Service Affecting (SA)

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.

Procedure: Clear the CARLOSS (EQPT) Alarm


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

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

Step 3 If the straight-through (CAT-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 4 If you are unable to establish connectivity, replace the straight-through cable with a new known-good cable.

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


2.6.29 CARLOSS (E-Series)

Major (MJ), Service Affecting (SA)

A Carrier Loss on the LAN alarm is the data equivalent of an SDH LOS alarm (see page 2-107). 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 will clear in 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 Spanning Tree Protocol (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.

Procedure: Clear the CARLOSS (E-Series) 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, no additional CTC provisioning is required.


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.

Step 9 If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm might 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 the Select Affected Circuits dialog box 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 10 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.30 CARLOSS (G-Series)

Major (MJ), Service Affecting (SA)

A Carrier Loss on the LAN alarm is the data equivalent of an LOS alarm (see page 2-107). 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 (see page 2-158) 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. Also see the "TRMT" section 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.

Procedure: Clear the CARLOSS (G-Series) 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 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 there is no misconnection to the STM-N card, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.

Step 4 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 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 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, verify whether there are conditions that could cause autonegotiation to fail:

a. Confirm that the attached Ethernet device has auto-negotiation 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 7 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. Autonegotiation restarts.

Step 8 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 might be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.


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

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

b. Click the Conditions tab and the Retrieve Conditions button.

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

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

Step 11 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm might 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 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 12 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet card.

Step 13 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, no additional CTC provisioning is required.


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


2.6.31 CARLOSS (ML-Series)

Major (MJ), Service Affecting (SA)

A CARLOSS alarm on the ML-series Ethernet (traffic) card is the data equivalent of an LOF alarm (see page 2-103). 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

Auto-negotiation is failing

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

For information about provisioning ML-series Ethernet cards from the internal operating system (IOS) interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide.

Procedure: Clear the CARLOSS (ML-Series) 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 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 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 card using the "Perform a Facility Loopback on a Source E3-12 Port" procedure on page 1-5.

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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, no additional CTC provisioning is required.


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


2.6.32 CKTDOWN

Critical (CR), Service Affecting (SA)

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.

Procedure: Clear the CKTDOWN Alarm


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

a. In the 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 or 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 will look similar but will 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 will get the following reply 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. In the Provisioning > UCP > Neighbor tabs, click the Create button.

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

c. 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 will say 0.0.0.0.

Step 3 If neighbor discovery is enabled, make sure that the neighbor node ID, remote 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 will not allow you to delete the IPCC, you will have to delete the neighbor and recreate it. Click the Neighbor tab.

c. Click to select the neighbor and click Delete.

d. Then 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 will contain 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 condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.


2.6.33 CLDRESTART

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

The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 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.

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


2.6.34 COMIOXC

Critical (CR), Service Affecting (SA)

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 (multispeed or high-speed) slot.

Procedure: Clear the COMIOXC Alarm


Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the reporting cross connect 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 2 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

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


2.6.35 CONTBUS-A-18

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

A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 7 loses communication with the coprocessor on the second TCC2 card in Slot 11. The problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the two TCC2 cards 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.

Procedure: 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 standbyTCC2. 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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.


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


2.6.36 CONTBUS-B-18

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

A Communication Failure from TCC2 Slot toTCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 11 loses communication with the coprocessor on the TCC2 card in Slot 7. The problem is with the physical path of communication from the TCC2 card to the reporting TCC2 card. The physical path of communication includes the two TCC2 cards 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.

Procedure: 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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.


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


2.6.37 CONTBUS-IO-A

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

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

The CONTBUS-IO-A alarm might 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 other 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.

Procedure: Clear the CONTBUS-IO-A Alarm


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

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

Step 2 If the alarm object is any single card slot than the standby TCC2 card in Slot 11,perform a CTC reset of the card. Complete the "Reset a Traffic Card in CTC" procedure. Verify that the following LED activity takes place:

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 3 If the alarm object is the standby TCC2 in Slot 11, perform a soft reset of this card:

a. Right-click the Slot 11 TCC2 card.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

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

Wait ten minutes to verify that the card you reset completely reboots. Verify that the standby LED is illuminated before proceeding to the next step.

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

Step 6 If the reseated card has not rebooted successfully, or the alarm has not cleared, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


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



2.6.38 CONTBUS-IO-B

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

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

The CONTBUS-IO-B alarm might appear briefly when the ONS 15454 SDH switches to the protect TCC2 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 other 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.

Procedure: Clear the CONTBUS-IO-B Alarm


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

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

Step 2 If the alarm object is any single card slot than the standby TCC2 card in Slot 7,perform a CTC reset of the card. Complete the "Reset a Traffic Card in CTC" procedure. Verify that the following LED activity takes place:

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 3 If the alarm object is the standby TCC2 in Slot 7, perform a soft reset of this card:

a. Right-click the Slot 7 TCC2 card.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

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

Wait ten minutes to verify that the card you reset completely reboots. Verify that the standby LED is illuminated before proceeding to the next step.

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

Step 6 If the reseated card has not rebooted successfully, or the alarm has not cleared, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


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



2.6.39 CTNEQPT-PBPROT

Critical (CR), Service Affecting (SA)

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus alarm indicates a failure of the main payload between the protect cross connect card and the reporting traffic (electrical, optical, or Ethernet) card. The cross connect card and the reporting card are no longer communicating through the backplane. The problem exists in either the cross connect card, the reporting traffic card, or the backplane.


Note If all traffic cards show 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.

Procedure: 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.

While the card resets, the FAIL LED on the physical card blinks and turns off.

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

Step 2 Verify that the reset is complete and error-free.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with "Sby" has replaced the white "LDG" depiction on the card in CTC.

f the cross-connect reset is not complete and error-free or if the TCC2 card reboots itself, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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 will be 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.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

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 an External Switching Command" procedure.

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

Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the standby 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. Consult 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 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.40 CTNEQPT-PBWORK

Critical (CR), Service Affecting (SA)

The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm affects indicates a failure in the main payload bus between the active cross connect card and the reporting traffic (electrical, optical, or Ethernet) 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 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.

Procedure: 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.

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 3 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

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


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.

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.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

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


2.6.41 DATAFLT

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

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.

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


2.6.42 DBOSYNC

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

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.

Procedure: 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 the node view, click the Provisioning > General tabs.

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

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

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


2.6.43 DS3-MISM

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

The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on the DS3i-N-12 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C-BIT for a DS3i-N-12 card, and the incoming signal's frame format is detected as M13 or UNFRAMED, then the ONS 15454 SDH reports a DS3-MISM condition. The condition does not occur when the line type is set to AUTO PROVISION or UNFRAMED, so changing the line type to either of these options will clear the condition. DS3-MISM will also clear if the port state is set to OOS.

Setting the line type to AUTO PROVIS ION causes the ONS 15454 SDH to detect the received frame format and provision the port to use the matching frame format, either Unframed, M13 or C-BIT.

Procedure: Clear the DS3-MISM Condition


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

Step 2 Click the Provisioning > Line tabs.

Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the entry in the Expected Line Type column.

Step 4 If you want to change the line type because the line type entry does not match the expected incoming type, click the cell to reveal a pull-down menu and select the correct type.

Step 5 Click Apply.

Step 6 If you want to change the port state to OOS, click the Maintenance tab at the card view.

Step 7 Locate the correct port and click the State column to reveal a pull-down menu. Click OOS.

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

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

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


2.6.44 DSP-COMM-FAIL

Major (MJ), Service Affecting (SA)

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

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

If the alarm remains for an extended period, The MXP or TXP card will raise the DSP-FAIL alarm (see page 2-55).


Note If the DSP-COMM-FAIL alarm continues for an extended period, traffic could be affected.



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


2.6.45 DSP-FAIL

Major (MJ), Service Affecting (SA)

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

Procedure: Clear the DSP-FAIL Alarm


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


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

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


2.6.46 EHIBATVG-A

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

The Extreme High Voltage on Battery A alarm occurs when the voltage level on battery lead A exceeds -56.7 VDC in -48 VDC systems or -72 VDC in -60 VDC systems. The alarm indicates that the voltage on the battery lead is extremely high and power redundancy is no longer guaranteed. The alarm remains until the voltage remains below the threshold for 120 seconds.

Procedure: Clear the EHIBATVG-A Alarm


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

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


2.6.47 EHIBATVG-B

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

The Extreme High Voltage on Battery B alarm occurs when the voltage level on battery lead B exceeds -56.7 VDC in -48 VDC systems or -72 VDC in -60 VDC systems. The alarm indicates that the voltage on the battery lead is extremely high and power redundancy is no longer guaranteed. The alarm remains until the voltage remains below the threshold for 120 seconds.

Procedure: Clear the EHIBATVG-B Alarm


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

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


2.6.48 ELWBATVG-A

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

The Extreme Low Voltage on Battery Feed A alarm indicates that the voltage is extremely low or has been lost, and power redundancy is no longer guaranteed. The alarm occurs when the voltage on battery feed A drops below -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage has remained above -40.5 VDC for 120 seconds.

Procedure: Clear the ELWBATVG-A Alarm


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

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


2.6.49 ELWBATVG-B

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

The Extreme Low Voltage on Battery Feed B alarm indicates that the voltage is extremely low or has been lost, and power redundancy is no longer guaranteed. The alarm occurs when the voltage on battery feed B drops below -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage has remained above -40.5 VDC for 120 seconds.

Procedure: Clear the ELWBATVG-B Alarm


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

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


2.6.50 EOC

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

The Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 SDH loses its DCC. The DCC is three bytes, D1 through D3, in the SDH overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the section layer to communicate network management information.


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



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 might be emitted from the end of 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might 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.


Note If a circuit shows an incomplete state when the EOC alarm is raised, the logical circuit is in place, and will be able to carry traffic after the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.


Procedure: Clear the EOC Alarm


Step 1 If an LOS alarm is also reported, complete the "Clear the LOS Alarm" procedure.

Step 2 If the alarm does not clear on the reporting node, verify the physical connections between the cards and the fiber-optic cables that are configured to carry DCC traffic.

Step 3 If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have in-service (IS) ports by verifying that the ACT LED on each STM-N card is illuminated.

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

Step 5 Repeat Step 4 at the adjacent nodes.

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

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

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

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

c. Click the Provisioning > Line tabs.

Verify that the State column lists the port as IS.

If the State column lists the port as OOS, click the column and choose IS from the pull-down menu. Click Apply.

Step 7 If the STM-N card is in service, use an optical test set to verify whether or not there are signal failures on fiber terminations.

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


Caution Using an optical test might disrupt service on the STM-N card. You might have to externally switch traffic carrying circuits over to a protection path.

Step 8 If no signal failures on terminations exist, measure power levels to verify that the budget loss is within the parameters of the receiver. See the "Optical Card Transmit and Receive Levels" section on page 1-80.

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

Step 10 If fiber connectors are properly fastened and terminated, 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.


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


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

Step 11 If resetting the TCC2 card does not clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card.If the TCC2 replacement does not clear the alarm, delete the problematic DCC termination:


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

a. Click the Provisioning > DCC/GCC tabs.

b. Highlight the problematic DCC termination.

c. Click Delete.

d. Click Yes at confirmation dialog box.

Step 12 Recreate the DCC termination using the "Provision SDH DCC Terminations" procedure in the Cisco ONS 15454 SDH Procedure Guide.

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

Step 14 If the alarm has not cleared, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free 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.6.51 EQPT

Critical (CR), Service Affecting (SA)

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

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


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.

Procedure: Clear the EQPT Alarm


Step 1 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 2 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

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

Step 4 If the physical reseat of the card fails to 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, you do not need to change the CTC database.


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


2.6.52 EQPT-MISS

Critical (CR), Service Affecting (SA)

The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. EQPT-MISS indicates that the replaceable fan-tray assembly is missing or not fully inserted.


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.

Procedure: Clear the EQPT-MISS Alarm


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

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

Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the "Install the Fan-Tray Assembly" procedure in the Cisco ONS 15454 SDH Procedure Guide.

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


2.6.53 ERROR-CONFIG

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

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

The typical reasons for an errored startup file are that (1) you stored the configuration for one type of ML card in the database and then installed another type in its slot, and (2) the configuration file contained a syntax error on one of the lines.

For information about provisioning the 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.

Procedure: Clear the ERROR-CONFIG Alarm


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

Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide.

Step 2 Upload the configuration file to the TCC2:

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

b. Choose IOS Startup Config from the shortcut menu.

c. Click Upload to TCC and navigate to the file location.

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

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

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

b. Choose Open IOS Connection from the shortcut menu.


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


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

Step 5 Execute the CLI command copy run start. The command copies the new card configuration into the database and clears the alarm.

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


2.6.54 E-W-MISMATCH

Major (MJ), Service Affecting (SA)

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


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



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



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


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


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

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

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

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

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

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

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

Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span.

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


Warning On the 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 Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.

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


Procedure: Clear the E-W-MISMATCH Alarm in CTC


Step 1 Log into the misconnected node. A misconnected node has both ring fibers to its neighbor nodes misconnected.

Step 2 Click the Maintenance > MS-SPRing tabs.

Step 3 From the row of information for the fiber span, complete the "Identify a Ring ID or Node ID Number" procedure to identify the node ID, ring ID, and the slot and port in the East Line list and West Line columns. Record the above information.

Step 4 Click View > Go to Network View.

Step 5 Delete and recreate the MS-SPRING:

a. Click the Provisioning > MS-SPRing tabs.

b. Click the row from Step 3 to select it and click Delete.

c. Click Create.

d. Fill in the ring ID and node ID from the information collected in Step 3.

e. Click Finish in the MS-SPRing Creation window.

Step 6 Display the node view and click the Maintenance > MS-SPRing tabs.

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

Step 8 Change the East Line pull-down menu to the slot you recorded for the West Line in Step 3.

Step 9 Click OK.

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


2.6.55 EXCCOL

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

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

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

Procedure: Clear the EXCCOL Alarm


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

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

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


2.6.56 EXERCISE-RING-REQ

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

The Exercise Request on Ring condition occurs when optical (traffic) cards in two-fiber and four-fiber MS-SPRings are tested using the EXERCISE RING command.


Note EXERCISE-RING-REQ is an informational condition. The condition does not require troubleshooting.


2.6.57 EXERCISE-SPAN-REQ

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

The Exercise Request on Span condition occurs when optical (traffic) cards in a four-fiber MS-SPRing are tested using the EXERCISE SPAN command.


Note EXERCISE-SPAN-REQ is an informational condition. The condition does not require troubleshooting.


2.6.58 EXT

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

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

Procedure: Clear the EXT Alarm


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

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

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

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


2.6.59 EXTRA-TRAF-PREEMPT

Major (MJ), Service Affecting (SA)

An Extra Traffic Preempted alarm occurs on STM-N cards in two-fiber and four-fiber MS-SPRings because low-priority traffic directed to the protect system has been preempted by a working system protection switch.

Procedure: Clear the EXTRA-TRAF-PREEMPT Alarm


Step 1 Verify the protection switch has occurred by verify that the Conditions window shows the switch.

Step 2 If a ring switch has occurred, clear the alarm on the working system by following the appropriate alarm procedure in this chapter.

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


2.6.60 E3-ISD

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

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


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


2.6.61 FAILTOSW

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

The Failure to Switch to Protection condition occurs when a working electrical (traffic) card cannot switch to the protect card in a 1:N protection group, because another working electrical card with a higher priority alarm has switched to the protect card.

Procedure: Clear the FAILTOSW Condition


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


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


Step 2 If the condition does not clear, replace the working electrical card that is reporting the higher priority alarm by following the "Physically Replace a Card" procedure. The working card is the one that is using the 1:N card protection and is not reporting FAILTOSW.


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. Consult the Cisco ONS 15454 SDH Procedure Guide for information

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


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


2.6.62 FAILTOSW-HO

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

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

Procedure: Clear the FAILTOSW-HO Condition


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


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


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


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.63 FAILTOSW-LO

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

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

Procedure: Clear the FAILTOSW-LO Condition


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

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


2.6.64 FAILTOSWR

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

The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems.

FAILTOSWR clears when one of the following actions occurs: a higher priority event, such as an external switch command occurs, the next ring switch succeeds, or the cause of the APS switch [such as an SD condition (see page 2-140) or an SF condition (see page 2-142)] clears.


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 Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


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


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

a. Click the Provisioning > MS-SPRing tabs.

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

c. Select Exercise Ring in the pull-down menu.

Step 2 If the condition does not clear, in the node view, click View > Go to Network View.

Step 3 Look for alarms on STM-N cards that make up the ring or span and troubleshoot these alarms.

Step 4 If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node and click the Maintenance > MS-SPRing tabs.

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

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

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

Step 7 If fiber continuity to the ports is OK, verify that the correct port is in service:

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

Step 8 If the correct port is in service, use an optical test set to verify that a valid signal exists on the line.

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


Caution Using an optical test set disrupts service on the optical (traffic) card. You might have to externally switch traffic carrying circuits over to a protection path.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the STM-N card's receiver specifications. The "Optical Card Transmit and Receive Levels" section on page 1-80 lists these specifications.

Step 11 Repeat Steps 6 to 10 for any other ports on the card.

Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Card" procedure for the protect standby STM-N card.


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

Step 13 If the condition does not clear after you replace the MS-SPRing cards on the node one by one, follow
Steps 4 to 12 for each of the nodes in the ring.

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


2.6.65 FAILTOSWS

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

The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber MS-SPRing, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS condition does not appear. If the ring switch does not occur, the FAILTOSWS condition appears. FAILTOSWS clears when one of the following actions occur: a higher priority event, such as an external switch command occurs, the next span switch succeeds, or the cause of the APS switch [such as an SD condition (see page 2-140) or an SF condition (see page 2-142)] clears.

Procedure: Clear the FAILTOSWS Condition


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

a. Click the Maintenance > MS-SPRing tabs.

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

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

d. Select Exercise Span in the pull-down menu.

Step 2 If the condition does not clear, in the node view, click View > Go to Network View.

Step 3 Look for alarms on STM-N cards that make up the ring or span and troubleshoot these alarms.

Step 4 If clearing other alarms does not clear the FAILTOSWS condition, log into the near-end node and click the Maintenance > MS-SPRing tabs.

Step 5 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-N cards are active and in service (IS):

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

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

Step 7 If fiber continuity to the ports is OK, verify that the correct port is in service:

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

Step 8 If the correct port is in service, use an optical test set to verify that a valid signal exists on the line.

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


Caution Using an optical test set disrupts service on the optical (traffic) card. It might be necessary to manually switch traffic carrying circuits over to a protection path.

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the STM-N card's receiver specifications. The "Optical Card Transmit and Receive Levels" section on page 1-80 lists these specifications.

Step 11 Repeat Steps 6 to 10 for any other ports on the card.

Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Card" procedure for the protect standby STM-N card.


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

Step 13 If the condition does not clear after you replace the MS-SPRing cards on the node one by one, follow
Steps 4 to 12 for each of the nodes in the ring.

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


2.6.66 FAN

Critical (CR), Service Affecting (SA)

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15454 SDH can rise above its normal operating range. The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the ONS 15454 SDH. However, even with five working fans, the fan-tray assembly can need replacement because a sixth working fan is required for extra protection against overheating.


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.

Procedure: Clear the FAN Alarm


Step 1 Verify whether the air filter needs replacement. Complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.

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


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


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

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


2.6.67 FE-AIS

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

The Far-End AIS condition occurs when an AIS condition (see page 2-21) has occurred at the far-end node. An AIS usually occurs in conjunction with a downstream LOS alarm (see page 2-107).

Procedure: Clear the FE-AIS Condition


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

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

2.6.68 FE-DS3-NSA

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

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

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

Procedure: Clear the FE-DS3-NSA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.69 FE-DS3-SA

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

The Far End DS3i-N-12 Equipment Failure Service Affecting condition occurs when there is a far-end DS-3 equipment failure that affects service because traffic is unable to switch to the protect port.

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

Procedure: Clear the FE-DS3-SA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.70 FE-E1-MULTLOS

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

The Far End Multiple E-1 LOS Detected on an E1-42 card condition occurs when multiple inputs detect an E-1 signal loss on a far-end E1-42 port at the far-end node.The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-MULTLOS condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. Both alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-E1-MULTLOS Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.71 FE-E1-NSA

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

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

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

Procedure: Clear the FE-E1-NSA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.72 FE-E1-SA

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

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

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

Procedure: Clear the FE-E1-SA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.73 FE-E1-SNGLLOS

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

The Far End Single E-1 LOS on the E-3 condition occurs when one of the E3-12 ports on the far end detects an LOS. The prefix FE in an alarm or condition means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-SNGLLOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-E1-SNGLLOS Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.74 FE-E3-NSA

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

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

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

Procedure: Clear the FE-E3-NSA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.75 FE-E3-SA

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

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

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

Procedure: Clear the FE-E3-SA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.76 FE-EQPT-NSA

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

The Far End Common Equipment Failure condition occurs when a non-service affecting equipment failure is detected on the far-end DS-3. The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-EQPT-NSA condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. Both alarms or conditions clear when the main alarm clears.


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.

Procedure: Clear the FE-EQPT-NSA Condition


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

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

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.

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


2.6.77 FE-EXERCISING-RING

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

The Far End Exercising Ring condition occurs when far-end optical (traffic) cards in a two-fiber or four-fiber MS-SPRing are being tested using the EXERCISE RING command.The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-EXERCISING-RING condition.


Note FE-EXERCISING-RING is an informational condition. The condition does not require troubleshooting.


2.6.78 FE-EXERCISING-SPAN

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

The Far End Exercising Span condition occurs when far-end optical (traffic) cards in a four-fiber MS-SPRing are being tested using the EXERCISE SPAN command.The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-EXERCISING-SPAN condition.


Note FE-EXERCISIGN-SPAN is an informational condition. The condition does not require troubleshooting.


2.6.79 FE-FRCDWKSWPR-RING

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

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

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

Procedure: Clear the FE-FRCDWKSWPR-RING Condition


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

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

Step 3 Clear the main alarm. Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.80 FE-FRCDWKSWPR-SPAN

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

The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber MS-SPRing is forced from working to protect using the FORCE SPAN command.

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

Procedure: Clear the FE-FRCDWKSWPR-SPAN Condition


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

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

Step 3 Clear the main alarm.Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.81 FE-IDLE

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

The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal.

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

Procedure: Clear the FE-IDLE Condition


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

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

Step 3 Clear the main alarm. Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.82 FE-LOCKOUTOFPR-ALL

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

The Far End Lockout of Protection All condition occurs on far-end MS-SPRing nodes when traffic is locked on a node using the LKOUTPR-S command.

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

Procedure: Clear the FE-LOCKOUTOFPR-ALL Condition


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

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

Step 3 Make sure there is no lockout set. Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.83 FE-LOCKOUTOFPR-RING

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

The Far-End Ring Lockout of Protection condition occurs when traffic in an MS-SPRing is locked off a protection ring from the far end using the LOCKOUT RING command.

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

Procedure: Clear the FE-LOCKOUTOFPR-RING Condition


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

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

Step 3 Make sure there is no lockout set. Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.84 FE-LOCKOUTOFPR-SPAN

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

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

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

Procedure: Clear the FE-LOCKOUTOFPR-SPAN Condition


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

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

Step 3 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.85 FE-LOCKOUTOFWK-RING

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

The Far-End Lockout of Working Ring condition is raised on an MS-SPRing node when traffic is traffic at the far-end node is locked out of a working ring using the LOCKOUT-REQ-RING command.

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

Procedure: Clear the FE-LOCKOUTOFWK-RING Condition


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

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

Step 3 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.86 FE-LOCKOUTOFWK-SPAN

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

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

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

Procedure: Clear the FE-LOCKOUTOFWK-SPAN Condition


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

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

Step 3 Make sure there is no lockout set. Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.87 FE-LOF

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

The Far End LOF condition occurs when a far-end node reports a DS-3 loss of frame (LOF).

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

Procedure: Clear the FE-LOF Condition


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

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

Step 3 Complete the "Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm" procedure. The procedure also applies to FE-LOF.

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


2.6.88 FE-LOS

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

The Far End LOS condition occurs when a far-end node reports a DS-3 LOS.

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

Procedure: Clear the FE-LOS Condition


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

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

Step 3 Complete the "Clear the LOS Alarm" procedure.

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


2.6.89 FE-MANWKSWPR-RING

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

The Far End Ring Manual Switch of Working Facility to Protect condition occurs when an MS-SPRing working ring is switched from working to protect at a far-end node using the MANUAL RING command.

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

Procedure: Clear the FE-MANWKSWPR-RING Condition


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

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

Step 3 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.90 FE-MANWKSWPR-SPAN

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

The Far-End Manual Switch Span Working Facility to Protect condition occurs when an MS-SPRing span is switched from working to protect at the far-end node using the MANUAL SPAN command.

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

Procedure: Clear the FE-MANWKSWPR-SPAN Condition


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

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

Step 3 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.91 FEPRLF

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

The Far-End Protection Line Failure alarm occurs when there was an APS channel SF condition (see page 2-142) on the protect card coming into the node.


Note The FEPRLF alarm only occurs on the ONS 15454 SDH when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration.


Procedure: Clear the FEPRLF Alarm on an MS-SPRing


Step 1 To troubleshoot the FE alarm, determine which node and card is linked directly to the card reporting the FE alarm.

For example, an FE alarm or condition on a card in Slot 16 of Node 1 might relate to a main alarm from a card in Slot 16 in Node 2.

Step 2 Log into the node that is linked directly to the card reporting the FE alarm.

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for instructions.

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


2.6.92 FE-SDPRLF

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

The Far-End SD Protection Line Failure alarm occurs when there was an APS channel failure of signal on the protect card coming into the node because of signal degrade.

Procedure: Clear the FE-SDPRLF Alarm on an MS-SPRing


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

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


2.6.93 FORCED-REQ

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

The Force Switch Request on Facility or Equipment condition occurs when you enter the FORCE command on a span or card to force traffic from a working card to a protection card or vice versa. You do not need to clear this condition if you want the force switch to remain.

Procedure: Clear the FORCED-REQ Condition


Step 1 Complete the "Clear an External Switching Command" procedure.

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


2.6.94 FORCED-REQ-RING

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

The Force Switch Request Ring condition applies to optical trunk (span) cards when the FORCE RING command is applied to two-fiber and four-fiber MS-SPRings to move traffic from working to protect.

Procedure: Clear the FORCED-REQ-RING Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.95 FORCED-REQ-SPAN

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

The Force Switch Request Span condition applies to optical trunk (span) cards in four-fiber MS-SPRings when the FORCE SPAN command is applied to an MS-SPRing to force traffic from working to protect or from protect to working.

Procedure: Clear the FORCED-REQ-SPAN Condition


Step 1 Complete the "Clear an SNCP Lockout" procedure.

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


2.6.96 FRCDSWTOINT

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

The Force Switch to Internal Timing condition occurs when the user issues a FORCE command to switch to an internal timing source.


Note FRCDSWTOINT is an informational condition. The condition does not require troubleshooting.


2.6.97 FRCDSWTOPRI

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

The Force Switch to Primary Timing Source condition occurs when the user issues a FORCE command to switch to the primary timing source.


Note FRCDSWTOPRI is an informational condition. The condition does not require troubleshooting.


2.6.98 FRCDSWTOSEC

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

The Force Switch to Second Timing Source condition occurs when the user issues a FORCE command to switch to the second timing source.


Note FRCDSWTOSEC is an informational condition. The condition does not require troubleshooting.


2.6.99 FRCDSWTOTHIRD

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

The Force Switch to Third Timing Source condition occurs when the user issues a FORCE command to switch to the third timing source.


Note FRCDSWTOTHIRD is an informational condition. The condition does not require troubleshooting.


2.6.100 FRNGSYNC

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

The Free Running Synchronization Mode condition occurs when the reporting ONS 15454 SDH is in free run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the ONS 15454 SDH has lost its designated BITS timing source. After the 24-hour holdover period expires, timing slips might begin to occur on an ONS 15454 SDH relying on an internal clock.

Procedure: Clear the FRNGSYNC Condition


Step 1 If the ONS 15454 SDH is configured to operate from its internal clock, disregard this condition.

Step 2 If the ONS 15454 SDH is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards.

Step 3 Clear alarms related to the failures of the primary and secondary reference sources, such as a SYNCPRI alarm (see page 2-155) and a SYSBOOT alarm (see page 2-157).

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


2.6.101 FSTSYNC

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

A Fast Start Synchronization mode alarm occurs when the ONS 15454 SDH is choosing a new timing reference. The previous timing reference has failed.

The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


Note FSTSYNC is an informational alarm. The condition does not require troubleshooting.


2.6.102 FULLPASSTHR-BI

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

The Bidirectional Full Pass-Through Active condition occurs on a non-switching node for an MS-SPRing LSR ring when the protect channels on the node are active and carrying traffic, and there is a change in the receive K byte from No Request.

Procedure: Clear the FULLPASSTHR-BI Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.103 GCC-EOC

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

The GCC Embedded Operation Channel Failure alarm applies to the OTN communication channel for TXP and MXP cards. The GCC-EOC is raised when the channel cannot operate.

Procedure: Clear the GCC-EOC Alarm


Step 1 Complete the "Clear the EOC Alarm" procedure.

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


2.6.104 HI-LASERBIAS

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

The Equipment High Transmit Laser Bias Current alarm is raised against the TXP and MXP card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.

Laser bias typically starts at about 30% of the manufacturer's maximum laser bias specification and increases as the laser ages. So if the HI-LASERBIAS alarm threshold is set at 100% of the maximum, the laser's usability has ended. If the threshold is set at 90% of the maximum, the card is still usable for several weeks or months before it needs to be replaced.

Procedure: Clear the HI-LASERBIAS Alarm


Step 1 Complete the "Clear the LASEREOL Alarm" procedure. Replacement is not urgent and can be scheduled during a maintenance window.

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


2.6.105 HI-LASERTEMP

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

The Equipment High Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card default level by 2° C.


Note To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.


Procedure: Clear the HI-LASERTEMP Alarm


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

Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.


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

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


2.6.106 HI-RXPOWER

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

The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP or MXP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.

Procedure: Clear the HI-RXPOWER Alarm


Step 1 Find out whether gain (the amplification power) of any amplifiers has been changed. The modification will also cause channel power to need adjustment.

Step 2 Find out whether channels have been dropped from the fiber. Increasing or decreasing channels can affect power. If channels have been dropped off, the power levels of all channels will have to be adjusted.


Note If the card is part of an amplified dense wavelength multiplexing system, dropping channels on the fiber affects the transmission power of each channel more than dropping would in an unamplified system.


Step 3 At the transmit end of the errored circuit, decrease the transmit power level within safe limits.

Step 4 If neither of these problems cause the HI-RXPOWER alarm, there is a slight possibility that another wavelength is drifting on top of the alarmed signal. In this case, the receiver gets signals from two transmitters at once and data alarms would be present. If wavelengths are drifting, the data will be garbled and receive power will increase by about +3dB.

Step 5 If the alarm does not clear, add fiber attenuators to the receive ports. Start with low-resistance attenuators and use stronger ones as needed, depending on factors such as the transmission distance according to standard practice.

Step 6 If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, do a facility loopback on the transmit and receive ports with known-good loopback cable. Complete the "Perform a Facility Loopback on a Source E3-12 Port" procedure on page 1-5.

Step 7 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.


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

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


2.6.107 HI-RXTEMP

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

The Equipment High Receive temperature alarm refers to the temperature of the trunk (span) card port for the TXP and MXP cards. The HI-RXTEMP threshold is user-provisionable.

Procedure: Clear the HI-RXTEMP Alarm


Step 1 If an EXT alarm is also present, complete the "Clear the EXT Alarm" procedure.

Step 2 If a shelf HITEMP alarm is also present, complete the "Clear the HITEMP Alarm" procedure.

Step 3 If a HI-LASERTEMP alarm is also present, complete the "Clear the HI-LASERTEMP Alarm" procedure.


Note If no data alarms have occurred, the card does not need to be replaced immediately.


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


2.6.108 HITEMP

Critical (CR), Service Affecting (SA) for NE

Minor (MN), Non-Service Affecting (NSA) for EQPT

The High Temperature alarm occurs when the temperature of the ONS 15454 SDH is above 50° C (122° F).


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.

Procedure: Clear the HITEMP Alarm


Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, refer to the "View Alarm Counts on the LCD for a Slot or Port" procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 2 Verify that the environmental temperature of the room is not abnormally high.

Step 3 If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454 SDH.

Step 4 If airflow is not blocked, physically ensure that blank faceplates fill the ONS 15454 SDH empty slots. Blank faceplates help airflow.

Step 5 If faceplates fill the empty slots, verify whether the air filter needs replacement. Refer to the "Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.

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


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


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

Step 8 If the replacement fan-tray assembly does not operate correctly, log into http://www.cisco.com/tac for more information. If the alarm does not clear, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service affecting condition.


2.6.109 HI-TXPOWER

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

The Equipment High Transmit Power alarm is an indicator on the TXP card and MXP card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold. The threshold value is user-provisionable.

Procedure: Clear the HI-TXPOWER Alarm


Step 1 In the node view, display the card view for the TXP or MXP card.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Decrease (i.e. change toward the negative direction) the TX Power High column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the "Physically Replace a 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

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


2.6.110 HLDOVRSYNC

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

The Holdover Synchronization Mode alarm indicates a loss of the primary or secondary timing reference. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS  15454 SDH. HLDOVRSYNC also usually occurs during the selection of a new node reference clock. The HLDOVRSYNC alarm indicates that the ONS 15454 SDH has gone into holdover and is using the ONS 15454 SDH internal reference clock, which is a Stratum 3-level timing device. The alarm clears when primary or secondary timing is reestablished.

Procedure: Clear the HLDOVRSYNC Alarm


Step 1 Clear additional events that relate to timing, such as a FRNGSYNC condition (see page 2-87); a FSTSYNC condition (see page 2-87); a HLDOVRSYNC alarm (see page 2-92); an LOF alarm (see page 2-103); an LOS alarm (see page 2-107); a MANSWTOINT condition (see page 2-115); a MANSWTOPRI condition (see page 2-116); a MANSWTOSEC condition (see page 2-116); a MANSWTOTHIRD condition (see page 2-116); a SYSBOOT alarm (see page 2-157); a SWTOSEC condition (see page 2-154); a SWTOTHIRD condition (see page 2-154); a SYNC-FREQ (BITS, STM-N) condition (see page 2-155); a SYNCPRI alarm (see page 2-155), or a SYSBOOT alarm (see page 2-157).

Step 2 Reestablish a primary and secondary timing source according to local site practice.

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


2.6.111 HP-RFI

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

The High-Order Remote Failure Indication (RFI) condition indicates that there is a remote failure indication in the high-order (VC-4 or VC-3) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The HP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the HP-RFI condition in the reporting node.

Procedure: Clear the HP-RFI Condition


Step 1 Log into the node at the far-end node of the reporting ONS 15454 SDH.

Step 2 Verify whether there are any alarms, especially an LOS alarm (see page 2-107).

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for instructions.

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


2.6.112 HP-TIM

Minor (MN), Service Affecting (SA)

The TIM High-Order TIM Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. HP-TIM occurs when there is a mismatch between the transmitted and received J1 identifier byte in the SDH path overhead. The error can originate at the transmit end or the receive end.

Procedure: Clear the HP-TIM Alarm


Step 1 Use an optical test set capable of viewing SDH path overhead to determine the validity of the J1 byte.

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

a. Examine the signal as near to the reporting card as possible.

b. Examine the signal as close as possible to the output card.

Step 2 If the output card signal is valid, complete the "Clear the SYNCPRI Condition" procedure.

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


2.6.113 HP-UNEQ

Critical (CR), Service Affecting (SA)

The SLMF Unequipped High-Order Path unequipped alarm applies to the C2 path signal label byte in the high-order (VC-4) path overhead. HP-UNEQ occurs when no C2 byte is received in the SDH path overhead.

Procedure: Clear the HP-UNEQ Alarm


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

Step 2 Right-click the alarm to display the Select Affected Circuits dialog box.

Step 3 Click the Select Affected Circuits dialog box.

Step 4 When the affected circuits appear, look in the Type column for virtual circuit (VC).

Step 5 If the Type column does not contain VC, there are no VCs. Go to Step 7.

Step 6 If the Type column does contain VC, attempt to delete these row(s):


Note The node does not allow you to delete a valid VC.


a. Click the VC row to highlight it. Complete the "Delete a Circuit" procedure.

b. If an error message dialog box appears, the VC is valid and not the cause of the alarm.

c. If any other columns contain VT, repeat Step 6.

Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the State column of any circuits.

Step 8 If you find circuits listed as incomplete, verify these circuits are not working circuits that continue to pass traffic with an appropriate optical test set and site-specific procedures.

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

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuits procedures.

Step 11 Log back in and verify that all circuits terminating in the reporting card are active:

a. Click the Circuits tab.

b. Verify that the State column lists all circuits as active.

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


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

Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.

Step 13 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the optical and/or electrical cards.


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult 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 14 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.114 IMPROPRMVL

Critical (CR), Service Affecting (SA for active card)

The Improper Removal alarm occurs when a card is physically removed from its slot before being deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm; CTC only has to recognize that the card is not present. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node.


Note CTC gives the user approximately 15 seconds to physically remove the card before CTC begins a card reboot.



Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot.


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.

Procedure: Clear the IMPROPRMVL Alarm


Step 1 In the node view, right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.


Note CTC does not allow you to delete this card if the card is in service, has a circuit mapped, is paired in a working/protection scheme, has DCC enabled, or is used as a timing reference.


Step 3 If any ports on the card are in service, take them out of service (OOS):


Caution Before taking the a port out of service, ensure that no live traffic is present.

a. In node view, double-click the reporting card to display the card view.

b. Click the Provisioning tab.

c. Click the State column of any in-service ports.

d. Choose OOS to take the ports out of service.

Step 4 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.


Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.

Step 5 If the card is paired in a protection scheme, delete the protection group:

a. Click View > Go to Previous View to return to the node view.

b. If you are already in node view, click the Provisioning > Protection tabs.

c. Click the protection group of the reporting card.

d. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning:

a. Click the Provisioning > SDH DCC/GCC tabs.

b. Click the slots and ports listed in DCC terminations.

c. Click Delete and click Yes in the dialog box that appears.

Step 7 f the card is used as a timing reference, change the timing reference:

a. Click the Provisioning > Timing tabs.

b. Under NE Reference, click the pull-down menu for Ref-1.

c. Change Ref-1 from the listed STM-N card to Internal Clock.

d. Click Apply.

Step 8 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.

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


2.6.115 INC-ISD

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

The DS-3 Idle condition indicates that the DS-3 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has an OO-MT state. INC-ISD is resolved when the OOS state ends.


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


2.6.116 INHSWPR

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

The Inhibit Switch To Protect Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a1:N protection scheme, traffic can be switched between working cards when the switched to protect is disabled.

Procedure: Clear the INHSWPR Condition


Step 1 Complete the "Clear an External Switching Command" procedure.

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


2.6.117 INHSWWKG

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

The Inhibit Switch To Working Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked on to the protect system. If the card is part of a1:N protection scheme, traffic can be switched between protect cards when the switched to working is disabled.

Procedure: Clear the INHSWWKG Condition


Step 1 Complete the "Clear an External Switching Command" procedure.

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


2.6.118 INVMACADR

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

The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15454 SDH Media Access Control layer address (MAC Address) is invalid. The MAC Address is permanently assigned to the ONS 15454 SDH chassis during manufacture. Do not attempt to troubleshoot an INVMACADR. Log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.119 KB-PASSTHR

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

The K Bytes Pass Through Active condition occurs on a non-switching node in an MS-SPRing when the protect channels on the node are not active and the node is in K Byte Pass-Through State.

Procedure: Clear the KB-PASSTHR Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.120 LAN-POL-REV

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

The Lan Connection Polarity Reversed condition is raised by the TCC-I card when the card detects that a connected Ethernet cable has reversed receive wire pairs. The TCC-I automatically compensates for this reversal, but LAN-POL-REV stays active. The condition usually occurs during software upgrades to Release 4.0 or in new NE installations.


Caution If you upgrading from a TCC-I card to a TCC2 card, you must resolve this condition before you begin the upgrade. The TCC2 card does not compensate for reversed polarity.

Procedure: Clear the LAN-POL-REV Condition


Step 1 Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the Cisco ONS 15454 SDH Procedure Guide.

Step 2 If the condition does not clear after you replaced the cable, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.121 LASEREOL

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

The Laser Approaching End of Life alarm applies to TXP and MXP cards. It is typically accompanied by a HI-LASERBIAS alarm (see page 2-88). It is an indicator that the laser in the card will need to be replaced. How soon the replacement must happen depends upon the HI-LASERBIAS threshold. If the threshold is set under 100%, the laser replacement can usually be done during a maintenance window. But if the HI-LASERBIAS threshold is set at 100% and is accompanied by data errors, the card must be replaced sooner.

Procedure: Clear the LASEREOL 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

Log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.122 LKOUTPR-R

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

The Lockout of Protection Span condition occurs on an MS-SPRing node when traffic is locked out of a working span using the LOCKOUT SPAN command.

Procedure: Clear the LKOUTPR-R Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.123 LKOUTPR-S

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

The Lockout of Protection condition occurs on an MS-SPRing node when traffic is locked out of a protect span using the LOCKOUT SPAN command.

Procedure: Clear the LKOUTPR-S Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.124 LKOUTWK-R

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

The Lockout of Working condition occurs on a BSLR node when traffic is locked on a working ring using the LOCKOUT-REQ-RING command.

Procedure: Clear the LKOUTWK-R Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.125 LKOUTWK-S

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

The Lockout of Working condition occurs on a BSLR node when traffic is locked on a working span using the LOCKOUT-REQ command.

Procedure: Clear the LKOUTWK-S Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.126 LMP-HELLODOWN

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

The Link Management Protocol (LMP) Hello Down alarm occurs when the Hello protocol, which monitors UCP control channel status, is not available for link management. Loss of Hello protocol can occur when there are physical layer errors (such as cabling) or when there is a control channel misconfiguration.

Procedure: Clear the LMP-HELLODOWN Alarm


Step 1 Verify that transmit and receive cables are not crossed at each end (login site and neighbor site).

Step 2 Verify that a LOF alarm (see page 2-103) is not present on the source or destination nodes. If a LOF is present, complete the "Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm" procedure.

Step 3 If the alarm does not clear, complete the "Clear the CKTDOWN Alarm" procedure to verify that IPCC provisioning is valid on both ends of the UNI.

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


2.6.127 LMP-NDFAIL

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

The LMP Neighbor Detection Fail alarm occurs when neighbor detection within the unified control plane (UCP) has failed. LMP-NDFAIL can be caused by physical failure (such as cabling) between the neighbors or by control channel misconfiguration.

Procedure: Clear the LMP-NDFAIL Alarm


Step 1 Complete the "Clear the LMP-HELLODOWN Alarm" procedure.

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


2.6.128 LOCKOUT-REQ

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

The Lockout Switch Request on Facility/Equipment condition occurs when a user initiates a lockout switch request for an STM-N card or a lockout switch request on an SNCP ring at the path level. A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Procedure: Clear the LOCKOUT-REQ Condition


Step 1 Complete the "Clear an SNCP Lockout" procedure.

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


2.6.129 LOCKOUT-REQ-RING

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

The Lockout Switch Request Ring condition occurs when a LOCKOUT RING command is applied to an MS-SPRing to prevent all protection switching on the ring.

Procedure: Clear the LOCKOUT-REQ-RING Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.130 LOF (BITS)

Major (MJ), Service Affecting (SA)

The Loss of Frame (LOF) BITS alarm occurs when a port on the TCC2 BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 SDH has lost frame delineation in the incoming data.


Note The procedure assumes that the BITS timing reference signal is functioning properly and that the alarm is not appearing during node turnup.



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.

Procedure: Clear the LOF (BITS) Alarm


Step 1 Verify that the line framing and line coding match between the BITS input and the TCC2 card:

a. In the node view or card view, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.

c. Click the Provisioning > Timing tabs to display the General Timing window.

d. Verify that the value listed in Coding matches the coding of the BITS timing source (either B8ZS or AMI).

e. If the coding does not match, click the BITS-1 or BITS2 Coding and choose the appropriate coding from the pull-down menu.

f. Verify that the value listed in Framing matches the framing of the BITS timing source (either ESF or SF).

g. If the framing does not match, click the BITS-1 or BITS-2 Framing and choose the appropriate framing from the pull-down menu.


Note On the timing subtab, the binary 8-zero substitution (B8ZS) coding field is normally paired with Extended Superframe (ESF) in the Framing field, and the alternate mark inversion (AMI) coding field is normally paired with SF (D4) in the Framing field.


Step 2 If the alarm does not clear when the line framing and line coding match between the BITS input and the TCC2 card, replace the TCC2 card. 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. Consult 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.131 LOF

Critical (CR), Service Affecting (SA)

An LOF alarm means the receiving ONS 15454 SDH has lost frame delineation in the incoming data. If, in this instance, the LOF appears on the E1-42 card or the E3-12 card, the framing of the transmitting equipment might be set to a format that differs from the receiving ONS 15454 SDH.


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.

Procedure: Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm


Step 1 Verify that the line framing and line coding match between the port and the signal source:

a. In CTC, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the signal source for the card reporting the alarm. You might need to contact your network administrator for the format information.

c. Display the card view of the reporting card.

d. Click the Provisioning > Line tabs.

e. Verify that the line type of the reporting port matches the line type of the signal source.

f. If the signal source line type does not match the reporting port, click Line Type and choose the appropriate type from the pull-down menu.

g. Verify that the reporting Line Coding matches the signal source's line type.

h. If the signal source line coding does not match the reporting port, click Line Coding and choose the appropriate type from the pull-down menu.

i. Click Apply.

Step 2 If the alarm does not clear when the coding and framing of the ONS 15454 SDH match the coding and framing of the signal source, replace the card.


Note When replacing a card with an identical type of card, you do not need to change the CTC database.


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


2.6.132 LO-LASERBIAS

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

The Equipment Low Transmit Laser Bias Current alarm is raised against the TXP and MXP card laser performance. The alarm indicates that the card laser has reached the minimum laser bias tolerance.

If the LO-LASERBIAS alarm threshold is set at 0% (the default), the laser's usability has ended. If the threshold is set at 5% to10%, the card is still usable for several weeks or months before you need to replace it.

Procedure: Clear the LO-LASERBIAS Alarm


Step 1 Complete the "Clear the LASEREOL Alarm" procedure.

Replacement is not urgent and can be scheduled during a maintenance window.

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


2.6.133 LO-LASERTEMP

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

The Equipment Low Laser Optical Transceiver Temperature alarm applies to the TXP and MXP cards. LO-LASERTEMP occurs when the internally measured transceiver temperature falls 2° C under the card default level.


Note To verify the card laser temperature level, double-click the card in node view and click the Performance > Optics PM tabs. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.


Procedure: Clear the LO-LASERTEMP Alarm


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

Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.


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

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


2.6.134 LOM

Critical (CR), Service Affecting (SA)

The Loss of Multiframe alarm applies to MXP and TXP cards when the MFAS overhead field is errored for more than five frames and persists for more than three milliseconds.

Procedure: Clear the LOM Alarm


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

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


2.6.135 LO-RXPOWER

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

The Equipment Low Receive Power alarm is an indicator for TXP card and MXP card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable.

Procedure: Clear the LO-RXPOWER Alarm


Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits.

Step 2 Find out whether new channels have been added to the fiber. Up to 32 channels can be transmitted on the same fiber, but the number of channels affects power. If channels have been added, power levels of all channels need to be adjusted.


Note If the card is part of an amplified dense wavelength multiplexing system, adding channels on the fiber affects the transmission power of each channel more than adding them would in an unamplified system.


Step 3 Find out whether gain (the amplification power) of any amplifiers has been changed. A modification will also cause channel power to need adjustment.

Step 4 If the alarm does not clear, remove any receive fiber attenuators, or replace them with lower-resistance attenuators.

Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 6 If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility loopback on a known-good port. The error readings you get will not be as precise, but you will generally know whether the fiber is faulty.

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

Step 7 If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, use known-good loopback cable to complete the. "Perform a Facility Loopback on a Source E3-12 Port" procedure on page 1-5.

Step 8 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.


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

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


2.6.136 LO-RXTEMP

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

The Equipment Low Receive temperature alarm refers to the temperature of the trunk (span) card port for the TXP and MXP cards. The LO-RXTEMP threshold is user-provisionable. The alarm does not occur unless the RxTemp Low threshold is set above 0° F or C.

Procedure: Clear the LO-RXTEMP Alarm


Step 1 If this alarm accompanies other receive or transmit alarms for power, troubleshoot these alarms first.

Step 2 If the alarm does not clear, display the TXP or MXP card view.

Step 3 Click the Provisioning > Optical Thresholds tabs.

Step 4 Adjust the temperature in the Rx Temp Low column down a few degrees [amount not furnished].

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


2.6.137 LOS (BITS)

Major (MJ), Service Affecting (SA)

The LOS (BITS) alarm indicates that the TCC2 card has an LOS from the BITS timing source. An LOS (BITS) occurs when an SDH receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (BITS-N) means the BITS clock or the connection to the BITS clock failed.


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.

Procedure: Clear the LOS (BITS) Alarm


Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15454 SDH backplane to the timing source.

Step 2 If wiring is OK, verify that the BITS clock is operating properly.

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


2.6.138 LOS

Critical (CR), Service Affecting (SA)

A LOS alarm for a DS-3, E-N, or STM-N port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure or a fiber cut.


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.


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


Procedure: Clear the LOS Alarm


Step 1 Verify cabling continuity to the port.

Step 2 Verify that the correct port is in service:

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

Step 3 Use an optical test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible.

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

Step 4 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 5 If there is a valid signal, replace the electrical connector on the ONS 15454 SDH.

Step 6 Repeat Steps 1 to 5 for any other port on the card that reports the LOS.

Step 7 Look for and troubleshoot any other alarm that might identify the source of the problem.

Step 8 If there were no other alarms that might be the source of the LOS, or if clearing an alarm did not clear the LOS alarm (see page 2-107), replace the reporting card with the same type of card. 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. Consult 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 change the CTC database.


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


2.6.139 LO-TXPOWER

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

The Equipment Low Transmit Power alarm is an indicator for TXP card and MXP card transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.

Procedure: Clear the LO-TXPOWER Alarm


Step 1 Display the MXP or TXP card view.

Step 2 Click the Provisioning > Optical Thresholds tabs.

Step 3 Increase the TX Power Low column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be increased without affecting the signal, complete the "Physically Replace a 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

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


2.6.140 LPBKCRS

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

The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between a traffic (optical) card and a cross-connect card. A cross-connect loopback is a sub-line speed test that does not affect traffic.

For more information on loopbacks, see the "Identify Points of Failure on a E3-12 Circuit Path" section on page 1-4.

Procedure: Clear the LBKCRS Condition


Step 1 To remove the loopback cross-connect condition, double-click the traffic (optical) card in CTC to display the card view.

Step 2 Click the Provisioning > VC4 tabs.

Step 3 Under the XC Loopback column, deselect the check box for the port.

Step 4 Click Apply.

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


2.6.141 LPBKFACILITY (DS-3, E-N, STM-N)

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

A Loopback Facility condition occurs when a software facility loopback is active for a port on the reporting card.

For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 1-2 or the "Identify Points of Failure on a E3-12 Circuit Path" section on page 1-4.


Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopback is service-affecting.

Procedure: Clear the LPBKFACILITY (DS-3, E-N, STM-N) Condition


Step 1 In the node view, double-click the reporting card to display the card view.

Step 2 Complete the "Clear a Loopback" procedure.

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


2.6.142 LPBKTERMINAL (DS-3, E-N, STM-N)

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

A Loopback Terminal condition occurs when a software facility loopback is active for a port on the reporting card.

For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 1-2.

Procedure: Clear the LPBKTERMINAL (DS-3, E-N, STM-N) Condition


Step 1 Complete the "Clear a Loopback" procedure.

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


2.6.143 LPBKTERMINAL(G1000-4)

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

A Loopback Terminal condition occurs when a software terminal loopback is active for a port on the reporting card.

When a port in terminal loopback, its outgoing signal is redirected into the receive direction on the same port, and the externally received signal is ignored. On the G1000-4 card the outgoing signal is not transmitted; the signal is only redirected in the receive direction. G1000-4 cards only support terminal loopbacks.

For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 1-2.

Procedure: Clear the LPBKTERMINAL (G-Series) Condition


Step 1 Complete the "Clear a Loopback" procedure.

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


2.6.144 LP-PLM

Minor (MN), Service Affecting (SA)

The SLMF-PLM Low-Order Path Label Mismatch alarm applies to the V5 byte in low-order (VC-2 or VC-1) path overhead. LP-PLM occurs when there is a mismatch between the transmitted and received V5 byte received in the SDH payload overhead.

The LP-PLM alarm occurs when the optical (traffic) cards cannot detect the value of the C2 byte in the payload. The low-order C2 byte would cause the LP-PLM to occur on terminating cards.

Procedure: Clear the LP-PLM Alarm


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

a. Click the Circuits tab.

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

c. If the State column lists the port as incomplete, wait 10 minutes for the ONS 15454 SDH to initialize fully. If the incomplete state does not change after full initialization, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

Step 2 After determining the port is active, verify the signal source to the traffic (electrical) card reporting the alarm with an optical test set according to site specific practice.

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

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


Caution Deleting a circuit can affect traffic.

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

Step 5 If the circuit deletion and recreation does not clear the alarm, verify the far-end STM-N card that provides STS payload to the electrical card.

Step 6 If the alarm does not clear, verify the cross-connect between the STM-N card and the electrical card.

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

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


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult 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 http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.145 LP-RFI

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

The Low-Order RFI condition indicates that there is a remote failure indication in the low-order (VC-2 or VC-1) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The LP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the LP-RFI condition in the reporting node.

Procedure: Clear the LP-RFI Condition


Step 1 Log into the far-end node of the reporting ONS 15454 SDH.

Step 2 Verify whether there are other alarms, especially an LOS alarm (see page 2-107).

Step 3 Clear the alarms. Refer to the appropriate alarm section in this chapter for the procedure.

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


2.6.146 LP-TIM

Minor (MN), Service-Affecting (SA)

The Low-Order Path Section TIM alarm occurs when the expected J2 path trace string does not match the received string.

If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Follow the procedure below to clear either instance.

LP-TIM also occurs on a port that has previously been operating without alarms if someone switches or removes the electrical cables or optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the "LOS" alarm on page 2-107 or the LP-UNEQ alarm (see page 2-113). If these alarms accompany the TIM alarm (see page 2-158), reattach or replace the original cables/fibers to clear the alarms.

Procedure: Clear the LP-TIM Alarm


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

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


2.6.147 LP-UNEQ

Major (MJ), Service Affecting (SA)

The SLMF Unequipped Low-Order Path Unequipped alarm applies to the V5 byte in low-order (VC-2 or VC-1) path overhead. LP-UNEQ occurs when no V5 byte is received in the SDH payload overhead.

Procedure: Clear the LP-UNEQ Alarm


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

Step 2 Right-click the alarm to display the Select Affected Circuits dialog box.

Step 3 Click the Select Affected Circuits dialog box.

Step 4 When the affected circuits appear, look in the Type column for VCT, which indicates a VC tunnel Circuit. A VC tunnel with no VCs assigned might be the cause of an LP-UNEQ alarm.

Step 5 If the Type column does not contain VCT, there are no VC tunnels connected with the alarm. Go to Step 7.

Step 6 If the Type column does contain VCT, attempt to delete these row(s):


Note The node will not allow you to delete a valid VT tunnel or one with a valid VT circuit inside.


a. Click the VC tunnel circuit row to highlight it. Complete the "Delete a Circuit" procedure.

b. If an error message dialog box appears, the VC tunnel is valid and not the cause of the alarm.

c. If any other columns contain VCT, repeat Step 6.

Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the State column of any circuits.

Step 8 If you find circuits listed as incomplete, verify these circuits are not working circuits that continue to pass traffic with an appropriate optical test set and site-specific procedures.

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

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.

Step 11 Log back in and verify that all circuits terminating in the reporting card are active:

a. Click the Circuits tab.

b. Verify that the State column lists all circuits as active.

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


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

Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.

Step 13 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the optical and/or electrical cards.


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult 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 14 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.148 MAN-REQ

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

The Manual Switch Request on a Facility/Equipment condition occurs when a user initiates a manual switch request on an STM-N card or SNCP path. Clearing the manual switch clears the MAN-REQ condition.

Procedure: Clear the MAN-REQ Condition


Step 1 Complete the "Clear an SNCP Lockout" procedure.

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


2.6.149 MANRESET

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

A User-Initiated Manual Reset condition occurs when you right-click a card in CTC and choose Reset. Resets performed during a software upgrade also prompt the condition. The MANRESET condition clears automatically when the card finishes resetting.


Note MANRESET is an informational condition. The condition does not require troubleshooting.


2.6.150 MANSWTOINT

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

The Manual Switch To Internal Clock condition occurs when the NE timing source is manually switched to the internal timing source.


Note MANSWTOINT is an informational condition. The condition does not require troubleshooting.


2.6.151 MANSWTOPRI

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

The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary timing source.


Note MANSWTOPRI is an informational condition. The condition does not require troubleshooting.


2.6.152 MANSWTOSEC

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

The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to the secondary timing source.


Note MANSWTOSEC is an informational condition. The condition does not require troubleshooting.


2.6.153 MANSWTOTHIRD

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

The Manual Switch To Third Reference condition occurs when the NE timing source is manually switched to the tertiary timing source.


Note MANSWTOTHIRD is an informational condition. The condition does not require troubleshooting.


2.6.154 MANUAL-REQ-RING

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

The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on two-fiber and four-fiber MS-SPRings to switch from working to protect or protect to working.

Procedure: Clear the MANUAL-REQ-RING Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.155 MANUAL-REQ-SPAN

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

The Manual Switch Request on Ring condition occurs on four-fiber MS-SPRings when a user initiates a MANUAL SPAN command to move MS-SPRing traffic from a working span to a protect span.

Procedure: Clear the MANUAL-REQ-SPAN Condition


Step 1 Complete the "Clear an MS-SPRing Span Lock Out" procedure.

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


2.6.156 MEA (BP)

Critical (CR), Service Affecting (SA)

The Mismatch of Equipment Attributes (MEA) alarm for the backplane occurs when the revision of the backplane is incompatible with XC10G equipment.

Procedure: Clear the MEA (BP) Alarm


Step 1 If the MEA is also raised against other equipment, troubleshoot these alarms first.

Step 2 If alarms are reported directly against the XC10G card, such as SWMTXMOD, troubleshoot these alarms next.

Step 3 Determine whether the ONS 15454 SDH shelf assembly is a newer European Telecommunications Standards Institute (ETSI) 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) or an earlier shelf assembly:

a. In the node view, click the Inventory tab.

b. Under the HW Part # column, if the part number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454E-SA-ETSI).

c. Under the HW Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.

Step 4 If the shelf assembly is not compatible with 10-Gbps equipment, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.157 MEA (EQPT)

Critical (CR), Service Affecting (SA)

The MEA alarm for equipment is reported against a card slot when the physical card inserted into a slot does not match the card type that is provisioned for that slot in CTC.

Procedure: Clear the MEA Alarm


Step 1 In CTC, click the Inventory tab to reveal the provisioned card type.

Step 2 If you prefer the card type depicted by CTC, replace the physical card reporting the mismatch with the card type depicted by CTC (provisioned for that slot). 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

Step 3 If you prefer the card that physically occupies the slot and the card is not in service, has no circuits mapped, and is not part of a protection group, put the cursor over the provisioned card in CTC and right-click to choose Delete Card.

The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.


Note If the card is in service, has a circuit mapped, is paired in a working/protection scheme, has DCC communications enabled, or is used as a timing reference, CTC does not allow you to delete the card.


Step 4 If any ports on the card are in service, take them out of service (OOS):


Caution Before taking ports out of service, ensure that no live traffic.

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

b. Click the Provisioning tab.

c. Click the State column of any in-service (IS) ports.

d. Choose OOS to take the ports out of service.

Step 5 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.


Caution Before deleting the circuit, ensure that live traffic is not present.

Step 6 If the card is paired in a protection scheme, delete the protection group:

a. Click the Provisioning > Protection tabs.

b. Choose the protection group of the reporting card.

c. Click Delete.

Step 7 Right-click the card reporting the alarm.

Step 8 Choose Delete.

The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.

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


2.6.158 MEA (FAN)

Critical (CR), Service Affecting (SA)

The Mismatch of Equipment Attributes alarm is reported against the fan-tray assembly when an older ONS 15454 SDH fan-tray assembly (FTA2) is used with certain cards that require the newer fan-tray assembly (15454E-FTA-48V). The 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) and fan-tray assembly (15454E-FTA-48V) are required with the ONS 15454 SDH OC192 LR/STM64 LH 1550, E1000-2-G, E100T-G, OC48 IR/STM16 SH AS 1310, or OC48 LR/STM16 AS 1550 cards.

Procedure: Clear the MEA Alarm


Step 1 Determine whether the ONS 15454 SDH shelf assembly is a newer ETSI 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) or an earlier shelf assembly:

a. In the node view, click the Inventory tab.

b. Under the HW Part # column, if the number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454-SA-10G).

c. Under the HW Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.

Step 2 If you have a 10-Gbps-compatible shelf assembly (15454E-SA-ETSI), the alarm indicates that an older, incompatible fan-tray assembly is installed in the shelf assembly. Obtain a newer fan-tray assembly (15454-FTA3) with a 5A fuse and complete the "Replace the Fan-Tray Assembly" procedure on page 3-9.

Step 3 If you are using an earlier shelf assembly, the alarm indicates that you are using a newer fan-tray assembly (15454-FTA3), which is incompatible with the earlier version of the shelf assembly. Obtain an earlier version of the fan-tray assembly (15454-FTA2) and complete the "Replace the Fan-Tray Assembly" section on page 3-9.

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


2.6.159 MEM-GONE

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

The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC2 card. CTC will not function properly until this alarm clears. The alarm clears when additional memory becomes available.

The alarm does not require user intervention. Log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.160 MEM-LOW

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

The Free Memory of Card Almost Gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the TCC2 card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the TCC2 card is exceeded, CTC ceases to function.

The alarm does not require user intervention. Log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.161 MFGMEM

Critical (CR), Service Affecting (SA)

The Manufacturing Data Memory Failure (MFGMEM) alarm occurs if the ONS 15454 SDH cannot access the data in the electronically erasable programmable read-only memory (EEPROM). Either the memory module on the component failed or the TCC2 card lost the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. Inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.

Procedure: Clear the MFGMEM Alarm


Step 1 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. If the TCC2 card reset is not complete and error-free or if the TCC2 card reboots itself, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


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 2 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure.

Step 3 If the alarm does not clear, physically replace the standby TCC2 card on the ONS 15454 SDH with a new TCC2 card. Complete the "Physically Replace a Card" procedure.


Note The active TCC2 card takes up to 30 minutes to transfer the system software to the newly installed TCC2 card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2 card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2 card reboots and goes into standby mode after approximately three minutes.


Step 4 Reset the active TCC2 card. 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. If the TCC2 card reset is not complete and error-free or if the TCC2 card reboots itself, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

Step 5 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.

The ONS 15454 SDH boots up the second TCC2 card. The second TCC2 card must also copy the system software, which can take up to twenty minutes.

Step 6 If the MFGMEM alarm continues to report after replacing the TCC2 cards, the problem is with the EEPROM.

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


2.6.162 MFGMEM (Backplane or Fan)

Critical (CR), Service Affecting (SA)

The Manufacturing Data Memory (EEPROM) failure alarm occurs if the ONS 15454 SDH cannot access the data in the EEPROM. Lack of access occurs when either the memory module on the component fails or the TCC2 card loses the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. An inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.

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


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


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 2 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure.

Step 3 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.


Note The active TCC2 card takes up to 30 minutes to transfer the system software to the newly installed TCC2 card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2 card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2 card reboots and goes into standby mode after approximately three minutes.


Step 4 Perform a CTC reset on the TCC2 card. Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.

Step 5 Verify that the remaining TCC2 card is now in standby mode. (The ACT/STBY LED changes to amber.)

Step 6 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.

Step 7 If the MFGMEM alarm continues to report after replacing the TCC2 cards, the problem is with the EEPROM.

Step 8 If the MFGMEM is reported from the fan-tray assembly, replace the fan-tray assembly. Obtain a fan-tray assembly and complete the "Replace the Fan-Tray Assembly" procedure on page 3-9.

Step 9 If the MFGMEM is reported from backplane, or if the alarm persists after the fan-tray assembly is replaced, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.163 MS-AIS

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

The Multiplex Section AIS condition indicates that there is a defect in the multiplexing section layer of the SDH overhead. The line layer refers to the segment between two SDH devices in the circuit and is also known as a maintenance span. The line layer deals with SDH payload transport, and its functions include multiplexing and synchronization.

MS-AIS is secondary to another alarm occurring simultaneously in an upstream node. An incomplete circuit path causes an MS-AIS, for example, when the port on the reporting node is in service but the DS-3 or STM-N port on a node upstream on the circuit is not in service. The upstream node often reports a loss of service, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an OOS port. The AIS clears when you clear the primary alarm on the upstream node. However, the primary alarm node might not report any alarms that indicate a fault.

Procedure: Clear the MS-AIS Condition


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

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


2.6.164 MS-RFI

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

The Multiplex Section (MS) Remote Fault Indication (RFI) condition indicates that there is an RFI occurring at the SDH overhead multiplexing section level.

An RFI occurs when the ONS 15454 SDH detects an RFI in the SDH overhead because of a fault in another node. Resolving the fault in the adjoining node clears the MS-RFI condition in the reporting node.

Procedure: Clear the MS-RFI Condition


Step 1 Log into the far-end node of the reporting ONS 15454 SDH.

Step 2 Verify whether there are other alarms, especially an LOS alarm (see page 2-107).

Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for the procedure.

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


2.6.165 MSSP-OOSYNC

Major (MJ), Service Affecting (SA)

The Procedural Error MS-SPRing Out of Synchronization alarm occurs when you attempt to add or delete a circuit and a node on a working ring loses its DCC connection because all transmit and receive fiber has been removed. The CTC cannot generate a table of the nodes and causes the MSSP-OOSYNC alarm.


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



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


Procedure: Clear the MSSP-OOSYNC Alarm


Step 1 Reestablish cabling continuity to the node reporting the alarm.

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

Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" section.

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


2.6.166 NO-CONFIG

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

The No Startup Configuration alarm applies to ML-series Ethernet (traffic) cards and occurs when you pre-provision a high-speed slot (Slots 5-6 and 12-13) for the card without inserting the card first, or when you insert a card without pre-provisioning. (This is an exception to the usual rule in card provisioning.) Because this is normal operation, you should expect this alarm during provisioning. When the startup configuration file is copied to the active TCC2, the alarm clears.

Procedure: Clear the NO-CONFIG Alarm


Step 1 Create a startup configuration for the card in IOS.

Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide.

Step 2 Upload the configuration file to the TCC2:

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

b. Choose IOS Startup Config from the shortcut menu.

c. Click Upload to TCC and navigate to the file location.

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

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


2.6.167  NOT-AUTHENTICATED

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

The NOT-AUTHENTICATED alarm is raised by CTC (not by the NE) when it fails to log into a node. This alarm only displays in CTC where the login failure occurred.


Note NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.


2.6.168 ODUK-AIS-PM

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

The Optical Data Unit (ODUK) AIS Path Monitoring (PM) condition applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. ODUK-AIS-PM is a secondary condition that indicates a more serious condition such as an LOS alarm (see page 2-107) is occurring downstream. ODUK-AIS-PM is reported in the path monitoring area of the optical data unit wrapper overhead and is caused by a ODUK-OCI-PM condition (see page 2-126) upstream.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-AIS-PM Condition


Step 1 Verify whether the upstream nodes and equipment have alarms, especially an LOF alarm (see page 2-103) or OOS ports.

Step 2 Clear the upstream alarms using the applicable procedure(s) in this chapter.

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


2.6.169 ODUK-BDI-PM

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

The ODUK Backward Defect Indicator (BDI) PM condition applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. ODUK-BDI-PM indicates that there is a path termination error upstream in the data. The error is read as a BDI bit in the path monitoring area of the digital wrapper overhead. ODUK-BDI-PM occurs when a PORT-CODE-MISM condition (see page 2-132) occurs upstream.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-BDI-PM Condition


Step 1 Complete the "Clear the OTUK-BDI Condition" procedure.

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


2.6.170 ODUK-LCK-PM

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

The ODUK Locked Defect (LCK) PM condition applies to TXP and MXP cards when G.709 monitoring is enabled for the cards. ODUK-LCK-PM indicates that a signal is being sent downstream to indicate that the upstream connection is locked, preventing the signal from being passed. The lock is indicated by the STAT bit in the path overhead monitoring fields of the optical transport unit overhead of the digital wrapper.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-LCK-PM Condition


Step 1 Unlock the upstream node signal [needs more information].

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


2.6.171 ODUK-OCI-PM

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

The ODUK Open Connection Indication (OCI) PM condition applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. ODUK-OCI-PM indicates that the upstream signal is not connected to a trail termination source. The error is read as a STAT bit in the path monitoring area of the digital wrapper overhead. ODUK-OCI-PM causes a ODUK-AIS-PM condition (see page 2-125) downstream.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-OCI-PM Condition


Step 1 Verify that upstream nodes do not have fiber connectivity problems.

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


2.6.172 ODUK-SD-PM

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

The ODUK Signal Degrade (SD) PM condition applies to TXP cards and MXP cards when G.709 monitoring is enabled. ODUK-SD-PM indicates that incoming signal quality is poor, but the incoming line BER has not passed the fail threshold. The BER problem is indicated in the path monitoring area of the optical data unit frame overhead.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-SD-PM Condition


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

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


2.6.173 ODUK-SF-PM

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

The ODUK Signal Fail (SF) PM condition (ODUK-SD-PM) applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled. ODUK-SF-PM indicates that incoming signal quality is poor and the incoming line BER has passed the fail threshold. The BER problem is indicated in the path monitoring area of the optical data unit frame overhead.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-SF-PM Condition


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

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


2.6.174 ODUK-TIM-PM

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

The ODUK Trace Identifier Mismatch (TIM) PM condition applies to the path monitoring area of the optical transport network (OTN) overhead for TXP cards and MXP cards. ODUK-TIM-PM occurs when there is a trace identifier mismatch in the data stream. The condition causes a BKUPMEMP condition (see page 2-36) downstream.

The ODUK-TIM-PM condition applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. ODUK-TIM-PM indicates that there is an error upstream in the optical transport unit overhead of the digital wrapper.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the ODUK-TIM-PM Condition


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

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


2.6.175 OTUK-AIS

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

The Optical Transport Unit (OTUK) AIS condition applies to transponder (TXP) cards and muxponder (MXP) cards when G.709 monitoring is enabled when G.709 monitoring is enabled for the cards. The OTUK-AIS is a secondary condition that indicates a more serious condition such as an LOS alarm (see page 2-107) is occurring downstream. The OTUK-AIS is reported in the optical transport unit overhead of the digital wrapper.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-AIS Condition


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

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


2.6.176 OTUK-BDI

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

The OTUK-BDI condition applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. OTUK-BDI is indicated by the BDI bit in the section monitoring overhead. The condition occurs when there is an SF condition (see page 2-142) upstream. OTUK-BDI is triggered by a TPTFAIL (G-Series) alarm (see page 2-158).

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-BDI Condition


Step 1 Verify that the upstream nodes for an APSB condition (see page 2-21).

Step 2 In the upstream node, click the MXP or TXP card in the node view to display the card view.

Step 3 Click the Provisioning > OTN > Trail Trade Identifier tabs.

Step 4 Compare the Current Transmit String with the Current Expected String in the downstream node. (Verify that the Current Expected String is correct by making the same navigations in another CTC session to the downstream node.)

Step 5 If the two do not match, modify the Current Expected String.

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


2.6.177 OTUK-IAE

Major (MJ), Service Affecting (SA)

The OTUK Incoming Alignment Error (IAE) alarm applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. OTUK-IAE refers to a single bit that allows the input port to notify the output port that the incoming signal has an alignment error. An alignment error is indicated in the section monitoring overhead of the digital wrapper.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-IAE Alarm


Step 1 OTUK-IAE problem indicates an internal problem in the reporting card. 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information

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


2.6.178 OTUK-LOF

Critical (CR), Service Affecting (SA)

The OTUK-LOF alarm applies to TXP cards and MXP cards when G.709 monitoring is enabled for the cards. The alarm indicates that the card has lost frame delineation on the input data. Loss of frame occurs when the optical transport unit overhead frame alignment (FAS) area is errored for more than five frames and that the error persists more than three milliseconds.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-LOF Alarm


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

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


2.6.179 OTUK-SD

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

The OTUK-SD condition applies to TXP cards and MXP cards when the G.709 monitoring is enabled. The condition indicates that incoming signal quality is poor, but the incoming line BER has not passed the fail threshold. The BER problem is indicated in the optical transport unit frame overhead.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-SD Condition


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

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


2.6.180 OTUK-SF

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

The OTUK-SF condition applies to TXP cards and MXP cards when G.709 monitoring is enabled. The condition indicates that incoming signal quality is poor and that the BER for the incoming line has passed the fail threshold. The BER problem is indicated in the optical transport unit frame overhead.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-SF Condition


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

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


2.6.181 OTUK-TIM

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

The OTUK-TIM alarm applies to TXP cards and MXP cards when G.709 monitoring is enabled and section trace mode is set to manual. The alarm indicates that the expected TT1 string does not match the received TTI string in the optical transport unit overhead of the digital wrapper.

G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP and MXP cards to enable G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Clear the OTUK-TIM Alarm


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

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


2.6.182 PEER-NORESPONSE

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

The switch agent raises a Peer Card Not Responding alarm if either traffic (electrical, optical, or Ethernet) card in a protection group does not receive a response to the peer status request message. PEER-NORESPONSE is a software failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure between peer cards.

Procedure: Clear the PEER-NORESPONSE Alarm


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

While the card resets, the FAIL LED on the physical card blinks and turns off.

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

Step 2 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms window in CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with "Sby" has replaced the white "LDG" depiction on the card in CTC.

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

While the card resets, the FAIL LED on the physical card blinks and turns off.

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

Step 4 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms window in CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with "Sby" has replaced the white "LDG" depiction on the card in CTC.

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


2.6.183 PORT-CODE-MISM

Major (MJ) Non-Service Affecting (NSA)

The Pluggable Port Security Code Mismatch alarm refers to ML-series Ethernet (traffic) cards, MXPs, and TXPs. PORT-CODE-MISM occurs when the SFP connector that is plugged into the card is not supported by Cisco.

Procedure: Clear the PORT-CODE-MISM Alarm


Step 1 Unplug the SFP connector and fiber from the reporting card.

Step 2 If the SFP connector has a latch securing the fiber cable, pull the latch upward to release the cable.

Step 3 Pull the fiber cable straight out of the connector.

Step 4 Plug the fiber into a Cisco-supported SFP connector.

Step 5 If the new SFP connector has a latch, close the latch over the cable to secure it.

Step 6 Plug the cabled SFP connector into the card port until it clicks.

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


2.6.184 PORT-COMM-FAIL

Major (MJ), Service Affecting (SA)

The Port Communication Failure alarm applies to TXP and MXP card SFPs. It occurs when the card cannot communicate with the SFP.

Procedure: Clear the PORT-COMM-FAIL Alarm


Step 1 Replace the faulty SFP with a new SFP:

a. Unplug the SFP connector and fiber from the ML-series Ethernet (traffic) card.

b. If the SFP connector has a latch securing the fiber cable, pull the latch upward to release the cable.

c. Pull the fiber cable straight out of the connector.

d. Plug the fiber into a Cisco-supported SFP connector.

e. If the new SFP connector has a latch, close the latch over the cable to secure it.

f. Plug the cabled SFP connector into the ML-series Ethernet card port until it clicks.

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


2.6.185 PORT-MISMATCH

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

The Pluggable Port Mismatch alarm applies to ML-series Ethernet (traffic) card SFP connectors. The alarm indicates that the provisioned payload for the connector does not match the SFP configuration.

The error must be resolved in the IOS configuration. PORT-MISMATCH cannot be resolved in CTC. For information about provisioning the 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. If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).

2.6.186 PORT-MISSING

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

The Pluggable Port Code Missing alarm applies to ML-series Ethernet (traffic) card SFP connectors. The alarm indicates that the connector is not plugged into the card port.

For information about provisioning the 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.

Procedure: Clear the PORT-MISSING Alarm


Step 1 If fiber is not plugged into the SFP connector, plug it in.

Step 2 If the SFP connector has a latch, pull the latch over the connector.

Step 3 Push the SFP connector into the ML-series Ethernet (traffic) card port until it clicks in place.

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


2.6.187 PRC-DUPID

Major (MJ), Service Affecting (SA) for Ring

The Procedural Error Duplicate Node ID alarm indicates that two identical node IDs exist in the same ring. The ONS 15454 SDH requires each node in the ring to have a unique node ID.

Procedure: Clear the PRC-DUPID Alarm


Step 1 Log into a node on the ring.

Step 2 Find the node ID by completing the "Identify a Ring ID or Node ID Number" procedure.

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

Step 4 If two nodes have an identical node ID number, complete the "Change a Node ID Number" procedure so that each node ID is unique.

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


2.6.188 PROTNA

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

The Protection Unit Not Available alarm is caused by an OOS protection card when a TCC2 or cross-connect card that is provisioned as part of a protection group is not available. Unavailable protection can occur when a card is reset, but the alarm clears as soon as the card is back in service. The alarm clears if the device or facility is brought back in service.

Procedure: Clear the PROTNA Alarm


Step 1 If the PROTNA alarm occurs and does not clear, and if the alarm is raised against a common control card (TCC2 or XC-10G), ensure that there is a redundant control card installed and provisioned in the chassis.

Step 2 If the alarm is raised against a line card, verify whether the ports have been taken out of service (OOS):

a. In CTC, double-click the reporting card to display the card view (if the card is not a cross-connect card).

b. Click the Provisioning tab.

c. Click the State of any in-service (IS) ports.

d. Choose OOS to take the ports out of service.

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

While the card resets, the FAIL LED on the physical card blinks and turns off.

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

Step 4 Verify that the reset is complete and error-free.

No new alarms appear in the Alarms window in CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with "Sby" has replaced the white "LDG" depiction on the card in CTC.

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

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


2.6.189 PWR-A

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

The NE Power Failure at Connector A alarm applies to the NE rack. PWR-A occurs when no power is supplied to the main power connector. PWR-A alarm can occur if power is connected to the backup power connector (connector B) but not to connector A, because power must be applied to both supplies.


Warning Hazardous energy levels available at the power source and power connection. Do not bridge across battery terminals or bridge battery terminal to ground/ metal objects will heat up and can cause serious burns or weld the metal objects to the terminals.


Procedure: Clear the PWR-A Alarm


Step 1 Ensure that a power connection is present between the power source and power connector A.

Step 2 If necessary, reseat the connections between the power source and power connector A.

Step 3 If the alarm cannot be cleared, verify the continuity of the power connection with a voltmeter using the procedures in the Cisco ONS 15454 SDH Procedure Guide.

Step 4 If the alarm cannot be cleared, verify the source power output with a voltmeter following the procedures in the Cisco ONS 15454 SDH Procedure Guide.

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


2.6.190 PWR-B

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

The NE Power Failure at Connector B alarm applies to the NE rack. PWR-B occurs when no power is supplied to the backup power connector. PWR-B can occur if power is connected to the main power connector (connector A) but not to connector B, because power must be applied to both supplies.


Warning Hazardous energy level available at the power source and power connection. Do not bridge across battery terminals or bridge battery terminal to ground. Metal objects will heat up and can cause serious burns or weld the metal object to the terminals.


Procedure: Clear the PWR-B Alarm


Step 1 Ensure that a power connection is present between the power source and power connector B.

Step 2 If necessary, reseat the connections between the power source and power connector B.

Step 3 If the alarm cannot be cleared, verify the continuity of the power connection with a voltmeter using the procedures in the Cisco ONS 15454 SDH Procedure Guide.

Step 4 If the alarm cannot be cleared, verify the source power output with a voltmeter following the procedures in the Cisco ONS 15454 SDH Procedure Guide.

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


2.6.191 PWR-REDUN

Minor (MN), Non-Service Affecting

The Redundant Power Capability Lost alarm applies to cards that have two built-in fuses [such as the cross-connect and newer optical (traffic) cards]. The alarm indicates that one of the fuses has blown and must be serviced. When this alarm occurs, the card's power redundancy is lost because only one card power connection can contact one of the redundant power supplies.

Procedure: Clear the PWR-REDUN Alarm


Step 1 The card fuse is not field-replaceable. 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

Step 2 Log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to arrange a card return for service.


2.6.192 RAI

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

The Remote Alarm Indication condition signifies an end-to-end failure. The error condition is sent from one end of the SDH path to the other. RAI on the DS3XM-6 card indicates that the far-end node is receiving a DS-3 AIS condition (see page 2-21).

Procedure: Clear the RAI Condition


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

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


2.6.193 RCVR-MISS

Major (MJ), Service Affecting (SA)

A Facility Termination Equipment Receiver Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance usually occurs when a receive cable is missing from the E-1 port or a possible mismatch of backplane equipment occurs, for example, an SMB connector or a BNC connector is connected to an E-1 card.


Note DS-1s are four-wire circuits and need a positive (tip) and negative (ring) connection for both transmit and receive.



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.

Procedure: Clear the RCVR-MISS Alarm


Step 1 Ensure that the device attached to the E-1 port is operational.

Step 2 If the attachment is OK, verify that the cabling is securely connected.

Step 3 If the cabling is OK, verify that the pinouts are correct.

Step 4 If the pinouts are correct, replace the receive cable.

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


2.6.194 RFI

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

sonet] A Remote Fault Indication condition occurs when the ONS 15454 SDH detects an RFI in the SDH overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI condition in the reporting node. RFI indicates that the condition is occurring at the line level.

Procedure: Clear the RFI Condition


Step 1 Log into the node at the far-end node of the reporting ONS 15454 SDH.

Step 2 Verify whether there are other alarms, especially an LOS alarm (see page 2-107).

Step 3 Clear alarms, especially LOS, by referring to the LOS sections as appropriate.

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


2.6.195 RING-MISMATCH

Major (MJ), Service Affecting (SA)

A Procedural Error Mismatched Ring alarm occurs when the ring ID of the ONS 15454 SDH that is reporting the alarm does not match the ring ID of another ONS node in the MS-SPRing. ONS nodes connected in an MS-SPRing must have identical ring IDs to function.

Procedure: Clear the RING-MISMATCH Alarm


Step 1 Log into the first node in the ring.

Step 2 Verify the ring ID. Complete the "Identify a Ring ID or Node ID Number" procedure.

Step 3 Note the number in the Ring ID field.

Step 4 Log into the next ONS node in the MS-SPRing.

Step 5 Verify the ring ID. Complete the "Identify a Ring ID or Node ID Number" procedure.

Step 6 If the ring ID matches the ring ID in the reporting ONS node, repeat Step 5 for the next ONS node in the MS-SPRing.

Step 7 Complete the "Change a Ring ID Number" procedure.

Step 8 Verify that the ring map is correct.

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


2.6.196 RING-SW-EAST

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

The Ring Switch is Active on the East Side condition occurs when a manual ring switch occurs at the east side of a two-fiber MS-SPRing. The condition clears when the switch is cleared.


Note RING-SW-EAST is an informational condition. The condition does not require troubleshooting.


2.6.197 RING-SW-WEST

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

The Ring Switch is Active On the West Side condition occurs when a manual ring switch occurs at the west side of a two-fiber MS-SPRing. The condition clears when the switch is cleared.


Note RING-SW-WEST is an informational condition. The condition does not require troubleshooting.


2.6.198 RSVP-HELLODOWN

Minor (NA), Non-Service Affecting (NSA)

The Resource Reservation Protocol (RSVP) Hello Down alarm occurs when the Hello protocol, which monitors UCP control channel status, is not available for reserving resources. The Hello protocol can become unavailable because of a misconfiguration or loss of connectivity between the reporting node and its neighbor.

Procedure: Clear the RSVP-HELLODOWN Alarm


Step 1 Ensure that there are no physical layer problems between the reporting node and its neighbor.

Step 2 Ensure that neighbor discovery (if enabled) has completed without any errors:

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

b. Look for the neighbor ID and address. If the ID is present, neighbor discovery is working.

Step 3 Ensure that RSVP hello is enabled on the neighbor node:

a. In the node view, click View > Go to Network View.

b. Double-click the neighbor node in the network map.

c. Click the Provisioning > UCP > Node tabs on this neighbor.

d. Ensure that the RSVP area of the window contains entries in the Restart Time, Retransmit Interval, Recovery Time, and Refresh Interval fields.

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


2.6.199 RUNCFG-SAVENEED

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

The Run Configuration Save Needed condition occurs when you change the running configuration file for ML1000 and ML100T cards. RUNCFG-SAVENEED is a reminder that you must save the change to the startup configuration file permanently.

The condition clears after you save the running configuration to the startup configuration, such as by entering "copy run start" at the CLI. If you do not save the change, the change is lost after the card reboots.

2.6.200 SD

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

A Signal Degrade (SD) condition occurs on optical STM-N lines and the low-order path termination when the quality of the signal is so poor that the bit error rate (BER) on the incoming optical line passed the signal degrade threshold. Signal degrade is defined by the ITU as a "soft failure" condition. SD and signal failure (SF) both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF.

An SD condition occurs for STM-N cards and the low-order path termination when the BER on the incoming optical line has passed the signal failure threshold in the range of 10-9 to 10-5. For unprotected circuits, the BER threshold value is not user-provisionable and the error rate is set to a GR253 specification of 10-6.

The SD condition travels on the B2 byte of the multiplexing section SDH overhead. The condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.


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



Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might 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 lower-right outside edge of the shelf assembly.

Procedure: Clear the SD Condition


Step 1 Verify that the user-provisionable BER threshold is set at the expected level. Complete the "Verify BER Threshold Level" procedure.

Step 2 With an optical test set, measure the power level of the line to ensure the power is within guidelines.

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

Step 3 Verify that optical receive levels are within the acceptable range.

Step 4 If the receive levels are out of range, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 5 Verify that single-mode fiber is used.

Step 6 Verify that a single-mode laser is used at the far-end node.

Step 7 If the problem persists, the transmitter at the other end of the optical line might be failing and require replacement.

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


2.6.201 SDBER-EXCEED-HO

Not Alarmed (NA), Service Affecting (SA) for HPMON

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

The Signal Degrade Threshold Exceeded for High Order condition indicates that the signal degrade BER threshold has been exceeded for a high-order (VC-4) path on optical (traffic) cards. SDBER-EXCEED-HO occurs when the signal BER falls within the degrade threshold (typically 1E-7 dB) set on the node.


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



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


Procedure: Clear the SDBER-EXCEED-HO Condition


Step 1 Determine the BER threshold. Complete the "Verify BER Threshold Level" procedure.

Step 2 If adjustment is acceptable in site practices, adjust the threshold.

Using an optical test set, measure the input power level of the line and ensure the level is within the guidelines.

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

Step 3 Verify the input fiber cable connections to the reporting card.

Step 4 Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

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


2.6.202 SF

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

A Signal Failure (SF) condition occurs on optical STM-N cards and the low-order path termination when the BER on the incoming optical line has passed the signal failure threshold in the range of 10-5 to 10-3. The condition travels on the B2 byte of the multiplexing section SDH overhead; this condition causes a protection switch at the line (facility) level.

The SF condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

Signal failure is defined by the ITU as a "hard failure" condition. SD and SF both monitor the incoming BER error rate and are similar alarms, but SF is triggered at a higher BER than SD.


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



Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might 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 lower-right outside edge of the shelf assembly.

Procedure: Clear the SF Condition


Step 1 Verify that the user-provisionable BER threshold is set at the expected level. Complete the "Verify BER Threshold Level" procedure.

Step 2 Using an optical test set, measure the power level of the line and ensure the level is within the guidelines.

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

Step 3 Verify that optical receive levels are within the acceptable range.

Step 4 Clean the fibers at both ends according to site practice for a line signal failure. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

Step 5 Verify that single-mode fiber is being used.

Step 6 Verify that a single-mode laser is being used at the far-end node.

Step 7 If the problem persists, the transmitter at the other end of the optical line might be failing and need replacement.

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


2.6.203 SFBER-EXCEED-HO

Not Alarmed (NA), Service Affecting (SA) for HPMON

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

The Signal Failure Threshold Exceeded for High Order condition occurs when the signal fail BER threshold has been exceeded for a high-order (VC-4 or VC-3) path on optical (traffic) cards. SFBER-EXCEED-HO occurs when the signal BER falls past the fail threshold (typically 1E-4 dB) set on the node.


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



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


Procedure: Clear the SFBER-EXCEED-HO Condition


Step 1 Determine the BER threshold by clicking the card reporting the condition, and clicking the Provisioning tab.

Step 2 If adjustment is acceptable in site practices, adjust the threshold.

Step 3 Verify the input power levels to the reporting card.

Step 4 Verify input fiber cable connections to the reporting card.

Step 5 Clean the input fiber cable ends according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.

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


2.6.204 SFTWDOWN

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

A Software Download in Progress alarm occurs when the TCC2 card is downloading or transferring software.

No action is necessary. Wait for the transfer or the software download to complete. If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


Caution Updating software on a standby TCC2 card can take up to 30 minutes. Wait the full time period before removing the card. Premature removal can cause Flash corruption.


Note SFTWDOWN is an informational alarm and does not require troubleshooting.


2.6.205 SNTP-HOST

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

The Simple Network Time Protocol (SNTP) host failure alarm indicates that an ONS node serving as an IP proxy for the other ONS nodes in the ring is not forwarding SNTP information to the other ONS nodes in the network. The host failure can result from two causes: the IP network attached to the ONS proxy node is experiencing problems, or the ONS proxy node itself is not functioning properly.

Procedure: Clear the SNTP-HOST Alarm


Step 1 Ping the SNTP host from a workstation in the same subnet to ensure that communication is possible within the subnet.

Step 2 If the ping fails, contact the network administrator that manages the IP network that supplies the SNTP information to the proxy and determine whether the network is experiencing problems which might affect the SNTP server/router connecting to the proxy ONS 15454 SDH.

Step 3 Ensure that the ONS 15454 SDH is provisioned correctly:

a. In node view of the ONS node serving as the proxy, click the Provisioning > General tabs.

b. Ensure the Enable Proxy check box is checked.

c. If the Enable Proxy check box is not checked, select this box to check it.

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


2.6.206 SPAN-SW-EAST

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

The Span Switch is Active on the East Side condition occurs when a span switch occurs at the east side of a four-fiber MS-SPRing span. The condition clears when the switch is cleared.


Note SPAN-SW-EAST is an informational condition. The condition does not require troubleshooting.


2.6.207 SPAN-SW-WEST

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

The Span Switch is Active on the West Side condition occurs when a span switch occurs at the west side of a four-fiber MS-SPRing span. The condition clears when the switch is cleared.


Note SPAN-SW-WEST is an informational condition. The condition does not require troubleshooting.


2.6.208 SQUELCH

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

The Ring Squelching Traffic condition occurs in an MS-SPRing when a node that originates or terminates STS circuits fails or is isolated by multiple fiber cuts or maintenance FORCE RING commands. The isolation or failure of the node disables the circuits that originate or terminate on the failed node. Squelch conditions appear on one or both of the nodes on either side of the isolated/failed node. The AU-AIS condition also appears on all nodes in the ring, except the isolated node.


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.


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



Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Procedure: Clear the SQUELCH Condition


Step 1 Determine the isolated node:

a. Display the CTC network view.

b. The dimmed node with red spans is the isolated node.

Step 2 Verify fiber continuity to the ports on the isolated node.

Step 3 Verify that the proper ports are in service:

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

Step 4 Use an optical test set to verify that a valid signal exists on the line.

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

Test the line as close to the receiving card as possible.

Step 5 Verify that the power level of the optical signal is within the optical (traffic) card's receiver specifications. Refer to the Cisco ONS 15454 SDH Reference Manual for card specifications.

Step 6 Ensure that the optical transmit and receive fibers are connected properly.

Step 7 Replace the STM-N card. 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

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


2.6.209 SQUELCHED

Major (MJ), Service Affecting (SA)

The DWDM Client Signal Squelched alarm is raised by an MXP or TXP card when G.709 monitoring is enabled and the card is operating in transparent mode. The alarm occurs on a far-end MXP or TXP client port when the near end detects anLOF alarm (see page 2-103) or LOS alarm (see page 2-107). The signal loss is indicated by an OTUK-AIS condition (see page 2-128) in the OTN overhead. SQUELCHED can also indicate that the far-end trunk signal is invalid.

Procedure: Clear the SQUELCHED Alarm


Step 1 Verify that the far-end node and near-end node are not reporting an LOF alarm (see page 2-103) or an LOS alarm (see page 2-107). If so, complete the "Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm" procedure.

Step 2 If no LOF or LOS is reported, verify that the far-end node and near-end are not reporting a trunk WVL-MISMATCH alarm (see page 2-162) or DSP-FAIL alarm (see page 2-55). If either alarm is reported, complete the "Clear the WVL-MISMATCH alarm" procedure or the "Clear the DSP-FAIL Alarm" procedure as appropriate.

Step 3 If no WVL-MISMATCH or DSP-FAIL is reported, verify that the near-end port reporting the SQUELCHED alarm is not out of service (OOS) or in loopback:

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

b. Click the Maintenance > Loopback tabs.

c. If the Port State column says OOS or OOS_MT, click the cell to highlight it and choose IS from the pull-down menu. Changing the state to IS will also clear any loopback provisioned on the port.

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


2.6.210 SQUELCH-PATH

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

The Ring Squelching Traffic condition occurs in an MS-SPRing when a node that originates or terminates STS circuits fails or is isolated by multiple fiber cuts or maintenance force ring commands. The isolation or failure of the node disables the circuits that originate or terminate on the failed node. Squelch alarms appear on one or both of the nodes on either side of the isolated/failed node. The AU-AIS condition (see page 2-27) also appears on all nodes in the ring, except the isolated node.


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.


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



Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.


Procedure: Clear the SQUELCH-PATH Alarm


Step 1 Determine the isolated node:

a. Display the CTC network view.

b. The dimmed node with red spans is the isolated node.

Step 2 Verify fiber continuity to the ports on the isolated node.

Step 3 Verify that the proper ports are in service:

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

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

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

c. Click the Provisioning > Line tabs.

d. Verify that the State column lists the port as IS.

e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.

Step 4 Use an optical test set to verify that a valid signal exists on the line.

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

Test the line as close to the receiving card as possible.

Step 5 Verify that the power level of the optical signal is within the optical (traffic) card's receiver specifications. Refer to the Cisco ONS 15454 SDH Reference Manual for card specifications.

Step 6 Ensure that the optical transmits and receives are connected properly.

Step 7 Replace the STM-N card. 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.

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


2.6.211 SSM-DUS

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

The Synchronization Status Messaging (SSM) Quality level Changed to Do Not Use (DUS) occurs when the synchronization status message (SSM) quality level degrades to DUS or is manually changed to DUS.

The signal is often manually changed to DUS to prevent timing loops from occurring. Sending a DUS prevents the timing from being reused in a loop. SSM-DUS can also be sent for line maintenance testing.


Note SSM-DUS is an informational condition alarm. The condition does not require troubleshooting.


2.6.212 SSM-FAIL (BITS)

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

The SSM Failed BITS alarm occurs when the synchronization status messaging (SSM) byte (S1 byte) of the SDH overhead multiplexing section received by the ONS 15454 SDH has failed. The problem is external to ONS 15454 SDH. The ONS 15454 SDH is set up to receive SSM, but the timing source is not delivering valid SSM messages.

Procedure: Clear the SSM-FAIL (BITS) Alarm


Step 1 Verify that SSM is enabled on the external timing source.

Step 2 Use an optical test set to determine that the external timing source is delivering the SSM (S1) byte.

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

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


2.6.213 SSM-FAIL (STM-N)

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

The SSM Failed STM-N alarm occurs when the SSM byte (S1 byte) of the SDH overhead multiplexing section received by the ONS 15454 SDH has failed. The problem is external to ONS 15454 SDH. The ONS 15454 SDH is set up to receive SSM, but the timing source is not delivering valid SSM messages.

Procedure: Clear the SSM-FAIL (STM-N) Alarm


Step 1 Verify that SSM is enabled on the external timing source.

Step 2 Use an optical test set to determine that the external timing source is delivering the SSM (S1) byte.

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

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


2.6.214 SSM-LNC

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

The SSM Local Node Clock (LNC) Traceable condition occurs when the SSM (S1) byte of the SDH overhead multiplexing section has been changed to signify that the line or BITS timing source SSM quality level is G812L.


Note SSM-LNC is an informational condition. The condition does not require troubleshooting.


2.6.215 SSM-OFF (BITS)

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

The SSM Off BITS condition applies to references used for timing the node. SSM-OFF occurs when the SSM (S1) byte of the SDH overhead multiplexing section for this reference has been turned off. The ONS 15454 SDH is set up to receive SSM, but the timing source is not delivering SSM messages.

SSM is an SDH protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

To clear the condition, complete the "Clear the SSM-FAIL (BITS) Alarm" procedure. If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.216 SSM-OFF (STM-N)

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

The SSM Off STM-N condition indicates that the SSM (S1) byte of the SDH multiplexing section overhead has been turned off. SSM-OFF applies to optical trunk (span) cards. The alarm occurs when SSM is off. The ONS 15454 SDH is set up to receive SSM, but the timing source is not delivering SSM messages.

SSM is an SDH protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

To clear the condition, complete the "Clear the SSM-FAIL (BITS) Alarm" procedure. If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.217 SSM-PRC

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

The SSM Primary Reference Clock (PRC) Traceable condition occurs when the SDH overhead multiplexing section S1 byte indicates that the line or BITS timing source SSM quality level is G811.


Note SSM-PRC is an informational condition. The condition does not require troubleshooting.


2.6.218 SSM-SETS

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

The SSM Synchronous Equipment Timing Source (SETS) Traceable condition occurs when the SSM (S1) byte indicates that the line or BITS timing source has changed to SETS.


Note SSM-SETS is an informational condition. The condition does not require troubleshooting.


2.6.219 SSM-STU (BITS)

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

The SSM Synchronization Traceability Unknown (STU) BITS condition occurs when the reporting node is timed to a reference that does not report the SSM S1 byte, but the ONS 15454 SDH has SSM support enabled. STU also occurs if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15454 SDH.

Procedure: Clear the SSM-STU (BITS) Condition


Step 1 Click the Provisioning > Timing tabs.

Step 2 If the Sync Messaging check box is checked, uncheck it.

Step 3 If the Sync Messaging check box is unchecked, check it.

Step 4 Click Apply.

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


2.6.220 SSM-STU (STM-N)

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

The SSM STU STM-N condition occurs when the reporting node is timed to a reference that does not report the SSM S1 byte, but the ONS 15454 SDH has SSM support enabled. STU can also occur if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15454 SDH.

Procedure: Clear the SSM-STU (STM-N) Condition


Step 1 Click the Provisioning > Timing tabs.

Step 2 If the Sync Messaging check box is checked, uncheck it.

Step 3 If the Sync Messaging check box is unchecked, check it.

Step 4 Click Apply.

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


2.6.221 SSM-TNC (BITS)

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

The SSM Transit Node Clock (TNC) Traceable BITS condition occurs when the SSM quality level is changed to G812T.


Note SSM-TNC is an informational condition. The condition does not require troubleshooting.


2.6.222 SSM-TNC (STM-N)

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

The SSM TNC Traceable STM-N condition occurs when the SSM quality level is changed to G812T.


Note SSM-TNC is an informational condition. The condition does not require troubleshooting.


2.6.223 SWMTXMOD

Critical (CR), Service Affecting (SA)

The Switching Matrix Module Failure alarm occurs on the cross connect card or a traffic (electrical, optical, or Ethernet) card. If the alarm reports against a traffic card, the logic component on the cross connect card is out of frame (OOF) with the logic component on the reporting traffic card. All traffic on the reporting traffic card is lost. If the alarm reports against a cross connect card, a logic component internal to the reporting cross connect card is out of frame with a second logic component on the same cross connect card. One or more traffic cards might lose traffic as a result of this failure.

Procedure: Clear the SWMTXMOD Alarm


Step 1 If the card reporting the alarm is the standby cross connect card, perform a CTC reset on the standby cross connect. Complete the "Reset a Traffic Card in CTC" procedure.

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 2 Verify that the CTC reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 3 If the alarm persists, physically reseat the standby cross connect card. Complete the "Remove and Reinsert (Reseat) a Card" procedure.

Step 4 If the card reporting the alarm is the active cross connect card, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to move traffic from the active cross connect card to the standby cross connect card.


Note After the active cross-connect goes into standby, the original standby slot becomes active. The active card ACT/STBY LED becomes green.


Step 5 If the card reporting the alarm is not the active cross connect card or if you completed the side switch in Step 4, perform a CTC reset on the reporting card. Complete the "Reset a Traffic Card in CTC" procedure.

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 6 Verify that the CTC reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 7 If the alarm persists, physically reseat the standby cross connect card. Complete the "Remove and Reinsert (Reseat) a Card" procedure.

Step 8 If the card reporting the alarm is a traffic (electrical, optical, or Ethernet) card, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to move traffic from the active cross connect card to the standby cross connect card.

Step 9 If the alarm does not clear after the cross connect side switch, perform a CTC reset on the reporting card. Complete the "Reset a Traffic Card in CTC" procedure.

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 10 Verify that the CTC reset is complete and error-free.

No new alarms appear in the Alarms tab on CTC.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED is illuminated.

If you are looking at the node view of the ONS 15454 SDH, an amber LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 11 If the alarm persists, physically reseat the reporting traffic card. Complete the "Remove and Reinsert (Reseat) a Card" procedure.

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


2.6.224 SWTOPRI

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

The Synchronization Switch to Primary Reference condition occurs when the ONS 15454 SDH switches to the primary timing source (reference 1). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.


Note SWTOPRI is an informational condition. The condition does not require troubleshooting.


2.6.225 SWTOSEC

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

The Synchronization Switch to Secondary Reference condition occurs when the ONS 15454 SDH has switched to the secondary timing source (reference 2). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.

To clear the condition, clear alarms related to failures of the primary source, such as the SYNCPRI alarm (see page 2-155). If the condition does not clear, Lloyd into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.226 SWTOTHIRD

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

The Synchronization Switch to Third Reference condition occurs when the ONS 15454 SDH has switched to the third timing source (reference 3). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.

To clear the condition, clear alarms related to failures of the primary source, such as the SYNCPRI alarm (see page 2-155) and SYSBOOT alarm (see page 2-157). If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.

2.6.227 SYNC-FREQ (BITS, STM-N)

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

The Synchronization Reference Frequency Out Of Bounds condition is reported against any reference that is out of the bounds for valid references. The NE will fail this reference and choose another reference or internal to run on.

Procedure: Clear the SYNC-FREQ (BITS, STM-N) Condition


Step 1 Use an optical test set to verify the timing frequency of the line or BITS timing source and ensure that that timing falls within the proper frequency.

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

For BITS, the proper timing frequency range is approximately -15 PPM to 15 PPM. For optical line timing, the proper frequency range is approximately -16 PPM to 16 PPM.

Step 2 If the reference source frequency is not out of bounds, replace the TCC2 card. Complete the "Physically Replace a Card" procedure.

Step 3 If the SYNC-FREQ condition continues to report after replacing the TCC2 card, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


2.6.228 SYNCPRI

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

A Loss of Timing on Primary Reference alarm occurs when the ONS 15454 SDH loses the primary timing source (reference 1). The ONS 15454 SDH uses three ranking timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the ONS 15454 SDH should switch to its secondary timing source (reference 2). The timing switch also triggers the SWTOSEC alarm (see page 2-154).

Procedure: Clear the SYNCPRI Condition


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

Step 2 Verify the current configuration for the REF-1 of the NE reference.

Step 3 If the primary reference is a BITS input, verify the wiring connection from the ONS 15454 SDH backplane BITS clock pin fields to the timing source.

Step 4 Verify that the BITS clock is operating properly.

Step 5 If the primary reference clock is an incoming port on the ONS 15454 SDH, complete the "Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm" procedure.

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


2.6.229 SYNCSEC

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

A Loss of Timing on Secondary Reference alarm occurs when the ONS 15454 SDH loses the secondary timing source (reference 2). The ONS 15454 SDH uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCSEC occurs, the ONS 15454 SDH should switch to the third timing source (reference 3) to obtain valid timing for the ONS 15454 SDH. The timing switch also triggers the SWTOTHIRD alarm (see page 2-154).

Procedure: Clear the SYNCSEC Alarm


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

Step 2 Verify the current configuration of the REF-2 for the NE Reference.

Step 3 If the secondary reference is a BITS input, verify the wiring connection from the ONS 15454 SDH backplane BITS clock pin fields to the timing source.

Step 4 Verify that the BITS clock is operating properly.

Step 5 If the secondary timing source is an incoming port on the ONS 15454 SDH, complete the "Clear the LOS (BITS) Alarm" procedure.

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


2.6.230 SYNCTHIRD

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

A Loss of Timing on Third Reference alarm occurs when the ONS 15454 SDH loses the third timing source (reference 3). The ONS 15454 SDH uses three ranking timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCTHIRD occurs and the ONS 15454 SDH uses an internal reference for source three, then the TCC2 card might have failed. The ONS 15454 SDH often reports either a FRNGSYNC condition (see page 2-87) or a HLDOVRSYNC alarm (see page 2-92) after a SYNCTHIRD alarm.


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

Procedure: Clear the SYNCTHIRD Alarm


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

Step 2 Verify the current configuration of the REF-3 for the NE Reference. For more information about references, refer to the Cisco ONS 15454 SDH Procedure Guide.

Step 3 If the third timing source is a BITS input, complete the "Clear the LOS (BITS) Alarm" procedure.

Step 4 If the third timing source is an incoming port on the ONS 15454 SDH, complete the "Clear the LOF (DS-3, DS-3, E-N, or STM-N) Alarm" procedure.

Step 5 If the third timing source uses the internal ONS 15454 SDH timing, perform a CTC reset on the TCC2 card. 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. If the TCC2 card reset is not complete and error-free or if the TCC2 card reboots itself, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.


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 this fails to clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure.

Step 7 If the CTC reset fails to clear the alarm, replace the TCC2 card. Complete the "Physically Replace a Card" procedure.


Note When replacing a card with an identical type of card, you do not need to change the CTC database.


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


2.6.231 SYSBOOT

Major (MJ), Service Affecting (SA)

The System Reboot alarm indicates that new software is booting on the TCC2 card. SYSBOOT is an informational alarm.

No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 30 minutes. If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


Note SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.


2.6.232 TIM

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

The Regenerator Section Trace Identifier Mismatch (TIM) occurs when the expected J1 path trace string does not match the received string.

If the condition occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Follow the procedure below to clear either instance.

TIM also occurs on a port that has previously been operating without alarms if someone switches or removes the DS-3 cables or optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as an LOS alarm (see page 2-107) or an HP-UNEQ alarm (see page 2-94). If these alarms accompany TIM, reattach or replace the original cables/fibers to clear the alarms.

Procedure: Clear the TIM Condition


Step 1 Log into the circuit source node and click the Circuits tab.

Step 2 Select the circuit reporting the condition, then click Edit.

Step 3 In the Edit Circuit window, check the Show Detailed Map box.

Step 4 On the detailed circuit map, right-click the source circuit port and choose Edit J1 Path Trace (port) from the shortcut menu.

Step 5 On the detailed circuit map, right-click the drop/destination circuit port and choose Edit Path Trace from the shortcut menu.

Step 6 Compare the Current Transmit String and the Current Expected String entries in the Edit J1 Path Trace dialog box.

Step 7 If the strings differ, correct the Transmit or Expected strings and click Apply.

Step 8 Click Close.

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


2.6.233 TPTFAIL (G-Series)

Major (MJ), Service Affecting (SA)

The Transport (TPT) Layer Failure alarm indicates a break in the end-to-end Ethernet link integrity feature of the G1000-4 cards. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.

The TPTFAIL alarm indicates a problem on either the SDH path or the remote Ethernet port that prevents the complete end-to-end Ethernet path from working. If any SDH path alarms such as an AU-AIS condition (see page 2-27), an AU-LOP alarm (see page 2-28) or an HP-UNEQ alarm (see page 2-94) exist on the SDH path used by the Ethernet port, the affected port causes a TPTFAIL alarm. Also, if the far-end G1000-4 Ethernet port is administratively disabled or the port is reporting a CARLOSS (G-Series) alarm (see page 2-39), the C2 byte in the SDH path overhead causes a TPTFAIL to be reported against the near-end port.

When a TPTFAIL alarm occurs, the near-end port is automatically disabled (transmit laser turned off). In turn the laser shutoff can also cause the external Ethernet device attached at the near end to detect a link down and turn off its transmitter. This also causes a CARLOSS condition to occur on the reporting port. In all cases the source problem is either in the SDH path being used by the G1000-4 port or the far- end G1000-4 port to which it is mapped.

Procedure: Clear the TPTFAIL (G-Series) Alarm


Step 1 An occurrence of TPTFAIL on a G1000-4 port indicates either a problem with the SDH path that the port is using or with the far end G1000-4 port that is mapped to the port. Clear any alarms being reported by the STM-N card on the G1000-4 circuit.

Step 2 If no alarms are reported by the STM-N card, the problem might be on the far-end G1000-4 port. Clear any alarms, such as CARLOSS, reported against the far-end port or card.

Step 3 If the alarm does not clear, log into http://www.cisco.com/tac to obtain information about handling the failed card or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.234 TPTFAIL (ML-Series)

Major (MJ), Service Affecting (SA)

The TPT Layer Failure alarm indicates a break in the end-to-end POS link integrity feature of the ML-series POS cards. TPTFAIL indicates a far-end condition or misconfiguration of the POS port.

The TPTFAIL alarm indicates a problem on either the SDH path, the remote POS port, or a misconfiguration of the POS port which prevents the complete end-to-end POS path from working. If any SDH conditions such as an AU-AIS condition (see page 2-27); an AU-LOP alarm (see page 2-28), or an HP-UNEQ alarm (see page 2-94) exist on the circuit used by the POS port, the affected port might report a TPTFAIL alarm. If the far-end ML-series POS port is administratively disabled, the port inserts an AU-AIS condition (see page 2-27) that is detected by the near-end port. The near-end port could report TPTFAIL in this event. If the POS port is misconfigured at the IOS CLI level, the misconfiguration will cause the port to go down and report TPTFAIL.

Procedure: Clear the TPTFAIL (ML-Series) Alarm


Step 1 If there are no SDH alarms reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide for configuration information.

Step 2 If an LP-PLM alarm (see page 2-111) is the only alarm reported against the POS port circuit, verify that both POS ports are properly configured. Refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide for configuration information.

Step 3 If an AU-AIS condition (see page 2-27); an AU-LOP alarm (see page 2-28), or an HP-UNEQ alarm (see page 2-94) is present, clear those alarms using the procedures in those sections.

Step 4 If the alarm does not clear, log into http://www.cisco.com/tac to obtain information about handling the failed card or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.


2.6.235 TRMT

Major (MJ), Service Affecting (SA)

A Facility Termination Equipment Failure alarm occurs when there is a transmit failure on the E1-N-14 card because of an internal hardware failure. The card must be replaced.


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.

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


Step 1 Replace the E1-N-14 card reporting the failure. 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. Consult the Cisco ONS 15454 SDH Procedure Guide for information.


Note When replacing a card with an identical type of card, you do not need to change the CTC database.


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


2.6.236 TRMT-MISS

Major (MJ), Service Affecting (SA)

A Facility Termination Equipment Transmitter Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance is detected when a transmit cable is missing on the E-1 port or the backplane does not match the inserted card, for example, an SMB connector or a BNC connector is connected to an E-1 card.


Note DS-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.


Procedure: Clear the TRMT-MISS Alarm


Step 1 Verify that the device attached to theE-1 port is operational.

Step 2 If the device is operational, verify that the cabling is securely connected.

Step 3 If the cabling is secure, verify that the pinouts are correct.

Step 4 If the pinouts are correct, replace the transmit cable.

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


2.6.237 TU-AIS

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

A Tributary Unit (TU) AIS occurs when there is an AIS, indicating a secondary condition, in the low-order tributary overhead of the virtual circuit (VC).

An incomplete circuit path causes a TU-AIS, for example, when the port on the reporting node is in service but the DS-3 or STM-N port on a node upstream on the circuit is not in service. The upstream node often reports a loss of service, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an OOS port. The TU-AIS clears when you clear the primary alarm on the upstream node. However, the primary alarm node might not report any alarms that indicate there is a fault.

Procedure: Clear the TU-AIS Condition


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

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


2.6.238 TU-LOP

Major (MJ), Service-Affecting (SA)

A TU Loss of Pointer (LOP) alarm indicates that the SDH low order path overhead section of the administration unit has detected a loss of path. TU-LOP occurs when 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 might 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.


Procedure: Clear the TU-LOP Alarm


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

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


2.6.239 UNC-WORD

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

The Uncorrected Forward Error Correction (FEC) Word condition indicates that forward error correction (FEC), which is used to lower signal to noise ratio by 7dB to 8dB, could not correct the frame sufficiently.

Procedure: Clear the UNC-WORD Condition


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

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


2.6.240 WVL-MISMATCH

Major (MJ), Service Affecting (SA)

The Equipment Wavelength Mismatch alarm applies to the TXP and MXP cards. It occurs when you provision the card in CTC with a wavelength that the card does not support.

Procedure: Clear the WVL-MISMATCH alarm


Step 1 In the node view, double-click the TXP or MXP card to display the card view.

Step 2 Click the Provisioning > Card tabs.

Step 3 In the Wavelength field, view the provisioned card wavelength.

Step 4 If you have access to the site, compare the wavelength listed on the card faceplate with the provisioned wavelength. If you are remote, compare this wavelength with the card identification in the inventory:

a. In the node view, click the Inventory tab.

b. Locate the slot where the TXP card or MXP card is installed and view the card wavelength in the name.

Step 5 If the card was provisioned for the wrong wavelength, double-click the card in the node view to display the card view and click the Provisioning > Card tabs.

Step 6 In the Wavelength field, click the pull-down menu and choose the correct wavelength.

Step 7 Click Apply.

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


2.6.241 WKSWPR

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

The Working Switched To Protection condition occurs when a line experiences an LOS alarm (see page 2-107), an SF condition (see page 2-142) or a SD condition (see page 2-140).

Procedure: Clear the WKSWPR Condition


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

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


2.6.242 WTR

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

The Wait To Restore condition occurs when a WKSWPR condition (see page 2-163) is raised the wait-to-restore time has not expired, meaning the active protect path cannot revert to the working path. The condition clears when the timer expires and traffic is switched back to the working path.


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


2.7 Common Procedures in Alarm Troubleshooting

This section gives common procedures that are frequently used when troubleshooting alarms. For more information about ring or node traffic switching operations, refer to the Cisco ONS 15454 SDH Procedure Guide.

Procedure: Identify a Ring ID or Node ID Number


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 From the View menu, choose Go to Network View.

Step 3 Click the Provisioning > MS-SPRing tabs.

Step 4 From the Ring ID column, record the Ring ID, or in the node ID column, record the node IDs in the MS-SPRing.


Procedure: Change a Ring ID Number


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 From the View menu, choose Go to Network View.

Step 3 Click the Provisioning > MS-SPRing tabs.

Step 4 Highlight the ring and click Edit.

Step 5 In the MS-SPRing window, enter the new ID in the Ring ID field.

Step 6 Click Apply.

Step 7 Click Yes in the Changing Ring ID dialog box.


Procedure: Change a Node ID Number


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 From the View menu, choose Go to Network View.

Step 3 Click the Provisioning > MS-SPRing tabs.

Step 4 Highlight the ring and click Edit.

Step 5 In the MS-SPRing window, right-click the node on the ring map.


Tip To move a node in the MS-SPRing window for greater visibility, click the node once, then hold the Ctrl key while you click the node again and hold down the mouse button as you move the node.


Step 6 Select Set Node ID from the shortcut menu.

Step 7 In the Edit Node ID window, enter the new ID in the field.

Step 8 Click OK.


Procedure: Verify Node Visibility for Other Nodes


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 At the node (default) view, click the Provisioning > MS-SPRing tabs.

Step 3 Highlight an MS-SPRing.

Step 4 Click Ring Map.

Step 5 Verify that each node in the ring appears on the ring map with a node ID and IP address.

Step 6 Click Close.


Procedure: Verify or Create Node DCC Terminations


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.