Cisco ONS 15310-CL Troubleshooting Guide, Release 6.0
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 1.42MB) The complete bookPDF (PDF - 5.8MB) | Feedback

Alarm Troubleshooting

Table Of Contents

Alarm Troubleshooting

2.1  Alarm Index by Default Severity

2.1.1  Critical Alarms (CR)

2.1.2  Major Alarms (MJ)

2.1.3  Minor Alarms (MN)

2.1.4  Not Alarmed Conditions

2.1.5  Not Reported (NR) Conditions

2.2  Alarms and Conditions Indexed 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-END

2.7.7  APSB

Clear the APSB Alarm

2.7.8  APSCDFLTK

2.7.9  APSC-IMP

2.7.10  APSCINCON

Clear the APSCINCON Alarm

2.7.11  APSCM

Clear the APSCM Alarm

2.7.12  APSCNMIS

2.7.13  APSIMP

Clear the APSIMP Alarm

2.7.14  APS-INV-PRIM

2.7.15  APSMM

Clear the APSMM Alarm

2.7.16  APS-PRIM-FAC

2.7.17  APS-PRIM-SEC-MISM

2.7.18  AS-CMD

Clear the AS-CMD Condition

2.7.19  AS-MT

Clear the AS-MT Condition

2.7.20  AS-MT-OOG

2.7.21  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.22  AUD-LOG-LOW

2.7.23  AUTOLSROFF

2.7.24  AUTORESET

Clear the AUTORESET Alarm

2.7.25  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.7.26  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.7.27  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Alarm

2.7.28  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.7.29  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.7.30  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.7.31  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.7.32  AUTOSW-UNEQ (VT-MON)

Clear the AUTOSW-UNEQ (VT-MON) Alarm

2.7.33  BAT-FAIL

Clear the BAT-FAIL Alarm

2.7.34  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.35  BLSROSYNC

2.7.36  CARLOSS (CE100T)

Clear the CARLOSS (CE100T) Alarm

2.7.37  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.38  CLDRESTART

Clear the CLDRESTART Condition

2.7.39  COMIOXC

Clear the COMIOXC Alarm

2.7.40  CONTBUS-DISABLED

Clear the CONTBUS-DISABLED Alarm

2.7.41  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.42  CTNEQPT-PBPROT

2.7.43  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.44  DATAFLT

Clear the DATAFLT Alarm

2.7.45  DS3-MISM

Clear the DS3-MISM Condition

2.7.46  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.47  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.48  EHIBATVG

Clear the EHIBATVG Alarm

2.7.49  ELWBATVG

Clear the ELWBATVG Alarm

2.7.50  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.7.51   EOC

Clear the EOC Alarm

2.7.52  EOC-L

Clear the EOC-L Alarm

2.7.53  EQPT

Clear the EQPT Alarm

2.7.54  EQPT-MISS

2.7.55  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.7.56  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.7.57  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.7.58  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.59  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.60  E-W-MISMATCH

2.7.61  EXCCOL

Clear the EXCCOL Alarm

2.7.62  EXT

Clear the EXT Alarm

2.7.63  EXTRA-TRAF-PREEMPT

2.7.64  FAILTOSW

Clear the FAILTOSW Condition

2.7.65  FAILTOSW-PATH

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration

2.7.66  FAN

2.7.67  FAN-DEGRADE

2.7.68  FE-AIS

Clear the FE-AIS Condition

2.7.69  FE-DS1-MULTLOS

2.7.70  FE-DS1-NSA

2.7.71  FE-DS1-SA

2.7.72  FE-DS1-SNGLLOS

2.7.73  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.7.74  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.7.75  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.76  FE-FRCDWKSWBK-SPAN

2.7.77  FE-FRCDWKSWPR-SPAN

2.7.78  FE-IDLE

Clear the FE-IDLE Condition

2.7.79  FE-LOCKOUTOFPR-SPAN

2.7.80  FE-LOF

Clear the FE-LOF Condition

2.7.81  FE-LOS

Clear the FE-LOS Condition

2.7.82  FE-MANWKSWBK-SPAN

2.7.83  FE-MANWKSWPR-SPAN

2.7.84  FEPRLF

Clear the FEPRLF Alarm

2.7.85  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.86  FORCED-REQ-SPAN

Clear the FORCED-REQ-SPAN Condition

2.7.87  FRCDSWTOINT

2.7.88  FRCDSWTOPRI

2.7.89  FRCDSWTOSEC

2.7.90  FRCDSWTOTHIRD

2.7.91  FRNGSYNC

Clear the FRNGSYNC Condition

2.7.92  FSTSYNC

2.7.93  FULLPASSTHR-BI

2.7.94  GFP-CSF

Clear the GFP-CSF Alarm

2.7.95  GFP-LFD

Clear the GFP-LFD Alarm

2.7.96  GFP-UP-MISMATCH

Clear the GFP-UP-MISMATCH Alarm

2.7.97  HELLO

Clear the HELLO Alarm

2.7.98  HIBATVG

Clear the HIBATVG Alarm

2.7.99  HI-LASERBIAS

Clear the HI-LASERBIAS Alarm

2.7.100  HI-LASERTEMP

Clear the HI-LASERTEMP Alarm

2.7.101  HI-RXPOWER

Clear the HI-RXPOWER Alarm

2.7.102  HITEMP

Clear the HITEMP Alarm

2.7.103  HI-TXPOWER

Clear the HI-TXPOWER Alarm

2.7.104  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.105  I-HITEMP

Clear the I-HITEMP Alarm

2.7.106  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.107  INC-ISD

2.7.108  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.109  INVMACADR

2.7.110  IOSCFGCOPY

2.7.111  ISIS-ADJ-FAIL

Clear the ISIS-ADJ-FAIL Alarm

2.7.112  KB-PASSTHR

2.7.113  LASEREOL

2.7.114  LCAS-CRC

Clear the LCAS-CRC Condition

2.7.115  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.7.116  LCAS-TX-ADD

2.7.117  LCAS-TX-DNU

2.7.118  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.119  LOA

Clear the LOA Alarm

2.7.120  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.121  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.122  LOF (DS1)

Clear the LOF (DS1) Alarm

2.7.123  LOF (DS3)

Clear the LOF (DS3) Alarm

2.7.124  LOF (EC1)

Clear the LOF (EC1) Alarm

2.7.125  LOF (OCN)

Clear the LOF (OCN) Alarm

2.7.126  LO-LASERBIAS

2.7.127  LO-LASERTEMP

2.7.128  LOM

Clear the LOM Alarm

2.7.129  LOP-P

Clear the LOP-P Alarm

2.7.130  LOP-V

Clear the LOP-V Alarm

2.7.131  LO-RXPOWER

Clear the LO-RXPOWER Alarm

2.7.132  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.133  LOS (DS1)

Clear the LOS (DS1) Alarm

2.7.134  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.135  LOS (EC1)

Clear the LOS (EC1) Alarm

2.7.136  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.137  LOS (OCN)

Clear the LOS (OCN) Alarm

2.7.138  LO-TXPOWER

Clear the LO-TXPOWER Alarm

2.7.139  LPBKCRS

Clear the LPBKCRS Condition

2.7.140  LPBKDS1FEAC

Clear the LPBKDS1FEAC Condition

2.7.141  LPBKDS1FEAC-CMD

2.7.142  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.143  LPBKDS3FEAC-CMD

2.7.144  LPBKFACILITY (CE100T)

Clear the LPBKFACILITY (CE100T) Condition

2.7.145  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.146  LPBKFACILITY (EC1)

Clear the LPBKFACILITY (EC1) Condition

2.7.147  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.7.148  LPKTERMINAL (CE100T)

Clear the LPBKTERMINAL (CE100T) Condition

2.7.149  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.7.150  LPBKTERMINAL (EC1)

Clear the LPBKTERMINAL (EC1) Condition

2.7.151  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.7.152  LWBATVG

Clear the LWBATVG Alarm

2.7.153  MAN-REQ

Clear the MAN-REQ Condition

2.7.154  MANRESET

2.7.155  MANSWTOINT

2.7.156  MANSWTOPRI

2.7.157  MANSWTOSEC

2.7.158  MANSWTOTHIRD

2.7.159  MANUAL-REQ-SPAN

Clear the MANUAL-REQ-SPAN Condition

2.7.160  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.161  MEA (FAN)

2.7.162  MEA (PPM)

Clear the MEA (PPM) Alarm

2.7.163  MEM-GONE

2.7.164  MEM-LOW

2.7.165  MFGMEM

2.7.166  NO-CONFIG

Clear the NO-CONFIG Condition

2.7.167  NOT-AUTHENTICATED

2.7.168  OOU-TPT

Clear the OOT-TPT Condition

2.7.169  OPEN-SLOT

2.7.170  PDI-P

Clear the PDI-P Condition

2.7.171  PLM-P

Clear the PLM-P Alarm

2.7.172  PLM-V

Clear the PLM-V Alarm

2.7.173  PRC-DUPID

2.7.174  PROTNA

2.7.175  PROV-MISMATCH

Clear the PROV-MISMATCH Alarm

2.7.176  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.177  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.178  RAI

Clear the RAI Condition

2.7.179  RFI-L

Clear the RFI-L Condition

2.7.180  RFI-P

Clear the RFI-P Condition

2.7.181  RFI-V

Clear the RFI-V Condition

2.7.182  ROLL

2.7.183  ROLL-PEND

2.7.184  RPRW

Clear the RPRW Condition

2.7.185  RUNCFG-SAVENEED

2.7.186  SD

Clear the SD (DS1, DS3) Condition

2.7.187  SD-L

Clear the SD-L Condition

2.7.188  SD-P

Clear the SD-P Condition

2.7.189  SD-V

Clear the SD-V Condition

2.7.190  SF

Clear the SF (DS1, DS3) Condition

2.7.191  SF-L

Clear the SF-L Condition

2.7.192  SF-P

Clear the SF-P Condition

2.7.193  SFTWDOWN

2.7.194  SF-V

Clear the SF-V Condition

2.7.195  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.196  SQUELCH

2.7.197  SQUELCHED

2.7.198  SQM

Clear the SQM Alarm

2.7.199  SSM-DUS

2.7.200  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.201  SSM-OFF

Clear the SSM-OFF Condition

2.7.202  SSM-PRS

2.7.203  SSM-RES

2.7.204  SSM-SMC

2.7.205  SSM-ST2

2.7.206  SSM-ST3

2.7.207  SSM-ST3E

2.7.208  SSM-ST4

2.7.209  SSM-STU

Clear the SSM-STU Condition

2.7.210  SSM-TNC

2.7.211  SW-MISMATCH

2.7.212  SWMTXMOD-PROT

2.7.213  SWMTXMOD-WORK

Clear the SWMTXMOD-WORK Alarm

2.7.214  SWTOPRI

2.7.215  SWTOSEC

Clear the SWTOSEC Condition

2.7.216  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.7.217  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.218  SYNCPRI

Clear the SYNCPRI Alarm

2.7.219  SYNCSEC

Clear the SYNCSEC Alarm

2.7.220  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.221  SYSBOOT

2.7.222  TIM

Clear the TIM Alarm

2.7.223  TIM-MON

2.7.224  TIM-P

Clear the TIM-P Alarm

2.7.225  TIM-S

Clear the TIM-S Alarm

2.7.226  TIM-V

Clear the TIM-V Alarm

2.7.227  TPTFAIL (CE100T)

Clear the TPTFAIL (CE100T) Alarm

2.7.228  TX-AIS

2.7.229  TX-LOF

2.7.230  TX-RAI

2.7.231  UNEQ-P

Clear the UNEQ-P Alarm

2.7.232  UNEQ-V

Clear the UNEQ-V Alarm

2.7.233  VCG-DEG

Clear the VCG-DEG Condition

2.7.234  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.235  WKSWPR

Clear the WKSWPR Condition

2.7.236  WTR

2.8  15310-CL-CTX Line Alarms

2.9  ONS 15310-CL Traffic Card LED Activity

2.9.1  Typical 155310-CL-CTX Card or Ethernet Card LED Activity After Insertion

2.9.2  Typical 15310-CL-CTX Card or Ethernet Card LED Activity During Reset

2.10  Frequently Used Alarm Troubleshooting Procedures

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

2.10.2  CTC Card Resetting and Switching

Soft- or Hard-Reset an Ethernet Card in CTC

Soft- or Hard-Reset a 15310-CL-CTX Card

2.10.3  Physical Card Reseating and Replacement

Remove and Reinsert (Reseat) an Ethernet Card

Physically Replace an Ethernet Card

2.10.4  Generic Signal and Circuit Procedures

Verify the Signal BER Threshold Level

Delete a Circuit

Verify or Create Node DCC Terminations

Clear an OC-N Port Facility or Terminal Loopback Circuit

Clear an OC-N Port XC Loopback Circuit

Clear a DS-3 or DS-1 Port Loopback Circuit

Clear an EC-1 Port Loopback

Clear an Ethernet Card Loopback Circuit


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 15310-CL alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15310-CL alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all ONS 15310-CL 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 SONET TL1 Command Guide. For further information about Transaction Language One (TL1), refer to the Cisco ONS SONET TL1 Reference Guide.

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

More information about alarm profile information modification and downloads is located in the "Manage Alarms" chapter in the Cisco ONS 15310-CL Procedure Guide.

2.1  Alarm Index by Default Severity

The following tables group alarms and conditions by their default severities in the ONS 15310-CL 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, Major/Minor [MJ/MN]). The ONS 15310-CL 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 15310-CL Critical (CR) alarms.

Table 2-1 ONS 15310-CL Critical Alarm List 

AUTOLSROFF (OCN)

LOF (DS3)

MFGMEM (FAN)

BKUPMEMP (EQPT)

LOF (EC1)

MFGMEM (PPM)

COMIOXC (EQPT)

LOF (OCN)

PLM-P (STSMON)

CTNEQPT-PBPROT (EQPT)

LOF (STSTRM)

PLM-P (STSTRM)

CTNEQPT-PBWORK (EQPT)

LOM (STSMON)

SQM (STSTRM)

ENCAP-MISMATCH-P (STSTRM)

LOP-P (STSMON)

SWMTXMOD-PROT (EQPT)

EQPT (EQPT)

LOP-P (STSTRM)

SWMTXMOD-WORK (EQPT)

EQPT (PPM)

LOS (DS3)

TIM (OCN)

EQPT-MISS (FAN)

LOS (EC1)

TIM-P (STSTRM)

FAN (FAN)

LOS (OCN)

TIM-S (EC1)

HITEMP (NE)

MEA (EQPT)

TIM-S (OCN)

I-HITEMP (NE)

MEA (FAN)

UNEQ-P (STSMON)

IMPROPRMVL (EQPT)

MEA (PPM)

UNEQ-P (STSTRM)

IMPROPRMVL (PPM)

MFGMEM (BPLANE)

CONTBUS-DISABLED (EQPT)

LOA (VCG)


2.1.2  Major Alarms (MJ)

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

Table 2-2 ONS 15310-CL Major Alarm List 

APSCM (OCN)

GFP-CSF (CE100T)

LWBATVG (PWR)

APSCNMIS (OCN)

GFP-LFD (CE100T)

MEM-GONE (EQPT)

BAT-FAIL (PWR)

GFP-UP-MISMATCH (CE100T)

PLM-V (VT-TERM)

BLSROSYNC (OCN)

HIBATVG (PWR)

PRC-DUPID (OCN)

CARLOSS (CE100T)

INVMACADR (BPLANE)

SQM (VT-TERM)

CARLOSS (EQPT)

LOF (DS1)

SYNCPRI (NE-SREF)

EHIBATVG (PWR)

LOM (STSTRM)

SYSBOOT (NE)

ELWBATVG (PWR)

LOM (VT-TERM)

TIM-V (VT-TERM)

E-W-MISMATCH (OCN)

LOP-V (VT-MON)

TPTFAIL (CE100T)

EXTRA-TRAF-PREEMPT (OCN)

LOP-V (VT-TERM)

UNEQ-V (VT-MON)

FANDEGRADE (FAN)

LOS (DS1)

UNEQ-V (VT-TERM)


2.1.3  Minor Alarms (MN)

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

Table 2-3 ONS 15310-CL Minor Alarm List 

APSB (OCN)

HELLO (OCN)

LO-TXPOWER (OCN)

APSCDFLTK (OCN)

HI-LASERBIAS (OCN)

LO-TXPOWER (PPM)

APSC-IMP (OCN)

HI-LASERBIAS (PPM)

MEM-LOW (EQPT)

APSCINCON (OCN)

HI-LASERTEMP (OCN)

PROTNA (EQPT)

APSIMP (OCN)

HI-LASERTEMP (PPM)

PROV-MISMATCH (PPM)

APS-INV-PRIM (OCN)

HI-RXPOWER (OCN)

PWR-FAIL-A (EQPT)

APSMM (OCN)

HITEMP (EQPT)

PWR-FAIL-B (EQPT)

APS-PRIM-SEC-MISM (OCN)

HI-TXPOWER (OCN)

SFTWDOWN (EQPT)

AUTORESET (EQPT)

HI-TXPOWER (PPM)

