Cisco ONS 15454 Troubleshooting Guide, Release 3.4
Chapter 2, Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

2.1 Alarm Index by Default Severity

2.1.1 Critical Alarms (CR)

2.1.2 Major Alarms (MJ)

2.1.3 Minor Alarms (MN)

2.1.4 Conditions (NA or NR)

2.2 Alarm Index By Alphabetical Entry

2.3 Alarm Index by Alarm Type

2.3.1 Alarm Type/Object Definition

2.4 Trouble Notifications

2.4.1 Conditions

2.4.2 Severities

2.5 Safety Summary

2.6 Alarm Procedures

2.6.1 AIS

2.6.2 AIS-L

2.6.3 AIS-P

2.6.4 AIS-V

2.6.5 APSB

2.6.6 APSCDFLTK

2.6.7 APSC-IMP

2.6.8 APSCINCON

2.6.9 APSCM

2.6.10 APSCNMIS

2.6.11 APSMM

2.6.12 AS-CMD

2.6.13 AS-MT

2.6.14 AUTOLSROFF

2.6.15 AUTORESET

2.6.16 AUTOSW-AIS

2.6.17 AUTOSW-LOP (STSMON)

2.6.18 AUTOSW-LOP (VT-MON)

2.6.19 AUTOSW-PDI

2.6.20 AUTOSW-SDBER

2.6.21 AUTOSW-SFBER

2.6.22 AUTOSW-UNEQ (STSMON)

2.6.23 AUTOSW-UNEQ (VT-MON)

2.6.24 BKUPMEMP

2.6.25 BLSROSYNC

2.6.26 CARLOSS (EQPT)

2.6.27 CARLOSS (E-Series)

2.6.28 CARLOSS (G1000-4)

2.6.29 CLDRESTART

2.6.30 COMIOXC

2.6.31 CONCAT

2.6.32  CONTBUS-A-18

2.6.33  CONTBUS-B-18

2.6.34  CONTBUS-IO-A

2.6.35  CONTBUS-IO-B

2.6.36 CTNEQPT-PBPROT

2.6.37 CTNEQPT-PBWORK

2.6.38 DATAFLT

2.6.39 DS3-MISM

2.6.40 EHIBATVG-A

2.6.41 EHIBATVG-B

2.6.42 ELWBATVG-A

2.6.43 ELWBATVG-B

2.6.44 EOC

2.6.45 EQPT

2.6.46 EQPT-MISS

2.6.47 E-W-MISMATCH

2.6.48 EXCCOL

2.6.49 EXERCISE-RING-REQ

2.6.50 EXERCISE-SPAN-REQ

2.6.51 EXT

2.6.52 EXTRA-TRAF-PREEMPT

2.6.53 FAILTOSW

2.6.54 FAILTOSW-PATH

2.6.55 FAILTOSWR

2.6.56 FAILTOSWS

2.6.57 FAN

2.6.58 FE-AIS

2.6.59 FE-DS1-MULTLOS

2.6.60 FE-DS1-NSA

2.6.61 FE-DS1-SA

2.6.62 FE-DS1-SNGLLOS

2.6.63 FE-DS3-NSA

2.6.64 FE-DS3-SA

2.6.65 FE-EQPT-NSA

2.6.66 FE-EXERCISING-RING

2.6.67 FE-EXERCISING-SPAN

2.6.68 FE-FRCDWKSWPR-RING

2.6.69 FE-FRCDWKSWPR-SPAN

2.6.70 FE-IDLE

2.6.71 FE-LOCKOUTOFPR-SPAN

2.6.72 FE-LOF

2.6.73 FE-LOS

2.6.74 FE-MANWKSWPR-RING

2.6.75 FE-MANWKSWPR-SPAN

2.6.76 FEPRLF

2.6.77 FORCED-REQ

2.6.78 FORCED-REQ-RING

2.6.79 FORCED-REQ-SPAN

2.6.80 FRCDSWTOINT

2.6.81 FRCDSWTOPRI

2.6.82 FRCDSWTOSEC

2.6.83 FRCDSWTOTHIRD

2.6.84 FRNGSYNC

2.6.85 FSTSYNC

2.6.86 FULLPASSTHR-BI

2.6.87 HITEMP

2.6.88 HLDOVRSYNC

2.6.89 IMPROPRMVL

2.6.90 INC-ISD

2.6.91 INHSWPR

2.6.92 INHSWWKG

2.6.93 INVMACADR

2.6.94 KB-PASSTHR

2.6.95 LKOUTPR-S

2.6.96 LOCKOUT-REQ

2.6.97 LOCKOUT-REQ-RING

2.6.98 LOCKOUT-REQ-SPAN

2.6.99 LOF (BITS)

2.6.100 LOF (DS1)

2.6.101 LOF (DS3)

2.6.102 LOF (EC1-12)

2.6.103 LOF (OC-N)

2.6.104 LOP-P

2.6.105 LOP-V

2.6.106 LOS (BITS)

2.6.107 LOS (DS-1)

2.6.108 LOS (DS-3)

2.6.109 LOS (EC1-12)

2.6.110 LOS (OC-N)

2.6.111 LPBKDS1FEAC

2.6.112 LPBKDS1FEAC-CMD

2.6.113 LPBKDS3FEAC

2.6.114 LPBKDS3FEAC-CMD

2.6.115 LPBKFACILITY (DS-N or EC1-12)

2.6.116 LPBKFACILITY (OC-N)

2.6.117 LPBKTERMINAL (DS-N, EC1-12, OC-N)

2.6.118 LPBKTERMINAL(G1000-4)

2.6.119 MAN-REQ

2.6.120 MANRESET

2.6.121 MANSWTOINT

2.6.122 MANSWTOPRI

2.6.123 MANSWTOSEC

2.6.124 MANSWTOTHIRD

2.6.125 MANUAL-REQ-RING

2.6.126 MANUAL-REQ-SPAN

2.6.127 MEA (AIP)

2.6.128 MEA (Bplane)

2.6.129 MEA (EQPT)

2.6.130 MEA (FAN)

2.6.131 MEM-GONE

2.6.132 MEM-LOW

2.6.133 MFGMEM

2.6.134  NOT-AUTHENTICATED

2.6.135 PDI-P

2.6.136 PEER-NORESPONSE

2.6.137 PLM-P

2.6.138 PLM-V

2.6.139 PRC-DUPID

2.6.140 PROTNA

2.6.141 PWR-A

2.6.142 PWR-B

2.6.143 RAI

2.6.144 RCVR-MISS

2.6.145 RFI-L

2.6.146 RFI-P

2.6.147 RFI-V

2.6.148 RING-MISMATCH

2.6.149 RING-SW-EAST

2.6.150 RING-SW-WEST

2.6.151 SD-L

2.6.152 SD-P

2.6.153 SF-L

2.6.154 SF-P

2.6.155 SFTWDOWN

2.6.156 SNTP-HOST

2.6.157 SPAN-SW-EAST

2.6.158 SPAN-SW-WEST

2.6.159 SQUELCH

2.6.160 SSM-DUS

2.6.161 SSM-FAIL

2.6.162 SSM-OFF

2.6.163 SSM-PRS

2.6.164 SSM-RES

2.6.165 SSM-SMC

2.6.166 SSM-ST2

2.6.167 SSM-ST3

2.6.168 SSM-ST3E

2.6.169 SSM-ST4

2.6.170 SSM-STU

2.6.171 SSM-TNC

2.6.172 SWMTXMOD

2.6.173 SWTOPRI

2.6.174 SWTOSEC

2.6.175 SWTOTHIRD

2.6.176 SYNC-FREQ

2.6.177 SYNCPRI

2.6.178 SYNCSEC

2.6.179 SYNCTHIRD

2.6.180 SYSBOOT

2.6.181 TIM-P

2.6.182 TPTFAIL

2.6.183 TRMT

2.6.184 TRMT-MISS

2.6.185 UNEQ-P

2.6.186 UNEQ-V

2.6.187 WKSWPR

2.6.188 WTR

2.7 DS3-12E Line Alarms

2.8 Common Procedures in Alarm Troubleshooting


Alarm Troubleshooting


This chapter gives a description, severity, and troubleshooting procedure for each Cisco ONS 15454 alarm and conditions commonly encountered while troubleshooting major alarms. Table 2-5 gives an alphabetical list of alarms that appear on the ONS 15454. Table 2-6 gives a list of alarms organized by alarm type. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and ONS 15327 TL1 Command Guide.

The troubleshooting procedure for an alarm applies to both the CTC and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

The default standby severity for all ONS 15454 alarms on unprovisioned card ports is Minor, Non-Service Affecting, as defined in Telcordia GR-474. All severities listed in the alarm entry are the default for the active card, if applicable. Alarm severities can be altered from default settings for individual alarms or groups of alarms on a card, node, or network basis. These alterations can be made using NTP-71 Create, Download, and Assign Alarm Severity Profiles in the Cisco ONS 15454 Procedure Guide.

2.1 Alarm Index by Default Severity

The alarm index by severity groups alarms and conditions by the severity displayed in the CTC Alarms tab in the severity (SEV) column. You can change the severity of any alarm by creating an alarm profile. See the Cisco ONS 15454 Procedure Guide for alarm profile procedures.


Note The CTC default alarm profile contains alarms that apply to multiple product platforms. The alarms that apply to this product are listed in the following tables and sections.


2.1.1 Critical Alarms (CR)


2.1.2 Major Alarms (MJ)


2.1.3 Minor Alarms (MN)


2.1.4 Conditions (NA or NR)

Table 2-4 Conditions Index 

AIS

FE-LOF

MANSWTOTHIRD

AIS-L

FE-LOS

MANUAL-REQ-RING

AIS-P

FE-MANWKSWPR-RING

MANUAL-REQ-SPAN

AIS-V

FE-MANWKSWPR-SPAN

PDI-P

AS-CMD

FORCED-REQ

RAI

AS-MT

FORCED-REQ-RING

RFI-L

AUTOSW-AIS

FORCED-REQ-SPAN

RFI-P

AUTOSW-LOP (STSMON)

FRCDSWTOINT

RFI-V

AUTOSW-PDI

FRCDSWTOPRI

RING-SW-EAST

AUTOSW-SDBER

FRCDSWTOSEC

RING-SW-WEST

AUTOSW-SFBER

FRCDSWTOTHIRD

SD-L

AUTOSW-UNEQ (STSMON)

FULLPASSTHR-BI

SD-P

CLDRESTART

INC-ISD

SF-L

DS3-MISM

INHSWPR

SF-P

EXERCISE-RING-REQ

INHSWWKG

SPAN-SW-EAST

EXERCISE-SPAN-REQ

KB-PASSTHR

SPAN-SW-WEST

EXTRA-TRAF-PREEMPT

LKOUTPR-S

SQUELCH

FAILTOSW

LOCKOUT-REQ

SSM-DUS

FAILTOSW-PATH

LOCKOUT-REQ-RING

SSM-OFF

FAILTOSWR

LOCKOUT-REQ-SPAN

SSM-PRS

FAILTOSWS

LPBKDS1FEAC

SSM-RES

FE-AIS

LPBKDS3FEAC-CMD

SSM-SMC

FE-DS1-MULTLOS

LPBKDS3FEAC

SSM-ST2

FE-DS1-NSA

LPBKDS3FEAC-CMD

SSM-ST3

FE-DS1-SA

LPBKFACILITY (DS-N or EC1-12)

SSM-ST3E

FE-DS1-SNGLLOS

LPBKFACILITY (OC-N)

SSM-ST4

FE-DS3-NSA

LPBKTERMINAL (DS-N, EC1-12, OC-N)

SSM-TNC

FE-DS3-SA

LPBKTERMINAL(G1000-4)

SSM-STU

FE-EQPT-NSA

MAN-REQ

SWTOPRI

FE-EXERCISING-RING

MANRESET

SWTOSEC

FE-EXERCISING-SPAN

MANUAL-REQ-RING

SWTOTHIRD

FE-FRCDWKSWPR-RING

MANUAL-REQ-SPAN

SYNC-FREQ

FE-FRCDWKSWPR-SPAN

MANSWTOINT

WKSWPR

FE-IDLE

MANSWTOPRI

WTR

FE-LOCKOUTOFPR-SPAN

MANSWTOSEC

 

2.2 Alarm Index By Alphabetical Entry

The following table lists alarms by the name displayed on the CTC Alarms tab in the conditions column.

Table 2-5 Alarm Index 

AIS

FE-EQPT-NSA

MEA (AIP)

AIS-L

FE-EXERCISING-RING

MEA (Bplane)

AIS-P

FE-EXERCISING-SPAN

MEA (EQPT)

AIS-V

FE-FRCDWKSWPR-RING

MEM-GONE

APSB

FE-FRCDWKSWPR-SPAN

MEM-LOW

APSCDFLTK

FE-IDLE

MFGMEM

APSC-IMP

FE-LOCKOUTOFPR-SPAN

NOT-AUTHENTICATED

APSCINCON

FE-LOF

PDI-P

APSCM

FE-LOS

PEER-NORESPONSE

APSCNMIS

FE-MANWKSWPR-RING

PLM-P

APSMM

FE-MANWKSWPR-SPAN

PLM-V

AS-CMD

FEPRLF

PRC-DUPID

AS-MT

FORCED-REQ

PWR-A

AUTOLSROFF

FORCED-REQ-RING

PWR-B

AUTORESET

FORCED-REQ-SPAN

RAI

AUTOSW-AIS

FRCDSWTOINT

RCVR-MISS

AUTOSW-LOP (STSMON)

FRCDSWTOPRI

RFI-L

AUTOSW-LOP (VT-MON)

FRCDSWTOSEC

RFI-V

AUTOSW-PDI

FRCDSWTOTHIRD

RING-MISMATCH

AUTOSW-SDBER

FRNGSYNC

RING-SW-EAST

AUTOSW-SFBER

FSTSYNC

RING-SW-WEST

AUTOSW-UNEQ (STSMON)

FULLPASSTHR-BI

SD-L

AUTOSW-UNEQ (VT-MON)

HITEMP

SD-P

BKUPMEMP

HLDOVRSYNC

SF-L

BLSROSYNC

IMPROPRMVL

SF-P

CARLOSS (E-Series)

INC-ISD

SFTWDOWN

CLDRESTART

INHSWPR

SNTP-HOST

COMIOXC

INHSWWKG

SPAN-SW-EAST

CONCAT

INVMACADR

SPAN-SW-WEST

CONTBUS-A-18

KB-PASSTHR

SQUELCH

CONTBUS-B-18

LKOUTPR-S

SSM-DUS

CONTBUS-IO-A

LOCKOUT-REQ

SSM-FAIL

CONTBUS-IO-B

LOCKOUT-REQ-RING

SSM-OFF

CTNEQPT-PBPROT

LOF (BITS)

SSM-PRS

CTNEQPT-PBWORK

LOF (DS1)

SSM-RES

DATAFLT

LOF (DS3)

SSM-SMC

DS3-MISM

LOF (EC1-12)

SSM-STU

EHIBATVG-A

LOF (OC-N)

SSM-ST2

EHIBATVG-B

LOP-P

SSM-ST3

ELWBATVG-A

LOP-V

SSM-ST3E

ELWBATVG-B

LOS (BITS)

SSM-ST4

EOC

LOS (DS-1)

SSM-TNC

EQPT

LOS (EC1-12)

SWMTXMOD

EQPT-MISS

LOS (OC-N)

SWTOPRI

E-W-MISMATCH

LOS (OC-N)

SWTOSEC

EXCCOL

LOS (OC-N)

SWTOTHIRD

EXERCISE-RING-REQ

LPBKDS1FEAC

SYNC-FREQ

EXERCISE-SPAN-REQ

LPBKDS1FEAC-CMD

SYNCPRI

EXT

LPBKDS3FEAC

SYNCSEC

FAILTOSW

LPBKDS3FEAC-CMD

SYNCTHIRD

FAILTOSW-PATH

LPBKFACILITY (DS-N or EC1-12)

SYSBOOT

FAILTOSWR

LPBKFACILITY (OC-N)

TIM-P

FAILTOSWS

