Cisco ONS 15327 Troubleshooting Guide, Release 7.0 - Chapter 2, Alarm Troubleshooting [Cisco ONS 15300 Series]

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Index by Default Severity

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  Not Alarmed Conditions

2.1.5  Not Reported Conditions

2.2  Alarms and Conditions Listed By Alphabetical Entry

2.3  Alarm Logical Objects

2.4  Alarm List by Logical Object Type

2.5  Trouble Notifications

2.5.1  Alarm Characteristics

2.5.2  Condition Characteristics

2.5.3  Severities

2.5.4  Alarm Hierarchy

2.5.5  Service Effect

2.5.6  States

2.6  Safety Summary

2.7  Alarm Procedures

2.7.1  AIS

Clear the AIS Condition

2.7.2  AIS-L

Clear the AIS-L Condition

2.7.3  AIS-P

Clear the AIS-P Condition

2.7.4  AIS-V

Clear the AIS-V Condition

2.7.5  ALS

2.7.6  APC-DISABLED

2.7.7  APC-END

2.7.8  APSB

Clear the APSB Alarm

2.7.9  APSCDFLTK

Clear the APSCDFLTK Alarm

2.7.10  APSC-IMP

Clear the APSC-IMP Alarm

2.7.11  APSCINCON

Clear the APSCINCON Alarm

2.7.12  APSCM

Clear the APSCM Alarm

2.7.13  APSCNMIS

Clear the APSCNMIS Alarm

2.7.14  APSIMP

Clear the APSIMP Alarm

2.7.15  APS-INV-PRIM

2.7.16  APSMM

Clear the APSMM Alarm

2.7.17  APS-PRIM-FAC

2.7.18  APS-PRIM-SEC-MISM

2.7.19  AS-CMD

Clear the AS-CMD Condition

2.7.20  AS-MT

Clear the AS-MT Condition

2.7.21  AS-MT-OOG

Clear the AS-MT-OOG Alarm

2.7.22  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.23  AUD-LOG-LOW

2.7.24  AUTOLSROFF

2.7.25  AUTORESET

Clear the AUTORESET Alarm

2.7.26  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.7.27  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.7.28  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Condition

2.7.29  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.7.30  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.7.31  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.7.32  AUTOSW-UNEQ

Clear the AUTOSW-UNEQ Condition

2.7.33  BAT-FAIL

Clear the BAT-FAIL Alarm

2.7.34  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.35  BLSROSYNC

Clear the BLSROSYNC Alarm

2.7.36  BLSR-SW-VER-MISM

2.7.37  CARLOSS (E100T)

2.7.38  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.39  CARLOSS (G1000)

Clear the CARLOSS (G1000) Alarm

2.7.40  CLDRESTART

Clear the CLDRESTART Condition

2.7.41  COMIOXC

Clear the COMIOXC Alarm

2.7.42  COMM-FAIL

2.7.43  CONTBUS-A-18

Clear the CONTBUS-A-18 Alarm

2.7.44  CONTBUS-B-18

Clear the CONTBUS-B-18 Alarm

2.7.45  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.7.46  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.47  CONTBUS-IO-B

Clear the CONTBUS-IO-B Alarm

2.7.48  CTNEQPT-MISMATCH

2.7.49  CTNEQPT-PBPROT

Clear the CTNEQPT-PBPROT Alarm

2.7.50  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.51  DATAFLT

Clear the DATAFLT Alarm

2.7.52  DBOSYNC

Clear the DBOSYNC Alarm

2.7.53  DISCONNECTED

Clear the DISCONNECTED Alarm

2.7.54  DS3-MISM

Clear the DS3-MISM Condition

2.7.55  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.56  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.57  DUP-SHELF-ID

2.7.58  EHIBATVG

Clear the EHIBATVG Alarm

2.7.59  ELWBATVG

Clear the ELWBATVG Alarm

2.7.60  ENCAP-MISMATCH-P

2.7.61   EOC

Clear the EOC Alarm

2.7.62  EOC-L

Clear the EOC-L Alarm

2.7.63  EQPT

Clear the EQPT Alarm

2.7.64  EQPT-DIAG

Clear the EQPT-DIAG Alarm

2.7.65  EQPT-MISS

Clear the EQPT-MISS Alarm

2.7.66  ERFI-P-CONN

2.7.67  ERFI-P-PAYLD

2.7.68  ERFI-P-SRVR

2.7.69  ERROR-CONFIG

2.7.70  E-W-MISMATCH

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

Clear the E-W-MISMATCH Alarm in CTC

2.7.71  EXCCOL

Clear the EXCCOL Alarm

2.7.72  EXERCISE-RING-FAIL

Clear the EXERCISE-RING-FAIL Condition

2.7.73  EXT

Clear the EXT Alarm

2.7.74  EXTRA-TRAF-PREEMPT

Clear the EXTRA-TRAF-PREEMPT Alarm

2.7.75  FAILTOSW

Clear the FAILTOSW Condition

2.7.76  FAILTOSW-PATH

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration

2.7.77  FAILTOSWR

Clear the FAILTOSWR Condition in a BLSR Configuration

2.7.78  FAN

Clear the FAN Alarm

2.7.79  FANDEGRADE

Clear the FANDEGRADE Alarm

2.7.80  FE-AIS

Clear the FE-AIS Condition

2.7.81  FE-DS1-MULTLOS

Clear the FE-DS1-MULTLOS Condition

2.7.82  FE-DS1-NSA

Clear the FE-DS1-NSA Condition

2.7.83  FE-DS1-SA

Clear the FE-DS1-SA Condition

2.7.84  FE-DS1-SNGLLOS

Clear the FE-DS1-SNGLLOS Condition

2.7.85  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.7.86  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.7.87  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.88  FE-FRCDWKSWBK-SPAN

Clear the FE-FRCDWKSWBK-SPAN Condition

2.7.89  FE-FRCDWKSWPR-RING

Clear the FE-FRCDWKSWPR-RING Condition

2.7.90  FE-FRCDWKSWPR-SPAN

Clear the FE-FRCDWKSWPR-SPAN Condition

2.7.91  FE-IDLE

Clear the FE-IDLE Condition

2.7.92  FE-LOCKOUTOFPR-SPAN

Clear the FE-LOCKOUTOFPR-SPAN Condition

2.7.93  FE-LOF

Clear the FE-LOF Condition

2.7.94  FE-LOS

Clear the FE-LOS Condition

2.7.95  FE-MANWKSWBK-SPAN

Clear the FE-MANWKSWBK-SPAN Condition

2.7.96  FE-MANWKSWPR-RING

Clear the FE-MANWKSWPR-RING Condition

2.7.97  FE-MANWKSWPR-SPAN

Clear the FE-MANWKSWPR-SPAN Condition

2.7.98  FEPRLF

Clear the FEPRLF Alarm on a BLSR

2.7.99  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.100  FORCED-REQ-RING

Clear the FORCED-REQ-RING Condition

2.7.101  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.102  FRCDSWTOINT

2.7.103  FRCDSWTOPRI

2.7.104  FRCDSWTOSEC

2.7.105  FRCDSWTOTHIRD

2.7.106  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.107  FSTSYNC

2.7.108  FULLPASSTHR-BI

Clear the FULLPASSTHR-BI Condition

2.7.109  HELLO

Clear the HELLO Alarm

2.7.110  HIBATVG

Clear the HIBATVG Alarm

2.7.111  HI-LASERBIAS

2.7.112  HI-LASERTEMP

2.7.113  HI-RXPOWER

2.7.114  HITEMP

Clear the HITEMP Alarm

2.7.115  HI-TXPOWER

2.7.116  HLDOVRSYNC

Clear the HLDOVRSYNC Condition

2.7.117  I-HITEMP

Clear the I-HITEMP Alarm

2.7.118  IMPROPRMVL

Clear the IMPROPRMVL (EQPT) Alarm

2.7.119  INC-ISD

2.7.120  INCOMPATIBLE-SEND-PDIP

Clear the INCOMPATIBLE-SEND-PDIP Alarm

2.7.121  INCOMPATIBLE-SW

Clear the INCOMPATIBLE-SW Alarm

2.7.122  INHSWPR

Clear the INHSWPR Condition

2.7.123  INHSWWKG

Clear the INHSWWKG Condition

2.7.124  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.125  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.7.126  KB-PASSTHR

Clear the KB-PASSTHR Condition

2.7.127  KBYTE-APS-CHANNEL-FAILURE

2.7.128  LAN-POL-REV

2.7.129  LASEREOL

2.7.130  LCAS-CRC

2.7.131  LCAS-RX-FAIL

2.7.132  LCAS-TX-ADD

2.7.133  LCAS-TX-DNU

2.7.134  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.135  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.136  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.137  LOF (DS1)

Clear the LOF (DS1) Alarm

2.7.138  LOF (DS3)

Clear the LOF (DS3) Alarm

2.7.139  LOF (OCN)

Clear the LOF (OCN) Alarm

2.7.140  LOF (STSTRM)

Clear the LOF (STSTRM) Alarm

2.7.141  LOGBUFR90

2.7.142  LOGBUFROVFL

Clear the LOGBUFROVFL Alarm

2.7.143  LO-LASERBIAS

2.7.144  LO-LASERTEMP

2.7.145  LOM

Clear the LOM Alarm

2.7.146  LOP-P

Clear the LOP-P Alarm

2.7.147  LOP-V

Clear the LOP-V Alarm

2.7.148  LO-RXPOWER

2.7.149  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.150  LOS (DS1)

Clear the LOS (DS1) Alarm

2.7.151  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.152  LOS (OCN)

Clear the LOS (OCN) Alarm

2.7.153  LO-TXPOWER

2.7.154  LPBKCRS

Clear the LPBKCRS Condition

2.7.155  LPBKDS1FEAC-CMD

2.7.156  LPBKDS3FEAC

2.7.157  LPBKDS3FEAC-CMD

2.7.158  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.159  LPBKFACILITY (G1000)

Clear the LPBKFACILITY (G1000) Condition

2.7.160  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.7.161  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.7.162  LPBKTERMINAL (G1000)

Clear the LPBKTERMINAL (G1000) Condition

2.7.163  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.7.164  LWBATVG

Clear the LWBATVG Alarm

2.7.165  MAN-REQ

Clear the MAN-REQ Condition

2.7.166  MANRESET

2.7.167  MANSWTOINT

2.7.168  MANSWTOPRI

2.7.169  MANSWTOSEC

2.7.170  MANSWTOTHIRD

2.7.171  MANUAL-REQ-RING

Clear the MANUAL-REQ-RING Condition

2.7.172  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.173  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.174  MEA (FAN)

Clear the MEA (FAN) Alarm

2.7.175  MEM-GONE

2.7.176  MEM-LOW

2.7.177  MFGMEM

Clear the MFGMEM Alarm

2.7.178  NOT-AUTHENTICATED

2.7.179  OOU-TPT

Clear the OOT-TPT Condition

2.7.180  OPTNTWMIS

2.7.181  PDI-P

Clear the PDI-P Condition

2.7.182  PEER-NORESPONSE

Clear the PEER-NORESPONSE Alarm

2.7.183  PLM-P

Clear the PLM-P Alarm

2.7.184  PLM-V

Clear the PLM-V Alarm

2.7.185  PRC-DUPID

Clear the PRC-DUPID Alarm

2.7.186  PROTNA

Clear the PROTNA Alarm

2.7.187  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.188  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.189  PWR-FAIL-RET-A

Clear the PWR-FAIL-RET-A Alarm

2.7.190  PWR-FAIL-RET-B

Clear the PWR-FAIL-RET-B Alarm

2.7.191  RAI

Clear the RAI Condition

2.7.192  RFI-L

Clear the RFI-L Condition

2.7.193  RFI-P

Clear the RFI-P Condition

2.7.194  RFI-V

Clear the RFI-V Condition

2.7.195  RING-ID-MIS

2.7.196  RING-MISMATCH

Clear the RING-MISMATCH Alarm

2.7.197  RING-SW-EAST

2.7.198  RING-SW-WEST

2.7.199  ROLL

2.7.200  ROLL-PEND

2.7.201  RUNCFG-SAVENEED

2.7.202  SD (DS1, DS3)

Clear the SD (DS1, DS3) Condition

2.7.203  SD-L

Clear the SD-L Condition

2.7.204  SD-P

Clear the SD-P Condition

2.7.205  SD-V

Clear the SD-V Condition

2.7.206  SF (DS1, DS3)

Clear the SF (DS1, DS3) Condition

2.7.207  SF-L

Clear the SF-L Condition

2.7.208  SF-P

Clear the SF-P Condition

2.7.209  SFTWDOWN

2.7.210  SF-V

Clear the SF-V Condition

2.7.211  SHELF-COMM-FAIL

2.7.212  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.213  SQUELCH

Clear the SQUELCH Condition

2.7.214  SQUELCHED

2.7.215  SQM

Clear the SQM Alarm

2.7.216  SSM-DUS

2.7.217  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.218  SSM-LNC

2.7.219  SSM-OFF

Clear the SSM-OFF Condition

2.7.220  SSM-PRC

2.7.221  SSM-PRS

2.7.222  SSM-RES

2.7.223  SSM-SDH-TN

2.7.224  SSM-SETS

2.7.225  SSM-SMC

2.7.226  SSM-ST2

2.7.227  SSM-ST3

2.7.228  SSM-ST3E

2.7.229  SSM-ST4

2.7.230  SSM-STU

Clear the SSM-STU Condition

2.7.231  SSM-TNC

2.7.232  STS-SQUELCH-L

2.7.233  SW-MISMATCH

Clear the SW-MISMATCH Condition

2.7.234  SWMTXMOD-PROT

Clear the SWMTXMOD-PROT Alarm

2.7.235  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.7.236  SWTOPRI

2.7.237  SWTOSEC

Clear the SWTOSEC Condition

2.7.238  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.7.239  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.240  SYNCPRI

Clear the SYNCPRI Alarm

2.7.241  SYNCSEC

Clear the SYNCSEC Alarm

2.7.242  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.243  SYSBOOT

2.7.244  TIM

Clear the TIM Alarm

2.7.245  TIM-MON

2.7.246  TIM-P

Clear the TIM-P Alarm

2.7.247  TIM-S

2.7.248  TIM-V

Clear the TIM-V Alarm

2.7.249  TPTFAIL (G1000)

Clear the TPTFAIL (G1000) Alarm

2.7.250  TRMT

Clear the TRMT Alarm

2.7.251  TRMT-MISS

Clear the TRMT-MISS Alarm

2.7.252  TX-AIS

Clear the TX-AIS Condition

2.7.253  TX-LOF

Clear the TX-LOF Condition

2.7.254  TX-RAI

Clear the TX-RAI Condition

2.7.255  UNEQ-P

Clear the UNEQ-P Alarm

2.7.256  UNEQ-V

Clear the UNEQ-V Alarm

2.7.257  VT-SQUELCH-L

2.7.258  WKSWPR

Clear the WKSWPR Condition

2.7.259  WTR

2.8  XTC Card Line Alarms

2.9  ONS 15327 Traffic Card LED Activity

2.9.1  Typical ONS 15327 Traffic Card LED Activity After Insertion

2.9.2  Typical ONS 15327 Traffic Card LED Activity During Reset

2.9.3  Typical ONS 15327 Cross-Connect LED Activity During Side Switch

2.10  Frequently Used Alarm Troubleshooting Procedures

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

Identify an ONS 15327 BLSR Ring Name or Node ID Number

Change an ONS 15327 BLSR Ring Name

Change an ONS 15327 BLSR Node ID Number

Verify ONS 15327 Node Visibility for Other Nodes

2.10.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

Initiate a 1+1 Protection Port Manual Switch Command

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

Initiate a Card or Port Lock-On Command

Initiate a Card or Port Lockout Command

Clear a Card or Port Lock-On or Lockout Command

Initiate a 1:1 Card Switch Command

Initiate a Force Switch for All Circuits on a Path Protection Span

Initiate a Manual Switch for All Circuits on a Path Protection Span

Initiate a Lock-Out-of-Protect Switch for All Circuits on a Path Protection Span

Clear a Path Protection Span External Switching Command

Initiate a Force Ring Switch on a BLSR

Initiate a Manual Ring Switch on a BLSR

Initiate a Lockout on a BLSR Protect Span

Initiate an Exercise Ring Switch on a BLSR

Clear a BLSR External Switching Command

2.10.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Reset an Active XTC Card and Activate the Standby Card

Side Switch the Active and Standby XTC Cards

2.10.4  Physical Card Reseating, Resetting, and Replacement

Remove and Reinsert (Reseat) the Standby XTC Card

Remove and Reinsert (Reseat) a Card

Physically Replace a Card

2.10.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node SDCC Terminations

Clear an OC-N Card Facility or Terminal Loopback Circuit

Clear an OC-N Card XC Loopback Circuit

Clear an XTC Card DS-1 or DS-3 Loopback Circuit

Clear a G1000 Card Loopback

Clear a CE_100T-8 Ethernet Card Loopback Circuit

2.10.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

Remove and Reinsert a Fan-Tray Assembly

Replace the Fan-Tray Assembly

2.10.7  Chassis Replacement Procedure

Alarm Troubleshooting

Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.

This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15327 alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15327 alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all ONS 15327 alarm logical objects, which are the basis of the alarm profile list in Table 2-8. For a comprehensive list of all conditions, refer to the Cisco ONS SONET TL1 Command Guide.

An alarm's troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and Transaction Language One (TL1) version of that alarm. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.1  Alarm Index by Default Severity

The following tables group alarms and conditions by their default severities in the ONS 15327 system. These severities are the same whether they are reported in the CTC Alarms window severity (SEV) column or in TL1.

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

Note The CTC default alarm profile in some cases contains two severities for one alarm (for example, MJ/MN). The ONS 15327 platform default severity comes first (in this example, MJ), but the alarm can be demoted to the second severity in the presence of a higher-ranking alarm. This is in accordance with Telcordia GR-474-CORE.

2.1.1  Critical Alarms (CR)

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

Table 2-1 ONS 15327 Critical Alarm List

AUTOLSROFF (OCN)

IMPROPRMVL (EQPT)

MFGMEM (FAN)

BKUPMEMP (EQPT)

LOF (DS3)

PLM-P (STSMON)

COMIOXC (EQPT)

LOF (OCN)

PLM-P (STSTRM)

CONTBUS-DISABLED (EQPT)

LOF (STSTRM)

SQM (STSTRM)

CTNEQPT-PBPROT (EQPT)

LOM (STSMON)

SWMTXMOD-PROT (EQPT)

CTNEQPT-PBWORK (EQPT)

LOP-P (STSMON)

SWMTXMOD-WORK (EQPT)

ENCAP-MISMATCH-P (STSTRM)

LOP-P (STSTRM)

TIM (OCN)

EQPT (EQPT)

LOS (DS3)

TIM-P (STSTRM)

EQPT-MISS (FAN)

LOS (OCN)

TIM-S (OCN)

FAN (FAN)

MEA (EQPT)

UNEQ-P (STSMON)

HITEMP (NE)

MEA (FAN)

UNEQ-P (STSTRM)

I-HITEMP (NE)

MFGMEM (BPLANE)

—

2.1.2  Major Alarms (MJ)

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

Table 2-2 ONS 15327 Major Alarm List

APSCM (OCN)

FANDEGRADE (FAN)

PRC-DUPID (OCN)

APSCNMIS (OCN)

HIBATVG (PWR)

RING-ID-MIS (OCN)

BAT-FAIL (PWR)

LOF (DS1)

RING-MISMATCH (OCN)

BLSROSYNC (OCN)

LOM (STSTRM)

SQM (VT-TERM)

BLSR-SW-VER-MISM (OCN)

LOM (VT-TERM)

SYNCPRI (NE-SREF)

CARLOSS (E100T)

LOP-V (VT-MON)

SYSBOOT (NE)

CARLOSS (EQPT)

LOP-V (VT-TERM)

TIM-V (VT-TERM)

CARLOSS (G1000)

LOS (DS1)

TPTFAIL (G1000)

DBOSYNC (NE)

LWBATVG (PWR)

TRMT (DS1)

EHIBATVG (PWR)

MEM-GONE (EQPT)

TRMT-MISS (DS1)

ELWBATVG (PWR)

OPTNTWMIS (NE)

UNEQ-V (VT-MON)

E-W-MISMATCH (OCN)

PEER-NORESPONSE (EQPT)

UNEQ-V (VT-TERM)

EXTRA-TRAF-PREEMPT (OCN)

PLM-V (VT-TERM)

—

2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15327 Minor Alarm List

APSB (OCN)

ERROR-CONFIG (EQPT)

LOS (BITS)

APSCDFLTK (OCN)

EXCCOL (EQPT)

LO-TXPOWER (OCN)

APSC-IMP (OCN)

EXT (ENVALRM)

MEM-LOW (EQPT)

APSCINCON (OCN)

FEPRLF (OCN)

NOT-AUTHENTICATED (SYSTEM)

APSIMP (OCN)

HELLO (OCN)

PROTNA (EQPT)

APS-INV-PRIM (OCN)

HI-LASERBIAS (OCN)

PWR-FAIL-A (EQPT)

APSMM (OCN)

HI-LASERTEMP (OCN)

PWR-FAIL-B (EQPT)

APS-PRIM-SEC-MISM (OCN)

HI-RXPOWER (OCN)

PWR-FAIL-RET-A (EQPT)

AUTORESET (EQPT)

HITEMP (EQPT)

PWR-FAIL-RET-B (EQPT)

AUTOSW-UNEQ (VT-MON)

HI-TXPOWER (OCN)

SFTWDOWN (EQPT)

COMM-FAIL (EQPT)

INCOMPATIBLE-SEND-PDIP (SYSTEM)

SNTP-HOST (NE)

CONTBUS-A-18 (EQPT)

INCOMPATIBLE-SW (SYSTEM)

SSM-FAIL (BITS)

CONTBUS-B-18 (EQPT)

ISIS-ADJ-FAIL (OCN)

SSM-FAIL (OCN)

CONTBUS-IO-A (EQPT)

KBYTE-APS-CHANNEL-FAILURE (OCN)

SYNCPRI (EXT-SREF)

CONTBUS-IO-B (EQPT)

LASEREOL (OCN)

SYNCSEC (EXT-SREF)

DATAFLT (NE)

LOF (BITS)

SYNCSEC (NE-SREF)

DISCONNECTED (SYSTEM)

LOGBUFR90 (SYSTEM)

SYNCTHIRD (EXT-SREF)

DUP-IPADDR (NE)

LOGBUFROVFL (SYSTEM)

SYNCTHIRD (NE-SREF)

DUP-NODENAME (NE)

LO-LASERBIAS (OCN)

TIM-MON (OCN)

EOC (OCN)

LO-LASERTEMP (OCN)

TIM-P (STSMON)

EOC-L (OCN)

LO-RXPOWER (OCN)

—

2.1.4  Not Alarmed Conditions

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

Table 2-4 ONS 15327 NA Conditions List

ALS (OCN)

FRCDSWTOTHIRD (EXT-SREF)

SD-P (STSMON)

APC-DISABLED (NE)

FRCDSWTOTHIRD (NE-SREF)

SD-P (STSTRM)

APC-END (NE)

FRNGSYNC (NE-SREF)

SD-V (VT-MON)

APS-PRIM-FAC (OCN)

FSTSYNC (NE-SREF)

SD-V (VT-TERM)

AS-CMD (BPLANE)

INC-ISD (DS3)

SF (DS1)

AS-CMD (DS1)

INHSWPR (EQPT)

SF (DS3)

AS-CMD (DS3)

INHSWWKG (EQPT)

SF-L (OCN)

AS-CMD (E100T)

INTRUSION-PSWD (NE)

SF-P (STSMON)

AS-CMD (EQPT)

KB-PASSTHR (OCN)

SF-P (STSTRM)

AS-CMD (G1000)

LAN-POL-REV (NE)

SF-V (VT-MON)

AS-CMD (NE)

LCAS-CRC (STSTRM)

SF-V (VT-TERM)

AS-CMD (OCN)

LCAS-CRC (VT-TERM)

SQUELCH (OCN)

AS-CMD (SHELF)

LCAS-RX-FAIL (STSTRM)

SQUELCHED (OCN)

AS-MT (DS1)

LCAS-RX-FAIL (VT-TERM)

SSM-DUS (BITS)

AS-MT (DS3)

LCAS-TX-ADD (STSTRM)

SSM-DUS (OCN)

AS-MT (EQPT)

LCAS-TX-ADD (VT-TERM)

SSM-OFF (BITS)

AS-MT (G1000)

LCAS-TX-DNU (STSTRM)

SSM-OFF (OCN)

AS-MT (OCN)

LCAS-TX-DNU (VT-TERM)

SSM-PRS (BITS)

AS-MT (SHELF)

LKOUTPR-S (OCN)

SSM-PRS (NE-SREF)

AS-MT-OOG (STSTRM)

LOCKOUT-REQ (EQPT)

SSM-PRS (OCN)

AS-MT-OOG (VT-TERM)

LOCKOUT-REQ (OCN)

SSM-RES (BITS)

AUD-LOG-LOSS (NE)

LOCKOUT-REQ (STSMON)

SSM-RES (NE-SREF)

AUD-LOG-LOW (NE)

LOCKOUT-REQ (VT-MON)

SSM-RES (OCN)

AUTOSW-LOP (STSMON)

LPBKCRS (STSMON)

SSM-SMC (BITS)

AUTOSW-LOP (VT-MON)

LPBKCRS (STSTRM)

SSM-SMC (NE-SREF)

AUTOSW-PDI (STSMON)

LPBKDS1FEAC-CMD (DS1)