SNTP-HOST (NE)

AUTOSW-UNEQ (VT-MON)

ISIS-ADJ-FAIL (OCN)

SSM-FAIL (BITS)

CONTBUS-IO-A (EQPT)

LASEREOL (OCN)

SSM-FAIL (DS1)

DATAFLT (NE)

LOF (BITS)

SSM-FAIL (OCN)

DUP-IPADDR (NE)

LO-LASERBIAS (OCN)

SYNCPRI (EXT-SREF)

DUP-NODENAME (NE)

LO-LASERBIAS (PPM)

SYNCSEC (EXT-SREF)

EOC (OCN)

LO-LASERTEMP (OCN)

SYNCSEC (NE-SREF)

EOC-L (OCN)

LO-LASERTEMP (PPM)

SYNCTHIRD (EXT-SREF)

ERROR-CONFIG (EQPT)

LO-RXPOWER (OCN)

SYNCTHIRD (NE-SREF)

EXCCOL (EQPT)

LOS (BITS)

TIM-MON (OCN)

EXT (ENVALRM)

LOS (FUDC)

TIM-P (STSMON)

FEPRLF (OCN)


2.1.4  Not Alarmed Conditions

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

Table 2-4 ONS 15310-CL NA Conditions List 

ALS (OCN)

INTRUSION-PSWD (NE)

SF-L (OCN)

APC-END (NE)

IOSCFGCOPY (EQPT)

SF-P (STSMON)

APS-PRIM-FAC (OCN)

KB-PASSTHR (OCN)

SF-P (STSTRM)

AS-CMD (BPLANE)

LCAS-CRC (STSTRM)

SF-V (VT-MON)

AS-CMD (CE100T)

LCAS-CRC (VT-TERM)

SF-V (VT-TERM)

AS-CMD (DS1)

LCAS-RX-FAIL (STSTRM)

SQUELCH (OCN)

AS-CMD (DS3)

LCAS-RX-FAIL (VT-TERM)

SQUELCHED (OCN)

AS-CMD (EC1)

LCAS-TX-ADD (STSTRM)

SSM-DUS (BITS)

AS-CMD (EQPT)

LCAS-TX-ADD (VT-TERM)

SSM-DUS (DS1)

AS-CMD (NE)

LCAS-TX-DNU (STSTRM)

SSM-DUS (OCN)

AS-CMD (OCN)

LCAS-TX-DNU (VT-TERM)

SSM-OFF (BITS)

AS-CMD (PPM)

LKOUTPR-S (OCN)

SSM-OFF (DS1)

AS-CMD (PWR)

LOCKOUT-REQ (OCN)

SSM-OFF (OCN)

AS-MT (CE100T)

LOCKOUT-REQ (STSMON)

SSM-PRS (BITS)

AS-MT (DS1)

LOCKOUT-REQ (VT-MON)

SSM-PRS (DS1)

AS-MT (DS3)

LPBKCRS (STSMON)

SSM-PRS (NE-SREF)

AS-MT (EC1)

LPBKCRS (STSTRM)

SSM-PRS (OCN)

AS-MT (EQPT)

LPBKDS1FEAC-CMD (DS1)

SSM-RES (BITS)

AS-MT (OCN)

LPBKDS3FEAC (DS3)

SSM-RES (DS1)

AS-MT (PPM)

LPBKDS3FEAC-CMD (DS3)

SSM-RES (NE-SREF)

AS-MT-OOG (STSTRM)

LPBKFACILITY (CE100T)

SSM-RES (OCN)

AS-MT-OOG (VT-TERM)

LPBKFACILITY (DS1)

SSM-SMC (BITS)

AUD-LOG-LOSS (NE)

LPBKFACILITY (DS3)

SSM-SMC (DS1)

AUD-LOG-LOW (NE)

LPBKFACILITY (EC1)

SSM-SMC (NE-SREF)

AUTOSW-LOP (STSMON)

LPBKFACILITY (OCN)

SSM-SMC (OCN)

AUTOSW-LOP (VT-MON)

LPBKTERMINAL (CE100T)

SSM-ST2 (BITS)

AUTOSW-PDI (STSMON)

LPBKTERMINAL (DS1)

SSM-ST2 (DS1)

AUTOSW-SDBER (STSMON)

LPBKTERMINAL (DS3)

SSM-ST2 (NE-SREF)

AUTOSW-SFBER (STSMON)

LPBKTERMINAL (EC1)

SSM-ST2 (OCN)

AUTOSW-UNEQ (STSMON)

LPBKTERMINAL (OCN)

SSM-ST3 (BITS)

CLDRESTART (EQPT)

MAN-REQ (STSMON)

SSM-ST3 (DS1)

DS3-MISM (DS3)

MAN-REQ (VT-MON)

SSM-ST3 (NE-SREF)

ETH-LINKLOSS (NE)

MANRESET (EQPT)

SSM-ST3 (OCN)

FAILTOSW (OCN)

MANSWTOINT (NE-SREF)

SSM-ST3E (BITS)

FAILTOSW-PATH (STSMON)

MANSWTOPRI (EXT-SREF)

SSM-ST3E (DS1)

FAILTOSW-PATH (VT-MON)

MANSWTOPRI (NE-SREF)

SSM-ST3E (NE-SREF)

FE-AIS (DS3)

MANSWTOSEC (EXT-SREF)

SSM-ST3E (OCN)

FE-DS1-MULTLOS (DS3)

MANSWTOSEC (NE-SREF)

SSM-ST4 (BITS)

FE-DS1-NSA (DS3)

MANSWTOTHIRD (EXT-SREF)

SSM-ST4 (DS1)

FE-DS1-SA (DS3)

MANSWTOTHIRD (NE-SREF)

SSM-ST4 (NE-SREF)

FE-DS1-SNGLLOS (DS3)

MANUAL-REQ-SPAN (OCN)

SSM-ST4 (OCN)

FE-DS3-NSA (DS3)

NO-CONFIG (EQPT)

SSM-STU (BITS)

FE-DS3-SA (DS3)

OOU-TPT (STSTRM)

SSM-STU (DS1)

FE-EQPT-NSA (DS3)

OOU-TPT (VT-TERM)

SSM-STU (NE-SREF)

FE-FRCDWKSWBK-SPAN (OCN)

OPEN-SLOT (EQPT)

SSM-STU (OCN)

FE-FRCDWKSWPR-SPAN (OCN)

PDI-P (STSMON)

SSM-TNC (BITS)

FE-IDLE (DS3)

PDI-P (STSTRM)

SSM-TNC (NE-SREF)

FE-LOCKOUTOFPR-SPAN (OCN)

RAI (DS1)

SSM-TNC (OCN)

FE-LOF (DS3)

RAI (DS3)

SW-MISMATCH (EQPT)

FE-LOS (DS3)

RFI-V (VT-MON)

SWTOPRI (EXT-SREF)

FE-MANWKSWBK-SPAN (OCN)

ROLL (STSMON)

SWTOPRI (NE-SREF)

FE-MANWKSWPR-SPAN (OCN)

ROLL (STSTRM)

SWTOSEC (EXT-SREF)

FORCED-REQ (EQPT)

ROLL (VT-MON)

SWTOSEC (NE-SREF)

FORCED-REQ (STSMON)

ROLL-PEND (STSMON)

SWTOTHIRD (EXT-SREF)

FORCED-REQ (VT-MON)

ROLL-PEND (VT-MON)

SWTOTHIRD (NE-SREF)

FORCED-REQ-SPAN (OCN)

RPRW (CE100T)

SYNC-FREQ (BITS)

FRCDSWTOINT (NE-SREF)

RUNCFG-SAVENEED (EQPT)

SYNC-FREQ (DS1)

FRCDSWTOPRI (EXT-SREF)

SD (DS1)

SYNC-FREQ (OCN)

FRCDSWTOPRI (NE-SREF)

SD (DS3)

TX-RAI (DS3)

FRCDSWTOSEC (EXT-SREF)

SD-L (EC1)

VCG-DEG (VCG)

FRCDSWTOSEC (NE-SREF)

SD-L (OCN)

VCG-DOWN (VCG)

FRCDSWTOTHIRD (EXT-SREF)

SD-P (STSMON)

WKSWPR (OCN)

FRCDSWTOTHIRD (NE-SREF)

SD-P (STSTRM)

WKSWPR (STSMON)

FRNGSYNC (NE-SREF)

SD-V (VT-MON)

WKSWPR (VT-MON)

FSTSYNC (NE-SREF)

SD-V (VT-TERM)

WTR (EQPT)

FULLPASSTHR-BI (OCN)

SF (DS1)

WTR (OCN)

HLDOVRSYNC (NE-SREF)

SF (DS3)

WTR (STSMON)

INC-ISD (DS3)

SF-L (EC1)

WTR (VT-MON)


2.1.5  Not Reported (NR) Conditions

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

Table 2-5 ONS 15310-CL NR Conditions List 

AIS (BITS)

AIS-V (VT-TERM)

RFI-L (EC1)

AIS (DS1)

AUTOSW-AIS (STSMON)

RFI-L (OCN)

AIS (DS3)

AUTOSW-AIS (VT-MON)

RFI-P (STSMON)

AIS (FUDC)

ERFI-P-CONN (STSMON)

RFI-P (STSTRM)

AIS-L (EC1)

ERFI-P-CONN (STSTRM)

RFI-V (VT-TERM)

AIS-L (OCN)

ERFI-P-PAYLD (STSMON)

ROLL-PEND (STSTRM)

AIS-P (STSMON)

ERFI-P-PAYLD (STSTRM)

TX-AIS (DS3)

AIS-P (STSTRM)

ERFI-P-SRVR (STSMON)

TX-LOF (DS1)

AIS-V (VT-MON)

ERFI-P-SRVR (STSTRM)


2.2  Alarms and Conditions Indexed By Alphabetical Entry

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

Table 2-6 ONS 15310-CL Alarm and Condition Alphabetical List 

AIS (BITS)

FRCDSWTOTHIRD (NE-SREF)

RFI-P (STSMON)

AIS (DS1)

FRNGSYNC (NE-SREF)

RFI-P (STSTRM)

AIS (DS3)

FSTSYNC (NE-SREF)

RFI-V (VT-MON)

AIS (FUDC)

FULLPASSTHR-BI (OCN)

RFI-V (VT-TERM)

AIS-L (EC1)

GFP-CSF (CE100T)

ROLL (STSMON)

AIS-L (OCN)

GFP-LFD (CE100T)

ROLL (STSTRM)

AIS-P (STSMON)

GFP-UP-MISMATCH (CE100T)

ROLL (VT-MON)

AIS-P (STSTRM)

HELLO (OCN)

ROLL-PEND (STSMON)

AIS-V (VT-MON)

HIBATVG (PWR)

ROLL-PEND (STSTRM)

AIS-V (VT-TERM)

HI-LASERBIAS (OCN)

ROLL-PEND (VT-MON)

ALS (OCN)

HI-LASERBIAS (PPM)

RPRW (CE100T)

APC-END (NE)

HI-LASERTEMP (OCN)

RUNCFG-SAVENEED (EQPT)

APSB (OCN)

HI-LASERTEMP (PPM)

SD (DS1)

APSCDFLTK (OCN)

HI-RXPOWER (OCN)

SD (DS3)

APSC-IMP (OCN)

HITEMP (EQPT)

SD-L (EC1)

APSCINCON (OCN)

HITEMP (NE)

SD-L (OCN)

APSCM (OCN)

HI-TXPOWER (OCN)

SD-P (STSMON)

APSCNMIS (OCN)

HI-TXPOWER (PPM)

SD-P (STSTRM)

APSIMP (OCN)

HLDOVRSYNC (NE-SREF)

SD-V (VT-MON)

APS-INV-PRIM (OCN)

I-HITEMP (NE)

SD-V (VT-TERM)

APSMM (OCN)

IMPROPRMVL (EQPT)

SF (DS1)

APS-PRIM-FAC (OCN)

IMPROPRMVL (PPM)

SF (DS3)

APS-PRIM-SEC-MISM (OCN)

INC-ISD (DS3)

SF-L (EC1)

AS-CMD (BPLANE)

INTRUSION-PSWD (NE)

SF-L (OCN)

AS-CMD (CE100T)

INVMACADR (BPLANE)

SF-P (STSMON)

AS-CMD (DS1)

IOSCFGCOPY (EQPT)

SF-P (STSTRM)

AS-CMD (DS3)

ISIS-ADJ-FAIL (OCN)

SFTWDOWN (EQPT)

AS-CMD (EC1)

KB-PASSTHR (OCN)

SF-V (VT-MON)

AS-CMD (EQPT)

LASEREOL (OCN)

SF-V (VT-TERM)

AS-CMD (NE)

LCAS-CRC (STSTRM)

SNTP-HOST (NE)

AS-CMD (OCN)

LCAS-CRC (VT-TERM)

SQM (STSTRM)

AS-CMD (PPM)

LCAS-RX-FAIL (STSTRM)

SQM (VT-TERM)

AS-CMD (PWR)

LCAS-RX-FAIL (VT-TERM)

SQUELCH (OCN)

AS-MT (CE100T)

LCAS-TX-ADD (STSTRM)

SQUELCHED (OCN)

AS-MT (DS1)

LCAS-TX-ADD (VT-TERM)

SSM-DUS (BITS)

AS-MT (DS3)

LCAS-TX-DNU (STSTRM)

SSM-DUS (DS1)

AS-MT (EC1)

LCAS-TX-DNU (VT-TERM)

SSM-DUS (OCN)

AS-MT (EQPT)

LKOUTPR-S (OCN)

SSM-FAIL (BITS)

AS-MT (OCN)

LOA (VCG)

SSM-FAIL (DS1)

AS-MT (PPM)

LOCKOUT-REQ (OCN)

SSM-FAIL (OCN)

AS-MT-OOG (STSTRM)

LOCKOUT-REQ (STSMON)

SSM-OFF (BITS)

AS-MT-OOG (VT-TERM)

LOCKOUT-REQ (VT-MON)

SSM-OFF (DS1)

AUD-LOG-LOSS (NE)

LOF (BITS)

SSM-OFF (OCN)

AUD-LOG-LOW (NE)

LOF (DS1)

SSM-PRS (BITS)

AUTOLSROFF (OCN)

LOF (DS3)

SSM-PRS (DS1)

AUTORESET (EQPT)

LOF (EC1)

SSM-PRS (NE-SREF)

AUTOSW-AIS (STSMON)

LOF (OCN)

SSM-PRS (OCN)

AUTOSW-AIS (VT-MON)

LOF (STSTRM)

SSM-RES (BITS)

AUTOSW-LOP (STSMON)

LO-LASERBIAS (OCN)

SSM-RES (DS1)

AUTOSW-LOP (VT-MON)

LO-LASERBIAS (PPM)

SSM-RES (NE-SREF)

AUTOSW-PDI (STSMON)

LO-LASERTEMP (OCN)

SSM-RES (OCN)

AUTOSW-SDBER (STSMON)

LO-LASERTEMP (PPM)

SSM-SMC (BITS)

AUTOSW-SFBER (STSMON)

LOM (STSMON)

SSM-SMC (DS1)

AUTOSW-UNEQ (STSMON)

LOM (STSTRM)

SSM-SMC (NE-SREF)

AUTOSW-UNEQ (VT-MON)

LOM (VT-TERM)

SSM-SMC (OCN)

BAT-FAIL (PWR)

LOP-P (STSMON)

SSM-ST2 (BITS)

BKUPMEMP (EQPT)

LOP-P (STSTRM)

SSM-ST2 (DS1)

BLSROSYNC (OCN)

LOP-V (VT-MON)

SSM-ST2 (NE-SREF)

CARLOSS (CE100T)

LOP-V (VT-TERM)

SSM-ST2 (OCN)

CARLOSS (EQPT)

LO-RXPOWER (OCN)

SSM-ST3 (BITS)

CLDRESTART (EQPT)

LOS (BITS)

SSM-ST3 (DS1)

COMIOXC (EQPT)

LOS (DS1)

SSM-ST3 (NE-SREF)

CONTBUS-DISABLED (EQPT)

LOS (DS3)

SSM-ST3 (OCN)

CONTBUS-IO-A (EQPT)

LOS (EC1)

SSM-ST3E (BITS)

CTNEQPT-PBPROT (EQPT)

LOS (FUDC)

SSM-ST3E (DS1)

CTNEQPT-PBWORK (EQPT)

LOS (OCN)

SSM-ST3E (NE-SREF)

DATAFLT (NE)

LO-TXPOWER (OCN)

SSM-ST3E (OCN)

DS3-MISM (DS3)

LO-TXPOWER (PPM)

SSM-ST4 (BITS)

DUP-IPADDR (NE)

LPBKCRS (STSMON)

SSM-ST4 (DS1)

DUP-NODENAME (NE)

LPBKCRS (STSTRM)

SSM-ST4 (NE-SREF)

EHIBATVG (PWR)

LPBKDS1FEAC-CMD (DS1)

SSM-ST4 (OCN)

ELWBATVG (PWR)

LPBKDS3FEAC (DS3)

SSM-STU (BITS)

