Cisco ONS 15310-CL Troubleshooting Guide, Release 5.0
Chapter 2, Alarm Troubleshooting
Downloads: This chapterpdf (PDF - 1.42MB) The complete bookPDF (PDF - 4.41MB) | 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 (NA) 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 Index 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  Service Effect

2.5.5  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  APSB

Clear the APSB Alarm

2.7.7  APSCDFLTK

2.7.8  APSC-IMP

2.7.9  APSCINCON

Clear the APSCINCON Alarm

2.7.10  APSCM

Clear the APSCM Alarm

2.7.11  APSIMP

Clear the APSIMP Alarm

2.7.12  APS-INV-PRIM

2.7.13  APSMM

Clear the APSMM Alarm

2.7.14  APS-PRIM-FAC

Clear the APS-PRIM-FAC Condition

2.7.15  APS-PRIM-SEC-MISM

Clear the APS-PRIM-SEC-MISM Alarm

2.7.16  AS-CMD

Clear the AS-CMD Condition

2.7.17  AS-MT

Clear the AS-MT Condition

2.7.18  AS-MT-OOG

Clear the AS-MT-OOG Condition

2.7.19  AUD-LOG-LOSS

Clear the AUD-LOG-LOSS Condition

2.7.20  AUD-LOG-LOW

2.7.21  AU-LOF

2.7.22  AUTOLSROFF

2.7.23  AUTORESET

Clear the AUTORESET Alarm

2.7.24  AUTOSW-AIS

Clear the AUTOSW-AIS Condition

2.7.25  AUTOSW-LOP (STSMON)

Clear the AUTOSW-LOP (STSMON) Condition

2.7.26  AUTOSW-LOP (VT-MON)

Clear the AUTOSW-LOP (VT-MON) Alarm

2.7.27  AUTOSW-PDI

Clear the AUTOSW-PDI Condition

2.7.28  AUTOSW-SDBER

Clear the AUTOSW-SDBER Condition

2.7.29  AUTOSW-SFBER

Clear the AUTOSW-SFBER Condition

2.7.30  AUTOSW-UNEQ (STSMON)

Clear the AUTOSW-UNEQ (STSMON) Condition

2.7.31  AUTOSW-UNEQ (VT-MON)

Clear the AUTOSW-UNEQ (VT-MON) Alarm

2.7.32  BAT-FAIL

Clear the BAT-FAIL Alarm

2.7.33  BKUPMEMP

Clear the BKUPMEMP Alarm

2.7.34  CARLOSS (CE100T)

Clear the CARLOSS (CE100T) Alarm

2.7.35  CARLOSS (EQPT)

Clear the CARLOSS (EQPT) Alarm

2.7.36  CLDRESTART

Clear the CLDRESTART Condition

2.7.37  COMIOXC

Clear the COMIOXC Alarm

2.7.38  CONTBUS-IO-A

Clear the CONTBUS-IO-A Alarm

2.7.39  CTNEQPT-PBWORK

Clear the CTNEQPT-PBWORK Alarm

2.7.40  DATAFLT

Clear the DATAFLT Alarm

2.7.41  DS3-MISM

Clear the DS3-MISM Condition

2.7.42  DUP-IPADDR

Clear the DUP-IPADDR Alarm

2.7.43  DUP-NODENAME

Clear the DUP-NODENAME Alarm

2.7.44  EHIBATVG

Clear the EHIBATVG Alarm

2.7.45  ELWBATVG

Clear the ELWBATVG Alarm

2.7.46  ENCAP-MISMATCH-P

Clear the ENCAP-MISMATCH-P Alarm

2.7.47   EOC

Clear the EOC Alarm

2.7.48  EOC-L

Clear the EOC-L Alarm

2.7.49  EQPT

Clear the EQPT Alarm

2.7.50  EQPT-MISS

2.7.51  ERFI-P-CONN

Clear the ERFI-P-CONN Condition

2.7.52  ERFI-P-PAYLD

Clear the ERFI-P-PAYLD Condition

2.7.53  ERFI-P-SRVR

Clear the ERFI-P-SRVR Condition

2.7.54  ERROR-CONFIG

Clear the ERROR-CONFIG Alarm

2.7.55  ETH-LINKLOSS

Clear the ETH-LINKLOSS Condition

2.7.56  EXCCOL

Clear the EXCCOL Alarm

2.7.57  EXT

Clear the EXT Alarm

2.7.58  EXTRA-TRAF-PREEMPT

2.7.59  FAILTOSW

Clear the FAILTOSW Condition

2.7.60  FAILTOSW-PATH

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration

2.7.61  FAN

2.7.62  FAN-DEGRADE

2.7.63  FE-AIS

Clear the FE-AIS Condition

2.7.64  FE-DS1-MULTLOS

2.7.65  FE-DS1-NSA

2.7.66  FE-DS1-SA

2.7.67  FE-DS1-SNGLLOS

2.7.68  FE-DS3-NSA

Clear the FE-DS3-NSA Condition

2.7.69  FE-DS3-SA

Clear the FE-DS3-SA Condition

2.7.70  FE-EQPT-NSA

Clear the FE-EQPT-NSA Condition

2.7.71  FE-FRCDWKSWBK-SPAN

2.7.72  FE-FRCDWKSWPR-SPAN

2.7.73  FE-IDLE

Clear the FE-IDLE Condition

2.7.74  FE-LOCKOUTOFPR-SPAN

2.7.75  FE-LOF

Clear the FE-LOF Condition

2.7.76  FE-LOS

Clear the FE-LOS Condition

2.7.77  FE-MANWKSWBK-SPAN

2.7.78  FE-MANWKSWPR-SPAN

2.7.79  FEPRLF

Clear the FEPRLF Alarm

2.7.80  FORCED-REQ

Clear the FORCED-REQ Condition

2.7.81  FORCED-REQ-SPAN

2.7.82  FRCDSWTOINT

2.7.83  FRCDSWTOPRI

2.7.84  FRCDSWTOSEC

2.7.85  FRCDSWTOTHIRD

2.7.86  FRNGSYNC

Clear the FRNGSYNC Alarm

2.7.87  FSTSYNC

2.7.88  GFP-CSF

Clear the GFP-CSF Alarm

2.7.89  GFP-LFD

2.7.90  HELLO

Clear the HELLO Alarm

2.7.91  HIBATVG

Clear the HIBATVG Alarm

2.7.92  HI-LASERBIAS

2.7.93  HI-LASERTEMP

2.7.94  HI-RXPOWER

2.7.95  HITEMP

Clear the HITEMP Alarm

2.7.96  HI-TXPOWER

2.7.97  HLDOVRSYNC

Clear the HLDOVRSYNC Alarm

2.7.98  I-HITEMP

Clear the I-HITEMP Alarm

2.7.99  IMPROPRMVL

Clear the IMPROPRMVL Alarm

2.7.100  INC-ISD

2.7.101  INTRUSION-PSWD

Clear the INTRUSION-PSWD Condition

2.7.102  INVMACADR

2.7.103  IOSCFGCOPY

2.7.104  KBYTE-APS-CHANNEL-FAILURE

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm

2.7.105  LCAS-CRC

Clear the LCAS-CRC Condition

2.7.106  LCAS-RX-FAIL

Clear the LCAS-RX-FAIL Condition

2.7.107  LCAS-TX-ADD

2.7.108  LCAS-TX-DNU

2.7.109  LKOUTPR-S

Clear the LKOUTPR-S Condition

2.7.110  LOA

2.7.111  LOCKOUT-REQ

Clear the LOCKOUT-REQ Condition

2.7.112  LOF (BITS)

Clear the LOF (BITS) Alarm

2.7.113  LOF (DS1)

Clear the LOF (DS1) Alarm

2.7.114  LOF (DS3)

Clear the LOF (DS3) Alarm

2.7.115  LOF (EC1)

Clear the LOF (EC1) Alarm

2.7.116  LOF (OCN)

Clear the LOF (OCN) Alarm

2.7.117  LOM

2.7.118  LOP-P

Clear the LOP-P Alarm

2.7.119  LOP-V

Clear the LOP-V Alarm

2.7.120  LO-RXPOWER

2.7.121  LOS (BITS)

Clear the LOS (BITS) Alarm

2.7.122  LOS (DS1)

Clear the LOS (DS1) Alarm

2.7.123  LOS (DS3)

Clear the LOS (DS3) Alarm

2.7.124  LOS (EC1)

Clear the LOS (EC1) Alarm

2.7.125  LOS (FUDC)

Clear the LOS (FUDC) Alarm

2.7.126  LOS (OCN)

Clear the LOS (OCN) Alarm

2.7.127  LO-TXPOWER

2.7.128  LPBKCRS

Clear the LPBKCRS Condition

2.7.129  LPBKDS1FEAC

2.7.130  LPBKDS1FEAC-CMD