SSM-SMC (OCN)

AUTOSW-SDBER (STSMON)

LPBKDS3FEAC (DS3)

SSM-ST2 (BITS)

AUTOSW-SFBER (STSMON)

LPBKDS3FEAC-CMD (DS3)

SSM-ST2 (NE-SREF)

AUTOSW-UNEQ (STSMON)

LPBKFACILITY (DS1)

SSM-ST2 (OCN)

CLDRESTART (EQPT)

LPBKFACILITY (DS3)

SSM-ST3 (BITS)

CTNEQPT-MISMATCH (EQPT)

LPBKFACILITY (G1000)

SSM-ST3 (NE-SREF)

DS3-MISM (DS3)

LPBKFACILITY (OCN)

SSM-ST3 (OCN)

EXERCISE-RING-FAIL (OCN)

LPBKTERMINAL (DS1)

SSM-ST3E (BITS)

FAIL (EQPT)TOSW

LPBKTERMINAL (DS3)

SSM-ST3E (NE-SREF)

FAILTOSW (OCN)

LPBKTERMINAL (G1000)

SSM-ST3E (OCN)

FAILTOSW-PATH (STSMON)

LPBKTERMINAL (OCN)

SSM-ST4 (BITS)

FAILTOSW-PATH (VT-MON)

MAN-REQ (EQPT)

SSM-ST4 (NE-SREF)

FAILTOSWR (OCN)

MAN-REQ (STSMON)

SSM-ST4 (OCN)

FE-AIS (DS3)

MAN-REQ (VT-MON)

SSM-STU (BITS)

FE-DS1-MULTLOS (DS3)

MANSWTOINT (NE-SREF)

SSM-STU (NE-SREF)

FE-DS1-NSA (DS3)

MANSWTOPRI (EXT-SREF)

SSM-STU (OCN)

FE-DS1-SA (DS3)

MANSWTOPRI (NE-SREF)

SSM-TNC (BITS)

FE-DS1-SNGLLOS (DS3)

MANSWTOSEC (EXT-SREF)

SSM-TNC (NE-SREF)

FE-DS3-NSA (DS3)

MANSWTOSEC (NE-SREF)

SSM-TNC (OCN)

FE-DS3-SA (DS3)

MANSWTOTHIRD (EXT-SREF)

STS-SQUELCH-L (OCN)

FE-EQPT-NSA (DS3)

MANSWTOTHIRD (NE-SREF)

SW-MISMATCH (EQPT)

FE-FRCDWKSWBK-SPAN (OCN)

MANUAL-REQ-RING (OCN)

SWTOPRI (EXT-SREF)

FE-FRCDWKSWPR-RING (OCN)

MANUAL-REQ-SPAN (OCN)

SWTOPRI (NE-SREF)

FE-FRCDWKSWPR-SPAN (OCN)

OOU-TPT (STSTRM)

SWTOSEC (EXT-SREF)

FE-IDLE (DS3)

OOU-TPT (VT-TERM)

SWTOSEC (NE-SREF)

FE-LOCKOUTOFPR-SPAN (OCN)

PDI-P (STSMON)

SWTOTHIRD (EXT-SREF)

FE-LOF (DS3)

PDI-P (STSTRM)

SWTOTHIRD (NE-SREF)

FE-LOS (DS3)

RAI (DS1)

SYNC-FREQ (BITS)

FE-MANWKSWBK-SPAN (OCN)

RAI (DS3)

SYNC-FREQ (OCN)

FE-MANWKSWPR-RING (OCN)

RFI-V (VT-MON)

TX-RAI (DS1)

FE-MANWKSWPR-SPAN (OCN)

RING-SW-EAST (OCN)

TX-RAI (DS3)

FORCED-REQ (EQPT)

RING-SW-WEST (OCN)

VT-SQUELCH-L (OCN)

FORCED-REQ (STSMON)

ROLL (STSMON)

WKSWPR (EQPT)

FORCED-REQ (VT-MON)

ROLL (STSTRM)

WKSWPR (OCN)

FORCED-REQ-RING (OCN)

ROLL (VT-MON)

WKSWPR (STSMON)

FORCED-REQ-SPAN (OCN)

ROLL-PEND (STSMON)

WKSWPR (VT-MON)

FRCDSWTOINT (NE-SREF)

ROLL-PEND (VT-MON)

WTR (EQPT)

FRCDSWTOPRI (EXT-SREF)

RUNCFG-SAVENEED (EQPT)

WTR (OCN)

FRCDSWTOPRI (NE-SREF)

SD (DS1)

WTR (STSMON)

FRCDSWTOSEC (EXT-SREF)

SD (DS3)

WTR (VT-MON)

FRCDSWTOSEC (NE-SREF)

SD-L (OCN)

—

2.1.5  Not Reported Conditions

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

Table 2-5 ONS 15327 NR Conditions List

AIS (BITS)

AUTOSW-AIS (STSMON)

RFI-L (OCN)

AIS (DS1)

AUTOSW-AIS (VT-MON)

RFI-P (STSMON)

AIS (DS3)

ERFI-P-CONN (STSMON)

RFI-P (STSTRM)

AIS-L (OCN)

ERFI-P-CONN (STSTRM)

RFI-V (VT-TERM)

AIS-P (STSMON)

ERFI-P-PAYLD (STSMON)

ROLL-PEND (STSTRM)

AIS-P (STSTRM)

ERFI-P-PAYLD (STSTRM)

TX-AIS (DS1)

AIS-V (VT-MON)

ERFI-P-SRVR (STSMON)

TX-AIS (DS3)

AIS-V (VT-TERM)

ERFI-P-SRVR (STSTRM)

TX-LOF (DS1)

AIS-V (VT-TERM)

—

—

2.2  Alarms and Conditions Listed By Alphabetical Entry

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

Table 2-6 ONS 15327 Alarm and Condition Alphabetical List

AIS (BITS)

FEPRLF (OCN)

PWR-FAIL-RET-A (EQPT)

AIS (DS1)

FORCED-REQ (EQPT)

PWR-FAIL-RET-B (EQPT)

AIS (DS3)

FORCED-REQ (STSMON)

RAI (DS1)

AIS-L (OCN)

FORCED-REQ (VT-MON)

RAI (DS3)

AIS-P (STSMON)

FORCED-REQ-RING (OCN)

RFI-L (OCN)

AIS-P (STSTRM)

FORCED-REQ-SPAN (OCN)

RFI-P (STSMON)

AIS-V (VT-MON)

FRCDSWTOINT (NE-SREF)

RFI-P (STSTRM)

AIS-V (VT-TERM)

FRCDSWTOPRI (EXT-SREF)

RFI-V (VT-MON)

ALS (OCN)

FRCDSWTOPRI (NE-SREF)

RFI-V (VT-TERM)

APC-DISABLED (NE)

FRCDSWTOSEC (EXT-SREF)

RING-ID-MIS (OCN)

APC-END (NE)

FRCDSWTOSEC (NE-SREF)

RING-MISMATCH (OCN)

APSB (OCN)

FRCDSWTOTHIRD (EXT-SREF)

RING-SW-EAST (OCN)

APSCDFLTK (OCN)

FRCDSWTOTHIRD (NE-SREF)

RING-SW-WEST (OCN)

APSC-IMP (OCN)

FRNGSYNC (NE-SREF)

ROLL (STSMON)

APSCINCON (OCN)

FSTSYNC (NE-SREF)

ROLL (STSTRM)

APSCM (OCN)

FULLPASSTHR-BI (OCN)

ROLL (VT-MON)

APSCNMIS (OCN)

HELLO (OCN)

ROLL-PEND (STSMON)

APSIMP (OCN)

HIBATVG (PWR)

ROLL-PEND (STSTRM)

APS-INV-PRIM (OCN)

HI-LASERBIAS (OCN)

ROLL-PEND (VT-MON)

APSMM (OCN)

HI-LASERTEMP (OCN)

RUNCFG-SAVENEED (EQPT)

APS-PRIM-FAC (OCN)

HI-RXPOWER (OCN)

SD (DS1)

APS-PRIM-SEC-MISM (OCN)

HITEMP (EQPT)

SD (DS3)

AS-CMD (BPLANE)

HITEMP (NE)

SD-L (OCN)

AS-CMD (DS1)

HI-TXPOWER (OCN)

SD-P (STSMON)

AS-CMD (DS3)

HLDOVRSYNC (NE-SREF)

SD-P (STSTRM)

AS-CMD (E100T)

I-HITEMP (NE)

SD-V (VT-MON)

AS-CMD (EQPT)

IMPROPRMVL (EQPT)

SD-V (VT-TERM)

AS-CMD (G1000)

INC-ISD (DS3)

SF (DS1)

AS-CMD (NE)

INCOMPATIBLE-SEND-PDIP (SYSTEM)

SF (DS3)

AS-CMD (OCN)

INCOMPATIBLE-SW (SYSTEM)

SF-L (OCN)

AS-CMD (SHELF)

INHSWPR (EQPT)

SF-P (STSMON)

AS-MT (DS1)

INHSWWKG (EQPT)

SF-P (STSTRM)

AS-MT (DS3)

INTRUSION-PSWD (NE)

SFTWDOWN (EQPT)

AS-MT (EQPT)

ISIS-ADJ-FAIL (OCN)

SF-V (VT-MON)

AS-MT (G1000)

KB-PASSTHR (OCN)

SF-V (VT-TERM)

AS-MT (OCN)

KBYTE-APS-CHANNEL-FAILURE (OCN)

SNTP-HOST (NE)

AS-MT (SHELF)

LAN-POL-REV (NE)

SQM (STSTRM)

AS-MT-OOG (STSTRM)

LASEREOL (OCN)

SQM (VT-TERM)

AS-MT-OOG (VT-TERM)

LCAS-CRC (STSTRM)

SQUELCH (OCN)

AUD-LOG-LOSS (NE)

LCAS-CRC (VT-TERM)

SQUELCHED (OCN)

AUD-LOG-LOW (NE)

LCAS-RX-FAIL (STSTRM)

SSM-DUS (BITS)

AUTOLSROFF (OCN)

LCAS-RX-FAIL (VT-TERM)

SSM-DUS (OCN)

AUTORESET (EQPT)

LCAS-TX-ADD (STSTRM)

SSM-FAIL (BITS)

AUTOSW-AIS (STSMON)

LCAS-TX-ADD (VT-TERM)

SSM-FAIL (OCN)

AUTOSW-AIS (VT-MON)

LCAS-TX-DNU (STSTRM)

SSM-OFF (BITS)

AUTOSW-LOP (STSMON)

LCAS-TX-DNU (VT-TERM)

SSM-OFF (OCN)

AUTOSW-LOP (VT-MON)

LKOUTPR-S (OCN)

SSM-PRS (BITS)

AUTOSW-PDI (STSMON)

LOCKOUT-REQ (EQPT)

SSM-PRS (NE-SREF)

AUTOSW-SDBER (STSMON)

LOCKOUT-REQ (OCN)

SSM-PRS (OCN)

AUTOSW-SFBER (STSMON)

LOCKOUT-REQ (STSMON)

SSM-RES (BITS)

AUTOSW-UNEQ (STSMON)

LOCKOUT-REQ (VT-MON)

SSM-RES (NE-SREF)

AUTOSW-UNEQ (VT-MON)

LOF (BITS)

SSM-RES (OCN)

BAT-FAIL (PWR)

LOF (DS1)

SSM-SMC (BITS)

BKUPMEMP (EQPT)

LOF (DS3)

SSM-SMC (NE-SREF)

BLSROSYNC (OCN)

LOF (OCN)

SSM-SMC (OCN)

BLSR-SW-VER-MISM (OCN)

LOF (STSTRM)

SSM-ST2 (BITS)

CARLOSS (E100T)

LOGBUFR90 (SYSTEM)

SSM-ST2 (NE-SREF)

CARLOSS (EQPT)

LOGBUFROVFL (SYSTEM)

SSM-ST2 (OCN)

CARLOSS (G1000)

LO-LASERBIAS (OCN)

SSM-ST3 (BITS)

CLDRESTART (EQPT)

LO-LASERTEMP (OCN)

SSM-ST3 (NE-SREF)

COMIOXC (EQPT)

LOM (STSMON)

SSM-ST3 (OCN)

COMM-FAIL (EQPT)

LOM (STSTRM)

SSM-ST3E (BITS)

CONTBUS-A-18 (EQPT)

LOM (VT-TERM)

SSM-ST3E (NE-SREF)

CONTBUS-B-18 (EQPT)

LOP-P (STSMON)

SSM-ST3E (OCN)

CONTBUS-DISABLED (EQPT)

LOP-P (STSTRM)

SSM-ST4 (BITS)

CONTBUS-IO-A (EQPT)

LOP-V (VT-MON)

SSM-ST4 (NE-SREF)

CONTBUS-IO-B (EQPT)

LOP-V (VT-TERM)

SSM-ST4 (OCN)

CTNEQPT-MISMATCH (EQPT)

LO-RXPOWER (OCN)

SSM-STU (BITS)

CTNEQPT-PBPROT (EQPT)

LOS (BITS)

SSM-STU (NE-SREF)

CTNEQPT-PBWORK (EQPT)

LOS (DS1)

SSM-STU (OCN)

DATAFLT (NE)

LOS (DS3)

SSM-TNC (BITS)

DBOSYNC (NE)

LOS (OCN)

SSM-TNC (NE-SREF)

DISCONNECTED (SYSTEM)

LO-TXPOWER (OCN)

SSM-TNC (OCN)

DS3-MISM (DS3)

LPBKCRS (STSMON)

STS-SQUELCH-L (OCN)

DUP-IPADDR (NE)

LPBKCRS (STSTRM)

SW-MISMATCH (EQPT)

DUP-NODENAME (NE)

LPBKDS1FEAC-CMD (DS1)

SWMTXMOD-PROT (EQPT)

EHIBATVG (PWR)

LPBKDS3FEAC (DS3)

SWMTXMOD-WORK (EQPT)

ELWBATVG (PWR)

LPBKDS3FEAC-CMD (DS3)

SWTOPRI (EXT-SREF)

ENCAP-MISMATCH-P (STSTRM)

LPBKFACILITY (DS1)

SWTOPRI (NE-SREF)

EOC (OCN)

LPBKFACILITY (DS3)

SWTOSEC (EXT-SREF)

EOC-L (OCN)

LPBKFACILITY (G1000)

SWTOSEC (NE-SREF)

EQPT (EQPT)

LPBKFACILITY (OCN)

SWTOTHIRD (EXT-SREF)

EQPT-MISS (FAN)

LPBKTERMINAL (DS1)

SWTOTHIRD (NE-SREF)

ERFI-P-CONN (STSMON)

LPBKTERMINAL (DS3)

SYNC-FREQ (BITS)

ERFI-P-CONN (STSTRM)

LPBKTERMINAL (G1000)

SYNC-FREQ (OCN)

ERFI-P-PAYLD (STSMON)

LPBKTERMINAL (OCN)

SYNCPRI (EXT-SREF)

ERFI-P-PAYLD (STSTRM)

LWBATVG (PWR)

SYNCPRI (NE-SREF)

ERFI-P-SRVR (STSMON)

MAN-REQ (EQPT)

SYNCSEC (EXT-SREF)

ERFI-P-SRVR (STSTRM)

MAN-REQ (STSMON)

SYNCSEC (NE-SREF)

ERROR-CONFIG (EQPT)

MAN-REQ (VT-MON)

SYNCTHIRD (EXT-SREF)

E-W-MISMATCH (OCN)

MANRESET (EQPT)

SYNCTHIRD (NE-SREF)

EXCCOL (EQPT)

MANSWTOINT (NE-SREF)

SYSBOOT (NE)

EXERCISE-RING-FAIL (OCN)

MANSWTOPRI (EXT-SREF)

TIM (OCN)

EXT (ENVALRM)

MANSWTOPRI (NE-SREF)

TIM-MON (OCN)

EXTRA-TRAF-PREEMPT (OCN)

MANSWTOSEC (EXT-SREF)

TIM-P (STSMON)

FAIL (EQPT)TOSW

MANSWTOSEC (NE-SREF)

TIM-P (STSTRM)

FAILTOSW (OCN)

MANSWTOTHIRD (EXT-SREF)

TIM-S (OCN)

FAILTOSW-PATH (STSMON)

MANSWTOTHIRD (NE-SREF)

TIM-V (VT-TERM)

FAILTOSW-PATH (VT-MON)

MANUAL-REQ-RING (OCN)

TPTFAIL (G1000)

FAILTOSWR (OCN)

MANUAL-REQ-SPAN (OCN)

TRMT (DS1)

FAN (FAN)

MEA (EQPT)

TRMT-MISS (DS1)

FANDEGRADE (FAN)

MEA (FAN)

TX-AIS (DS1)

FE-AIS (DS3)

MEM-GONE (EQPT)

TX-AIS (DS3)

FE-DS1-MULTLOS (DS3)

MEM-LOW (EQPT)

TX-LOF (DS1)

FE-DS1-NSA (DS3)

MFGMEM (BPLANE)

TX-RAI (DS1)

FE-DS1-SA (DS3)

MFGMEM (FAN)

TX-RAI (DS3)

FE-DS1-SNGLLOS (DS3)

NOT-AUTHENTICATED (SYSTEM)

UNEQ-P (STSMON)

FE-DS3-NSA (DS3)

OOU-TPT (STSTRM)

UNEQ-P (STSTRM)

FE-DS3-SA (DS3)

OOU-TPT (VT-TERM)

UNEQ-V (VT-MON)

FE-EQPT-NSA (DS3)

OPTNTWMIS (NE)

UNEQ-V (VT-TERM)

FE-FRCDWKSWBK-SPAN (OCN)

PDI-P (STSMON)

VT-SQUELCH-L (OCN)

FE-FRCDWKSWPR-RING (OCN)

PDI-P (STSTRM)

WKSWPR (EQPT)

FE-FRCDWKSWPR-SPAN (OCN)

PEER-NORESPONSE (EQPT)

WKSWPR (OCN)

FE-IDLE (DS3)

PLM-P (STSMON)

WKSWPR (STSMON)

FE-LOCKOUTOFPR-SPAN (OCN)

PLM-P (STSTRM)

WKSWPR (VT-MON)

FE-LOF (DS3)

PLM-V (VT-TERM)

WTR (EQPT)

FE-LOS (DS3)

PRC-DUPID (OCN)

WTR (OCN)

FE-MANWKSWBK-SPAN (OCN)

PROTNA (EQPT)

WTR (STSMON)

FE-MANWKSWPR-RING (OCN)

PWR-FAIL-A (EQPT)

WTR (VT-MON)

FE-MANWKSWPR-SPAN (OCN)

PWR-FAIL-B (EQPT)

—

2.3  Alarm Logical Objects

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

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

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

Table 2-7 Alarm Logical Object Definitions

Logical Object

Definition

BITS

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

BPLANE

The backplane object (not used in ONS 15327).

DS1

DS1 card.

DS3

DS3 card.

E100T

E100T card.

ENVALRM

An environmental alarm port.

EQPT

A card, its physical objects, and logical objects as they are located in any of the eight noncommon card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signal (STS), and Virtual Tributary (VT).

EXT-SREF

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

FAN

Fan-tray assembly.

G1000

G1000-2 card.

NE

The entire network element.

NE-SREF

The timing status of the NE.

OCN

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

PWR

The node power supply.

STSMON

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

STSTERM

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

2.4  Alarm List by Logical Object Type

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

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

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

Table 2-8 ONS 15327 Alarm List by Logical Object Type as Listed in Alarm Profile

BITS: AIS

FAN: EQPT-MISS

OCN: SSM-DUS

BITS: LOF

FAN: FAN

OCN: SSM-FAIL

BITS: LOS

FAN: FANDEGRADE

OCN: SSM-OFF

BITS: SSM-DUS

FAN: MEA

OCN: SSM-PRS

BITS: SSM-FAIL

FAN: MFGMEM

OCN: SSM-RES

BITS: SSM-OFF

G1000: AS-CMD

OCN: SSM-SMC

BITS: SSM-PRS

G1000: AS-MT

OCN: SSM-ST2

BITS: SSM-RES

G1000: CARLOSS

OCN: SSM-ST3

BITS: SSM-SMC

G1000: LPBKFACILITY

OCN: SSM-ST3E

BITS: SSM-ST2

G1000: LPBKTERMINAL

OCN: SSM-ST4

BITS: SSM-ST3

G1000: TPTFAIL

OCN: SSM-STU

BITS: SSM-ST3E

NE-SREF: FRCDSWTOINT

OCN: SSM-TNC

BITS: SSM-ST4

NE-SREF: FRCDSWTOPRI

OCN: STS-SQUELCH-L

BITS: SSM-STU

NE-SREF: FRCDSWTOSEC

OCN: SYNC-FREQ

BITS: SSM-TNC

NE-SREF: FRCDSWTOTHIRD

OCN: TIM

BITS: SYNC-FREQ

NE-SREF: FRNGSYNC

OCN: TIM-MON

BPLANE: AS-CMD

NE-SREF: FSTSYNC

OCN: TIM-S

BPLANE: MFGMEM

NE-SREF: HLDOVRSYNC

OCN: VT-SQUELCH-L

DS1: AIS

NE-SREF: MANSWTOINT

OCN: WKSWPR

DS1: AS-CMD

NE-SREF: MANSWTOPRI

OCN: WTR

DS1: AS-MT

NE-SREF: MANSWTOSEC

PWR: AS-CMD

DS1: LOF

NE-SREF: MANSWTOTHIRD

PWR: BAT-FAIL

DS1: LOS

NE-SREF: SSM-PRS

PWR: EHIBATVG

DS1: LPBKDS1FEAC-CMD

NE-SREF: SSM-RES

PWR: ELWBATVG

DS1: LPBKFACILITY

NE-SREF: SSM-SMC

PWR: HIBATVG

DS1: LPBKTERMINAL

NE-SREF: SSM-ST2

PWR: LWBATVG

DS1: RAI

NE-SREF: SSM-ST3

SHELF: AS-CMD

DS1: SD

NE-SREF: SSM-ST3E

SHELF: AS-MT

DS1: SF

NE-SREF: SSM-ST4

STSMON: AIS-P

DS1: TRMT

NE-SREF: SSM-STU

STSMON: AUTOSW-AIS

DS1: TRMT-MISS

NE-SREF: SSM-TNC

STSMON: AUTOSW-LOP

DS1: TX-AIS

NE-SREF: SWTOPRI

STSMON: AUTOSW-PDI

DS1: TX-LOF

NE-SREF: SWTOSEC

STSMON: AUTOSW-SDBER

DS1: TX-RAI

NE-SREF: SWTOTHIRD

STSMON: AUTOSW-SFBER

DS3: AIS

NE-SREF: SYNCPRI

STSMON: AUTOSW-UNEQ

DS3: AS-CMD

NE-SREF: SYNCSEC

STSMON: ERFI-P-CONN

DS3: AS-MT

NE-SREF: SYNCTHIRD

STSMON: ERFI-P-PAYLD

DS3: DS3-MISM

NE: APC-DISABLED

STSMON: ERFI-P-SRVR

DS3: FE-AIS

NE: APC-END

STSMON: FAILTOSW-PATH

DS3: FE-DS1-MULTLOS

NE: AS-CMD

STSMON: FORCED-REQ

DS3: FE-DS1-NSA

NE: AUD-LOG-LOSS

STSMON: LOCKOUT-REQ

DS3: FE-DS1-SA

NE: AUD-LOG-LOW

STSMON: LOM

DS3: FE-DS1-SNGLLOS

NE: DATAFLT

STSMON: LOP-P

DS3: FE-DS3-NSA

NE: DBOSYNC

STSMON: LPBKCRS

DS3: FE-DS3-SA

NE: DUP-IPADDR

STSMON: MAN-REQ

DS3: FE-EQPT-NSA

NE: DUP-NODENAME

STSMON: PDI-P

DS3: FE-IDLE

NE: HITEMP

STSMON: PLM-P

DS3: FE-LOF

NE: I-HITEMP

STSMON: RFI-P

DS3: FE-LOS

NE: INTRUSION-PSWD

STSMON: ROLL

DS3: INC-ISD

NE: LAN-POL-REV

STSMON: ROLL-PEND

DS3: LOF

NE: OPTNTWMIS

STSMON: SD-P

DS3: LOS

NE: SNTP-HOST

STSMON: SF-P

DS3: LPBKDS3FEAC

NE: SYSBOOT

STSMON: TIM-P

DS3: LPBKDS3FEAC-CMD

OCN: AIS-L

STSMON: UNEQ-P

DS3: LPBKFACILITY

OCN: ALS

STSMON: WKSWPR

DS3: LPBKTERMINAL

OCN: APS-INV-PRIM

STSMON: WTR

DS3: RAI

OCN: APS-PRIM-FAC

STSTRM: AIS-P

DS3: SD

OCN: APS-PRIM-SEC-MISM

STSTRM: AS-MT-OOG

DS3: SF

OCN: APSB

STSTRM: ENCAP-MISMATCH-P

DS3: TX-AIS

OCN: APSC-IMP

STSTRM: ERFI-P-CONN

DS3: TX-RAI

OCN: APSCDFLTK

STSTRM: ERFI-P-PAYLD

E100T: AS-CMD

OCN: APSCINCON

STSTRM: ERFI-P-SRVR

E100T: CARLOSS

OCN: APSCM

STSTRM: LCAS-CRC

ENVALRM: EXT

OCN: APSCNMIS

STSTRM: LCAS-RX-FAIL

EQPT: AS-CMD

OCN: APSIMP

STSTRM: LCAS-TX-ADD

EQPT: AS-MT

OCN: APSMM

