Cisco ONS 15454 SDH Troubleshooting and Maintenance Guide, Release 3.4
Chapter 1, Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

1.1 Alarm Index by Default Severity

1.1.1 Critical Alarms (CR)

1.1.2 Major Alarms (MJ)

1.1.3 Minor Alarms (MN)

1.1.4 Conditions (NA or NR)

1.2 Alarm Index Alphabetical

1.3 Alarm Index by Alarm Type

1.3.1 Alarm Type/Object Definition

1.4 Trouble Notifications

1.4.1 Conditions

1.4.2 Severities

1.5 Safety Summary

1.6 Alarm Procedures

1.6.1 AIS

1.6.2 APSB

1.6.3 APSCDFLTK

1.6.4 APSC-IMP

1.6.5 APSCINCON

1.6.6 APSCM

1.6.7 APSCNMIS

1.6.8 AS-CMD

1.6.9 AS-MT

1.6.10 AU-AIS

1.6.11 AU-LOP

1.6.12 AUTOLSROFF

1.6.13 AUTORESET

1.6.14 AUTOSW-AIS-SNCP

1.6.15 AUTOSW-LOP-SNCP

1.6.16 AUTOSW-SDBER-SNCP

1.6.17 AUTOSW-SFBER-SNCP

1.6.18 AUTOSW-UNEQ-SNCP

1.6.19 BKUPMEMP

1.6.20 CARLOSS (EQPT)

1.6.21 CARLOSS (E-Series)

1.6.22 CARLOSS (G1000-4)

1.6.23 CLDRESTART

1.6.24 COMIOXC

1.6.25 CONTBUS-A-18

1.6.26 CONTBUS-B-18

1.6.27 CONTBUS-IO-A

1.6.28 CONTBUS-IO-B

1.6.29 CTNEQPT-PBPROT

1.6.30 CTNEQPT-PBWORK

1.6.31 DATAFLT

1.6.32 E3-ISD

1.6.33 EHIBATVG-A

1.6.34 EHIBATVG-B

1.6.35 ELWBATVG-A

1.6.36 ELWBATVG-B

1.6.37 EOC

1.6.38 EQPT

1.6.39 EQPT-MISS

1.6.40 E-W-MISMATCH

1.6.41 EXCCOL

1.6.42 EXERCISE-RING-REQ

1.6.43 EXERCISE-SPAN-REQ

1.6.44 EXT

1.6.45 EXTRA-TRAF-PREEMPT

1.6.46 FAILTOSW

1.6.47 FAILTOSW-HO

1.6.48 FAILTOSW-LO

1.6.49 FAILTOSWR

1.6.50 FAILTOSWS

1.6.51 FAN

1.6.52 FE-EXERCISING-RING

1.6.53 FE-EXERCISING-SPAN

1.6.54 FE-FRCDWKSWPR-RING

1.6.55 FE-FRCDWKSWPR-SPAN

1.6.56 FE-LOCKOUTOFPR-SPAN

1.6.57 FE-MANWKSWPR-RING

1.6.58 FE-MANWKSWPR-SPAN

1.6.59 FEPRLF

1.6.60 FORCED-REQ

1.6.61 FORCED-REQ-RING

1.6.62 FORCED-REQ-SPAN

1.6.63 FRNGSYNC

1.6.64 FSTSYNC

1.6.65 FULLPASSTHR-BI

1.6.66 HITEMP

1.6.67 HLDOVRSYNC

1.6.68 HP-RFI

1.6.69 HP-TIM

1.6.70 HP-UNEQ

1.6.71 IMPROPRMVL

1.6.72 INHSWPR

1.6.73 INHSWWKG

1.6.74 INVMACADR

1.6.75 KB-PASSTHR

1.6.76 LKOUTPR-S

1.6.77 LKOUTWK-R

1.6.78 LKOUTWK-S

1.6.79 LOCKOUT-REQ

1.6.80 LOCKOUT-REQ-RING

1.6.81 LOCKOUT-REQ-SPAN

1.6.82 LOF (BITS)

1.6.83 LOF (DS3, E-N, STM-N)

1.6.84 LOS (BITS)

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

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

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

1.6.88 LPBKTERMINAL(G1000-4)

1.6.89 LP-PLM

1.6.90 LP-RFI

1.6.91 LP-UNEQ

1.6.92 MAN-REQ

1.6.93 MANRESET

1.6.94 MANSWTOINT

1.6.95 MANSWTOPRI

1.6.96 MANSWTOSEC

1.6.97 MANSWTOTHIRD

1.6.98 MANUAL-REQ-RING

1.6.99 MANUAL-REQ-SPAN

1.6.100 MEA (Bplane)

1.6.101 MEA (EQPT)

1.6.102 MEA (FAN)

1.6.103 MEM-GONE

1.6.104 MEM-LOW

1.6.105 MFGMEM

1.6.106 MFGMEM (Backplane or Fan)

1.6.107 MS-AIS

1.6.108 MS-RFI

1.6.109 MSSP-OOSYNC

1.6.110  NOT-AUTHENTICATED

1.6.111 PRC-DUPID

1.6.112 PROTNA

1.6.113 PWR-A

1.6.114 PWR-B

1.6.115 RAI

1.6.116 RING-MISMATCH

1.6.117 RING-SW-EAST

1.6.118 RING-SW-WEST

1.6.119 SD

1.6.120 SDBER-EXCEED-HO

1.6.121 SF

1.6.122 SFBER-EXCEED-HO

1.6.123 SFTWDOWN

1.6.124 SNTP-HOST

1.6.125 SPAN-SW-EAST

1.6.126 SPAN-SW-WEST

1.6.127 SQUELCH

1.6.128 SSM-DUS

1.6.129 SSM-FAIL (BITS)

1.6.130 SSM-FAIL (STM-N)

1.6.131 SSM-LNC

1.6.132 SSM-OFF (BITS)

1.6.133 SSM-OFF (STM-N)

1.6.134 SSM-PRC

1.6.135 SSM-SETS

1.6.136 SSM-STU (BITS)

1.6.137 SSM-STU (STM-N)

1.6.138 SSM-TNC (BITS)

1.6.139 SSM-TNC (STM-N)

1.6.140 SWMTXMOD

1.6.141 SWTOPRI

1.6.142 SWTOSEC

1.6.143 SWTOTHIRD

1.6.144 SYNC-FREQ (BITS, STM-N)

1.6.145 SYNCPRI

1.6.146 SYNCSEC

1.6.147 SYNCTHIRD

1.6.148 SYSBOOT

1.6.149 TPTFAIL

1.6.150 TRMT

1.6.151 TU-AIS

1.6.152 TU-LOP

1.6.153 WKSWPR

1.6.154 WTR

1.7 Common Procedures in Alarm Troubleshooting


Alarm Troubleshooting


This chapter gives a list of alarm descriptions, default severities, and troubleshooting procedures for all alarms that can be resolved in the Cisco ONS 15454 SDH system. See Table 1-1 for an alphabetical list of alarms that appear on the ONS 15454 SDH. See Table 1-6 for a list of alarms organized by alarm type. This chapter provides comprehensive lists of alarm conditions with severities of Critical, Major, or Minor.

All listed alarm severities are defaults for active cards, if applicable. Active cards have provisioned ports, even if they are not put in service. Cards with unprovisioned ports are considered inactive. The default severity for all inactive card alarms is Minor, Non-Service-Affecting. The default standby severity for conditions with a severity of Not Alarmed (NA), Non-Service Affecting is NA, NSA. The default standby severity for conditions with a severity of Not Reported (NR), NSA is NR, NSA. Alarm severities can be changed by single alarm or by profile. For more information about this, see the Alarm Monitoring and Management Chapter in the Cisco ONS 15454 SDH Installation and Operations Guide. The troubleshooting procedures in this chapter apply to the Cisco Transport Controller (CTC) version of that 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.

1.1 Alarm Index by Default Severity

The alarm index by default severity groups alarms and conditions by the severity displayed in the CTC Alarms tab in the severity (SEV) column.

1.1.1 Critical Alarms (CR)

Table 1-1 lists of critical alarms.


1.1.2 Major Alarms (MJ)

Table 1-2 lists major alarms.


1.1.3 Minor Alarms (MN)

Table 1-3 lists minor alarms.


1.1.4 Conditions (NA or NR)

Table 1-4 lists conditions that are not alarmed or not reported.

Table 1-4 Conditions Index 

AIS

FULLPASSTHR-BI

RING-SW-WEST

AS-CMD

HP-RFI

SD

AS-MT

INHSWPR

SDBER-EXCEED-HO

AU-AIS

INHSWWKG

SF

AUTOSW-AIS-SNCP

KB-PASSTHR

SFBER-EXCEED-HO

AUTOSW-SDBER-SNCP

LKOUTPR-S

SPAN-SW-EAST

AUTOSW-SFBER-SNCP

LKOUTWK-R

SPAN-SW-WEST

CLDRESTART

LKOUTWK-S

SQUELCH

E3-ISD

LOCKOUT-REQ

SSM-DUS

EXERCISE-RING-REQ

LOCKOUT-REQ-SPAN

SSM-LNC

EXERCISE-SPAN-REQ

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

SSM-OFF (BITS)

FAILTOSW

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

SSM-OFF (STM-N)

FAILTOSW-HO

LPBKTERMINAL(G1000-4)

SSM-PRC

FAILTOSW-LO

LP-RFI

SSM-SETS

FAILTOSWR

MAN-REQ

SSM-STU (BITS)

FAILTOSWS

MANRESET

SSM-STU (STM-N)

FE-EXERCISING-RING

MANSWTOINT

SSM-TNC (BITS)

FE-EXERCISING-SPAN

MANSWTOPRI

SWTOPRI

FE-FRCDWKSWPR-RING

MANSWTOSEC

SWTOSEC

FE-FRCDWKSWPR-SPAN

MANSWTOTHIRD

SWTOTHIRD

FE-LOCKOUTOFPR-SPAN

MANUAL-REQ-RING

SYNC-FREQ (BITS, STM-N)

FE-MANWKSWPR-RING

MANUAL-REQ-SPAN

TU-AIS

FE-MANWKSWPR-SPAN

MS-AIS

TU-LOP

FORCED-REQ

MS-RFI

WKSWPR

FORCED-REQ-RING

RAI

WTR

FORCED-REQ-SPAN

RING-SW-EAST

 

1.2 Alarm Index Alphabetical

Table 1-5 lists alarms by the name displayed on the CTC Alarms tab in the conditions column.

Table 1-5 Alarm Index 

AIS

FE-EXERCISING-RING

MEM-GONE

APSB

FE-EXERCISING-SPAN

MEM-LOW

APSCDFLTK

FE-FRCDWKSWPR-RING

MFGMEM

APSC-IMP

FE-FRCDWKSWPR-SPAN

MFGMEM (Backplane or Fan)

APSCINCON

FE-LOCKOUTOFPR-SPAN

MS-AIS

APSCM

FE-MANWKSWPR-RING

MS-RFI

APSCNMIS

FE-MANWKSWPR-SPAN

MSSP-OOSYNC

AS-CMD

FEPRLF

NOT-AUTHENTICATED

AS-MT

FORCED-REQ

PRC-DUPID

AU-AIS

FORCED-REQ-RING

PROTNA

AU-LOP

FORCED-REQ-SPAN

PWR-A

AUTOLSROFF

FRNGSYNC

PWR-B

AUTORESET

FSTSYNC

RAI

AUTOSW-AIS-SNCP

FULLPASSTHR-BI

RING-MISMATCH

AUTOSW-LOP-SNCP

HITEMP

RING-SW-EAST

AUTOSW-SDBER-SNCP

HLDOVRSYNC

RING-SW-WEST

AUTOSW-SFBER-SNCP

HP-RFI

SD

AUTOSW-UNEQ-SNCP

HP-TIM

SDBER-EXCEED-HO

BKUPMEMP

HP-UNEQ

SF

CARLOSS (EQPT)

IMPROPRMVL

SFBER-EXCEED-HO

CARLOSS (E-Series)

INHSWPR

SFTWDOWN

CARLOSS (G1000-4)

INHSWWKG

SNTP-HOST

CLDRESTART

INVMACADR

SPAN-SW-EAST

COMIOXC

KB-PASSTHR

SPAN-SW-WEST

CONTBUS-A-18

LKOUTPR-S

SQUELCH

CONTBUS-B-18

LKOUTWK-R

SSM-DUS

CONTBUS-IO-A

LKOUTWK-S

SSM-FAIL (BITS)

CONTBUS-IO-B

LOCKOUT-REQ

SSM-FAIL (STM-N)

CTNEQPT-PBPROT

LOCKOUT-REQ-RING

SSM-LNC

CTNEQPT-PBWORK

LOCKOUT-REQ-SPAN

SSM-OFF (BITS)

DATAFLT

LOF (BITS)

SSM-OFF (STM-N)

E3-ISD

LOF (DS3, E-N, STM-N)

SSM-PRC

EHIBATVG-A

LOS (BITS)

SSM-SETS

EHIBATVG-B

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

SSM-STU (BITS)

ELWBATVG-A

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

SSM-STU (STM-N)

ELWBATVG-B

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

SSM-TNC (BITS)

EOC

LPBKTERMINAL(G1000-4)

SSM-TNC (STM-N)

EQPT

LP-PLM

SWMTXMOD

EQPT-MISS

LP-RFI

SWTOPRI

E-W-MISMATCH

LP-UNEQ

SWTOSEC

EXCCOL

MAN-REQ

SWTOTHIRD

EXERCISE-RING-REQ

MANRESET

SYNC-FREQ (BITS, STM-N)

EXERCISE-SPAN-REQ

MANSWTOINT

SYNCTHIRD

EXT

MANSWTOPRI