2.7.131  LPBKDS3FEAC

Clear the LPBKDS3FEAC Condition

2.7.132  LPBKDS3FEAC-CMD

2.7.133  LPBKFACILITY (CE100T)

Clear the LPBKFACILITY (CE100T) Condition

2.7.134  LPBKFACILITY (DS1, DS3)

Clear the LPBKFACILITY (DS1, DS3) Condition

2.7.135  LPBKFACILITY (EC1)

Clear the LPBKFACILITY (EC1) Condition

2.7.136  LPBKFACILITY (OCN)

Clear the LPBKFACILITY (OCN) Condition

2.7.137  LPKTERMINAL (CE100T)

Clear the LPBKTERMINAL (CE100T) Condition

2.7.138  LPBKTERMINAL (DS1, DS3)

Clear the LPBKTERMINAL (DS1, DS3) Condition

2.7.139  LPBKTERMINAL (EC1)

Clear the LPBKTERMINAL (EC1) Condition

2.7.140  LPBKTERMINAL (OCN)

Clear the LPBKTERMINAL (OCN) Condition

2.7.141  LWBATVG

Clear the LWBATVG Alarm

2.7.142  MAN-REQ

Clear the MAN-REQ Condition

2.7.143  MANRESET

2.7.144  MANSWTOINT

2.7.145  MANSWTOPRI

2.7.146  MANSWTOSEC

2.7.147  MANSWTOTHIRD

2.7.148  MANUAL-REQ-SPAN

2.7.149  MEA (EQPT)

Clear the MEA (EQPT) Alarm

2.7.150  MEA (FAN)

2.7.151  MEA (PPM)

Clear the MEA (PPM) Alarm

2.7.152  MEM-GONE

2.7.153  MEM-LOW

2.7.154  MFGMEM

2.7.155  NO-CONFIG

Clear the NO-CONFIG Condition

2.7.156  NOT-AUTHENTICATED

2.7.157  OOU-TPT

Clear the OOT-TPT Condition

2.7.158  PDI-P

Clear the PDI-P Condition

2.7.159  PLM-P

Clear the PLM-P Alarm

2.7.160  PLM-V

Clear the PLM-V Alarm

2.7.161  PWR-FAIL-A

Clear the PWR-FAIL-A Alarm

2.7.162  PWR-FAIL-B

Clear the PWR-FAIL-B Alarm

2.7.163  RAI

Clear the RAI Condition

2.7.164  RFI-L

Clear the RFI-L Condition

2.7.165  RFI-P

Clear the RFI-P Condition

2.7.166  RFI-V

Clear the RFI-V Condition

2.7.167  RUN-CFG-SAVENEED

2.7.168  SD

Clear the SD (DS1, DS3) Condition

2.7.169  SD-L

Clear the SD-L Condition

2.7.170  SD-P

Clear the SD-P Condition

2.7.171  SD-V

Clear the SD-V Condition

2.7.172  SF

Clear the SF (DS1, DS3) Condition

2.7.173  SF-L

Clear the SF-L Condition

2.7.174  SF-P

Clear the SF-P Condition

2.7.175  SF-V

2.7.176  SFTWDOWN

2.7.177  SNTP-HOST

Clear the SNTP-HOST Alarm

2.7.178  SQM

Clear the SQM Alarm

2.7.179  SSM-DUS

2.7.180  SSM-FAIL

Clear the SSM-FAIL Alarm

2.7.181  SSM-OFF

Clear the SSM-OFF Condition

2.7.182  SSM-PRS

2.7.183  SSM-RES

2.7.184  SSM-SMC

2.7.185  SSM-ST2

2.7.186  SSM-ST3

2.7.187  SSM-ST3E

2.7.188  SSM-ST4

2.7.189  SSM-STU

Clear the SSM-STU Condition

2.7.190  SSM-TNC

2.7.191  SWTOPRI

2.7.192  SWTOSEC

Clear the SWTOSEC Condition

2.7.193  SWTOTHIRD

Clear the SWTOTHIRD Condition

2.7.194  SWMTXMOD

Clear the SWMTXMOD Alarm

2.7.195  SYNC-FREQ

Clear the SYNC-FREQ Condition

2.7.196  SYNCPRI

Clear the SYNCPRI Alarm

2.7.197  SYNCSEC

Clear the SYNCSEC Alarm

2.7.198  SYNCTHIRD

Clear the SYNCTHIRD Alarm

2.7.199  SYSBOOT

2.7.200  TIM-P

Clear the TIM-P Alarm

2.7.201  TIM-V

Clear the TIM-V Alarm

2.7.202  TPTFAIL (CE100T)

Clear the TPTFAIL (CE100T) Alarm

2.7.203  UNEQ-P

Clear the UNEQ-P Alarm

2.7.204  UNEQ-V

Clear the UNEQ-V Alarm

2.7.205  VCG-DEG

Clear the VCG-DEG Condition

2.7.206  VCG-DOWN

Clear the VCG-DOWN Condition

2.7.207  WKSWPR

Clear the WKSWPR Condition

2.7.208  WTR

2.8  15310-CL-CTX Line Alarms

2.9  ONS 15310-CL Traffic Card LED Activity

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

2.9.2  Typical 15310-CL-CTX 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 Loopbacks

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 ONS SONET TL1 Command 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/techsupport for more information or call the Cisco Technical Assistance Center (1-800-553-2447).

More information about alarm profile information modification and downloads are located 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.


2.1.1  Critical Alarms (CR)

Table 2-1 alphabetically lists ONS 15310-CL Critical alarms.


2.1.2  Major Alarms (MJ)

Table 2-2 alphabetically lists ONS 15310-CL Major alarms.


2.1.3  Minor Alarms (MN)

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


2.1.4  Not Alarmed (NA) Conditions

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

Table 2-4 ONS 15310-CL NA Conditions Index 

APS-PRIM-FAC

INC-ISD

RAI

AS-CMD

INTRUSION-PSWD

RUN-CFG-SAVENEED

AS-MT

IOSCFGCOPY

SD

AS-MT-OOG

LCAS-CRC

SD-L

AUD-LOG-LOSS

LCAS-RX-FAIL

SD-P

AUD-LOG-LOW

LCAS-TX-ADD

SD-V

AUTOSW-LOP (STSMON)

LCAS-TX-DNU

SF

AUTOSW-PDI

LKOUTPR-S

SF-L

AUTOSW-SDBER

LOCKOUT-REQ

SF-P

AUTOSW-SFBER

LPBKCRS

SF-V

AUTOSW-UNEQ (STSMON)

LPBKDS3FEAC

SSM-DUS

CLDRESTART

LPBKDS3FEAC-CMD

SSM-OFF

DS3-MISM

LPBKFACILITY (CE100T)

SSM-PRS

ETH-LINKLOSS

LPBKFACILITY (DS1, DS3)

SSM-RES

FAILTOSW

LPBKFACILITY (EC1)

SSM-SMC

FAILTOSW-PATH

LPBKFACILITY (OCN)

SSM-ST2

FE-AIS

LPKTERMINAL (CE100T)

SSM-ST3

FE-EQPT-NSA

LPBKTERMINAL (DS1, DS3)

SSM-ST3E

FE-DS3-SA

LPBKTERMINAL (EC1)

SSM-ST4

FE-EQPT-NSA

LPBKTERMINAL (OCN)

SSM-STU

FE-IDLE

MAN-REQ

SSM-TNC

FE-LOF

MANRESET

SWTOPRI

FE-LOS

MANSWTOINT

SWTOSEC

FORCED-REQ

MANSWTOPRI

SWTOTHIRD

FRCDSWTOINT

MANSWTOSEC

SYNC-FREQ

FRCDSWTOPRI

MANSWTOTHIRD

VCG-DEG

FRCDSWTOSEC

NO-CONFIG

VCG-DOWN

FRCDSWTOTHIRD

OOU-TPT

WKSWPR

FRNGSYNC

PDI-P

WTR


2.1.5  Not Reported (NR) Conditions

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

Table 2-5 ONS 15310-CL NR Conditions Index 

AIS

AUTOSW-AIS

RFI-L

AIS-L

ERFI-P-CONN

RFI-P

AIS-P

ERFI-P-PAYLD

RFI-V

AIS-V

ERFI-P-SRVR

 

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 Index 

AIS

FE-FRCDWKSWBK-SPAN

LPBKTERMINAL (OCN)

AIS-L

FE-FRCDWKSWPR-SPAN

LWBATVG

AIS-P

FE-IDLE

MAN-REQ

AIS-V

FE-LOCKOUTOFPR-SPAN

MANRESET

ALS

FE-LOF

MANSWTOINT

APSB

FE-LOS

MANSWTOPRI

APSCDFLTK

FE-MANWKSWBK-SPAN

MANSWTOSEC

APSC-IMP