STSTRM: LCAS-TX-DNU

EQPT: AUTORESET

OCN: AS-CMD

STSTRM: LOF

EQPT: BKUPMEMP

OCN: AS-MT

STSTRM: LOM

EQPT: CARLOSS

OCN: AUTOLSROFF

STSTRM: LOP-P

EQPT: CLDRESTART

OCN: BLSR-SW-VER-MISM

STSTRM: LPBKCRS

EQPT: COMIOXC

OCN: BLSROSYNC

STSTRM: OOU-TPT

EQPT: COMM-FAIL

OCN: E-W-MISMATCH

STSTRM: PDI-P

EQPT: CONTBUS-A-18

OCN: EOC

STSTRM: PLM-P

EQPT: CONTBUS-B-18

OCN: EOC-L

STSTRM: RFI-P

EQPT: CONTBUS-DISABLED

OCN: EXERCISE-RING-FAIL

STSTRM: ROLL

EQPT: CONTBUS-IO-A

OCN: EXTRA-TRAF-PREEMPT

STSTRM: ROLL-PEND

EQPT: CONTBUS-IO-B

OCN: FAILTOSW

STSTRM: SD-P

EQPT: CTNEQPT-MISMATCH

OCN: FAILTOSWR

STSTRM: SF-P

EQPT: CTNEQPT-PBPROT

OCN: FE-FRCDWKSWBK-SPAN

STSTRM: SQM

EQPT: CTNEQPT-PBWORK

OCN: FE-FRCDWKSWPR-RING

STSTRM: TIM-P

EQPT: EQPT

OCN: FE-FRCDWKSWPR-SPAN

STSTRM: UNEQ-P

EQPT: ERROR-CONFIG

OCN: FE-LOCKOUTOFPR-SPAN

SYSTEM: DISCONNECTED

EQPT: EXCCOL

OCN: FE-MANWKSWBK-SPAN

SYSTEM: INCOMPATIBLE-SEND-PDIP

EQPT: FAILTOSW

OCN: FE-MANWKSWPR-RING

SYSTEM: INCOMPATIBLE-SW

EQPT: FORCED-REQ

OCN: FE-MANWKSWPR-SPAN

SYSTEM: LOGBUFR90

EQPT: HITEMP

OCN: FEPRLF

SYSTEM: LOGBUFROVFL

EQPT: IMPROPRMVL

OCN: FORCED-REQ-RING

SYSTEM: NOT-AUTHENTICATED

EQPT: INHSWPR

OCN: FORCED-REQ-SPAN

VT-MON: AIS-V

EQPT: INHSWWKG

OCN: FULLPASSTHR-BI

VT-MON: AUTOSW-AIS

EQPT: LOCKOUT-REQ

OCN: HELLO

VT-MON: AUTOSW-LOP

EQPT: MAN-REQ

OCN: HI-LASERBIAS

VT-MON: AUTOSW-UNEQ

EQPT: MANRESET

OCN: HI-LASERTEMP

VT-MON: FAILTOSW-PATH

EQPT: MEA

OCN: HI-RXPOWER

VT-MON: FORCED-REQ

EQPT: MEM-GONE

OCN: HI-TXPOWER

VT-MON: LOCKOUT-REQ

EQPT: MEM-LOW

OCN: ISIS-ADJ-FAIL

VT-MON: LOP-V

EQPT: PEER-NORESPONSE

OCN: KB-PASSTHR

VT-MON: MAN-REQ

EQPT: PROTNA

OCN: KBYTE-APS-CHANNEL-FAILURE

VT-MON: RFI-V

EQPT: PWR-FAIL-Au

OCN: LASEREOL

VT-MON: ROLL

EQPT: PWR-FAIL-B

OCN: LKOUTPR-S

VT-MON: ROLL-PEND

EQPT: PWR-FAIL-RET-A

OCN: LO-LASERBIAS

VT-MON: SD-V

EQPT: PWR-FAIL-RET-B

OCN: LO-LASERTEMP

VT-MON: SF-V

EQPT: RUNCFG-SAVENEED

OCN: LO-RXPOWER

VT-MON: UNEQ-V

EQPT: SFTWDOWN

OCN: LO-TXPOWER

VT-MON: WKSWPR

EQPT: SW-MISMATCH

OCN: LOCKOUT-REQ

VT-MON: WTR

EQPT: SWMTXMOD-PROT

OCN: LOF

VT-TERM: AIS-V

EQPT: SWMTXMOD-WORK

OCN: LOS

VT-TERM: AS-MT-OOG

EQPT: WKSWPR

OCN: LPBKFACILITY

VT-TERM: LCAS-CRC

EQPT: WTR

OCN: LPBKTERMINAL

VT-TERM: LCAS-RX-FAIL

EXT-SREF: FRCDSWTOPRI

OCN: MANUAL-REQ-RING

VT-TERM: LCAS-TX-ADD

EXT-SREF: FRCDSWTOSEC

OCN: MANUAL-REQ-SPAN

VT-TERM: LCAS-TX-DNU

EXT-SREF: FRCDSWTOTHIRD

OCN: PRC-DUPID

VT-TERM: LOM

EXT-SREF: MANSWTOPRI

OCN: RFI-L

VT-TERM: LOP-V

EXT-SREF: MANSWTOSEC

OCN: RING-ID-MIS

VT-TERM: OOU-TPT

EXT-SREF: MANSWTOTHIRD

OCN: RING-MISMATCH

VT-TERM: PLM-V

EXT-SREF: SWTOPRI

OCN: RING-SW-EAST

VT-TERM: RFI-V

EXT-SREF: SWTOSEC

OCN: RING-SW-WEST

VT-TERM: SD-V

EXT-SREF: SWTOTHIRD

OCN: SD-L

VT-TERM: SF-V

EXT-SREF: SYNCPRI

OCN: SF-L

VT-TERM: SQM

EXT-SREF: SYNCSEC

OCN: SQUELCH

VT-TERM: TIM-V

EXT-SREF: SYNCTHIRD

OCN: SQUELCHED

VT-TERM: UNEQ-V

2.5  Trouble Notifications

The ONS 15327 system reports trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253-CORE, and graphical user interface (GUI) state indicators.These notifications are described in the following paragraphs.

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

2.5.1  Alarm Characteristics

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

2.5.2  Condition Characteristics

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

For a comprehensive list of all conditions, refer to the Cisco ONS SONET TL1 Command Guide. For more information about transient conditions, see Chapter 3 "Transient Conditions."

2.5.3  Severities

The ONS 15327 uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), and Not Reported (NR):

•A Critical (CR) alarm generally indicates severe, Service-Affecting (SA) trouble that needs immediate correction. Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.

•A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, loss of traffic on more than five DS-1 circuits is Critical (CR), but loss of traffic on one to four DS-1 circuits is Major (MJ).

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

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

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

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

2.5.4  Alarm Hierarchy

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

A path alarm can be demoted if a higher-ranking alarm is raised for the same object. For example, If a path trace identifier mismatch (TIM-P) is raised on a circuit path and then a loss of pointer on the path (LOP-P) is raised on the path, the LOP-P alarm stands and the TIM-P closes. The path alarm hierarchy is shown in Table 2-9.

Table 2-9 Path Alarm Hierarchy

Priority

Condition Type

Highest

AIS-P

—

LOP-P

—

UNEQ-P

Lowest

TIM-P

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

Table 2-10 Facility Alarm Hierarchy

Priority

Condition Type

Highest

LOS

—

LOF

—

AIS-L

—

SF-L

—

SD-L

—

RFI-L

—

TIM-S

—

AIS-P

—

LOP-P

—

SF-P

—

SD-P

—

UNEQ-P

—

TIM-P

Lowest

PLM-P

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

Table 2-11 Near-End Alarm Hierarchy

Priority

Condition Type

Highest

LOS

—

LOF

—

AIS-L

—

AIS-P¹

—

LOP-P²

—

UNEQ-P

—

TIM-P

—

PLM-P

—

AIS-V1

—

LOP-V2

—

UNEQ-V

—

PLM-V

Lowest

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

¹Although it is not defined as a defect or failure, all-ones STS pointer relay is also higher priority than LOP-P. Similarly, all-ones VT pointer relay is higher priority than LOP-V.

²LOP-P is also higher priority than the far-end failure RFI-P, which does not affect the detection of any near-end failures. Similarly, LOP-V is higher priority than RFI-V.

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

Table 2-12 Far-End Alarm Hierarchy

Priority

Condition Type

Highest

RFI-L

—

RFI-P

Lowest

RFI-V

2.5.5  Service Effect

Service-Affecting (SA) alarms—those that interrupt service—could be Critical (CR), Major (MJ), or Minor (MN) severity alarms. Service-Affecting (SA) alarms indicate service is affected. Non-Service-Affecting (NSA) alarms always have a Minor (MN) default severity.

2.5.6  States

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

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

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

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

2.6  Safety Summary

This section covers safety considerations designed to ensure safe operation of the ONS 15327. Personnel should not perform any procedures in this chapter 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 could be present when the system is operating. Use caution when removing or installing cards.

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

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

Warning Class 1 laser product. Statement 1008

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

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

2.7  Alarm Procedures

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

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

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

Note When an entity is put in the Out-of-Service and Maintenance (OOS,MT) administrative state, the ONS 15327 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab.

2.7.1  AIS

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

Logical Objects: BITS, DS1, DS3

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

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

Clear the AIS Condition

Step 1 Determine whether there are alarms on the upstream nodes and equipment, especially the "LOS (OCN)" alarm on page 2-99, or if there are out-of-service (OOS,MT or OOS,DSBLD) ports.

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

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

2.7.2  AIS-L

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

Logical Object: OCN

The AIS Line condition indicates that this node is detecting line-level AIS in the incoming signal. This alarm is secondary to another alarm occurring simultaneously in an upstream node.

This condition can also be raised in conjunction with the "TIM-S" alarm on page 2-144 if AIS-L is enabled.

Clear the AIS-L Condition

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

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

2.7.3  AIS-P

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

Logical Objects: STSMON, STSTRM

The AIS Path condition means that this node is detecting AIS in the incoming path. This alarm is secondary to another alarm occurring simultaneously in an upstream node.

Clear the AIS-P Condition

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

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

2.7.4  AIS-V

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

Logical Objects: VT-MON, VT-TERM

The AIS VT condition means that this node is detecting AIS in the incoming VT-level path.

See the "AIS-V on XTC-28-3 Card Unused VT Circuits" section for more information.

Clear the AIS-V Condition

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

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

2.7.5  ALS

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.6  APC-DISABLED

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.7  APC-END

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.8  APSB

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

Logical Object: OCN

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

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 might not interoperate effectively with the ONS 15327.

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

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

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

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

2.7.9  APSCDFLTK

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

Logical Object: OCN

The APS Default K Byte Received alarm occurs during bidirectional line switched ring (BLSR) provisioning or when a BLSR is not properly configured—for example, when a four-node BLSR has one node configured as a path protection. When this misconfiguration occurs, a node in a path protection 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 the "BLSROSYNC" alarm on page 2-35.

Clear the APSCDFLTK Alarm

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

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

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

Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" alarm on page 2-59.) West port fibers must connect to east port fibers and east port fibers must connect to west port fibers. The "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide provides procedures for fibering BLSRs.

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

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

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

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

2.7.10  APSC-IMP

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

Logical Object: OCN

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

•Unused code in bits 6 through 8 of byte K2.

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

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

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

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

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

Clear the APSC-IMP Alarm

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

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

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

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

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

2.7.11  APSCINCON

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

Logical Object: OCN

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

Clear the APSCINCON Alarm

Step 1 Look for other alarms, especially the "LOS (OCN)" alarm on page 2-99, the "LOF (OCN)" alarm on page 2-93, or the "AIS" condition on page 2-18. Clearing these alarms clears the APSCINCON alarm.

Step 2 If an APSINCON alarm occurs with no other alarms, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.12  APSCM

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

Logical Object: OCN

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

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

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

Clear the APSCM Alarm

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 2 If the fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node protection-card channel fibers.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.13  APSCNMIS

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

Logical Object: OCN

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

Clear the APSCNMIS Alarm

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

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

Step 3 Click Close in the Ring Map dialog box.

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

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

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

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

Step 6 Complete the "Clear a BLSR External Switching Command" procedure to clear the lockout.

Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.14  APSIMP

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

Logical Object: OCN

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

The alarm is superseded by an APSCM or APSMM alarm, but not by an AIS condition. It clears when the port receives a valid code for 10 ms.

Clear the APSIMP Alarm

Step 1 Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group. For procedures, refer to the "Turn Up Node" chapter in the Cisco ONS 15327 Procedure Guide.

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

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

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

2.7.15  APS-INV-PRIM

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

2.7.16  APSMM

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

Logical Object: OCN

An APS Mode Mismatch failure alarm occurs on OC-N cards when there is a mismatch of the protection switching schemes at the two ends of the span, such as being bidirectional at one end and unidirectional at the other. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional.

If one end is provisioned for 1+1 protection switching and the other is provisioned for path protection switching, an APSMM alarm occurs in the ONS 15327 that is provisioned for 1+1 protection switching.

Clear the APSMM Alarm

Step 1 For the reporting ONS 15327, display node view and verify the protection scheme provisioning by completing the following steps:

a. Click the Provisioning > Protection tabs.

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

The chosen protection group is the protection group optically connected (with data communications channel [DCC] connectivity) to the far end.

c. Click Edit.

d. Record whether the Bidirectional Switching check box is checked.

Step 2 Click OK in the Edit Protection Group dialog box.

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

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

Step 5 Click Apply.

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

2.7.17  APS-PRIM-FAC

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

2.7.18  APS-PRIM-SEC-MISM

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

2.7.19  AS-CMD

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

Logical Objects: BPLANE, DS1, DS3, E100T, EQPT, G1000, NE, OCN, PWR, SHELF

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

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

Clear the AS-CMD Condition

Step 1 In node view, click the Conditions tab.

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

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

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

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

If the Condition window says that the object is "NE," the condition applies to the shelf. Go to Step 8.

Step 3 Determine whether alarms are suppressed for a port and if so, raise the suppressed alarms by completing the following steps:

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

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

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

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

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

Step 5 Locate the row number for the reported card slot.

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

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

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

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

c. Click Apply.

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

a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs if you have not already done so.

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

c. Click Apply.

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

2.7.20  AS-MT

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

Logical Objects: DS1, DS3, EQPT, G1000, OCN, SHELF

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

Clear the AS-MT Condition

Step 1 Complete the "Clear an OC-N Card Facility or Terminal Loopback Circuit" procedure, the "Clear an OC-N Card XC Loopback Circuit" procedure, the "Clear an XTC Card DS-1 or DS-3 Loopback Circuit" procedure, or the "Clear a G1000 Card Loopback" procedure, as appropriate.

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

2.7.21  AS-MT-OOG

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

Logical Objects: STSTRM, VT-TERM

The Alarms Suppressed on an Out-Of-Group Virtual Concatenation (VCAT) Member alarm is raised on an STS or VT member of a VCAT group whenever the member is in the IDLE (AS-MT-OOG) Admin State. This alarm can be raised when a member is initially added to a group. In IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.

Clear the AS-MT-OOG Alarm

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

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

2.7.22  AUD-LOG-LOSS

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

Logical Object: NE

The Audit Trail Log Loss condition occurs when the log is 100 percent full and the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries. The log must be off-loaded using the following procedure to make room for more entries.

Clear the AUD-LOG-LOSS Condition

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

Step 2 Click Retrieve.

Step 3 Click Archive.

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

Step 5 Enter a name in the File Name field.

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

Step 6 Click Save.

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

Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.23  AUD-LOG-LOW

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

Logical Object: NE

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

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

2.7.24  AUTOLSROFF

The AUTOLSROFF alarm is not used in this platform in this release. It is reserved for development.

2.7.25  AUTORESET

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

Logical Object: EQPT

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

AUTORESET typically clears after a card reboots (up to ten minutes). If the alarm does not clear, complete the following procedure.

Clear the AUTORESET Alarm

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

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

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

2.7.26  AUTOSW-AIS

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

Logical Objects: STSMON, VT-MON

The Automatic UPSR Switch Caused by an AIS condition indicates that automatic path protection switching occurred because of an AIS condition. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.

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

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

Clear the AUTOSW-AIS Condition

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

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

2.7.27  AUTOSW-LOP (STSMON)

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

Logical Object: STSMON

The Automatic UPSR Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the "LOP-P" alarm on page 2-95. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

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

Clear the AUTOSW-LOP (STSMON) Condition

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

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

2.7.28  AUTOSW-LOP (VT-MON)

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

Logical Object: VT-MON

The Automatic UPSR Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the "LOP-V" alarm on page 2-96. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

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

Clear the AUTOSW-LOP (VT-MON) Condition

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

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

2.7.29  AUTOSW-PDI

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

Logical Object: STSMON

The Automatic UPSR Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a "PDI-P" alarm on page 2-112. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

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

Clear the AUTOSW-PDI Condition

Step 1 Complete the "Clear the PDI-P Condition" procedure.

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

2.7.30  AUTOSW-SDBER

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

Logical Object: STSMON

The Automatic UPSR Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a "SD-P" condition on page 2-126 caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SD-P is resolved.

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

Clear the AUTOSW-SDBER Condition

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

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

2.7.31  AUTOSW-SFBER

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

Logical Object: STSMON

The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a "SF-P" condition on page 2-128 caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SF-P is resolved.

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

Clear the AUTOSW-SFBER Condition

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

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

2.7.32  AUTOSW-UNEQ

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA) for STSMON; Minor (MN), Non-Service-Affecting (NSA) for VT-MON

Logical Objects: STSMON, VT-MON

The Automatic UPSR Switch Caused by Unequipped condition indicates that an UNEQ alarm caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

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

Clear the AUTOSW-UNEQ Condition

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

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

2.7.33  BAT-FAIL

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

Logical Object: PWR

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

Clear the BAT-FAIL Alarm

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

Step 2 Remove the power cable from the faulty supply. procedures, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide and reverse the power cable installation procedure.

Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.34  BKUPMEMP

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

Logical Object: EQPT

The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the XTC card flash memory. The alarm occurs when the XTC card has one of four problems:

•Flash manager fails to format a flash partition.

•Flash manager fails to write a file to a flash partition.

•Problem at the driver level.

•Code volume fails the cyclic redundancy check (CRC, a method to verify for errors in data transmitted to the XTC card).

The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-56. 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 XTC card.

Clear the BKUPMEMP Alarm

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

Step 2 Determine whether the active or standby XTC card has the alarm.

Step 3 If both cards are powered and enabled, reset the active XTC card to make the standby XTC card active. Complete the "Reset an Active XTC Card and Activate the Standby Card" procedure. If the card is the standby XTC card, complete the following steps:

a. Right-click the standby XTC card in CTC.

b. Choose Reset Card from the shortcut menu.

c. Click Yes in the Are You Sure dialog box. The card resets, the FAIL LED blinks on the physical card.

d. Wait ten minutes to verify that the card you reset completely reboots.

Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active XTC card LED should be green.

Step 4 If the XTC card you reset does not reboot successfully, or the alarm has not cleared, call Cisco Technical Support (1-800-553-2447). If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.35  BLSROSYNC

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

Logical Object: OCN

The BLSR Out Of Synchronization alarm occurs during BLSR setup when you attempt to add or delete a circuit, and a working ring node loses its DCC connection because all transmit and receive fiber has been removed. CTC cannot generate the ring table and causes the BLSROSYNC alarm.

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

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

Clear the BLSROSYNC Alarm

Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide for cabling information to reestablish the DCC. To verify cable continuity, follow site practices.

When the DCC is established between the node and the rest of the BLSR, it becomes visible to the BLSR and should be able to function on the circuits.

Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" alarm on page 2-53.

Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.36  BLSR-SW-VER-MISM

This alarm is not used in this platform in this release. It is reserved for development.

2.7.37  CARLOSS (E100T)

The CARLOSS alarm for E100T is not used in this platform in this release. It is reserved for development.

2.7.38  CARLOSS (EQPT)

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

Logical Object: EQPT

A Carrier Loss on the LAN Equipment alarm generally occurs on optical cards when the ONS 15327 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 XTC card. 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 node.

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Clear the CARLOSS (EQPT) Alarm

Step 1 If the reporting card is an OC-N card, verify connectivity by pinging the ONS 15327 that is reporting the alarm by completing the procedure in the "Verify PC Connection to the ONS 15327 (Ping)" section.

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

Step 3 Using optical test equipment, verify that proper receive levels are achieved. (For instructions to use optical test equipment, refer to the manufacturer documentation.)

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 4 Verify that the optical LAN cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

Step 5 If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

Step 6 If you are unable to establish connectivity, replace the fiber cable with a new known-good cable. To do this, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide for procedures.

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

Step 8 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.39  CARLOSS (G1000)

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

Logical Object: G1000

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

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

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

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

For more information about Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327. This manual includes a description of the G-Series card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-145 for more information about alarms that occur when a point-to-point circuit exists between two cards.

Ethernet card ports must be enabled for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.

Clear the CARLOSS (G1000) Alarm

Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

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

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

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

Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

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

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

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

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

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

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

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

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

b. Click the Maintenance > Loopback tabs.

c. If the service state is listed as OOS-MA,MT, a loopback is provisioned. Go to Step 11.

Step 11 If a loopback was provisioned, complete the "Clear a G1000 Card Loopback" procedure.

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

If the G1000-2 card does not have a loopback condition, continue to Step 12.

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

Note An ONS 15327 Ethernet manual cross-connect is used when another vendor's equipment sits between ONS nodes, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15327 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.

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

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

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

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

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

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

•Click the Circuits tab.

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

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

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

g. 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. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

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

Step 14 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.40  CLDRESTART

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

Logical Object: EQPT

The Cold Restart condition occurs when a card is physically removed and inserted (reseated), replaced, or when the ONS 15327 power is initialized.

Clear the CLDRESTART Condition

Step 1 Complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

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

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

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

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

2.7.41  COMIOXC

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

Logical Object: EQPT

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

Clear the COMIOXC Alarm

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

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

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

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

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

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

Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.42  COMM-FAIL

The COMM-FAIL alarm is not used in this platform in this release. It is reserved for development.

2.7.43  CONTBUS-A-18

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

Logical Object: EQPT

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

Clear the CONTBUS-A-18 Alarm

Step 1 Complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure to make the Slot 6 XTC card active.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

Step 3 Position the cursor over the Slot 5 XTC card and complete the "Reset an Active XTC Card and Activate the Standby Card" procedure to return the card to the active state.

Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco Technical Assistance Center (TAC) at 1-800-553-2447. If the Cisco TAC technician tells you to reseat the card, complete the "Reset an Active XTC Card and Activate the Standby Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.44  CONTBUS-B-18

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

Logical Object: EQPT

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

Clear the CONTBUS-B-18 Alarm

Step 1 Complete the "Reset an Active XTC Card and Activate the Standby Card" procedure to make the Slot 5 XTC card active.

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

Step 3 Position the cursor over the Slot 5 XTC card and complete the "Reset an Active XTC Card and Activate the Standby Card" procedure to return the Slot 6 XTC card to the active state.

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

2.7.45  CONTBUS-DISABLED

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

Logical Object: EQPT

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

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

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

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

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

Clear the CONTBUS-DISABLED Alarm

Step 1 If the IMPROPRMVL alarm is raised, complete the "Physically Replace a Card" procedure. (For general information about card installation, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.)

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

2.7.46  CONTBUS-IO-A

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

Logical Object: EQPT

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

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

Clear the CONTBUS-IO-A Alarm

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

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

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

Step 3 If the alarm object is the standby Slot 6 XTC card, complete the "Reset a Traffic Card in CTC" procedure for it. The process is similar for the standby XTC card.

Note Resetting the standby XTC card card does not activate it.

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

If CONTBUS-IO-A is raised on several cards at the same time, complete the "Reset an Active XTC Card and Activate the Standby Card" procedure.

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

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco Technical Support (1-800-553-2447) and perform the following steps under their supervision:

a. If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure.

b. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

c. If the Cisco Technical Support technician tells you to remove the chassis and install a new one, complete the "Chassis Replacement Procedure" section.

2.7.47  CONTBUS-IO-B

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

Logical Object: EQPT

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

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

Clear the CONTBUS-IO-B Alarm

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

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

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

Step 3 If the alarm object is the standby Slot 5 XTC card, complete the "Reset a Traffic Card in CTC" procedure for it. The process is similar for the standby XTC card.

Note Resetting the standby XTC card card does not activate it.

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

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

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

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 7 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco Technical Support (1-800-553-2447) and perform the following steps under their supervision:

a. If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure.

b. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

c. If the Cisco Technical Support technician tells you to remove the chassis and install a new one, complete the "Chassis Replacement Procedure" section.

2.7.48  CTNEQPT-MISMATCH

The CTNEQPT-MISMATCH alarm is not used in this platform in this release. It is reserved for development.

2.7.49  CTNEQPT-PBPROT

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

Logical Object: EQPT

The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus alarm indicates a failure of the main payload between the protect XTC card and the reporting traffic card. The XTC card and the reporting card are no longer communicating. The problem exists in the XTC card or the reporting traffic card.

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC card slots.

Clear the CTNEQPT-PBPROT Alarm

Step 1 If all traffic cards show CTNEQPT-PBPROT alarm, complete the following steps:

a. Complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure for the standby XTC card.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

Caution Do not physically reseat an active XTC card. Doing so disrupts traffic.

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

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

If the cross-connect reset is not complete and error-free or if the XTC card reboots automatically, call Cisco TAC (1-800-553-2447).

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

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

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

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

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

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

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

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

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

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

Step 12 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.50  CTNEQPT-PBWORK

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