ENCAP-MISMATCH-P (STSTRM)

LPBKDS3FEAC-CMD (DS3)

SSM-STU (DS1)

EOC (OCN)

LPBKFACILITY (CE100T)

SSM-STU (NE-SREF)

EOC-L (OCN)

LPBKFACILITY (DS1)

SSM-STU (OCN)

EQPT (EQPT)

LPBKFACILITY (DS3)

SSM-TNC (BITS)

EQPT (PPM)

LPBKFACILITY (EC1)

SSM-TNC (NE-SREF)

EQPT-MISS (FAN)

LPBKFACILITY (OCN)

SSM-TNC (OCN)

ERFI-P-CONN (STSMON)

LPBKTERMINAL (CE100T)

SW-MISMATCH (EQPT)

ERFI-P-CONN (STSTRM)

LPBKTERMINAL (DS1)

SWMTXMOD-PROT (EQPT)

ERFI-P-PAYLD (STSMON)

LPBKTERMINAL (DS3)

SWMTXMOD-WORK (EQPT)

ERFI-P-PAYLD (STSTRM)

LPBKTERMINAL (EC1)

SWTOPRI (EXT-SREF)

ERFI-P-SRVR (STSMON)

LPBKTERMINAL (OCN)

SWTOPRI (NE-SREF)

ERFI-P-SRVR (STSTRM)

LWBATVG (PWR)

SWTOSEC (EXT-SREF)

ERROR-CONFIG (EQPT)

MAN-REQ (STSMON)

SWTOSEC (NE-SREF)

ETH-LINKLOSS (NE)

MAN-REQ (VT-MON)

SWTOTHIRD (EXT-SREF)

E-W-MISMATCH (OCN)

MANRESET (EQPT)

SWTOTHIRD (NE-SREF)

EXCCOL (EQPT)

MANSWTOINT (NE-SREF)

SYNC-FREQ (BITS)

EXT (ENVALRM)

MANSWTOPRI (EXT-SREF)

SYNC-FREQ (DS1)

EXTRA-TRAF-PREEMPT (OCN)

MANSWTOPRI (NE-SREF)

SYNC-FREQ (OCN)

FAILTOSW (OCN)

MANSWTOSEC (EXT-SREF)

SYNCPRI (EXT-SREF)

FAILTOSW-PATH (STSMON)

MANSWTOSEC (NE-SREF)

SYNCPRI (NE-SREF)

FAILTOSW-PATH (VT-MON)

MANSWTOTHIRD (EXT-SREF)

SYNCSEC (EXT-SREF)

FAN (FAN)

MANSWTOTHIRD (NE-SREF)

SYNCSEC (NE-SREF)

FANDEGRADE (FAN)

MANUAL-REQ-SPAN (OCN)

SYNCTHIRD (EXT-SREF)

FE-AIS (DS3)

MEA (EQPT)

SYNCTHIRD (NE-SREF)

FE-DS1-MULTLOS (DS3)

MEA (FAN)

SYSBOOT (NE)

FE-DS1-NSA (DS3)

MEA (PPM)

TIM (OCN)

FE-DS1-SA (DS3)

MEM-GONE (EQPT)

TIM-MON (OCN)

FE-DS1-SNGLLOS (DS3)

MEM-LOW (EQPT)

TIM-P (STSMON)

FE-DS3-NSA (DS3)

MFGMEM (BPLANE)

TIM-P (STSTRM)

FE-DS3-SA (DS3)

MFGMEM (FAN)

TIM-S (EC1)

FE-EQPT-NSA (DS3)

MFGMEM (PPM)

TIM-S (OCN)

FE-FRCDWKSWBK-SPAN (OCN)

NO-CONFIG (EQPT)

TIM-V (VT-TERM)

FE-FRCDWKSWPR-SPAN (OCN)

NOT-AUTHENTICATED

TPTFAIL (CE100T)

FE-IDLE (DS3)

OOU-TPT (STSTRM)

TX-AIS (DS3)

FE-LOCKOUTOFPR-SPAN (OCN)

OOU-TPT (VT-TERM)

TX-LOF (DS1)

FE-LOF (DS3)

OPEN-SLOT (EQPT)

TX-RAI (DS3)

FE-LOS (DS3)

PDI-P (STSMON)

UNEQ-P (STSMON)

FE-MANWKSWBK-SPAN (OCN)

PDI-P (STSTRM)

UNEQ-P (STSTRM)

FE-MANWKSWPR-SPAN (OCN)

PLM-P (STSMON)

UNEQ-V (VT-MON)

FEPRLF (OCN)

PLM-P (STSTRM)

UNEQ-V (VT-TERM)

FORCED-REQ (EQPT)

PLM-V (VT-TERM)

VCG-DEG (VCG)

FORCED-REQ (STSMON)

PRC-DUPID (OCN)

VCG-DOWN (VCG)

FORCED-REQ (VT-MON)

PROTNA (EQPT)

WKSWPR (OCN)

FORCED-REQ-SPAN (OCN)

PROV-MISMATCH (PPM)

WKSWPR (STSMON)

FRCDSWTOINT (NE-SREF)

PWR-FAIL-A (EQPT)

WKSWPR (VT-MON)

FRCDSWTOPRI (EXT-SREF)

PWR-FAIL-B (EQPT)

WTR (EQPT)

FRCDSWTOPRI (NE-SREF)

RAI (DS1)

WTR (OCN)

FRCDSWTOSEC (EXT-SREF)

RAI (DS3)

WTR (STSMON)

FRCDSWTOSEC (NE-SREF)

RFI-L (EC1)

WTR (VT-MON)

FRCDSWTOTHIRD (EXT-SREF)

RFI-L (OCN)


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 Type Definitions 

Type
Definition
BITS

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

BPLANE

The backplane.

CE100T

The CE-100T-8 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 located in the ONS 15310-CL shelf.

FUDC

SONET F1 byte user data channel for ONS 15310-CL ML100T-8 Ethernet cards.

NE

The entire network element.

NE-SREF

The timing status of the NE.

OCN

An OC-3 port or OC-12 port on the 15310-CL-CTX 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).

VT-MON

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

VT-TERM

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


2.4  Alarm List by Logical Object Type

Table 2-8 lists all ONS 15310-CL Release 6.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 The list is given here exactly as it is shown in CTC, and in some cases does not follow alphabetical order.


Table 2-8 ONS 15310-CL Alarm List by Logical Object as Shown in Alarm Profile 

BITS: AIS

EQPT: SWMTXMOD-PROT

OCN: SSM-SMC

BITS: LOF

EQPT: SWMTXMOD-WORK

OCN: SSM-ST2

BITS: LOS

EQPT: WTR

OCN: SSM-ST3

BITS: SSM-DUS

EXT-SREF: FRCDSWTOPRI

OCN: SSM-ST3E

BITS: SSM-FAIL

EXT-SREF: FRCDSWTOSEC

OCN: SSM-ST4

BITS: SSM-OFF

EXT-SREF: FRCDSWTOTHIRD

OCN: SSM-STU

BITS: SSM-PRS

EXT-SREF: MANSWTOPRI

OCN: SSM-TNC

BITS: SSM-RES

EXT-SREF: MANSWTOSEC

OCN: SYNC-FREQ

BITS: SSM-SMC

EXT-SREF: MANSWTOTHIRD

OCN: TIM

BITS: SSM-ST2

EXT-SREF: SWTOPRI

OCN: TIM-MON

BITS: SSM-ST3

EXT-SREF: SWTOSEC

OCN: TIM-S

BITS: SSM-ST3E

EXT-SREF: SWTOTHIRD

OCN: WKSWPR

BITS: SSM-ST4

EXT-SREF: SYNCPRI

OCN: WTR

BITS: SSM-STU

EXT-SREF: SYNCSEC

PPM: AS-CMD

BITS: SSM-TNC

EXT-SREF: SYNCTHIRD

PPM: AS-MT

BITS: SYNC-FREQ

FAN: EQPT-MISS

PPM: EQPT

BPLANE: AS-CMD

FAN: FAN

PPM: HI-LASERBIAS

BPLANE: INVMACADR

FAN: FANDEGRADE

PPM: HI-LASERTEMP

BPLANE: MFGMEM

FAN: MEA

PPM: HI-TXPOWER

CE100T: AS-CMD

FAN: MFGMEM

PPM: IMPROPRMVL

CE100T: AS-MT

FUDC: AIS

PPM: LO-LASERBIAS

CE100T: CARLOSS

FUDC: LOS

PPM: LO-LASERTEMP

CE100T: GFP-CSF

NE-SREF: FRCDSWTOINT

PPM: LO-TXPOWER

CE100T: GFP-LFD

NE-SREF: FRCDSWTOPRI

PPM: MEA

CE100T: GFP-UP-MISMATCH

NE-SREF: FRCDSWTOSEC

PPM: MFGMEM

CE100T: LPBKFACILITY

NE-SREF: FRCDSWTOTHIRD

PPM: PROV-MISMATCH

CE100T: LPBKTERMINAL

NE-SREF: FRNGSYNC

PWR: AS-CMD

CE100T: RPRW

NE-SREF: FSTSYNC

PWR: BAT-FAIL

CE100T: TPTFAIL

NE-SREF: HLDOVRSYNC

PWR: EHIBATVG

DS1: AIS

NE-SREF: MANSWTOINT

PWR: ELWBATVG

DS1: AS-CMD

NE-SREF: MANSWTOPRI

PWR: HIBATVG

DS1: AS-MT

NE-SREF: MANSWTOSEC

PWR: LWBATVG

DS1: LOF

NE-SREF: MANSWTOTHIRD

STSMON: AIS-P

DS1: LOS

NE-SREF: SSM-PRS

STSMON: AUTOSW-AIS

DS1: LPBKDS1FEAC-CMD

NE-SREF: SSM-RES

STSMON: AUTOSW-LOP

DS1: LPBKFACILITY

NE-SREF: SSM-SMC

STSMON: AUTOSW-PDI

DS1: LPBKTERMINAL

NE-SREF: SSM-ST2

STSMON: AUTOSW-SDBER

DS1: RAI

NE-SREF: SSM-ST3

STSMON: AUTOSW-SFBER

DS1: SD

NE-SREF: SSM-ST3E

STSMON: AUTOSW-UNEQ

DS1: SF

NE-SREF: SSM-ST4

STSMON: ERFI-P-CONN

DS1: SSM-DUS

NE-SREF: SSM-STU

STSMON: ERFI-P-PAYLD

DS1: SSM-FAIL

NE-SREF: SSM-TNC

STSMON: ERFI-P-SRVR

DS1: SSM-OFF

NE-SREF: SWTOPRI

STSMON: FAILTOSW-PATH

DS1: SSM-PRS

NE-SREF: SWTOSEC

STSMON: FORCED-REQ

DS1: SSM-RES

NE-SREF: SWTOTHIRD

STSMON: LOCKOUT-REQ

DS1: SSM-SMC

NE-SREF: SYNCPRI

STSMON: LOM

DS1: SSM-ST2

NE-SREF: SYNCSEC

STSMON: LOP-P

DS1: SSM-ST3

NE-SREF: SYNCTHIRD

STSMON: LPBKCRS

DS1: SSM-ST3E

NE: APC-END

STSMON: MAN-REQ

DS1: SSM-ST4

NE: AS-CMD

STSMON: PDI-P

DS1: SSM-STU

NE: AUD-LOG-LOSS

STSMON: PLM-P

DS1: SYNC-FREQ

NE: AUD-LOG-LOW

STSMON: RFI-P

DS1: TX-LOF

NE: DATAFLT

STSMON: ROLL

DS3: AIS

NE: DUP-IPADDR

STSMON: ROLL-PEND

DS3: AS-CMD

NE: DUP-NODENAME

STSMON: SD-P

DS3: AS-MT

NE: ETH-LINKLOSS

STSMON: SF-P

DS3: DS3-MISM

NE: HITEMP

STSMON: TIM-P

DS3: FE-AIS

NE: I-HITEMP

STSMON: UNEQ-P

DS3: FE-DS1-MULTLOS

NE: INTRUSION-PSWD

STSMON: WKSWPR

DS3: FE-DS1-NSA

NE: SNTP-HOST

STSMON: WTR

DS3: FE-DS1-SA

NE: SYSBOOT

STSTRM: AIS-P

DS3: FE-DS1-SNGLLOS

OCN: AIS-L

STSTRM: AS-MT-OOG

DS3: FE-DS3-NSA

OCN: ALS

STSTRM: ENCAP-MISMATCH-P

DS3: FE-DS3-SA

OCN: APS-INV-PRIM

STSTRM: ERFI-P-CONN

DS3: FE-EQPT-NSA

OCN: APS-PRIM-FAC

STSTRM: ERFI-P-PAYLD

DS3: FE-IDLE

OCN: APS-PRIM-SEC-MISM

STSTRM: ERFI-P-SRVR

DS3: FE-LOF

OCN: APSB

STSTRM: LCAS-CRC

DS3: FE-LOS

OCN: APSC-IMP

STSTRM: LCAS-RX-FAIL

DS3: INC-ISD

OCN: APSCDFLTK

STSTRM: LCAS-TX-ADD

DS3: LOF

OCN: APSCINCON

STSTRM: LCAS-TX-DNU

DS3: LOS

OCN: APSCM

STSTRM: LOF

DS3: LPBKDS3FEAC

OCN: APSCNMIS

STSTRM: LOM

DS3: LPBKDS3FEAC-CMD

OCN: APSIMP

STSTRM: LOP-P

DS3: LPBKFACILITY

OCN: APSMM

STSTRM: LPBKCRS

DS3: LPBKTERMINAL

OCN: AS-CMD

STSTRM: OOU-TPT

DS3: RAI

OCN: AS-MT

STSTRM: PDI-P

DS3: SD

OCN: AUTOLSROFF

STSTRM: PLM-P

DS3: SF

OCN: BLSROSYNC

STSTRM: RFI-P

DS3: TX-AIS

OCN: E-W-MISMATCH

STSTRM: ROLL

DS3: TX-RAI

OCN: EOC

STSTRM: ROLL-PEND

EC1: AIS-L

OCN: EOC-L

STSTRM: SD-P

EC1: AS-CMD

OCN: EXTRA-TRAF-PREEMPT

STSTRM: SF-P

EC1: AS-MT

OCN: FAILTOSW

STSTRM: SQM

EC1: LOF

OCN: FE-FRCDWKSWBK-SPAN

STSTRM: TIM-P

EC1: LOS

OCN: FE-FRCDWKSWPR-SPAN

STSTRM: UNEQ-P

EC1: LPBKFACILITY

OCN: FE-LOCKOUTOFPR-SPAN

VCG: LOA

EC1: LPBKTERMINAL

OCN: FE-MANWKSWBK-SPAN

VCG: VCG-DEG

EC1: RFI-L

OCN: FE-MANWKSWPR-SPAN

VCG: VCG-DOWN

EC1: SD-L

OCN: FEPRLF

VT-MON: AIS-V

EC1: SF-L

OCN: FORCED-REQ-SPAN

VT-MON: AUTOSW-AIS

EC1: TIM-S

OCN: FULLPASSTHR-BI

VT-MON: AUTOSW-LOP

ENVALRM: EXT

OCN: HELLO

VT-MON: AUTOSW-UNEQ

EQPT: AS-CMD

OCN: HI-LASERBIAS

VT-MON: FAILTOSW-PATH

EQPT: AS-MT

OCN: HI-LASERTEMP

VT-MON: FORCED-REQ

EQPT: AUTORESET

OCN: HI-RXPOWER

VT-MON: LOCKOUT-REQ

EQPT: BKUPMEMP

OCN: HI-TXPOWER

VT-MON: LOP-V

EQPT: CARLOSS

OCN: ISIS-ADJ-FAIL

VT-MON: MAN-REQ

EQPT: CLDRESTART

OCN: KB-PASSTHR

VT-MON: RFI-V

EQPT: COMIOXC

OCN: LASEREOL

VT-MON: ROLL

EQPT: CONTBUS-DISABLED

OCN: LKOUTPR-S

VT-MON: ROLL-PEND

EQPT: CONTBUS-IO-A

OCN: LO-LASERBIAS

VT-MON: SD-V

EQPT: CTNEQPT-PBPROT

OCN: LO-LASERTEMP

VT-MON: SF-V

EQPT: CTNEQPT-PBWORK

OCN: LO-RXPOWER

VT-MON: UNEQ-V

EQPT: EQPT

OCN: LO-TXPOWER

VT-MON: WKSWPR

EQPT: ERROR-CONFIG

OCN: LOCKOUT-REQ

VT-MON: WTR

EQPT: EXCCOL

OCN: LOF

VT-TERM: AIS-V

EQPT: FORCED-REQ

OCN: LOS

VT-TERM: AS-MT-OOG

EQPT: HITEMP

OCN: LPBKFACILITY

VT-TERM: LCAS-CRC

EQPT: IMPROPRMVL

OCN: LPBKTERMINAL

VT-TERM: LCAS-RX-FAIL

EQPT: IOSCFGCOPY

OCN: MANUAL-REQ-SPAN

VT-TERM: LCAS-TX-ADD