SYSBOOT

EXTRA-TRAF-PREEMPT

MANSWTOSEC

TPTFAIL

FAILTOSW

MANSWTOTHIRD

TRMT

FAILTOSW-HO

MANUAL-REQ-RING

TU-AIS

FAILTOSW-LO

MANUAL-REQ-SPAN

TU-LOP

FAILTOSWR

MEA (Bplane)

WKSWPR

FAILTOSWS

MEA (EQPT)

WTR

FAN

MEA (FAN)

 

1.3 Alarm Index by Alarm Type

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

Table 1-6 Alarm Index by Alarm Type 

AIP: EQPT

AIE: EQPT

AIE: MFGMEM (Backplane or Fan)

BITS: AIS

BITS: LOF (BITS)

BITS: LOS (BITS)

BITS: SSM-DUS

BITS: SSM-FAIL (BITS)

BITS: SSM-LNC

BITS: SSM-OFF (BITS)

BITS: SSM-PRC

BITS: SSM-SETS

BITS: SSM-STU (BITS)

BITS: SSM-TNC (BITS)

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

BPLANE: AS-CMD

BPLANE: INVMACADR

BPLANE: MEA (Bplane)

BPLANE: MFGMEM (Backplane or Fan)

DS3: AIS

DS3: AS-CMD

DS3: AS-MT

DS3: LOF (DS3, E-N, STM-N)

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

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

DS3: RAI

E-1: AS-CMD

E-1: AIS

E-1: AS-MT

E-1: LOF (DS3, E-N, STM-N)

E-1: LOF (DS3, E-N, STM-N)

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

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

E-1: RAI

E-1: TRMT

E-3: AIS

E-3: AS-CMD

E-3: AS-MT

E-3: E3-ISD

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

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

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

EC-N: AS-CMD

EC-N: AS-MT

EC-N: LOF (DS3, E-N, STM-N)

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

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

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

ENV: EXT

EQPT: AS-CMD

EQPT: AUTORESET

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: 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: PROTNA

EQPT: SFTWDOWN

EQPT: SWMTXMOD

EQPT: WKSWPR

EQPT: WTR

ETHER: CARLOSS (E-Series)

EXTSYNC: MANSWTOPRI

EXTSYNC: MANSWTOSEC

EXTSYNC: MANSWTOTHIRD

EXTSYNC: SWTOPRI

EXTSYNC: SWTOSEC

EXTSYNC: SWTOTHIRD

EXTSYNC: SYNCPRI

EXTSYNC: SYNCSEC

EXTSYNC: SYNCTHIRD

FAN: EQPT-MISS

FAN: FAN

FAN: MEA (FAN)

FAN: MFGMEM (Backplane or Fan)

FUDC: AIS

FUDC: LOF (DS3, E-N, STM-N)

HDGE [G1000]: CARLOSS (G1000-4)

HDGE [G1000]: LPBKTERMINAL(G1000-4)

HDGE [G1000]: TPTFAIL

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: FAILTOSW-HO

HPMON: FORCED-REQ

HPMON: HP-RFI

HPMON: HP-TIM

HPMON: HP-UNEQ

HPMON: LOCKOUT-REQ

HPMON: MAN-REQ

HPMON: SDBER-EXCEED-HO

HPMON: SFBER-EXCEED-HO

HPMON: WKSWPR

HPTERM: AU-AIS

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-SFBER-SNCP

LPMON: FAILTOSW-LO

LPMON: FORCED-REQ

LPMON: LOCKOUT-REQ

LPMON: LP-UNEQ

LPMON: MAN-REQ

LPMON: TU-AIS

LPMON: TU-LOP

LPMON: WKSWPR

LPTERM: LP-PLM

LPTERM: LP-RFI

LPTERM: LP-UNEQ

LPTERM: SD

LPTERM: SF

LPTERM: TU-AIS

LPTERM: TU-LOP

NE: DATAFLT

NE: EHIBATVG-A

NE: EHIBATVG-B

NE: ELWBATVG-A

NE: EHIBATVG-B

NE: PRC-DUPID

NE: PWR-A

NE: PWR-B

NE: SNTP-HOST

NE: SYSBOOT

NERING: FULLPASSTHR-BI

NERING: MSSP-OOSYNC

NERING: PRC-DUPID

NERING: RING-MISMATCH

NESYNC: FRNGSYNC

NESYNC: FSTSYNC

NESYNC: HLDOVRSYNC

NESYNC: KB-PASSTHR

NESYNC: MANSWTOINT

NESYNC: MANSWTOPRI

NESYNC: MANSWTOSEC

NESYNC: MANSWTOTHIRD

NESYNC: SSM-SETS

NESYNC: SSM-STU (STM-N)

NESYNC: SSM-TNC (STM-N)

NESYNC: SWTOPRI

NESYNC: SWTOSEC

NESYNC: SWTOTHIRD

NESYNC: SYNCPRI

NESYNC: SYNCSEC

NESYNC: SYNCTHIRD

NE: EQPT

STM-N: APSB

STM-N: APSB

STM-N: APSCDFLTK

STM-N: APSC-IMP

STM-N: APSCINCON

STM-N: APSCM

STM-N: AS-CMD

STM-N: AS-MT

STM-N: AUTOLSROFF

STM-N: EOC

STM-N: E-W-MISMATCH

STM-N: EXERCISE-RING-REQ

STM-N: EXERCISE-SPAN-REQ

STM-N: EXTRA-TRAF-PREEMPT

STM-N: FAILTOSW

STM-N: FAILTOSWR

STM-N: FAILTOSWS

STM-N: FE-EXERCISING-RING

STM-N: FE-EXERCISING-SPAN

STM-N: FE-FRCDWKSWPR-RING

STM-N: FE-FRCDWKSWPR-SPAN

STM-N: FE-LOCKOUTOFPR-SPAN

STM-N: FE-MANWKSWPR-RING

STM-N: FE-MANWKSWPR-SPAN

STM-N: FEPRLF

STM-N: FORCED-REQ-RING

STM-N: FORCED-REQ-SPAN

STM-N: LKOUTPR-S

STM-N: LKOUTWK-R

STM-N: LKOUTWK-S

STM-N: LOCKOUT-REQ

STM-N: LOCKOUT-REQ-RING

STM-N: LOF (DS3, E-N, STM-N)

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

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

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

STM-N: MANUAL-REQ-RING

STM-N: MANUAL-REQ-SPAN

STM-N: MS-AIS

STM-N: MS-RFI

STM-N: RING-SW-EAST

STM-N: RING-SW-WEST

STM-N: SD

STM-N: SF

STM-N: SPAN-SW-EAST

STM-N: SPAN-SW-WEST

STM-N: SQUELCH

STM-N: SSM-DUS

STM-N: SSM-FAIL (STM-N)

STM-N: SSM-LNC

STM-N: SSM-OFF (STM-N)

STM-N: SSM-PRC

STM-N: SSM-SETS

STM-N: SSM-STU (STM-N)

STM-N: SSM-TNC (STM-N)

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

STM-N: WKSWPR

STM-N: WTR


1.3.1 Alarm Type/Object Definition

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

Table 1-7 Alarm Type/Object Definition

BITS

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

BPLANE

Backplane

E1

E1-N-14 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 (SYSTEM)

NERINGSDH

SDH NE1 ring

NESYNCHSDH

SDH NE synchronization

STMN

Synchronous Transfer Mode (speed)

1 Network element


1.4 Trouble Notifications

The ONS 15454 SDH uses ITU-T x.733-compliant categories to characterize alarm levels. In CTC, the Critical, Major, and Minor ONS 15454 SDH alarms are reported in the Alarms tab. This tab contains alarms such as loss of signal (LOS) indicating problems a user must correct. The ONS CTC Conditions tab contains ONS 15454 SDH conditions as well as alarms. If a condition is not listed in the Alarms tab as well, it is a notification and does not require user action.

Alarms are further divided into Service Affecting (SA) and NSA status. An SA failure affects a provided service or the network's ability to provide service. The high temperature ( HITEMP) alarm, which means the ONS 15454 SDH is hotter than 50 degrees Celsius (122 degrees Fahrenheit), is an SA failure. For example, although a particular E-1 port might not be affected, a high temperature affects the network's ability to provide service.

1.4.1 Conditions

When an SA failure is detected, the ONS 15454 SDH also sends an alarm indication signal (AIS) downstream. When it receives the AIS, the receiving node sends a remote failure indication (RFI) upstream. AIS and RFI belong in the conditions category and are shown on the Conditions tab of the ONS 15454 SDH. The condition reporting is not ITU-compliant.

1.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 Fast Start Synchronization (FSTSYNC), 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.

The ONS 15454 SDH uses standard severity reporting that is ITU-compliant. You can customize ONS 15454 SDH alarm severities with the alarm profiles feature. For additional information about alarm severities, refer to the Cisco ONS 15454 SDH Installation and Operations Guide.

1.5 Safety Summary

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


Caution Hazardous voltage or energy 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 optical (STM) cards. In these instances, users should 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 may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may result in hazardous radiation exposure.



Warning Class 1 laser product.



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


1.6 Alarm Procedures

This section lists alarms alphabetically. Each alarm or condition topic gives the severity, description, and troubleshooting procedure.

1.6.1 AIS

Not Reported (NR) (Condition)

The ONS 15454 SDH detects an Alarm Indication Signal (AIS) in the SDH overhead. This condition 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 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 it is at fault.

Procedure: Clear the AIS Condition


Step 1 Check upstream nodes and equipment for alarms, especially for LOS and out-of-service ports.

Step 2 If the condition does not clear, 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.


1.6.2 APSB

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

The Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming automatic protection switching (APS) signal. This happens 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 raise an APSB on an ONS 15454 SDH node.

Procedure: Clear the APSB Alarm


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

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

Step 2 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. You might need to replace the upstream cards for protection switching to operate 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.


1.6.3 APSCDFLTK

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

The Default K Byte received alarm occurs when an multiplex section-shared protection ring (MS-SPRing) is not properly configured. For example, it occurs when a four-node MS-SPRing has one node configured as an SNCP ring. In this case, a node in an subnetwork connection protection (SNCP) 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.


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



Warning Invisible laser radiation may 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 APSCDFLTK Alarm


Step 1 Verify that each node has a unique node ID number by using the "Identify a Ring ID or Node ID Number" procedure.

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

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

Step 3 If the alarm does not clear, verify correct configuration of east port and west port optical fibers (see the "E-W-MISMATCH" section). West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 SDH Installation and Operations Guide provides a procedure for fibering MS-SPRings.

Step 4 If the alarm does not clear and if it is a four-fiber MS-SPRing system, 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 5 If the alarm does not clear, check the ring in network view and verify that each node is visible to the other nodes using the "Verify Node Visibility for Other Nodes" procedure.

Step 6 If nodes are not visible, use the "Check or Create Node SDCC Terminations" procedure to ensure that SDCC terminations exist on each node.

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.


1.6.4 APSC-IMP

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

An Improper APS Code alarm indicates invalid K bytes. This alarm 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 lies in 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, verify that each node has a ring ID that matches the other node ring IDs. Use 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, make the ring ID number of that node identical to the other nodes. Use the "Change a Ring ID Number" procedure.

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.


1.6.5 APSCINCON

Minor (MN), Service Affecting (SA)

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 LOS (DS-3, E-N, STM-N), loss of frame ( LOF (DS3, E-N, STM-N)) or AIS. Clearing these alarms 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 in order to report a service affecting problem.


1.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. This alarm is raised in a 1+1 configuration. The APSCM alarm only occurs on the ONS 15454 SDH when 1+1 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 for the laser to be on. The laser is off when the safety key is off (labeled 0).



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


1.6.7 APSCNMIS

Major (MJ), Service Affecting (SA)

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

Procedure: Clear the APSCNMIS Alarm


Step 1 Verify that each node has a unique node ID number using the "Identify a Ring ID or Node ID Number" procedure.

Step 2 If the Nodes 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, use 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 > BLSR tabs. This window displays the node ID of the node you are logged into.



Note Locking out and clearing the 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, lock out the span using the "Lock Out an MS-SPRing Span" procedure.

Step 6 Clear the lockout using the "Clear an MS-SPRing Span Command" procedure.

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.


1.6.8 AS-CMD

Not Alarmed (NA) (Condition)

The Alarms Suppressed by User Command condition applies to the node, backplane, and cards. This condition is caused when alarms are suppressed for one or more cards or for the entire shelf.

Procedure: Clear the AS-CMD Condition


Step 1 Click the Conditions tab. From the Object column and Eqpt Type column, note what entity the condition is reported against, such as against a port, slot, shelf, or against the ONS 15454 SDH.

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

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

If the Condition tab says that the object is "system," it means that it applies to the shelf. Go to Step 7.

Step 2 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, click it to deselect it and click Apply.

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

Step 3 In the CTC node (default login) view, if the AS-CMD condition is reported for a card and not an individual port, click the Provisioning > Alarm Behavior tabs.

Step 4 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 1.)

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

Step 6 If the condition is reported for the backplane, the alarms are suppressed for cards such as the alarm interface panel (AIP) that are not in the optical or electrical slots.

a. In the CTC node (default login) view, click the Provisioning > Alarm Behavior tabs.

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

Step 7 If the condition is reported for the shelf, then cards and other equipment are affected.

a. In the CTC node (default login) 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 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.


1.6.9 AS-MT

Not Alarmed (NA) (Condition)

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

To clear the AS-MT condition by clearing the loopback, follow the "Clear a Loopback" 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.

1.6.10 AU-AIS

Not Reported (NR) (Condition)

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. This condition 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, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an out-of-service 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 it is at fault.

Procedure: Clear the AU-AIS Condition


Step 1 Check upstream nodes and equipment for alarms, especially for LOS and out-of-service ports.

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