Logical Object: EQPT

The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the ONS 15327 XTC card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the XTC card and the reporting traffic card.

Note This alarm automatically raises and clears when the ONS 15327 Slot 6 XTC card is reseated.

Clear the CTNEQPT-PBWORK Alarm

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

a. Complete the "Reset an Active XTC Card and Activate the Standby Card" procedure for the active XTC card and then complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure.

b. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the XTC card.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Caution Do not physically reseat an active XTC card; it disrupts traffic.

Step 2 If not all traffic cards show the alarm, complete the "Side Switch the Active and Standby XTC Cards" procedure for the active XTC card.

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

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

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

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

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

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

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

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

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

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

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

Step 13 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.51  DATAFLT

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

Logical Object: NE

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

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

Clear the DATAFLT Alarm

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

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

2.7.52  DBOSYNC

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

Logical Object: NE

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

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

Clear the DBOSYNC Alarm

Step 1 Save a backup copy of the active XTC card database. Refer to the "Maintain the Node" chapter of the Cisco ONS 15327 Procedure Guide for procedures.

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

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

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

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

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

2.7.53  DISCONNECTED

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

Logical Object: SYSTEM

The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm is cleared when CTC is reconnected to the node.

Clear the DISCONNECTED Alarm

Step 1 Restart the CTC application.

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

2.7.54  DS3-MISM

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

Logical Object: DS3

The DS-3 Frame Format Mismatch condition indicates that a frame format mismatch on a signal transiting the XTC-28-3 card. The condition occurs when the provisioned line type and incoming signal frame format type do not match. For example, if the line type is set to D4 for a DS-1 transiting the XTC-28-3 card, and the incoming signal's frame format is detected as unframed, then the ONS 15327 reports a DS3-MISM condition.

Clear the DS3-MISM Condition

Step 1 Display the CTC card view for the reporting XTC-28-3 card.

Step 2 Click the Provisioning > Line tabs.

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

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

Step 5 Click Apply.

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

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

2.7.55  DUP-IPADDR

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

Logical Object: NE

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

Clear the DUP-IPADDR Alarm

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

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

b. Begin a CTC session.

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

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

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

Step 4 Click Apply.

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

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

2.7.56  DUP-NODENAME

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

Logical Object: NE

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

Clear the DUP-NODENAME Alarm

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

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

Step 3 Click Apply.

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

2.7.57  DUP-SHELF-ID

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.58  EHIBATVG

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

Logical Object: PWR

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

Clear the EHIBATVG Alarm

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

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.59  ELWBATVG

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

Logical Object: PWR

The Extreme Low Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage falls below the extreme low power threshold. This threshold, with a default value of -40.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains over the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up Node" chapter of the Cisco ONS 15327 Procedure Guide.)

Clear the ELWBATVG Alarm

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

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.60  ENCAP-MISMATCH-P

The ENCAP-MISMATCH-P alarm is not used in this platform in this release. It is reserved for development.

2.7.61   EOC

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

Logical Object: OCN

The SONET DCC Termination Failure alarm occurs when the ONS 15327 loses its DCC. Although this alarm is primarily SONET, it can apply to dense wavelength division multiplexing (DWDM) in other platforms.

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

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

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

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

Clear the EOC Alarm

Step 1 If the "LOS (OCN)" alarm on page 2-99 is also reported, complete the "Clear the LOS (OCN) Alarm" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 2 If the "SF-L" condition on page 2-128 is reported, complete the "Clear the SF-L Condition" procedure.

Step 3 If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry SDCC traffic. If they are not correct, correct them. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

Step 4 If the physical connections are correct and configured to carry DCC traffic, ensure that the ports at both ends of the fiber span are in the In Service and Normal (IS-NR) service state. Ensure that the ACT/SBY LED on each OC-N card is green.

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

Step 6 Repeat Step 4 at the adjacent nodes.

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

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

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

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

c. Click the Provisioning > Line tabs.

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

e. If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and click IS from the drop-down list. Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

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

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

Step 9 If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. See the Table 1-5 for optical transmit and receive levels.

Step 10 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide.

Step 11 If fiber connectors are properly fastened and terminated, complete the "Reset an Active XTC Card and Activate the Standby Card" procedure.

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

Resetting the active XTC card switches control to the standby XTC card. If the alarm clears when the ONS 15327 node switches to the standby XTC card, the user can assume that the previously active card is the cause of the alarm.

Step 12 If the XTC card reset does not clear the alarm, delete the problematic SDCC termination by completing the following steps:

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

b. Click the Provisioning > Comm Channels > SDCC tabs.

c. Highlight the problematic DCC termination.

d. Click Delete.

e. Click Yes in the Confirmation Dialog box.

Step 13 Recreate the SDCC termination. Refer to the "Turn Up Network" chapter of the Cisco ONS 15327 Procedure Guide for procedures.

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

Step 15 If the alarm has not cleared, call Cisco Technical Support (1-800-553-2447). If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.62  EOC-L

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

Logical Objects: OCN

The Line DCC Termination Failure alarm occurs when the ONS 15327 loses its Line DCC (LDCC) termination. The LDCC consists of nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS 15327 uses the LDCCs on the SONET line layer to communicate network management information.

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

Clear the EOC-L Alarm

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

Step 2 If the alarm has not cleared, call Cisco Technical Support (1-800-553-2447). If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

2.7.63  EQPT

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

Logical Object: EQPT

An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card. If the EQPT alarm occurs with a BKUPMEMP alarm, refer to the "BKUPMEMP" section. The BKUPMEMP procedure also clears the EQPT alarm.

This alarm is also invoked if a diagnostic circuit detects a card application-specific integrated circuit (ASIC) failure. In this case, if the card is part of a protection group, an APS switch occurs. If the card is the protect card, switching is inhibited and a PROTNA alarm is raised. The standby path generates a path-type alarm.

Clear the EQPT Alarm

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

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

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

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

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

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.64  EQPT-DIAG

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

Logical Object: EQPT

An Equipment-Diagnostic Failure alarm indicates that a software or hardware failure has occurred on the reporting card. This alarm can be raised against an OC-N card or an XTC card.

Clear the EQPT-DIAG Alarm

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

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

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

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

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

2.7.65  EQPT-MISS

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

Logical Object: FAN

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Clear the EQPT-MISS Alarm

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

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

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

Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.66  ERFI-P-CONN

The ERFI-P-CONN alarm is not used in this platform in this release. It is reserved for development.

2.7.67  ERFI-P-PAYLD

The ERFI-P-PAYLD alarm is not used in this platform in this release. It is reserved for development.

2.7.68  ERFI-P-SRVR

The ERFI-P-SRVR alarm is not used in this platform in this release. It is reserved for development.

2.7.69  ERROR-CONFIG

The ERROR-CONFIG alarm is not used in this platform in this release. It is reserved for development.

2.7.70  E-W-MISMATCH

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

Logical Object: OCN

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

Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its east-west slots 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 at a node is traditionally labeled the west slot and the higher numbered slot is labeled the east slot. For example, in the ONS 15327 system, Slot 1 is west and Slot 4 is east.

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

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

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

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

Step 3 Click the circuit and click Edit. The network map detailed view window appears. This window contains the node name, slot, and port for each end of each span.

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

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

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

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

Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span. Refer to the "Install Hardware" chapter of the Cisco ONS 15327 Procedure Guide for more information about cabling the system.

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

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

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

Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

Clear the E-W-MISMATCH Alarm in CTC

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

Step 2 Click the Maintenance > BLSR tabs.

Step 3 From the row of information for the fiber span, complete the "Identify an ONS 15327 BLSR Ring Name or Node ID Number" procedure to identify the node ID, ring name, and the slot and port in the East Line column and West Line column. Record the above information.

Step 4 Click View > Go to Network View.

Step 5 Delete and recreate the BLSR by completing the following steps:

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 name and node ID from the information collected in Step 3.

e. Click Finish.

Step 6 Display node view and click the Maintenance > BLSR tabs.

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

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

Step 9 Click OK.

Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.71  EXCCOL

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

Logical Object: EQPT

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

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

Clear the EXCCOL Alarm

Step 1 Verify that the network device port connected to the XTC 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 XTC card and the network management LAN.

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

2.7.72  EXERCISE-RING-FAIL

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

Logical Object: OCN

The Exercise Ring command issues ring protection switching of the requested channel without completing the actual bridge and switch. The EXERCISE-RING-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.

Note If the exercise command gets rejected due to the existence of a higher priority condition in the ring, EXERCISE-RING-FAIL is Not Reported (NR).

Clear the EXERCISE-RING-FAIL Condition

Step 1 Look for and clear, if present, the "LOF (OCN)" alarm on page 2-93, the "LOS (OCN)" alarm on page 2-99, or BLSR alarms.

Step 2 Reissue the "Initiate an Exercise Ring Switch on a BLSR" procedure.

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

2.7.73  EXT

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

Logical Object: ENVALRM

A Failure Detected External to the NE alarm occurs because an environmental alarm is present. For example, a door could be open or flooding could have occurred.

Clear the EXT Alarm

Step 1 Follow your standard operating procedure to remedy environmental conditions that cause alarms. The alarm clears when the situation is remedied.

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

2.7.74  EXTRA-TRAF-PREEMPT

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

Logical Object: OCN

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

Clear the EXTRA-TRAF-PREEMPT Alarm

Step 1 Verify that the protection switch has occurred by checking the Conditions tab.

Step 2 If a ring switch has occurred, clear the ring switch on the working system by following the appropriate alarm in this chapter. For more information about protection switches, refer to the "Protection Switching, Lock Initiation, and Clearing" section.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.75  FAILTOSW

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

Logical Objects: EQPT, OCN

The Failure to Switch to Protection Facility condition occurs when a working or protect electrical facility switches to its companion port by using a MANUAL command. For example, if you attempt to manually switch traffic from an unused protect port to an in-service working port, the switch will fail (because traffic is already present on the working port) and you will see the FAILTOSW condition.

Clear the FAILTOSW Condition

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

Step 2 If the condition does not clear, replace the working electrical card that is reporting the higher priority alarm by following the "Physically Replace a Card" procedure. This card is the working electrical card using the protect card and not reporting FAILTOSW.

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

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

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

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

2.7.76  FAILTOSW-PATH

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

Logical Objects: STSMON, VT-MON

The Fail to Switch to Protection Path condition occurs when the working circuit does not switch to the protection circuit on a path protection. Common causes of the FAILTOSW-PATH alarm include a missing or defective protect port, a lockout set on one of the path protection nodes, or path-level alarms that would cause a path protection switch to fail including the "AIS-P" condition on page 2-19, the "LOP-P" alarm on page 2-95, the "SD-P" condition on page 2-126, the "SF-P" condition on page 2-128, and the "UNEQ-P" alarm on page 2-147.

The "LOF (OCN)" alarm on page 2-93, the "LOS (OCN)" alarm on page 2-99, the "SD-P" condition on page 2-126, or the "SF-L" condition on page 2-128 can also occur on the failed path.

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration

Step 1 Look up and clear the higher priority alarm. Clearing this condition frees the standby card and clears the FAILTOSW-PATH condition. If the "AIS-P" condition on page 2-19, the "LOP-P" alarm on page 2-95, the "UNEQ-P" alarm on page 2-147, the "SF-P" condition on page 2-128, the "SD-P" condition on page 2-126, the "LOF (OCN)" alarm on page 2-93, the "LOS (OCN)" alarm on page 2-99, the "SD-P" condition on page 2-126, or the "SF-L" condition on page 2-128 are also occurring on the reporting port, complete the applicable alarm clearing procedure.

Step 2 If the alarm does not clear, replace the active OC-N card that is reporting the higher priority alarm. Complete the "Physically Replace a Card" procedure. Replacing the active OC-N card that is reporting the higher priority alarm allows traffic to revert to the active slot. Reverting frees the standby card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW-PATH condition.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

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

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

2.7.77  FAILTOSWR

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

Logical Object: OCN

The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems. FAILTOSWR clears in any of the following situations:

•A physical card pull of the active XTC card (done under Cisco Technical Support supervision).

•A node power cycle.

•A higher-priority event such as an external switch command.

•The next ring switch succeeds.

•The cause of the APS switch (such as the "SD (DS1, DS3)" condition on page 2-124 or the "SF (DS1, DS3)" condition on page 2-127) clears.

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

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

Clear the FAILTOSWR Condition in a BLSR Configuration

Step 1 Perform the EXERCISE RING command on the reporting card by completing the following steps:

a. Click the Maintenance > 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, from the view menu, choose Go to 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.

Step 5 Click the Maintenance > BLSR tabs.

Step 6 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards and ports are active and in service by completing the following steps:

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

b. Double-click the card in CTC to display the card view.

c. Click the Provisioning > Line tabs.

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

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

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Step 7 If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards. To verify fiber continuity, follow site practices.

Step 8 If fiber continuity to the ports is okay, use an optical test set to verify that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.

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

Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 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 receiver specifications. Table 1-5 lists these specifications.

Step 11 Repeat Steps 7 through 10 for any other ports on the card.

Step 12 If the optical power level for all 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. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

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

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

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

2.7.78  FAN

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

Logical Object: FAN

The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15327 can rise above its normal operating range.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Clear the FAN Alarm

Step 1 Determine whether the air filter needs replacement. Complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Step 2 If the filter is clean, complete the "Remove and Reinsert a Fan-Tray Assembly" 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.

Step 4 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447).

2.7.79  FANDEGRADE

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

Logical Object: FAN

The Partial Fan Failure Speed Control Degradation alarm occurs if fan speed for one of the fans in the fan-tray assembly falls under 500 RPM when read by a tachometry counter.

Clear the FANDEGRADE Alarm

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

Step 2 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447).

2.7.80  FE-AIS

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

Logical Object: DS3

The Far-End AIS condition occurs when an AIS has occurred at the far-end node. FE-AIS usually occurs in conjunction with a downstream LOS alarm (see the "LOS (OCN)" alarm on page 2-99).

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

Clear the FE-AIS Condition

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

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

2.7.81  FE-DS1-MULTLOS

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

Logical Object: DS3

The Far-End Multiple DS-1 LOS Detected condition occurs when multiple DS-1 signals are lost on a far-end XTC card.

The prefix FE 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 or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.

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 ONS 15327 FE condition on an XTC card in Slot 5 of Node 1 could relate to a main alarm from an XTC card in Slot 6 of Node 2.

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

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

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

2.7.82  FE-DS1-NSA

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

Logical Object: DS3

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

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 alarm from an XTC card in Slot 5 of Node 1 could link to an alarm from an XTC card in Slot 6 of Node 2.

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

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

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

2.7.83  FE-DS1-SA

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

Logical Object: DS3

The Far End DS-1 Equipment Failure Service-Affecting condition occurs when there is a far-end equipment failure on an XTC card that affects service because traffic is unable to switch to the protect port.

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 alarm from an XTC card in Slot 5 of Node 1 could link to an alarm from an XTC card in Slot 6 of Node 2.

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

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

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

2.7.84  FE-DS1-SNGLLOS

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

Logical Object: DS3

The Far-End Single DS-1 LOS condition occurs when a single DS-1 signal is lost on the far-end XTC card (within a DS3). Signal loss also causes the "LOS (OCN)" alarm on page 2-99.

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 an XTC card in Slot 5 of Node 1 could link to an alarm from an XTC card in Slot 6 of Node 2.

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

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

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

2.7.85  FE-DS3-NSA

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

Logical Object: DS3

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

Clear the FE-DS3-NSA Condition

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

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

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

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

2.7.86  FE-DS3-SA

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

Logical Object: DS3

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

Clear the FE-DS3-SA Condition

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

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

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

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

2.7.87  FE-EQPT-NSA

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

Logical Object: DS3

The Far End Common Equipment Failure condition occurs when a Non-Service-Affecting (NSA) equipment failure is detected on far-end XTC card equipment.

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 an XTC card in Slot 5 of Node 1 could relate to a main alarm from an XTC card in Slot 6 of Node 2.

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

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

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

2.7.88  FE-FRCDWKSWBK-SPAN

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

Logical Object: OCN

The Far End Forced Switch Back to Working-Span condition is raised on a far-end 1+1 protect port when it is Force-switched to the working port.

Note WKSWBK-type conditions apply only to nonrevertive circuits.

Clear the FE-FRCDWKSWBK-SPAN Condition

Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure for the far-end port.

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

2.7.89  FE-FRCDWKSWPR-RING

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

Logical Object: OCN

The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a BLSR is forced from working to protect using the Force Ring command. This condition is only visible on the network view Conditions tab.

Clear the FE-FRCDWKSWPR-RING Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 2 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 3 of Node 2.

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

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-RING condition does not clear, complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.90  FE-FRCDWKSWPR-SPAN

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

Logical Object: OCN

The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber BLSR is forced from working to protect using the Force Span command. This condition is only visible on the network view Conditions tab. The port where the Force Switch occurred is indicated by an "F" on the network view detailed circuit map. This condition is accompanied by WKSWPR.

Clear the FE-FRCDWKSWPR-SPAN Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 2 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 3 of Node 2.

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

Step 3 Clear the main alarm.

Step 4 If the FE-FRCDWKSWPR-SPAN condition does not clear, complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.91  FE-IDLE

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

Logical Object: DS3

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

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 3 of Node 1 could relate to a main alarm from a card in Slot 4 of Node 2.

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

Step 3 Clear the main alarm by clearing the protection switch. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

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

2.7.92  FE-LOCKOUTOFPR-SPAN

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

Logical Object: OCN

The Far-End Lock Out of Protection Span condition occurs when a BSLR span is locked out of the protection system from a far-end node using the Lockout Protect Span command. This condition is only seen on the network view Conditions tab and is accompanied by LKOUTPR-S. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

Clear the FE-LOCKOUTOFPR-SPAN Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 3 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 4 of Node 2.

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

Step 3 Ensure there is no lockout set. Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.93  FE-LOF

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

Logical Object: DS3

The Far End LOF condition occurs when a far-end node reports an "LOF (DS3)" alarm on page 2-92.

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 3 of Node 1 could relate to a main alarm from a card in Slot 4 of Node 2.

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

Step 3 Complete the "Clear the LOF (DS3) Alarm" procedure. It also applies to FE-LOF.

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

2.7.94  FE-LOS

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

Logical Object: DS3

The Far End LOS condition occurs in C-bit framing mode when a far-end node reports the "LOS (DS3)" alarm on page 2-99.

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 5 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.

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

Step 3 Complete the "Clear the LOS (DS1) Alarm" procedure.

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

2.7.95  FE-MANWKSWBK-SPAN

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

Logical Object: OCN

The Far End Manual Switch Back to Working-Span condition occurs when a far-end span is Manual switched back to working.

Note WKSWBK-type conditions apply only to nonrevertive circuits.

Clear the FE-MANWKSWBK-SPAN Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 2 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 3 of Node 2.

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

Step 3 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.96  FE-MANWKSWPR-RING

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

Logical Object: OCN

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

Clear the FE-MANWKSWPR-RING Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 3 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 4 of Node 2.

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

Step 3 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.97  FE-MANWKSWPR-SPAN

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

Logical Object: OCN

The Far-End Span Manual Switch Working Facility to Protect condition occurs when a four-fiber BLSR span is switched from working to protect at the far-end node using the Manual Span command. This condition is only visible on the network view Conditions tab and is accompanied by WKSWPR. The port where the Manual switch occurred is indicated by an "M" on the network view detailed circuit map.

Clear the FE-MANWKSWPR-SPAN Condition

Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 4 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 4 of Node 2.

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

Step 3 Complete the "Clear a BLSR External Switching Command" alarm on page 2-160.

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

2.7.98  FEPRLF

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

Logical Object: OCN

The Far End Protection Line Failure alarm occurs when an APS channel "SF-L" condition on page 2-128 occurs on the protect card coming into the node.

Note The FEPRLF alarm occurs when bidirectional protection is used on optical (traffic) cards in a 1+1 protection group configuration.

Clear the FEPRLF Alarm on a BLSR

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

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

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

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

2.7.99  FORCED-REQ

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

Logical Objects: EQPT, STSMON, VT-MON

The Force Switch Request on Facility or Port condition occurs when you enter the Force command on a port to force traffic from a working port to a protect port or protection span (or from a protect port to a working port or span). You do not need to clear the condition if you want the Force switch to remain.

Clear the FORCED-REQ Condition

Step 1 Complete the "Clear a 1+1 Protection Port Force or Manual Switch Command" procedure.

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

2.7.100  FORCED-REQ-RING

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

Logical Object: OCN

The Force Switch Request Ring condition applies to optical trunk cards when the Force Ring command is applied to BLSRs to move traffic from working to protect. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the FORCE RING command originated is marked with an "F" on the network view detailed circuit map.

Clear the FORCED-REQ-RING Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.101  FORCED-REQ-SPAN

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

Logical Objects: OCN

The Force Switch Request Span condition applies to optical trunk cards in two-fiber or four-fiber BLSRs when the Force Span command is applied to a BLSR SPAN to force traffic from working to protect or from protect to working. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the FORCE SPAN command was applied is marked with an "F" on the network view detailed circuit map.

This condition can also be raised in 1+1 facility protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.

This condition can also be raised in 1+1 facility protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by "FORCED TO WORKING"), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.

Clear the FORCED-REQ-SPAN Condition

Step 1 Complete the "Clear a Path Protection Span External Switching Command" procedure.

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

2.7.102  FRCDSWTOINT

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

Logical Object: NE-SREF

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

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

2.7.103  FRCDSWTOPRI

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

Logical Objects: EXT-SREF, NE-SREF

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

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

2.7.104  FRCDSWTOSEC

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

Logical Objects: EXT-SREF, NE-SREF

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

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

2.7.105  FRCDSWTOTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

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

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

2.7.106  FRNGSYNC

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

Logical Object: NE-SREF

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

Note If the ONS 15327 is configured to operate from its internal clock, disregard the FRNGSYNC condition.

Clear the FRNGSYNC Condition

Step 1 If the ONS 15327 is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the "Timing" chapter in the Cisco ONS 15327 Reference Manual for more information about timing and the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide for wiring procedures.

Step 2 If the BITS source is valid, clear alarms related to the failures of the primary and secondary reference sources, such as the "SYNCPRI" alarm on page 2-140 and the "SYNCSEC" alarm on page 2-141.

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

2.7.107  FSTSYNC

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

Logical Object: NE-SREF

A Fast Start Synchronization Mode condition occurs when the ONS 15327 is choosing a new timing reference. The previous timing reference has failed.

The FSTSYNC condition disappears after approximately 30 seconds. If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

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

2.7.108  FULLPASSTHR-BI

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

Logical Object: OCN

The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are active and carrying traffic and there is a change in the receive K byte from No Request.

Clear the FULLPASSTHR-BI Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.109  HELLO

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

Logical Object: OCN

The Open Shortest Path First (OSPF) Hello alarm is raised when the two end nodes cannot bring an OSPF neighbor up to the full state. Typically, this problem is caused by an area ID mismatch, and/or an OSPF HELLO packet loss over the DCC.

Clear the HELLO Alarm

Step 1 Ensure that the area ID is correct on the missing neighbor by completing the following steps:

a. In node view, click the Provisioning > Network > OSPF tabs.

b. Ensure that the IP address in the Area ID column matches the other nodes.

c. If the address does not match, click the incorrect cell and correct it.

d. Click Apply.

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

2.7.110  HIBATVG

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

Logical Object: PWR

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

Clear the HIBATVG Alarm

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

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.111  HI-LASERBIAS

The HI-LASERBIAS condition is not used in this platform in this release. It is reserved for development.

2.7.112  HI-LASERTEMP

The HI-LASERTEMP condition is not used in this platform in this release. It is reserved for development.

2.7.113  HI-RXPOWER

The HI-RXPOWER condition is not used in this platform in this release. It is reserved for development.

2.7.114  HITEMP

Default Severity: Critical (CR), Service-Affecting (SA) for NE; Minor (MN), Non-Service-Affecting (NSA) for EQPT

Logical Objects: EQPT, NE

The High Temperature alarm occurs when the temperature of the ONS 15327 is above 122 degrees F (50 degrees C).

Clear the HITEMP Alarm

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

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

Step 3 If air flow is not blocked, physically ensure that blank faceplates fill the ONS 15327 shelf empty slots. Blank faceplates help air flow.

Step 4 If faceplates fill the empty slots, determine whether the air filter needs replacement. Refer to the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Note The fan should run immediately when correctly inserted.

Step 6 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.7.115  HI-TXPOWER

The HI-TXPOWER condition is not used in this platform in this release. It is reserved for development.

2.7.116  HLDOVRSYNC

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

Logical Object: NE-SREF

The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15327 relying on an internal clock.

Clear the HLDOVRSYNC Condition

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

•SYNCTHIRD

Step 2 Reestablish a primary and secondary timing source according to local site practice. If none exists, refer to the "Change Node Settings" chapter in the Cisco ONS 15327 Procedure Guide for procedures.

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

2.7.117  I-HITEMP

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

Logical Object: NE

The Industrial High Temperature alarm occurs when the temperature of the ONS 15327 is above 149 degrees F (65 degrees C) or below -40 degrees F (-40 degrees C). This alarm is similar to the HITEMP alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.

Clear the I-HITEMP Alarm

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

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

2.7.118  IMPROPRMVL

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

Logical Object: EQPT

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. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node. It can also occur if the card is inserted into a slot but is not fully plugged into the backplane.

Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot. When you delete the card, CTC loses connection with the node view and goes to network view.

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

Clear the IMPROPRMVL (EQPT) Alarm

Step 1 In node view, right-click the card reporting the IMPROPRMVL alarm.

Step 2 Choose Delete from the shortcut menu.