FE-MANWKSWPR-SPAN

MANSWTOTHIRD

APSCINCON

FEPRLF

MANUAL-REQ-SPAN

APSCM

FORCED-REQ

MEA (EQPT)

APSIMP

FORCED-REQ-SPAN

MEA (FAN)

APS-INV-PRIM

FRCDSWTOINT

MEA (PPM)

APSMM

FRCDSWTOPRI

MEM-GONE

APS-PRIM-FAC

FRCDSWTOSEC

MEM-LOW

APS-PRIM-SEC-MISM

FRCDSWTOTHIRD

MFGMEM

AS-CMD

FRNGSYNC

NO-CONFIG

AS-MT

FSTSYNC

NOT-AUTHENTICATED

AS-MT-OOG

GFP-CSF

OOU-TPT

AUD-LOG-LOSS

GFP-LFD

PDI-P

AUD-LOG-LOW

HELLO

PLM-P

AU-LOF

HIBATVG

PLM-V

AUTOLSROFF

HI-LASERBIAS

PWR-FAIL-A

AUTORESET

HI-LASERTEMP

PWR-FAIL-B

AUTOSW-AIS

HI-RXPOWER

RAI

AUTOSW-LOP (STSMON)

HITEMP

RFI-L

AUTOSW-LOP (VT-MON)

HI-TXPOWER

RFI-P

AUTOSW-PDI

HLDOVRSYNC

RFI-V

AUTOSW-SDBER

I-HITEMP

RUN-CFG-SAVENEED

AUTOSW-SFBER

IMPROPRMVL

SD

AUTOSW-UNEQ (STSMON)

INC-ISD

SD-L

AUTOSW-UNEQ (VT-MON)

INTRUSION-PSWD

SD-P

BAT-FAIL

INVMACADR

SD-V

BKUPMEMP

IOSCFGCOPY

SF

CARLOSS (CE100T)

KBYTE-APS-CHANNEL-FAILURE

SF-L

CARLOSS (EQPT)

LCAS-CRC

SF-P

CLDRESTART

LCAS-RX-FAIL

SF-V

COMIOXC

LCAS-TX-ADD

SFTWDOWN

CONTBUS-IO-A

LCAS-TX-DNU

SNTP-HOST

CTNEQPT-PBWORK

LKOUTPR-S

SQM

DATAFLT

LOA

SSM-DUS

DS3-MISM

LOCKOUT-REQ

SSM-FAIL

DUP-IPADDR

LOF (BITS)

SSM-OFF

DUP-NODENAME

LOF (DS1)

SSM-PRS

EHIBATVG

LOF (DS3)

SSM-RES

ELWBATVG

LOF (EC1)

SSM-SMC

ENCAP-MISMATCH-P

LOF (OCN)

SSM-ST2

EOC

LOM

SSM-ST3

EOC-L

LOP-P

SSM-ST3E

EQPT

LOP-V

SSM-ST4

EQPT-MISS

LO-RXPOWER

SSM-STU

ERFI-P-CONN

LOS (BITS)

SSM-TNC

ERFI-P-PAYLD

LOS (DS1)

SWTOPRI

ERFI-P-SRVR

LOS (DS3)

SWTOSEC

ERROR-CONFIG

LOS (EC1)

SWTOTHIRD

ETH-LINKLOSS

LOS (FUDC)

SWMTXMOD

EXCCOL

LOS (OCN)

SYNC-FREQ

EXT

LO-TXPOWER

SYNCPRI

EXTRA-TRAF-PREEMPT

LPBKCRS

SYNCSEC

FAILTOSW

LPBKDS1FEAC

SYNCTHIRD

FAILTOSW-PATH

LPBKDS1FEAC-CMD

SYSBOOT

FAN

LPBKDS3FEAC

TIM-P

FAN-DEGRADE

LPBKDS3FEAC-CMD

TIM-V

FE-AIS

LPBKFACILITY (CE100T)

TPTFAIL (CE100T)

FE-DS1-MULTLOS

LPBKFACILITY (DS1, DS3)

UNEQ-P

FE-DS1-NSA

LPBKFACILITY (EC1)

UNEQ-V

FE-DS1-SA

LPBKFACILITY (OCN)

VCG-DEG

FE-DS1-SNGLLOS

LPKTERMINAL (CE100T)

VCG-DOWN

FE-DS3-NSA

LPBKTERMINAL (DS1, DS3)

WKSWPR

FE-DS3-SA

LPBKTERMINAL (EC1)

WTR

FE-EQPT-NSA

   

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 might appear in multiple entries when 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 Definition 

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 non-common 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 Index by Logical Object Type

Table 2-8 lists all ONS 15310-CL Release 5.0 alarms and logical objects as they are given in the system alarm profile. The list entries are organized logical object name and then by alarm or condition name. Each entry contains a page number that refers to an alarm description in this chapter. 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 Logical Object Type Alarm Index 

BITS: AIS

EQPT: PWR-FAIL-A

OCN: SSM-FAIL

BITS: LOF (BITS)

EQPT: PWR-FAIL-B

OCN: SSM-OFF

BITS: LOS (BITS)

EQPT: RUN-CFG-SAVENEED

OCN: SSM-RES

BITS: SSM-DUS

EQPT: SFTWDOWN

OCN: SSM-SMC

BITS: SSM-FAIL

EQPT: SWMTXMOD

OCN: SSM-ST2

BITS: SSM-OFF

EXT-SREF: FRCDSWTOPRI

OCN: SSM-ST3

BITS: SSM-PRS

EXT-SREF: FRCDSWTOSEC

OCN: SSM-ST3E

BITS: SSM-RES

EXT-SREF: FRCDSWTOTHIRD

OCN: SSM-ST4

BITS: SSM-SMC

EXT-SREF: FRNGSYNC

OCN: SSM-STU

BITS: SSM-ST2

EXT-SREF: FSTSYNC

OCN: SSM-TNC

BITS: SSM-ST3

EXT-SREF: HLDOVRSYNC

OCN: SYNC-FREQ

BITS: SSM-ST3E

EXT-SREF: MANSWTOINT

OCN: WKSWPR

BITS: SSM-ST4

EXT-SREF: MANSWTOPRI

OCN: WTR

BITS: SSM-STU

EXT-SREF: MANSWTOSEC

PPM: AS-CMD

BITS: SSM-TNC

EXT-SREF: MANSWTOTHIRD

PPM: AS-MT

BITS: SYNC-FREQ

EXT-SREF: SWTOPRI

PPM: EQPT

BPLANE: AS-CMD

EXT-SREF: SWTOSEC

PPM: HI-LASERBIAS

BPLANE: INVMACADR

EXT-SREF: SWTOTHIRD

PPM: HI-LASERTEMP

BPLANE: MFGMEM

EXT-SREF: SYNCPRI

PPM: HI-TXPOWER

CE100T: AS-CMD

EXT-SREF: SYNCSEC

PPM: IMPROPRMVL

CE100T: AS-MT

EXT-SREF: SYNCTHIRD

PPM: LO-TXPOWER

CE100T: CARLOSS (CE100T)

FAN: EQPT-MISS

PPM: MEA (PPM)

CE100T: GFP-CSF

FAN: FAN

PPM: MFGMEM

CE100T: GFP-LFD

FAN: FAN-DEGRADE

PWR: AS-CMD

CE100T: LPBKFACILITY (CE100T)

FAN: MEA (FAN)

PWR: BAT-FAIL

CE100T: LPKTERMINAL (CE100T)

FAN: MFGMEM

PWR: EHIBATVG

CE100T: TPTFAIL (CE100T)

FUDC: AIS

PWR: ELWBATVG

DS1: AIS

FUDC: LOS (FUDC)

PWR: HIBATVG

DS1: AS-CMD

NE-SREF: FRCDSWTOINT

PWR: LWBATVG

DS1: AS-MT

NE-SREF: FRCDSWTOPRI

STSMON: AIS-P

DS1: LOF (DS1)

NE-SREF: FRCDSWTOSEC

STSMON: AUTOSW-AIS

DS1: LOS (DS1)

NE-SREF: FRCDSWTOTHIRD

STSMON: AUTOSW-LOP (STSMON)

DS1: LPBKDS1FEAC

NE-SREF: FRNGSYNC

STSMON: AUTOSW-PDI

DS1: LPBKDS1FEAC-CMD

NE-SREF: FSTSYNC

STSMON: AUTOSW-SDBER

DS1: LPBKFACILITY (DS1, DS3)

NE-SREF: HLDOVRSYNC

STSMON: AUTOSW-SFBER

DS1: LPBKTERMINAL (DS1, DS3)

NE-SREF: MANSWTOINT

STSMON: AUTOSW-UNEQ (STSMON)

DS1: RAI

NE-SREF: MANSWTOPRI

STSMON: ERFI-P-CONN

DS1: SD