Step 3 If the condition does not clear, follow the procedure in the "APSB" section.

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.


1.6.11 AU-LOP

Critical (CR), Service Affecting (SA)

An Administration Unit Loss of Pointer (LOP) alarm applies to the administration unit, which consists of the VC capacity and pointer bytes (H1, H2, and H3) in the SDH frame. This alarm is caused when the first payload pointer is not synchronized according to the system clock.


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



Warning Invisible laser radiation may 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 Check for LOS (DS-3, E-N, STM-N) on the reporting card and clear that alarm if applicable.

Step 2 If the AU-LOP does not clear, check whether attenuation is present on the input fiber cable on the card raising the alarm.

Step 3 If the alarm does not clear, check the signal level on the input fiber with the attenuator (if present).

Step 4 If the fiber signal level with an attenuator is below the correct threshold, remove the attenuator and check signal level again.

Step 5 If the signal level is still low, clean both ends of the fiber cable connection according to site practice.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

Step 6 If the alarm does not clear, clean the far-end optical fiber cable ends.

Step 7 If error remains, check for a timing alarm. Follow the procedure in the "SYNCPRI" section.

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 in order to report a service affecting problem.


1.6.12 AUTOLSROFF

Critical (CR), Service Affecting (SA)

The Automatic Laser Off alarm is raised when the OC192 LR/STM64 LH 1550 card temperature exceeds 90 degrees Celsius (194 degrees Fahrenheit). The internal equipment automatically shuts down the OC192 LR/STM64 LH 1550 laser when the card temperature rises to prevent the card from self-destructing.


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



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



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


Procedure: Clear the AUTOLSROFF Alarm


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

Step 2 If the temperature of the ONS 15454 SDH is below 90 degrees Celsius (194 degrees Fahrenheit), the ONS 15454 SDH temperature is not the cause of the alarm, and you should replace the OC-192 card. Use the "Physically Replace a Card" procedure.


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


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


1.6.13 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 Check for additional alarms that might have triggered an automatic reset.

Step 2 If the card automatically resets more than once a month with no apparent cause, replace it with a new card. Follow 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 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.


1.6.14 AUTOSW-AIS-SNCP

Not Reported (NR) (Condition)

The Automatic SNCP Switch Caused by AIS condition indicates that automatic SNCP protection switching took place because of an AIS alarm. The SNCP is configured for revertive switching and will switch back to the working path after the fault clears.

The AIS condition 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 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 out-of-service port. The AUTOSW-AIS-SNCP clears when you clear the primary alarm on the upstream node.

To clear the condition, follow the procedure in the "MS-AIS" section. 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.

1.6.15 AUTOSW-LOP-SNCP

Minor (MN), Service Affecting (SA)

An Automatic SNCP Switch Caused by LOP alarm indicates that automatic SNCP protection switching took place because of the LOP alarm. The SNCP 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 Verify the cabling and physical connections on the reporting card.

Step 2 If the alarm does not clear, perform a CTC reset on the reporting card. Follow the "Reset a Card in CTC" procedure.

Step 3 If the alarm does not clear, do a manual switch (side switch) to move traffic away from the card. Follow the "Side-Switch the Active and Standby Cross-Connect Card" procedure.


Note If you do not have a protect card for the reporting card, create a new circuit on the reporting card to achieve the same effect.


Step 4 Clear the manual switch. Follow the "Clear a Protection Group Switch Command" procedure.

Step 5 If the alarm persists, the problem is at the far-end node. Verify the stability of the cabling and physical connections that connect to the far-end card.

Step 6 If the alarm does not clear, do a CTC reset on the far-end card. Follow the "Reset a Card in CTC" procedure.

Step 7 If the alarm does not clear, do another CTC reset on the reporting card. Follow the "Reset a Card in CTC" procedure.

Step 8 If the alarm does not clear, switch from the far-end working card to the far-end protect card. Follow the "Lock Out an MS-SPRing Span" procedure.

Step 9 If the alarm persists, replace the far-end card. Use 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 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.


1.6.16 AUTOSW-SDBER-SNCP

Not Alarmed (NA) (Condition)

The Automatic SNCP Switch Caused by Bit Error Rate Signal Degrade (SDBER) condition indicates that a signal degrade alarm caused automatic SNCP protection switching to occur. The SNCP is configured for revertive switching and will switch back to the working path after the signal degrade is resolved.

To clear the condition, follow the procedure in the "SDBER-EXCEED-HO" section. 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.

1.6.17 AUTOSW-SFBER-SNCP

Not Alarmed (NA) (Condition)

The Automatic SNCP Switch Caused by Bit Error Rate Signal Failure (SFBER) condition indicates that a signal fail alarm caused automatic SNCP protection switching to occur. The SNCP is configured for revertive switching and will switch back to the working path after the signal fail is resolved.

To clear the condition, follow the procedure in the "SFBER-EXCEED-HO" section. 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.

1.6.18 AUTOSW-UNEQ-SNCP

Minor (MN), Service Affecting (SA)

An Automatic SNCP Switch Caused by UNEQ alarm indicates that automatic SNCP protection switching took place because of an UNEQ alarm. The SNCP is configured for revertive switching and will switch back 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 may 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 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, check for low-order paths 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, check for incomplete circuits such as stranded bandwidth from circuits that were not deleted completely.

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 check 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 (default login) 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, check the far-end STM-N card that provides payload to the card.

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, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.


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 may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may 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 in order to report a service affecting problem.


1.6.19 BKUPMEMP

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

The BKUPMEMP alarm refers to a problem with the Timing Communications and Control-International (TCC-I) card Flash memory. The alarm occurs when the TCC-I 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 check for errors in data transmitted to the TCC-I. The BKUPMEMP alarm also raises 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 TCC-I cards are powered and enabled by confirming the lit ACT/STBY LEDs on the TCC-I cards.

Step 2 If both TCC-I cards are powered and enabled, reset the active TCC-I card to make the standby TCC-I card active. Use the "Reset Active TCC-I Card and Activate Standby Card" procedure.


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


Wait ten minutes to verify that the standby TCC-I does not reset by itself due to a code volume failure or other external failure. If the reset is not complete and error-free or if the standby TCC-I reboots by itself, 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 3 If the alarm clears, follow the "Reset the TCC-I using a Card Pull" procedure on page 4-7 on the new standby TCC-I and allow it to boot up completely.

Step 4 If the alarm does not clear, perform a second CTC reset, this time on the newly active TCC-I card to make the recently reseated standby TCC-I card active. Use the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC-I does not reset itself. If the TCC-I reset is not complete and error-free or if the TCC-I reboots itself, 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 5 If the alarm reappears after you perform the switch, replace the TCC-I card. Use the "Physically Replace a Card" procedure.


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


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.


1.6.20 CARLOSS (EQPT)

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

This carrier loss alarm means the ONS 15454 SDH and the workstation hosting CTC do not have a TCP/IP connection. It is a problem involving the LAN or data circuit used by the RJ-45 connector on the TCC-I card or the LAN backplane pin connection on the back of the ONS 15454 SDH. It does not involve an Ethernet circuit connected to a port on an Ethernet card. The problem is in the connection (usually a LAN problem) and not the CTC or the ONS 15454 SDH.

Procedure: Clear the CARLOSS Alarm (EQPT)


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 IP address]

For example, ping 192.1.0.2.

If the workstation has connectivity to the ONS 15454 SDH, it displays a "reply from [IP Address]" after the ping. If the workstation does not have connectivity, a "Request timed out" message displays.

Step 2 If the ping is successful, an active TCP/IP connection exists. Restart CTC.

Step 3 If you are unable to establish connectivity, perform standard network/LAN diagnostics.

For example, trace the IP route, check cables, and check any routers between the node and CTC.

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.


1.6.21 CARLOSS (E-Series)

Major (MJ), Service Affecting (SA)

A Carrier Loss on the LAN alarm is the data equivalent of an SDH LOS alarm. The Ethernet 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 (put in service) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

This alarm also occurs after the restoration of a node database. In this instance, the alarm will clear in approximately 30 seconds after spanning-tree protection reestablishes. This 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 Alarm (E Series)


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, check 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, physically reseat the Ethernet card. Use the "Physically Reseat a Card" procedure.

Step 7 If the alarm does not clear, replace the Ethernet card. Use the "Physically Replace a Card" procedure.


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 particular network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect. If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm might be a result of mismatched STS circuit sizes in the set up of the manual cross-connect. If the Ethernet circuit is not part of a manual cross-connect, these steps do not apply.


Note A Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454 SDHs, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 SDH TCP/IP-based data communications channel (DCC). To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an synchronous transport signal (STS) channel riding through the non-Cisco optical system network.


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

b. Click the Select Affected Circuits dialog that appears.

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

d. From the examination of the layout of your particular network, determine the ONS 15454 SDH and card that 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 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. This 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.

If one of the circuit sizes is incorrect, follow the "Delete a Circuit" procedure.

f. Reconfigure the circuit with the correct circuit size. For more information, refer to the Cisco ONS 15454 SDH Installation and Operations Guide.

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.


1.6.22 CARLOSS (G1000-4)

Major (MJ), Service Affecting (SA)

A Carrier Loss on the LAN alarm is the data equivalent of an SDH LOS alarm. The Ethernet card has lost its link and is not receiving a valid signal.

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

The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. A common cause is that a straight-through (Category 5) LAN cable is not connected properly to the reporting Ethernet port, an STM-N card is connected to the port instead of an Ethernet device, or there is a problem with the signal from the Ethernet device attached to the G1000-4 port.

There is a problem in the end-to-end path (including possibly the remote end G1000-4 card) that is causing 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 this clears the CARLOSS on the reporting card. In this case, the CARLOSS alarm is normally accompanied by another alarm or condition on the end-to-end path, such as a TPTFAIL or an STM-N alarm or condition.

Refer to the "G1000-4 Card" section on page 3-91 for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TPTFAIL" section for more information on alarms that occur when a point-to-point circuit exists between two G1000-4 cards.

Ethernet card ports must be enabled (put in service) 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 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, check that the transmitting attached 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 link auto-negotiation is enabled on the G1000-4 port, but the auto-negotiation process fails, the G1000-4 turns off its transmitter laser and reports a CARLOSS alarm. If link auto-negotiation has been enabled for the port, check for conditions that could cause auto-negotiation 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.

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

Step 7 If all previous attempts fail, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. (This restarts the auto-negotiation process.)

Step 8 If the TPTFAIL alarm is also reported, see the "TPTFAIL" section. 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, check to see whether terminal loopback has been provisioned on this port by clicking the Conditions tab and the Retrieve Conditions button and seeing if LPBKTERMINAL is listed for the port.

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 this as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could cause the CARLOSS alarm detected by the G1000-4 port in loopback.

If the port is not set in LPBKTERMINAL, continue to Step 11.

Step 11 If a CARLOSS alarm repeatedly appears and clears, examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect. If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm might be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. If the Ethernet circuit is not part of a manual cross-connect, these steps do not apply.


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 the Select Affected Circuits dialog.

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

d. From the examination of the layout of your particular network, determine the ONS 15454 SDH and card that 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 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. This 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.

If one of the circuit sizes is incorrect, follow the "Delete a Circuit" procedure.

f. Reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Installation and Operations Guide for detailed procedures on how to create circuits.

Step 12 If a valid Ethernet signal is present, physically reseat the Ethernet card. Use the "Physically Reseat a Card" procedure.

Step 13 If the alarm does not clear, replace the Ethernet card. Use the "Physically Replace a Card" procedure.


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.


1.6.23 CLDRESTART

Not Alarmed (NA) (Condition)

A Cold Restart condition occurs when you physically remove and insert a card, power up an ONS 15454 SDH, or replace a card.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the 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, physically reseat the card. Use the "Physically Reseat a Card" procedure.

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


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.


1.6.24 COMIOXC

Critical (CR), Service Affecting (SA)

The Input/Output (I/O) Slot to Cross-Connect (XCON) Communication Failure alarm is raised by the 10 Gigabit Cross Connect (XC10G) card. It occurs when there is a communication failure for a particular I/O slot.

Procedure: Clear the COMIOXC Condition


Step 1 Follow the "Reset a Card in CTC" procedure on the reporting XC10G 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 3 If the CTC reset does not clear the alarm, move traffic off the XC10G card. Use the "Side-Switch the Active and Standby Cross-Connect Card" procedure.

Step 4 Physically reseat the reporting card. Use the "Physically Reseat a Card" procedure.

Step 5 If the alarm does not clear, replace the XC10G card. Use the "Physically Replace a Card" procedure.


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.


1.6.25 CONTBUS-A-18

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

The Communication Failure from TCC-I slot to TCC-I slot alarm means the main processor on the TCC-I card in Slot 7 has lost communication with the coprocessor on the second TCC-I card in Slot 11. The problem is with the physical path of communication from the TCC-I card to the reporting card. The physical path of communication includes the two TCC-I 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 Position the cursor over the TCC-I card in Slot 7 and reset it by following the "Reset Active TCC-I Card and Activate Standby Card" procedure to make the TCC-I in Slot 11 active.


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


Step 2 Wait approximately 2 minutes for the TCC-I in Slot 7 to reset as the standby TCC-I. Verify that the Standby LED is on before proceeding to the next step.

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

Step 4 If the alarm reappears when the TCC-I in Slot 7 reboots as the active TCC-I, the TCC-I card in Slot 7 is defective and must be replaced by following 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 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.


1.6.26 CONTBUS-B-18

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

The Communication Failure from TCC-I slot to TCC-I slot alarm means the main processor on the TCC-I card in Slot 11 lost communication with the coprocessor on the TCC-I card in Slot 7. The problem is with the physical path of communication from the TCC-I card to the reporting TCC-I card. The physical path of communication includes the two TCC-I 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 TCC-I Card