Note CTC does not allow you to delete the reporting card if the card is in service, has a circuit mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.

Step 3 If any ports on the card are in service, place them out of service (OOS,MT) by completing the following steps:

Caution Before placing a port out of service (OOS,MT or OOS,DSBLD), ensure that no live traffic is present.

a. In node view, double-click the reporting card to display the card view.

b. Click the Provisioning > Line tabs.

c. Click the Admin State column of any in-service (IS) ports.

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

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

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

Step 5 If the card is paired in a protection scheme, delete the protection group by completing the following steps:

a. Click View > Go to Previous View to return to node view.

b. If you are already in node view, click the Provisioning > Protection tabs.

c. Click the protection group of the reporting card.

d. Click Delete.

Step 6 If the card is provisioned for DCC, delete the DCC provisioning by completing the following steps:

a. Click the ONS 15327 Provisioning > Comm Channels > SDCC tabs.

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

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

Step 7 If the card is used as a timing reference, change the timing reference by completing the following steps:

a. Click the Provisioning > Timing > General tabs.

b. Under NE Reference, click the drop-down list for Ref-1.

c. Change Ref-1 from the listed OC-N card to Internal Clock.

d. Click Apply.

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.119  INC-ISD

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

Logical Object: DS3

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

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

2.7.120  INCOMPATIBLE-SEND-PDIP

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

Logical Object: SYSTEM

The Incompatible Send-PDIP alarm is raised when CTC's send-PDIP provisioning differs from host node's send-PDIP provisioning.

Clear the INCOMPATIBLE-SEND-PDIP Alarm

Step 1 Reconfigure CTC's send-PDI-P alarm capability to align with the host node settings.

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

2.7.121  INCOMPATIBLE-SW

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

Logical Object: SYSTEM

The Incompatible Software alarm is raised when CTC cannot connect to the NE due to incompatible versions of software between CTC and the NE. The alarm is cleared by restarting CTC in order to download the CTC JAR files again from the NE.

Clear the INCOMPATIBLE-SW Alarm

Step 1 Restart the CTC application.

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

2.7.122  INHSWPR

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

Logical Object: EQPT

The Inhibit Switch To Protect Request on Equipment condition occurs on traffic cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.

Clear the INHSWPR Condition

Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" section.

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

2.7.123  INHSWWKG

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

Logical Object: EQPT

The Inhibit Switch To Working Request on Equipment condition occurs on traffic cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the protect system. If the card is part of a 1:N protection scheme, traffic can be switched between protect cards when the switch to working is disabled.

Clear the INHSWWKG Condition

Step 1 If the condition is raised against a 1+1 port, complete the "Initiate a 1+1 Protection Port Manual Switch Command" section.

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

2.7.124  INTRUSION-PSWD

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

Logical Object: NE

The Security Intrusion Incorrect Password condition occurs after a user attempts a settable (by Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not in login sessions for lower-level users. The INTRUSION-PSWD condition is automatically cleared when a settable lockout timeout expires, or it can be manually cleared in CTC by the Superuser if lockout is permanent.

Clear the INTRUSION-PSWD Condition

Step 1 Click the Provisioning > Security > Users tabs.

Step 2 Click Clear Security Intrusion Alarm.

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

2.7.125  ISIS-ADJ-FAIL

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

Logical Object: OCN

The Open System Interconnection (OSI) Intermediate System to Intermediate-System (IS-IS) Adjacency Failure alarm is raised by an intermediate system (node routing IS Level 1 or Level 1 and 2) when no IS or end system (ES) adjacency is established on a point-to-point subnet. The Intermediate-System Adjacency Failure alarm is not raised by ES. It is also not raised by IS for disabled routers.

The alarm is typically caused by a misconfigured router manual area adjacency (MAA) address. For more information about IS-IS OSI routing and Manual Area Address (MAA) configuration, refer to the "Management Network Connectivity" chapter in the Cisco ONS 15327 Reference Manual. For more information about configuring OSI, refer to the "Turn Up Node" chapter in the Cisco ONS 15327 Procedure Guide.

Clear the ISIS-ADJ-FAIL Alarm

Step 1 Ensure that both ends of the communication channel are using the correct Layer 2 protocol and settings (LAPD or PPP). To do this, complete the following steps:

a. At the local node, in node view, click the Provisioning > Comm Channels > SDCC tabs.

b. Click the row of the circuit. Click Edit.

c. In the Edit SDCC termination dialog box, view and record the following selections: Layer 2 protocol (LAPD or PPP); Mode radio button selection (AITS or UITS); Role radio button selection (Network or User); MTU value; T200 value; and T203 selections.

d. Click Cancel.

e. Log into the remote node and follow the same steps, also recording the same information for this node.

Step 2 If both nodes do not use the same Layer 2 settings, you will have to delete the incorrect termination and recreate it. To delete it, click the termination and click Delete. To recreate it, refer to the "Turn Up Node" chapter in the Cisco ONS 15327 Procedure Guide for the procedure.

Step 3 If the nodes use Point-to-Point Protocol (PPP) Layer 2, complete the "Clear the EOC Alarm" procedure. If the alarm does not clear, go to Step 7.

Step 4 If both nodes use the ISDN Link Access Protocol-Channel D (LAPD) Layer 2 protocol but have different Mode settings, change the incorrect node's entry by clicking the correct setting radio button in the Edit SDCC termination dialog box and clicking OK.

Step 5 If the Layer 2 protocol and Mode settings are correct, ensure that one node is using the Network role and the other has the User role. If not (that is, if both have the same mode settings), correct the incorrect one by clicking the correct radio button in the Edit SDCC termination dialog box and clicking OK.

Step 6 If the Layer 2, Mode, and Role settings are correct, compare the MTU settings for each node. If one is incorrect, choose the correct value in the Edit SDCC dialog box and click OK.

Step 7 If all of the preceding settings are correct, ensure that OSI routers are enabled for the communication channels at both ends by completing the following steps:

a. Click the Provisioning > OSI > Routers > Setup tabs.

b. View the router entry under the Status column. If the status is Enabled, check the other end.

c. If the Status is Disabled, click the router entry and click Edit.

d. Check the Enabled check box and click OK.

Step 8 If the routers on both ends are enabled and the alarm still has not cleared, ensure that both ends of the communications channel have a common MAA by completing the following steps:

a. Click the Provisioning > OSI > Routers > Setup tabs.

b. Record the primary MAA and secondary MAAs, if configured.

Tip You can record long strings of information such as the MAA address by using the CTC export and print functions. Export it by choosing File > Export > html. Print it by choosing File > Print.

c. Log into the other node and record the primary MAA and secondary MAAs, if configured.

d. Compare this information. There should be at least one common primary or secondary MAA in order to establish an adjacency.

e. If there is no common MAA, one must be added to establish an adjacency. Refer to the "Turn Up Node" chapter in the Cisco ONS 15327 Procedure Guide for procedures to do this.

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

2.7.126  KB-PASSTHR

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

Logical Object: OCN

The K Byte Pass Through Active condition occurs on a nonswitching node in a BLSR when the protect channels on the node are not active and the node is in K Byte pass-through state. It also occurs when a BLSR ring is being exercised using the Exercise Ring command.

Clear the KB-PASSTHR Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.127  KBYTE-APS-CHANNEL-FAILURE

The KBYTE-APS-CHANNEL-FAILURE alarm is not used in this platform in this release. It is reserved for development.

2.7.128  LAN-POL-REV

The LAN-POL-REV alarm is not used in this platform in this release. It is reserved for development.

2.7.129  LASEREOL

The LASEREOL alarm is not used in this platform in this release. It is reserved for development.

2.7.130  LCAS-CRC

The LCAS-CRC alarm is not used in this platform in this release. It is reserved for development.

2.7.131  LCAS-RX-FAIL

The LCAS-RX-FAIL alarm is not used in this platform in this release. It is reserved for development.

2.7.132  LCAS-TX-ADD

The LCAS-TX-ADD alarm is not used in this platform in this release. It is reserved for development.

2.7.133  LCAS-TX-DNU

The LCAS-TX-DNU alarm is not used in this platform in this release. It is reserved for development.

2.7.134  LKOUTPR-S

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

Logical Object: OCN

The Lockout of Protection Span condition occurs when span traffic is locked out of a protect span using the Lockout of Protect command. This condition is visible on the network view Alarms, Conditions, and History tabs after the lockout has occurred and accompanies the FE-LOCKOUTPR-SPAN condition. The port where the lockout originated is marked by an "L" on the network view detailed circuit map.

Clear the LKOUTPR-S Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.135  LOCKOUT-REQ

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

Logical Objects: EQPT, OCN, STSMON, VT-MON

The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a lockout switch request for an OC-N port in a 1+1 facility protection group. This can be accomplished by locking traffic onto the working port with the LOCK ON command (thus locking it off the protect port), or locking it off the protect port with the LOCK OUT command. In either case, the protect port will show "Lockout of Protection," and the Conditions window will show the LOCKOUT-REQ condition.

A lockout prevents protection switching. Clearing the lockout again allows protection switching and clears the LOCKOUT-REQ condition.

Clear the LOCKOUT-REQ Condition

Step 1 Complete the "Clear a Card or Port Lock-On or Lockout Command" procedure.

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

2.7.136  LOF (BITS)

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

Logical Object: BITS

The Loss of Frame (LOF) BITS alarm occurs when a port on the XTC card BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15327 has lost frame delineation in the incoming data.

Note The procedure assumes that the BITS timing reference signal is functioning properly. It also assumes that the alarm is not appearing during node turn-up.

Clear the LOF (BITS) Alarm

Step 1 Verify that the line framing and line coding match between the BITS input and the XTC card by completing the following steps:

a. In node view or card view, note the slot and port reporting the alarm.

b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.

c. Click the Provisioning > Timing > BITS Facilities tabs.

d. Verify that the Coding setting matches the coding of the BITS timing source, either B8ZS or AMI.

e. If the coding does not match, click Coding and choose the appropriate coding from the drop-down list.

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 and choose the appropriate framing from the drop-down list.

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 XTC card, complete the "Physically Replace a Card" procedure for the XTC card.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.137  LOF (DS1)

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

Logical Object: DS1

The DS-1 LOF alarm indicates that the receiving ONS 15327 has lost frame delineation in an incoming DS-1 data stream or the transmitting equipment could have its framing set to a format that differs from the receiving ONS 15327.

Clear the LOF (DS1) Alarm

Step 1 Verify that the line framing and line coding match between the XTC card port and the signal source by completing the following steps:

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

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

c. Display the card view of the reporting XTC card.

d. Click the Provisioning > DS1 > Line tabs.

e. Verify that the line type of the reporting port matches the line type of the signal source (DS4 and DS4, unframed and unframed, or ESF and ESF). If the signal source line type does not match the reporting port, click the Line Type cell to reveal a drop-down list and choose the matching type.

f. Verify that the reporting Line Coding matches the signal source's line coding (AMI and AMI or B8ZS and B8ZS).

g. If the signal source line coding does not match the reporting port, click the Line Coding cell and choose the correct type from the drop-down list.

h. Click Apply.

Note On the DS-1 Line tab, the B8ZS coding field is normally paired with ESF in the Line Type field. AMI coding is normally paired with D4 in the Line Type field.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.138  LOF (DS3)

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

Logical Object: DS3

The DS-3 LOF alarm indicates that the receiving ONS 15327 has lost frame delineation in the incoming DS-3 data stream. The framing of the transmitting equipment could be set to a format that differs from the receiving ONS 15327. On XTC-28-3 cards, the alarm occurs only on DS-1 lines with the provisionable framing format set to SF (D4) and not on cards with the provisionable framing format set to unframed.

Clear the LOF (DS3) Alarm

Step 1 Complete the "Clear the LOF (DS1) Alarm" procedure.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.139  LOF (OCN)

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

Logical Object: OCN

The LOF alarm occurs when a port on the reporting card has an LOF condition. The alarm indicates that the receiving ONS 15327 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.

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

Clear the LOF (OCN) Alarm

Step 1 Verify cabling continuity to the port reporting the alarm. To verify cable continuity, follow site practices.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 2 If cabling continuity is good, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 Procedure Guide.

Step 3 If the alarm does not clear, see the "Troubleshooting Circuit Paths with Loopbacks" section to isolate the fault causing the LOF alarm.

Step 4 If the alarm does not clear, or if you need assistance conducting network troubleshooting tests, call Cisco TAC to report a Service-Affecting (SA) problem (1-800-553-2447).

2.7.140  LOF (STSTRM)

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

Logical Object: STSTRM

A Loss of Frame alarm for an STS circuit termination indicates that the LOF has occurred at the terminating point of the circuit (such as an OC-N port). It is similar to the "LOF (OCN)" alarm on page 2-93.

Clear the LOF (STSTRM) Alarm

Step 1 Complete the "Clear the LOF (OCN) Alarm" alarm on page 2-93.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.141  LOGBUFR90

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

Logical Object: SYSTEM

The Log Buffer Over 90 alarm indicates that the per-NE queue of incoming alarm, event, or update capacity of 5000 entries is over 90 percent full. LOGBUFR90 will clear if CTC recovers. If it does not clear, LOGBUFROVFL occurs.

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

2.7.142  LOGBUFROVFL

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

Logical Object: SYSTEM

The Log Buffer Overflow alarm indicates that the CTC per-NE queue of incoming alarm, event, or updates, which has a capacity of 5000 entries, has overflowed. This happens only very rarely; however if it happens, you must restart the CTC session. It is likely that some updates will have been missed if this alarm occurs.

Clear the LOGBUFROVFL Alarm

Step 1 Restart the CTC session.

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

2.7.143  LO-LASERBIAS

The LO-LASERBIAS condition is not used in this platform in this release. It is reserved for development.

2.7.144  LO-LASERTEMP

The LO-LASERTEMP condition is not used in this platform in this release. It is reserved for development.

2.7.145  LOM

Default Severity: Critical (CR), Service-Affecting (SA) for STSMON, STSTRM; Major (MJ) for VT-TERM

Logical Objects: STSMON, STSTRM, VT-TERM

The Optical Transport Unit (OTU) Loss of Multiframe is a VCAT member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm applies when the Multi Frame Alignment Signal (MFAS) overhead field is errored for more than five frames and persists for more than 3 milliseconds.

Clear the LOM Alarm

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.146  LOP-P

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

Logical Objects: STSMON, STSTRM

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

The LOP-P alarm can occur when the received payload does not match the provisioned payload. The alarm is caused by a circuit type mismatch on the concatenation facility. For example, if an STS-1 is sent across a circuit provisioned for STS-3c, an LOP-P alarm occurs.

Clear the LOP-P Alarm

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

Step 2 Verify the circuit size listed in the Size column. If the size is different from what is expected, such as an STS-3c instead of an STS-1, this causes the alarm.

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

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 4 If the error is not due to an incorrectly configured test set, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.

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

Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.147  LOP-V

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

Logical Objects: VT-MON, VT-TERM

The LOP VT alarm indicates a loss of pointer at the VT level. The LOP-V alarm can occur when the received payload does not match the provisioned payload. LOP-V is caused by a circuit size mismatch on the concatenation facility.

Clear the LOP-V Alarm

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

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

2.7.148  LO-RXPOWER

The LO-RXPOWER condition is not used in this platform in this release. It is reserved for development.

2.7.149  LOS (BITS)

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

Logical Object: BITS

The LOS (BITS) alarm indicates that the XTC card has an LOS from the BITS timing source. The LOS (BITS-N) means the BITS clock or the connection to it failed.

Clear the LOS (BITS) Alarm

Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15327 MIC card to the timing source.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 2 If wiring is good, verify that the BITS clock is operating properly.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.150  LOS (DS1)

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

Logical Object: DS1

A LOS (DS1) alarm for a DS-1 port occurs when the port on the card is in service but no signal is being received. A cabling issue or a configuration issue could cause this alarm. If an upstream equipment failure causes a transmission failure, the LOS (DS1) will likely be demoted by a card-level alarm.

Clear the LOS (DS1) Alarm

Step 1 Verify that the cable is properly connected and attached from the correct transmitting port to the correct receiving port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

If an optical TDM signal such as an OC-3 or OC-12 is plugged into an E1000 or G1000 card GBIC connector, this can trigger an LOS.

Step 2 Consult site records to determine whether the port raising the alarm has been assigned.

Step 3 If the port is not currently assigned, place the port out of service using the following steps:

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

b. For a DS-1 port, click the Maintenance > DS1 > Loopback tabs. For a DS-3 port, click the Maintenance > DS3 > Loopback tabs.

c. Under Admin State, click OOS,DSBLD.

d. Click Apply.

Step 4 If the port is assigned, verify that the correct port is in service by completing the following steps:

a. To confirm this physically, confirm that the card shows a green LED on the physical card.

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

b. To determine this virtually, double-click the card in CTC to display the card view and complete the following substeps:

•Click the Provisioning > DS1 > Line tabs or the Provisioning > DS3 > Line tabs.

•Verify that the Admin State column lists the port as IS.

•If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS. Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. For specific procedures to use the test set equipment, consult the manufacturer.

Step 6 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected. For more information about cable connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.

Step 7 If there is a valid signal, replace the electrical connector on the ONS 15327.

Step 8 If a valid signal is not present and the transmitting device is operational, replace the cable connecting the transmitting device to the port. To do this, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.

Step 9 Repeat Steps 1 to 8 for any other port on the card that reports the LOS.

Step 10 If no other alarms are present that could be the source of the LOS (DS1), or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Card" procedure for the reporting card.

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

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

Step 11 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.151  LOS (DS3)

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

Logical Object: DS3

The LOS for a DS-3 port alarm occurs when the port on the card is in service but no signal is being received.The alarm is caused by incorrect or dirty cabling, a break, upstream equipment failure, or incorrect port provisioning.

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

Clear the LOS (DS3) Alarm

Step 1 Complete the "Clear the LOS (DS1) Alarm" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.152  LOS (OCN)

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

Logical Object: OCN

An LOS alarm on an OC-N port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS alarm means that 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. It clears when two consecutive valid frames are received.

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

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

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

Clear the LOS (OCN) Alarm

Step 1 Verify fiber continuity to the port. To verify cable continuity, follow site practices.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 2 If the cabling is okay, verify that the correct port is in service by completing the following steps:

a. Confirm that the LED is correctly illuminated on the physical card.

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

b. To determine whether the 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 Admin State column lists the port as IS.

e. If the Admin State column lists the port as OOS,MT or OOS,DSBLD, click the column and choose IS.

f. Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Step 3 If the correct port is in service, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 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 receiver specifications. The "Optical Card Transmit and Receive Levels" section lists these specifications for each OC-N card.

Step 5 If the 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 to 6 for any other port on the card reporting the LOS (OC-N).

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

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

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

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

Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.153  LO-TXPOWER

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.154  LPBKCRS

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

Logical Objects: STSMON, STSTRM

The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between an optical card and an XTC card. A cross-connect loopback test occurs below line speed and does not affect traffic.

For more information on loopbacks, see the "Troubleshooting Electrical Circuit Paths with Loopbacks" section.

Note Cross-connect loopbacks occur below line speed. They do not affect traffic.

Clear the LPBKCRS Condition

Step 1 To remove the loopback cross-connect condition, double-click the optical card in CTC to display the card view.

Step 2 Complete the "Clear an OC-N Card XC Loopback Circuit" procedure.

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

2.7.155  LPBKDS1FEAC-CMD

The LPBKDS1FEAC-CMD alarm is not used in this platform in this release. It is reserved for development.

2.7.156  LPBKDS3FEAC

The LPBKDS3FEAC alarm is not used in this platform in this release. It is reserved for development.

2.7.157  LPBKDS3FEAC-CMD

The LPBKDS3FEAC-CMD alarm is not used in this platform in this release. It is reserved for development.

2.7.158  LPBKFACILITY (DS1, DS3)

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

Logical Objects: DS1, DS3

A Loopback Facility condition for a DS-1 or DS-3 signal occurs when a software facility (line) loopback is active for a DS-1 or DS-3 port on the reporting XTC card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Troubleshooting Electrical Circuit Paths with Loopbacks" section. Facility loopbacks are described in the "Troubleshooting Circuit Paths with Loopbacks" section.

Note CTC permits loopbacks to be performed on an in-service (IS) circuit. Performing a loopback is Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the LPBKFACILITY condition can be accompanied by a more serious alarms such as LOS.

Note DS-3 facility (line) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted to the loopback is provided.

Clear the LPBKFACILITY (DS1, DS3) Condition

Step 1 Complete the "Clear an XTC Card DS-1 or DS-3 Loopback Circuit" procedure.

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

2.7.159  LPBKFACILITY (G1000)

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

Logical Object: G1000

A Loopback Facility condition for the G1000 object occurs when a software facility (line) loopback is active for a port on the reporting G1000-2 Ethernet card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Troubleshooting Optical Circuit Paths with Loopbacks" section. Facility loopbacks are described in the "Troubleshooting Circuit Paths with Loopbacks" section.

Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

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

Clear the LPBKFACILITY (G1000) Condition

Step 1 Complete the "Clear a G1000 Card Loopback" procedure.

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

2.7.160  LPBKFACILITY (OCN)

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

Logical Object: OCN

A Loopback Facility condition for an OC-N signal occurs when a software facility (line) loopback is active for a port on the reporting OC-N card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Troubleshooting Optical Circuit Paths with Loopbacks" section.

Note OC-3 facility loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted to the loopback is provided.

Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

Note Before performing a facility (line) loopback on an OC-N card, ensure the card contains at least two DCC paths to the node where the card is installed. A second DCC path provides a nonlooped path to log into the node after the loopback is applied, thus enabling you to remove the facility loopback. Ensuring a second DCC is not necessary if you are directly connected to the ONS 15327 containing the loopback OC-N.

Clear the LPBKFACILITY (OCN) Condition

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

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

2.7.161  LPBKTERMINAL (DS1, DS3)

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

Logical Objects: DS1, DS3

A Loopback Terminal condition for a DS-1 or DS-3 signal occurs when a software terminal (inward) loopback is active for a DS-1 or DS-3 port on the reporting XTC card. DS-1 and DS-3 terminal loopbacks do not typically return an AIS signal.

For information about troubleshooting optical circuits with loopbacks, refer to the "Troubleshooting Electrical Circuit Paths with Loopbacks" section. Facility loopbacks are described in the "Troubleshooting Circuit Paths with Loopbacks" section.

Clear the LPBKTERMINAL (DS1, DS3) Condition

Step 1 Complete the "Clear an XTC Card DS-1 or DS-3 Loopback Circuit" procedure.

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

2.7.162  LPBKTERMINAL (G1000)

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

Logical Object: G1000

A Loopback Terminal condition for the G1000 object occurs when a software terminal (inward) loopback is active for a port on the reporting G1000-2 Ethernet card.

When a port in terminal (inward) loopback, its outgoing signal is redirected into the receive direction on the same port, and the externally received signal is ignored. On the G-Series card, the outgoing signal is not transmitted; it is only redirected in the receive direction.

For more information about troubleshooting optical circuits, refer to the "Troubleshooting Electrical Circuit Paths with Loopbacks" section. Terminal loopbacks are described in the "Troubleshooting Circuit Paths with Loopbacks" section.

Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

Clear the LPBKTERMINAL (G1000) Condition

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

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

2.7.163  LPBKTERMINAL (OCN)

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

Logical Object: OCN

A Loopback Terminal condition for an OC-N occurs when a software terminal (inward) loopback is active for a port on the reporting card.

Note OC-N terminal loopbacks do not typically return an AIS.

Note DS-3 terminal (inward) loopbacks do not transmit an in the direction away from the loopback. Instead of an AIS, a continuance of the signal transmitted to the loopback is provided.

Note Performing a loopback on an in-service circuit is Service-Affecting (SA). If you did not perform a lockout or Force switch to protect traffic, the LPBKTERMINAL condition can also be accompanied by a more serious alarm such as LOS.

For information about troubleshooting electrical circuits with loopbacks, refer to the "Troubleshooting Electrical Circuit Paths with Loopbacks" section; for optical circuits, refer to the "Troubleshooting Optical Circuit Paths with Loopbacks" section. Terminal loopbacks are described in the "Troubleshooting Circuit Paths with Loopbacks" section.

Clear the LPBKTERMINAL (OCN) Condition

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

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

2.7.164  LWBATVG

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

Logical Object: PWR

The Low Voltage Battery alarm occurs in a -48 VDC environment when a battery lead input voltage falls below the low power threshold. This threshold, with a default value of -44 VDC, is user-provisionable. The alarm remains raised until the voltage remains above the threshold for 120 seconds. (For information about changing this threshold, refer to the "Turn Up Node" chapter in the Cisco ONS 15327 Procedure Guide.)

Clear the LWBATVG Alarm

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

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.165  MAN-REQ

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

Logical Objects: EQPT, STSMON, VT-MON

The Manual Switch Request condition occurs when a user initiates a Manual switch request on an OC-N port. Clearing the Manual switch clears the MAN-REQ condition. You do not need to clear the switch if you want the manual switch to remain.

Clear the MAN-REQ Condition

Step 1 Complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

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

2.7.166  MANRESET

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

Logical Object: EQPT

A User-Initiated Manual Reset condition occurs when you right-click a card in CTC and choose Reset. Resets performed during a software upgrade also prompt the condition. The MANRESET condition clears automatically when the card finishes resetting.

Note MANRESET is an informational condition and does not require troubleshooting.

2.7.167  MANSWTOINT

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

Logical Object: NE-SREF

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

Note MANSWTOINT is an informational condition and does not require troubleshooting.

2.7.168  MANSWTOPRI

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

Logical Objects: EXT-SREF, NE-SREF

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

Note MANSWTOPRI is an informational condition and does not require troubleshooting.

2.7.169  MANSWTOSEC

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

Logical Objects: EXT-SREF, NE-SREF

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

Note MANSWTOSEC is an informational condition and does not require troubleshooting.

2.7.170  MANSWTOTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

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

Note MANSWTOTHIRD is an informational condition and does not require troubleshooting.

2.7.171  MANUAL-REQ-RING

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

Logical Object: OCN

The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on BLSR rings to switch from working to protect or protect to working. This condition is visible on the network view Alarms, Conditions, and History tabs and is accompanied by WKSWPR. The port where the MANUAL RING command originated is marked with an "M" on the network view detailed circuit map.

Clear the MANUAL-REQ-RING Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.172  MANUAL-REQ-SPAN

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

Logical Object: OCN

The Manual Switch Request on Ring condition occurs on BLSRs when a user initiates a Manual Span command to move BLSR traffic from a working span to a protect span. This condition appears on the network view Alarms, Conditions, and History tabs. The port where the MANUAL SPAN command was applied is marked with an "M" on the network view detailed circuit map.

Clear the MANUAL-REQ-SPAN Condition

Step 1 Complete the "Clear a BLSR External Switching Command" procedure.

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

2.7.173  MEA (EQPT)

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

Logical Object: EQPT

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. Removing the incompatible cards clears the alarm.

Clear the MEA (EQPT) Alarm

Step 1 Physically verify the type of card that sits in the slot reporting the MEA alarm. In node view, click the Inventory tab, then compare it with what is actually installed.

Step 2 If you prefer the card type depicted by CTC, complete the "Physically Replace a Card" procedure for the reporting card.

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

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

Step 3 If you prefer the card that physically occupies the slot and the card is not in service, does not have circuits mapped to it, and is not part of a protection group, place the cursor over the provisioned card in CTC, right-click, and choose Delete Card from the shortcut menu.

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, does have circuits mapped to it, is paired in a working protection scheme, has DCC communications turned on, or is used as a timing reference, CTC does not allow you to delete the card.

Step 4 If any ports on the card are in service, place them out of service (OOS) by completing the following steps:

Caution Before placing ports out of service, ensure that live traffic is not present.

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

b. Click the Provisioning tab.

c. Click the Admin State of any in-service (IS) ports.

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

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

Caution Before deleting the circuit, ensure that live traffic is not present.

Step 6 If the card is paired in a protection scheme, delete the protection group by completing the following steps:

a. Click the Provisioning > Protection tabs.

b. Choose the protection group of the reporting card.

c. Click Delete.

Step 7 Right-click the card reporting the alarm.

Step 8 Choose Delete.

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

Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.174  MEA (FAN)

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

Logical Object: FAN

The MEA alarm is reported against the fan-tray assembly when a fuse failure or mismatch occurs in the fan-tray assembly.

Clear the MEA (FAN) Alarm

Step 1 Obtain a fan-tray assembly with a 5-A fuse and complete the "Replace the Fan-Tray Assembly" procedure.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.175  MEM-GONE

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

Logical Object: EQPT

The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the XTC card. The XTC cards which exceed the memory capacity reboot to avoid failure of card operations.

Note The alarm does not require user intervention. The MEM-LOW alarm always preceeds the MEM-GONE alarm.

2.7.176  MEM-LOW

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

Logical Object: EQPT

The Free Memory of Card Almost Gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the XTC card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the card is exceeded, CTC ceases to function.

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

2.7.177  MFGMEM

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

Logical Objects: BPLANE, FAN

The Manufacturing Data Memory Failure alarm occurs when the electronically erasable programmable read-only memory (EEPROM) fails on a card or component, or when the XTC card cannot read this memory. EEPROM stores manufacturing data that a system XTC card uses to determine system compatibility and shelf inventory status. Unavailability of this information can cause less-significant problems.

Clear the MFGMEM Alarm

Step 1 Complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure.

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

Step 2 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco Technical Support (1-800-553-2447). If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, complete the "Physically Replace a Card" procedure.

Step 3 If the MFGMEM alarm continues to report after replacing the XTC cards, the problem lies with the EEPROM.

Step 4 If the MFGMEM is reported from the fan-tray assembly, obtain a fan-tray assembly and complete the "Replace the Fan-Tray Assembly" procedure.

Step 5 If the MFGMEM alarm persists after the fan-tray assembly is replaced, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco Technical Support (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.7.178  NOT-AUTHENTICATED

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

Logical Object: SYSTEM

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. This alarm differs from the "INTRUSION-PSWD" alarm on page 2-87 in that INTRUSION-PSWD occurs when a user exceeds the login failures threshold.

Note NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.

2.7.179  OOU-TPT

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

Logical Objects: STSTRM, VT-TERM

The Out of Use Transport Failure condition is a VCAT member condition. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) This condition is raised when a member circuit in a VCAT is unused, such as when it is removed by SW-LCAS.

Clear the OOT-TPT Condition

Step 1 Look for and clear any Critical (CR) alarms that apply to the errored card, such as the "LOS (OCN)" alarm on page 2-99.

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

2.7.180  OPTNTWMIS

The OPTNTWMIS alarm is not used in this platform in this release. It is reserved for development.

2.7.181  PDI-P

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

Logical Objects: STSMON, STSTRM

PDI-P is a set of application-specific codes indicating a signal label mismatch failure (SLMF) in the ONS 15327 STS path overhead. The condition indicates to downstream equipment that there is a defect in one or more of the directly mapped payloads contained in that STS synchronous payload envelope (SPE). For example, the mismatch could occur in the overhead to the path selector in a downstream node configured as part of a path protection. The PDI-P codes appear in the STS Signal Label (C2 byte).

An SLMF often occurs when the payload does not match what the signal label is reporting. The "AIS" condition on page 2-18 often accompanies a PDI-P condition. If the PDI-P is the only condition reported with the AIS, clearing PDI-P clears the AIS. PDI-P can also occur during an upgrade, but usually clears itself and is not a valid condition.

A PDI-P condition reported on an OC-N port supporting a G-Series card circuit could result from the end-to-end Ethernet link integrity feature of the G-Series card. If the link integrity is the cause of the path defect, it is typically accompanied by the "TPTFAIL (G1000)" alarm on page 2-144 or the "CARLOSS (G1000)" alarm on page 2-37 reported against one or both Ethernet ports terminating the circuit. If this is the case, clear the TPTFAIL and CARLOSS alarms to resolve the PDI-P condition.

A PDI-P condition reported on an OC-N port supporting an ONS 15327 G-Series card circuit could result from the end-to-end Ethernet link integrity feature of the G-Series card. If the link integrity is the cause of the path defect, it is typically accompanied by the "TPTFAIL (G1000)" alarm on page 2-144 reported against or Ethernet ports terminating the circuit. If this is the case, clear the TPTFAIL and CARLOSS alarms to resolve the PDI-P condition. Refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327 for more information about Ethernet cards.

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

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

Clear the PDI-P Condition

Step 1 Verify that all circuits terminating in the reporting card are in an active state by completing the following steps:

a. Click the Circuits tab.

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

c. If the Status column lists the port as incomplete, wait 10 minutes for the ONS 15327 to initialize fully. If the incomplete state does not change after full initialization, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco Technical Support to report a Service-Affecting (SA) problem (1-800-553-2447).

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

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

Caution Deleting a circuit can affect existing traffic.

Step 4 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15327 Procedure Guide for detailed procedures to create circuits.

Step 5 If the circuit deletion and re-creation does not clear the condition, verify that there is no problem stemming from the far-end OC-N card providing 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 according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 Procedure Guide.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

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

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

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

2.7.182  PEER-NORESPONSE

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

Logical Object: EQPT

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.

Clear the PEER-NORESPONSE Alarm

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

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

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

2.7.183  PLM-P

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

Logical Objects: STSMON, STSTRM

A Payload Label Mismatch Path alarm indicates that signal does not match its label. The condition is indicated by a problematic C2 byte value in the SONET path overhead. The alarm is raised if all of the following conditions are met:

•The received C2 byte is not 0x00 (unequipped).

•The received C2 byte is not a PDI value.

•The received C2 does not match the expected C2.

•The expected C2 byte is not 0x01 (equipped, unspecified).

•The received C2 byte is not 0x01 (equipped, unspecified).

This alarm can occur on the XTC card when the card expects a DS-1 signal but receives a DS-3 signal. The DS-3 signal C2 byte value is 4, so this causes a label mismatch and a PLM-P alarm.

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

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

Clear the PLM-P Alarm

Step 1 Complete the "Clear the PDI-P Condition" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

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

2.7.184  PLM-V

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

Logical Object: VT-TERM

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 15327s interoperate with equipment that performs bit-synchronous mapping for a DS-1 signal. The ONS 15327 uses asynchronous mapping.

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 into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.185  PRC-DUPID

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

Logical Object: OCN

The Procedural Error Duplicate Node ID alarm indicates that two identical node IDs exist in the same ring. The ONS 15327 requires each node in the ring to have a unique node ID.

Clear the PRC-DUPID Alarm

Step 1 Log into a node on the ring.

Step 2 Find the node ID by completing the "Identify an ONS 15327 BLSR Ring Name or Node ID Number" procedure.

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

Step 4 If two nodes have an identical node ID number, complete the "Change an ONS 15327 BLSR Node ID Number" procedure so that each node ID is unique.

Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.186  PROTNA

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

Logical Object: EQPT

The Protection Unit Not Available alarm is caused by an out-of-service (OOS) protection card when a XTC card or XTC card that has been provisioned as part of a protection group is not available. Unavailable protection can occur when a card is reset, but the alarm clears as soon as the card is back in service. The alarm clears if the device or facility is brought back in service.

Clear the PROTNA Alarm

Step 1 If the PROTNA alarm occurs and does not clear, and if it is raised against a controller or cross-connect card, ensure that there is a redundant XTC card installed and provisioned in the chassis.

Step 2 If the alarm is raised against a line card, verify that the ports have been taken out of service (OOS,MT) by completing the following steps:

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

b. Click the Provisioning tab.

c. Click the administrative state of any in-service (IS) ports.

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

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

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

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

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

2.7.187  PWR-FAIL-A

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

Logical Object: EQPT

The Equipment Power Failure at Connector A alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the MIC, XTC card, or OC-N cards.

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

Clear the PWR-FAIL-A Alarm

Step 1 If a single card has reported the alarm and is an active traffic line port in a 1+1 protection group or part of a path protection, ensure that an APS traffic switch has occurred to move traffic to the protect port.

•If the reporting card is an active traffic line port in a 1+1 protection group or part of a path protection, ensure that an APS traffic switch has occurred to move traffic to the protect port.

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

•If the alarm is reported against a XTC card, complete the "Reset an Active XTC Card and Activate the Standby Card" procedure.

•If the alarm is reported against an OC-N card, complete the "Reset a Traffic Card in CTC" procedure.

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

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

Step 4 If the single card replacement does not clear the alarm, or if multiple cards report the alarm, verify the office power. Refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide. For procedures to install power or refer to the Chapter 1 "General Troubleshooting," for power supply troubleshooting procedures.

Step 5 If the alarm does not clear, reseat the power cable connection to the connector.

Step 6 If the alarm does not clear, physically replace the power cable connection to the connector.

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

2.7.188  PWR-FAIL-B

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

Logical Object: EQPT

The Equipment Power Failure at Connector B alarm occurs when there is no power supply from the main power connector to the equipment. This alarm occurs on the MIC, XTC card, or OC-N cards.

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

Clear the PWR-FAIL-B Alarm

Step 1 Complete the "Clear the PWR-FAIL-A Alarm" procedure.

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

2.7.189  PWR-FAIL-RET-A

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

Logical Object: EQPT

The Equipment Power Failure at Connector A alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the XTC card, MIC-A/P, or OC-N cards.

Clear the PWR-FAIL-RET-A Alarm

Step 1 Complete the "Clear the PWR-FAIL-A Alarm" procedure.

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

2.7.190  PWR-FAIL-RET-B

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

Logical Object: EQPT

The Equipment Power Failure at Connector B alarm occurs when there is no power supplied to the backup power connector on the shelf. This alarm occurs on the XTC card, MIC-A/P, or OC-N cards.

Clear the PWR-FAIL-RET-B Alarm

Step 1 Complete the "Clear the PWR-FAIL-A Alarm" procedure.

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

2.7.191  RAI

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

Logical Objects: DS1, DS3

The Remote Alarm Indication (RAI) condition signifies an end-to-end failure. The error condition is sent from one end of the SONET path to the other. RAI on an XTC card indicates that the far-end node is receiving a DS-3 AIS.

Clear the RAI Condition

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

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

2.7.192  RFI-L

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

Logical Object: OCN

A Remote Fault Indication (RFI) Line condition occurs when the ONS 15327 detects an RFI in OC-N card SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-L condition in the reporting node. RFI-L indicates that the condition is occurring at the line level.

Clear the RFI-L Condition

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

Step 2 Identify and clear any alarms, particularly the "LOS (OCN)" alarm on page 2-99.

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

2.7.193  RFI-P

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

Logical Objects: STSMON, STSTRM

An RFI Path condition occurs when the ONS 15327 detects an RFI in the an STS-1 signal SONET overhead because of a fault in another node. Resolving the fault in the adjoining node clears the RFI-P condition in the reporting node. RFI-P occurs in the terminating node in that path segment.

Clear the RFI-P Condition

Step 1 Verify that the ports are enabled and in service (IS) on the reporting ONS 15327 by completing the following steps:

a. Confirm that the LED is correctly illuminated on the physical card.

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

b. To determine whether the 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 Admin State column lists the port as IS.

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

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

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 Clear alarms in the node with the failure, especially the "UNEQ-P" alarm on page 2-147.

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

2.7.194  RFI-V

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

Logical Objects: VT-MON, VT-TERM

An RFI VT Layer condition occurs when the ONS 15327 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 condition in the reporting node. RFI-V indicates that an upstream failure has occurred at the VT layer.

Clear the RFI-V Condition

Step 1 Verify that the connectors are securely fastened and connected to the correct slot. For more information, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 2 If connectors are correctly connected, verify that the XTC card DS-1 port is active and in service (IS-NR) by completing the following steps:

a. Confirm that the LED is correctly illuminated on the physical card:

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

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

c. Click the Provisioning > DS1 > Line tabs.

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

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

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Step 3 If the ports are active and in service, use an optical test set to verify that the signal source does not have errors. For specific procedures to use the test set equipment, consult the manufacturer.

Step 4 If the signal is valid, log into the node at the far-end of the reporting ONS 15327.

Step 5 Clear alarms in the far-end node, especially the "UNEQ-P" alarm on page 2-147 or the "UNEQ-V" alarm on page 2-149.

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

2.7.195  RING-ID-MIS

The RING-ID-MIS alarm is not used in this platform in this release. It is reserved for development.

2.7.196  RING-MISMATCH

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

Logical Object: OCN

A Procedural Error Mismatch Ring alarm occurs when the ring name of the ONS 15327 node that is reporting the alarm does not match the ring name of another node in the BLSR. Nodes connected in a BLSR must have identical ring names to function. This alarm can occur during BLSR provisioning.

RING-MISMATCH is somewhat similar to RING-ID-MIS, but it applies to BLSR protection discovery instead of node discovery.

Clear the RING-MISMATCH Alarm

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

Step 2 Note the number in the Ring Name field.

Step 3 Log into the next ONS 15327 in the BLSR.

Step 4 Complete the "Identify an ONS 15327 BLSR Ring Name or Node ID Number" procedure.

Step 5 If the ring name matches the ring name in the reporting ONS 15327 node, repeat Step 4 for the next node in the BLSR.

Step 6 Complete the "Change an ONS 15327 BLSR Ring Name" procedure.

Step 7 Verify that the ring map is correct.

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.197  RING-SW-EAST

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

Logical Object: OCN

The Ring Switch Is Active East Side condition occurs when a ring switch occurs at the east side of a BLSR using a Force Ring command. The condition clears when the switch is cleared. RING-SW-EAST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an "F" on the network view detailed circuit map.

Note RING-SW-EAST is an informational condition. It does not require troubleshooting.

2.7.198  RING-SW-WEST

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

Logical Object: OCN

The Ring Switch Is Active West Side condition occurs when a ring switch occurs at the west side of a BLSR using a Force Ring command. The condition clears when the switch is cleared. RING-SW-WEST is visible on the network view Alarms, Conditions, and History tabs. The port where the Force Ring was applied shows an "F" on the network view detailed circuit map.

Note RING-SW-WEST is an informational condition. It does not require troubleshooting.

2.7.199  ROLL

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

Logical Objects: STSMON, STSTRM, VT-MON

The ROLL condition indicates that circuits are being rolled. This is typically carried out to move traffic for a maintenance operation or to perform bandwidth grooming. The condition indicates that a good signal has been received on the roll destination leg, but the roll origination leg has not yet been dropped. The condition clears when the roll origination leg is dropped.

Note ROLL is an informational condition and does not require troubleshooting.

2.7.200  ROLL-PEND

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

Logical Objects: STSMON, STSTRM, VT-MON

ROLL-PEND indicates that a roll process has been started, but a good signal has not been received yet by the roll destination leg. This condition can be raised individually by each path in a bulk circuit roll.

The condition clears when a good signal has been received on the roll destination leg.

Note ROLL-PEND is an informational condition and does not require troubleshooting.

2.7.201  RUNCFG-SAVENEED

The RUNCFG-SAVENEED alarm is not used in this platform in this release. It is reserved for development.

2.7.202  SD (DS1, DS3)

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

Logical Objects: DS1, DS3

A Signal Degrade (SD) condition for DS-1 or DS-3 occurs when the quality of an electrical signal has exceeded the bit error rate (BER) 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, but SD is triggered at a lower BER than SF.

The BER threshold is user-provisionable and has a range for SD from 1E-9 dBm to 1E-5 dBm.

SD can be reported on electrical card ports that are IS-NR; Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AIS); or OOOS-MA,MT but not in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state. The BER count increase associated with this alarm does not take an IS-NR port out of service, but if it occurs on an AINS port, the alarm prevents the port from going into service.