NE-SREF: MANSWTOSEC

STSMON: ERFI-P-PAYLD

DS1: SF

NE-SREF: MANSWTOTHIRD

STSMON: ERFI-P-SRVR

DS1: SSM-DUS

NE-SREF: SSM-PRS

STSMON: FAILTOSW-PATH

DS1: SSM-FAIL

NE-SREF: SSM-RES

STSMON: FORCED-REQ

DS1: SSM-OFF

NE-SREF: SSM-SMC

STSMON: LOCKOUT-REQ

DS1: SSM-PRS

NE-SREF: SSM-ST2

STSMON: LOP-P

DS1: SSM-RES

NE-SREF: SSM-ST3

STSMON: LPBKCRS

DS1: SSM-SMC

NE-SREF: SSM-ST3E

STSMON: MAN-REQ

DS1: SSM-ST2

NE-SREF: SSM-ST4

STSMON: PDI-P

DS1: SSM-ST3

NE-SREF: SSM-STU

STSMON: PLM-P

DS1: SSM-ST3E

NE-SREF: SSM-TNC

STSMON: RFI-P

DS1: SSM-ST4

NE-SREF: SWTOPRI

STSMON: SD-P

DS1: SSM-STU

NE-SREF: SWTOSEC

STSMON: SF-P

DS1: SSM-TNC

NE-SREF: SWTOTHIRD

STSMON: TIM-P

DS1: SYNC-FREQ

NE-SREF: SYNCPRI

STSMON: UNEQ-P

DS3: AIS

NE-SREF: SYNCSEC

STSMON: WKSWPR

DS3: AS-CMD

NE-SREF: SYNCTHIRD

STSMON: WTR

DS3: AS-MT

NE: AS-CMD

STSTRM: AIS-P

DS3: DS3-MISM

NE: AUD-LOG-LOSS

STSTRM: AS-MT-OOG

DS3: FE-AIS

NE: AUD-LOG-LOW

STSTRM: AU-LOF

DS3: FE-DS1-MULTLOS

NE: DATAFLT

STSTRM: ENCAP-MISMATCH-P

DS3: FE-DS1-NSA

NE: DUP-IPADDR

STSTRM: ERFI-P-CONN

DS3: FE-DS1-SA

NE: DUP-NODENAME

STSTRM: ERFI-P-PAYLD

DS3: FE-DS1-SNGLLOS

NE: ETH-LINKLOSS

STSTRM: ERFI-P-SRVR

DS3: FE-DS3-NSA

NE: HITEMP

STSTRM: LCAS-CRC

DS3: FE-DS3-SA

NE: I-HITEMP

STSTRM: LCAS-RX-FAIL

DS3: FE-DS3-NSA

NE: INTRUSION-PSWD

STSTRM: LCAS-TX-ADD

DS3: FE-EQPT-NSA

NE: SNTP-HOST

STSTRM: LCAS-TX-DNU

DS3: FE-IDLE

NE: SYSBOOT

STSTRM: LOM

DS3: FE-LOF

OCN: AIS-L

STSTRM: LOP-P

DS3: FE-LOS

OCN: ALS

STSTRM: OOU-TPT

DS3: INC-ISD

OCN: APS-INV-PRIM

STSTRM: PDI-P

DS3: LOF (DS3)

OCN: APS-PRIM-FAC

STSTRM: PLM-P

DS3: LOS (DS3)

OCN: APS-PRIM-SEC-MISM

STSTRM: RFI-P

DS3: LPBKDS1FEAC

OCN: APSB

STSTRM: SD-P

DS3: LPBKDS3FEAC

OCN: APSC-IMP

STSTRM: SF-P

DS3: LPBKDS3FEAC-CMD

OCN: APSCDFLTK

STSTRM: SQM

DS3: LPBKFACILITY (DS1, DS3)

OCN: APSCINCON

STSTRM: TIM-P

DS3: LPBKTERMINAL (DS1, DS3)

OCN: APSCM

STSTRM: UNEQ-P

DS3: RAI

OCN: APSIMP

VCG: LOA

DS3: SD

OCN: APSMM

VCG: VCG-DEG

DS3: SF

OCN: AS-CMD

VCG: VCG-DOWN

EC1: AIS-L

OCN: AS-MT

VT-MON: AIS-V

EC1: AS-CMD

OCN: AUTOLSROFF

VT-MON: AUTOSW-AIS

EC1: AS-MT

OCN: EOC

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

EC1: LOF (EC1)

OCN: EOC-L

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

EC1: LOS (EC1)

OCN: EXTRA-TRAF-PREEMPT

VT-MON: FAILTOSW-PATH

EC1: LPBKFACILITY (EC1)

OCN: FAILTOSW

VT-MON: FORCED-REQ

EC1: LPBKTERMINAL (EC1)

OCN: FE-FRCDWKSWBK-SPAN

VT-MON: LOCKOUT-REQ

EC1: RFI-L

OCN: FE-FRCDWKSWPR-SPAN

VT-MON: LOP-V

EC1: SD-L

OCN: FE-LOCKOUTOFPR-SPAN

VT-MON: MAN-REQ

EC1: SF-L

OCN: FE-MANWKSWBK-SPAN

VT-MON: SD-V

ENVALRM: EXT

OCN: FE-MANWKSWPR-SPAN

VT-MON: SF-V

EQPT: AS-CMD

OCN: FEPRLF

VT-MON: UNEQ-V

EQPT: AS-MT

OCN: FORCED-REQ-SPAN

VT-MON: WKSWPR

EQPT: AUTORESET

OCN: HELLO

VT-MON: WTR

EQPT: BKUPMEMP

OCN: HI-LASERBIAS

VT-TERM: AIS-V

EQPT: CARLOSS (EQPT)

OCN: HI-RXPOWER

VT-TERM: AS-MT-OOG

EQPT: CLDRESTART

OCN: HI-TXPOWER

VT-TERM: LCAS-CRC

EQPT: COMIOXC

OCN: KBYTE-APS-CHANNEL-FAILURE

VT-TERM: LCAS-RX-FAIL

EQPT: CONTBUS-IO-A

OCN: LKOUTPR-S

VT-TERM: LCAS-TX-ADD

EQPT: CTNEQPT-PBWORK

OCN: LO-RXPOWER

VT-TERM: LCAS-TX-DNU

EQPT: EQPT

OCN: LO-TXPOWER

VT-TERM: LOM

EQPT: ERROR-CONFIG

OCN: LOCKOUT-REQ

VT-TERM: LOP-V

EQPT: EXCCOL

OCN: LOF (OCN)

VT-TERM: OOU-TPT

EQPT: HITEMP

OCN: LOS (OCN)

VT-TERM: PLM-V

EQPT: IMPROPRMVL

OCN: LPBKFACILITY (OCN)

VT-TERM: RFI-V

EQPT: IOSCFGCOPY

OCN: LPBKTERMINAL (OCN)

VT-TERM: SD-P

EQPT: MANRESET

OCN: MANUAL-REQ-SPAN

VT-TERM: SF-P

EQPT: MEA (EQPT)

OCN: RFI-L

VT-TERM: SQM

EQPT: MEM-GONE

OCN: SD-L

VT-TERM: TIM-V

EQPT: MEM-LOW

OCN: SF-L

VT-TERM: UNEQ-V

EQPT: NO-CONFIG

OCN: SSM-DUS

 

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, 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 ONS 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 alarm generally indicates severe, service-affecting 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, but loss of traffic on one to five DS-1 circuits is Major (MJ).

Minor (MN) alarms generally are those that do not affect service. For example, the APS byte failure (APSB) alarm indicates that line terminating equipment 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 might or might 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.

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.

Severities can also 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. Procedures for customizing alarm severities are located in the Cisco ONS 15310-CL Procedure Guide.

2.5.4  Service Effect

Service-Affecting (SA) alarms—those that interrupt service—might be Critical (CR), Major (MJ), or Minor (MN) severity alarms. In some cases the severity of an alarm might not correspond to its service effect. For example, the AUTOSW-LOP alarm for the VTMON object is Minor but service-affecting because it indicates a traffic switch has occurred directing traffic away from a loss of circuit path. Non-Service Affecting (NSA) alarms always have a Minor (MN) default severity.

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


Note Transient events are not defined in this documentation release.


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


Caution Hazardous voltage or energy could be present when the system is operating. Use caution when removing or installing cards.


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



Warning Use of controls, adjustments, or performing procedures other than those specified may 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 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 AIS 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-73, or 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/techsupport for 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.

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 AIS-L Condition


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

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


2.7.3  AIS-P

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

Logical Objects: STSMON, STS-TRM

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.

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 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-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/techsupport for 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.

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

See the "AIS-V on Unused 15310-CL-CTX VT Circuits" section for more information.

Clear the AIS-V Condition


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

Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call 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  APSB

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

Logical Object: OCN