Step 1 Position the cursor over the TCC-I card in Slot 11 and reset it by following the "Reset Active TCC-I Card and Activate Standby Card" procedure to make the TCC-I in Slot 7 active.


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


Step 2 Wait approximately 2 minutes for the TCC-I in Slot 11 to reset as the standby TCC-I. Verify that the Standby LED is on before proceeding to the next step.

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


Note If the alarm reappears when the TCC-I in Slot 7 reboots as the active TCC-I, the TCC-I card in Slot 7 is defective and must be replaced. Follow the "Physically Replace a Card" procedure. When you replace a card with an identical type of card, you do not need to make any changes to the database.


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


1.6.27 CONTBUS-IO-A

Major (MJ), Service Affecting (SA)

A TCC-I A to Shelf Slot Communication Failure alarm occurs when the active TCC-I card in Slot 7 (TCC-I 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 TCC-I card. In the case of a TCC-I protection switch, the alarm clears after the other cards establish communication with the new active TCC-I card. If the alarm persists, the problem is with the physical path of communication from the TCC-I card to the reporting card. The physical path of communication includes the TCC-I 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 for the reporting card.

Step 2 If the alarm object is any single card slot other than the standby TCC-I in Slot 11, perform a CTC reset of the traffic card. Use the "Reset a Card in CTC" procedure. Verify that the following LED behavior 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 card in CTC.

Step 3 If the alarm object is the standby TCC-I in Slot 11, perform a soft reset of this card:

a. Right-click the Slot 11 TCC-I 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 TCC-I 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 "Physically Reseat a Card" procedure.

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 in order to report a service-affecting problem.


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



1.6.28 CONTBUS-IO-B

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

A TCC-I B to Shelf Slot Communication Failure alarm occurs when the active TCC-I card in Slot 11 (TCC-I 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 TCC-I card. In the case of a TCC-I protection switch, the alarm clears after the other cards establish communication with the new active TCC-I card. If the alarm persists, the problem is with the physical path of communication from the TCC-I card to the reporting card. The physical path of communication includes the TCC-I 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 for the reporting card.

Step 2 If the alarm object is any single card slot other than the standby TCC-I in Slot 7, perform a CTC reset of the traffic card. Use the "Reset a Card in CTC" procedure. Verify that the following LED behavior 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 card in CTC.

Step 3 If the alarm object is the standby TCC-I in Slot 7, perform a soft reset of this card:

a. Right-click the Slot 7 TCC-I 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 TCC-I 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 "Physically Reseat a Card" procedure.

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 in order to report a service-affecting problem.


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



1.6.29 CTNEQPT-PBPROT

Critical (CR), Service Affecting (SA)

The Interconnection Equipment Failure Protect Payload Bus alarm indicates a failure of the main payload between the protect cross-connect XC10G card in Slot 10 and the reporting traffic 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 this alarm, physically reseat the standby TCC-I card. If this fails to clear the alarm, replace the standby TCC-I card. Do not physically reseat an active TCC-I card. This 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 XC10G card. Use the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

If the cross-connect reset is not complete and error-free or if the TCC-I 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, physically reseat the standby cross-connect card. Use the "Physically Reseat a Card" procedure.

Step 4 If the alarm does not clear and the reporting traffic card is the active card in the protection group, follow the "Move Protection Group Traffic with a Switch Command" procedure.

Step 5 Perform a CTC reset on the reporting card. Use the "Reset a 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 card in CTC.

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

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 7 If the alarm does not clear, physically reseat the reporting card. Use the "Physically Reseat a Card" procedure.

Step 8 Follow the "Clear a Protection Group Switch Command" procedure.

Step 9 If the reporting traffic card is protect, perform a CTC reset on the reporting card. Use the "Reset a 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 card in CTC.

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

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 11 If the alarm does not clear, physically reseat the reporting card. Use the "Physically Reseat a Card" procedure.

Step 12 If the alarm does not clear, replace the standby cross-connect card. Use the "Physically Replace a Card" procedure.


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


Step 13 If the alarm does not clear, replace the reporting traffic card. Use the "Physically Replace a Card" procedure.

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.


1.6.30 CTNEQPT-PBWORK

Critical (CR), Service Affecting (SA)

The Interconnection Equipment Failure Protect Payload Bus alarm affects the main payload bus between the active cross-connect XC10G card in Slot 8 and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, or the backplane.


Note If all traffic cards show this alarm, do a forced side switch on the active TCC-I card, as shown in Step 1, and physically reseat this TCC-I card. If this fails to clear the alarm, replace the TCC-I card. Do not physically reseat an active TCC-I card because it 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 Follow the "Side-Switch the Active and Standby Cross-Connect Card" procedure to move traffic from the active card to the standby cross-connect card.


Note After the active cross-connect goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.


Step 2 Perform a CTC reset on the reporting card. Use the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 4 If the alarm does not clear, physically reseat the standby cross-connect card. Use the "Physically Reseat a Card" procedure.


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


Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, follow the "Move Protection Group Traffic with a Switch Command" procedure.

Step 6 Perform a CTC reset on the reporting card. Use the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 8 If the CTC reset does not clear the alarm, physically reseat the reporting card. Use the "Physically Reseat a Card" procedure.

Step 9 Follow the "Clear a Protection Group Switch Command" procedure.

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


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, replace the reporting traffic card. Use the "Physically Replace 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 in order to report a service affecting problem.


1.6.31 DATAFLT

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

The Software Fault or Data Integrity Fault alarm means that the database has exceeded the capacity of the Flash memory on the TCC-I.


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

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.

1.6.32 E3-ISD

Not Alarmed (Condition)

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. This condition occurs when the transmitting card is OOS-MNT. It is resolved when the OOS condition ends.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.33 EHIBATVG-A

Major (MJ), Service Affecting (SA)

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.

The problem is external to the ONS 15454 SDH. Troubleshoot the power source for battery lead A. 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.

1.6.34 EHIBATVG-B

Major (MJ), Service Affecting (SA)

The Extreme High Voltage on Battery B alarm occurs when the voltage level on battery lead B exceeds -56.7 VDC in -48 V DC 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.

The problem is external to the ONS 15454 SDH. Troubleshoot the power source for battery lead B. 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.

1.6.35 ELWBATVG-A

Major (MJ), Service Affecting (SA)

The Extreme Low Voltage on Battery Feed A alarm indicates 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.

The problem is external to the ONS 15454 SDH. Troubleshoot the power source for battery lead A. 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.

1.6.36 ELWBATVG-B

Major (MJ), Service Affecting (SA)

The Extreme Low Voltage on Battery Feed B alarm indicates 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 V DC in -48 V DC systems or -50 V DC in -60 V DC systems. The alarm clears when voltage has remained above -40.5 Vdc for 120 seconds.

The problem is external to the ONS 15454 SDH. Troubleshoot the power source for battery lead B. 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.

1.6.37 EOC

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

The Termination Failure DCC alarm means the ONS 15454 SDH has lost the 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 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 for the laser to be on. The laser is off when the safety key is off (labeled 0).



Warning Invisible laser radiation may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may 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 EOC Alarm


Step 1 If an LOF (DS3, E-N, STM-N) alarm is also reported, first resolve the LOS alarm by following the troubleshooting procedure given for that alarm.

Step 2 If the alarm does not clear, on the node reporting the alarm, check the physical connections from the cards to 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 ports by checking that the ACT LED on each STM-N card is on.

Step 4 If the ACT LEDs on CN-N cards are on, follow the "Check or Create Node SDCC 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 by viewing CTC or viewing the physical card.

A green LED indicates an active card. A yellow 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 7 If the STM-N card is in service, use an optical test set to check for signal failures on fiber terminations.

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


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

Step 8 If there are no signal failures on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. See the Cisco ONS 15454 SDH Installation and Operations Guide for levels.

Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. Refer to the Cisco ONS 15454 SDH Installation and Operations Guide for more information.

Step 10 If fiber connectors are properly fastened and terminated, reset the active TCC-I by following the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC-I does not reset itself. If the TCC-I reset is not complete and error-free or if the TCC-I reboots itself, 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 If CTC stops responding after performing a reset on the TCC-I, close the browser and start CTC again on the affected node.


Resetting the active TCC-I switches the traffic to the standby TCC-I. If the alarm clears when the ONS 15454 SDH switches to the standby TCC-I, the user can assume that the original active TCC-I is the cause of the alarm.

Step 11 If resetting the TCC-I does not clear the alarm, replace the original active TCC-I with a new TCC-I card. Use the "Physically Replace a Card" procedure.


Caution Resetting the active TCC-I can result in loss of traffic.

Step 12 If the TCC-I replacement does not clear the alarm, delete the problematic SDCC termination.

a. Click the Provisioning > SDH DCC tabs.

b. Highlight the problematic SDCC termination.

c. Click Delete.

d. Click Yes at confirmation dialog box.

Step 13 Recreate the SDCC termination.

Step 14 Verify that both ends of the SDCC have been recreated at the optical ports.

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


1.6.38 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 is raised with a BKUPMEMP alarm, complete the procedure in the "BKUPMEMP" section. This procedure clears both the EQPT alarm and the BKUPMEMP 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 Perform a CTC reset on the reporting card. Use the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 3 If the CTC reset does not clear the alarm, physically reseat the card. Use the "Physically Reseat a Card" procedure.

Step 4 If the physical reseat of the card fails to clear the alarm, replace the card. Use 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 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.


1.6.39 EQPT-MISS

Critical (CR), Service Affecting (SA)

The Replaceable Equipment Unit is Missing alarm is reported against the fan-tray assembly unit. It indicates that a replaceable fan-tray assembly unit 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 object, check that the fan-tray assembly is present.

Step 2 If the fan-tray assembly is present, follow the "Physically Reseat Fan-Tray" procedure.

Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and refer to "Replace the Fan-Tray Assembly" procedure on page 4-4.

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.


1.6.40 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/port misconnected to another East slot/port or a West slot/port misconnected to another West slot/port. In most cases, the user did not connect the fiber cables correctly, or the ring provisioning plan was flawed. You can physically reconnect the fiber cable to the correct slot/ports 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. Although the CTC method clears the alarm, it 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 slot/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.


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 Display the CTC network view and label each of the nodes on the diagram with the same name that appears on the network map.

Step 3 Double-click each span to reveal the node name and slot/port for each end of the span.

Step 4 Label the span ends on the diagram with the same information.

For example, with Node 1/Slot12/Port1 - Node2/Slot6/Port1, label the end of the span that connects Node 1 and Node 2 at the Node 1 end "Slot 12/Port 1." Label the Node 2 end of that same span "Slot 6/ Port 1."

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

Step 6 Label the highest numbered slot at each node "East" and the lowest numbered slot at each node "West."

Step 7 Look at the diagram. You should see a clockwise pattern of West slots connecting to East slots for each span.

Step 8 If any span has an East-to-West or West-to-West connection, physically switch the fiber cable connectors from the card that does not fit the pattern to the card that will continue the pattern. This should clear the alarm.


Note The physical switch procedure is the recommend method of clearing this alarm. This method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slot/ports as East and West. This is useful when the misconnected node is not geographically near the troubleshooter.



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

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.


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


Step 1 Log into the misconnected node. This is the node with both ring fibers misconnected; it is in the middle of the two nodes that have one of two ring fibers misconnected.

Step 2 Click the Provisioning > MS-SPRing tabs.

Step 3 From the row of information for the fiber span, use 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 this information before proceeding to Step 4.

Step 4 From the View menu, choose 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 CTC node (default login) view and click the Maintenance > MS-SPRing tabs.

Step 7 Change the West Line pull-down menu to the slot/port you recorded for the east line in Step 3.

Step 8 Change the East Line pull-down menu to the slot/port 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.


1.6.41 EXCCOL

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

The Excessive 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 unit and CTC might be affected. The network management LAN is the data network connecting the workstation running the CTC software to the TCC-I card. This problem is external to the ONS 15454 SDH.

Procedure: Clear the EXCCOL Alarm

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


Step 1 Verify that the network device port connected to the TCC-I 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 TCC-I 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.


1.6.42 EXERCISE-RING-REQ

Not Alarmed (NA) (Condition)

The Exercise Request on Ring condition is raised when optical cards in a two-fiber MS-SPRing are tested without switching traffic using the EXERCISE RING command. The condition clears on its own.


Note This is a condition and not an alarm. It does not require troubleshooting.


1.6.43 EXERCISE-SPAN-REQ

Not Alarmed (NA) (Condition)

The Exercise Request on Span condition is raised when optical cards in a four-fiber MS-SPRing are tested without switching traffic using the EXERCISE SPAN command. The condition clears on its own.


Note This is a condition and not an alarm. It does not require troubleshooting.


1.6.44 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 Open the MIC-A/P card Maintenance tab to gather further information about this alarm.

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

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.


1.6.45 EXTRA-TRAF-PREEMPT

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

An Extra Traffic Preempted alarm is raised on STM-N cards because low-priority traffic directed to the protect system has been preempted. This is caused by a working system protection switch.

Procedure: Clear the EXTRA-TRAF-PREEMPT Alarm


Step 1 Verify that the protection switch has occurred by checking the ring map.

Step 2 If a ring switch has occurred, clear the alarm on the working system by following the appropriate alarm 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.


1.6.46 FAILTOSW

Not Alarmed (NA) (Condition)

The Failure to Switch to Protection condition is raised when a working electrical card cannot switch to the protect card in a 1:N protection group, because another working electrical card with a higher priority alarm, is switched over and monopolizing the lone protect card.

Procedure: Clear the FAILTOSW Condition


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


Note A higher priority alarm is an alarm raised on the working electrical card using the 1:N card protection group. This working electrical card is reporting an alarm, but not reporting a FAILTOSW alarm.


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. This card is the working electrical card using the 1:N card protection and not reporting FAILTOSW.

Replacing the working electrical card that is reporting the higher priority alarm allows traffic to revert back to this slot. This frees up the 1:N card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW alarm.


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.


1.6.47 FAILTOSW-HO

Not Alarmed (NA) (Condition)

The Failure to Switch to Protection-High Order Path condition is raised when a working (or protect) STM-N card carrying high-order (VC-4 or VC-3) traffic cannot switch to the protect (or working) card because another electrical 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. For information on viewing alarms, refer to the Cisco ONS 15454 SDH Installation and Operations  Guide. Clearing this alarm frees the protection card and clears the FAILTOSW-HO condition.


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


Step 2 If the condition does not clear, replace the working STM-N card that is reporting the higher priority alarm. Follow the "Physically Replace a Card" procedure. Replacing the working (or protect) STM-N card that is reporting the higher priority alarm allows traffic to revert back to this slot. This frees up the protect (or working) card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW-HO alarm.


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 in order to report a service affecting problem.


1.6.48 FAILTOSW-LO

Not Alarmed (NA) (Condition)

The Failure to Switch to Protection-Low-Order Path condition is raised when a working (or protect) STM-N card carrying low-order (VC-2 or VC-1) 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 Look up and clear the higher priority alarm. For information on viewing alarms, refer to the Cisco ONS 15454 SDH Installation and Operations Guide. Clearing this alarm frees up the protect (or working) card and clears the FAILTOSW-LO condition.


Note A higher priority alarm is an alarm raised on the working STM-N card using the protection group. This working STM-N card is reporting an alarm, but not reporting a FAILTOSW-LO alarm.


Step 2 Replace the working STM-N card that is reporting the higher priority alarm. Follow the "Physically Replace a Card" procedure. Replacing the working (or protect) STM-N card that is reporting the higher priority alarm allows traffic to revert back to this slot. This frees up the protect (or working) card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW-LO alarm.


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.


1.6.49 FAILTOSWR

Not Alarmed (NA) (Condition)

The Ring Fail to Switch to Protection condition signals an APS ring switch failure. FAILTOSWR clears when one of the following actions occurs: a higher priority event, such as a user-switch command occurs, the next ring switch succeeds, or the cause of the APS switch (such as a signal failure [ SF] or signal degrade [ SD] alarm) clears.


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



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


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


Step 1 Check to see that every node expected to be part of the ring is listed in the ring map.

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 drop-down list.

Step 2 If the condition does not clear, display the CTC network view.

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

Step 4 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 these STM-N cards are active and in service.

a. Confirm that the STM-N card shows a green LED by viewing CTC or viewing the physical card.

A green LED indicates an active card. A yellow 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 Verify fiber continuity to the ports on the recorded cards.

Step 7 Verify that the correct port is in service.

a. Confirm that the STM-N card shows a green LED by viewing CTC or viewing the physical card.

A green LED indicates an active card. A yellow 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.


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

Step 8 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 9 Clean the fiber according to site practice.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

Step 10 Verify that the power level of the optical signal is within the STM-N card's receiver specifications. The Cisco ONS 15454 SDH Installation and Operations Guide lists these specifications.

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

Step 12 Replace the protect standby STM-N card. Follow the "Physically Replace a Card" procedure.

Step 13 If the condition does not clear after you replace the MS-SPRing cards on this 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.


1.6.50 FAILTOSWS

Not Alarmed (NA) (Condition)

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

To clear the condition, follow the "Clear the FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration" 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.

1.6.51 FAN

Critical (CR), Service Affecting (SA)

The Failure of the Cooling-Fan Tray alarm indicates a problem with the fan-tray assembly. When the fan 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 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 Check the condition of the air filter to see if it needs replacement. Refer to the "Air Filter Inspection" section on page 4-2.

Step 2 If the filter is clean, follow the "Physically Reseat Fan-Tray" procedure.


Note The fan should run immediately when correctly inserted.


Step 3 If the fan does not run or the alarm persists, replace the fan tray. Follow the "Replace the Fan-Tray Assembly" procedure on page 4-4.

Step 4 If the replacement fan tray 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.


1.6.52 FE-EXERCISING-RING

Not Alarmed (NA) (Condition)

The Far-End Exercising Ring condition is raised when far-end optical cards in a two-fiber MS-SPRing are being tested without switching traffic using the EXERCISE RING command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS alarm. The condition clears on its own.


Note This is a condition and not an alarm. It does not require troubleshooting.


1.6.53 FE-EXERCISING-SPAN

Not Alarmed (NA) (Condition)

The Far-End Exercising Span condition is raised when far-end optical cards in a four-fiber MS-SPRing are being tested without switching traffic using the EXERCISE SPAN command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS alarm. The condition clears on its own.


Note This is a condition and not an alarm. It does not require troubleshooting.


1.6.54 FE-FRCDWKSWPR-RING

Not Alarmed (NA) (Condition)

The Far-End Ring Working Facility Forced to Switch to Protection condition is raised from a far-end node when a ring is forced from the working system to the protect system using the FORCE RING command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both of 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 AIS alarm from the DS3i-N-12 card in Slot 16 of Node 1 might link to the main AIS alarm from an DS3i-N-12 card in Slot 16 of Node 2.

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

Step 3 View and clear the main alarm. Refer to the "Clear an MS-SPRing Span Command" procedure 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.


1.6.55 FE-FRCDWKSWPR-SPAN

Not Alarmed (NA) (Condition)

The Far-End Working Facility Forced to Switch to Protection Span condition is raised from a far-end node when a span on a four-fiber MS-SPRing is forced from the working system to the protect system using the FORCE SPAN command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS 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-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 AIS alarm from the DS3i-N-12 card in Slot 16 of Node 1 might link to the main AIS alarm from an DS3i-N-12 card in Slot 16 of Node 2.

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

Step 3 View and clear the main alarm. Refer to the "Clear an MS-SPRing Span Command" procedure 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.


1.6.56 FE-LOCKOUTOFPR-SPAN

Not Alarmed (NA) (Condition)

The Far-End Span Far End Lockout of Protection condition is raised when a bidirectional line switch ring (BSLR) span is locked out of the protection system from a far-end node using the LOCKOUT SPAN command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS 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-LOCKOUTOFPR-SPAN Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm.

For example, an AIS alarm from the DS3i-N-12 card in Slot 16 of Node 1 might link to the main AIS alarm from an DS3i-N-12 card in Slot 16 of Node 2.

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

Step 3 Click the Maintenance > MS-SPRing tabs.

Step 4 Click the MS-SPRing row in the West Switch column to reveal a pull-down menu and choose CLEAR.

Step 5 Click Apply. Click Yes on the confirmation dialog boxes. (Two confirmations are displayed.)

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.


1.6.57 FE-MANWKSWPR-RING

Not Alarmed (NA) (Condition)

The Far-End Ring Manual Switch of Working Facility to Protect condition is raised 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 in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS 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-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 AIS alarm from the DS3i-N-12 card in Slot 16 of Node 1 might link to the main AIS alarm from an DS3i-N-12 card in Slot 16 of Node 2.

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

Step 3 View and clear the main alarm. Refer to the "Clear an MS-SPRing Span Command" procedure 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.


1.6.58 FE-MANWKSWPR-SPAN

Not Alarmed (NA) (Condition)

The Far-End Span Manual Switch of Working Facility to Protect condition is raised when an MS-SPRing span is switched from working to protect at the far end using the MANUAL SPAN command. The prefix FE in an alarm or condition message means the main alarm is occurring at the far-end node and not at the node reporting this AIS 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 link directly to the card reporting the FE alarm.

For example, an AIS alarm from the DS3i-N-12 card in Slot 16 of Node 1 might link to the main AIS alarm from an DS3i-N-12 card in Slot 16 of Node 2.

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

Step 3 View and clear the main alarm. Refer to the "Clear an MS-SPRing Span Command" procedure 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.


1.6.59 FEPRLF

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

The Far-End Protection Line Failure alarm means that there was an APS switching channel failure of signal on the protect card coming into the node.


Note The FEPRLF alarm only is raised on the ONS 15454 SDH when 1+1 bidirectional protection is used on optical 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 link directly to the card reporting the FE alarm.

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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section 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.


1.6.60 FORCED-REQ

Not Alarmed (NA) (Condition)

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 or working span to a protection card or protection span or vice versa. You do not need to clear this condition if you want the force switch to remain in place. To clear this condition, clear the force command.

Procedure: Clear the FORCED-REQ Condition


Step 1 Click the Maintenance tab.

Step 2 Click the Protection tab for a card or span switch.

Step 3 At Operation, click the drop-down arrow.

Step 4 Choose Clear and 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.


1.6.61 FORCED-REQ-RING

Not Alarmed (NA) (Condition)

The Force Switch Request on Ring condition applies to optical line cards when the FORCE RING command is applied to a two-fiber MS-SPRing to move traffic from the working system to the protect system, or vice versa.

To clear the condition, follow the "Clear the FORCED-REQ Condition" 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.

1.6.62 FORCED-REQ-SPAN

Not Alarmed (NA) (Condition)

The Force Switch Request on Span condition applies to optical line cards when the FORCE SPAN command is applied to an MS-SPRing to force traffic from working to protect or from protect to working.

To clear the condition, follow the "Clear the FORCED-REQ Condition" 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.

1.6.63 FRNGSYNC

Major (MJ), Service Affecting (SA)

The Free-Running Synchronization Mode alarm means that 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 that relies on an internal clock.

Procedure: Clear the FRNGSYNC Alarm


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

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 View and clear alarms related to the failures of the primary and secondary reference sources, such as SYNCPRI and SYSBOOT.

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.


1.6.64 FSTSYNC

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

A Fast-Start Synchronization Mode alarm raises when the ONS 15454 SDH is choosing a new timing reference. The previous timing reference has failed. This alarm disappears after approximately 30 seconds.


Note This is an informational alarm. No troubleshooting is required.


1.6.65 FULLPASSTHR-BI

Not Alarmed (NA) (Condition)

The Bidirectional Full Pass-Through active condition is raised on a non-switching node for an MS-SPRing 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.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.66 HITEMP

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

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

The Equipment Failure from High Temperature alarm means the temperature of the ONS 15454 SDH is above 50 degrees Celsius (122 degrees Fahrenheit).


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 on the upper-right corner. For an illustration of the LCD panel, refer to the Cisco ONS 15454 SDH Installation and Operations Guide.

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

Step 3 Physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454 SDH.

Step 4 Physically ensure that blank faceplates fill the ONS 15454 SDH empty slots. Blank faceplates help airflow.

Step 5 Check the condition of the air filter to see whether it needs replacement. Refer to the "Air Filter Inspection" section on page 4-2.

Step 6 If the filter is clean, follow the "Physically Reseat Fan-Tray" procedure.


Note The fan should run immediately when correctly inserted.


Step 7 If the fan does not run or the alarm persists, replace the fan tray. Follow the "Replace the Fan-Tray Assembly" procedure on page 4-4.

Step 8 If the replacement fan tray 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.


1.6.67 HLDOVRSYNC

Major (MJ), Service Affecting (SA)

Loss of the primary or secondary timing reference raises the Holdover Synchronization alarm. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS 15454 SDH. It also usually occurs during the selection of a new node reference clock. The 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 View and clear additional alarms that relate to timing, such as FRNGSYNC, FSTSYNC, HLDOVRSYNC, LOF (DS3, E-N, STM-N), LOS (DS-3, E-N, STM-N), MANSWTOINT, MANSWTOPRI, MANSWTOSEC, MANSWTOTHIRD, SYSBOOT, SWTOSEC, SWTOTHIRD, SYNC-FREQ (BITS, STM-N), SYNCPRI, SYSBOOT, and SYSBOOT.

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.


1.6.68 HP-RFI

Not Reported (NR) (Condition)

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 RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the RFI alarm 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 Check for alarms, especially LOS.

Step 3 View and clear the main alarm. Refer to the appropriate alarm section 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.


1.6.69 HP-TIM

Minor (MN), Service Affecting (SA)

The TIM High-Order Trace Identifier Mismatch Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. This alarm is caused when there is a mismatch between the transmitted and received J1 identifier byte in the SDH path overhead. The error can originate in 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, follow the procedure in the "SYNCPRI" 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.


1.6.70 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 or VC-3) path overhead. This alarm is caused when no C2 byte is received in the SDH path overhead.

Procedure: Clear the HP-UNEQ Alarm


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

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

a. Examine signal as near the reporting card as possible.

b. Examine the signal as near the output card as possible.

Step 2 If the output card signal is valid, follow the procedure in the "SYNCPRI" 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.


1.6.71 IMPROPRMVL

Critical (CR), Service Affecting (SA) (for active card)

Minor (MN), Non-Service Affecting (NSA) (for standby card)

The procedural error improper removal alarm means a card was physically removed from its slot before the card was deleted in CTC. The card does not need to be in service to cause this alarm. It only needs to be recognized by CTC and the TCC-I card. This 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 pull 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 CTC 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 to it, is paired in a working/protection scheme, has DCC enabled, or is used as a timing reference.


Step 3 If the card is in service, take the facility out of service.


Caution Before taking the facility out of service, ensure that no live traffic is present on the facility.

a. In the CTC node (default login) 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, delete the circuit.


Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.

a. At the CTC node view, click the Circuits tab.

b. Click the applicable circuit, i.e., the circuit that connects to the reporting card.

c. Click Delete.

Step 5 If the card is paired in a protection scheme, delete the protection group.

a. Click the Provisioning > Protection tabs.

b. Click the protection group of the reporting card.

c. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning.

a. Click the Provisioning > SDH DCC tabs.

b. Click the slots and ports listed in DCC terminations.

c. Click Delete and click Yes in the confirmation box that appears.

Step 7 If the card is used as a timing reference, change the timing reference.

a. Click the Provisioning > Timing tabs.

b. Click the Ref-1 menu.

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


1.6.72 INHSWPR

Not Alarmed (NA) (Condition)

The Inhibit Switch To Protect Request On Equipment condition is raised on line cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 protection scheme, traffic remains locked onto the working system. If the card is part of a1:N protection scheme, the traffic is not prevented from being switched to another card in the protection scheme unless each card was specifically locked on.

Procedure: Clear the INHSWPR Condition


Step 1 In the CTC node (default login) view, click the Maintenance > Protection tabs.

Step 2 Under the Protection Groups column, click the group containing the card that is reporting the INHSWPR condition. The Selected Group column lists the status of all cards or ports in the group.

Step 3 Click the card or port that says LOCKED OUT.

Step 4 If the card or port is locked, click the Unlock button.

Step 5 If the card or port is switched, click the Clear button.

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.


1.6.73 INHSWWKG

Not Alarmed (NA) (Condition)

The Inhibit Switch To Working Request On Equipment condition is raised on line cards when the ability to switch to working has been disabled. If the card is part of a 1:1 protection scheme, traffic remains locked on to the protect system. If the card is part of a1:N protection scheme, the traffic is not prevented from being switched to another card in the protection scheme unless each card was specifically locked on.

Procedure: Clear the INHSWWKG Condition


Step 1 In the CTC node (default login) view, click the Maintenance > Protection tabs.

Step 2 Under the Protection Groups column, click the group containing the card that is reporting the INHSWWKG condition. The Selected Group column lists the status of all cards or ports in the group.

Step 3 Click the card or port that says LOCKED OUT.

Step 4 If the card or port is locked, click the Unlock button.

Step 5 If the card or port is switched, click the Clear button.

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.


1.6.74 INVMACADR

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

The equipment failure Invalid MAC Layer Address alarm means the ONS 15454 SDH MAC address is invalid. The MAC address is permanently set into the ONS 15454 SDH chassis when it is manufactured. Do not attempt to troubleshoot an INVMACADR.

Procedure: Clear the INVMACADR Alarm

This is not a user-serviceable problem. 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.

1.6.75 KB-PASSTHR

Not Alarmed (NA) (Condition)

The K Bytes Pass-Through Active condition is raised on a non-switching node for an MS-SPRing ring when the protect channels on the node are not active, and the node is in K Byte Pass-Through State due to a FORCE SPAN command.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.76 LKOUTPR-S

Not Alarmed (NA) (Condition)

The Lockout of Protection condition is raised on a BSLR node when traffic is locked out of a working span using the LOCKOUT SPAN command.

To clear the condition, follow the "Clear an MS-SPRing Span Command" procedure. 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.

1.6.77 LKOUTWK-R

Not Alarmed (NA) (Condition)

The Lockout of Working condition is raised on a BSLR node when traffic is locked on a working ring using the LOCKOUT-REQ-RING command.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.78 LKOUTWK-S

Not Alarmed (NA) (Condition)

The Lockout of Working condition is raised on a BSLR node when traffic is locked on a working span using the LOCKOUT-REQ-SPAN command.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.79 LOCKOUT-REQ

Not Alarmed (NA) (Condition)

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 a SNCP at the path level. A lockout prevents protection switching from occurring. Clearing the lockout allows protection switching to take place again. Clearing the lockout switch request clears the LOCKOUT-REQ condition.

To clear the condition, follow the "Clear an SNCP Lockout" 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.

1.6.80 LOCKOUT-REQ-RING

Not Alarmed (NA) (Condition)

The Lockout Switch Request On Ring condition is raised when a LOCKOUT RING command is applied to an MS-SPRing to keep traffic locked out of either working or protect systems.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.81 LOCKOUT-REQ-SPAN

Not Alarmed (NA) (Condition)

The Lockout Switch Request On Span condition is raised when a LOCKOUT SPAN command is applied to an MS-SPRing to lock traffic out of either a working or protect span.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.82 LOF (BITS)

Major (MJ), Service Affecting (SA)

The Loss of Frame (LOF) alarm occurs when a port on the TCC-I 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. It also assumes the alarm is not appearing during node turn-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 LOF Alarm


Step 1 Verify that the line framing and line coding match between the BITS input and the TCC-I.

a. In CTC node (default login) 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. This 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 Coding to reveal a menu. Choose the appropriate coding.

f. Verify that the value listed in Framing matches the framing of the BITS timing source (either ESF or SF [D4]).

g. If the framing does not match, click Framing to reveal the menu. Choose the appropriate framing.


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 TCC-I, replace the TCC-I card. Follow the "Physically Replace a Card" procedure.


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.


1.6.83 LOF (DS3, E-N, STM-N)

Major (MJ), 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-N-14 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 Alarm on DS3, E-N, or STM-N Card


Step 1 Verify that the line framing and line coding between the E1-N-14 port and the signal source match.

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. Your network administrator has this information.

c. Display the card-level 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 Type and enter the correct type.

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


1.6.84 LOS (BITS)

Major (MJ), Service Affecting (SA)

The TCC-I card has an LOS from the BITS timing source. An LOS 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 Alarm


Step 1 Verify the wiring connection from the ONS 15454 SDH backplane BITS clock pin fields to the timing source.

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


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

Major (MJ), Service Affecting (SA)

An LOS for either a DS-3 port or a DS1-14 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.

Procedure: Clear the DS-3, E-N, or STM-N 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 by viewing CTC or viewing the physical card.

A green LED indicates an active card. A yellow 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 DS-N 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 such an alarm did not clear the LOS, replace the reporting card with the same type of card. Follow the "Physically Replace a Card" procedure.


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.


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

Not Alarmed (NA) (Condition)

A Loopback Facility condition occurs when a software facility loopback is active for a port on the reporting card.

Loopback is a commonly used troubleshooting technique. A signal is sent out on a link or part of the network and returned to the sending device. If the signal does not return or returns with errors, the test confirms that the problem is present in the tested link or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically narrow down the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1 or the "Identify Points of Failure on a Circuit Path" section on page 2-4.

Two types of loopbacks are available: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far-end equipment. You can provision loopbacks through CTC.


Caution The CTC permits loopbacks to be performed on an in-service circuit. This operation is service affecting.

Procedure: Clear the LPBKFACILITY Condition


Step 1 From the CTC node (default login) view, double-click the reporting card to display the card view.

Step 2 Click the Maintenance tab.

Step 3 Follow the "Clear a Loopback" 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.


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

Not Alarmed (NA) (Condition)

A Loopback Terminal condition occurs when a software facility loopback is active for a port on the reporting card.

Loopback is a commonly used troubleshooting technique. A signal is sent out on a suspect link or part of the network, and a signal comes back to the sending device. If the signal does not come back or returns with errors, the test confirms that the problem is present in the tested link or network part. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter can logically isolate the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.

Two types of loopbacks are available: Facility and Terminal. Facility loopbacks troubleshoot ports only and are generally performed locally or at the near end. Terminal loopbacks test ports and spans and are often used for remote sites or far end equipment. You provision loopbacks using CTC.

Procedure: Clear the LPBKTERMINAL Condition


Step 1 From the CTC node (default login) view, double-click the reporting card to display the card view.

Step 2 Click the Maintenance tab.

If the condition is reported against a DS3i-N-12 card, also click the DS1 tab.

Step 3 Follow the "Clear a Loopback" 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.


1.6.88 LPBKTERMINAL(G1000-4)

Not Alarmed (NA) (Condition)

A Loopback Terminal condition occurs when a software terminal loopback is active for a port on the reporting card.

Loopback is a commonly used troubleshooting technique. By setting up loopbacks on various parts of the network and excluding other parts, a troubleshooter logically isolates the source of the problem. For more information on loopbacks, see the "Network Troubleshooting Tests" section on page 2-1.

G1000-4 cards only support Terminal loopbacks. When a port is set in terminal loopback, the outgoing signal being transmitted is fed back 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; it is only fed back to the receive direction. Terminal loopbacks test ports and spans and are often used for remote sites or far-end equipment. Loopbacks are provisioned using CTC. CTC permits loopbacks on an in-service circuit. This operation is service affecting.

To clear the condition, follow the "Clear a Loopback" 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.

1.6.89 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. This alarm is caused when there is a mismatch between the transmitted and received V5 byte received in the SDH payload overhead.

Procedure: Clear the LP-PLM Condition


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

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

a. Examine signal as close to the reporting card as possible.

b. Examine the signal as close as possible to the card.

Step 2 If the output card signal is valid, follow the procedure in the "SYNCPRI" 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.


1.6.90 LP-RFI

Not Reported (NR) (Condition)

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 RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the RFI alarm 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 Check for alarms, especially LOS.

Step 3 View and clear the alarms. Refer to the appropriate alarm section 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.


1.6.91 LP-UNEQ

Critical (CR), 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. This alarm is caused when no V5 byte is received in the SDH payload overhead.

To clear the alarm, follow the "Clear the LP-PLM Condition" procedure. 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.

1.6.92 MAN-REQ

Not Alarmed (NA) (Condition)

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

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.93 MANRESET

Not Alarmed (NA) (Condition)

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 alarm. This condition clears automatically, when the card finishes resetting.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.94 MANSWTOINT

Not Alarmed (NA) (Condition)

The Manual Switch To Internal Clock condition occurs when the NE timing source is manually switched to the internal timing source.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.95 MANSWTOPRI

Not Alarmed (NA) (Condition)

The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary source.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.96 MANSWTOSEC

Not Alarmed (NA) (Condition)

The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to the secondary source.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.97 MANSWTOTHIRD

Not Alarmed (NA) (Condition)

The Manual Switch To Third Reference condition occurs when the NE timing source is manually switched to the third source.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.98 MANUAL-REQ-RING

Not Alarmed (NA) (Condition)

The Manual Switch Request On Ring condition occurs when a user initiates a MANUAL RING command on a two-fiber MS-SPRing ring to switch from working to protect or protect to working.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.99 MANUAL-REQ-SPAN

Not Alarmed (NA) (Condition)

The Manual Switch Request On Ring condition occurs when a user initiates a MANUAL SPAN command to move MS-SPRing traffic from a working span to a protect span, or vice versa.

To clear the condition, follow the "Clear an MS-SPRing Span Command" 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.

1.6.100 MEA (Bplane)

Critical (CR), Service Affecting (SA)

The Mismatch of Equipment Attributes (MEA) alarm for the backplane means that the revision of the backplane is incompatible with XC10G equipment.

Procedure: Clear the MEA Alarm


Step 1 If the MEA is also raised against other equipment, such as the AIP or a fan tray, 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. At the CTC node (default login) view, click the Inventory tab.

b. Under the Hardware 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 Hardware 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.


1.6.101 MEA (EQPT)

Critical (CR), Service Affecting (SA)

The Mismatch of Equipment Attributes alarm occurs when the physical card inserted in a slot does not match the card type that is provisioned for that slot in CTC. The alarm clears when the provisioned card type and the physical card type match.

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. At the CTC node (default login) view, click the Inventory tab.

b. Under the Hardware 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 Hardware Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.

Step 2 Read the name at the top of the card faceplate to physically verify that the type of card in the slot is the same type of card that is reported in the object column of the MEA row on the Alarms tab.

a. If you have a newer ETSI 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) and the card reporting the alarm is not an E1000-2-G or E100T-G, proceed to Step 3.