The SD condition clears when the BER level falls to one-tent h of the threshold level that triggered the condition. 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. SD can also be caused by repeated XTC card switches that in turn can cause switching on the lines or paths.

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

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

Note Some levels of BER errors (such as 1E-9 dBm) take a long period to raise or clear, about 9,000 seconds, or 150 minutes. If the SD threshold is provisioned at 1E-9 dBm rate, the SD alarm needs at least one and one-half hours to raise and then another period at least as long to clear.

Note The recommended test set for use on all SONET ONS electrical cards is the Omniber 718.

Clear the SD (DS1, DS3) Condition

Step 1 Complete the "Clear an XTC Card DS-1 or DS-3 Loopback Circuit" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 2 Ensure that the fiber connector for the card is completely plugged in. For more information about fiber connections and card insertion, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide.

Step 3 If the 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 4 If the optical power level is good, verify that optical receive levels are within the acceptable range.

Step 5 If receive levels are good, clean the fibers at both ends according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 Procedure Guide.

Step 6 If the condition does not clear, verify that single-mode fiber (SMF) is used.

Step 7 If the fiber is of the correct type, verify that a single-mode laser is used at the far-end node.

Step 8 Clean the fiber connectors at both ends for a signal degrade according to site practice.

Step 9 If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement. Refer to the "Physical Card Reseating, Resetting, and Replacement" section.

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

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

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

2.7.203  SD-L

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

Logical Object: OCN

An SD Line condition is similar to the "SD (DS1, DS3)" condition on page 2-124. It applies to the line level of the SONET signal and travels on the B2 byte of the SONET overhead.

An SD-L on an Ethernet or OC-N card does not cause a protection switch. If the alarm is reported on a card that has also undergone a protection switch, the SD BER count continues to accumulate. The condition is superseded by higher-priority alarms such as LOF (OCN) and LOS (OCN).

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

Clear the SD-L Condition

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

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

2.7.204  SD-P

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

Logical Objects: STSMON, STSTRM

An SD Path condition is similar to the "SD (DS1, DS3)" condition on page 2-124, but it applies to the path (STS) layer of the SONET overhead. A path or STS-level SD alarm travels on the B3 byte of the SONET overhead.

For path protection protected circuits, the BER threshold is user-provisionable and has a range for SD from 1E-9 dBm to 1E-5 dBm. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E-6 dBm.

On path protection, an SD-P condition causes a switch from the working card to the protect card at the path (STS) level. On BLSR, 1+1, and unprotected circuits, an SD-P condition does not cause switching.

The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

The SD alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.

Clear the SD-P Condition

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

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

2.7.205  SD-V

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

Logical Objects: VT-MON, VT-TERM

An SD-V condition is similar to the "SD (DS1, DS3)" condition on page 2-124, but it applies to the VT layer of the SONET overhead.

For path protection protected circuits, the BER threshold is user-provisionable and has a range for SD from 1E-9 dBm to 1E-5 dBm. For BLSR 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E-6 dBm. On path protection configurations, an SD-V condition does not cause a switch from the working card to the protect card at the path (STS) level. On BLSR, 1+1, and unprotected circuits, an SD-V condition does not cause switching.

The BER increase that causes the alarm is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

The SD alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.

Clear the SD-V Condition

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

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

2.7.206  SF (DS1, DS3)

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

Logical Objects: DS1, DS3

A Signal Fail (SF) condition occurs when the quality of the signal has exceeded the BER signal failure threshold. Signal failure is defined by Telcordia as a "hard failure" condition. The SD and SF conditions both monitor the incoming BER error rate and are similar conditions, but SF is triggered at a higher BER than SD.

The BER threshold is user-provisionable and has a range for SF from 1E-5 dBm to 1E-3 dBm.

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

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

Clear the SF (DS1, DS3) Condition

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

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

2.7.207  SF-L

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

Logical Object: OCN

An SF Line condition is similar to the "SF (DS1, DS3)" condition on page 2-127, but it applies to the line layer B2 overhead byte of the SONET signal. It can trigger a protection switch.

The SF-L condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

The condition is superseded by a higher-priority alarm, such as LOS (OCN).

Clear the SF-L Condition

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

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

2.7.208  SF-P

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

Logical Objects: STSMON, STSTRM

An SF Path condition is similar to an "SF-L" condition on page 2-128, but it applies to the path (STS) layer B3 byte of the SONET overhead. It can trigger a protection switch.

The SF-P condition clears when the BER level falls to one-tenth of the threshold level that triggered the condition. A BER increase is sometimes caused by a physical fiber problem, including a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.

Clear the SF-P Condition

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

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

2.7.209  SFTWDOWN

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

Logical Object: EQPT

A Software Download in Progress alarm occurs when the XTC card is downloading or transferring software. If the active and standby XTC cards have the same versions of software, it takes approximately three minutes for software to be updated on a standby XTC card. If the active and standby XTC cards have different software versions, the system software transfer can take up to 30 minutes for ONS 15327 cards.

No action is necessary. Wait for the transfer or the software download to complete. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco Technical Support (1-800-553-2447).

Note SFTWDOWN is an informational alarm.

2.7.210  SF-V

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

Logical Objects: VT-MON, VT-TERM

An SF-V condition is similar to the "SF (DS1, DS3)" condition on page 2-127, but it applies to the VT layer of the SONET overhead.

Clear the SF-V Condition

Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

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

2.7.211  SHELF-COMM-FAIL

For information about this alarm or condition, refer to the "Alarm Troubleshooting" chapter of the Cisco ONS 15454 DWDM Troubleshooting Guide.

2.7.212  SNTP-HOST

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

Logical Object: NE

The Simple Network Time Protocol (SNTP) Host Failure alarm indicates that an ONS 15327 serving as an IP proxy for the other nodes in the ring is not forwarding SNTP information to the other ONS 15327 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.

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 by completing the procedure in the "Verify PC Connection to the ONS 15327 (Ping)" section.

Step 2 If the ping fails, contact the network administrator who manages the IP network that supplies the SNTP information to the proxy and determine whether the network is experiencing problems that could affect the SNTP server/router connecting to the proxy ONS system.

Step 3 If no network problems exist, ensure that the ONS 15327 proxy is provisioned correctly by completing the following steps:

a. In node view for the ONS 15327 node serving as the proxy, click the Provisioning > General tabs.

b. Ensure that the Use NTP/SNTP Server check box is checked.

c. If the Use NTP/SNTP Server check box is not checked, check it.

d. Ensure that the Use NTP/SNTP Server field contains a valid IP address for the server.

Step 4 If proxy is correctly provisioned, refer to the "Timing" chapter of the Cisco ONS 15327 Reference Manual for more information on the SNTP host.

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

2.7.213  SQUELCH

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

Logical Object: OCN

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 disables circuits that originate or terminate on the failed node. SQUELCH conditions appear on one or both of the nodes on either side of the isolated or failed node. The "AIS-P" condition on page 2-19 also appears on all nodes in the ring except the isolated node.

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

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

Clear the SQUELCH Condition

Step 1 Determine the isolated node by completing the following steps:

a. In node view, click View > Go to Network View.

b. The grayed-out node with red spans is the isolated node.

Step 2 Verify fiber continuity to the ports on the isolated node. To verify cable continuity, follow site practices.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 3 If fiber continuity is okay, verify that the proper ports are in service by completing the following steps:

a. Confirm that the LED is correctly illuminated on the physical card.

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

b. To determine whether the 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 Admin State column lists the port as IS.

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

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

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 (traffic) card's receiver specifications. Refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide, for optical card transmit and receive specifications.

Step 6 If the receiver levels are good, ensure that the optical transmit and receive fibers are connected properly.

Step 7 If the connectors are good, complete the "Physically Replace a Card" procedure 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. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

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

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