EQPT: MANRESET

OCN: PRC-DUPID

VT-TERM: LCAS-TX-DNU

EQPT: MEA

OCN: RFI-L

VT-TERM: LOM

EQPT: MEM-GONE

OCN: SD-L

VT-TERM: LOP-V

EQPT: MEM-LOW

OCN: SF-L

VT-TERM: OOU-TPT

EQPT: NO-CONFIG

OCN: SQUELCH

VT-TERM: PLM-V

EQPT: OPEN-SLOT

OCN: SQUELCHED

VT-TERM: RFI-V

EQPT: PROTNA

OCN: SSM-DUS

VT-TERM: SD-V

EQPT: PWR-FAIL-A

OCN: SSM-FAIL

VT-TERM: SF-V

EQPT: PWR-FAIL-B

OCN: SSM-OFF

VT-TERM: SQM

EQPT: RUNCFG-SAVENEED

OCN: SSM-PRS

VT-TERM: TIM-V

EQPT: SFTWDOWN

OCN: SSM-RES

VT-TERM: UNEQ-V

EQPT: SW-MISMATCH


2.5  Trouble Notifications

The ONS 15310-CL 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 sections.

The ONS 15310-CL uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and status or 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 15310-CL uses standard alarm entities to identify what is causing trouble. All alarms stem 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 15310-CL shelf. They can include standing or transient notifications. A snapshot of all current raised, 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 SONET TL1 Command Guide.

2.5.3  Severities

The ONS 15310-CL uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are described below:

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 the free-run synchronization state (FRNGSYNC) or a forced-switch to primary timing source event (FRCSWTOPRI). 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 usually accompany 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 in the Cisco ONS 15310-CL 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 used in the ONS 15310-CL system 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; lower-ranking alarms are closed by higher-ranking alarms. The facility alarm hierarchy used in the ONS 15310-CL system 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 (loss of signal [LOS], loss of frame alignment [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-P1

LOP-P2

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)

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

2 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 State column on the Alarms or History tabs indicates 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 provides safety considerations designed to ensure safe operation of the ONS 15310-CL. Do not perform any procedures in this chapter unless you understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances pay close attention to the following cautions and warnings.


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 Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals. Statement 43

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 tool in the lower right corner of the GUI is not indented. When you are done checking for alarms, click the alarm filter tool again to turn filtering back on. For more information about alarm filtering, refer to the "Manage Alarms" chapter in the Cisco ONS 15310-CL 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 15310-CL Procedure Guide.


2.7.1  AIS

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

Logical Objects: BITS, DS1, DS3, FUDC

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

Generally, an 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 resolve 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-87, 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.htmlfor more information or call TAC (1 800 553-2447).


2.7.2  AIS-L

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

Logical Objects: EC1, 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-128 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/cisco/web/support/index.htmlfor more information or call 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.htmlfor more information or call 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 Unused 15310-CL-CTX Card 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/cisco/web/support/index.html for more information or call TAC (1 800 553-2447).


2.7.5  ALS

The ALS condition is not used in this platform in this release. It is reserved for future development.

2.7.6  APC-END

The APC-END condition is not used in this platform in this release. It is reserved for future development.

2.7.7  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 15310-CL. These invalid codes cause an APSB alarm on the ONS 15310-CL.

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

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


2.7.8  APSCDFLTK

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

2.7.9  APSC-IMP

The APSC-IMP alarm is not used in this platform in this release. It is reserved for future development.

2.7.10  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 15310-CL, 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-87,or the "LOF (OCN)" alarm on page 2-79 (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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.11  APSCM

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

Logical Object: OCN

The APS Channel Mismatch alarm occurs when the ONS 15310-CL 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 15310-CL when bidirectional protection is used on OC-N ports in a 1+1 protection group configuration. The APSCM alarm does not occur in an optimized 1+1 protection 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-port channel fibers are physically connected directly to the adjoining node working-port channel fibers.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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

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


2.7.12  APSCNMIS

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

2.7.13  APSIMP

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

Logical Object: OCN

The APS Invalid Mode 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 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. It is not superseded 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 15310-CL 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.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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

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


2.7.14  APS-INV-PRIM

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

2.7.15  APSMM

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

Logical Object: OCN

An APS Mode Mismatch failure alarm occurs on OC-3 ports 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 15310-CL that is provisioned for 1+1 protection switching.

Clear the APSMM Alarm


Step 1 For the reporting ONS 15310-CL, in node view 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-3 or OC-12 ports.

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

Step 2 Click Edit.

Record whether the Bidirectional Switching check box is checked.

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

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

Step 5 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 6 Click Apply.

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


2.7.16  APS-PRIM-FAC

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

2.7.17  APS-PRIM-SEC-MISM

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

2.7.18  AS-CMD

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

Logical Objects: BPLANE, CE100T, DS1, DS3, EC1, EQPT, NE, OCN, PPM, PWR

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. For example, suppressing alarms on a card also suppresses alarms on its ports.


Note For more information about suppressing alarms, refer to the "Manage Alarms" chapter in the Cisco ONS 15310-CL Procedure Guide.


Clear the AS-CMD Condition


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

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

If the condition is reported against 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 NE object, go to Step 7.

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 15310-CL-CTX card, CE-100T-8, or ML100-T 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 If the AS-CMD condition is reported for a card and not an individual port, in node view 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 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 8 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.htmlfor more information or call TAC (1 800 553-2447).


2.7.19  AS-MT

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

Logical Objects: CE100T, DS1, DS3, EC1, EQPT, OCN, PPM

The Alarms Suppressed for Maintenance Command condition applies to OC-3, OC-12 and electrical ports and occurs when a port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations.

Clear the AS-MT Condition


Step 1 Complete the "Clear an OC-N Port Facility or Terminal Loopback Circuit" procedure.

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


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

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.

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

2.7.21  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 with new entries. 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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.22  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.23  AUTOLSROFF

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

2.7.24  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 additional alarms are present that could have triggered an automatic reset. If so, troubleshoot these alarms using the applicable section of this chapter.

Step 2 If the reporting card is an ML-100T-8 or CE-100T-8 card and automatically resets more than once a month with no apparent cause, complete the "Physically Replace an Ethernet Card" procedure.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.


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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.25  AUTOSW-AIS

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

Logical Objects: STSMON, VT-MON

The Automatic path protection 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.

Generally, an AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when the node sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolve 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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.26  AUTOSW-LOP (STSMON)

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

Logical Object: STSMON

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

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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.27  AUTOSW-LOP (VT-MON)

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

Logical Object: VT-MON

The AUTOSW-LOP alarm for the VT monitor (VT-MON) indicates that automatic path protection switching occurred because of the "LOP-V" alarm on page 2-81. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

Clear the AUTOSW-LOP (VT-MON) Alarm


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

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


2.7.28  AUTOSW-PDI

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

Logical Object: STSMON

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

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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.29  AUTOSW-SDBER

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

Logical Object: STSMON

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

Clear the AUTOSW-SDBER Condition


Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.

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


2.7.30  AUTOSW-SFBER

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

Logical Object: STSMON

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

Clear the AUTOSW-SFBER Condition


Step 1 Complete the "Clear the SF (DS1, DS3) Condition" procedure.

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


2.7.31  AUTOSW-UNEQ (STSMON)

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

Logical Object: STSMON

The Automatic path protection Switch Caused by Unequipped condition indicates that an UNEQ alarm caused automatic path protection switching to occur (see the "UNEQ-P" condition on page 2-130). If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.

Clear the AUTOSW-UNEQ (STSMON) 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/cisco/web/support/index.htmlhttp://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.32  AUTOSW-UNEQ (VT-MON)

Default Severity: Minor (MN), Service-Affecting (SA)

Logical Object: VT-MON

The automatic path protection switch caused by an unequipped condition (VT-MON) indicates that the "UNEQ-V" alarm on page 2-132 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.

Clear the AUTOSW-UNEQ (VT-MON) Alarm


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

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


2.7.33  BAT-FAIL

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

Logical Object: PWR

The Battery Fail alarm occurs when the power supply 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. The "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide contains instructions for installing both AC and DC power supply cables. To remove the cable, reverse the appropriate procedure.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html 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 15310-CL-CTX flash memory. The alarm occurs when the 15310-CL-CTX 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 cyclic redundancy checking (CRC, a method to verify for errors in data transmitted to the 15310-CL-CTX).

The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-46. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarms.

Clear the BKUPMEMP Alarm


Step 1 Verify that the 15310-CL-CTX card is powered and enabled by confirming a lighted ACT LED on front of the ONS 15310-CL.

Step 2 Complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

Wait ten minutes to verify that the card you reset completely reboots. The ACT LED should be green.

Step 3 If the 15310-CL-CTX card does not reboot successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447).


2.7.35  BLSROSYNC

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

2.7.36  CARLOSS (CE100T)

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

Logical Objects: CE100T

The Carrier Loss alarm is raised on CE-100T-8 cards in Mapper mode when there is a circuit failure due to link integrity. It does not get raised when a user simply puts the port in the In-Service and Normal (IS-NR) service state. In order for the alarm to be raised, the card has to be IS-NR with a circuit or loopback.

Clear the CARLOSS (CE100T) 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 in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device.

Step 3 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 "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

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 in the Cisco ONS 15310-CL Procedure Guide for procedures.

Step 7 If the alarm does not clear, and link autonegotiation is enabled on the 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 (CE100T)" alarm on page 2-129 is also reported, complete the "Clear the TPTFAIL (CE100T) 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 CE100T-8 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,LPBK&MT, a loopback is provisioned. Go to Step 11.

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

On the CE100T-8, 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 CE100T-8 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked CE100T-8 port detects the termination. For more information about CE100T-8 cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

If the 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 15310-CL 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 15310-CL 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. Right-click or left-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 15310-CL and card are hosting the Ethernet circuit at the other end of the Ethernet manual cross-connect using 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 port to an OC-N port 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" chapter in the Cisco ONS 15310-CL Procedure Guide for detailed procedures to do this.

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

Step 14 If the alarm does not clear, complete the "Physically Replace an Ethernet Card" procedure for the Ethernet 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 15 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.37  CARLOSS (EQPT)

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

Logical Object: EQPT

A Carrier Loss on the LAN Equipment alarm generally occurs on OC-3 and OC-12 ports when the ONS 15310-CL and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the LAN (RJ-45) connector on the ONS 15310-CL. 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

Clear the CARLOSS (EQPT) Alarm


Step 1 If the reporting entity is a PPM port, confirm that the PPM is correctly configured by completing the following steps:

a. Double-click the 15310-CL-CTX card.

b. Click the Provisioning > Pluggable Port Modules tabs.

c. View the Pluggable Port Modules area port listing in the Actual Eqpt Type column and compare this with the contents of the Selected PPM area Rate column for the port.

d. If the rate does not match the actual equipment, you must delete and recreate the selected PPM. Select the PPM, click Delete, then click Create and choose the correct rate for the port rate.

Step 2 If the reporting port is an OC-3 or OC-12 port, verify connectivity by pinging the ONS 15310-CL that is reporting the alarm by completing the procedure in the "Verify PC Connection to the ONS 15310-CL (Ping)" section.

Step 3 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 4 Using optical test equipment, verify that proper receive levels are achieved. (For specific procedures to use the test set equipment, consult the manufacturer.)

Step 5 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 in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 6 If the fiber cable is properly connected and attached to the port, verify that the cable connects the port to another Ethernet device and is not misconnected to an OC-3 or OC-12 port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide. For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Step 7 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 in the Cisco ONS 15310-CL Procedure Guide for procedures.

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

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


2.7.38  CLDRESTART

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

Logical Object: EQPT

The Cold Restart condition occurs when an Ethernet card is reseated or replaced, or when the ONS 15310-CL power is initialized.

Clear the CLDRESTART Condition


Step 1 If the condition is raised on the controller card, it should clear after booting. If the condition is raised on an Ethernet card, complete the "Remove and Reinsert (Reseat) an Ethernet Card" procedure.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 If the condition raised against an Ethernet card does not clear, complete the "Physically Replace an Ethernet Card" procedure for the 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 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.39  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 15310-CL-CTX card when there is a communication failure for a traffic slot.

Clear the COMIOXC Alarm


Step 1 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure on the 15310-CL-CTX card.

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

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


2.7.40  CONTBUS-DISABLED

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

Logical Object: EQPT

The CONTBUS-DISABLED alarm is a function of the Release 6.0 enhanced cell bus verification feature. This alarm occurs when an Ethernet 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 Ethernet slot to the 15310-CL-CTX 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 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.

For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Clear the CONTBUS-DISABLED Alarm


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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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


2.7.41  CONTBUS-IO-A

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

Logical Object: EQPT

An 15310-CL-CTX A to Shelf Slot Communication Failure alarm occurs when the 15310-CL-CTX card has lost communication with an Ethernet card in the shelf. The other card is identified by the Object column in the CTC alarm window.

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-98 for the reporting card.

Step 2 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure. For LED behavior, see the "Typical 15310-CL-CTX Card or Ethernet Card LED Activity During Reset" section.

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

Step 3 If CONTBUS-IO-A is raised on more than one Ethernet card at once, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

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

Step 5 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1 800 553-2447).


2.7.42  CTNEQPT-PBPROT

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

2.7.43  CTNEQPT-PBWORK

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

Logical Object: EQPT

The Interconnection Equipment Failure Working 15310-CL-CTX Card Payload Bus alarm indicates a failure in the main payload bus between the 15310-CL-CTX card and the reporting Ethernet card. The 15310-CL-CTX card and the Ethernet card are no longer communicating.

Clear the CTNEQPT-PBWORK Alarm


Step 1 If the alarm is reported against the controller card, go to Step 5. If the Ethernet traffic card shows the CTNEEQPT-PBWORK alarm, complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure for the Ethernet card.

Step 2 If the alarm does not clear, complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure for the reporting card.

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

Step 4 If the alarm does not clear, complete the "Physically Replace an Ethernet Card" procedure.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.


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


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


2.7.44  DATAFLT

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

Logical Object: NE

The Software Data Integrity Fault alarm occurs when the 15310-CL-CTX card exceeds its flash memory capacity.

Clear the DATAFLT Alarm


Step 1 Complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

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


2.7.45  DS3-MISM

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

Logical Object: DS3

The DS-3 Frame Format Mismatch condition indicates that a line type format mismatch on a signal received on the ONS 15310-CL DS-3 port. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type for a DS-3 port is set to C Bit and the incoming signal line type is detected as M13, then the ONS 15310-CL reports a DS3-MISM condition.

Clear the DS3-MISM Condition


Step 1 In node view, double-click the 15310-CL-CTX card to display the card view.

Step 2 Click the Provisioning > DS3 > 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 (C bit or M13).

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 15310-CL 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.46  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 15310-CL chassis.

b. Begin a CTC session.

c. In the login dialog window, 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 in the Cisco ONS 15310-CL Procedure Guide.)

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


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

Step 2 In the Node Name/TID 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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.48  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 has a preset value of -56.5 VDC and is not user-provisionable. The alarm is raised until the voltage remains under the threshold for 120 seconds.

Clear the EHIBATVG Alarm


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

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


2.7.49  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 has a preset value of -40.5 VDC and is not user-provisionable. The alarm remains raised until the voltage remains over the threshold for 120 seconds.

Clear the ELWBATVG Alarm


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

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


2.7.50  ENCAP-MISMATCH-P

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

Logical Object: STSTRM

The Encapsulation C2 Byte Mismatch Path alarm applies to the ML-100T-8 Ethernet card. It occurs when the first three following conditions are met and one of the last two is false:

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 is in contrast to the "PLM-P" alarm on page 2-104, which must meet all five criteria.) For an ENCAP-MISMATCH-P alarm to be raised, there is a mismatch between the received and expected C2 byte, with either the expected byte or received byte value being 0x01.

For example, an ENCAP-MISMATCH-P alarm is raised if a circuit created between two ML-100T-8 cards has generic framing procedure (GFP) framing provisioned on one end and high-level data link control (HDLC) framing with LEX encapsulation provisioned on the other. The GFP-framing card transmits and expects a C2 byte of 0x1B, while the HDLC-framing card transmits and expects a C2 byte of 0x01.

A mismatch between the transmit and receive cards on any of the following parameters can cause the alarm:

Mode (HDLC, GFP-F)

Encapsulation (LEX, HDLC, PPP)

CRC size (16 or 32)

Scrambling state (on or off)

This alarm is demoted by PLM-P or PLM-V.


Note By default, an ENCAP-MISMATCH-P alarm causes an ML-100T-8 card data link to go down. This behavior can be modified using the command line interface (CLI) command no pos trigger defect encap.



Note For more information about the ML-100T-8 Ethernet card, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the ENCAP-MISMATCH-P Alarm


Step 1 Ensure that the correct line type is in use on the receive card by completing the following steps:

a. In node view, double-click the receive ML-100T-8 card to display the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply.

Step 2 Ensure that the correct line type is in use on the transmit card and that it is identical to the receiving card by completing the following steps:

a. In node view, double-click the transmit ML-100T-8 card to display the card view.