The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure or an invalid switching code in the incoming APS signal. Some older non-Cisco SONET nodes send invalid APS codes if they are configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15310-CL. These invalid codes cause an APSB 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.7  APSCDFLTK

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

2.7.8  APSC-IMP

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

2.7.9  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. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.

Clear the APSCINCON Alarm


Step 1 Look for other alarms, especially the "LOS (OCN)" alarm on page 2-73, the "LOF (OCN)" alarm on page 2-67, or the "AIS" alarm on page 2-13. Clearing these alarms clears the APSCINCON alarm.

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


2.7.10  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-3 ports in a 1+1 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 may result in hazardous radiation exposure. Statement 1057



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

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.

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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.11  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 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 APS, APSCM, or APSMM. It is not superseded by AIS or remote defect indication (RDI) line alarms. 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 instructions, refer to 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.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.12  APS-INV-PRIM

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

Logical Object: OCN

The Optimized 1+1 APS Primary Facility alarm occurs on OC-N cards in an optimized 1+1 protection system if the incoming primary section header does not indicate whether it is primary or secondary.


Note APS-INV-PRIM is an informational alarm and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.


2.7.13  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 and unidirectional at each end. 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 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:

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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.14  APS-PRIM-FAC

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

Logical Object: OCN

The Optimized 1+1 APS Invalid Primary Section condition occurs on OC-N cards in an optimized 1+1 protection system if there is an APS status switch between the primary and secondary facilities to identify which port is primary.

Clear the APS-PRIM-FAC Condition


Step 1 APS-PRIM-FAC is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter. This condition clears when the card receives a valid primary section indication (1 or 2).

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


2.7.15  APS-PRIM-SEC-MISM

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

Logical Object: OCN

The Optimized 1+1 APS Primary Section Mismatch alarm occurs on OC-N ports in an optimized 1+1 protection system if there is a mismatch between the primary section of the near end facility and the primary section of the far-end facility.

Clear the APS-PRIM-SEC-MISM Alarm


Step 1 Ensure that the near end and far-end ports are correctly provisioned with the same way. For more information about optimized 1+1 configurations, refer to the "SONET Topologies and Upgrades"
chapter in the Cisco ONS 15310-CL Reference Manual.

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


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

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:

a. Double-click the 15310-CL-CTX, CE-100T-8, or ML100-T card to display the card view.

b. Click the Provisioning > Alarm Profiles > Alarm Behavior tabs.

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:

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/techsupport for more information or call TAC (1-800-553-2447).


2.7.17  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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.18  AS-MT-OOG

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

Logical Objects: STSTRM, VT-TRM

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

Clear the AS-MT-OOG Condition


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

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


2.7.19  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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.20  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.21  AU-LOF

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

2.7.22  AUTOLSROFF

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

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


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


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


2.7.24  AUTOSW-AIS

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

Logical Objects: STSMON, VTMON

The Automatic path protection Switch Caused by AIS condition indicates that automatic path protection protection switching occurred because of an AIS condition. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.25  AUTOSW-LOP (STSMON)

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

Logical Object: STSMON

The Automatic path protection Switch Caused by Loss of Pointer (LOP) condition for the STS monitor (STSMON) condition indicates that automatic path protection protection switching occurred because of the "LOP-P" alarm on page 2-68. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.26  AUTOSW-LOP (VT-MON)

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

Logical Object: VT-MON

The AUTOSW-LOP alarm for the virtual tributary monitor (VT-MON) indicates that automatic path protection protection switching occurred because of the "LOP-V" alarm on page 2-68. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.27  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 protection switching occurred because of a "PDI-P" alarm on page 2-87. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.28  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 caused automatic path protection protection switching to occur (see the "SD-L" condition on page 2-95). The path protection is configured for revertive switching and reverts to the working path when the SD is resolved.

Clear the AUTOSW-SDBER 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.29  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-L" condition on page 2-97 caused automatic path protection protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SF is resolved.

Clear the AUTOSW-SFBER Condition


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

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


2.7.30  AUTOSW-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 protection switching to occur. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.31  AUTOSW-UNEQ (VT-MON)

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

Logical Object: VT-MON

AUTOSW-UNEQ (VT-MON) indicates that the "UNEQ-V" alarm on page 2-111 alarm caused automatic path protection protection switching to occur. The path protection is configured for revertive switching and 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.32  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 on-site 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 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.

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


2.7.33  BKUPMEMP

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

Logical Object: EQPT

The Primary Non-Volatile 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:

The flash manager fails to format a flash partition.

The flash manager fails to write a file to a flash partition.

There is a problem at the driver level.

The code volume fails cyclic redundancy checking (CRC). CRC is 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-40. 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.34  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 Cisco ONS 15310-CL Procedure Guide.


Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15310-CL. Plug the wristband cable into the ESD jack located on the between the top high-speed and Integrated Cross-Connect, Timing, and Control (XTC) slots of the shelf assembly.

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

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 Cisco ONS 15310-CL Reference Manual.

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

Step 7 If the alarm does not clear and link autonegotiation is enabled on the CE100T-8 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:

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-109 is also reported, complete the "Clear the TPTFAIL (CE100T) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.


Note When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition 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 reported, determine whether a terminal (inward) loopback has been provisioned on the port:

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 EC-1 Port Loopbacks" 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.

If the 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:


Note An ONS 15310-CL Ethernet manual cross-connect is used when another vendors' 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 host the Ethernet circuit at the other end of the Ethernet manual cross-connect.

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 Cisco ONS 15310-CL Procedure Guide for detailed procedures to create circuits.

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 an 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.35  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 may result in hazardous radiation exposure. Statement 1057


Clear the CARLOSS (EQPT) Alarm


Step 1 If the reporting entity is a pluggable port module (PPM) port, confirm that the PPM is correctly configured:

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:

a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Accessories > Command Prompt.

b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.

c. For both the Sun and Microsoft operating systems, at the prompt type:

ping ONS-15310-IP-address

For example:

ping 198.168.10.10

If the workstation has connectivity to the ONS 15310-CL, it shows a "reply from IP-Address" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.

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

a. Exit from CTC.

b. Reopen the browser.

c. Log into CTC.

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


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

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

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.36  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 an identical type of card, you do not need to make any changes to the database.


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


2.7.37  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. It occurs 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 reporting 15310-CL-CTX cross-connect 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.38  CONTBUS-IO-A

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

Logical Object: EQPT

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

In the event of a 15310-CL-CTX port protection switch, the alarm clears after the other ports establish communication with the 15310-CL-CTX. If the alarm persists, the problem is with the physical path of communication from the 15310-CL-CTX card to the reporting card or port.

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-82 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 or Ethernet Card LED Activity During Reset" section.

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

If CONTBUS-IO-A is raised on several cards at once, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

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 reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447).


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


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


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


2.7.40  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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.41  DS3-MISM

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

Logical Object: DS3

The DS-3 Frame Format Mismatch condition indicates 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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.42  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, TC no longer reliably connects to either node. Depending on how the packets are routed, CTC may 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).

For the ONS 15310, if two nodes are given the same IP address, the addresses may continue in use even after you change one of them. The procedure given below will clear the alarm in most cases. If it does not, contact Cisco TAC at the number given in the last step.

Clear the DUP-IPADDR Alarm


Step 1 Isolate the alarmed node from the other node having the same address:

a. Connect to the alarmed node using the Craft port on the front of the ONS 15310-CL chassis.

b. Begin a CTC session.

c. On 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. The node will reboot following this change.

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


2.7.43  DUP-NODENAME

Default Severity: Major (MJ), 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 field, enter a unique name for the node.

Step 3 Click Apply.

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


2.7.44  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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.45  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 default value of -40.5 VDC. 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.46  ENCAP-MISMATCH-P

Default Severity: Major (MJ), Service-Affecting

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 PLM-P, which must meet all five criteria.) For an ENCAP-MISMATCH-P 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.

An example of a situation that would raise ENCAP-MISMATCH-P is 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 a 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 Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL.


Clear the ENCAP-MISMATCH-P Alarm


Step 1 Ensure that the correct line type is in use on the receive card:

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:

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 Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.47   EOC

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

Logical Objects: OCN

The SONET Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15310-CL loses its data communications channel. This alarm is primarily SONET but can apply to DWDM in other platforms.

The SDCCs consist 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 may 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-73 is also reported, complete the "Clear the LOS (OCN) Alarm" procedure.

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

Step 3 If the alarm does not clear on the reporting node, verify that the physical connections between the ports and 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 of 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 verify that the DCC is provisioned for the ports at both ends of the fiber span.

Step 5 Repeat Step 4 at the adjacent nodes.

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

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. See the Cisco ONS 15310-CL Reference Manual 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 reset does not clear the alarm, delete the problematic SDCC termination:

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

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

b. Highlight the problematic DCC termination.

c. Click Delete.