2.7.214  SQUELCHED

The SQUELCHED alarm is not used in this platform in this release. It is reserved for development.

2.7.215  SQM

Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Major (MJ), Service-Affecting (SA) for VT-TERM

Logical Objects: STSTRM, VT-TERM

The Sequence Mismatch alarm is a virtual concatenated (VCAT) member alarm. (VCAT member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when the expected sequence numbers of VCAT members do not match the received sequence numbers.

Clear the SQM Alarm

Step 1 For the errored circuit, complete the "Delete a Circuit" procedure.

Step 2 Recreate the circuit using the procedure in the "Create Circuits and VT Tunnels" chapter of the Cisco ONS 15327 Procedure Guide.

Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.216  SSM-DUS

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

Logical Objects: BITS, DS1, OCN

The Synchronization Status Message (SSM) Quality Changed to Do Not Use (DUS) condition 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 an informational condition. It does not require troubleshooting.

2.7.217  SSM-FAIL

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

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

Logical Objects: BITS, OCN

The SSM Failed alarm occurs when the synchronization status messaging received by the ONS 15327 fails. The problem is external to the ONS 15327. This alarm indicates that although the ONS 15327 is set up to receive SSM, the timing source is not delivering valid SSM messages.

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.

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

2.7.218  SSM-LNC

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

2.7.219  SSM-OFF

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

Logical Objects: BITS, DS1, OCN

The SSM Off condition applies to references used for timing the node. It occurs when the SSM for the reference has been turned off. The ONS system is set up to receive SSM, but the timing source is not delivering SSM messages.

Clear the SSM-OFF Condition

Step 1 Complete the "Clear the SSM-FAIL Alarm" procedure.

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

2.7.220  SSM-PRC

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

2.7.221  SSM-PRS

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

Logical Objects: BITS, NE-SREF, OCN

The SSM Primary Reference Source (PRS) Traceable condition occurs when the SSM transmission level is changed to Stratum 1 Traceable.

Note SSM-PRS is an informational condition. It does not require troubleshooting.

2.7.222  SSM-RES

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

Logical Objects: BITS, DS1, NE-SREF, OCN

The SSM Reserved (RES) For Network Synchronization Use condition occurs when the synchronization message quality level is changed to RES.

Note SSM-RES is an informational condition. It does not require troubleshooting.

2.7.223  SSM-SDH-TN

The SSM-SDH-TN condition is not used in this platform in this release. It is reserved for development.

2.7.224  SSM-SETS

The SSM-SETS condition is not used in this platform in this release. It is reserved for development.

2.7.225  SSM-SMC

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

Logical Objects: BITS, NE-SREF, OCN

The SSM SONET Minimum Clock (SMC) Traceable condition occurs when the synchronization message quality level changes to SMC. The login node does not use the clock because the node cannot use any reference beneath its internal level, which is ST3.

Note SSM-SMC is an informational condition. It does not require troubleshooting.

2.7.226  SSM-ST2

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

Logical Objects: BITS, NE-SREF, OCN

The SSM Stratum 2 (ST2) Traceable condition occurs when the synchronization message quality level is changed to ST2.

Note SSM-ST2 is an informational condition. It does not require troubleshooting.

2.7.227  SSM-ST3

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

Logical Objects: BITS, NE-SREF, OCN

The SSM Stratum 3 (ST3) Traceable condition occurs when the synchronization message quality level is changed to ST3.

Note SSM-ST3 is an informational condition. It does not require troubleshooting.

2.7.228  SSM-ST3E

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

Logical Objects: BITS, NE-SREF, OCN

The SSM Stratum 3E (ST3E) Traceable condition indicates that 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.

Note SSM-ST3E is an informational condition. It does not require troubleshooting.

2.7.229  SSM-ST4

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

Logical Objects: BITS, DS1, NE-SREF, OCN

The SSM Stratum 4 (ST4) Traceable condition occurs when the synchronization message quality level is lowered to ST4. The message quality is not used because it is below ST3.

Note SSM-ST4 is an informational condition. It does not require troubleshooting.

2.7.230  SSM-STU

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

Logical Objects: BITS, NE-SREF, OCN

The SSM Synchronization Traceability Unknown (STU) condition occurs when the reporting node is timed to a reference that does not support SSM, but the ONS 15327 has SSM support enabled. SSM-STU can also occur if the timing source is sending out SSM messages but SSM is not enabled on the ONS 15327.

Clear the SSM-STU Condition

Step 1 In node view, click the Provisioning > Timing > BITS Facilities tabs.

Step 2 If the Sync. Messaging Enabled check box for the BITS source is checked, uncheck the box.

Step 3 If the Sync. Messaging Enabled check box for the BITS source is not checked, check the box.

Step 4 Click Apply.

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

2.7.231  SSM-TNC

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

Logical Object: BITS

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

Note SSM-TNC is an informational condition. It does not require troubleshooting.

2.7.232  STS-SQUELCH-L

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

Logical Object: OCN

The Ring is Squelching STS Traffic condition is raised on an OC-N facility. If a node failure includes the source or destination node, the process of switching nodes squelches all of the STSs that originate from or have a destination of the failure node. The condition resolves when the node is no longer failing.

This condition is raised as NA severity by default. However, it indicates that traffic is squelched due to node failure, that is, traffic outage. Traffic outage can be caused by different problems, such as multiple LOS alarms, AIS-L, or node power outage. STS-SQUELCH-L is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what causes node isolation.

Note STS-SQUELCH-L is an informational condition. It does not require troubleshooting.

2.7.233  SW-MISMATCH

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

Logical Object: EQPT

The Software Mismatch condition occurs during software upgrade when there is a mismatch between software versions. The card connecting to the XTC card is running an older version than the XTC card is.

Clear the SW-MISMATCH Condition

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

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

2.7.234  SWMTXMOD-PROT

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

Logical Object: EQPT

The Switching Matrix Module Failure on Protect Slot alarm is raised by the Slot 6 cross-connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-PROT occurs when a logic component internal to the Slot 6 cross connect is out of frame (OOF) with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.

The XTC card can raise this alarm (in Slot 6) whether it is ACT or standby (SBY). The XTC card can raise SWMTXMOD-PROT against itself if the cross-connect card is OOF with a second logic component on the same cross connect card.

Clear the SWMTXMOD-PROT Alarm

Step 1 Complete the "Reset a Traffic Card in CTC" procedure for the Slot 6 card. For the LED behavior, see the "Typical ONS 15327 Traffic Card LED Activity During Reset" section.

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

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

Step 4 Complete the "Side Switch the Active and Standby XTC Cards" procedure.

Note After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.

Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.235  SWMTXMOD-WORK

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

Logical Object: EQPT

The Switching Matrix Module Failure on Working Slot alarm is raised by the Slot 5 cross-connect card if this card is active (ACT). Any kind of cross-connect card can raise this alarm. (Two exceptions are given in the following paragraph.) SWMTXMOD-WORK occurs when a logic component internal to the Slot 5 XTC card is OOF with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.

TheXTC card can raise this alarm (in Slot 5) whether it is ACT or standby (SBY). The XTC card can raise SWMTXMOD-WORK against itself if the cross-connect card is OOF with a second logic component on the same cross-connect card.

Clear the SWMTXMOD-WORK Alarm

Step 1 Complete the "Reset a Traffic Card in CTC" procedure for the Slot 5 card. For the LED behavior, see the "Typical ONS 15327 Traffic Card LED Activity During Reset" section.

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

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

Step 4 Complete the "Side Switch the Active and Standby XTC Cards" procedure.

Note After the active cross-connect card goes into standby mode, the original standby slot becomes active. The former standby card ACT/SBY LED becomes green.

Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.236  SWTOPRI

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

Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Primary Reference condition occurs when the ONS 15327 switches to the primary timing source (reference 1). The ONS 15327 system uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference.

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

2.7.237  SWTOSEC

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

Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Secondary Reference condition occurs when the ONS 15327 has switched to a secondary timing source (reference 2).

Clear the SWTOSEC Condition

Step 1 To clear the condition, clear alarms related to failures of the primary source, such as the "SYNCPRI" alarm on page 2-140.

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

2.7.238  SWTOTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

The Synchronization Switch to Third Reference condition occurs when the ONS 15327 has switched to a third timing source (reference 3).

Clear the SWTOTHIRD Condition

Step 1 To clear the condition, clear alarms related to failures of the primary source, such as the "SYNCPRI" alarm on page 2-140 or the "SYNCSEC" alarm on page 2-141.

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

2.7.239  SYNC-FREQ

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

Logical Objects: BITS, DS1, OCN

The Synchronization Reference Frequency Out Of Bounds condition is reported against any reference that is out of the bounds for valid references. The login node fails the reference and chooses another internal or external reference to use.

Clear the SYNC-FREQ Condition

Step 1 Use an optical test set to verify the timing frequency of the line or BITS timing source and ensure that it falls within the proper frequency. For specific procedures to use the test set equipment, consult the manufacturer.

For BITS, the proper timing frequency range is approximately -15 PPM to 15 PPM. For optical line timing, the proper frequency range is approximately -16 PPM to 16 PPM.

Step 2 If the reference source frequency is not outside of bounds, complete the "Physically Replace a Card" procedure for the XTC card.

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

Note It takes up to 30 minutes for the ONS 15327 XTC card to transfer the system software to the newly installed XTC card. Software transfer occurs in instances where different software versions exist on the two cards. When the transfer completes, the active XTC card reboots and goes into standby mode after approximately three minutes.

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

2.7.240  SYNCPRI

Default Severity: Minor (MN), Non-Service-Affecting (NSA) for EXT-SREF; Major (MJ), Service-Affecting (SA) for NE-SREF

Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Primary Reference alarm occurs when the ONS 15327 loses the primary timing source (Reference 1). The ONS 15327 system uses three ranked timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCPRI occurs, the ONS 15327 should switch to its secondary timing source (Reference 2). Switching to a secondary timing source also triggers the "SWTOSEC" alarm on page 2-139.

Clear the SYNCPRI Alarm

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

Step 2 Verify the current configuration for REF-1 of the NE Reference.

Step 3 If the primary timing reference is a BITS input, complete the "Clear the LOS (BITS) Alarm" procedure.

Step 4 If the primary reference clock is an incoming port on the ONS 15327, complete the "Clear the LOS (OCN) Alarm" procedure.

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

2.7.241  SYNCSEC

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

Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Secondary Reference alarm occurs when the ONS 15327 loses the secondary timing source (reference 2). If SYNCSEC occurs, the ONS 15327 should switch to a third timing source (reference 3) to obtain valid timing. Switching to a third timing source also triggers the "SWTOTHIRD" alarm on page 2-139.

Clear the SYNCSEC Alarm

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

Step 2 Verify the current configuration of REF-2 for the NE Reference.

Step 3 If the second reference is a BITS input, complete the "Clear the LOS (BITS) Alarm" procedure.

Step 4 Verify that the BITS clock is operating properly.

Step 5 If the secondary timing source is an incoming port on the ONS 15327, complete the "Clear the LOS (OCN) Alarm" procedure.

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

2.7.242  SYNCTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

A Loss of Timing on Third Reference alarm occurs when the ONS 15327 loses the third timing source (reference 3). If SYNCTHIRD occurs and the ONS 15327 uses an internal reference for source three, the XTC card could have failed. The system often reports either the "FRNGSYNC" condition on page 2-79 or the "HLDOVRSYNC" condition on page 2-82 after a SYNCTHIRD alarm.

Clear the SYNCTHIRD Alarm

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

Step 2 Verify that the current configuration of REF-3 for the NE Reference. For more information about references, refer to the "Timing" chapter in the Cisco ONS 15327 Reference Manual.

Step 3 If the third timing source is a BITS input, complete the "Clear the LOS (BITS) Alarm" procedure.

Step 4 If the third timing source is an incoming port on the ONS 15327, complete the "Clear the LOS (OCN) Alarm" procedure.

Step 5 If the third timing source uses the internal ONS system timing, complete the "Reset an Active XTC Card and Activate the Standby Card" procedure.

Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.

Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco Technical Support (1-800-553-2447). If the Cisco Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby XTC Card" procedure. If the Cisco Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

2.7.243  SYSBOOT

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: NE

The System Reboot alarm indicates that new software is booting on the XTC card. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 30 minutes.

Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

Note SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.

2.7.244  TIM

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Object: OCN

The Section TIM alarm occurs when the expected J0 section trace string does not match the received section trace string. This occurs because the data being received is not correct, and the receiving port could not be connected to the correct transmitter port.

If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed due to a fibering misconnection, a TL1 routing change, or to someone entering an incorrect value in the Current Transmit String field.

TIM occurs on a port that has previously been operating without alarms if someone switches optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the "LOS (OCN)" alarm on page 2-99 or the "UNEQ-P" alarm on page 2-147. If these alarms accompany a TIM alarm, reattach or replace the original cables/fibers to clear the alarms. If a Transmit or Expected String was changed, restore the original string.

Clear the TIM Alarm

Step 1 Ensure that the physical fibers are correctly configured and attached. To do this, consult site documents. For more information about cabling the ONS 15327, refer to the "Install the Shelf and Common Control Cards" chapter in the Cisco ONS 15454 DWDM Procedure Guide.

Step 2 If the alarm does not clear, you can compare the J0 expected and transmitted strings and, if necessary, change them by completing the following steps:

a. Log into the circuit source node and click the Circuits tab.

b. Select the circuit reporting the condition, then click Edit.

c. In the Edit Circuit window, check the Show Detailed Circuit Map check box and click Apply.

d. On the detailed circuit map, right-click the source circuit port and choose Edit J0 Path Trace (port) from the shortcut menu.

e. Compare the Current Transmit String and the Current Expected String entries in the Edit J0 Path Trace dialog box.

f. If the strings differ, correct the Transmit or Expected strings and click Apply.

g. Click Close.

Step 3 If the alarm does not clear, ensure that the signal has not been incorrectly routed. (Although the ONS 15327 routes circuits automatically, the circuit route could have been changed using TL1.) If necessary, manually correct the routing using TL1. For instructions, consult the Cisco ONS SONET TL1 Reference Guide and the Cisco ONS SONET TL1 Command Guide.

Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem if necessary.

2.7.245  TIM-MON

The TIM-MON alarm is not used in this platform in this release. It is reserved for development.

2.7.246  TIM-P

Default Severity: Minor (MN), Non-Service-Affecting (NSA) for STSMON; Critical (CR), Service-Affecting (SA) for STSTRM

Logical Objects: STSMON, STSTRM

The 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 Current Expected String field for the receiving port. The string must match the string typed into the Transmit String field for the sending port. If these fields do not match, the login node raises the TIM-P alarm. 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 Current Transmit String field. Complete the following procedure to clear either instance.

Clear the TIM-P Alarm

Step 1 Log into the circuit source node and click the Circuits tab.

Step 2 Select the circuit reporting the condition, then click Edit.

Step 3 In the Edit Circuit window, check the Show Detailed Circuit Map check box and click Apply.

Step 4 On the detailed circuit map, right-click the source circuit port and choose Edit J1 Path Trace (port) from the shortcut menu.

Step 5 Compare the Current Transmit String and the Current Expected String entries in the Edit J1 Path Trace dialog box.

Step 6 If the strings differ, correct the Transmit or Expected strings and click Apply.

Step 7 Click Close.

Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.247  TIM-S

The TIM-S alarm is not used in this platform in this release. It is reserved for development.

2.7.248  TIM-V

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: VT-TERM

The VT Path TIM alarm is raised on VT terminations when the J2 path trace is enabled and is mismatched with the expected trace string.

Clear the TIM-V Alarm

Step 1 Complete the "Clear the TIM Alarm" procedure.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a Service-Affecting (SA) problem.

2.7.249  TPTFAIL (G1000)

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: G1000

The Transport (TPT) Layer Failure alarm for the G-Series Ethernet (traffic) card indicates a break in the end-to-end Ethernet link integrity feature of the G-Series 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 that prevents the complete end-to-end Ethernet path from working. If any SONET path alarms such as the "AIS-P" condition on page 2-19, the "LOP-P" alarm on page 2-95, the "PDI-P" alarm on page 2-112, or the "UNEQ-P" alarm on page 2-147 exist on the SONET path used by the Ethernet port, the affected port causes a TPTFAIL alarm. Also, if the far-end G-Series port Ethernet port is administratively disabled or it is reporting the "CARLOSS (G1000)" alarm on page 2-37, the C2 byte in the SONET path overhead indicates the "PDI-P" alarm on page 2-112, which in turn causes a TPTFAIL to be reported against the near-end port.

When a TPTFAIL alarm occurs, the near-end port is automatically disabled (transmit laser turned off). In turn, the laser shutoff can also cause the external Ethernet device attached at the near end to detect a link down and turn off its transmitter. This also causes a CARLOSS alarm to occur on the reporting port. In all cases, the source problem is either in the SONET path being used by the G-Series port or the far-end G-Series port to which it is mapped.

An occurrence of TPTFAIL on an ONS 15327 G-Series port indicates either a problem with the SONET path that the port is using or with the far-end G-Series port that is mapped to the port.

Note For more information about Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.

Clear the TPTFAIL (G1000) Alarm

Step 1 Clear any alarms being reported by the OC-N card on the G-Series circuit.

Step 2 If no alarms are reported by the OC-N card, or if the "PDI-P" condition on page 2-112 is reported, the problem could be on the far-end G-Series port. Clear any alarms, such as CARLOSS, reported against the far-end port or card.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.250  TRMT

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: DS1

A Missing Transmitter alarm occurs when there is a transmit failure on the ONS 15327 XTC card DS-1 port because of an internal hardware failure. The card must be replaced.

Clear the TRMT Alarm

Step 1 Complete the "Physically Replace a Card" procedure for the reporting DS-1 card.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

Note When you replace a card with the identical type of card, you do not need to make any changes to the database.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.251  TRMT-MISS

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Object: DS1

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 DS-1 port on the XTC card or the backplane does not match the inserted card. For example, an SMB connector or a BNC connector could be connected to an XTC-14 card instead of an XTC-28-3 card.

Note DS-1s are four-wire circuits and need a positive and negative connection for both transmit and receive.

Clear the TRMT-MISS Alarm

Step 1 Verify that the device attached to the DS-1 port is operational.

Step 2 If the device is operational, verify that the cabling is securely connected.

Step 3 If the cabling is secure, verify that the pinouts are correct.

Step 4 If the pinouts are correct, replace the transmit cable.

Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.252  TX-AIS

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)

Logical Objects: DS1, DS3

The (TX) Transmit Direction AIS condition is raised by the ONS 15327 backplane when it receives a far-end DS-1 LOS.

Clear the TX-AIS Condition

Step 1 Determine whether there are alarms on the downstream nodes and equipment, especially the "LOS (OCN)" alarm on page 2-99, or OOS ports.

Step 2 Clear the downstream alarms using the applicable procedures in this chapter.

Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.7.253  TX-LOF

Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)

Logical Object: DS1

The Transmit Direction LOF condition is transmitted by the backplane when it receives a DS-1 TX-LOF.

This alarm is raised only at the transmit (egress) side.

Clear the TX-LOF Condition

Step 1 Complete the "Clear the LOF (DS1) Alarm" alarm on page 2-92 procedure.

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).

2.7.254  TX-RAI

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects:DS1, DS3

The Transmit Direction RAI condition is transmitted by the backplane when it receives a DS-1 TX-AIS. This alarm is raised only at the transmit side, but RAI is raised at both ends.

Clear the TX-RAI Condition

Step 1 Complete the "Clear the TX-AIS Condition" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.7.255  UNEQ-P

Default Severity: Critical (CR), Service-Affecting (SA)

Logical Objects: STSMON, STSTRM

An SLMF UNEQ 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 could result from an incomplete circuit or an empty VT tunnel. UNEQ-P occurs in the node that terminates a path.

Note If a newly created circuit has no signal, an UNEQ-P alarm is reported on the OC-N cards and the "AIS-P" condition on page 2-19 is reported on the terminating cards. These alarms clear when the circuit carries a signal.

Caution Deleting a circuit can affect traffic.

Clear the UNEQ-P Alarm

Step 1 In node view, click View > Go to Network View.

Step 2 Right-click the alarm to display the Select Affected Circuits shortcut menu.

Step 3 Click Select Affected Circuits.

Step 4 When the affected circuits appear, look in the Type column for VTT, which indicates a VT tunnel circuit. A VT tunnel with no VTs assigned could 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) by completing the following steps:

Note The node does 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.

b. Complete the "Delete a Circuit" procedure.

c. If an error message dialog box appears, the VT tunnel is valid and not the cause of the alarm.

d. Repeat Steps a through c for each column containing VTT.

Step 7 If all ONS 15327 nodes in the ring appear in the CTC network view, determine whether the circuits are complete by completing the following steps:

a. Click the Circuits tab.

b. Verify that PARTIAL is not listed in the Status column of any circuits.

c. If you find circuits listed as PARTIAL, use an optical test set to verify that these circuits are not working circuits that continue to pass traffic. For specific procedures to use the test set equipment, consult the manufacturer.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located between the top high-speed and XTC slots of the shelf assembly.

Step 8 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits. Complete the "Delete a Circuit" procedure.

Step 9 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15327 Procedure Guide for procedures.

Step 10 Log back in and verify that all circuits terminating in the reporting card are active by completing the following steps:

a. Click the Circuits tab.

b. Verify that the Status column lists all circuits as active.

Step 11 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15327 Procedure Guide.

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Step 12 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the OC-N and DS-N ports.

Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

Note When you replace a card with the identical type of card, you do not need to make any changes to the database.

Step 13 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.256  UNEQ-V

Default Severity: Major (MJ), Service-Affecting (SA)

Logical Objects: VT-MON, VT-TERM

An SLMF UNEQ 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 zeros. The source of the problem is not the node raising the alarm, but the node transmitting the VT signal to it. The V in UNEQ-V indicates that the failure has occurred at the VT layer.

Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056

Warning Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057

Clear the UNEQ-V Alarm

Step 1 Complete the "Clear the UNEQ-P Alarm" procedure.

Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15327. Plug the wristband cable into the ESD jack located on the between the top high-speed and XTC slots of the shelf assembly.

Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.

2.7.257  VT-SQUELCH-L

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Object: OCN

The Ring is Squelching VT Traffic condition is raised on an OC-N facility. If the node failure includes the source node, when the node drops the VT, VT traffic is squelched. The condition resolves when the node failure is recovered.

This condition is raised as NA severity by default. However, it indicates that traffic is squelched due to node failure, that is, traffic outage. Traffic outage can be caused by different problems, such as multiple LOS alarms, AIS-L, or node power outage. VT-SQUELCH-L is symptomatic and indicates that the user must investigate which node in a ring is being isolated and what causes node isolation.

Note VT-SQUELCH-L is an informational condition.

2.7.258  WKSWPR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: EQPT, OCN, STSMON, VT-MON

The Working Switched To Protection condition occurs when a line experiences the "LOS (OCN)" alarm on page 2-99 or the "SD (DS1, DS3)" condition on page 2-124.

Clear the WKSWPR Condition

Step 1 Complete the "Clear the LOS (OCN) Alarm" procedure.

Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).

2.7.259  WTR

Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)

Logical Objects: EQPT, OCN, STSMON, VT-MON

The Wait To Restore condition occurs when the "WKSWPR" condition on page 2-150 is raised and the wait-to-restore time has not expired, meaning that the active protect path cannot revert to the working path. The condition clears when the timer expires and traffic switches back to the working path.

Note WTR is an informational condition. It does not require troubleshooting.

2.8  XTC Card Line Alarms

The XTC-28-3 card's ports provide three choices of line types: ESF, D4, or Unframed. The choice of framing format determines the line alarms that the XTC-28-3 card reports. Table 2-13 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 XTC-14 card reports the same STS alarms as the standard XTC-28-3 card does.

Table 2-13 DS3-12E Line Alarms

Alarm

UNFRAMED

D4

ESF

LOS

Yes

Yes

Yes

AIS

Yes

Yes

Yes

LOF

No

Yes

Yes

IDLE

No

Yes

Yes

RAI

No

Yes

Yes

Terminal Lpbk

Yes

Yes

Yes

Facility Lpbk

Yes

Yes

Yes

FE Lpbk

No

No

Yes

FE Common Equipment Failure

No

No

Yes

FE Equipment Failure-SA

No

No

Yes

FE LOS

No

No

Yes

FE LOF

No

No

Yes

FE AIS

No

No

Yes

FE IDLE

No

No

Yes

FE Equipment Failure-NSA

No

No

Yes

2.9  ONS 15327 Traffic Card LED Activity

ONS 15327 card LED behavior patterns are listed in the following sections.

2.9.1  Typical ONS 15327 Traffic Card LED Activity After Insertion

When a traffic card is inserted, the following LED activities occur:

1. The red FAIL LED turns on and remains illuminated for 20 to 30 seconds.

2. The red FAIL LED blinks for 35 to 45 seconds.

3. All LEDs blink once and turn off for 5 to 10 seconds.

4. The ACT or ACT/SBY LED turns on. The SF LED can persist until all card ports connect to their far-end counterparts and a signal is present.

2.9.2  Typical ONS 15327 Traffic Card LED Activity During Reset

While an ONS 15327 card resets, the following LED activities occur:

1. The FAIL LED on the physical card blinks and turns off.

2. The white LED with the letters "LDG" appears on the reset card in CTC.

3. The green ACT LED appears in CTC.

2.9.3  Typical ONS 15327 Cross-Connect LED Activity During Side Switch

While an XTC card is switched in CTC from active (ACT) to standby (SBY) or from SBY to ACT, the following LED activities occur:

1. The FAIL LED on the physical card blinks and turns off.