LPBKTERMINAL (DS-N, EC1-12, OC-N)

TPTFAIL

FAN

MAN-REQ

TRMT

FE-AIS

MANRESET

TRMT-MISS

FE-DS1-MULTLOS

MANSWTOINT

UNEQ-P

FE-DS1-NSA

MANSWTOPRI

UNEQ-P

FE-DS1-SA

MANSWTOSEC

UNEQ-V

FE-DS1-SNGLLOS

MANSWTOTHIRD

WKSWPR

FE-DS3-NSA

MANUAL-REQ-RING

WTR

FE-DS3-SA

MANUAL-REQ-SPAN

 

2.3 Alarm Index by Alarm Type

The following table by alarm type gives the name and page number of every alarm in the chapter organized by alarm type.

Table 2-6 Alarm Index by Alarm Type 

AIP: EQPT

AIP: INVMACADR

AIP: MEA (AIP)

AIP: MFGMEM

AEP: MFGMEM

BITS: AIS

BITS: LOF (BITS)

BITS: LOS (BITS)

BITS: SSM-DUS

BITS: SSM-FAIL

BITS: SSM-OFF

BITS: SSM-PRS

BITS: SSM-RES

BITS: SSM-SMC

BITS: SSM-ST2

BITS: SSM-ST3

BITS: SSM-ST3E

BITS: SSM-ST4

BITS: SSM-STU

BITS: SSM-TNC

BITS: SYNC-FREQ

BPLANE: AS-CMD

BPLANE: MEA (Bplane)

BPLANE: MFGMEM

DS1: AIS

DS1: AS-CMD

DS1: AS-MT

DS1: LOF (DS1)

DS1: LOS (DS-1)

DS1: LPBKDS1FEAC

DS1: LPBKDS1FEAC-CMD

DS1: LPBKFACILITY (DS-N or EC1-12)

DS1: LPBKTERMINAL (DS-N, EC1-12, OC-N)

DS1: RAI

DS1: RCVR-MISS

DS1: TRMT

DS1: TRMT-MISS

DS3: AIS

DS3: AS-CMD

DS3: AS-MT

DS3: DS3-MISM

DS3: FE-AIS

DS3: FE-DS1-MULTLOS

DS3: FE-DS1-NSA

DS3: FE-DS1-SA

DS3: FE-DS1-SNGLLOS

DS3: FE-DS3-NSA

DS3: FE-DS3-SA

DS3: FE-EQPT-NSA

DS3: FE-IDLE

DS3: FE-LOF

DS3: FE-LOS

DS3: INC-ISD

DS3: LOF (DS3)

DS3: LOS (DS-3)

DS3: LPBKDS1FEAC

DS3: LPBKDS3FEAC

DS3: LPBKDS3FEAC-CMD

DS3: LPBKFACILITY (DS-N or EC1-12)

DS3: LPBKTERMINAL (DS-N, EC1-12, OC-N)

DS3: RAI

ECN: AIS-L

ECN: AS-CMD

ECN: AS-MT

ECN: LOF (EC1-12)

ECN: LPBKFACILITY (DS-N or EC1-12)

ECN: LPBKTERMINAL (DS-N, EC1-12, OC-N)

ECN: LOS (EC1-12)

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: PEER-NORESPONSE

EQPT: PROTNA

EQPT: SFTWDOWN

EQPT: SWMTXMOD

EQPT: WKSWPR

EQPT: WTR

ETHER: CARLOSS (E-Series)

EXTSYNCH: FRCDSWTOPRI

EXTSYNCH: FRCDSWTOSEC

EXTSYNCH: FRCDSWTOTHIRD

EXTSYNCH: MANSWTOPRI

EXTSYNCH: MANSWTOSEC

EXTSYNCH: MANSWTOTHIRD

EXTSYNCH: SWTOPRI

EXTSYNCH: SWTOSEC

EXTSYNCH: SWTOTHIRD

EXTSYNCH: SYNCPRI

EXTSYNCH: SYNCSEC

EXTSYNCH: SYNCTHIRD

FAN: EQPT-MISS

FAN: FAN

FAN: MEA (FAN)

FAN: MFGMEM

FUDC: AIS

FUDC: LOF (OC-N)

HDGE [G1000]: CARLOSS (G1000-4)

HDGE [G1000]: LPBKTERMINAL (DS-N, EC1-12, OC-N)

HDGE [G1000]: TPTFAIL

NE: AS-CMD

NE: DATAFLT

NE: EHIBATVG-A

NE: EHIBATVG-B

NE: ELWBATVG-A

NE: ELWBATVG-B

NE: HITEMP

NE: PRC-DUPID

NE: PWR-A

NE: PWR-B

NE: SNTP-HOST

NE: SYSBOOT

NERING: BLSROSYNC

NERING: FULLPASSTHR-BI

NERING: KB-PASSTHR

NERING: PRC-DUPID

NERING: RING-MISMATCH

NESYNCH: FRCDSWTOINT

NESYNCH: FRCDSWTOPRI

NESYNCH: FRCDSWTOSEC

NESYNCH: FRCDSWTOTHIRD

NESYNCH: FRNGSYNC

NESYNCH: FSTSYNC

NESYNCH: HLDOVRSYNC

NESYNCH: MANSWTOINT

NESYNCH: MANSWTOPRI

NESYNCH: MANSWTOSEC

NESYNCH: MANSWTOTHIRD

NESYNCH: SSM-SMC

NESYNCH: SSM-ST3E

NESYNCH: SSM-ST4

NESYNCH: SSM-STU

NESYNCH: SSM-TNC

NESYNCH: SWTOPRI

NESYNCH: SWTOSEC

NESYNCH: SWTOTHIRD

NESYNCH: SYNCPRI

NESYNCH: SYNCSEC

NESYNCH: SYNCTHIRD

OCN: AIS-L

OCN: APSB

OCN: APSCDFLTK

OCN: APSC-IMP

OCN: APSCINCON

OCN: APSCM

OCN: APSCNMIS

OCN: APSMM

OCN: AS-CMD

OCN: AS-MT

OCN: AUTOLSROFF

OCN: EOC

OCN: E-W-MISMATCH

OCN: EXERCISE-RING-REQ

OCN: EXERCISE-SPAN-REQ

OCN: EXTRA-TRAF-PREEMPT

OCN: FAILTOSW

OCN: FAILTOSWR

OCN: FAILTOSWS

OCN: FE-EXERCISING-RING

OCN: FE-EXERCISING-SPAN

OCN: FE-FRCDWKSWPR-RING

OCN: FE-FRCDWKSWPR-SPAN

OCN: FE-LOCKOUTOFPR-SPAN

OCN: FE-MANWKSWPR-RING

OCN: FE-MANWKSWPR-SPAN

OCN: FEPRLF

OCN: FORCED-REQ

OCN: FORCED-REQ-RING

OCN: FORCED-REQ-SPAN

OCN: LKOUTPR-S

OCN: LOCKOUT-REQ

OCN: LOCKOUT-REQ-RING

OCN: LOF (OC-N)

OCN: LOS (OC-N)

OCN: LPBKFACILITY (OC-N)

OCN: LPBKTERMINAL (DS-N, EC1-12, OC-N)

OCN: MANUAL-REQ-RING

OCN: MANUAL-REQ-SPAN

OCN: RFI-L

OCN: RING-SW-EAST

OCN: RING-SW-WEST

OCN: SD-L

OCN: SF-L

OCN: SPAN-SW-EAST

OCN: SPAN-SW-WEST

OCN: SQUELCH

OCN: SSM-DUS

OCN: SSM-FAIL

OCN: SSM-OFF

OCN: SSM-PRS

OCN: SSM-RES

OCN: SSM-SMC

OCN: SSM-ST2

OCN: SSM-ST3

OCN: SSM-ST3E

OCN: SSM-ST4

OCN: SSM-STU

OCN: SSM-TNC

OCN: SYNC-FREQ

OCN: WKSWPR

OCN: WTR

STSMON: AIS-P

STSMON: AUTOSW-AIS

STSMON: AUTOSW-LOP (STSMON)

STSMON: AUTOSW-PDI

STSMON: AUTOSW-SDBER

STSMON: AUTOSW-SFBER

STSMON: AUTOSW-UNEQ (STSMON)

STSMON: CONCAT

STSMON: FAILTOSW-PATH

STSMON: FORCED-REQ

STSMON: LOCKOUT-REQ

STSMON: LOP-P

STSMON: MAN-REQ

STSMON: PDI-P

STSMON: PLM-P

STSMON: RFI-P

STSMON: SD-P

STSMON: SF-P

STSMON: TIM-P

STSMON: UNEQ-P

STSMON: WKSWPR

STSTERM: AIS-P

STSTERM: PDI-P

STSTERM: PLM-P

STSTERM: RFI-P

STSTERM: SD-P

STSTERM: SF-P

STSTERM: TIM-P

STSTERM: UNEQ-P

VT-MON: AIS-V

VT-MON: AUTOSW-AIS

VT-MON: AUTOSW-LOP (VT-MON)

VT-MON: AUTOSW-UNEQ (VT-MON)

VT-MON: FORCED-REQ

VT-MON: LOCKOUT-REQ

VT-MON: LOP-V

VT-MON: MAN-REQ

VT-MON: UNEQ-V

VT-MON: WKSWPR

VT-TERM: AIS-V

VT-TERM: PLM-V

VT-TERM: RFI-V

VT-TERM: SD-P

VT-TERM: SF-P

VT-TERM: UNEQ-V


2.3.1 Alarm Type/Object Definition

The following table defines abbreviations used in the alarm troubleshooting procedures.

Table 2-7 Alarm Type/Object Definition 

AIP

Auxiliary interface protection module

BITS

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

BPLANE

The backplane

DS1

A DS1 line on a DS1 or DS3XM card

DS3

A DS3 line on a DS3 or DS3XM card

ETHER

Ethernet, such as for straight-through (CAT-5) LAN cables

ECN

An EC1 line on an EC1 card

EC1-12

An EC1 line on an EC1 card

ENV

An environmental alarm port on an AIC card

EQPT

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

EXTSYNCH

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

E1000F

An Ethernet line on an E1000 card

E100T

An Ethernet line on an E100 card

FAN

Fan-tray assembly

HDGE

High Density Gigabit Ethernet. Applies to G1000 cards.

NE

The entire network element (SYSTEM)

NERING

Represents the ring status in the NE

NE-SYNCH

Represents the timing status of the NE

OCN

An OCN line on an OCN card

STSMON

STS alarm detection at the monitor point (upstream of cross-connect)

STSRNG

BLSR ring number (STSRNG)

STSTERM

STS alarm detection at termination (downstream of cross-connect)

VT-MON

VT1 alarm detection at the monitor point (upstream of cross-connect)

VT-TERM

VT1 alarm detection at termination (downstream of cross-connect)


2.4 Trouble Notifications

The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The ONS 15454 reports both alarmed trouble notifications, in the Alarms tab, and non-alarmed (NA) trouble notifications, in the Conditions tab in CTC. Alarms signify a problem that the user needs to fix, such as a loss of signal (LOS). Conditions notify the user of an event which does not require action, such as a Switch to Secondary Timing Reference ( SWTOSEC) or a User-Initiated Manual Reset ( MANRESET) condition.

Telcordia further divides alarms into Service Affecting (SA) and Non-Service Affecting (NSA) status. An SA failure affects a provided service or the network's ability to provide service. For example, a Missing Transmitter ( TRMT-MISS) is characterized as an SA failure. TRMT-MISS occurs when the cable connector leading to a port on an active DS1-14 card is removed. The missing cable or lost signal affects a provided service, because traffic switches to the protect card. The High Temperature ( HITEMP) alarm, which means the ONS 15454 is hotter than 122 degrees Fahrenheit (50 degrees Celsius), is also an SA failure. Although for example a particular DS1-14 port may not be affected, a high temperature affects the network's ability to provide service.

2.4.1 Conditions

When an SA failure is detected, the ONS 15454 also sends an 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 show up on the Conditions tab of the ONS 15454. However, unlike most conditions which are non-alarmed, Telcordia classifies these conditions as Not Reported (NR).

Both CTC and TL1 report NRs and NAs as conditions when conditions are retrieved. NAs are also reported as autonomous events in TL1 and in the History tab of CTC. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.

2.4.2 Severities

The ONS 15454 uses Tecordia-standard severities: Critical (CR), Major (MJ), and Minor (MN). Critical indicates a severe, service affecting alarm that needs immediate correction. Major is a serious alarm, but the failure has less of an impact on the network. For example, with a DS1-14 LOS, a Major alarm, 24 DS-0 circuits lose protection. But with an OC-192 LOS, a Critical alarm, over a hundred thousand DS-0 circuits lose protection.

Minor alarms, such as Fast Start Synchronization ( FSTSYNC), do not have a serious effect on service. FSTSYNC lets you know that the ONS 15454 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 a minor alarm should not immediately disrupt service.

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

2.5 Safety Summary

This section covers safety considerations to ensure safe operation of the ONS 15454 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 may 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 (OC-N) cards, in these instances users should pay close attention to the following warnings:


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



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


2.6 Alarm Procedures

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

2.6.1 AIS

Not Reported (NR) (Condition)

The ONS 15454 detects an Alarm Indication Signal (AIS) in the SONET overhead. 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 the DS-3 or OC-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 may 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 Clear the upstream alarms using the applicable procedure(s) in this chapter.

Step 3 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.2 AIS-L

Not Reported (NR) (Condition)

The Alarm Indication Signal-Line condition means there is an error in the SONET overhead at the line layer. The AIS-L 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 OC-N port in service. The upstream node often reports an LOS or has an out-of-service port. The AIS-L clears when you clear the primary alarm on the upstream node. However, the primary alarm node may not report any alarms that indicate it is at fault.

The SONET line layer refers to the segment between two SONET devices in the circuit and is also known as a maintenance span. The line layer deals with SONET payload transport, and its functions include multiplexing and synchronization.

Procedure: Clear the AIS-L Condition


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

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

Step 3 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.3 AIS-P

Not Reported (NR) (Condition)

The Alarm Indication Signal-Path condition means there is an error in the SONET overhead at the path layer. The AIS-P condition is secondary to another alarm occurring simultaneously in an upstream node. The AIS is caused by an incomplete circuit path, for example, when the port on the reporting node is in service, but a node upstream on the circuit does not have its port in service. The upstream node often reports an LOS or has an OC-N port out of service. The AIS-P clears when the primary alarm on the upstream node is cleared. However, the node with the primary alarm may not report any alarms to indicate it is at fault.

AIS-P occurs in each node on the incoming OC-N path. The path layer is the segment between the originating equipment and the terminating equipment. The path layer encompasses several consecutive line segments or segments between two SONET devices. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.

Procedure: Clear the AIS-P Condition


Step 1 Check upstream nodes and equipment for alarms, especially 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, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.4 AIS-V

Not Reported (NR) (Condition)

The Alarm Indication Signal-Virtual Tributary (VT) condition means there is an error in the SONET overhead at the VT layer. The AIS-V 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 OC-N port in service. The upstream node often reports an LOS or has an out-of-service port. The AIS-V clears when the primary alarm is cleared. The node with the out-of-service port may not report any alarms to indicate it is at fault.

An AIS-V indicates that an upstream failure occurred at the VT, or electrical, layer. The VT layer is created when the SONET signal is broken down into an electrical signal, for example when an optical signal enters an ONS 15454 OC-N card. If the optical signal is demultiplexed by the ONS 15454, and one of the channels separated from the optical signal is then cross-connected into the DS1-14 ports in the same node, that ONS 15454 reports an AIS-V alarm.

An AIS-V error message on the electrical card is accompanied by an AIS-P error message on the cross-connected OC-N card.


Note See the "AIS-V on DS3XM-6 Unused VT Circuits" section on page 1-65.



Note In non-revertive UPSR configurations, VT-layer alarms or conditions (ending in *-V) are not reported when a switch occurs due to VT-level errors. Only WKSWPR is reported.


Procedure: Clear the AIS-V Condition


Step 1 Check upstream nodes and equipment for alarms, especially 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, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.5 APSB

Minor (MN), Non-Service Affecting