b. Click the Provisioning > Card tabs.

c. In the Mode drop-down list, ensure that the same mode (GFP or HDLC) is selected. If it is not, choose it and click Apply.

Step 3 If the alarm does not clear, use the CLI to ensure that the remaining settings are correctly configured on the ML-100T-8 card:

Encapsulation

CRC size

Scrambling state

To open the interface, click the IOS tab and click Open IOS Command Line Interface (CLI). Refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide entries on all three of these topics to obtain the full configuration command sequences.

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


2.7.51   EOC

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

Logical Object: OCN

The SONET DCC Termination Failure alarm occurs when the ONS 15310-CL loses its DCC. The section data communication channel (SDCC) overhead 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 15310-CL 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-87 is also reported, complete the "Clear the LOS (OCN) Alarm" procedure.

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

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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have in-service (IS-NR) ports. Verify that the ACT LED is green.

Step 4 When the LED on the 15310-CL-CTX card is green, complete the "Verify or Create Node DCC Terminations" procedure to ensure that the DCC is provisioned for the ports at both ends of the fiber span.

Step 5 Repeat Step 4 at the adjacent nodes.

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

a. In node view, double-click the 15310-CL-CTX card to display the card view.

b. Click the Provisioning > Optical > Line tabs.

c. Confirm that the OC-3 or OC-12 port shows a green LED.

A green ACT LED indicates an active card.

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.

Step 7 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 port. It could be necessary to manually switch traffic carrying circuits over a protection path. See the "Protection Switching, Lock Initiation, and Clearing" section for commonly used switching procedures.

Step 8 If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. Refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide for levels.

Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated.

Step 10 If fiber connectors are properly fastened and terminated, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

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

Step 11 If the 15310-CL-CTX 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 12 Recreate the SDCC termination. Refer to the "Turn Up Network" chapter in the Cisco ONS 15310-CL Procedure Guide for procedures.

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

Step 14 If the alarm has not cleared, call Cisco TAC (1 800 553-2447).


2.7.52  EOC-L

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

Logical Object: OCN

The Line DCC (LDCC) Termination Failure alarm occurs when the ONS 15310-CL loses its LDCC termination. The LDCC consists of nine bytes, D4 through D12, that convey information about OAM&P and network management information in the SONET overhead.


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 an incomplete state when the EOC or EOC-L alarm is raised, it occurs when 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 TAC (1 800 553-2447).


2.7.53  EQPT

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

Logical Objects: EQPT, PPM

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" alarm on page 2-31. The BKUPMEMP procedure also clears the EQPT 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 "Soft- or Hard-Reset an Ethernet Card in CTC" procedure for the reporting card. For the LED behavior, see the "Typical 15310-CL-CTX Card or Ethernet Card LED Activity During Reset" section.

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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 4 If the physical reseat of the card fails to clear the alarm, complete the "Physically Replace an Ethernet Card" procedure for the reporting 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 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.54  EQPT-MISS

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

Logical Object: FAN

The Replaceable Equipment or Unit Missing alarm is reported against the fan within the ONS 15310-CL. It indicates that the fan is not operational. This alarm is not user-serviceable. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.

2.7.55  ERFI-P-CONN

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication (ERFI) Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the "UNEQ-P" alarm on page 2-130 and the "TIM-P" alarm on page 2-128 are raised on the transmission signal.

Clear the ERFI-P-CONN Condition


Step 1 Complete the "Clear the UNEQ-P Alarm" procedure and the "Clear the TIM-P Alarm" procedure. This should clear the ERFI condition.

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


2.7.56  ERFI-P-PAYLD

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

Logical Objects: STSMON, STSTRM

The Three-Bit ERFI Path Payload condition is triggered on DS-1, DS-3, or VT circuits when the "PLM-P" alarm on page 2-104 alarm is raised on the transmission signal.

Clear the ERFI-P-PAYLD Condition


Step 1 Complete the "Clear the PLM-P Alarm" procedure. This should clear the ERFI condition.

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


2.7.57  ERFI-P-SRVR

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

Logical Objects: STSMON, STSTRM

The Three-Bit ERFI Path Server condition is triggered on DS-1, DS-3, or VT circuits when the "AIS-P" alarm on page 2-19 or the "LOP-P" alarm on page 2-80 is raised on the transmission signal.

Clear the ERFI-P-SRVR Condition


Step 1 Complete the "Clear the LOP-P Alarm" procedure. This should clear the ERFI condition.

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


2.7.58  ERROR-CONFIG

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

Logical Object: EQPT

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

The typical reasons for an errored startup file are:

The user stored the configuration for one type of ML-100T-8 Ethernet card in the database and then installed another type in its slot.

The configuration file contained a syntax error.


Note For information about provisioning the ML-100T-8 Ethernet cards from the Cisco IOS interface, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the ERROR-CONFIG Alarm


Step 1 If the ML-100T-8 Ethernet configuration is different from the actual installation, create the correct startup configuration based upon the installation.

Consult the card provisioning instructions in the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Step 2 Upload the configuration file to the 15310-CL-CTX card by completing the following steps:

a. In node view, right-click the ML-100T-8 Ethernet card graphic.

b. Choose IOS Startup Config from the shortcut menu.

c. Click Local > TCC and navigate to the file location in the Open dialog box.

Step 3 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure.

Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start a Cisco IOS CLI for the card by completing the following steps:

a. Right-click the ML-100T-8 Ethernet card graphic in node view.

b. Choose Open IOS Connection from the shortcut menu.


Note "Open IOS Connection" is not available unless the ML-100T-8 Ethernet card is physically installed in the shelf.


Follow the card provisioning instructions in the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.

Step 5 Execute the following CLI command:

copy run start
 
   

The command copies the new card configuration into the database and clears the alarm.

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


2.7.59  ETH-LINKLOSS

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

Logical Object: NE

The Rear Panel Ethernet Link Removed condition, if enabled in the network defaults, is raised under the following conditions:

The node.network.general.AlarmMissingBackplaneLAN field in NE default is enabled.

The node is configured as a gateway network element (GNE).

The LAN cable is removed.

For more information about Ethernet in the ONS 15310-CL, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Clear the ETH-LINKLOSS Condition


Step 1 To clear this condition, reconnect the LAN cable on the front of the ONS 15310-CL.

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


2.7.60  E-W-MISMATCH

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

2.7.61  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 15310-CL and CTC could be affected. The network management LAN is the data network connecting the workstation running the CTC software to the 15310-CL-CTX card. The problem causing the alarm is external to the ONS 15310-CL.

Troubleshoot the network management LAN connected to the ONS 15310-CL 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 ONS 15310-CL 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 ONS 15310-CL and the network management LAN.

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


2.7.62  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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.63  EXTRA-TRAF-PREEMPT

The EXTRA-TRAF-PREEMPT alarm is not used in this platform in this release. It is reserved for future development.

2.7.64  FAILTOSW

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

Logical Object: 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 port and clears the FAILTOSW.

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


2.7.65  FAILTOSW-PATH

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

Logical Objects: STSMON

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 condition 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-80, the "SD-P" condition on page 2-114, the "SF-P" condition on page 2-116, and the "UNEQ-P" alarm on page 2-130.

The "LOF (OCN)" alarm on page 2-79, the "LOS (OCN)" alarm on page 2-87, the "SD-L" condition on page 2-113, or the "SF-L" condition on page 2-116 can also occur on the failed path.

Clear the FAILTOSW-PATH Condition in a Path Protection Configuration


Step 1 Look up and clear the higher priority alarm. If the "AIS-P" condition on page 2-19, the "LOP-P" alarm on page 2-80, the "UNEQ-P" alarm on page 2-130, the "SF-P" condition on page 2-116, the "SD-P" condition on page 2-114, the "LOF (OCN)" alarm on page 2-79, the "LOS (OCN)" alarm on page 2-87, the "SD-L" condition on page 2-113, or the "SF-L" condition on page 2-116 are also occurring on the reporting port, complete the applicable alarm clearing procedure.

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


2.7.66  FAN

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

Logical Object: FAN

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

This alarm is not user-serviceable. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1 800 553-2447).

2.7.67  FAN-DEGRADE

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Logical Object: FAN

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

This alarm is not user-serviceable. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).

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

Generally, an AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it detects 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 resolve 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.69  FE-DS1-MULTLOS

The FE-DS1-MULTLOS condition is not used in this platform in this release. It is reserved for future development.

2.7.70  FE-DS1-NSA

The FE-DS1-NSA condition is not used in this platform in this release. It is reserved for future development.

2.7.71  FE-DS1-SA

The FE-DS1-SA condition is not used in this platform in this release. It is reserved for future development.

2.7.72  FE-DS1-SNGLLOS

The FE-DS1-SNGLLOS condition is not used in this platform in this release. It is reserved for future development.

2.7.73  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 (SA) condition occurs when a far-end ONS 15310-CL DS-3 equipment failure occurs in C-bit line type mode, but does not affect service because the port is protected and traffic is able to switch to the protect port.

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

Clear the FE-DS3-NSA Condition


Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an alarm from a card in Node 1 could link to an alarm from a card in 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.74  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 15310-CL-CTX 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.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.75  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 DS-3 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 alarm from a card in Node 1 could link to an alarm from a card in 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.76  FE-FRCDWKSWBK-SPAN

The FE-FRCDWKSWBK-SPAN condition is not used in this platform in this release. It is reserved for future development.

2.7.77  FE-FRCDWKSWPR-SPAN

The FE-FRCDWKSWPR-SPAN condition is not used in this platform in this release. It is reserved for future development.

2.7.78  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 in C-bit line type mode.

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 alarm from a card in Node 1 could link to an alarm from a card in 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.79  FE-LOCKOUTOFPR-SPAN

The FE-LOCKOUTOFPR-SPAN condition is not used in this platform in this release. It is reserved for future development.

2.7.80  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 the "LOF (DS3)" alarm on page 2-78 in C-bit line type mode.

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 alarm from a card in Node 1 could link to an alarm from a card in 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 (DS1) Alarm" procedure. It also applies to FE-LOF.

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


2.7.81  FE-LOS

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

Logical Object: DS3

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

Clear the FE-LOS Condition


Step 1 To troubleshoot the FE condition, determine which node and card/port link directly to the card or port reporting the FE condition. For example, an alarm from a card or port in Node 1 could link to an alarm from a card or port in 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.82  FE-MANWKSWBK-SPAN

The FE-MANWKSWBK-SPAN condition is not used in this platform in this release. It is reserved for future development.

2.7.83  FE-MANWKSWPR-SPAN

The FE-MANWKSWPR-SPAN condition is not used in this platform in this release. It is reserved for future development.

2.7.84  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-116 occurs on the protect card coming into the node.


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


Clear the FEPRLF Alarm


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 in this chapter for instructions.

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


2.7.85  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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.86  FORCED-REQ-SPAN

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

Logical Object: OCN

The Force Switch Request Span condition applies to optical trunk cards in spans when the Force Span command is applied to a 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.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.87  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.88  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.89  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 a second timing source.


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


2.7.90  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.91  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 15310-CL 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 15310-CL node relying on an internal clock.


Note If the ONS 15310-CL is configured to operate from its internal clock, disregard the FRNGSYNC condition.


Clear the FRNGSYNC Condition


Step 1 If the ONS 15310-CL is configured to operate from an external timing source, verify that the BITS timing source is valid. Refer to the "Timing" chapter in the Cisco ONS 15310-CL Reference Manual for more information about it.

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-125 and the "SYNCSEC" alarm on page 2-125.

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


2.7.92  FSTSYNC

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

Logical Object: NE-SREF

A Fast Start Synchronization Mode condition occurs when the ONS 15310-CL 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


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


2.7.93  FULLPASSTHR-BI

The FULLPASSTHR-BI condition is not used in this platform in this release. It is reserved for future development.

2.7.94  GFP-CSF

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

Logical Object: CE100T

The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on ML-100T-8 Ethernet ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm is affecting a remote data port's transmission capability. For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Clear the GFP-CSF Alarm


Step 1 Clear the Service-Affecting (SA) alarm at the remote data port.

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


2.7.95  GFP-LFD

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

Logical Object: CE100T

The GFP Loss of Frame Delineation alarm applies to Fibre Channel/FICON GFP ports and occurs if there is a bad SONET connection, if SONET path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. The loss is service affecting.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-LFD Alarm


Step 1 Look for and clear any associated SONET path errors such as LOS or AIS-L originating at the transmit node.

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


2.7.96  GFP-UP-MISMATCH

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

Logical Object: CE100T

The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type. For example, the local port media type could be set to Fibre Channel—1 Gbps ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL or FICON—2 Gbps ISL.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the GFP-UP-MISMATCH Alarm


Step 1 Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps:

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

b. Click the Provisioning > Port > Distance Extension tabs.

c. Check the check box in the Enable Distance Extension column.

d. Click Apply.

Step 2 Ensure that both ports are set for the correct media type. For each port, complete the following steps:

a. Double-click the card to display the card view (if you are not already in card view).

b. Click the Provisioning > Port> General tabs.

c. Choose the correct media type (Fibre Channel - 1Gbps ISL, Fibre Channel - 2 Gbps ISL, FICON - 1 Gbps ISL, or FICON - 2 Gbps ISL) from the drop-down list.

d. Click Apply.

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


2.7.97  HELLO

Default Severity: Minor (MN), 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.98  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 has a preset value of -52 VDC and is not user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds.

Clear the HIBATVG Alarm


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

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


2.7.99  HI-LASERBIAS

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

Logical Objects: OCN, PPM

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

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

Clear the HI-LASERBIAS Alarm


Step 1 Complete the "Physically Replace an Ethernet Card" procedure for the 15310-CL-CTX 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.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.


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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.100  HI-LASERTEMP

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

Logical Objects: OCN, PPM

The Equipment High Laser Optical Transceiver Temperature alarm applies to the OC-N ports. HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength.

When the card raises this alarm, the laser is automatically shut off. The "LOS (OCN)" alarm on page 2-87 is raised at the far-end node and the "DUP-IPADDR" alarm on page 2-40 is raised at the near end.

Clear the HI-LASERTEMP Alarm


Step 1 In node view, double-click the 15310-CL-CTX card to display the card view.

Step 2 Click the Performance > Optics PM tabs.

Step 3 Verify the card laser temperature levels. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows.

Step 4 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure for the card.

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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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


2.7.101  HI-RXPOWER

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

Logical Object: OCN

The Equipment High Receive Power alarm is an indicator for OCN port received optical signal power. HI-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable.

Clear the HI-RXPOWER Alarm


Step 1 Complete the "Clear the LO-RXPOWER Alarm" procedure.

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


2.7.102  HITEMP

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

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

Logical Objects: EQPT, NE

The High Temperature alarm occurs when the temperature of the ONS 15310-CL 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 internal ONS 15310-CL fan from passing air through the ONS 15310-CL shelf.

Step 3 If the alarm persists, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1 800 553-2447) if it applies to the NE, or a Non-Service-Affecting (NSA) problem if it applies to equipment.


2.7.103  HI-TXPOWER

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

Logical Objects: OCN, PPM

The Equipment High Transmit Power alarm is an indicator on the OC-N port transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.

Clear the HI-TXPOWER Alarm


Step 1 In node view, display the card view for the 15310-CL-CTX card.

Step 2 Click the Provisioning > Optics Thresholds tabs.

Step 3 Decrease (change toward the negative direction) the OPT-HIGH column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the "Physically Replace an Ethernet Card" procedure.


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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.


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


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


2.7.104  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 15310-CL relying on an internal clock.

Clear the HLDOVRSYNC Alarm


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 15310-CL Procedure Guide for procedures.

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


2.7.105  I-HITEMP

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

Logical Object: NE

The Industrial High Temperature alarm occurs when the temperature of the ONS 15310-CL 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/cisco/web/support/index.html for more information or call TAC (1-800-553-2447) in order to report a Service-Affecting (SA) problem.


2.7.106  IMPROPRMVL

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

Logical Objects: EQPT, PPM

The Improper Removal equipment (IMPROPRMVL) alarm occurs under the following conditions:

A card is removed when the card was rebooting. It is recommended that after the card completely reboots, delete the card in CTC and only then remove the card physically. When you delete the card, CTC loses connection with the node view (single-shelf mode) or shelf view (multishelf mode), and goes to network view.

When a card is physically removed from its slot before it is deleted from CTC. It is recommended that any card be deleted in CTC before physically removing the card from the chassis.


Note CTC provides the user approximately 15 seconds to physically remove the card before it begins rebooting the card.


A card is inserted into a slot but is not fully plugged into the backplane.

A PPM (SFP) is provisioned but the physical module is not inserted into the port.

Electrical issues such as short circuit or failure of DC-DC conversion.

Clear the IMPROPRMVL Alarm


Step 1 In node view, right-click the card reporting the IMPROPRMVL.

Step 2 Choose Delete from the shortcut menu.


Note CTC does not allow you to delete the reporting card if the card is in service, does have circuits 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, put 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 15310-CL-CTX card to display the card view.

b. Click the Provisioning > Optical > Line tab.

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 15310-CL 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 source from Internal Clock.