b. If you have a newer ETSI 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) and the card reporting the alarm is an E1000-2-G or E100T-12, then that version of the Ethernet card is incompatible and must be removed.


Note The E1000-2-G and E100T-G cards are compatible with the newer ETSI 10-Gbps-compatible shelf assembly and are the functional equivalent of the older, non-compatible E1000-2 and E100T-12 cards. E1000-2-G and E100T-G cards can be used as replacements for E1000-2 and E100T-12 cards in a ETSI 10-Gbps-compatible shelf assembly.


c. If you have an older, pre-ETSI shelf assembly and the card reporting the alarm is not a card introduced in Release 3.1 or later (which includes the XC10G, OC-192, E1000-2-G, E100T-G or OC-48 any slot [AS]), proceed to Step 3.

d. If you have an older, pre-ETSI shelf assembly and the card reporting the alarm is a card introduced in Release 3.1 or later (which includes the XC10G, OC-192, E1000-2-G, E100T-G or OC-48 AS), the reporting card is incompatible with the shelf assembly and must be removed.

Step 3 On CTC, click the Inventory tab to reveal the provisioned card type.

Step 4 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). Follow the "Physically Replace a Card" procedure.

Step 5 If you prefer the card that physically occupies the slot and the card is not in service, has no circuits mapped to it and is not part of a protection group, then 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 to it, is paired in a working/protection scheme, has DCC communications enabled, or is used as a timing reference, then CTC does not allow you to delete the card.