2. The standby card yellow SBY LED becomes a green ACT LED, indicating it is now active.

3. The active card green ACT LED becomes a yellow SBY LED, indicating it is now standby.

2.10  Frequently Used Alarm Troubleshooting Procedures

This section gives common procedures that are frequently used when troubleshooting alarms. Most of these procedures are summarized versions of fuller procedures existing elsewhere in the ONS 15327 documentation. They are included in this chapter for the user's convenience. For further information, please refer to the "Manage Alarms" chapter in the Cisco ONS 15327 Procedure Guide.

2.10.1  Node and Ring Identification, Change, Visibility, and Termination

Identify an ONS 15327 BLSR Ring Name 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 In node view, click View > Go to Network View.

Step 3 Click the Provisioning > BLSR tabs.

From the Ring Name column, record the ring name, 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.

Note For more information about ring or node traffic switching operations, refer to the "Maintain the Node" chapter in the Cisco ONS 15327 Procedure Guide.

Change an ONS 15327 BLSR Ring Name

Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 In node view, click View > 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, enter the new name in the Ring Name field.

Step 6 Click Apply.

Step 7 Click Yes in the Changing Ring Name dialog box.

Change an ONS 15327 BLSR Node ID Number

Step 1 Log into a node on the network. If you are already logged in, go to Step 2.

Step 2 In node view, click View > 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 In the Edit Node ID dialog box, enter the new ID. The Node ID is the number in parentheses after the Node Name.

Step 8 Click OK.

Verify ONS 15327 Node Visibility for Other Nodes

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 In node view, click the Provisioning > BLSR tabs.

Step 3 Highlight a BLSR.

Step 4 Click Ring Map.

Step 5 In the BLSR Ring Map window, verify that each node in the ring appears on the ring map with a node ID and IP address.

Step 6 Click Close.

2.10.2  Protection Switching, Lock Initiation, and Clearing

Initiate a 1+1 Protection Port Force Switch Command

This procedure switches 1+1 protection group traffic from one port in the group to the other using a Force switch.

Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.

Caution Traffic is not protected during a Force protection switch.

Note A Force command switches traffic on a working path even if the path has SD or SF conditions. A Force switch does not switch traffic on a protect path. A Force switch preempts a Manual switch.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups area, select the protection group with the port you want to switch.

Step 3 In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the protect/standby port, click this port.

Step 4 In the Switch Commands area, click Force.

Step 5 Click Yes in the Confirm Force Operation dialog box.

Step 6 If the switch is successful, the group says "Force to working."

Initiate a 1+1 Protection Port Manual Switch Command

This procedure switches 1+1 protection group traffic from one port in the group to the other using a Manual switch.

Note A Manual command switches traffic if the path has an error rate less than the signal degrade. A Manual switch is preempted by a Force switch.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups area, select the protection group with the port you want to switch.

Step 3 In the Selected Groups area, select the port belonging to the card you are replacing. You can carry out this command for the working or protect port. For example, if you need to replace the card with the protect/standby port, click this port.

Step 4 In the Switch Commands area, click Manual.

Step 5 Click Yes in the Confirm Force Operation dialog box.

Step 6 If the switch is successful, the group says "Force to working."

Clear a 1+1 Protection Port Force or Manual Switch Command

Note If the 1+1 protection group is configured as revertive, clearing a Force switch to protect (or working) moves traffic back to the working port. In revertive operation, the traffic always switches back to working. There is no revert to protect. If ports are not configured as revertive, clearing a Force switch to protect does not move traffic back.

Note If the Force Switch was user-initiated, the reversion occurs immediately when the clear command is issued. The five-minute WTR period is not needed in this case. If the Force was system-initiated, allow the five-minute waiting period (during WTR) before the reversion occurs.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups area, choose the protection group containing the port you want to clear.

Step 3 In the Selected Group area, choose the port you want to clear.

Step 4 In the Switching Commands area, click Clear.

Step 5 Click Yes in the Confirmation Dialog box.

The Force switch is cleared. Traffic immediately reverts to the working port if the group was configured for revertive switching.

Initiate a Card or Port Lock-On Command

Note For 1:1 electrical protection groups, working or protect cards can be placed in the Lock On state. For a 1+1 optical protection group, only the working port can be placed in the Lock On state.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups list, click the protection group where you want to apply a lock-on.

Step 3 If you determine that the protect card is in standby mode and you want to apply the lock-on to the protect card, make the protect card active if necessary by completing the following steps:

a. In the Selected Group list, click the protect card.

b. In the Switch Commands area, click Force.

Step 4 In the Selected Group list, click the active card where you want to lock traffic.

Step 5 In the Inhibit Switching area, click Lock On.

Step 6 Click Yes in the confirmation dialog box.

Initiate a Card or Port Lockout Command

Note For 1:1 electrical protection groups, working or protect cards can be placed in the Lock Out state. For a 1+1 optical protection group, only the protect port can be placed in the Lock Out state.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups list, click the protection group that contains the card you want to lock out.

Step 3 In the Selected Group list, click the card you want to lock traffic out of.

Step 4 In the Inhibit Switching area, click Lock Out.

Step 5 Click Yes in the confirmation dialog box.

The lockout has been applied and traffic is switched to the opposite card.

Clear a Card or Port Lock-On or Lockout Command

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 In the Protection Groups list, click the protection group that contains the card you want to clear.

Step 3 In the Selected Group list, click the card you want to clear.

Step 4 In the Inhibit Switching area, click Unlock.

Step 5 Click Yes in the confirmation dialog box.

The lock-on or lockout is cleared.

Initiate a 1:1 Card Switch Command

Note The Switch command only works on the active card, whether this card is working or protect. It does not work on the standby card.

Step 1 In node view, click the Maintenance > Protection tabs.

Step 2 Click the protection group that contains the card you want to switch.

Step 3 Under Selected Group, click the active card.

Step 4 Next to Switch Commands, click Switch.

The working slot should change to working/active and the protect slot should change to protect/standby.

Initiate a Force Switch for All Circuits on a Path Protection Span

This procedure forces all circuits in a path protection from the working span to the protect. It is used to remove traffic from a card that originates or terminates path protection circuits.

Caution The Force command overrides normal protective switching mechanisms. Applying this command incorrectly can cause traffic outages.

Caution Traffic is not protected during a Force protection switch.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 3.

Step 2 Click View > Go to Network View.

Step 3 Right-click a network span and choose Circuits.

The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.

Step 4 Click the Perform UPSR span switching field.

Step 5 Choose FORCE SWITCH AWAY from the drop-down list.

Step 6 Click Apply.

Step 7 In the Confirm UPSR Switch dialog box, click Yes.

Step 8 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.

Initiate a Manual Switch for All Circuits on a Path Protection Span

This procedure manually switches all circuits in a path protection from the working span to the protect. It is used to remove traffic from a card that originates or terminates path protection circuits.

Caution The Manual command does not override normal protective switching mechanisms.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Right-click a network span and choose Circuits.

The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.

Step 3 Click the Perform UPSR span switching field.

Step 4 Choose MANUAL from the drop-down list.

Step 5 Click Apply.

Step 6 In the Confirm UPSR Switch dialog box, click Yes.

Step 7 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span dialog box, the switch state for all circuits is MANUAL. Unprotected circuits do not switch.

Initiate a Lock-Out-of-Protect Switch for All Circuits on a Path Protection Span

This procedure prevents all circuits in a path protection working span from switching to the protect span. It is used to keep traffic off cards that originate or terminate path protection circuits.

Caution The Lock Out of Protect command overrides normal protective switching mechanisms.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Right-click a network span and choose Circuits.

The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.

Step 3 Click the Perform UPSR span switching field.

Step 4 Choose LOCK OUT OF PROTECT from the drop-down list.

Step 5 Click Apply.

Step 6 In the Confirm UPSR Switch dialog box, click Yes.

Step 7 In the Protection Switch Result dialog box, click OK.

In the Circuits on Span dialog box, the switch state for all circuits is FORCE. Unprotected circuits do not switch.

Clear a Path Protection Span External Switching Command

Note If the ports terminating a span are configured as revertive, clearing a Force or Manual switch to protect moves traffic back to the working port. If ports are not configured as nonrevertive, clearing a Force switch to protect does not move traffic back.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Right-click a network span and choose Circuits.

The Circuits on Span dialog box shows the path protection circuits, including circuit names, locations, and a color code showing which circuits are active on the span.

Step 3 Initiate a Force switch for all circuits on the span by completing the following steps:

a. Click the Perform UPSR span switching field.

b. Choose CLEAR from the drop-down list.

c. Click Apply.

d. In the Confirm UPSR Switch dialog box, click Yes.

e. In the Protection Switch Result dialog box, click OK.

In the Circuits on Span dialog box, the switch state for all circuits is CLEAR. Unprotected circuits do not switch.

Initiate a Force Ring Switch on a BLSR

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 From the View menu, choose Go to Network View.

Step 3 In network view, click the Provisioning > BLSR tabs.

Step 4 Click the row of the BLSR you are switching, then click Edit.

Step 5 Right-click a BLSR node west port and choose Set West Protection Operation.

Step 6 In the Set West Protection Operation dialog box, choose FORCE RING from the drop-down list.

Step 7 Click OK.

Step 8 Click Yes in the two Confirm BLSR Operation dialog boxes that appear.

Initiate a Manual Ring Switch on a BLSR

Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Provisioning > BLSR tabs.

Step 3 Choose the BLSR and click Edit.

Step 4 Right-click the BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).

Step 5 In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose MANUAL RING from the drop-down list.

Step 6 Click OK.

Step 7 Click Yes in the two Confirm BLSR Operation dialog boxes.

Initiate a Lockout on a BLSR Protect Span

Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Provisioning > BLSR tabs.

Step 3 Choose the BLSR and click Edit.

Step 4 Right-click the BLSR node channel (port) and choose Set West Protection Operation (if you chose a west channel) or Set East Protection Operation (if you chose an east channel).

Step 5 In the Set West Protection Operation dialog box or the Set East Protection Operation dialog box, choose LOCKOUT PROTECT SPAN from the drop-down list.

Step 6 Click OK.

Step 7 Click Yes in the two Confirm BLSR Operation dialog boxes.

Initiate an Exercise Ring Switch on a BLSR

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Click View > Go to Network View.

Step 3 Click the Provisioning > BLSR tabs.

Step 4 Click the row of the BLSR you are exercising, then click Edit.

Step 5 Right-click the west port of a node and choose Set West Protection Operation.

Step 6 In the Set West Protection Operation dialog box, choose EXERCISE RING from the drop-down list.

Step 7 Click OK.

Step 8 Click Yes in the Confirm BLSR Operation dialog box.

Clear a BLSR External Switching Command

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Click View > Go to Network View.

Step 3 Click the Provisioning > BLSR tabs.

Step 4 Click the BLSR you want to clear.

Step 5 Right-click the west port of the BLSR node where you invoked the switch and choose Set West Protection Operation.

Step 6 In the Set West Protection Operation dialog box, choose CLEAR from the drop-down list.

Step 7 Click OK.

Step 8 Click Yes in the Confirm BLSR Operation dialog box.

2.10.3  CTC Card Resetting and Switching

Reset a Traffic Card in CTC

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 In node view, position the cursor over the optical or electrical traffic card slot reporting the alarm.

Step 3 Right-click the card. Choose Reset Card from the shortcut menu.

Step 4 Click Yes in the Resetting Card dialog box.

Reset an Active XTC Card and Activate the Standby Card

Caution Resetting an active XTC card reset can be traffic-affecting.

Note Before you reset the XTC card, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Identify the active XTC card:

If you are looking at the physical ONS 15327 shelf, the ACT/SBY LED of the active card is green. The ACT/STBLY LED of the standby card is amber.

Step 3 Right-click the active XTC card in CTC.

Step 4 Choose Reset Card from the shortcut menu.

Step 5 Click Yes in the Confirmation Dialog box.

The card resets, the FAIL LED blinks on the physical card, and connection to the node is lost. CTC switches to network view.

Step 6 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "ONS 15327 Traffic Card LED Activity" section.

Step 7 Double-click the node and ensure that the reset XTC card is in standby mode and that the other XTC card is active.

•If you are looking at the physical ONS 15327 shelf, the ACT/SBY LED of the active card is green. The ACT/STBLY LED of the standby card is amber.

•No new alarms appear in the Alarms window in CTC.

Side Switch the Active and Standby XTC Cards

Caution The cross-connect card side switch is traffic-affecting.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Display node view.

Step 3 Determine the active or standby XTC card.

The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.

Note You can also position the cursor over the card graphic to display a popup identifying the card as active or standby.

Step 4 In node view, click the Maintenance > Cross-Connect > Cards tabs.

Step 5 Click Switch.

Step 6 Click Yes in the Confirm Switch dialog box. See the "Typical ONS 15327 Cross-Connect LED Activity During Side Switch" section for LED information.

2.10.4  Physical Card Reseating, Resetting, and Replacement

Remove and Reinsert (Reseat) the Standby XTC Card

Caution Do not perform this action without the supervision and direction of Cisco Technical Support (1-800-553-2447).

Caution The XTC card reseat could be traffic-affecting.

Note Before you reset the XTC card, you should wait at least 60 seconds after the last provisioning change you made to avoid losing any changes to the database.

Note When a standby XTC card is removed and reinserted (reseated), all three fan lights could momentarily illuminate, indicating that the fan XTC cards have also reset.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Ensure that the XTC card you want to reseat is in standby mode. A standby card has an amber ACT/SBY (active/standby) LED illuminated.

Step 2 When the XTC card is in standby mode, unlatch both the top and bottom ejectors on the XTC card.

Step 3 Physically pull the card at least partly out of the slot until the lighted LEDs turn off.

Step 4 Wait 30 seconds. Reinsert the card and close the ejectors.

Note The XTC card takes several minutes to reboot and displays the amber standby LED after rebooting. Refer to the Cisco ONS 15327 Procedure Guide for more information about LED behavior during card rebooting.

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.

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. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.

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.

2.10.5  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 In node view, double-click the card reporting the alarm to display the card view.

Step 3 Click the Provisioning > Line tabs.

Step 4 Under the SD BER (or SF BER) column on the Provisioning tab, verify that the cell entry is consistent with the originally provisioned threshold. The default setting is 1E-7.

Step 5 If the entry is consistent with the original provisioning, go back to your original procedure.

Step 6 If the entry is not consistent with what the system was originally provisioned for, click the cell to display the range of choices and click the original entry.

Step 7 Click Apply.

Delete a Circuit

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 In node view, click the Circuits tab.

Step 3 Click the circuit row to highlight it and click Delete.

Step 4 Click Yes in the Delete Circuits dialog box.

Verify or Create Node SDCC Terminations

Note Portions of this procedure are different for ONS 15327 Multiservice Transport Platform (MSTP) nodes.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 In node view, click the Provisioning > Comm Channels > SDCC tabs.

Step 3 View the Port column entries to see where terminations are present for a node. If terminations are missing, proceed to Step 4.

Step 4 If necessary, create a DCC termination by completing the following steps:

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 radio button.

d. Verify that the Disable OSPF on Link check box is unchecked.

e. Click OK.

Clear an OC-N Card Facility or Terminal Loopback Circuit

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > Loopback > Port tabs.

Step 4 In the Loopback Type column, determine whether any port row shows a state other than 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 Admin State column, determine whether any port row shows a state other than IS.

Step 7 If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS.

Step 8 Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Clear an OC-N Card XC Loopback Circuit

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > Loopback > SONET STS tabs.

Step 4 Click Apply.

Clear an XTC Card DS-1 or DS-3 Loopback Circuit

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > DS3 > Loopback tabs or the Maintenance > DS1 > Loopback tabs.

Step 4 In the Loopback Type column, determine whether any port row shows a state other than 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 Admin State column, determine whether any port row shows a state other than IS.

Step 7 If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS.

Step 8 Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Clear a G1000 Card Loopback

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > Loopback tabs.

Step 4 In the Loopback Type column, determine whether any port row shows a state other than 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 Admin State column, determine whether any port row shows a state other than IS.

Step 7 If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS.

Step 8 Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

Clear a CE_100T-8 Ethernet Card Loopback Circuit

This procedure applies to CE_100T-8 cards.

Step 1 Log into a node on the network. If you are already logged in, continue with Step 2.

Step 2 Double-click the reporting card in CTC to display the card view.

Step 3 Click the Maintenance > Loopback tabs.

Step 4 In the Loopback Type column, determine whether any port row shows a state other than 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 Admin State column, determine whether any port row shows a state other than IS, for example, OOS,MT.

Step 7 If a row shows a state other than IS, click in the column cell to display the drop-down list and select IS.

Step 8 Click Apply.

Note If ports managed into IS administrative state are not receiving signals, the LOS alarm is either raised or remains, and the port service state transitions to OOS-AU,FLT.

2.10.6  Air Filter and Fan Procedures

Inspect, Clean, and Replace the Reusable Air Filter

You need a vacuum cleaner or detergent and water faucet, a spare filter, and a pinned hex key.

Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206

Note Although the filter works if it is installed with either side facing up, Cisco recommends that you install it with the metal bracing facing up to preserve the surface of the filter.

Step 1 Verify that you are replacing a reusable air filter. The reusable filter is made of a gray, open-cell, polyurethane foam that is specially coated to provide fire and fungi resistance. NEBS 3E and later versions of the ONS 15327 use a reusable air filter.

Step 2 If the air filter is installed in the external filter brackets, slide the filter out of the brackets while being careful not to dislodge any dust that could have collected on the filter. If the filter is installed beneath the fan tray and not in the external filter brackets:

a. Open the front door of the shelf assembly by completing the following substeps. (If it is already open or if the shelf assembly does not have a front door, continue with Step 3.)

•Open the front door lock.

•Press the door button to release the latch.

•Swing the door open.

b. (Optional) Remove the front door by completing the following substeps:

•Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.

•Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.

•Secure the dangling end of the ground strap to the door or chassis with tape.

Step 3 Push the outer side of the handles on the fan-tray assembly to expose the handles.

Step 4 Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.

Step 5 When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.

Step 6 Gently remove the air filter from the shelf assembly. Be careful not to dislodge any dust that could have collected on the filter.

Step 7 Visually inspect the air filter material for dirt and dust.

Step 8 If the reusable air filter has a concentration of dirt and dust, either vacuum or wash the air filter. Prior to washing the air filter, replace the dirty air filter with a clean air filter and also reinsert the fan-tray assembly. Wash the dirty air filter under a faucet with a light detergent.

Spare ONS 15327 filters should be kept in stock for this purpose.

Note Cleaning should take place outside the operating environment to avoid releasing dirt and dust near the equipment.

Step 9 If you washed the filter, allow it to completely air dry for at least eight hours.

Caution Do not put a damp filter back in the ONS 15327.

Step 10 If the air filter should be installed in the external filter brackets, slide the air filter all the way to the back of the brackets to complete the procedure.

Step 11 If the filter should be installed beneath the fan-tray assembly, remove the fan-tray assembly and slide the air filter into the recessed compartment at the bottom of the shelf assembly. Put the front edge of the air filter flush against the front edge of the recessed compartment. Push the fan tray back into the shelf assembly.

Caution If the fan tray does not slide all the way to the back of the shelf assembly, pull the fan tray out and readjust the position of the reusable filter until the fan tray fits correctly.

Note On a powered-up ONS 15327, the fans start immediately after the fan-tray assembly is correctly inserted.

Step 12 To verify that the tray is plugged into the backplane, ensure that the LCD on the front of the fan-tray assembly is activated and displays node information.

Step 13 Rotate the retractable handles back into their compartments.

Step 14 Replace the door and reattach the ground strap.

Remove and Reinsert a Fan-Tray Assembly

Step 1 Use the retractable handles embedded in the front of the fan-tray assembly to pull it forward several inches.

Step 2 Push the fan-tray assembly firmly back into the ONS 15327.

Step 3 Close the retractable handles.

Replace the Fan-Tray Assembly

Caution Do not force a fan-tray assembly into place. Doing so can damage the connectors on the fan tray and/or the connectors on the backplane.

Note To replace the fan-tray assembly (FTA), it is not necessary to move any of the cable management facilities.

Step 1 Open the front door of the shelf assembly by completing the following steps. If the shelf assembly does not have a front door, continue with Step 3.

a. Open the front door lock.

b. Press the door button to release the latch.

c. Swing the door open.

Step 2 (Optional) Remove the front door by completing the following steps:

a. Detach the ground strap from either the door or the chassis by removing one of the Kepnuts.

b. Place the Kepnut back on the stud after the ground strap is removed to avoid misplacement.

c. Secure the dangling end of the ground strap to the door or chassis with tape.

Step 3 Push the outer side of the handles on the fan-tray assembly to expose the handles.

Step 4 Fold out the retractable handles at the outside edges of the fan tray.

Step 5 Pull the handles and slide the fan-tray assembly one inch (25.4 mm) out of the shelf assembly and wait until the fans stop.

Step 6 When the fans have stopped, pull the fan-tray assembly completely out of the shelf assembly.

Step 7 If you are replacing the fan-tray air filter and it is installed beneath the fan-tray assembly, slide the existing air filter out of the shelf assembly and replace it before replacing the fan-tray assembly.

Step 8 If you are replacing the fan-tray air filter and it is installed in the external bottom bracket, you can slide the existing air filter out of the bracket and replace it at anytime. For more information on the fan-tray air filter, see the "Inspect, Clean, and Replace the Reusable Air Filter" section.

Step 9 Slide the new fan tray into the shelf assembly until the electrical plug at the rear of the tray plugs into the corresponding receptacle on the backplane.

Step 10 To verify that the tray has plugged into the backplane, check that the LCD on the front of the fan tray is activated.

Step 11 If you replace the door, be sure to reattach the ground strap.

2.10.7  Chassis Replacement Procedure

Caution This procedure is Service-Affecting (SA) and should be performed during a maintenance window. All traffic dropped at the NE is affected for the duration of this procedure. It is highly recommended that you reroute traffic to other facilities using the procedures in the "Protection Switching, Lock Initiation, and Clearing" section.

Step 1 Unpack the new chassis by completing the following steps:

a. When you receive the ONS 15327 system equipment at the installation site, open the top of the box. The Cisco Systems logo designates the top of the box.

b. Remove the foam inserts from the box. The box contains the ONS 15327 shelf (wrapped in plastic) and a smaller box containing items needed for installation.

c. Remove the shelf by grasping both sides and slowly lifting it out of the box.

Step 2 Inspect the chassis for any bent or broken pins and ensure that the frame is not bent. (If either of these defects is present, contact Cisco TAC to create a returned material authorization [RMA].)

Step 3 Label all external connections to the NE according to local site practice so they can be reconnected in the same way.

Step 4 Backup the database and log all pertinent information. For procedures, refer to the "Maintain the Node" chapter in the Cisco ONS 15327 Procedure Guide.

Caution Document the current NE MAC listed on the Provisioning > Network > General tab. The MAC address is associated with the chassis and changes when the chassis is replaced. If you do not record the address, circuit repair can be difficult after finishing the hardware replacement.

Step 5 Click the Alarms tab and click Synchronize to view any newly raised alarms relating to this procedure. Resolve them as needed according to the procedures in this chapter.

Step 6 Click the Conditions tab and click Retrieve to view any newly listed conditions relating to this procedure. Resolve them, if necessary, according to the procedures in this chapter.

Step 7 Force traffic away from the NE by the following methods:

a. If the NE is part of a BLSR, complete the "Initiate a Force Ring Switch on a BLSR" procedure for the neighboring nodes. For example, on the node connected to the East span of the defective chassis, force traffic away from the West span. On the node connected to the West Span of the defective chassis, force traffic away from the East Span.

b. If the NE is part of a path protection, complete the "Initiate a Force Switch for All Circuits on a Path Protection Span" procedure on all adjacent nodes for the defective chassis.

Step 8 Power down the NE. For procedures to do this, refer to the "Power Down the Node" chapter in the Cisco ONS 15327 Procedure Guide. You must remove the power feed to the shelf.

Step 9 Remove the existing chassis from the rack by completing the following steps:

a. Disconnect all external connections.

b. Remove all cards from chassis, taking care not to damage any connective interfaces.

c. Remove the chassis from the rack.

Step 10 Install the new chassis. To do this, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide for specific instructions that could be applicable to your site.

Step 11 Connect the PC to the node. To do this, refer to the "Install Hardware" chapter in the Cisco ONS 15327 Procedure Guide for specific instructions that could be applicable to your site.

Step 12 Log into the node.

Step 13 If any CTC sessions were running on this network through other NEs, close and relaunch them.

Step 14 Complete Step 5 for any new alarms.

Step 15 Complete Step 6 for any new conditions.

Step 16 Release any the force switch away using the following steps:

a. If you completed a force ring switch for a BLSR, complete the "Clear a BLSR External Switching Command" procedure.

b. If you completed a force span away switch for a path protection, complete the "Clear a Path Protection Span External Switching Command" procedure.

Step 17 Repair the circuits that have been broken by completing the following steps:

a. Verify that all NEs are visible by completing the "Verify ONS 15327 Node Visibility for Other Nodes" procedure.

b. Click View > Go to Network View.

c. Click the Circuits tab and view the Status column. All circuits terminating at this node should show INCOMPLETE.

d. Click Tools > Circuits > Repair Circuits and follow the prompts. To complete the repair process you need the documented previous MAC address.

e. After finishing the circuit repair, ensure that all circuits in the tab show an ACTIVE status.

Note If an Ethernet circuit does not reach ACTIVE status after the repair process, delete and rebuild it. For detailed instructions to do this, refer to the "Create Circuits and VT Tunnels" chapter in the Cisco ONS 15327 Procedure Guide.