d. Click Apply.

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


2.7.107  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.108  INTRUSION-PSWD

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

Logical Object: NE

The Security Intrusion Incorrect Password condition occurs after a Superuser attempts a settable 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 In node view, click the Provisioning > Security tabs.

Step 2 Click Clear Security Intrusion Alarm.

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


2.7.109  INVMACADR

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

Logical Object: BPLANE

The Equipment Failure Invalid MAC Address alarm occurs when the ONS 15310-CL MAC address is invalid. The MAC Address is permanently assigned to the ONS 15310-CL chassis when it is manufactured. Do not attempt to troubleshoot an INVMACADR alarm. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).

2.7.110  IOSCFGCOPY

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

Logical Object: EQPT

The IOS Configuration Copy in Progress condition occurs on ML-100T-8 Ethernet cards when a Cisco IOS startup configuration file is being uploaded or downloaded to or from an ML-100T-8 Ethernet card. (This condition is very similar to the "SFTWDOWN" condition on page 2-117 but it applies to ML-100T-8 Ethernet cards rather than to the 15310-CL-CTX card.)

The condition clears after the copy operation is complete. (If it does not complete correctly, the "NO-CONFIG" condition on page 2-101 could be raised.)


Note IOSCFGCOPY is an informational condition.



Note For more information about the Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


2.7.111  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 supported 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 MAA configuration, refer to the "Cisco Transport Controller Operation" chapter in the Cisco ONS 15310-CL Reference Manual. For more information about configuring OSI, refer to the "Turn Up Node" chapter in the Cisco ONS 15310-CL Procedure Guide.

Clear the ISIS-ADJ-FAIL Alarm


Step 1 Ensure that both ends of the communications 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. Login to 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 15310-CL Procedure Guide for the procedure.

Step 3 If the nodes use 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 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 Provisioning > OSI > Routers > Setup.

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 15310-CL Procedure Guide for procedures to do this.

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


2.7.112  KB-PASSTHR

The KB-PASSTHR condition is not used in this platform in this release. It is reserved for future development.

2.7.113  LASEREOL

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

2.7.114  LCAS-CRC

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

Logical Objects: STSTRM, VT-TERM

The Link Capacity Adjustment Scheme (LCAS) Control Word CRC Failure condition is raised against ML-100T-8 Ethernet cards and CE-100T cards. It occurs when there is an equipment, path, or provisioning error on the virtual concatenation group (VCG) that causes consecutive 2.5 second CRC failures in the LCAS control word.

The condition can occur if an LCAS-enabled node (containing ML-100T-8 cards) transmitting to another LCAS-enabled node delivers faulty traffic due to an equipment or SONET path failure. Transmission errors would also be reflected in CV-P, ES-P, or SES-P performance-monitoring statistics. (For more information about performance-monitoring statistics, see Chapter 5 "Performance Monitoring.") If these errors do not exist, an equipment failure is indicated.

If LCAS is not supported on the peer node, the condition does not clear.

LCAS-CRC can also occur if the VCG source node is not LCAS-enabled, but the receiving node does have the capability enabled. Both source and destination nodes must have LCAS enabled. Otherwise, the LCAS-CRC condition persists on the VCG.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the LCAS-CRC Condition


Step 1 Look for and clear any associated equipment failures, such as the EQPT alarm, on the receive node or transmit node.

Step 2 Look for and clear any bit error rate conditions at the transmit node.

Step 3 If no equipment or SONET path errors exist, ensure that the remote node has LCAS enabled on the circuit by completing the following steps:

a. In node view, click the Circuits tab.

b. Choose the VCAT circuit and click Edit.

c. In the Edit Circuit window, click the General tab.

d. Verify that the Mode column says LCAS.

Step 4 If the column does not say LCAS, complete the "Delete a Circuit" procedure and recreate it in LCAS mode using the instructions in the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

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


2.7.115  LCAS-RX-FAIL

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Receive-Side-In Fail condition is raised against ML-100T-8 Ethernet cards and CE-100T cards with LCAS-enabled VCG or software-enabled LCAS (SW-LCAS) VCG.

LCAS VCGs treat failures unidirectionally, meaning that failures of the transmit or receive points occur independently of each other. The LCAS-RX-FAIL condition can occur on the receive side of an LCAS VCG member for the following reasons:

SONET path failure (a unidirectional failure as seen by the receive side).

VCAT member is set out of group at the transmit side, but is set in group at the receive side.

VCAT member does not exist at the transmit side but does exist and is in group at the receive side.

The condition can be raised during provisioning operations on LCAS VCGs but should clear when the provisioning is completed.

Software-enabled LCAS VCGs treat failure bidirectionally, meaning that both directions of a VCG member are considered failed if either transmit or receive fails. The LCAS-RX-FAIL condition is raised on these VCG members when a member receive side fails due to a SONET path failure.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.



Note ONS 15310-CL ML-100T-8-Series cards are LCAS-enabled.


Clear the LCAS-RX-FAIL Condition


Step 1 Check for and clear any line or path alarms using the procedures in this chapter.

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


2.7.116  LCAS-TX-ADD

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Add State condition is raised against ML-100T-8 Ethernet and CE-100T cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed. The condition clears after provisioning is completed. The remote likely reports a path condition such as an "AIS-P" condition on page 2-19 or an "UNEQ-P" alarm on page 2-130.


Note LCAS-TX-ADD is an informational condition and does not require troubleshooting.



Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


2.7.117  LCAS-TX-DNU

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

Logical Objects: STSTRM, VT-TERM

The LCAS VCG Member Transmit-Side-In Do Not Use (DNU) State condition is raised on ML-100T-8 Ethernet andCE-100T cards when the transmit side of an LCAS VCG member is in the DNU state. For a unidirectional failure, this condition is only raised at the source node. The LCAS-TX-DNU condition is raised when the cable is unplugged.

The remote node likely reports a path alarm such as AIS-P or UNEQ-P.


Note LCAS-TX-DNU is an informational condition and does not require troubleshooting.


2.7.118  LKOUTPR-S

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

Logical Object: OCN

The Lockout of Protection Span condition occurs when path protection 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 Path Protection Span External Switching Command" procedure.

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


2.7.119  LOA

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

Logical Object: VCG

The Loss of Alignment on a VCG 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 occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.


Note This alarm occurs only if you provision circuits outside of CTC, such as by using TL1.


Clear the LOA Alarm


Step 1 In network view, click the Circuits tab.

Step 2 Click the alarmed VCG and then click Edit.

Step 3 In the Edit Circuit window, view the source and destination circuit slots, ports, and STSs.

Step 4 Identify whether the STS travels across different fibers. If it does, complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit using the procedure in the "Create Circuits" chapter in the Cisco ONS 15310-CL Procedure Guide.

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


2.7.120  LOCKOUT-REQ

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

Logical Objects: 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 Path Protection Span External Switching Command" procedure.

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


2.7.121  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 BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15310-CL has lost frame delineation in the incoming data.

Clear the LOF (BITS) Alarm


Note This procedure assumes that the BITS timing reference signal is functioning properly. It also assumes the alarm is not appearing during node turn-up.



Step 1 Verify that the line type and line coding match between the BITS port and the 15310-CL-CTX 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 Line Type matches the line type of the BITS timing source, either ESF or SF (D4).

g. If the line type does not match, click Line Type 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 Line Type field and the AMI coding field is normally paired with SF (D4) in the Line Type field.


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


2.7.122  LOF (DS1)

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

Logical Object: DS1

The DS-1 LOF alarm indicates that the receiving ONS 15310-CL has lost frame delineation in an incoming DS-1 data stream. If the LOF appears on a DS-1 port, the transmitting equipment could have its line type set to a format that differs from the receiving node.

Clear the LOF (DS1) Alarm


Step 1 Verify that the line type and line coding match between the DS-1 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 line type formats of the signal source for the port reporting the alarm. You could need to contact your network administrator for the format information.

c. Display the card view of the reporting 15310-CL-CTX card.

d. Click the ONS 15310-CL 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 line coding (AMI and AMI or B8ZS and B8ZS). 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.

g. Click Apply.


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


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


2.7.123  LOF (DS3)

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

Logical Object: DS3

The DS-3 LOF alarm indicates that the receiving ONS 15310-CL 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 system. On DS-3 ports, the alarm occurs only on when the provisionable line type format set to C bit or M13.

Clear the LOF (DS3) Alarm


Step 1 Change the line type of the non-ONS equipment attached to the reporting port to C bit by completing the following steps:

a. Double-click the 15310-CL-CTX to display the card view.

b. Click the Provisioning > DS3 > Line tabs.

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

d. If the signal source line type does not match the reporting port, click Line Type and choose C Bit from the drop-down list.

e. Click Apply.

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


2.7.124  LOF (EC1)

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

Logical Object: EC1

The EC1-1 LOF alarm occurs when a port on the reporting 15310-CL-CTX card EC1 port has an LOF condition. LOF indicates that the receiving ONS 15310-CL 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.

Clear the LOF (EC1) 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 15310-CL.

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 in the Cisco ONS 15310-CL Procedure Guide.

Step 3 If the alarm does not clear, see the "Network Troubleshooting Tests" 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.125  LOF (OCN)

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

Logical Objects: OCN, STSTRM

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

When the alarm is raised on an OC-3 or OC-12 port, it is sometimes an indication that the OC-3 or OC-12 port 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 Complete the "Clear the LOF (EC1) Alarm" procedure.

Step 2 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.126  LO-LASERBIAS

The LO-LASERBIAS alarm is not used in this platform in this release. It is reserved for future development.

2.7.127  LO-LASERTEMP

The LO-LASERTEMP alarm is not used in this platform in this release. It is reserved for future development.

2.7.128  LOM

Default Severity: Critical (CR), Service-Affecting (SA) for STSMON; Major (MJ) for STSTRM, 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 to OCN ports 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-L Condition" procedure.

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


2.7.129  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 STS1, this raises 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 15310-CL.

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" chapter in the Cisco ONS 15310-CL Procedure Guide.

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


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

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


2.7.131  LO-RXPOWER

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

Logical Object: OCN

The Equipment Low Receive Power alarm is an indicator for OCN port received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls below the threshold value, which is user-provisionable.

Clear the LO-RXPOWER Alarm


Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits.

Step 2 Find out whether new channels have been added to the fiber. The number of channels affects power. If channels have been added, power levels of all channels need to be adjusted.

Step 3 Find out whether gain (the amplification power) of any amplifiers has been changed. Changing amplification also causes channel power to need adjustment.

Step 4 If the alarm does not clear, remove any receive fiber attenuators or replace them with lower-resistance attenuators.

Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 6 If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility (line) loopback on a known-good port. The error reading you get is not as precise, but you generally know whether the fiber is faulty. For specific procedures to use the test set equipment, consult the manufacturer.

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

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


Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. 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 no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.132  LOS (BITS)

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

Logical Object: BITS

The LOS (BITS) alarm indicates that the 15310-CL-CTX 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 15310-CL to the timing source.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.133  LOS (DS1)

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

Logical Object: DS1

An LOS (DS1) alarm for a DS-1 port occurs when the port on the port is in service but no signal is being received. The cabling might not be correctly connected to the port, or the line could have no signal.

Clear the LOS (DS1) Alarm


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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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. In node view, double-click the 15310-CL-CTX card to display the card view.

b. Click the Maintenance > DS1 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 green ACT LED is on.

b. To determine this virtually, double-click the 15310-CL-CTX card in CTC to display the card view and complete the following substeps:

Click the Provisioning > DS1> 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.

Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving port 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 fiber connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 7 If a valid signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the port. To do this, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide for procedures. For more information about the cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Step 8 Repeat Steps 1 to 7 for any other port on the card that reports the LOS.

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


2.7.134  LOS (DS3)

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

Logical Object: DS3

The LOS (DS3) for a DS-3 port occurs when the port is in service but no signal is being received. The cabling might not be correctly connected to the port, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure or a fiber cut.


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 Verify that the cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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. In node view, double-click the 15310-CL-CTX card to display the card view.

b. Click the Maintenance > DS3 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 green ACT LED is on.

b. To determine this virtually, double-click the15310-CL-CTX card in CTC to display the card view and complete the following substeps:

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

Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving port 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 15310-CL Procedure Guide.

Step 7 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 15310-CL Procedure Guide for procedures. For more information about the cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Step 8 Repeat Steps 1 to 7 for any other port on the card that reports the LOS.

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


2.7.135  LOS (EC1)

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

Logical Object: EC1

LOS on an EC-1 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (EC1) most likely means that the upstream transmitter has failed. If an EC1 LOS alarm is not accompanied by additional alarms, a cabling problem (such as an incorrect attachment, a fiber cut, or another fiber error) usually causes this alarm. The condition clears when the problem is corrected, allowing two consecutive valid frames to be received.


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 (EC1) Alarm


Step 1 Using site practice, verify cabling continuity to the port reporting the alarm.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 If the cabling is good, verify that the correct port is in service by completing the following steps:

a. Confirm that the ACT LED is green.

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

c. Click the Provisioning > EC1 > 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.

Step 3 If the correct port is in service, use an optical test set to confirm that a valid signal exists on the line. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving port as possible.

Step 4 If the signal is valid, ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 5 Repeat Steps 1 through 4 for any other port on the card that reports the LOS (EC1).

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

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


2.7.136  LOS (FUDC)

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

Logical Object: FUDC

The LOS (FUDC) alarm is raised if there is a user data channel (UDC) circuit created but the port is not receiving signal input. The downstream node raises an AIS condition raised against the port transmitting the UDC. FUDC refers to the 64-kb user data channel using the F1 byte.

Clear the LOS (FUDC) Alarm


Step 1 Using site practices, verify cable continuity to the UDC port.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 Verify that there is a valid input signal using a test set. For instructions to do this, consult the test set manufacturer.

Step 3 If there is a valid signal, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 4 If the alarm does not clear, verify that the UDC is provisioned by completing the following steps:

a. At the network view, click the Provisioning > Overhead Circuits tabs.

b. If no UDC circuit exists, create one. Refer to the "Create Circuits" chapter in the Cisco ONS 15310-CL Procedure Guide for procedures.

c. If a user data circuit exists (shown as User Data F1 under the Type column), check the source and destination ports.

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

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


2.7.137  LOS (OCN)

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

Logical Object: OCN

An LOS alarm on an OC-3 or OC-12 port occurs when a SONET receiver detects an all-zero pattern for 10 microseconds or longer. An LOS alarm means the upstream transmitter has failed. If an OC-3 or OC-12 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 Using site practices, verify fiber continuity to the port.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 If the cabling is good, verify that the correct port is in service by completing the following steps:

a. Confirm that the green ACT LED is on.

b. To determine whether the OC-3 or OC-12 port is in service, double-click the 15310-CL-CTX card in CTC to display the card view.

c. Click the Provisioning > Optical > 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.

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 in the Cisco ONS 15310-CL Procedure Guide.

Step 4 If the alarm does not clear, verify that the power level of the optical signal is within the OC-3 or OC-12 port receiver specifications. The "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide lists these specifications for each OC-N port.

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 Repeat Steps 1 to 5 for any other port on the card reporting the LOS (OC-N).

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

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


2.7.138  LO-TXPOWER

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

Logical Objects: OCN, PPM

The Equipment Low Transmit Power alarm is an indicator for OCN port transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.

Clear the LO-TXPOWER Alarm


Step 1 Display the reporting card's card view.

Step 2 Click the Provisioning > Optics Thresholds tabs.

Step 3 Increase the TX Power Low column value by 0.5 dBm.

Step 4 If the card transmit power setting cannot be increased without affecting the signal, complete the "Physically Replace an Ethernet Card" procedure.


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


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.


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


Step 5 If no ports are shown bad and the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.139  LPBKCRS

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

Logical Objects: STSMON, STSTRM

The Cross-Connect Loopback condition indicates that there is a software cross-connect loopback active between two OC-3 or OC-12 optical ports. A cross-connect loopback test occurs below line speed and does not affect traffic.

For more information on loopbacks, see the "Identify Points of Failure on an Electrical Circuit Path" section.


Note Cross-connect loopbacks occur below line speed. They do not affect traffic.


Clear the LPBKCRS Condition


Step 1 To remove the cross-connect loopback condition, double-click the 15310-CL-CTX card in CTC to display the card view.

Step 2 Complete the "Clear an OC-N Port XC Loopback Circuit" procedure.

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


2.7.140  LPBKDS1FEAC

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

Logical Objects: DS1, DS3

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


Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

Clear the LPBKDS1FEAC Condition


Step 1 In node view, double-click the 15310-CL-CTX card to display the card view.

Step 2 Click the Maintenance > DS1 tabs.

Step 3 Click the cell for the port in the Send Code column and click No Code from the drop-down list.

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


2.7.141  LPBKDS1FEAC-CMD

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

Logical Object: DS1

The DS-1 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-1 FEAC loopback. For more information about FEAC loopbacks, see the "Identify Points of Failure on an Electrical Circuit Path" section.


Note LPBKDS1FEAC-CMD is an informational condition and does not require troubleshooting.



Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

2.7.142  LPBKDS3FEAC

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