d. Click Yes in the Confirmation Dialog box.

Step 12 Recreate the SDCC termination. Refer to the Cisco ONS 15310-CL Procedure Guide for instructions.

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.48  EOC-L

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

Logical Objects: OCN

The Line DCC (LDCC) Termination Failure alarm occurs when the ONS 15310-CL loses its line data communications channel. The LDCCs are nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS 15310-CL uses the LDCCs on the SONET line layer to communicate network management information.


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



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



Note If a circuit shows an incomplete state when the EOC 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.49  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-27. The BKUPMEMP procedure also clears the EQPT alarm.

Clear the EQPT Alarm


Step 1 If traffic is active on the alarmed port, you might 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.

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

Step 4 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 5 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 an identical type of card, you do not need to make any changes to the database.


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


2.7.50  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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.

2.7.51  ERFI-P-CONN

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

Logical Objects: STSMON, STSTRM

The Three-Bit (Enhanced) Remote Failure Indication Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the "UNEQ-P" alarm on page 2-109 and the "TIM-P" alarm on page 2-107 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.52  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-88 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.53  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-14 or the "LOP-P" alarm on page 2-68 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.54  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 Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL.


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 Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL.

Step 2 Upload the configuration file to the 15310-CL-CTX:

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:

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 Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

Clear the ETH-LINKLOSS Condition


Step 1 To clear this alarm, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.56  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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.57  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 might have occurred.

Clear the EXT Alarm


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

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


2.7.58  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.59  FAILTOSW

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

Logical Object: OCN

The Failure to Switch to Protection condition occurs when a working electrical port cannot switch to the protect port in a protection group because another working port with a higher-priority alarm has switched to the protect port.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.60  FAILTOSW-PATH

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

Logical Objects: STSMON, VT-MON

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

The "LOF (OCN)" alarm on page 2-67, the "LOS (OCN)" alarm on page 2-73, the "SD-L" condition on page 2-95, or the "SF-L" condition on page 2-97 can also occur on the failed path.

Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration


Step 1 Look up and clear the higher priority alarm. If the "AIS-P" condition on page 2-14, the "LOP-P" alarm on page 2-68, the "UNEQ-P" alarm on page 2-109, the "SF-P" condition on page 2-98, the "SD-P" condition on page 2-95, the "LOF (OCN)" alarm on page 2-67, the "LOS (OCN)" alarm on page 2-73, the "SD-L" condition on page 2-95, or the "SF-L" condition on page 2-97 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.61  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/techsupport for more information or call Cisco TAC to report a service-affecting problem (1-800-553-2447).

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

2.7.63  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-73).

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 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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.64  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.65  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.66  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.67  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.68  FE-DS3-NSA

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

Logical Object: DS3

The Far End DS-3 Equipment Failure Non-Service Affecting condition occurs when a far-end 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.70  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 equipment failure is detected on far-end DS-3 equipment.

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

Clear the FE-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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.71  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.72  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.73  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.

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.74  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.75  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-66 in C-bit line type mode.

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.77  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.78  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.79  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" condition on page 2-96 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 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. For example, an FE condition on a card in Node 1 could relate to a main 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 in this chapter for instructions.

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


2.7.80  FORCED-REQ

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

Logical Object: 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 vice versa). 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.81  FORCED-REQ-SPAN

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

2.7.82  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.83  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.84  FRCDSWTOSEC

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

Logical Objects: EXT-SREF, NE-SREF

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


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


2.7.85  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 the third timing source.


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


2.7.86  FRNGSYNC

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

Logical Object: NE-SREF

The Free Running Synchronization Mode alarm 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 Alarm


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 Cisco ONS 15310-CL Reference Manual for more information about timing.

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

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


2.7.87  FSTSYNC

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

Logical Object: NE-SREF

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

The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).


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


2.7.88  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 alarm causes invalid data transmission. The alarm is raised locally on ML-100T-8 Ethernet ports and does not indicate that a service-affecting failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm is affecting a remote data port's transmission capability.

Clear the GFP-CSF Alarm


Step 1 Clear the service-affecting alarm at the remote data port.

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


2.7.89  GFP-LFD

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

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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.91  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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.92  HI-LASERBIAS

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

2.7.93  HI-LASERTEMP

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

2.7.94  HI-RXPOWER

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

2.7.95  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/techsupport for more information or call Cisco TAC to report a service-affecting problem (1-800-553-2447) if it applies to the NE, or a non-service-affecting problem if it applies to equipment.


2.7.96  HI-TXPOWER

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

2.7.97  HLDOVRSYNC

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

Logical Object: NE-SREF

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

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 might 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 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.98  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/techsupport for more information or call TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.99  IMPROPRMVL

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

Logical Objects: EQPT, PPM

The Improper Removal alarm occurs when a card or PPM is physically removed before it is deleted from CTC. The card or port does not need to be in service to cause the IMPROPRMVL alarm; it only needs to be recognized by CTC. The alarm does not appear if you delete the card or PPM from CTC before you physically remove it from the node. It can also occur if the card or PPM is inserted but is not fully plugged in.


Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot. When you delete the card, CTC loses connection with the node view and goes to network view.


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


Clear the IMPROPRMVL 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, has a circuit mapped to it, is paired in a working protection scheme, has DCC enabled, or is used as a timing reference.


Step 3 If any ports on the card are in service, put them out of service (OOS,MT):


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:

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:

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:

a. Click the Provisioning > Timing 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 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.

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


2.7.100  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.101  INTRUSION-PSWD

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

Logical Object: NE

The Security Intrusion Incorrect Password condition occurs after a user attempts a settable (by Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not 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 the Clear security intrusion alarm button.

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


2.7.102  INVMACADR

Major (MJ), Service Affecting (SA)

Object: BPLANE

The Equipment Failure Invalid Media Access Control Layer (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. Contact TAC (1-800-553-2447).

2.7.103  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-98 but it applies to ML-100T-8 Ethernet cards rather than to the 15310-CL-CTX.)

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


Note IOSCFGCOPY is an informational condition.



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


2.7.104  KBYTE-APS-CHANNEL-FAILURE

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

Logical Object: OCN

The APS Channel Failure alarm is raised when there a span provisioned for different APS channels on each side. For instance, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.

This alarm is also raised during checksum failure occurs if the K1 and K2 bytes are overwritten by test equipment. It is not raised in bidirectional full pass-through or K Byte pass-through states. The alarm is overridden by AIS-P, LOF, LOS, or SF-BER alarms.

Clear the KBYTE-APS-CHANNEL-FAILURE Alarm


Step 1 The error could be due to checksum failures within the 15310-CL-CTX card. To allow CTC to clear the issue, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

Step 2 If the alarm does not clear and if third-party equipment is involved, ensure that it is configured for the same APS channel as the Cisco ONS equipment.

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


2.7.105  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. 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. 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 the ML-100T-8 Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL.


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 alarms such as SDBER or SFBER 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:

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

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


2.7.106  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 with LCAS-enabled VCG or software-enabled LCAS (SW-LCAS) VCG.


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


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 the ML-100T-8 Ethernet cards, refer to the Ethernet Card Software Feature and Configuration Guide for the ONS 15310-CL.


Clear the LCAS-RX-FAIL Condition


Step 1 Check for and clear any line or path alarms.

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


2.7.107  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 cards when the transmit side of an LCAS VCG member is in the add state. The condition clears after provisioning is completed.


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



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


2.7.108  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 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 node reporting this condition likely also reports an RDI-P alarm and 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.109  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.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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


2.7.111  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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.112  LOF (BITS)

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

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.


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


Clear the LOF (BITS) Alarm


Step 1 Verify that the line type and line coding match between the BITS port and the 15310-CL-CTX card:

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 tabs to display the General timing window.

d. Verify that Coding matches the coding of the BITS timing source, either B8ZS or AMI.

e. If the coding does not match, click Coding 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


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

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 might need to contact your network administrator for the format information.

c. Display the card view of the reporting ONS 15310-CL 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.114  LOF (DS3)

Default Severity: Major (MJ), 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:

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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


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


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


Note To verify cable continuity, follow site practices.


Step 2 If cabling continuity is OK, clean the fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 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 problem (1-800-553-2447).


2.7.116  LOF (OCN)

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

Logical Object: OCN

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 milliseconds. 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 problem (1-800-553-2447).


2.7.117  LOM

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

2.7.118  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 you have not been using a test set, or if the test set is correctly set up, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.

Step 5 Recreate the circuit for the correct size. For instructions, 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


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


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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.120  LO-RXPOWER

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

2.7.121  LOS (BITS)

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

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 the BITS clock 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.122  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 is not correctly connected to the port, or no signal exists on the line.

Clear the LOS (DS1) Alarm


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

a. To confirm this physically, confirm that the green ACT LED is on.

b. To determine this virtually, double-click the card in CTC to display the card view:

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

Step 7 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the "Install Hardware" chapter of the Cisco ONS 15310-CL Procedure 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.123  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 is not 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 fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 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 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:

a. To confirm this physically, confirm that the green ACT LED is on.

b. To determine this virtually, double-click the card in CTC to display the card view:

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 fiber connections and terminations, refer to the "Install Hardware" chapter of the Cisco ONS 15310-CL Procedure Guide.

Step 7 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the "Install Hardware" chapter of the Cisco ONS 15310-CL Procedure 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.124  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) means that the upstream transmitter has failed. If an EC-1 LOS alarm is not accompanied by additional alarms, a cabling problem is usually the cause of the alarm. The condition clears when two consecutive valid frames are 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 OK, verify that the correct port is in service:

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 of 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


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