Step 6 If the card is in service, take the facility out of service.


Caution Before taking the facility out of service, ensure that no live traffic exists on the facility.

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

d. Choose OOS to take the ports out of service.

Step 7 If a circuit has been mapped to the card, follow the "Delete a Circuit" procedure.


Caution Before deleting the circuit, ensure that no live traffic exists on the facility.

Step 8 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 9 Right-click the card reporting the alarm.

Step 10 Choose Delete.

The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.

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


1.6.102 MEA (FAN)

Critical (CR), Service Affecting (SA)

The Mismatch of Equipment Attributes alarm is reported against the fan tray 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. At the CTC node (default login) view, click the Inventory tab.

b. Under the Hardware Part # column, if the number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454-SA-10G).

c. Under the Hardware 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 follow the "Replace the Fan-Tray Assembly" procedure on page 4-4.

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 follow the "Replace the Fan-Tray Assembly" section on page 4-4.

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.


1.6.103 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 TCC-I card. CTC will not function properly until this alarm clears. The alarm clears when additional memory becomes available.

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.

1.6.104 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 TCC-I card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the TCC-I card is exceeded, CTC ceases to function.

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.

1.6.105 MFGMEM

Critical (CR), Service Affecting (SA)

The Manufacturing Data Memory Failure (MFGMEM) alarm raises 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 TCC-I lost the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. The EEPROM on the AIP also stores the MAC address. 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 AIP