Logical Object: DS3

A Loopback Due to FEAC Command DS-3 condition occurs when a DS-3 port loopback signal is received in C-bit line type mode from the far-end node because of an FEAC command. An FEAC command is often used with loopbacks. LPBKDS3FEAC is only reported by these DS-3 ports.


Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).


Note LPBKDS3FEAC is an informational condition and does not require troubleshooting.


Clear the LPBKDS3FEAC Condition


Step 1 In node view, double-click the 15310-CL-CTX card to display the card view.

Step 2 Click the Maintenance > DS3 > Line tabs.

Step 3 Click the cell for the port in the Send Code column and click No Code from the drop-down list.

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


2.7.143  LPBKDS3FEAC-CMD

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

Logical Object: DS3

The DS-3 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-3 FEAC loopback.


Note LPBKDS3FEAC-CMD is an informational condition and does not require troubleshooting.


2.7.144  LPBKFACILITY (CE100T)

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

Logical Object: CE100T

A Loopback Facility condition on a CE-100T-8 port occurs when a software facility (line) loopback is active for a port on the card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Network Troubleshooting Tests" section.

Clear the LPBKFACILITY (CE100T) Condition


Step 1 Complete the "Clear an Ethernet Card Loopback Circuit" procedure.

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


2.7.145  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 15310-CL-CTX card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Identify Points of Failure on an Electrical Circuit Path" section. Facility loopbacks are described in the "Network Troubleshooting Tests" 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 lock out 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 a DS-3 or DS-1 Port Loopback Circuit" procedure.

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


2.7.146  LPBKFACILITY (EC1)

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

Logical Object: EC1

A Loopback Facility condition for an EC-1 port occurs when a software facility (line) loopback is active for a port on the reporting EC1 port of the 15310-CL-CTX card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Network Troubleshooting Tests" section.


Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are Service-Affecting (SA).

Clear the LPBKFACILITY (EC1) Condition


Step 1 Complete the "Clear an EC-1 Port Loopback" procedure.

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


2.7.147  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 an OC-3 or OC-12 port on the 15310-CL-CTX card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Identify Points of Failure on an OC-N Circuit Path" section. Facility loopbacks are described in the "Facility Loopback" section.


Note OC-N 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-3 or OC-12 port, 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 15310-CL containing the loopback OC-3 or OC-12.


Clear the LPBKFACILITY (OCN) Condition


Step 1 Complete the "Clear an OC-N Port Facility or Terminal Loopback Circuit" procedure.

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


2.7.148  LPKTERMINAL (CE100T)

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

Logical Object: CE100T

A Loopback Terminal condition on a CE-100T-8 port occurs when a software terminal loopback is active for a port on the card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Network Troubleshooting Tests" section.

Clear the LPBKTERMINAL (CE100T) Condition


Step 1 Complete the "Clear an Ethernet Card Loopback Circuit" procedure.

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


2.7.149  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 DS1 or DS3 port. 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 "Identify Points of Failure on an Electrical Circuit Path" section. Facility loopbacks are described in the "Network Troubleshooting Tests" section.

Clear the LPBKTERMINAL (DS1, DS3) Condition


Step 1 Complete the "Clear a DS-3 or DS-1 Port Loopback Circuit" procedure.

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


2.7.150  LPBKTERMINAL (EC1)

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

Logical Object: EC1

A Loopback Terminal condition for an EC-1 port occurs when a software terminal (inward) loopback is active for an EC1 port on the 15310-CL-CTX card.

For information about troubleshooting optical circuits with loopbacks, refer to the "Network Troubleshooting Tests" section.


Caution CTC permits loopbacks to be performed on in-service (IS) circuits. Loopbacks are Service-Affecting (SA).

Clear the LPBKTERMINAL (EC1) Condition


Step 1 Complete the "Clear an EC-1 Port Loopback" procedure.

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


2.7.151  LPBKTERMINAL (OCN)

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

Logical Object: OCN

A Loopback Terminal condition for an OC-N port occurs when a software terminal (inward) loopback is active for an OC-3 or OC-12 port on the 15310-CL-CTX card.


Note OC-N terminal loopbacks do not typically return an AIS.



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 "Identify Points of Failure on an Electrical Circuit Path" section; for optical circuits, refer to the "Identify Points of Failure on an OC-N Circuit Path" section. Terminal loopbacks are described in the "Terminal Loopback" section.

Clear the LPBKTERMINAL (OCN) Condition


Step 1 Complete the "Clear an OC-N Port Facility or Terminal Loopback Circuit" procedure.

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


2.7.152  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 has a preset value of -44 VDC and is not 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 15310-CL Procedure Guide.)

Clear the LWBATVG Alarm


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

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


2.7.153  MAN-REQ

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

Logical Objects: 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.154  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.155  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.156  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.157  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.158  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 a third timing source.


Note MANSWTOTHIRD is an informational condition and does not require troubleshooting.


2.7.159  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 Path Protection Span External Switching Command" procedure.

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


2.7.160  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 is installed in the slot reporting the MEA alarm. In node view, click the Inventory tab and compare it to the actual installed card.

Step 2 If you prefer the card type depicted by CTC, complete the "Physically Replace an Ethernet Card" procedure for the reporting 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 3 If you prefer the card that physically occupies the slot but 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 and right-click to choose Delete Card.

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


Note If the card is in service, does have a circuit 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 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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.161  MEA (FAN)

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

Logical Object: FAN

The MEA alarm is reported against the fan unit located inside the ONS 15310-CL if it has a fuse problem.

This alarm is not user-serviceable. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.

2.7.162  MEA (PPM)

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

Logical Object: PPM

The Missing Equipment Attributes alarm for the PPM is raised on the 15310-CL-CTX card when a PPM is misprovisioned or unsupported. It can occur when you plug in a multirate PPM without first preprovisioning it, or when you provision the PPM for a wavelength that is explicitly not the first tunable wavelength.

Clear the MEA (PPM) Alarm


Step 1 To provision the multirate PPM you must first create it in CTC. To do this, complete the following steps:

a. Double-click the 15310-CL-CTX card to display the card view.

b. Click the Provisioning > Pluggable Port Modules tabs. (If you already see the PPM listed in the Pluggable Port Modules Area, go to Step 2.)

c. Under the Pluggable Port Modules area, click Create.

d. In the Create PPM dialog box, choose the PPM number from the drop-down list (for example, PPM 1).

e. Choose the PPM type from the second drop-down list, for example PPM (1 Port).

f. Click OK.


Note For more information about configuring PPMs, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.


Step 2 After you have created the PPM, or if you see it listed in the Pluggable Port Modules area but not in the Selected PPM area, choose the port rate by completing the following steps:

a. Under the Selected PPM area, click Create.

b. In the Create Port dialog box, choose the port (for example, 1-1) from the drop-down list.

c. Choose the correct port type from the drop-down list. (For more information about selecting PPM port types, refer to the "Change Node Settings" chapter in the Cisco ONS 15310-CL Procedure Guide.)

d. Click OK.

Step 3 If you see the port listed in the Pluggable Port Modules area and the Selected PPM, the MEA indicates that the incorrect port rate was selected. Click the port in the Selected PPM area and click Delete.

Step 4 Complete Step 2 to correctly provision the port rate.

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


2.7.163  MEM-GONE

Default Severity: Major (MJ), Non-Service-Affecting (NSA)

Logical Object: EQPT

The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the 15310-CL-CTX card. The 15310-CL-CTX 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.164  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 15310-CL-CTX 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.165  MFGMEM

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

Logical Objects: BPLANE, FAN, PPM

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 15310-CL-CTX cannot read this memory. EEPROM stores manufacturing data that a 15310-CL-CTX card uses to determine system compatibility and shelf inventory status. Unavailability of this information can cause less-significant problems.

To clear the MFGMEM alarm, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) to report a Service-Affecting (SA) problem.

2.7.166  NO-CONFIG

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

Logical Object: EQPT

The No Startup Configuration condition applies to ML-100T-8 Ethernet cards and occurs when no startup configuration file has been downloaded to the 15310-CL-CTX card, whether or not you preprovision the card slot. This alarm can occur during provisioning. When the startup configuration file is copied to the 15310-CL-CTX card, the alarm clears.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the NO-CONFIG Condition


Step 1 Create a startup configuration for the card in Cisco IOS.

Follow the card provisioning instructions in the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.

Step 2 Upload the configuration file to the 15310-CL-CTX card by completing the following steps:

a. In node view, right-click the ML-100T-8 Ethernet card graphic.

b. Choose IOS Startup Config from the shortcut menu.

c. Click Local > CTX and navigate to the file location.

Step 3 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure.

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


2.7.167  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-69 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.168  OOU-TPT

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

Logical Objects: STSTRM, VT-TERM

The Out of Use Transport Failure alarm is a VCAT member alarm. (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. It occurs in conjunction with the "VCG-DEG" alarm on page 2-133.

Clear the OOT-TPT Condition


Step 1 Complete the "Clear the VCG-DEG Condition" procedure. Clearing that condition clears this condition as well.

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


2.7.169  OPEN-SLOT

The OPEN-SLOT condition is not used in this platform in this release. It is reserved for future development.

2.7.170  PDI-P

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

Logical Objects: STSMON, STSTRM

A PDI-P is a set of application-specific codes indicating a signal label mismatch failure (SLMF) in the ONS 15310-CL STS path overhead. The condition indicates to downstream equipment that a defect is present 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-3 or OC-12 port supporting an ONS 15310-CL Ethernet card circuit could result from the end-to-end Ethernet link integrity feature of the Ethernet card. If the link integrity is the cause of the path defect, it is typically accompanied by the "CARLOSS (EQPT)" alarm on page 2-34 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.


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 15310-CL to initialize fully. If the incomplete state does not change after full initialization, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC to report a Service-Affecting (SA) problem (1 800 553-2447).

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

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


Caution Deleting a circuit can affect existing traffic.

Step 4 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits" chapter in the Cisco ONS 15310-CL Procedure Guide for procedures.

Step 5 If the circuit deletion and re-creation does not clear the condition, verify that there is no problem with the far-end OC-3 or OC-12 port providing STS payload to the reporting card.

Step 6 If the condition does not clear, confirm that the cross-connect between the OC-3 or OC-12 port and the reporting port is good.

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 in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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


2.7.171  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 an invalid C2 byte value in the SONET path overhead.

This alarm can occur on the 15310-CL-CTX 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.

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


2.7.172  PLM-V

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

Logical Object: VT-TERM

A Payload Label Mismatch VT Layer alarm raises when the content of the V5 byte in the SONET overhead is inconsistent or invalid. PLM-V occurs when ONS 15310-CLs interoperate with equipment that performs bit-synchronous mapping for DS-1 signal. The ONS 15310-CL 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 alarm will occur if your signal source uses VT6 or VT9 mapping, because this is not supported by the 15310-CL-CTX card.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.173  PRC-DUPID

The PRC-DUPID alarm is not used in this platform in this release. It is reserved for future development.

2.7.174  PROTNA

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

2.7.175  PROV-MISMATCH

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

Logical Object: PPM

The Provisioning Mismatch for a PPM alarm is raised against a PPM connector on the 15310-CL-CTX card under one or more of the following circumstances:

The physical PPM's range or wavelength does not match the provisioned value. PPMs have static wavelength values which must match the wavelengths provisioned for the card.

The PPM's reach (loss) value does not meet the reach value needed for the card.

The reach of the inserted PPM does not match the physical PPM.

Clear the PROV-MISMATCH Alarm


Step 1 Determine what the PPM wavelength range should be by viewing the frequency provisioned for the card by completing the following steps:

a. Double-click the 15310-CL-CTX card to display the card view.

b. Click the Maintenance > Info tabs.

c. Record the value shown in the Value column.

Step 2 Remove the incorrect PPM connector by completing the following steps:


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

a. Unplug the PPM connector and fiber from the reporting card.

b. if the PPM connector has a latch securing the fiber cable, pull the latch upward to release the cable.

c. Pull the fiber cable straight out of the connector.


Note For more information about configuring PPMs, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.


Step 3 Replace the unit with the correct PPM connector by completing the following steps:

a. Plug the fiber into a Cisco-supported PPM connector. For more information about supported small form-factor pluggables (SFPs), refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

b. If the new PPM connector has a latch, close the latch over the cable to secure it.

c. Plug the cabled PPM connector into the card port until it clicks.

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


2.7.176  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 electrical line card or the 15310-CL-CTX.


Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals. Statement 43

Clear the PWR-FAIL-A Alarm


Step 1 If a single port has reported the alarm, take the following actions depending on the reporting entity:

If the reporting port 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 15310-CL-CTX card, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

Step 2 If the alarm does not clear, reseat the power cable connection to the connector. For more information about power connections, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 3 If the alarm does not clear, physically replace the power cable connection to the connector.

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


2.7.177  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 electrical line card or the 15310-CL-CTX card.


Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or weld the metal object to the terminals. Statement 43

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.178  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 a DS-3 port 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.179  RFI-L

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

Logical Objects: EC1, OCN

A Remote Fault Indication (RFI) Line condition occurs when the ONS 15310-CL detects an RFI in OC-3 or OC-12 port 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 of the reporting ONS 15310-CL.

Step 2 Identify and clear any alarms, particularly the "LOS (OCN)" alarm on page 2-87.

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


2.7.180  RFI-P

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

Logical Objects: STSMON, STSTRM

An RFI Path condition occurs when the ONS 15310-CL 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 15310-CL by completing the following steps:

a. Confirm that the green ACT LED is on.

b. To determine whether the OC-3 or OC-12 port is in service, double-click the 15310-CL-CTX card in CTC to display the card view.

c. Click the Provisioning > Optical > 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.

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

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


2.7.181  RFI-V

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

Logical Objects: VTMON, VT-TERM

An RFI VT Layer condition occurs when the ONS 15310-CL 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 fiber connectors are securely fastened and connected to the correct slot. For more information, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 If connectors are correctly connected, verify that the port is active and in service (IS-NR) by completing the following steps:

a. Confirm that the green ACT LED is on.

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

c. Click the Provisioning > Optical > 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.

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

Step 5 Clear alarms in the far-end node, especially the "UNEQ-P" alarm on page 2-130 or the "UNEQ-V" alarm on page 2-132.

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


2.7.182  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 done 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.183  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.184  RPRW

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

Logical Object: CE100T

The Resilient Packet Ring (RPR) Wrapped condition applies to the CE100T-8 card and occurs when the RPR protocol initiates a ring wrap due to a fiber cut, node failure, node restoration, new node insertion, or other traffic problem. When the wrap occurs, traffic is redirected to the original destination by sending it in the opposite direction around the ring after a link state change or after receiving any SONET path-level alarms.

Clear the RPRW Condition


Step 1 Look for and clear any service-affecting SONET path-level alarms on the affected circuit, such as the "LOP-P" alarm on page 2-80, "PLM-P" alarm on page 2-104, or the "TIM-P" alarm on page 2-128. Clearing this alarm can also clear RPRW.

Step 2 If the condition does not clear, look for and clear any service alarms for the Ethernet card itself, such as the "CARLOSS (CE100T)" alarm on page 2-32 or the "TPTFAIL (CE100T)" alarm on page 2-129.

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


2.7.185  RUNCFG-SAVENEED

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

Logical Object: EQPT

The Run Configuration Save Needed condition occurs when you change the running configuration file for ML-100T-8 card. It is a reminder that you must save the change to the startup configuration file for it to be permanent.

The condition clears after you save the running configuration to the startup configuration, such as by entering the following command at the CLI:

copy run start
 
   

at the privileged EXEC mode of the Cisco IOS CLI. If you do not save the change, the change is lost after the card reboots. If the command "copy run start" is executed in configuration mode and not privileged EXEC mode, the running configuration will be saved, but the alarm will not clear.

2.7.186  SD

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

Logical Objects: DS1, DS3

A Signal Degrade condition for a DS-1 or DS-3 signal occurs when the quality of an electrical signal has exceeded the 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 conditions, but SD is triggered at a lower bit error rate 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 ports that are In-Service and Normal (IS-NR); Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AIS); or Out-of-Service and Management, Maintenance (OOS-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 15310-CL-CTX card resets 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 of time 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 ports is the Omniber 718.


Clear the SD (DS1, DS3) Condition


Step 1 Complete the "Clear a DS-3 or DS-1 Port Loopback Circuit" procedure.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 2 Ensure that the fiber connector for the port is completely plugged in. For more information about cable connections, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 3 If the BER threshold is correct and at the expected level, use a 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 power level is good, verify that receive levels are within the acceptable range. The correct specifications are listed in the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

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 in the Cisco ONS 15310-CL Procedure Guide.

Step 6 If the condition does not clear, verify that single-mode fiber 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. If no practice exists, use the procedure in the "Maintain the Node" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 9 If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement.

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


2.7.187  SD-L

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

Logical Objects: EC1, OCN

An SD Line condition applies to the line level of the SONET signal and travels on the B2 byte of the SONET overhead. An SD-L condition on an Ethernet card or OC-3 port does not cause a protection switch. If the condition is reported on a port 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) or LOS (OCN).

Clear the SD-L Condition