Step 2 Verify that there is a valid input signal using a test set.

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

Step 4 If the alarm does not clear, verify that the UDC is provisioned:

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.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.126  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. The condition 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 may 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 okay, verify that the correct port is in service:

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 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 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 Cisco ONS 15310-CL Reference Manual 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.127  LO-TXPOWER

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

2.7.128  LPBKCRS

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

Logical Object: STSMON

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.129  LPBKDS1FEAC

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

2.7.130  LPBKDS1FEAC-CMD

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

2.7.131  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-3port 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.


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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.132  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.133  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, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.134  LPBKFACILITY (DS1, DS3)

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

Logical Objects: DS1, DS3

A Loopback Facility condition 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, 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. 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.135  LPBKFACILITY (EC1)

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

Logical Object: EC1

A Loopback Facility condition 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, refer to the "Network Troubleshooting Tests" section.


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

Clear the LPBKFACILITY (EC1) Condition


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

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


2.7.136  LPBKFACILITY (OCN)

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

Logical Object: OCN

A Loopback Facility condition occurs when a software facility (line) loopback is active for an OC-3 or OC-12 port.

For information about troubleshooting optical circuits, 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-3 facility loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted to the loopback is provided.



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


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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.137  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, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.138  LPBKTERMINAL (DS1, DS3)

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

Logical Objects: DS1, DS3

A Loopback Terminal condition 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, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.139  LPBKTERMINAL (EC1)

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

Logical Object: EC1

A Loopback Terminal condition 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, refer to the "Network Troubleshooting Tests" section.


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

Clear the LPBKTERMINAL (EC1) Condition


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

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


2.7.140  LPBKTERMINAL (OCN)

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

Logical Object: OCN

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


Note Performing a loopback on an in-service circuit is service-affecting. 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, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.142  MAN-REQ

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

Logical Objects: EQPT, STSMON, VT-MON

The Manual Switch Request condition occurs when a user initiates a Manual switch request on an OC-N port. Clearing the Manual switch clears the MAN-REQ condition. You do not need to clear the switch if you want the manual switch to remain.

Clear the MAN-REQ Condition


Step 1 Complete the "Initiate a 1+1 Protection Port Manual Switch Command" procedure.

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


2.7.143  MANRESET

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

Logical Objects: EQPT, PPM

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.144  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 the internal timing source.


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


2.7.145  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.146  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 the second timing source.


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


2.7.147  MANSWTOTHIRD

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

Logical Objects: EXT-SREF, NE-SREF

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


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


2.7.148  MANUAL-REQ-SPAN

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

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

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 an 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, has no circuits mapped to it, and is not part of a protection group, put the cursor over the provisioned card in CTC and right-click to choose Delete Card.

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


Note If the card is in service, has a circuit mapped 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):


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:

a. Click the Provisioning > Protection tabs.

b. Choose the protection group of the reporting card.

c. Click Delete.

Step 7 Right-click the card reporting the alarm.

Step 8 Choose Delete.

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

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


2.7.150  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 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.

2.7.151  MEA (PPM)

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

Logical Object: PPM