Step 1 Perform a CTC reset on the TCC-I card. Follow the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC-I does not reset itself. If the TCC-I reset is not complete and error-free or if the TCC-I 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 TCC-I, close the browser and start CTC again on the affected node.


Step 2 If the alarm does not clear, perform a card pull reset on the TCC-I by referring to the "Reset the TCC-I using a Card Pull" procedure on page 4-7.

Step 3 If the alarm does not clear, physically replace the standby TCC-I card on the ONS 15454 SDH with a new TCC-I card. Follow the "Physically Replace a Card" procedure.


Note It takes up to 30 minutes for the active TCC-I to transfer the system software to the newly installed TCC-I. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC-I LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC-I reboots and goes into standby mode after approximately three minutes.


Step 4 Reset the active TCC-I card. Follow the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC-I does not reset itself. If the TCC-I reset is not complete and error-free or if the TCC-I 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 TCC-I card with the second TCC-I card. Follow the "Physically Replace a Card" procedure.

The ONS 15454 SDH boots up the second TCC-I card. The second TCC-I 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 TCC-I cards, the problem lies in 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.


1.6.106 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. This occurs when either the memory module on the component fails or the TCC-I 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


Step 1 Perform a CTC reset on the TCC-I card. Follow the "Reset Active TCC-I Card and Activate Standby Card" procedure.


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


Step 2 If the alarm does not clear, perform a card pull reset on the TCC-I by referring to the "Reset the TCC-I using a Card Pull" section on page 4-7.

Step 3 Physically replace the remaining TCC-I card with the second TCC-I card. Follow the "Physically Replace a Card" procedure.


Note It takes up to 30 minutes for the active TCC-I to transfer the system software to the newly installed TCC-I. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC-I LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC-I reboots and goes into standby mode after approximately three minutes.


Step 4 Perform a CTC reset on the TCC-I card. Follow the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Step 5 Verify that the remaining TCC-I card is now in standby mode. (The ACT/STBY LED changes to amber.)

Step 6 Physically replace the remaining TCC-I card with the second TCC-I card. Follow the "Physically Replace a Card" procedure.

Step 7 If the MFGMEM alarm continues to report after replacing the TCC-I cards, the problem lies in the EEPROM.

Step 8 If the MFGMEM is reported from the fan tray, replace the fan tray. Obtain a fan-tray assembly and follow the "Replace the Fan-Tray Assembly" procedure on page 4-4.

Step 9 If the MFGMEM is reported from backplane, or if the alarm persists after the fan tray 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.


1.6.107 MS-AIS

Not Reported (NR) (Condition)

The Multiplex Section AIS condition indicates that there is a defect at the line 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.

This condition 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, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an out-of-service 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 it is at fault.

Procedure: Clear the MS-AIS Condition


Step 1 View the main alarm.

Step 2 Clear the main alarm. Refer to the appropriate alarm section for instructions.

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.


1.6.108 MS-RFI

Not Reported (NR) (Condition)

The Multiplex Section (MS) Remote Fault Indication (RFI) condition indicates that the RFI condition is occurring at the line level. The line layer is 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. The line layer functions include multiplexing and synchronization.

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 Check for alarms, especially LOS.

Step 3 View and clear the main alarm. Refer to the appropriate alarm section 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.


1.6.109 MSSP-OOSYNC

Major (MJ), Service Affecting (SA)

The Procedural Error MS-SPRing Out of Synchronization alarm applies to the SDH NE ring. This alarm is caused when a node ring map is missing or changed.


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



Warning Invisible laser radiation may 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 Verify that each node has a unique node ID number by using the "Identify a Ring ID or Node ID Number" procedure.

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

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

Step 3 If the ring map does not exist, click Create.

Step 4 Create the ring. Choose two- or four-fiber, the node ID, and the East or West optical card as required.

Step 5 Click Yes on the Create MSSPRing dialog box.

Step 6 Check the fiber connections.

Step 7 Clean the fiber according to site practice.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

Step 8 Follow the procedure in the "SYNCPRI" section.

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.


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


1.6.111 PRC-DUPID

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

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 with 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, use the "Change a Ring ID Number" procedure o change one node ID number 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.


1.6.112 PROTNA

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

The Protection Unit Not Available alarm is raised by an out-of-service protection card when a TCC-I or XC10G card or port that is provisioned as part of a protection group is not available. This can occur when a card is reset, but clear 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 raises against a common control (TCC-I or XC10G) card and does not clear, ensure that a redundant control card is installed and provisioned in the chassis.

Step 2 If the alarm is raised against a line card, check whether the facility has been taken out of service.

a. In CTC, double-click the reporting card to display the card view (if the card is not an XC10G card).

b. Click the Provisioning tab.

c. Click the State column of any in-service ports.

d. Choose IS to take the ports out of service.

Step 3 Perform a CTC reset on the reporting card. Follow the "Reset a 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 card in CTC.

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

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 5 If the alarm persists, physically reseat the reporting card. Follow the "Physically Reseat a Card" 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.


1.6.113 PWR-A

Major (MJ), Service Affecting (SA)

The NE Power Failure at Connector A alarm applies to the NE rack. This alarm is caused when no power is supplied to the main power connector. This alarm can be raised if power is connected to the backup power connector (connector B) but not to connector A, since 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 Verify whether a power connection between the power source and power connector A is present.

Step 2 Verify and reseat, if necessary, 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 Installation and Operations 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 Installation and Operations 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.


1.6.114 PWR-B

Major (MJ), Service Affecting (SA)

The NE Power Failure at Connector B alarm applies to the NE rack. This alarm is caused when no power is supplied to the backup power connector. This alarm can be raised if power is connected to the main power connector (connector A) but not to connector B, since 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 Check whether a power connection is present between the power source and power connector B.

Step 2 Check and reseat, if necessary, 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 Installation and Operations 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 Installation and Operations  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.


1.6.115 RAI

Not Alarmed (NA) (Condition)

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 DS3i-N-12 card indicates that far-end node is receiving a DS-3 or E-1AIS.

To clear the condition, follow the "AIS" 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.

1.6.116 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 Check the ring ID. Follow 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 Check the ring ID. Follow 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 If the ring ID does not match the ring ID in the reporting ONS node, follow the "Change a Ring ID Number" procedure.

Step 8 Verify that the ring map is correct.

Step 9 Repeat Step 7 for all ONS nodes in the MS-SPRing.

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.


1.6.117 RING-SW-EAST

Not Alarmed (NA) (Condition)

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 This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.118 RING-SW-WEST

Not Alarmed (NA) (Condition)

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 This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.119 SD

Not Alarmed (NA) (Condition)

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

A 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. The condition travels on the B2 byte of the multiplexing section SDH overhead.

The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered the alarm. 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.


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



Warning Invisible laser radiation may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may 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. Follow the "Verify BER Threshold Level" procedure.

Step 2 With an optical test set, measure the power level of the line to ensure it 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 Clean the fiber according to site practice.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

Step 5 Verify that single-mode fiber is used.

Step 6 Verify that a single-mode laser is used at the far end.

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.


1.6.120 SDBER-EXCEED-HO

Not Alarmed, Service Affecting (SA)

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 or VC-3) path on optical cards. This alarm is caused 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 may 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 Alarm


Step 1 Determine the BER threshold. Follow the "Verify BER Threshold Level" procedure.

Step 2 If it is acceptable in site practices, adjust the threshold.

Using an optical test set, measure the input power level of the line and ensure it is within the guidelines.

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

Step 3 Check input fiber cable connections to the reporting card.

Step 4 Clean the input fiber cable ends according to site practices.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

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.


1.6.121 SF

Not Alarmed (NA) (Condition)

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 alarm travels on the B2 byte of the multiplexing section SDH overhead; this alarm causes a protection switch at the line (facility) level.

The SF alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm. 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 Telcordia 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 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).



Warning Invisible laser radiation may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may 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. Follow the "Verify BER Threshold Level" procedure.

Step 2 Using an optical test set, measure the power level of the line and ensure it 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, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

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.


1.6.122 SFBER-EXCEED-HO

Not Alarmed, Service Affecting (SA)

The Signal Failure Threshold Exceeded for High Order condition means that the signal fail BER threshold has been exceeded for a high-order (VC-4 or VC-3) path on optical cards. This alarm is caused 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 may 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 alarm, and clicking the Provisioning tab.

Step 2 If it is acceptable in site practices, adjust the threshold.

Step 3 Check the input power levels to the reporting card.

Step 4 Check input fiber cable connections to the reporting card.

Step 5 Clean the input fiber cable ends according to site practices.

If no practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

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.


1.6.123 SFTWDOWN

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

A Software Download in Progress alarm occurs when the TCC-I 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 It can take up to 30 minutes for software to be updated on a standby TCC-I card. Wait the full time period before removing the card. Premature removal can cause Flash corruption.


Note This is an informational alarm.


1.6.124 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. This 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 supplying 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. On the ONS node serving as the proxy, click the CTC 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.


1.6.125 SPAN-SW-EAST

Not Alarmed (NA) (Condition)

The Span Switch is Active on the East Side condition occurs when a force switch occurs at the east side of a four-fiber MS-SPRing span. The condition clears when the switch is cleared.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.126 SPAN-SW-WEST

Not Alarmed (NA) (Condition)

The Span Switch is Active on the West Side condition occurs when a force switch occurs at the west side of a four-fiber MS-SPRing span. The condition clears when the switch is cleared.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.127 SQUELCH

Not Alarmed (NA) (Condition)

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 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 OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).



Warning Invisible laser radiation may 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 may pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified may 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 by viewing CTC or viewing the physical card.

A green LED indicates an active card. A yellow 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 card's receiver specifications. Refer to the Cisco ONS 15454 SDH Installation and Operations Manual for card specifications.

Step 6 Ensure that the optical transmits and receives are connected properly.

Step 7 Replace the STM-N card. Follow the "Physically Replace a Card" procedure.

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.


1.6.128 SSM-DUS

Not Alarmed (NA) (Condition)

The Synchronization Status Message 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. This type of signal can also be sent for line maintenance testing.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.129 SSM-FAIL (BITS)

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

The Failed to Receive Synchronization Status Message alarm means 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 Alarm


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


1.6.130 SSM-FAIL (STM-N)

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

The Failed to Receive Synchronization Status Message alarm means 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 Alarm


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


1.6.131 SSM-LNC

Not Alarmed (Condition)

The Local Node Clock (LNC) Traceable SSM condition means that the SSM (S1) byte of the SDH overhead multiplexing section has been changed to signify that the line or BITS timing source is LNC.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.132 SSM-OFF (BITS)

Not Alarmed (NA) (Condition)

The SSM Disabled on this Interface condition applies to references used for timing the node. It 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, follow the "Clear the SSM-FAIL 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.

1.6.133 SSM-OFF (STM-N)

Not Alarmed (NA) (Condition)

The SSM Disabled on this Interface condition indicates that the SSM (S1) byte of the SDH multiplexing section overhead has been turned off. It applies to optical line cards. It 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, follow the "Clear the SSM-FAIL 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.

1.6.134 SSM-PRC

Not Alarmed (Condition)

The Primary Reference Clock (PRC) Traceable SSM condition means that the SDH overhead multiplexing section S1 byte indicates the line or BITS timing source SSM has changed to PRC.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.135 SSM-SETS

Not Alarmed (NA) (Condition)

The Synchronous Equipment Timing Source Traceable SSM condition means that the SSM (S1) byte indicates the line or BITS timing source has changed to SETS.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.136 SSM-STU (BITS)

Not Alarmed (NA) (Condition)

The SSM Synchronization Traceability Unknown (STU) 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 be raised if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15454 SDH.

SSM is a 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. SSM enables SDH devices to automatically choose the highest quality timing reference and to avoid timing loops.

Procedure: Clear the STU 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.


1.6.137 SSM-STU (STM-N)

Not Alarmed (NA) (Condition)

The SSM Synchronization Traceability Unknown 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 be raised if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15454 SDH.

SSM is a 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. SSM enables SDH devices to automatically choose the highest quality timing reference and to avoid timing loops.

Procedure: Clear the STU 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.


1.6.138 SSM-TNC (BITS)

Not Alarmed (NA) (Condition)

The SSM Transit Node Clock (TNC) Traceable condition occurs when the SSM quality level is changed to TNC.

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.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.139 SSM-TNC (STM-N)

Not Alarmed (NA) (Condition)

The SSM Transit Node Clock Traceable condition occurs when the SSM quality level is changed to TNC.

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.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.140 SWMTXMOD

Critical (CR), Service Affecting (SA)

The Switching Matrix Module Failure alarm occurs on the XC10G card or an I/O card. If the alarm reports against an I/O card, it means that the logic component on the cross-connect card is out of frame (OOF) with the logic component on the reporting I/O card. All traffic on the reporting I/O card is lost. If the alarm reports against an XC10G card, it means that a logic component internal to the reporting XC10G card is out of frame with a second logic component on the same XC10G card. One or more I/O 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 XC10G card, perform a CTC reset on the standby XC10G. Follow the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 3 If the alarm persists, physically reseat the standby XC10G card. Follow the "Physically Reseat a Card" procedure.