The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming APS signal. The failure occurs when an inconsistent APS byte or invalid code is detected. Some older, non-Cisco SONET nodes send invalid APS codes if configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15454. These invalid codes will raise an APSB on an ONS node.

Procedure: Clear the APSB Alarm


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

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

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


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

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.6 APSCDFLTK

Minor (MN), Non-Service Affecting

The APS Default K Byte Received alarm occurs when a BLSR is not properly configured, for example, when a four-node BLSR has one node configured as UPSR. A node in a UPSR or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.

Troubleshooting for APSCDFLTK is often similar to troubleshooting for BLSROSYNC.

Procedure: Clear the APSCDFLTK Alarm


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

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

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

Step 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 Procedure Guide provides a procedure for fibering BLSRs.

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

Step 6 If nodes are not visible, complete 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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.7 APSC-IMP

Minor (MN), Non-Service Affecting

An Improper SONET Automatic Protect Switch code alarm indicates invalid K bytes. The APSC-IMP alarm occurs on OC-N cards in a BLSR 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. APSCIMP 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. Plug the wristband cable into the ESD jack located on the lower-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. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.

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

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

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

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.8 APSCINCON

Minor (MN), Service Affecting

An APS-Inconsistent alarm means an inconsistent APS byte present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the SONET signal from a working to a protect path. 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


Step 1 Look for other alarms, especially LOS, loss of frame (LOF) or AIS. Clearing these alarms clears the APSCINCON alarm.

Step 2 If an APSINCON alarm occurs with no other alarms, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.9 APSCM

Major (MJ), Service Affecting

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


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. Plug the wristband cable into the ESD jack located on the lower-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 fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node's protection-card channel fibers.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.10 APSCNMIS

Major (MJ), Service Affecting

The APS 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. The APSCNMIS alarm may occur and clear when a BLSR is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains raised, the alarm clears when a K byte with a valid source node ID is received.

Procedure: Clear the APSCNMIS Alarm


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

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

Step 3 Click Close on the Ring Map dialog box.

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


Note If the node names shown on the network view do not correlate with the node IDs, log into each node and click the Provisioning > BLSR tabs. The BLSR tab 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 to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.


Step 5 If the alarm does not clear, use the "Lock Out a BLSR Span" procedure to lock out the span.

Step 6 Use the "Clear a BLSR Span Command" procedure to clear the lockout.

Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.11 APSMM

Minor (MN), Non-Service Affecting

An APS Mode Mismatch failure alarm occurs when there is a mismatch of the protection switching schemes at the two ends of the span. If one node is provisioned for bidirectional switching, the node at the other end of the span must also be provisioned for bidirectional switching. If one end is provisioned for bidirectional and the other is provisioned for unidirectional, an APSMM alarm occurs in the ONS node that is provisioned for bidirectional. The APSMM alarm occurs in a 1+1 configuration.

Procedure: Clear the APSMM Alarm


Step 1 For the reporting ONS 15454, display the CTC node (default login) view and check the protection scheme provisioning.

a. Click the Provisioning > Protection tabs.

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

The chosen protection group is the protection group optically connected (with DCC connectivity) to the far end.

Record whether the Bidirectional Switching checkbox is checked.

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

about is the protection group optically connected (with DCC connectivity) to the near end.

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

Step 4 Click Apply.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.12 AS-CMD

Not Alarmed (NA) (Condition)

The Alarms Suppressed by User Command condition applies to the Network Element (NE), backplane, and cards. It occurs 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.

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 checkbox is checked for a port row, click it to deselect it and click Apply.

If the Suppress Alarms column checkbox 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 checkbox 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 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 checkbox to deselect it and click Apply.

Step 7 If the condition is reported for the shelf, 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 checkbox located at the bottom of the tab to deselect the option.

c. Click Apply.

Step 8 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.13 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 maintenance (OOS-MT) state for loopback testing operations.

To clear the AS-MT condition, complete the "Clear a Loopback" procedure. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.14 AUTOLSROFF

Critical, Service Affecting

The Auto Laser Shutdown alarm raises when the OC-192 card temperature exceeds 90 degrees Celsius. The internal equipment automatically shuts down the OC-192 laser when the card temperature rises to prevent the card from self-destructing.


Warning On the 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 AUTOLSROFF Alarm


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

Step 2 If the temperature of the ONS 15454 exceeds 90 degrees Celsius, the alarm should clear if you solve the ONS 15454 temperature problem. Complete the "HITEMP" procedure.

Step 3 If the temperature of the ONS 15454 is below 90 degrees Celsius, the ONS 15454 temperature is not the cause of the alarm, complete the "Physically Replace a Card" procedure for the OC-192 card.


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


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


2.6.15 AUTORESET

Minor (MN), Non-Service Affecting

The Automatic System Reset alarm 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. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.

Procedure: Clear the AUTORESET Alarm


Step 1 Check for additional alarms that may have triggered an automatic reset.

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


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


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


Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.16 AUTOSW-AIS

Not Reported (NR) (Condition)

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

To clear the condition, see the "AIS" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.17 AUTOSW-LOP (STSMON)

Not Alarmed (Condition)

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

To clear the condition, see the "LOP-P" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.18 AUTOSW-LOP (VT-MON)

Minor (MN), Service Affecting

The AUTOSW-LOP alarm indicates that automatic UPSR protection switching took place because of an LOP alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears.

To clear the alarm, see the "LOP-P" section. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.19 AUTOSW-PDI

Not Alarmed (Condition)

The Automatic UPSR Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic UPSR protection switching took place because of a PDI alarm. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears.

To clear the condition, see the "PDI-P" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.20 AUTOSW-SDBER

Not Alarmed (NA) (Condition)

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

To clear the condition, see the "CLDRESTART" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.21 AUTOSW-SFBER

Not Alarmed (NA) (Condition)

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

To clear the condition, see the "SF-L" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.22 AUTOSW-UNEQ (STSMON)

Not Alarmed (NA) (Condition)

The Automatic UPSR Switch Caused by Unequipped (UNEQ) condition indicates that an UNEQ alarm caused automatic UPSR protection switching to occur. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears.

To clear the condition, see the "UNEQ-P" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.23 AUTOSW-UNEQ (VT-MON)

Minor (MN), Service Affecting

AUTOSW-UNEQ indicates that a UNEQ alarm caused automatic UPSR protection switching to occur. The UPSR is configured for revertive switching and will switch back to the working path after the fault clears.

To clear the alarm, see the "UNEQ-P" section. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.24 BKUPMEMP

Critical, Non-Service Affecting

The Primary Non-Volatile Backup Memory Failure alarm refers to a problem with the TCC+ card's flash memory. The alarm occurs when the TCC+ 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+.

The BKUPMEMP alarm will also raise the EQPT alarm. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.


Caution It can take up to 30 minutes for software to be updated on a standby TCC+ card.

Procedure: Clear the BKUPMEMP Alarm


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

Step 2 If both TCC+ cards are powered and enabled, reset the active TCC+ card to make the standby TCC+ card active. Complete the "Reset the Active TCC+ Card in CTC" procedure.

Wait ten minutes to verify that the card you reset completely reboots and displays as Standby. If not, call the Cisco Technical Assistance Center (1-800-553-2447).