The Missing Equipment Attributes alarm for the pluggable port module (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.

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:

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 Card 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.152  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. CTC does not function properly until the alarm clears. The alarm clears when additional memory becomes available.

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

2.7.153  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 15310-CL-CTX 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.154  MFGMEM

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

Logical Objects: BPLANE, FAN, PPM


Note The CAP object is not used in this release of the ONS 15310-CL. It is reserved for future development.


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

To clear the MFGMEM alarm, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report a service-affecting problem.

2.7.155  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, whether or not you preprovision the card slot. This alarm is to be expected during provisioning. When the startup configuration file is copied to the 15310-CL-CTX, the alarm clears.


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


Clear the NO-CONFIG Condition


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

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

Step 2 Upload the configuration file to the 15310-CL-CTX:

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.156  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-59 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.157  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-112.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.158  PDI-P

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

Logical Object: STSMON, STSTRM

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 alarm 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-13 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-29 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 may 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:

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/techsupport for more information or call Cisco TAC to report a service-affecting problem (1-800-553-2447).

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

Step 3 If traffic is affected, complete the "Delete a Circuit" 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 of the Cisco ONS 15310-CL Procedure Guide.

Step 5 If the circuit deletion and recreation 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 the cross-connect between the OC-3 or OC-12 port and the reporting port.

Step 7 If the condition does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the "Maintain the Node" chapter of the Cisco ONS 15310-CL Procedure Guide.

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


2.7.159  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 occurs due to 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 may result in hazardous radiation exposure. Statement 1057


Clear the PLM-P Alarm


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


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

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


2.7.160  PLM-V

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

Logical Object: VT-TERM

A Payload Label Mismatch VT Layer alarm indicates that the content of the V5 byte in the SONET overhead is inconsistent or invalid. PLM-V occurs when ONS 15310-CLs interoperate with equipment that performs bit-synchronous mapping for DS-1. 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 traffic port does not allow VT6 or VT9 mapping.

Step 2 If the signal source matches the card, verify that the SONET VT path originator is sending the correct VT label value. You can find the SONET VT path originator using circuit provisioning steps.

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


2.7.161  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 interface 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 or part of a path protection, ensure that an automatic protection switch (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.


Step 2 If the alarm is reported against a 15310-CL-CTX card, complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure.

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

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

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


2.7.162  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 interface 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.163  RAI

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

Logical Objects: DS1, DS3

The Remote Alarm Indication condition signifies an end-to-end failure. The error condition is sent from one end of the SONET path to the other. RAI on 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

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


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

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

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


2.7.166  RFI-V

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

Logical Object: 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 of 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 DS-1 port is active and in service (IS-NR):

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 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-109 or the "UNEQ-V" alarm on page 2-111.

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


2.7.167  RUN-CFG-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

If you do not save the change, the change is lost after the card reboots.

2.7.168  SD

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

Logical Objects: DS1, DS3

A Signal Degrade (SD) condition for DS-1 or DS-3 occurs when the quality of an electrical signal has exceeded the BER signal degrade threshold. Signal degrade is defined by Telcordia as a soft failure condition. SD and also signal fail (SF) both monitor the incoming BER and are similar alarms, but SD is triggered at a lower bit error rate than SF.

The BER threshold is user provisionable and has a range for SD from 10-9 to 10-5.

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 may result in hazardous radiation exposure. Statement 1057



Note Some levels of BER errors (such as 10E_9) take a long period of time to raise or clear, about 9,000 seconds, or 150 minutes. If the SD threshold is provisioned at 10E_9 rate, the SD alarm needs at least one and a 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 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 OK, verify that optical receive levels are within the acceptable range.

Step 5 If receive levels are OK, 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 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 Verify that a single-mode laser is used at the far end.

Step 10 If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement.

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


2.7.169  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 on an Ethernet card or OC-3 port does not cause a protection switch. If the alarm is reported on a port that has also undergone a protection switch, the SD BER count continues to accumulate. The alarm 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 "Maintain the Node" 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 OK, verify that optical receive levels are within the acceptable range.

Step 5 If receive levels are OK, 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 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 Verify that a single-mode laser is used at the far end.

Step 10 If the problem does not clear, the transmitter at the other end of the optical line could be failing and require replacement.

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


2.7.170  SD-P

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

Logical Objects: STSMON, STSTRM, VT-TERM

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 10-9 to 10-5. For 1+1 and unprotected circuits, the BER threshold value is not user provisionable and the error rate is hard-coded to 10-6.

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

Signal degrade and signal fail both monitor the incoming BER and are similar alarms, but SD is triggered at a lower BER than SF. SD causes the port to switch from working to protect. The SD alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.

Clear the SD-P Condition


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

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


2.7.171  SD-V

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

Logical Object: VT-MON

An SD-V condition is similar to the "SD" condition on page 2-93, 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 10-9 to 10-5.

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.

Signal degrade and signal fail both monitor the incoming BER and are similar alarms, but SD is triggered at a lower BER than SF. SD causes the port to switch from working to protect. The SD alarm clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.

Clear the SD-V Condition


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

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


2.7.172  SF

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

Logical Objects: DS1, DS3

A Signal Fail (SF) condition occurs when the quality of the signal has exceeded the BER signal failure threshold. Signal failure is defined by Telcordia as a "hard failure" condition. The SD and SF conditions both monitor the incoming BER error rate and are similar conditions, but SF is triggered at a higher BER than SD.

The BER threshold is user provisionable and has a range for SF from 10-5 to 10-3.


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 may 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.173  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 alarm 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.174  SF-P

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

Logical Objects: STSMON, STSTRM, VT-TERM

An SF Path condition is similar to an "SF-L" condition on page 2-97, 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.175  SF-V

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

Logical Object: VT-MON

An SF-V condition is similar to the "SF" condition on page 2-96, but it applies to the VT layer of the SONET overhead.


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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.176  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/techsupport for more information or call Cisco TAC (1-800-553-2447).


Note SFTWDOWN is an informational alarm.


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

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:

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 ONS 15310-CL Reference Manual for more information on SNTP Host.

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


2.7.178  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 of 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.179  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.180  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 ONS 15310-CL. The ONS 15310-CL is set up to receive SSM, but the timing source is not delivering valid SSM messages.

Clear the SSM-FAIL Alarm


Step 1 Verify that SSM is enabled on the external timing source.

Step 2 If timing is enabled, use an optical test set to determine that the external timing source is delivering SSM.

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

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


2.7.181  SSM-OFF

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

Logical Objects: BITS, DS1, OCN

The SSM Off condition applies to references used for timing the node. It occurs when the SSM for the reference has been turned off. The ONS  system is set up to receive SSM, but the timing source is not delivering SSM messages.

Clear the SSM-OFF Condition


Step 1 Complete the "Clear the SSM-FAIL Alarm" procedure.

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


2.7.182  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.183  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.184  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.185  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.186  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.187  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.188  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.189  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. 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 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.190  SSM-TNC

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

Logical Objects: BITS, DS1, 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.191  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.192  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 the secondary timing source (reference 2). 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.

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

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


2.7.193  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 the third timing source (reference 3). 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.

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-105 or the "SYNCSEC" alarm on page 2-106.

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


2.7.194  SWMTXMOD

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

Logical Object: EQPT

The Switching Matrix Module Failure alarm occurs on 15310-CL-CTX cards and Ethernet cards. If the alarm reports against an Ethernet card, it occurs when the cross-connect logic component on the 15310-CL-CTX card is out of frame (OOF) with the logic component on the reporting traffic port. All traffic on the reporting port is lost.

If the alarm reports against a 15310-CL-CTX, it occurs when a logic component internal to the reporting port is OOF with a second logic component on the same cross-connect card.

In R5.0, the alarm initiates an autonomous switch in 1+1 and path protection protection schemes if it is raised on the following I/O ports: DS-1, DS-3, and OC-3. The switching time is greater than 60 milliseconds and typically lasts approximately 500 milliseconds.

Clear the SWMTXMOD Alarm


Step 1 Complete the "Soft- or Hard-Reset a 15310-CL-CTX Card" procedure for the card. For the LED behavior, see the "Typical 15310-CL-CTX 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 LED indicates an active card.

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


2.7.195  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 continues to report after replacing the 15310-CL-CTX card, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.196  SYNCPRI

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

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 ranking 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 the secondary timing source also triggers the "SWTOSEC" alarm on page 2-104.

Clear the SYNCPRI Alarm


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

Step 2 Verify the current configuration for the REF-1 of the NE Reference.

Step 3 If the primary 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.197  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 the secondary timing source (reference 2). 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 SYNCSEC occurs, the ONS 15310-CL should switch to the third timing source (reference 3) to obtain valid timing. Switching to the third timing source also triggers the "SWTOTHIRD" alarm on page 2-104.

Clear the SYNCSEC Alarm


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

Step 2 Verify the current configuration of the REF-2 for the NE Reference.

Step 3 If the 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.198  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). The ONS 15310-CL system uses three ranking timing references. The timing references are typically two BITS-level or line-level sources and an internal reference. If SYNCTHIRD occurs and the ONS 15310-CL uses an internal reference for source three, the 15310-CL-CTX card might have failed. The system often reports either the "FRNGSYNC" condition on page 2-53 or the "HLDOVRSYNC" condition on page 2-56 after a SYNCTHIRD alarm.

Clear the SYNCTHIRD Alarm


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

Step 2 Verify that the current configuration of the REF-3 for the NE Reference. For more information about references, refer to the "Turn Up Node" chapter of 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.


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

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.199  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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


Note SYSBOOT is an informational alarm. It only requires troubleshooting if it does not clear.


2.7.200  TIM-P

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

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

TIM-P also occurs on a port that has previously been operating without alarms if someone switches or removes the DS-3 cables or optical fibers that connect the ports. TIM-P is usually accompanied by other alarms, such as the "LOS (OCN)" alarm on page 2-73, the "UNEQ-P" alarm on page 2-109, or the "PLM-P" alarm on page 2-88. If these alarms accompany TIM-P, reattach or replace the original cables/fibers to clear the alarms.

Clear the TIM-P Alarm


Step 1 Log into the circuit source node and click the Circuits tab.

Step 2 Select the circuit reporting the condition, then click Edit.

Step 3 In the Edit Circuit window, check the Show Detailed Map box.

Step 4 On the detailed circuit map, right-click the source circuit port and choose Edit J1 Path Trace (port) from the shortcut menu.

Step 5 Compare the Current Transmit String and the Current Expected String entries in the Edit J1 Path Trace dialog box.

Step 6 If the strings differ, correct the Transmit or Expected strings and click Apply.

Step 7 Click Close.

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


2.7.201  TIM-V

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

Logical Object: VT-TERM

The VT Path Trace Identifier Mismatch alarm is raised on VT terminations when the the J2 path trace is enabled and is mismatched with the expected trace string.

Clear the TIM-V Alarm


Step 1 Log into the circuit source node and click the Circuits tab.

Step 2 Select the circuit reporting the condition, then click Edit.

Step 3 In the Edit Circuit window, check the Show Detailed Map box.

Step 4 On the detailed circuit map, right-click the source circuit port and choose Edit J2 Path Trace (port) from the shortcut menu.

Step 5 Compare the Current Transmit String and the Current Expected String entries in the Edit J2 Path Trace dialog box.

Step 6 If the strings differ, correct the Transmit or Expected strings and click Apply.

Step 7 Click Close.

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

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


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

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-87 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.203  UNEQ-P

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

Logical Objects: STSMON, STSTRM

A signal label mismatch fault (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, a UNEQ-P alarm is reported on the OC-3 ports and the "AIS-P" condition on page 2-14 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:


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:

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.


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

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

Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.

Complete the "Delete a Circuit" procedure.

Step 10 Recreate the circuit with the correct circuit size. Refer to the "Create Circuits" chapter of the Cisco ONS 15310-CL Procedure Guide.

Step 11 Log back in and verify that all circuits terminating in the reporting port are active:

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 of 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 may 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.204  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 the node that is transmitting the VT-level signal into the node reporting the UNEQ-V. The problem node is the next node upstream that processes the signal at the VT level. The V in UNEQ-V indicates that the failure has occurred at the VT layer.


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 may 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/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.


2.7.205  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-87. It only occurs when a Critical alarm, such as LOS, causes a signal loss.

Clear the VCG-DEG Condition


Step 1 Look for and clear any Critical 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/techsupport for more information or call Cisco TAC (1-800-553-2447).


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

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.207  WKSWPR

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

Logical Objects: OCN, STSMON, STSTRM

The Working Switched To Protection condition occurs when a line experiences the "LOS (OCN)" alarm on page 2-73.

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/techsupport for more information or call Cisco TAC (1-800-553-2447).


2.7.208  WTR

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

Logical Objects: OCN, STSMON, VT-MON

The Wait To Restore condition occurs when the "WKSWPR" condition on page 2-112 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 is switched 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 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-9 lists the line alarms reported under each format. The choice of framing format does not affect the reporting of STS alarms.

Table 2-9 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 15310-CL-CTX 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 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 path protection span switching field.

Step 5 Choose FORCE SWITCH AWAY from the drop-down list.

Step 6 Click Apply.

Step 7 In the Confirm path protection 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 path protection span switching field.

Step 4 Choose MANUAL from the drop-down list.

Step 5 Click Apply.

Step 6 In the Confirm path protection 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 path protection span switching field.

Step 4 Choose LOCK OUT OF PROTECT from the drop-down list.

Step 5 Click Apply.

Step 6 In the Confirm path protection 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:

a. Click the Perform path protection span switching field.

b. Choose CLEAR from the drop-down list.

c. Click Apply.

d. In the Confirm path protection 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.



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. 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, 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 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. 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 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 on 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:

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 Loopbacks


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.