Step 4 If the card reporting the alarm is the active XC10G card, follow the "Side-Switch the Active and Standby Cross-Connect Card" procedure to move traffic from the active XC10G card to the standby XC10G card.


Note After the active cross-connect goes into standby, the original standby slot becomes active. This causes the ACT/STBY LED to become green on the former standby card.


Step 5 If the card reporting the alarm is not the active XC10G card or if you completed the side switch in Step 4, perform a CTC reset on the reporting card. Follow the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 7 If the alarm persists, physically reseat the standby XC10G card. Follow the "Physically Reseat a Card" procedure.

Step 8 If the card reporting the alarm is an I/O card, follow the "Side-Switch the Active and Standby Cross-Connect Card" procedure to move traffic from the active cross-connect XC10G card to the standby cross-connect card.

Step 9 If the alarm does not clear after the cross-connect XC10G side switch, perform a CTC reset on the reporting card. Follow the "Reset a 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 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 on.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.

Step 11 If the alarm persists, physically reseat the reporting traffic/line card. Follow the "Physically 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 in order to report a service affecting problem.


1.6.141 SWTOPRI

Not Alarmed (NA) (Condition)

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 This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.6.142 SWTOSEC

Not Alarmed (NA) (Condition)

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, view and clear alarms related to failures of the primary source, such as the SYNCPRI alarm. 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.

1.6.143 SWTOTHIRD

Not Alarmed (NA) (Condition)

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, view and clear alarms related to failures of the primary source, such as the SYNCPRI and SYSBOOT alarms. 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.

1.6.144 SYNC-FREQ (BITS, STM-N)

Not Alarmed (NA) (Condition)

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 Condition


Step 1 Use an optical test set to check the timing frequency of the line or BITS timing source and ensure that it 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 TCC-I card. Follow the "Physically Replace a Card" procedure.

Step 3 If the SYNC-FREQ condition continues to report after replacing the TCC-I 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.


1.6.145 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). This switch also triggers the SWTOSEC alarm.

Procedure: Clear the SYNCPRI Condition


Step 1 From the CTC node (default login) view, click the Provisioning > Timing tabs.

Step 2 Check 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 Check 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 procedure in the "LOF (DS3, E-N, STM-N)" section.

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.


1.6.146 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. This switch also triggers the SWTOTHIRD alarm.

Procedure: Clear the SYNCSEC Alarm


Step 1 From the CTC node (default login) view, click the Provisioning > Timing tabs.

Step 2 Check 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 Check 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 procedure in the "LOS (BITS)" section.

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.


1.6.147 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 TCC-I card may have failed. The ONS 15454 SDH often reports either FRNGSYNC or HLDOVERSYNC alarms 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 From CTC node (default login) view, click the Provisioning > Timing tabs.

Step 2 Check the current configuration of the REF-3 for the NE Reference. For more information about references, refer to the Cisco ONS 15454 SDH Installation and Operations Guide.

Step 3 If the third timing source is a BITS input, follow the procedure in the "LOS (BITS)" section.

Step 4 If the third timing source is an incoming port on the ONS 15454 SDH, follow the procedure in the "LOF (DS3, E-N, STM-N)" section.

Step 5 If the third timing source uses the internal ONS 15454 SDH timing, perform a CTC reset on the TCC-I card. Follow the "Reset Active TCC-I Card and Activate Standby Card" procedure.

Wait ten minutes to verify that the standby TCC-I does not reset itself. If the TCC-I reset is not complete and error-free or if the TCC-I 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 TCC-I, close the browser and start CTC again on the affected node.


Step 6 If this fails to clear the alarm, physically reseat the TCC-I card. See the "Reset the TCC-I using a Card Pull" section on page 4-7.

Step 7 If the CTC reset fails to clear the alarm, replace the TCC-I card. Follow 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.


1.6.148 SYSBOOT

Major (MJ), Service Affecting (SA)

The System Reboot alarm indicates that new software is booting on the TCC-I card. This 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.

1.6.149 TPTFAIL

Major (MJ), Service Affecting (SA)

The Transport Layer Failure alarm indicates a break in the end-to-end Ethernet link integrity feature of the G1000-4 cards. This alarm indicates a far-end condition rather than a problem with the port reporting TPTFAIL.

This 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 alarm is on the SDH path used by the Ethernet port, the affected port raises a TPTFAIL alarm. If the far-end G1000-4 Ethernet port is administratively disabled or it is exhibiting a CARLOSS condition, it sets the C2 byte in the SDH path overhead to indicate a payload defect condition. This causes a TPTFAIL to be reported against this near-end port.

Another important point regarding a TPTFAIL condition is that the near-end port is automatically disabled (transmit laser turned off) when this condition occurs. This could cause the external Ethernet device attached at the near end to detect a downed link and turn off its transmitter. In turn, this would cause a CARLOSS condition on this port. In all cases the real problem is either in the SDH path being used by this G1000-4 port or in the far-end G1000-4 port to which it is mapped.

Procedure: Clear the TPTFAIL Alarm


Step 1 An occurrence of TPTFAIL on a G1000-4 port indicates either a problem with the SDH path that this port is using or with the far end G1000-4 port that is mapped to this port. View and clear any alarms being reported by the STM-N card utilized by the Ethernet circuit of the G1000-4.

Step 2 If no alarms are reported by the STM-N card, the problem might be on the far-end G1000-4 port that the port reporting TPTFAIL is mapped to. Lookup and troubleshoot 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 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.


1.6.150 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. Follow 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 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.


1.6.151 TU-AIS

Not Reported (NR) (Condition)

A Tributary Unit AIS means that there is an AIS, indicating a secondary condition, in the tributary overhead of the VC.

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, loss of frame, bit error signal degrade or failure, trace identifier mismatch, or an out-of-service 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 it is at fault.

Procedure: Clear the TU-AIS Condition


Step 1 Check upstream nodes and equipment for alarms, especially for LOS and out-of-service ports.

Step 2 View and clear the alarms. Refer to the appropriate alarm section for the 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.


1.6.152 TU-LOP

Not Reported (NR) (Condition)

A Tributary Unit LOP means that the first payload pointer in the SDH overhead is not synchronized according to the system clock.


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



Warning Invisible laser radiation may 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 Check for LOS on the reporting card.

Step 2 On the card raising the alarm, check whether attenuation is present on the input fiber cable.

Step 3 Check the signal level on the input fiber with the attenuator (if present).

Step 4 If fiber signal level with the attenuator is below the correct threshold, remove the attenuator and check signal level again.

Step 5 If the signal level is still low, clean both ends of the fiber cable connection according to site practice.

If no site practice exists, follow the "Clean and Scope Fiber Connectors, Using Alcohol and Dry Wipes" procedure on page 4-36 or the "Clean and Scope Fiber Connectors, Using Cletop" procedure on page 4-36, as appropriate.

Step 6 Clean the far-end optical fiber cable ends.

Step 7 If error remains, check for a timing alarm. Follow the procedure in the "SYNCPRI" section.

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.


1.6.153 WKSWPR

Not Alarmed (NA) (Condition)

The Working Switched To Protection condition is raised when a line experiences an LOS, signal fail, or signal degrade.

To clear the condition, follow the procedure in the "LOS (DS-3, E-N, STM-N)" section. 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.

1.6.154 WTR

Not Alarmed (NA) (Condition)

The Wait To Restore condition indicates that the following conditions exist: revertive switching is specified, a WKSWPR occurred, and although the working path is good again, the wait to restore the timer has not expired. The alarm clears when the timer expires and traffic is switched back to the working path.


Note This is a condition and not an alarm. It is for information only and does not require troubleshooting.


1.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 Installation and Operations 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 from the Nodes column, record the node IDs in the MS-SPRing. The node IDs are the numbers in parentheses next to the node name.


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 row of 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 at 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.

Step 6 Select Set Node ID from the shortcut menu.

Step 7 Enter the new ID in the field.

Step 8 Click Apply.


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: Check or Create Node SDCC Terminations


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

Step 3 View the Port column entries to see where terminations are present for a node. If all terminations are not present, proceed to Step 4.

Step 4 If necessary, create a DCC termination.

a. Click Create.

b. In the Create SDCC Terminations dialog box, click the ports where you want to create the DCC termination. To select more than one port, press the Shift key.

c. In the Port State area, click the Set to IS, if allowed radio button.

d. Verify that the Disable OSPF on DCC Link check box is unchecked.

e. Click OK.


Procedure: Lock Out an MS-SPRing Span


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 In the node (default CTC login view), click the Maintenance > MS-SPRing tabs.

Step 3 Click the MS-SPRing row table cell under the West Switch column to reveal the pull-down menu.

Step 4 Choose LOCKOUT SPAN and click Apply.

Step 5 Click OK on the MS-SPRing Operations dialog box.


Procedure: Clear an MS-SPRing Span Command


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 In the node (default CTC login view), click the Maintenance > MS-SPRing tabs.

Step 3 Click the MS-SPRing row table cell under the West Switch column to reveal the pull-down menu.

Step 4 Choose CLEAR and click Apply.

Step 5 Click OK on the MS-SPRing Operations dialog box.


Procedure: Clear an SNCP Lockout


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 Right-click the span where you want to clear the switch. Choose Circuits from the shortcut menu.

Step 4 On the Circuits on Span dialog box, choose CLEAR to remove a previously set switch command. Click Apply.

Step 5 In the Confirm SNCP Switch dialog box, click Yes.

Step 6 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span window, the Switch State for all SNCP circuits is CLEAR.


Procedure: Move Protection Group Traffic with a Switch Command


Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 Display the CTC node (default login) view.

Step 3 At the CTC node (default login) view, click the Maintenance > Protection tabs.

Step 4 Double-click the protection group that contains the reporting card.

Step 5 Click the Working/Active card of the selected groups.

Step 6 Click Switch.

Step 7 Click Yes in the Confirmation dialog box.


Procedure: Side-Switch the Active and Standby Cross-Connect Card


Step 1 Log into a node on the network if you have not done so already.

Step 2 Display the CTC node (default login) view.

Step 3 Determine the active cross-connect card.

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


Note You can also place the cursor over the card graphic to display a popup identifying the card as active or standby.


Step 4 In the CTC node view, select the Maintenance > XC Cards tabs.

Step 5 Click Switch.

Step 6 Click Yes in the Confirm Switch dialog box.


Procedure: Clear a Protection Group Switch Command


Step 1 Log into a node on the network if you have not done so already.

Step 2 Display the CTC node (default login) view.

Step 3 At the CTC node view, click the Maintenance > Protection tabs.

Step 4 Double-click the protection group that contains the reporting card.

Step 5 Highlight either selected group.

Step 6 Click Clear and click Yes at the confirmation dialog box.


Procedure: Delete a Circuit


Step 1 Log into a node on the network if you have not done so already.

Step 2 Display the CTC node (default login) view.

Step 3 Click the circuit row to highlight it and click Delete.

Step 4 Click Yes at the Delete Circuits dialog box.


Procedure: Clear a Loopback


Step 1 Log into a node on the network if you have not done so already.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance tab.

Step 4 In the Loopback Type column, look for any port row that displays a state other then None.

Step 5 If a row contains a state other than None, click in the column cell to display the drop-down list and select None.

Step 6 In the State column, look for any port row that displays a state other than INS.

Step 7 If a row contains a state other than INS, click in the column cell to display the drop-down list and select INS.

Step 8 Click Apply.


Procedure: Reset Active TCC-I Card and Activate Standby Card


Step 1 Log into a node on the network if you have not done so already.

Step 2 Identify the active TCC-I.

If you are looking at the physical ONS 15454 SDH, the ACT/STBY LED of active TCC-I is green.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, the standby TCC-I has a green LED depiction with the letters "Act."

Step 3 Right-click the active TCC-I.

Step 4 Choose Reset Card from the shortcut menu.

Step 5 Click Yes in the Are You Sure dialog box.

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 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 steadily lit amber.

If you are looking at the CTC node (default login) view of the ONS 15454 SDH, a yellow LED depiction with the letters "Sby" has replaced the white "LDG" LED.


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



Procedure: Reset a Card in CTC


Step 1 Log into a node on the network if you have not done so already.

Step 2 Display the CTC node (default login) view.

Step 3 Position the cursor over the slot reporting the alarm.

Step 4 Right-click and choose RESET CARD from the shortcut menu.


Procedure: Verify BER Threshold Level


Step 1 Log into a node on the network if you have not done so already.

Step 2 Display the CTC node (default login) view.

Step 3 From the CTC node view, double-click the card reporting the alarm to display the card view.

Step 4 Click the Provisioning > Line tabs.

Step 5 Under the SD BER column on the Provisioning tab, verify that the cell entry is consistent with what the system was originally provisioned for. The default setting is 1E-7.

Step 6 If the entry is consistent with what the system was originally provisioned for, continue to Step 8.

Step 7 If the entry is not consistent with what the system was originally provisioned for, click the cell to reveal the range of choices and click the entry that is consistent with what the system was originally provisioned for.

Step 8 Click Apply.


Procedure: Physically Replace a Card


Step 1 Open the card ejectors.

Step 2 Slide the card out of the slot.

Step 3 Open the ejectors on the replacement card.

Step 4 Slide the replacement card into the slot along the guide rails.

Step 5 Close the ejectors.


Procedure: Physically Reseat a Card


Step 1 Open the card ejectors.

Step 2 Slide the card halfway out of the slot along the guide rails.

Step 3 Slide the card all the way back into the slot along the guide rails.

Step 4 Close the ejectors.


Procedure: Physically Reseat Fan-Tray


Step 1 Use the retractable handles embedded in the front of the fan tray to pull the fan-tray assembly forward several inches.

Step 2 Push the fan-tray assembly firmly back into the ONS 15454 SDH.

Step 3 Close the retractable handles.