Step 3 If the alarm has not cleared, call the Cisco Technical Assistance Center (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.


2.6.25 BLSROSYNC

Major (MJ), Service Affecting

The BLSR Out Of Sync alarm is caused when a node on a working ring loses its DCC connection because all transmit and receive fiber is removed, and you attempt to add or delete a circuit. The CTC cannot generate the table and raises the BLSROSYNC alarm.

Procedure: Clear the BLSROSYNC Alarm


Step 1 Reestablish cabling continuity to the node reporting the alarm.

Once the DCC is established between the node and the rest of the BLSR, it will become visible to the BLSR and be able to function on the circuits.

Step 2 If alarms are raised when the DCCs are turned on, see the "EOC" section.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.26 CARLOSS (EQPT)

Major (MJ), Service Affecting

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

Procedure: Clear the CARLOSS Alarm


Step 1 Verify connectivity by pinging the ONS 15454 that is reporting the alarm.

a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Accessories > 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, 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.

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

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

Step 4 If the straight-through (CAT-5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.

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

Step 6 If you are unable to establish connectivity, perform standard network/LAN diagnostics. For example, trace the IP route, check cables, and check any routers between the node and CTC.

Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.27 CARLOSS (E-Series)

Major (MJ), Service Affecting

A Carrier Loss on the LAN-E-Series Ethernet Card alarm is the data equivalent of a SONET LOS alarm. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of the CARLOSS alarm are a disconnected cable, an Ethernet GBIC fiber connected to an optical card rather than an Ethernet device, 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.

The CARLOSS alarm also occurs after the restoration of a node's database. After restoration, the alarm will clear in approximately 30 seconds after spanning tree protection (STP) reestablishes. The database restoration circumstance applies to the E-series Ethernet cards but not the G1000-4 card, because the G1000-4 card does not use STP and is unaffected by STP reestablishment.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. 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 (CAT-5) LAN cable is properly connected and attached to the correct port.

Step 2 If the straight-through (CAT-5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.

Step 3 If no misconnection to an OC-N card exists, 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 (CAT-5) LAN cable connecting the transmitting device to the Ethernet port.

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

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


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


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


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

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

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

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

b. Right-click or left-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 network, determine the ONS 15454 and card that host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

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

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

Click the Circuits tab.

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

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

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

f. Reconfigure the circuit with the correct circuit size. For more information, refer to the Cisco ONS 15454 Procedure Guide.

Step 10 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.28 CARLOSS (G1000-4)

Major, Service affecting

A Carrier Loss on the LAN-G-Series Ethernet Card alarm is the data equivalent of a SONET 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:

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

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

Refer to the Cisco ONS 15454 Reference Guide for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TPTFAIL" section for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.

Ethernet card ports must be enabled (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. 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 (CAT-5) LAN cable is properly connected and attached to the correct port.

Step 2 If the straight-through (CAT-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 OC-N card.

Step 3 If no misconnection to the OC-N card exists, 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 (CAT-5) LAN cable connecting the transmitting device to the Ethernet port.

Step 6 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the G1000-4 will turn off its transmitter laser and report a CARLOSS alarm. If link autonegotiation has been enabled for the port, check for conditions which could cause autonegotiation to fail.

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

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. (The autonegotiation process will restart.)

Step 8 If the alarm does not clear and a TPTFAIL alarm is also reported, complete the "TPTFAIL" procedure. If the TPTFAIL alarm is not reported, continue to the next step.


Note When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition may 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 the port.

a. In the node (default login) view, click the card to go to card view.

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

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

Step 10 If a loopback was provisioned, complete the "Clear a Loopback" procedure.

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

If the does not have a LPBKTERMINAL condition, continue to Step 11.

Step 11 If a CARLOSS alarm repeatedly appears and clears, use the following steps to examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect. If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm may 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, the following steps do not apply.


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


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

b. Right-click or left-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 network, determine the ONS 15454 and card that host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

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

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

Click the Circuits tab.

Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit will connect the Ethernet card to an OC-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, complete the "Delete a Circuit" procedure.

f. Reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide for detailed procedures about how to create circuits.

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

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


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


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


Step 14 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.29 CLDRESTART

Not Alarmed (NA) (Condition)

The Cold Restart condition occurs when a card is cold-restarted by being physically removed and inserted, replaced, or when the ONS 15454 is powered on.


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

Procedure: Clear the CLDRESTART Condition


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

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


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


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


Step 3 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.30 COMIOXC

Critical, Service Affecting

The I/O Slot To Cross-Connect (XCON) Communication Failure alarm is raised by the cross-connect card. It occurs when there is a communication failure for a particular I/O slot.

Procedure: Clear the COMIOXC Condition


Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the reporting cross-connect card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

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

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


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


Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.31 CONCAT

Critical, Service Affecting

The STS Concatenation Error alarm occurs when the transmitted STSc circuit is different from the provisioned STSc, which causes a mismatch of the circuit type on the concatenation facility. For example, an STS3c or STS1 is sent across a circuit provisioned for STS12c.

Either an incorrect circuit size was provisioned on the reporting node, or the circuit source is delivering the wrong circuit size. If a recently configured circuit reports the CONCAT alarm, it is more likely that the provisioned circuit size is incorrect. If an existing circuit has operated correctly and then reports the alarm, it is more likely that a problem occurred with the circuit source.

Procedure: Clear the CONCAT Alarm


Step 1 Check that the provisioned circuit size is correct.

a. In the network view, click the Circuits tab.

b. Find the appropriate row using the Circuit Name and record the size listed in the size column.

c. Determine whether the size listed matches the original network design plan.

Step 2 If the circuit size listed does not match the original network design plan, complete the "Delete a Circuit" procedure.

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

Step 4 Check that the size of the circuit source matches the correct circuit size.

a. Measuring the source signal with an optical test set to determine whether the circuit size matches the provisioned circuit.

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

b. If the source of the circuit signal is an optical test set, check that the optical test set settings match the intended circuit size.

c. If the source of the circuit signal is not an optical test set, troubleshoot the source of the circuit signal.

Step 5 If the source of the circuit signal is an ONS 15454 or other Cisco device, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.32  CONTBUS-A-18

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

A Communication Failure from TCC+ Slot to TCC+ Slot alarm occurs when the main processor on the TCC+ card in Slot 7 (termed TCC A) loses communication with the coprocessor on the same card.


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

Clear the CONTBUS-A-18 Alarm


Step 1 Complete the "Reset the Active TCC+ Card in CTC" procedure to make the TCC+ in Slot 11 active.

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

Step 3 Position the cursor over the TCC+ card in Slot 11 and complete the "Reset the Active TCC+ Card in CTC" procedure to make the standby TCC+ in Slot 7 active.

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


2.6.33  CONTBUS-B-18

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

A Communication Failure from TCC+ Slot to TCC+ Slot alarm occurs when the main processor on the TCC+ card in Slot 11 (termed TCC B) loses communication with the coprocessor on the same card.


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

Clear the CONTBUS-B-18 Alarm


Step 1 Position the cursor over the TCC+ card in Slot 11 and complete the "Reset the Active TCC+ Card in CTC" procedure to make the TCC+ in Slot 7 active.

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

Step 3 Position the cursor over the TCC+ card in Slot 7 and complete the "Reset the Active TCC+ Card in CTC" procedure to make the standby TCC+ in Slot 11 active.

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


2.6.34  CONTBUS-IO-A

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

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

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


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

Clear the CONTBUS-IO-A Alarm


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

If the actual card type and the provisioned card type do not match, see the MEA (Bplane) alarm (see page 2-89) for the reporting card.

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

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

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

a. Right-click the Slot 11 TCC+ 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 the Active TCC+ Card in CTC" procedure.

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

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

Step 6 If the reseated card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.


2.6.35  CONTBUS-IO-B

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

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

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


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

Clear the CONTBUS-IO-B Alarm


Step 1 Ensure that the reporting card is physically present in the shelf. 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, see the MEA (Bplane) alarm (see page 2-89) for the reporting card.

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

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

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

a. Right-click the Slot 7 TCC+ 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 the Active TCC+ Card in CTC" procedure.

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

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

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


2.6.36 CTNEQPT-PBPROT

Critical, Service Affecting

The Interconnection Equipment Failure-Protect Cross-Connect Card (XC) Payload Bus Alarm indicates a failure of the main payload between the protect cross-connect card (XC/XCVT/XC10G) 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, the TCC+ card, or the backplane.


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



Caution It can take up to 30 minutes for software to be updated on a standby TCC+ card.


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

Procedure: Clear the CTNEQPT-PBPROT Alarm


Step 1 Perform a CTC reset on the standby cross-connect card (XC/XCVT/XC10G). Complete the "Reset a Traffic Card in CTC" procedure.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

If the cross-connect reset is not complete and error-free or if the TCC+ reboots automatically, call the Cisco Technical Assistance Center (1-800-553-2447).

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

Step 4 Determine whether the card is an active card in a protection group. Refer to DLP 189, "Verify that a 1+1 Working Slot is Active," for information.

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

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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

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

Step 10 If the reporting traffic card is a protect card, complete the "Reset a Traffic Card in CTC" procedure for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

Step 11 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, the ACT/STBY LED is illuminated.

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

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

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


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


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

Step 15 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.37 CTNEQPT-PBWORK

Critical, Service Affecting

The Interconnection Equipment Failure-Working Cross-Connect Card (XC) Payload Bus alarm indicates a failure in the main payload bus between the active cross-connect card (XC/XCVT/XC10G) 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 CTNEEQPT-PBWORK alarm, complete the "Reset the Active TCC+ Card in CTC" procedure for the active TCC+ card and then complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4 for it. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC+ card. Do not physically reseat an active TCC+ card; it disrupts traffic.



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

Procedure: Clear the CTNEQPT-PBWORK Alarm


Step 1 Complete the "Side Switch the Active or Standby Cross-Connect Card" procedure for the active cross-connect card.


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


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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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


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


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

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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

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

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


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


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

Step 12 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.38 DATAFLT

Minor (MN), Non-Service Affecting

The Software Data Integrity Fault alarm occurs when the TCC+ exceeds its flash memory capacity.


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

Log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.39 DS3-MISM

Not Alarmed (NA) (Condition)

The DS3 Frame Format Mismatch condition indicates a frame format mismatch on the DS3-12E card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C-BIT for a DS3-12E card, and the incoming signal's frame format is detected as M23 or UNFRAMED, then the ONS 15454 reports a DS3-MISM alarm. The alarm is not raised when the line type is set to AUTO PROVISION or UNFRAMED.

The alarm or condition clears when the line type is set to AUTO PROVISION or UNFRAMED, the port state is set to OOS, or the correct frame format is set. Setting the line type to AUTO PROVIS ION causes the ONS 15454 to detect the received frame format and provision the port to use the matching frame format, either Unframed, M23 or C-bit.

Procedure: Clear the DS3-MISM Condition


Step 1 Display the CTC card view for the reporting DS3-12E.

Step 2 Click Provisioning > Line tabs.

Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the expected incoming signal.

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

Step 5 Click Apply.

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

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

Step 7 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.40 EHIBATVG-A

Major (MJ), Service Affecting

The Extreme High Voltage Battery A alarm occurs when the voltage level on battery lead A exceeds -56.7 Vdc. 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 -56.7 Vdc in the normal range for 120 seconds.

The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.41 EHIBATVG-B

Major (MJ), Service Affecting

The Extreme High Voltage Battery B alarm occurs when the voltage level on battery lead B exceeds -56.7 Vdc. 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 -56.7 Vdc in the normal range for 120 seconds.

The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.42 ELWBATVG-A

Major (MJ), Service Affecting

The Extreme Low Voltage Battery A alarm occurs when the voltage on battery feed A is extremely low or has been lost, and power redundancy is no longer guaranteed. The extreme low voltage battery A alarm occurs when the voltage on battery feed A drops below -40.5 Vdc. The alarm clears when voltage remains above -40.5 Vdc in the normal range for 120 seconds.

The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.43 ELWBATVG-B

Major (MJ), Service Affecting

The Extreme Low Voltage Battery B alarm occurs when the voltage on battery feed B is extremely low or has been lost, and power redundancy is no longer guaranteed. The extreme low voltage battery B alarm occurs when the voltage on battery feed B drops below -40.5 Vdc. The alarm clears when voltage remains above -40.5 Vdc in the normal range for 120 seconds.

The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.44 EOC

Major (MJ), Non-Service Affecting

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


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the EOC Alarm


Step 1 If an LOS alarm is also reported, complete the LOS procedure as appropriate to resolve the 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 OC-N card is illuminated.

Step 4 If the ACT LEDs on CN-N cards are illuminated, complete 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 OC-N port is active and in service.

a. Confirm that the OC-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 OC-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 OC-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 will disrupt service on the OC-N card. It may be necessary to manually switch traffic carrying circuits over to a protection path.

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

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

Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset the Active TCC+ Card in CTC" procedure.

Wait ten minutes to verify that the card you reset completely reboots and displays as Standby. If not, call the Cisco Technical Assistance Center (1-800-553-2447).

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

Step 11 If the alarm has not cleared, call the Cisco Technical Assistance Center (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

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

a. Click the Provisioning > SONET 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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.45 EQPT

Critical, Service Affecting

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

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


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

Procedure: Clear the EQPT Alarm


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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

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


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


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


Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.46 EQPT-MISS

Critical, Service Affecting

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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right 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, complete the "Remove and Reinsert Fan Tray" procedure.

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

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.47 E-W-MISMATCH

Major (MJ), Service Affecting

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 hook up the fibers correctly, or the ring provisioning plan was flawed. You can physically reconnect the 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. The CTC method will clear the alarm, but may change the traditional east-west node connection pattern of the ring.


Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its East-West slot/ports configured correctly. If the alarm appears during the initial setup, the alarm clears itself shortly after the ring setup is complete.



Note The lower numbered slot on a node is traditionally labelled as the west slot and the higher numbered slot is labelled as the east slot. For example, Slot 6 is west and Slot 12 is east.


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


Step 1 Log into the misconnected node. The misconnected node has both ring fibers misconnected. It is between the two nodes that have one of two ring fibers misconnected.

Step 2 Click the Maintenance > BLSR tabs.

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

Step 4 From the View menu, choose Go to Network View.

Step 5 Delete and recreate the BLSR.

a. Click the Provisioning > BLSR 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 BLSR Creation window.

Step 6 Display the CTC node (default login) view and click the Maintenance > BLSR 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, see the "E-W-MISMATCH" section.

Step 11 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


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 Right-click each span to reveal the node name/slot/port for each end of the span.

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

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

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

Step 7 Examine 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-east or west-to-west connection, physically switch the fiber connectors from the card that does not fit the pattern to the card that will continue the pattern should clear the alarm.


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



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.

Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.48 EXCCOL

Minor (MN), Non-Service Affecting

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

Procedure: Clear the EXCCOL Alarm

Troubleshoot the network management LAN connected to the TCC+ card for excess collisions. You may 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+ card has a flow rate set to 10 Mb, half-duplex.

Step 2 If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the TCC+ card and the network management LAN.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.49 EXERCISE-RING-REQ

Not Alarmed (NA) (Condition)

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


Note EXERCISE-RING-REQ is a condition and not an alarm. It does not require troubleshooting.


2.6.50 EXERCISE-SPAN-REQ

Not Alarmed (NA) (Condition)

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


Note EXERCISE-SPAN-REQ is a condition and not an alarm. It does not require troubleshooting.


2.6.51 EXT

Minor (MN), Non-Service Affecting

A Failure Detected External to the NE alarm is raised because an environmental alarm is present, for example, a door is open or flooding has occurred.

Procedure: Clear the EXT Alarm


Step 1 Open the AIC card Maintenance tab to gather further information about the EXT alarm.

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

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.52 EXTRA-TRAF-PREEMPT

Minor (MN), Non-Service Affecting

An Extra Traffic Preempted alarm is raised on OC-N cards in four-fiber BLSRs because low-priority traffic directed to the protect system has been preempted by a working system protection switch.

Procedure: Clear the EXTRA-TRAF-PREEMPT Alarm


Step 1 Verify the protection switch has occurred by 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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.53 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 the FAILTOSW alarm will free up the 1:N card and clear the FAILTOSW.


Note A higher-priority alarm is an alarm raised on the working DS-N or OC-N card using the 1:N card protection group. The working DS-N or OC-N card is reporting an alarm, but not reporting a FAILTOSW alarm.


Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the working electrical card. It is the working electrical card using the 1:N card protection and not reporting FAILTOSW.


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

Replacing the working electrical card reporting the higher-priority alarm will allow traffic to revert back to the working slot. The 1:N card is freed, and it 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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.54 FAILTOSW-PATH

Not Alarmed (NA) (Condition)

The Fail to Switch to Protection-Path condition occurs when the working path does not switch to the protection path on a UPSR. Common causes of the FAILTOSW-PATH alarm include a missing or defective protection card or a lockout set on one of the UPSR nodes.


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

Procedure: Clear the FAILTOSW-PATH Condition on a UPSR Configuration


Step 1 Complete the "Clear a UPSR Lockout" procedure to ensure there is no lockout set.

Step 2 If none is set, check the fiber connections to ensure they are securely fastened and intact.


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.

Step 3 If fiber connections are correct, ensure the OC-N cards are active and in service.

a. Confirm that the OC-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 OC-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 If OC-N cards are active and in service, verify that the protect OC-N card paired with the active reporting OC-N card is the same type and in service.

Step 5 If the alarm persists, complete the "Move Protection Group Traffic with a Switch Command" procedure for the reporting traffic card if it is active.

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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 8 If the condition persists, complete the Remove and Reinsert (Reseat) a Card for the reporting card.

Step 9 If the traffic does not switch, complete the Reset a Traffic Card in CTC.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 11 If the reset does not clear the condition, complete the "Move Protection Group Traffic with a Switch Command" procedure again after the protect cards have booted up completely.

Step 12 If you are unable to perform a switch, complete the "Remove and Reinsert (Reseat) a Card" procedure for the protect card.

Step 13 If the physical reset does not clear the condition, complete the "Move Protection Group Traffic with a Switch Command" procedure again.

Step 14 Complete the "Clear a Protection Group Switch Command" procedure.

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


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


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


Step 16 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.55 FAILTOSWR

Not Alarmed (NA) (Condition)

The Fail to Switch to Protection-Ring 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 an SF or 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 BLSR Configuration


Step 1 Perform the EXERCISE RING command on the BLSR.

a. Click the Provisioning > BLSR 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 OC-N cards that make up the ring or span and troubleshoot these alarms.

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

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

a. Confirm that the OC-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 OC-N port is in service, double-click the card in CTC to display the card view.

c. Click the Provisioning > Line tabs.

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

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

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

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

a. Confirm that the OC-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 OC-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 will disrupt service on the optical card. It may be necessary to manually switch traffic carrying circuits over to a protection path.

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

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

Step 9 If the signal is valid, clean the fiber. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

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

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

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


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

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

Step 14 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.56 FAILTOSWS

Not Alarmed (NA) (Condition)

The Failure to Switch to Protection-Span condition signals an APS span switch failure. For four-fiber BLSR, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS alarm will 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, see the "FAILTOSWR" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.57 FAN

Critical, Service Affecting

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan is not fully functional, the temperature of the ONS 15454 can rise above its normal operating range. The fan tray contains six fans and needs a minimum of five working fans to properly cool the ONS 15454. 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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the FAN Alarm


Step 1 Check the condition of the air filter to see whether it needs replacement. Refer to NTP-107, "Inspect and Maintain the Air Filter," in the Cisco ONS 15454 Procedure Guide for the detailed procedure.

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


Note The fan should run immediately when correctly inserted.


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

Step 4 If the replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.58 FE-AIS

Not Alarmed (NA) (Condition)

The Far-End AIS condition occurs when the far-end node's DS3XM-6 or DS3-12E card is reports an AIS. 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 the FE-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-AIS Condition


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

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

Step 3 View and clear the main alarm. See the "AIS" section.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.59 FE-DS1-MULTLOS

Not Alarmed (NA) (Condition)

The Far End Multiple DS1 LOS Detected on DS3XM-6 condition occurs when multiple inputs detect a loss on the far end. The prefix FE in an alarm/condition message means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-MULTLOS condition. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.

Procedure: Clear the FE-DS1-MULTLOS Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.60 FE-DS1-NSA

Not Alarmed (NA) (Condition)

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

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

Procedure: Clear the FE-DS1-NSA Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.61 FE-DS1-SA

Not Alarmed (NA) (Condition)

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

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 the FE-DS1-SA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-DS1-SA Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.62 FE-DS1-SNGLLOS

Not Alarmed (NA) (Condition)

The Far End Single DS1 LOS on the DS3XM-6 condition occurs when one of the DS1-14 ports on the far end detects an LOS. The prefix FE in an alarm/condition means the main alarm is occurring at the far-end node and not at the node reporting the FE-DS1-SNGLLOS alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.

Procedure: Clear the FE-DS1-SNGLLOS Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.63 FE-DS3-NSA

Not Alarmed (NA) (Condition)

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

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

Procedure: Clear the FE-DS3-NSA Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.64 FE-DS3-SA

Not Alarmed (NA) (Condition)

The Far End DS3 Equipment Failure Service Affecting condition occurs when a far-end DS-3 equipment failure occurs and affects service because even though the port is protected, traffic is unable to switch to the protect port.

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

Procedure: Clear the FE-DS3-SA Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.65 FE-EQPT-NSA

Not Alarmed (NA) (Condition)

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


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

Procedure: Clear the FE-EQPT-NSA Condition


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

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for troubleshooting instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.66 FE-EXERCISING-RING

Not Alarmed (NA) (Condition)

The Far End Exercising Ring condition is raised when far-end optical cards in a two-fiber BLSR 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 the FE-EXERCISING-RING condition. The condition clears on its own.


Note FE-EXERCISING-RING is a condition and not an alarm. It does not require troubleshooting.


2.6.67 FE-EXERCISING-SPAN

Not Alarmed (NA) (Condition)

The Far End Exercising Span condition is raised when far-end optical cards in a four-fiber BLSR 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 the FE-EXERCISING-SPAN condition. The condition clears on its own.


Note FE-EXERCISING-SPAN is a condition and not an alarm. It does not require troubleshooting.


2.6.68 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 the FE-FRCDWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-FRCDWKSWPR-RING Condition


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

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

Step 3 View and clear the main alarm. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.69 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 BLSR 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 the FE-FRCDWKSWPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-FRCDWKSWPR-SPAN Condition


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

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

Step 3 View and clear the main alarm. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.70 FE-IDLE

Not Alarmed (NA) (Condition)

The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal. The prefix FE in an alarm/condition means that the main alarm is occurring at the far-end node, not the node reporting the FE-IDLE condition. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarms clear when the main alarm clears.

Procedure: Clear the FE-IDLE Condition


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

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

Step 3 View and clear the main alarm. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.71 FE-LOCKOUTOFPR-SPAN

Not Alarmed (NA) (Condition)

The Far-End Lockout of Protection-Span condition is raised when a 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 the FE-LOCOUTOFPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-LOCKOUTOFPR-SPAN Condition


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

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

Step 3 Make sure there is no lockout set. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.72 FE-LOF

Not Alarmed (NA) (Condition)

The Far End LOF condition occurs when a far-end node reports a DS-3 loss of frame (LOF). The prefix FE in an alarm/condition means that the main alarm is occurring at the far-end node, not the node reporting the FE-LOF condition. Troubleshoot the FE alarm/condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.

Procedure: Clear the FE-LOF Condition


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

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

Step 3 View and clear the main alarm. See the "LOF (DS3)" section for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.73 FE-LOS

Not Alarmed (NA) (Condition)

The Far End LOS condition occurs when a far-end node reports a DS-3 LOS. The prefix FE in an alarm/condition message means that the main alarm is occurring at the far-end node, and not at the node reporting the FE-LOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both alarm/conditions clear when the main alarm clears.

Procedure: Clear the FE-LOS Condition


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

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

Step 3 View and clear the main alarm. See the "LOS (DS-3)" section for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.74 FE-MANWKSWPR-RING

Not Alarmed (NA) (Condition)

The Far End Ring Manual Switch of Working Facility to Protect condition is raised when a BLSR 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 the FE-MANWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-MANWKSWPR-RING Condition


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

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

Step 3 View and clear the main alarm. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.75 FE-MANWKSWPR-SPAN

Not Alarmed (NA) (Condition)

The Far-End Manual Switch Span Working Facility to Protect condition is raised when a BLSR 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 the alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.

Procedure: Clear the FE-MANWKSWPR-SPAN Condition


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

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

Step 3 View and clear the main alarm. See the "Clear a BLSR Span Command" procedure for instructions.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.76 FEPRLF

Minor (MN), Non-Service Affecting

The Far End Protection Line Failure alarm occurs when an APS switching channel signal failure occurs on the protect card coming into the node.


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


Procedure: Clear the FEPRLF Alarm on a Four-Fiber BLSR


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 condition on a card in Slot 12 of Node 1 may link to the main alarm from a card in Slot 6 of Node 2.

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

Step 3 View and clear the main alarm. Refer to the appropriate alarm section for instructions.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.77 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 about condition if you want the force switch to remain in place.

To clear the condition, complete the "Clear a BLSR Span Command" procedure. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.78 FORCED-REQ-RING

Not Alarmed (NA) (Condition)

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

To clear the condition, see the "FORCED-REQ" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.79 FORCED-REQ-SPAN

Not Alarmed (NA) (Condition)

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

To clear the condition, see the "FORCED-REQ" section. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.80 FRCDSWTOINT

Not Alarmed (NA) (Condition)

The Force Switch to Internal Timing condition occurs when the user issues a forced switch command to switch to Internal timing.


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


2.6.81 FRCDSWTOPRI

Not Alarmed (NA) (Condition)

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


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


2.6.82 FRCDSWTOSEC

Not Alarmed (NA) (Condition)

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


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


2.6.83 FRCDSWTOTHIRD

Not Alarmed (NA) (Condition)

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


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


2.6.84 FRNGSYNC

Major (MJ), Service Affecting

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

Procedure: Clear the FRNGSYNC Alarm


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

Step 2 If the ONS 15454 is configured to operate off 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 If the BITS source is valid, view and clear alarms related to the failures of the primary and secondary reference sources, such as the "SYNCPRI" section and the "SYNCSEC" section.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.85 FSTSYNC

Minor (MN), Non-Service Affecting

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

The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


Note FSTSYNC is an informational alarm and does not require troubleshooting.


2.6.86 FULLPASSTHR-BI

Not Alarmed (NA) (Condition)

The Bidirectional Full Pass-Through Active condition is raised on a non-switching node for a BLSR 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, complete the "Clear a BLSR Span Command" procedure. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.87 HITEMP

Critical, Service Affecting (NE)

Minor (MN), Non service affecting (EQPT)

The High Temperature alarm occurs when the temperature of the ONS 15454 is above 50 degrees Celsius (122 degrees Fahrenheit).


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

Procedure: Clear the HITEMP Alarm


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

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

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

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

Step 5 If faceplates fill the empty slots, check the condition of the air filter to see whether it needs replacement. Refer to NTP-107, "Inspect and Maintain the Air Filter," in the Cisco ONS 15454 Procedure Guide for the detailed procedure.

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


Note The fan should run immediately when correctly inserted.


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

Step 8 If the replacement fan tray does not operate correctly, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447) if it applies to the NE, or a non-service affecting problem if it applies to equipment.


2.6.88 HLDOVRSYNC

Major (MJ), Service Affecting

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

Procedure: Clear the HLDOVERSYNC Alarm


Step 1 View and clear additional alarms that relate to timing, such as FRNGSYNC, FSTSYNC, HLDOVRSYNC, LOF (BITS), LOS (BITS), MANSWTOINT, MANSWTOPRI, MANSWTOSEC, MANSWTOTHIRD, SWTOPRI, SWTOSEC, SWTOTHIRD, SYNC-FREQ, SYNCPRI, SYNCSEC, or SYNCTHIRD.

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

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.89 IMPROPRMVL

Critical, Service Affecting

The Improper Removal alarm occurs when a card is physically removed from its slot before it is deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm, it only needs to be recognized by CTC and the TCC+ card. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node.


Note CTC gives the user approximately 15 seconds to physically remove the card before CTC begins a card reboot.



Caution It can take up to 30 minutes for software to be updated on a standby TCC+ card.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the IMPROPRMVL Alarm


Step 1 If the card is not in service, right-click the card reporting the IMPROPRMVL and choose Delete.


Note CTC will not allow you to delete the reporting 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 2 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 CTC, double-click the reporting card to display the card view.

b. Click the Provisioning tab.

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

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

Step 3 If a circuit has been mapped to the card, complete the Delete a Circuit.


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

Step 4 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 5 If the card is provisioned for DCC, delete the SDCC provisioning.

a. Click the SONET DCC > Provisioning tabs.

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

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

Step 6 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 OC-N card to Internal Clock.

d. Click Apply.

Step 7 Right-click the card reporting the IMPROPRMVL and choose Delete.

Step 8 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.90 INC-ISD

Not Alarmed (NA) (Condition)

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


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


2.6.91 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 will remain 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. The Selected Group column will list 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 it is switched, click the Clear button.

Step 6 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.92 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 will remain locked onto 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. The Selected Group column will list 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 it is switched, click the Clear button.

Step 6 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.93 INVMACADR

Major (MJ), Non-Service Affecting

The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15454 Media Access Control layer address (MAC Address) is invalid. The MAC Address is permanently set into the ONS 15454 chassis when it is manufactured. Do not attempt to troubleshoot an INVMACADDR. Contact the Cisco Technical Assistance Center (TAC) at (1-800-553-2447).

2.6.94 KB-PASSTHR

Not Alarmed (NA) (Condition)

The K Bytes Pass Through Active condition is raised on a non-switching node for a BLSR 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, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.95 LKOUTPR-S

Not Alarmed (NA) (Condition)

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

To clear the lockout, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.96 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 OC-N card or a lockout switch request on a UPSR at the path level. A lockout prevents protection switching from occurring. Clearing the lockout will again allow protection switching to take place. Clearing the lockout switch request clears the LOCKOUT-REQ condition.

To clear the lockout, complete the Clear a UPSR Lockout. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.97 LOCKOUT-REQ-RING

Not Alarmed (NA) (Condition)

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

To clear the lockout, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.98 LOCKOUT-REQ-SPAN

Not Alarmed (NA) (Condition)

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

To clear the lockout, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.99 LOF (BITS)

Major (MJ), Service Affecting

The Loss of Frame (LOF) alarm occurs when a port on the TCC+ BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 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. 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+.

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. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.

c. Click the Provisioning > Timing tabs to display the General Timing window.

d. Verify that 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 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 B8ZS coding field is normally paired with ESF in the Framing field, and the 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+, complete the Physically Replace a Card for the TCC+ card.


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


Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.100 LOF (DS1)

Major (MJ), Service Affecting

The DS1 LOF alarm indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. If the LOF appears on the DS1-14 card, the transmitting equipment may have its framing set to a format that differs from the receiving ONS 15454.

Procedure: Clear the LOF Alarm


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

a. In CTC, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the signal source for the card reporting the alarm. You may need to contact your network administrator for the format information.

c. Display the card view of the reporting card.

d. Click the Provisioning > Line tabs.

e. Verify that the line type of the reporting port matches the line type of the signal source.

f. If the signal source line type does not match the reporting port, click Line Type to reveal a menu. Choose the matching type.

g. Verify that the reporting Line Coding matches the signal source's Line Type.

h. If the signal source line coding does not match the reporting port, click Line Coding to reveal the menu. Choose the matching type and click Apply.


Note On the Line tab, the B8ZS coding field is normally paired with ESF in the Framing field. AMI coding is normally paired with SF (D4) in the Framing field.



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


Step 2 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.101 LOF (DS3)

Critical, Service Affecting

The LOF alarm indicates that the receiving ONS 15454 lost frame delineation in the incoming data. The framing of the transmitting equipment may be set to a format that differs from the receiving ONS 15454. On DS3-12E cards, the alarm occurs only on cards with the provisionable framing format set to C-bit or M23, not on cards with the provisionable framing format is set to unframed.

To clear the alarm, change the line type of the non-ONS equipment attached to the reporting card to C-bit. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.102 LOF (EC1-12)

Critical, Service Affecting

The LOF alarm occurs when a port on the reporting EC1-12 card has an LOF condition. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.

LOF on an EC1-12 card is sometimes an indication that the EC1-12 card reporting the alarm expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver.


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

Procedure: Clear the LOF Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If cabling continuity is ok, clean the fiber connectors. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm does not clear, see "Network Troubleshooting Tests" section on page 1-2 to isolate the fault causing the LOF alarm.

Step 4 If the alarm does not clear, or if you need assistance in conducting network troubleshooting tests, call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.103 LOF (OC-N)

Critical, Service Affecting

The LOF alarm occurs when a port on the reporting OC-N card has an LOF condition. LOF indicates that the receiving ONS 15454 has lost frame delineation in the incoming data. LOF occurs when the SONET overhead loses a valid framing pattern for 3 milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.

LOF on an OC-N card is sometimes an indication that the OC-N card reporting the alarm expects a specific line rate and the input line rate source does not match the input line rate of the optical receiver.


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

Procedure: Clear the LOF Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If cabling continuity is ok, clean the fiber connectors. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 3 If the alarm does not clear, see the "Network Troubleshooting Tests" section on page 1-2 to isolate the fault causing the LOF alarm.

Step 4 If the alarm does not clear, or if you need assistance in conducting network troubleshooting tests, call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.104 LOP-P

Critical, Service Affecting

A Loss of Pointer alarm indicates that the pointer at the path level has been lost. LOP occurs when valid H1/H2 pointer bytes are missing from the SONET overhead. Receiving equipment monitors the H1/H2 pointer bytes to locate the SONET payload. A LOP alarm means that eight, nine, or ten consecutive frames do not have valid pointer values. The alarm clears when three consecutive valid pointers are received.

One of the conditions that can cause the LOP-P alarm is that the received payload does not match the provisioned payload. LOP-P causes a mismatch of the circuit type on the concatenation facility. For example, if an STS-3c or STS-1 is sent across a circuit provisioned for STS-12c, a LOP alarm occurs.


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

Procedure: Clear the LOP-P Alarm


Step 1 Verify the cabling and physical connections on the reporting card.

Step 2 If cabling and connections are ok, complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 4 If the reset does not clear the alarm, complete the Move Protection Group Traffic with a Switch Command.


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 5 Complete the Clear a Protection Group Switch Command.

Step 6 If the alarm does not clear, 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 7 Complete the Reset a Traffic Card in CTC for the far-end card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

Step 8 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, the ACT/STBY LED is illuminated.

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

Step 9 Complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 11 Complete the Move Protection Group Traffic with a Switch Command for the far-end working card.


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 12 Complete the Clear a Protection Group Switch Command.

Step 13 If the alarm does not clear, complete the Physically Replace a Card for the far-end card.


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


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


Step 14 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.105 LOP-V

Major (MJ), Service Affecting

The VT LOP alarm indicates a loss of pointer at the VT level. The VT, or electrical, layer occurs when the SONET signal is broken down into an electrical signal, for example, when an optical signal comes into an ONS 15454. The ONS 15454 demultiplexes the optical signal. One of the channels separated from the optical signal cross connects into a ONS 15454 DS3XM-6 or DS1-14 port. The ONS 15454 reports the LOS-V alarm.


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


Note In non-revertive UPSR configurations, VT-layer alarms or conditions (ending in *-V) are not reported when a switch occurs due to VT-level errors. Only WKSWPR is reported.


Procedure: Clear the LOP-V Alarm


Step 1 Verify the continuity of the cabling and physical connections on the reporting card.

Step 2 If cabling and connections are ok, complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 4 If the reset does not clear the alarm, complete the Move Protection Group Traffic with a Switch Command.


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 5 Complete the Clear a Protection Group Switch Command.

Step 6 If the alarm does not clear, the problem is at the far-end node. If the Verify the cabling and physical connections that connect to the far-end card.

Step 7 Complete the Reset a Traffic Card in CTC for the far-end card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

Step 8 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, the ACT/STBY LED is illuminated.

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

Step 9 Switch from the far-end working card to the far-end protect card.

Step 10 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.106 LOS (BITS)

Major (MJ), Service Affecting

This LOS alarm indicates the TCC+ card has an LOS from the BITS timing source. An LOS occurs when a SONET 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. 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 backplane BITS clock pin fields to the timing source.

Step 2 If wiring is ok, check that the BITS clock is operating properly.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.107 LOS (DS-1)

Major (MJ), Service Affecting

This 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. 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 cabling continuity to the port.

Step 2 If cabling is ok, verify that the correct port is in service.

a. Confirm that the OC-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 OC-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 If the correct port is in service, use an optical test set to confirm 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 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 5 If a valid signal exists, replace the DS-N connector on the ONS 15454.

Step 6 Repeat Steps 1- 5 for any other port on the card that reports the LOS.

Step 7 If the alarm does not clear, look for and troubleshoot any other alarm that may identify the source of the problem.

Step 8 If no other alarms are present that may be the source of the LOS, or if clearing such an alarm did not clear the LOS, complete the Physically Replace a Card for the reporting card.


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


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


Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.108 LOS (DS-3)

Major (MJ), Service Affecting

This 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. 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 cabling continuity to the port.

Step 2 If the cabling is ok, verify that the correct port is in service.

a. Confirm that the OC-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 OC-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 If the correct port is in service, use an optical test set to confirm 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 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 5 If a valid signal exists, replace the DS-N connector on the ONS 15454.

Step 6 Repeat Steps 1- 5 for any other port on the card that reports the LOS.

Step 7 If the alarm does not clear, look for and troubleshoot any other alarm that may identify the source of the problem.

Step 8 If no other alarms exist that may be the source of the LOS or if clearing such an alarm did not clear the LOS, complete the Physically Replace a Card for the reporting card.


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


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


Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.109 LOS (EC1-12)

Critical, Service Affecting

This LOS alarm on an EC1-12 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS means the upstream transmitter has failed. If an EC1-12 LOS alarm is not accompanied by additional alarms, a fiber break or cabling problem is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.


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

Procedure: Clear the LOS Alarm


Step 1 Verify cabling continuity to the port reporting the alarm.

Step 2 If the cabling is ok, verify that the correct port is in service.

a. Confirm that the OC-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 OC-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 If the correct port is in service, use an optical test set to confirm 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 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.

Step 5 If a valid signal exists, replace the cable connector on the ONS 15454.

Step 6 Repeat Steps 1- 5 for any other port on the card that reports the LOS.

Step 7 If the alarm does not clear, look for and troubleshoot any other alarm that may identify the source of the problem.

Step 8 If no other alarms exist that may be the source of the LOS or if clearing such an alarm did not clear the LOS, complete the Physically Replace a Card for the reporting card.


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


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


Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.110 LOS (OC-N)

Critical, Service Affecting

An OC-N LOS alarm occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS means the upstream transmitter has failed. If an OC-N LOS alarm is not accompanied by additional alarms, a fiber break is usually the cause of the alarm. The condition clears when two consecutive valid frames are received.


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. 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 fiber continuity to the port.

Step 2 If the cabling is ok, verify that the correct port is in service.

a. Confirm that the OC-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 OC-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 If the correct port is in service, clean the fiber connectors. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the OC-N card's receiver specifications. The "Optical Card Transmit and Receive Levels" section on page 1-77 lists these specifications for each card.

Step 5 If optical power level is within specifications, 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 6 If a valid signal exists, replace the connector on the backplane.

Step 7 Repeat Steps 1- 6 for any other port on the card reporting the alarm.

Step 8 If the alarm does not clear, look for and troubleshoot any other alarm that may identify the source of the problem.

Step 9 If no other alarms exist that may be the source of the LOS or if clearing such an alarm did not clear the LOS, complete the Physically Replace a Card for the reporting card.


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


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


Step 10 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.111 LPBKDS1FEAC

Not Alarmed (NA) (Condition)

A Loopback Caused by FEAC Command DS1 condition on the DS3XM-6 card occurs when a DS-1 loopback signal is received from the far-end node due to a Far-End Alarm and Control (FEAC) command. An FEAC command is often used with loopbacks.

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 about loopbacks, see the "Using the DS3XM-6 Card FEAC (Loopback) Functions" section on page 1-21.


Caution The CTC permits loopbacks on an in service circuit. Loopbacks are service affecting.


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


2.6.112 LPBKDS1FEAC-CMD

Not Alarmed (NA) (Condition)

The DS1 Loopback Command Sent To Far End condition when is raised when a FEAC loopback code is sent to a DS1 port on a DS3XM-6 card.


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


2.6.113 LPBKDS3FEAC

Not Alarmed (NA) (Condition)

A Loopback Due to FEAC Command DS3 condition occurs when a DS-3 loopback signal is received from the far-end node because of a Far-End Alarm and Control (FEAC) command. An FEAC command is often used with loopbacks. LPBKDS3FEAC is only reported by DS3-12E or DS3XM-6 cards. A DS3XM-6 card both generates and reports FEAC alarm/conditions, but a DS3-12E card only reports FEAC alarms/conditions.

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 about loopbacks, see the "Using the DS3XM-6 Card FEAC (Loopback) Functions" section on page 1-21.


Caution The CTC permits loopbacks on an in-service circuit. Loopbacks are service affecting.


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


2.6.114 LPBKDS3FEAC-CMD

Not Alarmed (NA) (Condition)

The DS3 Loopback Command Sent To Far End condition is raised when a FEAC loopback is sent to a DS3XM-6 card.


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


2.6.115 LPBKFACILITY (DS-N or EC1-12)

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 about loopbacks, see the "Network Troubleshooting Tests" section on page 1-2 or the "Identify Points of Failure on a DS-N Circuit Path" section on page 1-4.

There are three types of loopbacks: Facility, 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. Loopbacks are service affecting.


Note DS3XM-6 cards only support facility loopbacks on DS-1 circuits.


Procedure: Clear the LBKFACILITY 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 DS3XM-6 card, also click the DS1 tab.

Step 3 Complete the Clear a Loopback.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.116 LPBKFACILITY (OC-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 section 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 section. By setting up loopbacks on various parts of the network and excluding other parts, you can logically isolate the source of the problem. For more information about loopbacks, see the "Identify Points of Failure on an OC-N Circuit Path" section on page 1-22.

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.

To clear the loopback condition, complete the Clear a Loopback. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


Caution Before performing a facility loopback on an OC-N card, make sure the card contains at least two SDCC paths to the node where the card is installed. A second SDCC path provides a non-looped path to log into the node after the loopback is applied, thus enabling you to remove the facility loopback. Ensuring a second SDCC is not necessary if you are directly connected to the ONS 15454 containing the loopback OC-N.

2.6.117 LPBKTERMINAL (DS-N, EC1-12, OC-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 about loopbacks, see the "Network Troubleshooting Tests" section on page 1-2.

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.

To clear the loopback condition, complete the Clear a Loopback. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


Note Terminal loopback is not supported at the DS1 level for the DS3XM-6 card.


2.6.118 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 about loopbacks, see the "Network Troubleshooting Tests" section on page 1-2.

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. G1000-4 cards only support Terminal loopbacks. 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. Loopbacks are service affecting.

To clear the loopback condition, complete the Clear a Loopback. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.119 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 OC-N card or UPSR path. Clearing the manual switch clears the MAN-REQ alarm.

To clear the condition, complete the Clear a UPSR Lockout. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.120 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. The MANRESET condition clears automatically when the card finishes resetting.


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


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


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


2.6.123 MANSWTOSEC

Not Alarmed (NA) (Condition)

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


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


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


2.6.125 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 BLSR ring to switch from working to protect or protect to working.

To clear the condition, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.126 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 BLSR traffic from a working span to a protect span, or vice versa.

To clear the condition, complete the Clear a BLSR Span Command. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.127 MEA (AIP)

Critical, Service Affecting

If the Mismatch of Equipment Attributes (MEA) alarm is reported against the Alarm Interface Panel (AIP), the fuse in the AIP board blew or is missing. The MEA alarm also occurs when an old AIP board with a 2-Amp fuse is installed in a newer 10 Gbps-compatible or ANSI shelf assembly (15454-SA-ANSI).

To clear the alarm, complete the "Replace the Alarm Interface Panel" procedure on page 3-13. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

2.6.128 MEA (Bplane)

Critical (CR), Service Affecting

The MEA alarm for the backplane means that the revision of the backplane is incompatible with cross-connect (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 If the alarm does not clear, determine whether the ONS 15454 shelf assembly is a newer ANSI 10-Gbps compatible shelf assembly (15454-SA-ANSI) 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-19857-XX or 800-19856-XX, then you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly.

c. Under the Hardware Part # column, if the number is not 800-19856-XX or 800-19856-XX, then you are using an earlier shelf assembly.


Note On the 15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1 (P/N: 800-07149) shelves the AIP cover is clear plastic. On the 15454-SA-ANSI shelf (P/N: 800-19857), the AIP cover is metal.


Step 4 If the shelf assembly is not compatible with 10-Gbps equipment, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.129 MEA (EQPT)

Critical, Service Affecting

The MEA alarm for equipment is reported against a card slot when the physical card inserted into a slot does not match the card type that is provisioned for that slot in CTC. The alarm also occurs when certain cards introduced in Release 3.1 or later are inserted into an older, pre-ANSI (15454-SA-NEBS3E, hardware part number 800-08149-XX or older) shelf assembly or older Ethernet cards (E1000-2 and E100T-12) are used in a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI, hardware part number 800-19857-XX). Removing the incompatible cards to clear the alarm.

Procedure: Clear the MEA Alarm


Step 1 Determine whether the ONS 15454 shelf assembly is a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) or an earlier shelf assembly. At the CTC node (default login) view, click the Inventory tab.

Under the Hardware Part # column, if the part number is 800-19857-XX, then you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly.

Under the Hardware Part # column, if the number is not 800-19856-XX, then you are using an earlier shelf assembly.


Note On the 15454-SA-NEBS3E, 15454-SA-NEBS3, and 15454-SA-R1 (P/N: 800-07149) shelves the AIP cover is clear plastic. On the 15454-SA-ANSI shelf (P/N: 800-19857), the AIP cover is metal.


Step 2 Physically verify the type of card that sits in the slot reported in the object column of the MEA row on the Alarms tab by reading the name at the top of the card's faceplate.

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

b. If you have a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) and the card reporting the alarm is an E1000-2 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 ANSI 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 ANSI 10 Gbps compatible shelf assembly.


c. If you have an older, pre-ANSI 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-ANSI 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 any slot (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, complete the Physically Replace a Card for the reporting card.


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

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 turned on, or is used as a timing reference, then CTC will 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 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, complete the Delete a Circuit.:


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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.130 MEA (FAN)

Critical, Service Affecting

The MEA alarm is reported against the fan tray when a newer fan-tray assembly (15454-FTA3) with a 5 Amp fuse is used with an older shelf assembly or when an older fan tray with a 2 Amp fuse is used with a newer 10 Gbps compatible or ANSI shelf assembly (15454-SA-ANSI) that contains cards introduced in Release 3.1 or later. If a newer ANSI shelf assembly contains only cards introduced before Release 3.1, then an older fan-tray assembly (15454-FTA-2) can be used and will not report an MEA alarm.

Procedure: Clear the MEA Alarm


Step 1 Determine whether the ONS 15454 shelf assembly is a newer ANSI 10 Gbps compatible shelf assembly (15454-SA-ANSI) or an earlier shelf assembly. At the CTC node (default login) view, click the Inventory tab.

Under the Hardware Part # column, if the part number is 800-19857-XX or 800-19856-XX, then you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly.

Under the Hardware Part # column, if the number is not 800-19857-XX or 800-19856-XX, then you are using an earlier shelf assembly.

Step 2 If you have a 15454-SA-ANSI shelf or 10 Gbps compatible shelf assembly, 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 5 Amp fuse and complete the "Replace the Fan-Tray Assembly" procedure on page 3-11.

Step 3 If you are using an earlier shelf assembly, the alarm indicates that you are using a newer fan-tray assembly (15454-FTA3), which is incompatible with the earlier version of the shelf assembly. Obtain an earlier version of the fan-tray assembly (15454-FTA2) and complete the "Replace the Fan-Tray Assembly" procedure on page 3-11.

Step 4 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.131 MEM-GONE

Major (MJ), Non-Service Affecting

The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC+ card. CTC will not function properly until about alarm clears. The alarm clears when additional memory becomes available.

If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.132 MEM-LOW

Minor (MN), Non-Service Affecting

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

If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.133 MFGMEM

Critical, Service Affecting

The MFGMEM or Manufacturing Data Memory Failure alarm raises if the ONS 15454 cannot access the data in the erasable programmable read-only memory (EEPROM). Either the memory module on the component failed or the TCC+ lost the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. The EPROM on the alarm interface panel (AIP) also stores the MAC address. An inability to read a valid MAC address will disrupt IP connectivity and gray out the ONS 15454 icon on the CTC network view.

Procedure: Clear the MFGMEM Alarm on the AIP, Fan Tray, or Backplane


Step 1 Perform a CTC reset on the TCC+ card. Complete the Reset the Active TCC+ Card in CTC.

Wait ten minutes to verify that the card you reset completely reboots and displays as Standby. If not, call the Cisco Technical Assistance Center (1-800-553-2447).

Step 2 If the alarm has not cleared, call the Cisco Technical Assistance Center (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

Step 3 If the MFGMEM alarm continues to report after replacing the TCC+ cards, the problem lies in the EEPROM.

Step 4 If the MFGMEM is reported from the fan tray, obtain a fan-tray assembly and complete the "Replace the Fan-Tray Assembly" procedure on page 3-11.

Step 5 If the MFGMEM is reported from the AIP, the backplane, or the alarm persists after the fan tray is replaced, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.134  NOT-AUTHENTICATED

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

The NOT-AUTHENTICATED alarm is raised by CTC (not by the NE) when it fails to log into a node. This alarm only displays in CTC where the login failure occurred.


Note NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.


2.6.135 PDI-P

Not Alarmed (NA) (Condition)

A PDI Path condition indicates a signal label mismatch failure (SLMF). An invalid signal label C2 byte in the SONET path overhead causes an SLMF. The C2 byte tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.

The ONS 15454 encounters an SLMF when the payload, such as an ATM, does not match what the signal label is reporting. An AIS often accompanies the PDI-P condition. If the PDI-P is the only condition reported with the AIS, clear the PDI-P condition to clear the AIS condition. PDI-P can also occur during an upgrade, but usually clears itself and is not a valid condition.

A PDI-P condition reported on the port of an OC-N card supporting a G1000-4 card circuit might result from the end-to-end Ethernet link integrity feature of the G1000-4. If the link integrity is the cause, it typically is accompanied by an a TPTFAIL or a CARLOSS (G1000-4) reported against one or both Ethernet ports terminating the circuit. If TPTFAIL or CARLOSS are reported against one or both of the Ethernet ports, troubleshooting the accompanying alarm clears the PDI-P condition.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the PDI-P Condition


Step 1 Verify that all circuits terminating in the reporting card are in an active state.

a. Click the Circuits tab.

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

c. If the State column lists the port as incomplete, wait 10 minutes for the ONS 15454 to fully initialize. If incomplete does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

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

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


Caution Deleting a circuit may affect traffic.

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

Step 5 If circuit deletion and recreation does not clear the condition, check the far-end OC-N card that provides STS payload to the reporting card.

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

Step 7 If the condition does not clear, clean the far-end optical fiber. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

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


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


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


Step 9 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.136 PEER-NORESPONSE

Major (MJ), Non-Service Affecting

The switch agent raises a Peer Card Not Responding alarm if either traffic card in a protection group does not receive a response to the peer status request message. PEER-NORESPONSE is a software failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure between peer cards.

Procedure: Clear the PEER-NORESPONSE Alarm


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

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 3 Complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

Step 4 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, the ACT/STBY LED is illuminated.

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

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.137 PLM-P

Critical, Service Affecting

A Payload Label Mismatch-Path alarm indicates an SLMF. An invalid C2 byte in the SONET path overhead causes an SLMF. The C2 byte is the signal label byte. It tells the equipment what the SONET payload envelope contains and how it is constructed. It enables a SONET device to transport multiple types of services.

The ONS 15454 encounters an SLMF when the payload, such as a DS-3 signal, does not match what the signal label is reporting. An AIS alarm often accompanies the PLM-P alarm. If the PLM-P is the only alarm reported with the AIS, clearing the PLM-P alarm clears the AIS alarm.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the PLM-P Alarm


Step 1 Verify that all circuits terminating in the reporting card are active.

a. Click the Circuits tab.

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

c. If the State column lists the port as incomplete, wait 10 minutes for the ONS 15454 to fully initialize. If incomplete does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

Step 2 After determining the port is active, verify the signal source to the traffic card reporting the alarm with an optical test set according to site specific practice.

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

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


Caution Deleting a circuit may affect traffic.

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

Step 5 If the circuit deletion and recreation does not clear the alarm, verify the far-end OC-N card that provides STS payload to the DS-N card.

Step 6 If the alarm does not clear, verify the cross-connect between the OC-N card and the DS-N card.

Step 7 If the alarm does not clear, clean the far-end optical fiber. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 8 Complete the Physically Replace a Card for the reporting traffic card.


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


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


Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.138 PLM-V

Minor (MN), Service Affecting

A Payload Label Mismatch-VT Layer alarm indicates that the content of the V5 byte in the SONET overhead is inconsistent or invalid. PLM-V occurs when ONS nodes interoperate with equipment that performs bit-synchronous mapping for DS-1. ONS nodes use asynchronous mapping.


Note In non-revertive UPSR configurations, VT-layer alarms or conditions (ending in *-V) are not reported when a switch occurs due to VT-level errors. Only WKSWPR is reported.


Procedure: Clear the PLM-V Alarm


Step 1 Verify that your signal source matches the signal allowed by the traffic card. For example, the traffic card does not allow VT6 or VT9 mapping.

Step 2 If the signal source matches the card, verify that the SONET VT path originator is sending the correct VT label value. You can find the SONET VT path originator using circuit provisioning steps.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.139 PRC-DUPID

Major (MJ), Service Affecting

The Procedural Error-Duplicate Node ID alarm indicates that two identical node IDs exist in the same ring. The ONS 15454 requires each node in the ring to have a unique node ID.

Procedure: Clear the PRC-DUPID Alarm


Step 1 Log into a node on the ring.

Step 2 Find the node ID by completing the Identify a Ring ID or Node ID Number.

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

Step 4 If two nodes have an identical node ID number, complete the Change a Node ID Number so that each node ID is unique.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.140 PROTNA

Minor (MN), Non-Service Affecting

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

Step 2 If the alarm is raised against a line card, 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 a cross-connect card).

b. Click the Provisioning tab.

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

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

Step 3 Complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

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

Step 4 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, the ACT/STBY LED is illuminated.

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

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

Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.141 PWR-A

Major (MJ), Service Affecting

The NE Power Failure At Connector A alarm applies to the network element (NE) rack. It is raised when there is no power supplied to the main power connector. PWR-A 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 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-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 source and the power connector A.

Step 3 If the alarm does not clear, verify the continuity of the power connection with a voltmeter using the procedures in NTP-14, "Verify the Shelf Installation," in the Cisco ONS 15454 Procedure Guide.

Step 4 If the alarm does not clear, verify the source power output with a voltmeter following the procedures in NTP-14, "Verify the Shelf Installation," in the Cisco ONS 15454 Procedure Guide.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.142 PWR-B

Major (MJ), Service Affecting

The NE Power Failure at Connector B alarm applies to the NE rack. It is raised when there is no power supplied to the backup power connector. PWR-B 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 source and power connector B.

Step 3 If the alarm does not clear, verify the continuity of the power connection with a voltmeter using the procedures in NTP-14, "Verify the Shelf Installation," in the Cisco ONS 15454 Procedure Guide.

Step 4 If the alarm does not clear, verify the source power output with a voltmeter following the procedures in NTP-14, "Verify the Shelf Installation," in the Cisco ONS 15454 Procedure Guide.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.143 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 SONET path to the other. RAI on the DS3XM-6 card indicates that far-end node is receiving a DS-3 AIS.

To clear the condition, complete the "AIS" procedure. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.144 RCVR-MISS

Major (MJ), Service Affecting

A Facility Termination Equipment Receiver Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance usually occurs when a receive cable is missing from the DS1-14 port or a possible mismatch of backplane equipment, for example, an SMB connector or a BNC connector is connected to a DS1-14 card.


Note DS-1s are four-wire circuits and need a positive (tip) and negative (ring) connection for both transmit and receive.



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

Procedure: Clear the RCVR-MISS Alarm


Step 1 Ensure that the device attached to the DS1-14 port is operational.

Step 2 If the attachment is ok, verify that the cabling is securely connected.

Step 3 If the cabling is ok, verify that the pinouts are correct.

Step 4 If the pinouts are correct, replace the receive cable.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.145 RFI-L

Not Reported (NR) (Condition)

A Remote Fault Indication-Line condition occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-L alarm in the reporting node.

RFI-L indicates that the condition is occurring at the line level. The line layer is the segment between two SONET devices in the circuit and is also known as a maintenance span. The line layer deals with SONET payload transport. The line layer functions include multiplexing and synchronization.

Procedure: Clear the RFI-L Condition


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

Step 2 Check for alarms, especially LOS.

Step 3 View and clear alarms, especially LOS, by referring to the LOS sections as appropriate.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.146 RFI-P

Not Reported (NR) (Condition)

A Remote Failure Indication-Path condition occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-P alarm in the reporting node.

RFI-P occurs in the node that terminates a path. The path layer is the segment between the originating equipment and the terminating equipment. The path layer segment may encompass several consecutive line segments. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.

An RFI-P error message on the ONS 15454 indicates that the node reporting the RFI-P is the terminating node on that path segment.

Procedure: Clear the RFI-P Condition


Step 1 Verify that the ports are enabled and in service on the reporting ONS 15454.

a. Confirm that the OC-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 OC-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 2 To find the path and node failure, verify the integrity of the SONET STS circuit path at each of the intermediate SONET nodes.

Step 3 View and clear alarms in the node with the failure, especially UNEQ-P or UNEQ-V.

Step 4 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.147 RFI-V

Not Reported (NR) (Condition)

A Remote Fault Indication-VT Layer condition occurs when the ONS 15454 detects an RFI in the SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-V alarm in the reporting node.

RFI-V indicates that an upstream failure has occurred at the VT layer. The VT (electrical) layer is created when the SONET signal is broken down into an electrical signal, for example when an optical signal comes into an ONS 15454. If the optical signal is demultiplexed and one of the channels separated from the optical signal is cross connected into the DS1-14 port in the ONS 15454, the ONS 15454 reports an RFI-V alarm.


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


Note In non-revertive UPSR configurations, VT-layer alarms or conditions (ending in *-V) are not reported when a switch occurs due to VT-level errors. Only WKSWPR is reported.


Procedure: Clear the RFI-V Condition


Step 1 Check connectors to ensure they are securely fastened and connected to the correct slot/port. For more information, refer to NTP-19, "Install the Fiber-Optic Cables," in the Cisco ONS 15454 Procedure Guide.

Step 2 If connectors are correctly connected, verify that the DS1-14 port is active and in service.

a. Confirm that the OC-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 OC-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 If the ports are active and in service, check the signal source for errors using an optical test set.

Step 4 If the signal is valid, log into the node at the far-end of the reporting ONS 15454.

Step 5 View and clear alarms in the far-end node, especially UNEQ-P or UNEQ-V.

Step 6 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.148 RING-MISMATCH

Major (MJ), Service Affecting

A Procedural Error Mismatch-Ring alarm occurs when the ring ID of the ONS 15454 that is reporting the alarm does not match the ring ID of another ONS node in the BLSR. ONS nodes connected in a BLSR must have identical ring IDs to function.

Procedure: Clear the RING-MISMATCH Alarm


Step 1 From the node (default view), click the Provisioning > BLSR tabs.

Step 2 Note the number in the Ring ID field.

Step 3 Log into the next ONS node in the BLSR.

Step 4 Complete the Identify a Ring ID or Node ID Number.

Step 5 If the ring ID matches the ring ID in the reporting ONS node, repeat Step 4 for the next ONS node in the BLSR.

Step 6 If the ring ID does not match the ring ID in the reporting ONS node, complete the Change a Ring ID Number.

Step 7 Verify that the ring map is correct.

Step 8 Repeat Step 6 for all ONS nodes in the BLSR.

Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.149 RING-SW-EAST

Not Alarmed (NA) (Condition)

The Ring Switch Is Active-East Side condition occurs when a manual ring switch occurs at the east side of a two-fiber BLSR. The condition clears when the switch is cleared.


Note RING-SW-EAST is a condition and not an alarm. It is for information only and does not require troubleshooting.


2.6.150 RING-SW-WEST

Not Alarmed (NA) (Condition)

The Ring Switch Is Active-West Side condition occurs when a manual ring switch occurs at the west side of a two-fiber BLSR. The condition clears when the switch is cleared.


Note RING-SW-WEST is a condition and not an alarm. It is for information only and does not require troubleshooting.


2.6.151 SD-L

Not Alarmed (NA) (Condition)

A Signal Degrade-Line condition occurs when the quality of the signal is so poor that the bit error rate on the incoming optical line passed the signal degrade threshold. Signal degrade is defined by Telcordia as a "soft failure" condition. SD and signal fail (SF) both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF.

The BER threshold on the ONS 15454 is user provisionable and has a range for SD from 10-9 to 10-5.

SD-L causes a switch from the working card to the protect card at the line (facility) level. A line or facility level SD alarm travels on the B2 byte of the SONET overhead.

The SD condition clears when the BER level falls to one-tent h of the threshold level that triggered the alarm. A BER increase is sometimes caused by a physical fiber problem, including a faulty 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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the SD-L Condition


Step 1 Complete the Verify BER Threshold Level.

Step 2 If BER threshold is correct and at the expected level, use an optical test set to 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 If the optical power level is ok, verify that optical receive levels are within the acceptable range.

Step 4 If receive levels are ok, clean the fibers at both ends for a line signal degrade. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 5 If the alarm does not clear, verify that single-mode fiber is used.

Step 6 If the fiber is the correct type, verify that a single-mode laser is used at the far end.

Step 7 If the problem does not clear, the transmitter at the other end of the optical line may be failing and require replacement.


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

Step 8 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.152 SD-P

Not Alarmed (NA) (Condition)

A Signal Degrade-Path condition occurs 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 fail both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF.

For UPSR protected circuits, the BER threshold on the ONS 15454 is user provisionable and has a range for SD from 10-9 to 10-5. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user provisionable and the error rate is hard-coded to 10-6.

On UPSR, an SD-P condition causes a switch from the active card to the standby card at the path (STS) level. On BLSR 1+1 or on unprotected circuits, an SD-P condition does not cause switching.

A path or STS level SD alarm travels on the B3 byte of the SONET overhead. The ONS 15454 detects path SD on the STS level, not the VT level.

The SD alarm clears when the BER level falls to one-tent h 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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the SD-P Condition


Step 1 Complete the Verify BER Threshold Level.

Step 2 If the BER is ok and at the expected level, use an optical test set to 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 If the optical power level is ok, verify that optical receive levels are within the acceptable range.

Step 4 If the receive level is ok, verify that single-mode fiber is being used.

Step 5 If the fiber is correct, verify that a single-mode laser is being used at the far end.

Step 6 If the problem does not clear, the transmitter at the other end of the optical line may be failing and require replacement.


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

Step 7 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.153 SF-L

Not Alarmed (NA) (Condition)

A Signal Fail-Line condition occurs when the quality of the signal is so poor that the BER on the incoming optical line passed the signal failure threshold. 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.

The BER threshold on the ONS 15454 is user provisionable and has a range for SF from 10-5 to 10-3.

SF-L causes a switch from the working card to the protect card at the line (facility) level. A line or facility level SF alarm travels on the B2 byte of the SONET overhead.

SF causes a card to switch from working to protect at either the path or line 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.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the SF-L Condition


Step 1 Complete the Verify BER Threshold Level.

Step 2 If the BER is ok, and at the expected level, use an optical test set to 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 If the optical power is ok, verify that optical receive levels are within the acceptable range.

Step 4 If the receive levels are ok, clean the fibers at both ends for a line signal failure. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 5 If the alarm does not clear, verify that single-mode fiber is being used.

Step 6 If the correct fiber is used, verify that a single-mode laser is being used at the far-end node.

Step 7 If the problem does not clear, the transmitter at the other end of the optical line may be failing and need replacement.


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

Step 8 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.154 SF-P

Not Alarmed (NA) (Condition)

A Signal Fail-Path condition occurs when the quality of the signal is so poor that the BER on the incoming optical line passed the signal failure threshold. 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.

For UPSR circuits, the BER threshold on the ONS 15454 is user provisionable and has a range for SF from 10-5 to 10-3. For BLSR 1+1 or unprotected circuits, the BER threshold value is not user provisionable and the error rate is hard-coded to 10-3.

For UPSR, SF-P causes a switch from the active card to the standby card at the path (STS) level. For BLSR 1+1 or unprotected circuits, SF-P does not cause switching.

A path or STS level SF alarm travels on the B3 byte of the SONET overhead. The ONS 15454 detects path SF on the STS level, not the VT 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.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.

Procedure: Clear the SF-P Condition


Step 1 Complete the Verify BER Threshold Level.

Step 2 If the BER is correct and at the expected level, use an optical test set to 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 If the optical power level is ok, verify that optical receive levels are within the acceptable range.

Step 4 If the receive levels are ok, verify that single-mode fiber is being used.

Step 5 If the fiber is correct, verify that a single-mode laser is being used at the far-end node.

Step 6 If the problem does not clear, the transmitter at the other end of the optical line may be failing and need replacement.


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

Step 7 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.155 SFTWDOWN

Minor (MN), Non-Service Affecting


Caution It can take up to 30 minutes for software to be updated on a standby TCC+ card.

A Software Download in progress alarm occurs when the TCC+ is downloading or transferring software.

No action is necessary. Wait for the transfer or the software download to complete. If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


Note SFTWDOWN is an informational alarm.


2.6.156 SNTP-HOST

Minor (MN), Non-Service Affecting

The SNTP (Simple Network Timing Protocol) Host Failure alarm indicates that an ONS node serving as an IP proxy for the other ONS nodes in the ring is not forwarding SNTP information to the other ONS nodes in the network. The forwarding failure can result from two causes, either 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 who manages the IP network supplying the SNTP information to the proxy and determine whether the network is experiencing problems which may affect the SNTP server/router connecting to the proxy ONS 15454.

Step 3 If no network problems exist, ensure that the ONS 15454 proxy is provisioned correctly.

a. On the ONS node serving as the proxy, click the CTC Provisioning > General tabs.

b. Ensure the Enable Proxy checkbox is checked.

c. If the Enable Proxy checkbox is not checked, click it.

Step 4 If proxy is correctly provisioned, refer to the Cisco ONS 15454 Reference Manual for more information on SNTP Host.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.157 SPAN-SW-EAST

Not Alarmed (NA) (Condition)

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


Note SPAN-SW-EAST is a condition and not an alarm. It is for information only and does not require troubleshooting.


2.6.158 SPAN-SW-WEST

Not Alarmed (NA) (Condition)

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


Note SPAN-SW-EAST is a condition and not an alarm. It is for information only and does not require troubleshooting.


2.6.159 SQUELCH

Not Alarmed (NA) (Condition)

The Ring Squelching Traffic condition occurs in a BLSR 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 will disable 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 AIS-P alarm will also appear 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. 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 grayed out node with red spans will be the isolated node.

Step 2 Verify fiber continuity to the ports on the isolated node.

Step 3 If fiber continuity is ok, verify that the proper ports are in service.

a. Confirm that the OC-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 OC-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 If the correct ports are in service, use an optical test set to verify that a valid signal exists on the line.

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

Step 5 If the signal is valid, verify that the power level of the optical signal is within the optical card's receiver specifications. Refer to the Cisco ONS 15454 Reference Manual for card specifications.

Step 6 If the receiver levels are ok, ensure that the optical transmits and receives are connected properly.

Step 7 If the connectors are ok, complete the Physically Replace a Card for the OC-N card.


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

Step 8 the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.160 SSM-DUS

Not Alarmed (NA) (Condition)

The Synchronization Status (SSM) 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. The DUS signal can also be sent for line maintenance testing.


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


2.6.161 SSM-FAIL

Minor (MN), Non-Service Affecting

The Failed to Receive Synchronization Status Message alarm occurs when the synchronization status messaging received by the ONS 15454 fails. The problem is external to ONS 15454. The ONS 15454 is set up to receive SSM, but the timing source is not delivering valid SSM messages.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.

Procedure: Clear the SSM-FAIL Alarm


Step 1 Verify that SSM is enabled on the external timing source.

Step 2 If timing is enabled, use an optical test set to determine that the external timing source is delivering SSM.

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

If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.162 SSM-OFF

Not Alarmed (NA) (Condition)

The Synchronization Status Messages Disabled on Interface condition applies to references used for timing the node. It occurs when the SSM for the reference has been turned off. The ONS 15454 is set up to receive SSM, but the timing source is not delivering SSM messages.

SSM is an SDH protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH line layer. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.

To clear the condition, complete the "SSM-FAIL" procedure. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.163 SSM-PRS

Not Alarmed (NA) (Condition)

The SSM Stratum 1 Primary Reference Source Traceable condition occurs when the SSM transmission level is changed to Stratum 1 Traceable.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.164 SSM-RES

Not Alarmed (NA) (Condition)

The SSM Reserved For Network Synchronization Use condition occurs when the synchronization message quality level is changed to RES.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.165 SSM-SMC

Not Alarmed (NA) (Condition)

The SSM SONET Minimum Clock Traceable condition occurs when the synchronization message quality level changes to SMC. The NE will not use the clock since it will not use any reference beneath its internal level, which is ST3.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.166 SSM-ST2

Not Alarmed (NA) (Condition)

The SSM Stratum 2 Traceable condition occurs when the synchronization message quality level is changed to ST2.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.167 SSM-ST3

Not Alarmed (NA) (Condition)

The SSM Stratum 3 Traceable condition occurs when the synchronization message quality level is changed to ST3.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.168 SSM-ST3E

Not Alarmed (NA) (Condition)

The SSM Stratum 3E Traceable condition indicates the synchronization message quality level is changed to ST3E from a lower level of synchronization. SSM-ST3E is a Generation 2 SSM, and is not used for Generation 1.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.169 SSM-ST4

Not Alarmed (NA) (Condition)

The SSM Stratum 4 Traceable condition occurs when the synchronization message quality level is lowered to ST4. The message quality is not used since it is below ST3.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.170 SSM-STU

Not Alarmed (NA) (Condition)

The SSM Synchronization Traceability Unknown condition occurs when the reporting node is timed to a reference that does not support synchronization status messaging (SSM), but the ONS 15454 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.

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. SSM enables SONET 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 Sync Messaging is checked, uncheck the box.

Step 3 If Sync Messaging is unchecked, check the box.

Step 4 Click Apply.

Step 5 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.171 SSM-TNC

Not Alarmed (NA) (Condition)

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

SSM is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET line layer. They enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.


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


2.6.172 SWMTXMOD

Critical, Service Affecting

The Switching Matrix Module Failure alarm occurs on the cross-connect card or a traffic card. If the alarm reports against a traffic card, it means that the logic component on the cross-connect card is out of frame (OOF) with the logic component on the reporting traffic card. All traffic on the reporting traffic card is lost.

If the alarm reports against a cross-connect (XCVT) card, it means that a logic component internal to the reporting cross-connect (XCVT) card is out of frame with a second logic component on the same cross-connect card (XCVT). One or more traffic cards may lose traffic as a result of the cross-connect frame failure.

Procedure: Clear the SWMTXMOD Alarm


Step 1 If the card reporting the alarm is the standby cross-connect card (XCVT), complete the Reset a Traffic Card in CTC for the card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

Step 4 If the card reporting the alarm is the active cross-connect card (XCVT), complete the Side Switch the Active or Standby Cross-Connect Card.


Note After the active cross-connect goes into standby, the original standby slot becomes active. The former standby card ACT/STBY LED becomes green.


Step 5 If the card reporting the alarm is not the active cross-connect card (XCVT) or if you completed the side switch in Step 4, complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

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

Step 8 If the card reporting the alarm is an I/O card, complete the Side Switch the Active or Standby Cross-Connect Card.

Step 9 If the alarm does not clear after the cross-connect card (XC, XCVT, XC10G) side switch, complete the Reset a Traffic Card in CTC for the reporting card.

While the card resets, the FAIL LED on the physical card will blink and turn off.

While the card resets, the 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, the ACT/STBY LED is illuminated.

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

Step 11 If the alarm does not clear, complete the Remove and Reinsert (Reseat) a Card for the traffic line card.

Step 12 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.173 SWTOPRI

Not Alarmed (NA) (Condition)

The Synchronization Switch to Primary Reference condition occurs when the ONS 15454 switches to the primary timing source (reference 1). The ONS 15454 uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.


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


2.6.174 SWTOSEC

Not Alarmed (NA) (Condition)

The Synchronization Switch to Secondary Reference condition occurs when the ONS 15454 has switched to the secondary timing source (reference 2). The ONS 15454 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 on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.175 SWTOTHIRD

Not Alarmed (NA) (Condition)

The Synchronization Switch to Third Reference condition occurs when the ONS 15454 has switched to the third timing source (reference 3). The ONS 15454 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 SYNCSEC alarms. If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

2.6.176 SYNC-FREQ

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 the reference and choose another internal or external reference to use.

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 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 outside of bounds, complete the Physically Replace a Card for the TCC+ card.


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



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


Step 3 If the SYNC-FREQ alarm continues to report after replacing the TCC+ card, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.177 SYNCPRI

Minor (MN), Non-Service Affecting

A Loss of Timing on Primary Reference alarm occurs when the ONS 15454 loses the primary timing source (reference 1). The ONS 15454 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 should switch to its secondary timing source (reference 2). Switching to the secondary timing source also triggers the SWTOSEC alarm.

Procedure: Clear the SYNCPRI Alarm


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, complete the "LOS (BITS)" procedure.

Step 4 If the primary reference clock is an incoming port on the ONS 15454, complete the "LOS (OC-N)" procedure.

Step 5 If the condition does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.178 SYNCSEC

Minor (MN), Non-Service Affecting

A Loss of Timing on Secondary Reference alarm occurs when the ONS 15454 loses the secondary timing source (reference 2). The ONS 15454 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 should switch to the third timing source (reference 3) to obtain valid timing for the ONS 15454. Switching to the third timing source also triggers the SWTOTHIRD condition.

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, complete the "LOS (BITS)" procedure.

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, complete the "LOS (OC-N)" procedure.

Step 6 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (1-800-553-2447).


2.6.179 SYNCTHIRD

Minor (MN), Non-Service Affecting

A Loss of Timing on Third Reference alarm occurs when the ONS 15454 loses the third timing source (reference 3). The ONS 15454 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 uses an internal reference for source three, the TCC+ card may have failed. The ONS 15454 often reports either FRNGSYNC or HLDOVRSYNC alarms after a SYNCTHIRD alarm.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right 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 NTP-28, "Set Up Timing," in the Cisco ONS 15454 Procedure Guide.

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

Step 4 If the third timing source is an incoming port on the ONS 15454, complete the "LOS (OC-N)" procedure.

Step 5 If the third timing source uses the internal ONS 15454 timing, complete the Reset the Active TCC+ Card in CTC.

Wait ten minutes to verify that the card you reset completely reboots and displays as Standby. If not, call the Cisco Technical Assistance Center (1-800-553-2447).

Step 6 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) the Standby TCC+" section on page 3-4.

Step 7 If the alarm has not cleared, call the Cisco Technical Assistance Center (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+" procedure on page 3-4. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.


2.6.180 SYSBOOT

Major (MJ), Service Affecting

The System Reboot alarm indicates that new software is booting on the TCC+ card. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 30 minutes.

If it does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


Note SYSBOOT is an informational alarm and does not require troubleshooting.


2.6.181 TIM-P

Minor (MN), Service Affecting

The STS Path Trace Identifier Mismatch (TIM) Path alarm occurs when the expected path trace string does not match the received path trace string. Path Trace Mode must be set to manual or Auto for the TIM-P alarm to occur.

In manual mode at the Path Trace window, the user types the expected string into the New Expected String field for the receiving port. The string must match the string typed into the New Transmit String field for the sending port. If these fields do not match, the TIM-P alarm will occur. In Auto mode on the receiving port, the card sets the expected string to the value of the received string. If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the New Transmit String field. Follow the procedure below to clear either instance.

TIM-P also occurs on a port that has previously been operating without alarms if someone switches or removes the DS-3 cables or optical fibers that connect the ports. TIM-P is usually accompanied by other alarms, such as LOS, UNEQ-P, or PLM-P. If these alarms accompany TIM-P, reattach or replace the original cables/fibers to clear the alarms.

Procedure: Clear the TIM-P Alarm


Step 1 Log into the circuit source node and select the Circuits tab.

Step 2 Select the circuit reporting the alarm, then click Edit.

Step 3 At the bottom of the Edit Circuit window, check the Show Detailed Map box.

Step 4 On the detailed circuit map, right-click the source circuit port and choose Edit Path Trace from the shortcut menu.

Step 5 On the detailed circuit map, right-click the drop/destination circuit port and choose Edit Path Trace from the shortcut menu.

Step 6 Compare the New Transmit String and the New Expected String entries in the Path Trace Mode dialog box.

Step 7 If the strings differ, correct the Transmit or Expected strings and click Apply.

Step 8 Click Close.

Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.182 TPTFAIL

Major (MJ), Service Affecting

The Transport (TPT) Layer Failure alarm indicates a break in the end-to-end Ethernet link integrity feature of the G1000-4 cards. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL.

The TPTFAIL alarm indicates a problem on either the SONET path or the remote Ethernet port, which prevents the complete end-to-end Ethernet path from working. If any SONET path alarm such as AIS-P, LOP-P, UNEQ-P, or PDI-P exists on the SONET path used by the Ethernet port, the affected port raises a TPTFAIL alarm. Also, if the far-end G1000-4 Ethernet port is administratively disabled or it is seeing a CARLOSS condition it will set the C2 byte in the SONET path overhead to indicate a payload defect condition (PDI-P) which in turn will cause a TPTFAIL to be reported against the near-end port.

When a TPTFAIL alarm occurs, the near-end port is automatically disabled (transmit laser turned off). In turn the laser shutoff can also cause the external Ethernet device attached at the near end to detect a link down and turn off its transmitter and also cause a CARLOSS condition to occur on the reporting port. In all cases the source problem is either in the SONET path being used by the G1000-4 port or 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 SONET path that the port is using or with the far end G1000-4 port that is mapped to the port. View and clear any alarms being reported by the OC-N card utilized by the Ethernet circuit of the G1000-4.

Step 2 If no alarms are reported by the OC-N card, or if a PDI-P condition is reported, the problem may be on the far-end G1000-4 port that the port reporting TPTFAIL is mapped to. View and clear any alarms, such as CARLOSS, reported against the far-end port or card.

Step 3 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.183 TRMT

Major (MJ), Service Affecting

A Missing Transmitter alarm occurs when there is a transmit failure on the DS1-14 card because of an internal hardware failure. The card must be replaced.

Procedure: Clear the TRMT Alarm


Step 1 Complete the Physically Replace a Card for the reporting DS1-14 card.


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


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


Step 2 If the alarm does not clear, call the Technical Assistance Center (TAC) at (1-800-553-2447) to discuss the failed card and possibly open a returned materials authorization (RMA).


2.6.184 TRMT-MISS

Major (MJ), Service Affecting

A Facility Termination Equipment Transmitter Missing alarm occurs when the facility termination equipment detects an incorrect amount of impedance on its backplane connector. Incorrect impedance is detected when a transmit cable is missing on the DS1-14 port or the backplane does not match the inserted card; for example, an SMB connector or a BNC connector connects to a DS1-14 card instead of a DS-3 card.


Note DS-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.


Procedure: Clear the TRMT-MISS Alarm


Step 1 Check that the device attached to the DS1-14 port is operational.

Step 2 If the device is operational, verify that the cabling is securely connected.

Step 3 If the cabling is secure, verify that the pinouts are correct.

Step 4 If the pinouts are correct, replace the transmit cable.

Step 5 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.185 UNEQ-P

Critical, Service Affecting

A Signal Label Mismatch Failure Unequipped-Path alarm occurs when the path does not have a valid sender. The UNEQ-P indicator is carried in the C2 signal path byte in the SONET overhead. The source of the problem is the node that is transmitting the signal into the node reporting the UNEQ-P.

The alarm may result from an incomplete circuit or an empty VT tunnel, which is a VT tunnel with no valid VT circuit inside. Empty VT tunnels can result when a user highlights both a VT tunnel and VT circuit in CTC and attempts to delete them simultaneously. If the user attempts double deletion, CTC will delete only the VT circuit. The empty VT tunnel raises an UNEQ-P alarm.

UNEQ-P occurs in the node that terminates a path. The path layer is the segment between the originating equipment and the terminating equipment. The path segment can encompass several consecutive line segments. The originating equipment puts bits together into a SONET payload and the terminating equipment breaks the bits apart again. SONET multiplexers, such as the ONS 15454, often perform the origination and termination tasks of the SONET payload.


Note If you have created a new circuit but it has no signal, an UNEQ-P alarm is reported on the OC-N cards and an AIS-P alarm is reported on the terminating cards. These alarms clear when the circuit carries a signal.



Caution Deleting a circuit affects traffic.


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

Procedure: Clear the UNEQ-P Alarm


Step 1 Display the CTC network view.

Step 2 Right-click the alarm to display the Select Affected Circuits dialog.

Step 3 Click the Select Affected Circuits dialog.

Step 4 When the Affected Circuits appear, look in the Type column for VTT, which indicates a VT tunnel Circuit. A VT tunnel with no VTs assigned may be the cause of an UNEQ-P alarm.

Step 5 If the Type column does not contain VTT there are no VT tunnels connected with the alarm, go to Step 7.

Step 6 If the Type column does contain VTT, attempt to delete these row(s).


Note The CTC will not allow you to delete a valid VT tunnel or one with a valid VT circuit inside.


a. Click the VT tunnel circuit row to highlight it. Complete the Delete a Circuit.

b. If an error message dialog appears, the VT tunnel is valid and not the cause of the alarm.

c. If any other columns contain VTT, repeat Step 6.

Step 7 If all ONS nodes in the ring appear in the CTC network view, check for incomplete circuits.

a. Click the Circuits tab.

b. Verify that INCOMPLETE is not listed in the State column of any circuits.

Step 8 If you find circuits listed as incomplete, verify these circuits are not working circuits that continue to pass traffic with an appropriate optical test set and site-specific procedures.

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

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Click the row under the State column with incomplete and complete the Delete a Circuit.

Step 10 Log back in and verify that all circuits terminating in the reporting card are active.

a. Click the Circuits tab.

b. Verify that the State column lists all circuits as active.

Step 11 If the alarm does not clear, clean the far-end optical fiber.Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.


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.

Step 12 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.186 UNEQ-V

Major (MJ), Service Affecting

An Signal Label Mismatch Failure Unequipped-VT alarm indicates that the node is receiving SONET path overhead with bits 5, 6, and 7 of the V5 overhead byte all set to zeroes. The source of the problem is the node that is transmitting the VT-level signal into the node reporting the UNEQ-P. The problem node is the next node upstream that processes the signal at the VT level.

The V in UNEQ-V indicates that the failure has occurred at the VT layer. The VT (electrical) layer is created when the SONET signal is broken down into an electrical signal, for example, when an optical signal comes into an ONS 15454, the optical signal is demultiplexed and one of the channels separated from the optical signal is cross connected into an ONS 15454 cross-connect card (XC/XCVT/XC10G) and the corresponding DS-N card.


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. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.


Note In non-revertive UPSR configurations, VT-layer alarms or conditions (ending in *-V) are not reported when a switch occurs due to VT-level errors. Only WKSWPR is reported.


Procedure: Clear the UNEQ-V Alarm


Step 1 Verify that all circuits terminating in the reporting card are active.

a. Click the Circuits tab.

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

c. If the State column lists the port as incomplete. If incomplete does not change after full initialization, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).

Step 2 After you determine that the port is active, verify the signal source being received by the DS-N card reporting the alarm.

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


Caution Deleting a circuit can be service affecting.

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

Step 5 If circuit deletion and recreation does not clear the alarm, check the far-end OC-N card that provides STS payload to the DS-N card.

Step 6 If the far-end card is ok, verify the cross-connect between the OC-N card and the DS-N card.

Step 7 If the cross-connect is ok, clean the far-end optical fiber. Complete NTP-112, "Clean Fiber Connectors," in the Cisco ONS 15454 Procedure Guide.

Step 8 If the alarm does not clear, complete the "Physically Replace a Card" section for the OC-N/DS-N cards.


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


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


Step 9 If the alarm does not clear, log on to http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center to report a service affecting problem (1-800-553-2447).


2.6.187 WKSWPR

Not Alarmed (NA) (Condition)

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


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


2.6.188 WTR

Not Alarmed (NA) (Condition)

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


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


2.7 DS3-12E Line Alarms

Unlike the standard DS-3 card, which uses the unframed format exclusively, the DS3-12E card provides three choices: unframed, M23, or C-bit. The choice of framing format affects which line alarms the DS3-12E card reports. The table below lists the line alarms reported under each format.

The choice of framing format does not affect the reporting of STS alarms. Regardless of format, the DS3-12E card reports the same STS alarms as the standard DS-3 card.

Table 2-8 DS3-12E Line Alarms 

Alarm
UNFRAMED
M23
CBIT

LOS

u

u

u

AIS

u

u

u

LOF

m

u

u

IDLE

m

u

u

RAI

m

u

u

Terminal Lpbk

u

u

u

Facility Lpbk

u

u

u

FE Lpbk

m

m

u

FE Common Equipment Failure

m

m

u

FE Equipment Failure-SA

m

m

u

FE LOS

m

m

u

FE LOF

m

m

u

FE AIS

m

m

u

FE IDLE

m

m

u

FE Equipment Failure-NSA

m

m

u


2.8 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 Procedure Guide.

Procedure: Identify a Ring ID or Node ID Number


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

Step 2 From the View menu, choose Go to Network View.

Step 3 Click the Provisioning > BLSR tabs.

From the Ring ID column, record the ring ID, or from the Nodes column, record the Node IDs in the BLSR. 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 > BLSR tabs.

Step 4 Highlight the row of the ring and click Edit.

Step 5 In the BLSR 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 > BLSR tabs.

Step 4 Highlight the ring and click Edit.

Step 5 In the BLSR 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 > BLSR tabs.

Step 3 Highlight a BLSR.

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 > SONET 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 an SDCC 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 the Disable OSPF on DCC Link checkbox is unchecked.

e. Click OK.


Procedure: Lock Out a BLSR 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 > BLSR tabs.

Step 3 Click the BLSR 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 BLSR Operations dialog box.


Procedure: Clear a BLSR 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 > BLSR tabs.

Step 3 Click the BLSR 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 BLSR Operations dialog box.


Procedure: Clear a UPSR 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 On the Confirm UPSR Switch dialog box, click Yes.

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

On the Circuits on Span window, the Switch State for all UPSR 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 and Yes in the Confirmation dialog box.


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


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 Determine the active or standby 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 (default login) 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 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 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 are already logged in, go to Step 2.

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

Step 3 Click the Circuits tab.

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

Step 5 Click Yes at the Delete Circuits dialog box.


Procedure: Clear a Loopback


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

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, see whether any port row displays a state besides None.

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

Step 6 In the State column, see whether any port row displays a state besides INS.

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

Step 8 Click Apply.


Procedure: Reset the Active TCC+ Card in CTC


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

Step 2 Identify the active TCC+.

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

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

Step 3 Right-click the active TCC+.

Step 4 Choose Reset Card from the shortcut menu.

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

The card resets, the FAIL LED blinks on the physical card, and then no LED will be illuminated.

While the card resets, the 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, the ACT/STBY LED is steadily illuminated amber.

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


Procedure: Reset a Traffic Card in CTC


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 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 are already logged in, go to Step 2.

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

Step 3 From the CTC node (default login) 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 pane, 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 2.

Step 7 If the entry is not consistent with what the system was originally provisioned for, click on 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


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


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: Remove and Reinsert (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: Remove and Reinsert 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.

Step 3 Close the retractable handles.