Step 1 Complete the "Clear an OC-N Port Facility or Terminal Loopback Circuit" procedure.

Step 2 Ensure that the fiber connector for the port is completely plugged in. For more information about fiber connections, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL 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. The correct specifications are listed in the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.

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 in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

Step 6 If the condition does not clear, verify that single-mode fiber 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.

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


2.7.188  SD-P

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

Logical Objects: STSMON, STSTRM

An SD Path condition applies to the path (STS) layer of the SONET overhead. A path or ST-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 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E-6 dBm. An SD-P condition causes a switch from the working port to the protect port at the path (STS) level.

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.

SD causes the port to switch from working to protect. The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered it.

Clear the SD-P Condition


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

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


2.7.189  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" condition on page 2-112, 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. An SD-V condition does not cause a switch from the working port to the protect port at the path (STS) level.

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.

SD causes the port to switch from working to protect. The SD condition clears when the BER level falls to one-tenth of the threshold level that triggered it.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.190  SF

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

Logical Objects: DS1, DS3

A Signal Fail 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 15310-CL.

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


2.7.191  SF-L

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

Logical Objects: EC1, OCN

An SF Line condition 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 higher-priority alarms such as LOF (OCN) or 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.192  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-116, 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-L Condition" procedure.

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


2.7.193  SFTWDOWN

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

Logical Object: EQPT

A Software Download in Progress alarm occurs when the 15310-CL-CTX card is downloading or transferring software.

No action is necessary. Wait for the transfer or the software download to complete. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


Note SFTWDOWN is an informational alarm.


2.7.194  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" condition on page 2-115, but it applies to the VT layer of the SONET overhead.

Clear the SF-V Condition


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

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


2.7.195  SNTP-HOST

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

Logical Object: NE

The Simple Network Timing Protocol (SNTP) Host Failure alarm indicates that an ONS 15310-CL serving as an IP proxy for the other nodes in the ring is not forwarding SNTP information to the other ONS 15310-CL 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 15310-CL (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 which could affect the SNTP server/router connecting to the proxy ONS system.

Step 3 If no network problems exist, ensure that the ONS 15310-CL proxy is provisioned correctly by completing the following steps:

a. In node view for the ONS 15310-CL 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, click 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 "Cisco Transport Controller Operation" chapter in the Cisco ONS 15310-CL Reference Manual for more information on SNTP Host for general information about working with SNTP. Refer to the "Turn Up Node" chapter in the Cisco ONS 15310-CL Procedure Guide.

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


2.7.196  SQUELCH

The SQUELCH condition is not used in this platform in this release. It is reserved for future development.

2.7.197  SQUELCHED

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

2.7.198  SQM

Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Default Severity: Major (MJ), Service-Affecting (SA) for VT-TERM

Logical Objects: STSTRM, VT-TERM

The Sequence Mismatch alarm 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 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" chapter in the Cisco ONS 15310-CL Procedure Guide.

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


2.7.199  SSM-DUS

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

Logical Objects: BITS, DS1, OCN

The Synchronization Status (SSM) Message 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.200  SSM-FAIL

Single Failure Default Severity: Minor (MN), Non-Service-Affecting (NSA); Double Failure Default Severity: Major (MJ), Service-Affecting (SA)

Logical Objects: BITS, DS1, OCN

The SSM Failed alarm occurs when the synchronization status messaging received by the ONS 15310-CL fails. The problem is external to the ONS 15310-CL. This alarm indicates that although the ONS 15310-CL 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.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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


2.7.201  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 condition is raised when 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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.202  SSM-PRS

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

Logical Objects: BITS, DS1, 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.203  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.204  SSM-SMC

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

Logical Objects: BITS, DS1, 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.205  SSM-ST2

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

Logical Objects: BITS, DS1, 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.206  SSM-ST3

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

Logical Objects: BITS, DS1, 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.207  SSM-ST3E

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

Logical Objects: BITS, DS1, 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.208  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.209  SSM-STU

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

Logical Objects: BITS, DS1, 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 15310-CL 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 15310-CL.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.210  SSM-TNC

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

Logical Objects: BITS, NE-SREF, OCN

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.211  SW-MISMATCH

The SW-MISMATCH condition is not used in this platform in this release. It is reserved for future development.

2.7.212  SWMTXMOD-PROT

The SWMTXMOD-PROT alarm is not used in this platform in this release. It is reserved for future development.

2.7.213  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 15310-CL-CTX when a logic component internal to the 15310-CL-CTX cross connect is OOF with a traffic card in the system. In this case, the alarm is raised against the traffic card slot.

Clear the SWMTXMOD-WORK Alarm


Step 1 Complete the "Soft- or Hard-Reset an Ethernet Card in CTC" procedure for the 15310-CL-CTX. For the LED behavior, see the "Typical 15310-CL-CTX Card or Ethernet 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, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.214  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 15310-CL switches to the primary timing source (reference 1). The ONS 15310-CL 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.215  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 15310-CL 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-125.

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


2.7.216  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 15310-CL 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-125 or the "SYNCSEC" alarm on page 2-125.

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


2.7.217  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 SYNC-FREQ condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.218  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 15310-CL loses the primary timing source (reference 1). The ONS 15310-CL 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 15310-CL should switch to its secondary timing source (reference 2). Switching to a secondary timing source also triggers the "SWTOSEC" alarm on page 2-123.

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 15310-CL, complete the "Clear the LOS (OCN) Alarm" procedure.

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


2.7.219  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 15310-CL loses a secondary timing source (reference 2). If SYNCSEC occurs, the ONS 15310-CL 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-124.

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 15310-CL, complete the "Clear the LOS (OCN) Alarm" procedure.

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


2.7.220  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 15310-CL loses the third timing source (reference 3). If SYNCTHIRD occurs and the ONS 15310-CL uses an internal reference for source three, the 15310-CL-CTX card could have failed. The system often reports either the "FRNGSYNC" condition on page 2-59 or the "HLDOVRSYNC" condition on page 2-66 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 "Turn Up Node" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 3 If the third timing source is a BITS input, complete the "Clear the LOS (BITS) Alarm" procedure.

Step 4 If the third timing source is an incoming port on the ONS 15310-CL, complete the "Clear the LOS (OCN) Alarm" procedure.

Step 5 If the third timing source uses the internal ONS 15310-CL timing, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447).


2.7.221  SYSBOOT

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

Logical Object: NE

The System Reboot alarm indicates that new software is booting on the 15310-CL-CTX card. No action is required. The alarm clears when all cards finish rebooting the new software. The reboot takes up to 30 minutes.

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


Note SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.


2.7.222  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 or the receiving port could not connect 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 "LOF (OCN)" alarm on page 2-79 or the "UNEQ-P" alarm on page 2-130. 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 15310-CL, refer to the "Install Hardware" chapter in the Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL.

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 15310-CL routes circuits automatically, the circuit route could have been changed using TL1.) If necessary, manually correct the routing using TL1. For instructions, refer to the Cisco ONS SONET TL1 Reference Guide and the Cisco SONET TL1 Command Guide.

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


2.7.223  TIM-MON

The TIM-MON alarm is not used in this platform in this release. It is reserved for future development.

2.7.224  TIM-P

Default Severity: Critical (CR), Service-Affecting (SA) for STSTRM; Default Severity: Minor (MN), Non-Service-Affecting (NSA) for STSMON

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 Complete the "Clear the TIM Alarm" procedure. (The option will say "Edit J1 Path Trace" rather than "Edit J0 Path Trace.")

Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the alarm applies to the STSTRM object, it is Service-Affecting (SA).


2.7.225  TIM-S

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

Logical Objects: EC1, OCN

The TIM for Section Overhead alarm occurs when there is a mismatch between the expected and received J0 section overhead strings in either Manual or Auto mode.

In manual mode at the 15310-CL-CTX card Section Trace window, the user enters 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-S 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 problem.

TIM-S also occurs on a port that has previously been operating without alarms if someone switches the cables or optical fibers that connect the ports. If enabled on the port, the "AIS-L" condition on page 2-19 can be raised downstream and the "RFI-L" condition on page 2-108 can be raised upstream.


Note AIS-L and RFI-L are disabled or enabled in the Disable AIS/RDI on TIM-S? check box on the Provisioning > EC1 > Section Trace tab.


Clear the TIM-S Alarm


Step 1 Double-click the 15310-CL-CTX card to display the card view.

Step 2 Click the Provisioning > EC1 > Section Trace tabs.

Step 3 Choose the port from the Port pull-down.

Step 4 In the Expected area, enter the correct string into the Current Expected String field.

Step 5 Click Apply.

Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the alarm applies to the STSTRM object, it is Service-Affecting (SA).


2.7.226  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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) to report a service-affecting problem.


2.7.227  TPTFAIL (CE100T)

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

Logical Object: CE100T

The Transport (TPT) Layer Failure alarm for the CE-100T-8 card indicates a break in the end-to-end Ethernet link integrity feature of the ONS 15310-CL CE-100T-8 card. TPTFAIL indicates a far-end condition and not a problem with the port reporting TPTFAIL. TPTFAIL may also occurs on local ports with LCAS-enabled CE-100T-8 cards.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the TPTFAIL (CE100T) Alarm


Step 1 Clear any alarms being reported by the OC-N port on the CE100T-8 circuit.

Step 2 If no alarms are reported by the OC-N port, or if the "PDI-P" condition on page 2-103 is reported, the problem could be on the far-end G1000-2 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/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.228  TX-AIS

The TX-AIS condition is not used in this platform in this release. It is reserved for future development.

2.7.229  TX-LOF

The TX-LOF condition is not used in this platform in this release. It is reserved for future development.

2.7.230  TX-RAI

The TX-RAI condition is not used in this platform in this release. It is reserved for future development.

2.7.231  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-3 ports and the "AIS-P" condition on page 2-19 is reported on the terminating ports. These alarms clear when the circuit carries a signal.


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 rows 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. Complete the "Delete a Circuit" procedure.

b. If an error message dialog box appears, the VT tunnel is valid and not the cause of the alarm.

c. If any other columns contain VTT, repeat Step 6.

Step 7 If all ONS 15310-CL 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.

Step 8 If you find circuits listed as incomplete, 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 15310-CL.

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits" chapter in the Cisco ONS 15310-CL Procedure Guide.

Step 11 Log back in and verify that all circuits terminating in the reporting port are active by completing the following steps:

a. Click the Circuits tab.

b. Verify that the Status column lists all circuits as active.

Step 12 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter in the Cisco ONS 15310-CL 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 13 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447) in order to report a Service-Affecting (SA) problem.


2.7.232  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 zeroes. 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 15310-CL.

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


2.7.233  VCG-DEG

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

Logical Object: VCG

The VCAT Group Degraded alarm is a VCAT group alarm. The condition occurs when one member circuit carried by the ML-100T-8 Ethernet card is down. This condition is accompanied by the "OOU-TPT" alarm on page 2-102. It only occurs when a Critical (CR) alarm, such as LOS, causes a signal loss.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the VCG-DEG Condition


Step 1 Look for and clear any Critical (CR) alarms that apply to the errored card or port.

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


2.7.234  VCG-DOWN

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

Logical Object: VCG

The VCAT Group Down alarm is a VCAT group alarm. The condition occurs when both member circuits carried by the ML-100T-8 Ethernet card are down. This condition occurs in conjunction with another Critical (CR) alarm.


Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.


Clear the VCG-DOWN Condition


Step 1 Complete the "Clear the VCG-DEG Condition" procedure.

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


2.7.235  WKSWPR

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

Logical Objects: OCN, STSMON, VT-MON

The Working Switched To Protection condition occurs when a line experiences the "LOS (OCN)" alarm on page 2-87.

This condition is also raised when you use the FORCE RING, FORCE SPAN, or MANUAL SPAN command at the network level. WKSWPR is visible on the network view Alarms, Conditions, and History tabs.

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 Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).


2.7.236  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-134 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  15310-CL-CTX Line Alarms

The 15310-CL-CTX card DS1 port provides three line types: ESF, D4, or Unframed. The choice of framing format determines the line alarms that the 15310-CL-CTX 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.

Table 2-13 DS3-1 Alarms by Line Type 

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 15310-CL Traffic Card LED Activity

ONS 15310-CL card LED behavior patterns are listed in the following sections.

2.9.1  Typical 155310-CL-CTX Card or Ethernet Card LED Activity After Insertion

When a traffic card is inserted, the following LED activities occur:

1. The ACT LED blinks once and turns off for 5 to 10 seconds.

2. The ACT LED turns on.

2.9.2  Typical 15310-CL-CTX Card or Ethernet Card LED Activity During Reset

When a traffic card is inserted, the following LED activities occur:

1. The ACT LED blinks once and turns off for 5 to 10 seconds.

2. The ACT LED turns on.

2.10  Frequently Used Alarm Troubleshooting Procedures

This section provides procedures that are frequently used when troubleshooting alarms. Most of these procedures are summarized versions of more detailed procedures found in the Cisco ONS 15310-CL Procedure Guide. They are included in this chapter for the user's convenience. For further information, please refer to the Cisco ONS 15310-CL Procedure Guide.

2.10.1  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. A Force switch switches traffic on a working path even if the path has signal degrade (SD) or signal fail (SF) conditions. A Force switch does not switch traffic on a protect path. A Force switch preempts a Manual 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.


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 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. A Manual switch 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 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 revert traffic.



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 Force Switch for All Circuits on a Path Protection Span

This procedure 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. A Force switch has a higher priority than a Manual 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.


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 switches all circuits in a path protection from the working span to the protect. It is used to remove traffic from a port 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 ports that originate or terminate path protection circuits.


Caution The Lock Out of Protect 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 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 switch to protect (or working) moves traffic back to the working port. If ports are not configured as revertive, 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.


2.10.2  CTC Card Resetting and Switching

Soft- or Hard-Reset an Ethernet Card in CTC


Note The hard-reset option is enabled on CE-100T-8 and ML-100T-8 cards only when the card is placed in the OOS-MA,MT service state.



Note Hard-resetting a traffic card causes a traffic hit in the ONS 15310-CL. To preserve traffic flow, perform a traffic switch in the "Protection Switching, Lock Initiation, and Clearing" section as appropriate.



Note Soft-resetting an ML-100T-8 Ethernet traffic card causes a traffic hit. To preserve traffic flow, perform a traffic switch in the "Protection Switching, Lock Initiation, and Clearing" section as appropriate. Soft-resetting a CE-100T-8 card is errorless. For more information about Ethernet cards, refer to the Cisco ONS 15310-CL Ethernet Card Software Feature and Configuration Guide.



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 Ethernet card slot reporting the alarm.

Step 3 Right-click the card. Choose Hard-Reset Card or Soft-Reset Card from the shortcut menu.

Step 4 Click Yes in the Resetting Card dialog box.


Soft- or Hard-Reset a 15310-CL-CTX Card


Caution Hard-resetting a 15310-CL-CTX card can cause a traffic hit. A soft reset causes a traffic hit only if a provisioning change or firmware upgrade has occurred. This can be traffic-affecting. To preserve traffic flow, perform a traffic switch in the "Protection Switching, Lock Initiation, and Clearing" section as appropriate.


Note The reset options are enabled only in the OOS-MA,MT service state.



Note Before you reset the 15310-CL-CTX 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 Right-click the active 15310-CL-CTX card in CTC.

Step 3 Choose Hard-Reset Card or Soft-Reset Card from the shortcut menu.


Caution Hard-resetting a 15310-CL-CTX card can cause a traffic hit. A soft reset causes a traffic hit only if a provisioning change or firmware upgrade has occurred. This can be traffic-affecting. To preserve traffic flow, perform a traffic switch in the "Protection Switching, Lock Initiation, and Clearing" section as appropriate.


Note The hard-reset option is enabled only when the card is placed in the OOS-MA,MT service state.


Step 4 Click Yes in the Confirmation Dialog box.

If you performed a hard reset, the connection to the node is lost. CTC switches to network view.

Step 5 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Typical 15310-CL-CTX Card or Ethernet Card LED Activity During Reset" section.


2.10.3  Physical Card Reseating and Replacement

Remove and Reinsert (Reseat) an Ethernet 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 an Ethernet Card


Step 1 Open the card ejectors.

Step 2 Slide the card out of the slot.

Step 3 Open the ejectors on the replacement card.

Step 4 Slide the replacement card into the slot along the guide rails.

Step 5 Close the ejectors.


2.10.4  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 > Optical > Line tabs.

Step 4 Under the SD BER (or SF BER) column in the Provisioning window, 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 DCC Terminations


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

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 Port 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 15310-CL-CTX card in CTC to display the card view.

Step 3 Click the Maintenance > Optical > 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.


Clear an OC-N Port 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 > Optical > Loopback > SONET STS tabs.

Step 4 Click Apply.


Clear a DS-3 or DS-1 Port 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 the15310-CL-CTX card in CTC to display the card view.

Step 3 Click the Maintenance > DS3 > Line or the Maintenance > DS1 > Line 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.


Clear an EC-1 Port 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 > EC1 > Loopback > Line 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.


Clear an Ethernet Card Loopback Circuit

This procedure applies to CE-100T-8 or ML-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.