Cisco ONS 15454 DWDM Troubleshooting Guide, Release 9.8
- Updated:
- February 8, 2014
Chapter: Chapter 2, Alarm Troubleshooting
- Alarm Indexes
- Logical Objects
- Trouble Characterizations
- Safety Summary
- Trouble-Clearing Procedures
- ACT-SOFT-VERIF-FAIL
- AIS
- AIS-L
- AIS-P
- ALS
- ALS-DISABLED
- AMPLI-INIT
- APC-CORR-SKIPPED
- APC-DISABLED
- APC-END
- APC-OUT-OF-RANGE
- APC-WRONG-GAIN
- APSB
- APSCM
- APSIMP
- APS-INV-PRIM
- APSMM
- APS-PRIM-FAC
- APS-PRIM-SEC-MISM
- AS-CMD
- AS-MT
- AU-AIS
- AU-LOP
- AUTO-SENSE
- AUTO-SENSE-DSBLD
- AUTOLSROFF
- AUTORESET
- AUTOSW-AIS
- AUTOSW-AIS-SNCP
- AUTOSW-LOP (STSMON)
- AUTOSW-LOP-SNCP
- AUTOSW-PDI
- AUTOSW-PDI-SNCP
- AUTOSW-SDBER
- AUTOSW-SDBER-SNCP
- AUTOSW-SFBER
- AUTOSW-SFBER-SNCP
- AUTOSW-UNEQ (STSMON)
- AUTOSW-UNEQ-SNCP (VCMON-HP)
- AWG-DEG
- AWG-FAIL
- AWG-OVERTEMP
- AWG-WARM-UP
- BAT-FAIL
- BKUPMEMP
- BP-LPBKFACILITY
- BP-LPBKTERMINAL
- BPV
- CARLOSS (EQPT)
- CARLOSS (FC)
- CARLOSS (GE)
- CARLOSS (ISC)
- CARLOSS (TRUNK)
- CASETEMP-DEG
- CD
- CFM-CONFIG-ERROR
- CFM-LOOP
- CFM-MEP-DOWN
- CFM-XCON-SERVICE
- CHANLOSS
- CLDRESTART
- COMP-CARD-MISSING
- COMM-FAIL
- CONTBUS-DISABLED
- CONTBUS-IO-A
- CONTBUS-IO-B
- COOL-MISM
- CP-UNVER-CLEARED Alarm
- CTNEQPT-MISMATCH
- DATA-CRC
- DATAFLT
- DBOSYNC
- DCU-LOSS-FAIL
- DISCONNECTED
- DSP-COMM-FAIL
- DSP-FAIL
- DUP-IPADDR
- DUP-NODENAME
- DUP-SHELF-ID
- EFM-PEER-MISSING
- EFM-RFI-CE
- EFM-RFI-DG
- EFM-RFI-LF
- EFM-RLBK
- EHIBATVG
- ELWBATVG
- ENCAP-MISMATCH-P
- EOC
- EOC-E
- EOC-L
- EQPT
- EQPT-DEGRADE
- EQPT-DIAG
- EQPT-FAIL
- EQPT-MISS
- ERFI-P-CONN
- ERFI-P-SRVR
- ESMC-FAIL
- EVAL-LIC
- EXC-BP
- EXCCOL
- EXT EXT
- FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS)
- FAILTOSW (TRUNK)
- FAILTOSW-HO
- FAILTOSW-PATH FAILTOSW-PATH
- FAN
- FAPS
- FAPS-CONFIG-MISMATCH
- FC-NO-CREDITS
- FDI
- FE-FRCDWKSWBK-SPAN
- FE-FRCDWKSWPR-SPAN
- FE-MANWKSWBK-SPAN
- FE-MANWKSWPR-SPAN
- FEC-MISM
- FEPRLF
- FIBERTEMP-DEG
- FIPS_TEST_FAILED
- FORCED-REQ
- FORCED-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN, OTS)
- FORCED-REQ-SPAN (TRUNK)
- FP-LINK-LOSS
- FRCDSWTOINT
- FRCDSWTOPRI
- FRCDSWTOSEC
- FRCDSWTOTHIRD
- FRNGSYNC
- FSTSYNC
- FTA-MISMATCH
- GAIN-HDEG
- GAIN-HFAIL
- GAIN-LDEG
- GAIN-LFAIL
- GCC-EOC
- GE-OOSYNC (FC, GE, ISC)
- GE-OOSYNC (TRUNK)
- GFP-CSF
- GFP-CSF-SIGLOSS
- GFP-CSF-SYNCLOSS
- GFP-LFD
- GFP-UP-MISMATCH
- HELLO
- HIBATVG
- HI-BER
- HI-CCVOLT
- HI-LASERBIAS
- HI-LASERTEMP
- HI-RXPOWER
- HITEMP
- HI-TXPOWER
- HLDOVRSYNC
- HP-DEG
- HP-ENCAP-MISMATCH
- HP-EXC
- HP-PLM
- HP-RFI
- HP-TIM
- HP-UNEQ
- I-HITEMP
- ILK-FAIL
- IMPROPRMVL
- INHSWPR
- INHSWWKG
- INCOMPATIBLE-SEND-PDIP
- INCOMPATIBLE-SW
- INTRUSION-PSWD
- INVALID-MUXCONF
- INVMACADR
- ISIS-ADJ-FAIL
- KEY_EX_FAIL
- KEY_WRITE_FAIL
- LASER-APR
- LASER-OFF-WVL-DRIFT
- LASERBIAS-DEG
- LASERBIAS-FAIL
- LASEREOL
- LASERTEMP-DEG
- LICENSE-EXPIRED
- LIC-EXPIRING-SHORTLY
- LIC-EXPIRING-SOON
- LIC-MISSING
- LMP-FAIL
- LMP-SD
- LMP-SF
- LMP-UNALLOC
- LOCAL-FAULT
- LOCKOUT-REQ
- LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC)
- LOCKOUT-REQ (TRUNK)
- LOF (BITS)
- LOF (TRUNK)
- LOGBUFR90
- LOGBUFROVFL
- LO-LASERBIAS
- LO-LASERTEMP
- LOM
- LOP-P
- LO-RXPOWER
- LOS (2R)
- LOS (BITS)
- LOS (ESCON)
- LOS (ISC)
- LOS (OTS)
- LOS (TRUNK)
- LOS-O
- LOS-P (AOTS, OMS, OTS)
- LOS-P (OCH)
- LOS-P (TRUNK)
- LOS-RAMAN (OTS)
- LO-TXPOWER
- LPBKCRS
- LPBKFACILITY (ESCON)
- LPBKFACILITY (FC)
- LPBKFACILITY (GE)
- LPBKFACILITY (ISC)
- LPBKFACILITY (TRUNK)
- LPBKTERMINAL (ESCON)
- LPBKTERMINAL (FC)
- LPBKTERMINAL (GE)
- LPBKTERMINAL (ISC)
- LPBKTERMINAL (TRUNK)
- LWBATVG
- MAN-LASER-RESTART
- MAN-REQ
- MANRESET
- MANSWTOINT
- MANSWTOPRI
- MANSWTOSEC
- MANSWTOTHIRD
- MANUAL-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN, OTS)
- MANUAL-REQ-SPAN (TRUNK)
- MEA (AIP)
- MEA (EQPT)
- MEA (FAN)
- MEA (PPM)
- MEA (SHELF)
- MEM-GONE
- MEM-LOW
- MFGMEM
- MS-AIS
- MS-DEG
- MS-EOC
- MS-EXC
- MS-RFI
- MT-OCHNC
- NON-CISCO-PPM
- NOT-AUTHENTICATED
- OCHNC-INC
- OCHTERM-INC
- ODUK-1-AIS-PM
- ODUK-2-AIS-PM
- ODUK-3-AIS-PM
- ODUK-4-AIS-PM
- ODUK-AIS-PM
- ODUK-BDI-PM
- ODUK-LCK-PM
- ODUK-OCI-PM
- ODUK-SD-PM
- ODUK-SF-PM
- ODUK-TIM-PM
- OPEN-SLOT
- OPTNTWMIS
- OPWR-HDEG
- OPWR-HFAIL
- OPWR-LDEG
- OPWR-LFAIL
- OSRION
- OTUK-AIS
- OTUK-BDI
- OTUK-IAE
- OTUK-LOF
- OTUK-SD
- OTUK-SF
- OTUK-TIM
- OUT-OF-BUNDLE
- OUT-OF-SYNC
- OVER-TEMP-UNIT-PROT
- PARAM-MISM
- PAYLOAD-UNKNOWN
- PDI-P
- PEER-CSF
- PEER-NORESPONSE
- PMD-DEG
- PMI
- PORT-COMM-FAIL
- PORT-FAIL
- PPR-BDI
- PPR-FDI
- PPR-MAINT
- PPR-TRIG-EXCD
- PROT-SOFT-VERIF-FAIL
- PROTNA
- PROV-MISMATCH
- PTIM
- PWR-CON-LMT
- PWR-FAIL-A
- PWR-FAIL-B
- PWR-FAIL-RET-A
- PWR-FAIL-RET-B
- PWR-PROT-ON
- RAMAN-G-NOT-REACHED
- REMOTE-FAULT
- REP-LINK-FLAPPING
- REP-NEIHB-ADJ-FAIL
- REP-SEGMENT-FAULT
- RFI
- RFI-L
- RFI-P
- RLS
- ROUTE-OVERFLOW
- RS-EOC
- RS-TIM
- SBYTCC-NEINTCLK
- SD (TRUNK)
- SD-L
- SD-L (TRUNK)
- SD-P
- SDBER-EXCEED-HO
- SEQ_MISMATCH_COUNT
- SF (TRUNK)
- SF-L
- SF-L (TRUNK)
- SF-P
- SFTWDOWN
- SFTWDOWN-FAIL
- SHELF-COMM-FAIL
- SH-IL-VAR-DEG-HIGH
- SH-IL-VAR-DEG-LOW
- SHUTTER-OPEN SHUTTER-OPEN
- SIGLOSS SIGLOSS
- SNTP-HOST
- SOFT-VERIF-FAIL
- SPANLEN-OUT-OF-RANGE
- SPAN-NOT-MEASURED
- SQUELCHED
- SSM-DUS
- SSM-FAIL
- SSM-LNC
- SSM-OFF
- SSM-PRC
- SSM-PRS
- SSM-RES
- SSM-SMC
- SSM-ST2
- SSM-ST3
- SSM-ST3E
- SSM-ST4
- SSM-STU
- SSM-TNC
- SW-MISMATCH
- SWTOPRI
- SWTOSEC
- SWTOTHIRD
- SYNC-FREQ
- SYNCLOSS
- SYNCPRI
- SYNCSEC
- SYNCTHIRD
- SYSBOOT
- TEMP-LIC
- TEMP-MISM
- TIM
- TIM-MON
- TIM-P
- TIM-S
- TRAIL-SIGNAL-FAIL
- TRUNK-ODU-AIS
- TRUNK-PAYLOAD-MISM
- TX-OFF-NON-CISCO-PPM
- UNC-WORD
- UNEQ-P
- UNIT-HIGH-TEMP
- UNQUAL-PPM
- UNREACHABLE-TARGET-POWER
- USBSYNC
- USB-WRITE-FAIL
- UT-COMM-FAIL
- UT-FAIL
- VOA-DISABLED
- VOA-HDEG
- VOA-HFAIL
- VOA-LMDEG
- VOA-LFAIL
- VOLT-MISM
- WAN-SYNCLOSS
- WKSWPR (2R, EQPT, ESCON, FC, GE, ISC, OTS)
- WKSWPR (TRUNK)
- WTR (2R, ESCON, FC, GE, ISC)
- WTR (TRUNK)
- WVL-DRIFT-CHAN-OFF
- WVL-MISMATCH
- Node and Ring Identification, Change, Visibility, and Termination
- Protection Switching, Lock Initiation, and Clearing
- Initiate a 1+1 Protection Port Force Switch Command
- Initiate a 1+1 Manual Switch Command
- Initiate a 1:1 Card Switch Command
- Clear a 1+1 Force or Manual Switch Command
- Initiate a Lock-On Command
- Initiate a Card or Port Lockout Command
- Clear a Lock-On or Lockout Command
- Initiate a Lockout on a BLSR Protect Span
- Clear a BLSR External Switching Command
- CTC Card Resetting and Switching
- Physical Card Reseating, Resetting, and Replacement
- Generic Signal and Circuit Procedures
- Air Filter and Fan Procedures
- Interface Procedures
Alarm Troubleshooting
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco DWDM alarm and condition. Tables Table 1 through Table 1 provide lists of DWDM alarms organized by severity. Table 1 provides a list of alarms organized alphabetically. Table 1 gives definitions of all DWDM alarm logical objects, which are the basis of the alarm profile list in Table 1. For a comprehensive list of all conditions and instructions for using TL1 commands, refer to the Cisco ONS SONET TL1 Command GuideAn alarm troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm.
If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html or call the Cisco Technical Assistance Center (1 800 553-2447) to report the problem.
Alarms can occur even in those cards that are not explicitly mentioned in the Alarm sections. When an alarm is raised, refer to its clearing procedure.
For more information about alarm profiles, see the Alarm and TCA Monitoring and Management document.
 Note |
Unless otherwise noted, ONS 15454 refers to the ANSI and ETSI versions of the platform. |
- Alarm Indexes
- Logical Objects
- Trouble Characterizations
- Safety Summary
- Trouble-Clearing Procedures
- Trouble-Clearing Procedures
- DWDM Card LED Activity
- Traffic Card LED Activity
- Frequently Used Alarm Troubleshooting Procedures
Alarm Indexes
The following tables group alarms and conditions by their default severities in the ONS DWDM 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 that are not currently implemented but are reserved for future use. |
Note |
The CTC default alarm profile in some cases contains two severities for one alarm (for example, MJ/MN). The 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. |
- Critical Alarms (CR)
- Major Alarms (MJ)
- Minor Alarms (MN)
- NA Conditions
- NR Conditions
- Alarms and Conditions Listed By Alphabetical Entry
Critical Alarms (CR)
Table 1 alphabetically lists Critical (CR) DWDM alarms.
ACT-SOFT-VERIF-FAIL (EQPT) |
HP-UNEQ (VCTRM-HP) |
OPWR-HFAIL (OCH) |
AU-LOP (VCMON-HP) |
I-HITEMP (NE) |
OPWR-HFAIL (OMS) |
AU-LOP (VCTRM-HP) |
ILK-FAIL (TRUNK) |
OPWR-HFAIL (OTS) |
AUTOLSROFF (OCN) |
IMPROPRMVL (EQPT) |
OPWR-LFAIL (AOTS) |
AWG-FAIL (OTS) |
IMPROPRMVL (PPM) |
OPWR-LFAIL (OCH-TERM) |
— |
INVALID-MUXCONF (EQPT) |
— |
— |
LIC-MISSING (EQPT) |
— |
— |
LICENSE-EXPIRED (EQPT) |
— |
AWG-OVERTEMP (OTS) |
LOF (TRUNK) |
OPWR-LFAIL (OCH) |
BKUPMEMP (EQPT) |
LOM (TRUNK) |
OPWR-LFAIL (OMS) |
CD (TRUNK) |
LOP-P (STSMON) |
OPWR-LFAIL (OTS) |
CONTBUS-DISABLED (EQPT) |
LOP-P (STSTRM) |
OTUK-LOF (TRUNK) |
ENCAP-MISMATCH-P (POS) |
LOS (2R) |
OTUK-TIM (TRUNK) |
OVER-TEMP-UNIT-PROT (EQPT) |
||
— |
— |
PAYLOAD-UNKNOWN (PPM) |
— |
— |
PORT-COMM-FAIL (DWDM-CLIENT) |
— |
— |
PORT-COMM-FAIL (DWDM-TRUNK) |
ENCAP-MISMATCH-P (STSTRM) |
LOS (ESCON) |
PORT-FAIL (OCH) |
EQPT (AICI-AEP) |
LOS (ISC) |
RS-TIM (STMN) |
EQPT (AICI-AIE) |
LOS (OTS) |
TIM (TRUNK) |
EQPT-DIAG (EQPT) |
LOS (TRUNK) |
SOFT-VERIF-FAIL (EQPT) |
EQPT (EQPT) |
LOS-P (OCH) |
TIM-P (STSTRM) |
EQPT (PPM) |
LOS-P (OMS) |
TIM-S (OCN) |
EQPT-MISS (FAN) |
LOS-P (OTS) |
UNEQ-P (STSMON) |
FAN (FAN) |
LOS-P (TRUNK) |
UNEQ-P (STSTRM) |
FIPS_TEST_FAILED (EQPT) |
LOS-RAMAN (OTS) |
— |
GAIN-HFAIL (AOTS) |
MEA (AIP) |
VOA-DISABLED (EQPT) |
GAIN-LFAIL (AOTS) |
MEA (EQPT) |
VOA-HFAIL (AOTS) |
GE-OOSYNC (FC) |
MEA (FAN) |
VOA-HFAIL (OCH) |
GE-OOSYNC (GE) |
MEA (PPM) |
VOA-HFAIL (OMS) |
GE-OOSYNC (ISC) |
MFGMEM (AICI-AEP) |
VOA-HFAIL (OTS) |
GE-OOSYNC (TRUNK) |
MFGMEM (AICI-AIE) |
VOA-LFAIL (AOTS) |
HITEMP (NE) |
MFGMEM (BPLANE) |
VOA-LFAIL (OCH) |
HP-ENCAP-MISMATCH (VCTRM-HP) |
MFGMEM (FAN) |
VOA-LFAIL (OMS) |
HP-PLM (VCMON-HP) |
MFGMEM (PPM) |
VOA-LFAIL (OTS) |
HP-PLM (VCTRM-HP) |
OPWR-HFAIL (AOTS) |
USBSYNC (USB) |
HP-TIM (VCMON-HP) |
— |
USB-WRITE-FAIL (USB) |
HP-UNEQ (VCMON-HP) |
— |
— |
Major Alarms (MJ)
Table 1 alphabetically lists the Major (MJ) DWDM alarms.
APSCNMIS (OCN) |
GFP-LFD (GFP-FAC) |
PEER-NORESPONSE (EQPT) |
BAT-FAIL (PWR) |
GFP-LFD (ML100T) |
PMD-DEG (TRUNK) |
CARLOSS (EQPT) |
GFP-LFD (ML1000) |
PROV-MISMATCH (TRUNK) |
CARLOSS (FC) |
GFP-LFD (MLMR) |
PROT-SOFT-VERIF-FAIL (EQPT) |
CARLOSS (GE) |
GFP-LFD (POS) |
PTIM (TRUNK) |
CARLOSS (ISC) |
GFP-UP-MISMATCH (CE100T) |
PWR-PROT-ON (OTS) |
CARLOSS (TRUNK) |
GFP-UP-MISMATCH (CE1000) |
REMOTE-FAULT (ETH) |
DATA-CRC (OCH) |
GFP-UP-MISMATCH (CEMR) |
REP-LINK-FLAPPING (ETH) |
DBOSYNC (NE) |
GFP-UP-MISMATCH (FCMR) |
REP-NEIHB-ADJ-FAIL (ETH) |
DSP-COMM-FAIL (TRUNK) |
GFP-UP-MISMATCH (GFP-FAC) |
RING-ID-MIS (OSC-RING) |
DSP-FAIL (TRUNK) |
GFP-UP-MISMATCH (ML100T) |
SHELF-COMM-FAIL (SHELF) |
DUP-SHELF-ID (SHELF) |
GFP-UP-MISMATCH (ML1000) |
SIGLOSS (ESCON) |
EFM-RFI-CE (GE) |
GFP-UP-MISMATCH (MLMR) |
SIGLOSS (FC) |
EFM- RFI-LF (GE) |
GFP-UP-MISMATCH (POS) |
SIGLOSS (GE) |
— |
HI-BER1 (DWDM-CLIENT) |
— |
— |
HI-BER1 (DWDM-TRUNK) |
— |
EHIBATVG (PWR) |
HIBATVG (PWR) |
SIGLOSS (ISC) |
ELWBATVG (PWR) |
INVMACADR (AIP) |
SIGLOSS (TRUNK) |
EQPT-FAIL (EQPT) |
KEY_EX_FAIL (OTU-TRUNK) |
— |
— |
KEY_WRITE_FAIL (OTU-TRUNK)) |
— |
FC-NO-CREDITS (FC) |
LASER-OFF-WVL-DRIFT (OCN) |
SYNCLOSS (FC) |
FC-NO-CREDITS (TRUNK) |
LASER-OFF-WVL-DRIFT (STMN) |
SYNCLOSS (GE) |
FEC-MISM (TRUNK) |
LASER-OFF-WVL-DRIFT (TRUNK) |
SYNCLOSS (ISC) |
GFP-CSF (CE100T) |
LASERBIAS-FAIL (AOTS) |
SYNCLOSS (TRUNK) |
— |
LIC-EXPIRING-SHORTLY (EQPT) |
— |
— |
LIC-EXPIRING-SOON (EQPT) |
— |
GFP-CSF (CE1000) |
LWBATVG (PWR) |
SYNCPRI (NE-SREF) |
GFP-CSF (CEMR) |
LOCAL-FAULT (ETH) |
SYSBOOT (NE) |
GFP-CSF (FCMR) |
MEA (SHELF) |
UT-COMM-FAIL (TRUNK) |
GFP-CSF (GFP-FAC) |
MEM-GONE (EQPT) |
UT-FAIL (TRUNK) |
— |
— |
TRUNK-PAYLOAD-MISM (FC) |
— |
— |
TRUNK-PAYLOAD-MISM (GE) |
— |
— |
TRUNK-PAYLOAD-MISM (OCN) |
— |
— |
TRUNK-PAYLOAD-MISM (OTU) |
GFP-CSF (ML100T) |
ODUK-TIM-PM (TRUNK) |
TX-OFF-NON-CISCO-PPM (PPM) |
GFP-CSF (ML1000) |
OUT-OF-BUNDLE (ETH) |
WAN-SYNCLOSS (STSMON) |
GFP-CSF (MLMR) |
OUT-OF-BUNDLE (CHGRP) |
WAN-SYNCLOSS (STSTRM) |
GFP-CSF-SIGLOSS (GFP-FAC) |
— |
— |
GFP-CSF-SYNCLOSS (GFP-FAC) |
— |
— |
GFP-LFD (CE100T) |
OUT-OF-SYNC (FC) |
WAN-SYNCLOSS (VCMON-HP) |
GFP-LFD (CE1000) |
OUT-OF-SYNC (GE) |
WAN-SYNCLOSS (VCTRM-HP) |
GFP-LFD (CEMR) |
OUT-OF-SYNC (TRUNK) |
WVL-MISMATCH (TRUNK) |
GFP-LFD (FCMR) |
OUT-OF-SYNC (TRUNK) |
— |
— |
PEER-CSF (OCN) |
— |
— |
PEER-CSF (STM) |
— |
Minor Alarms (MN)
Table 1 alphabetically lists Minor (MN) DWDM alarms.
AMPLI-INIT (AOTS) |
HI-LASERBIAS (FC) |
LO-TXPOWER (EQPT) |
APC-CORR-SKIPPED (AOTS) |
HI-LASERBIAS (GE) |
LO-TXPOWER (ESCON) |
APC-CORR-SKIPPED (OCH) |
HI-LASERBIAS (ISC) |
LO-TXPOWER (FC) |
APC-CORR-SKIPPED (OMS) |
HI-LASERBIAS (OCN) |
LO-TXPOWER (GE) |
APC-CORR-SKIPPED (OTS) |
HI-LASERBIAS (PPM) |
LO-TXPOWER (ISC) |
APC-OUT-OF-RANGE (AOTS) |
HI-LASERBIAS (TRUNK) |
LO-TXPOWER (OCN) |
APC-OUT-OF-RANGE (OCH) |
HI-LASERTEMP (EQPT) |
LO-TXPOWER (PPM) |
APC-OUT-OF-RANGE (OMS) |
HI-LASERTEMP (OCN) |
LO-TXPOWER (TRUNK) |
APC-OUT-OF-RANGE (OTS) |
HI-LASERTEMP (PPM) |
MEM-LOW (EQPT) |
APS-INV-PRIM (OCN) |
HI-RXPOWER (2R) |
MS-EOC (STMN) |
APS-PRIM-FAC (OCN) |
HI-RXPOWER (ESCON) |
NON-CISCO-PPM (PPM) |
APS-PRIM-SEC-MISM (OCN) |
HI-RXPOWER (FC) |
OPWR-HDEG (AOTS) |
APSB (OCN) |
HI-RXPOWER (GE) |
OPWR-HDEG (OCH-TERM) |
APSC-IMP (OCN) |
HI-RXPOWER (ISC) |
OPWR-HDEG (OCH) |
APSCDFLTK (OCN) |
HI-RXPOWER (OCN) |
OPWR-HDEG (OMS) |
APSCINCON (OCN) |
HI-RXPOWER (TRUNK) |
OPWR-HDEG (OTS) |
APSCM (OCN) |
HITEMP (EQPT) |
OPWR-LDEG (AOTS) |
APSIMP (OCN) |
HI-TXPOWER (2R) |
OPWR-LDEG (OCH-TERM) |
APSMM (OCN) |
HI-TXPOWER (EQPT) |
OPWR-LDEG (OCH) |
AUTORESET (EQPT) |
HI-TXPOWER (ESCON) |
OPWR-LDEG (OMS) |
AWG-DEG (OTS) |
HI-TXPOWER (FC) |
OPWR-LDEG (OTS) |
BPV (BITS) |
HI-TXPOWER (GE) |
OTUK-IAE (TRUNK) |
CASETEMP-DEG (AOTS) |
HI-TXPOWER (ISC) |
OUT-OF-BUNDLE (ETH) |
CFM-CONFIG-ERROR (ETH) |
HI-TXPOWER (OCN) |
OUT-OF-BUNDLE (CHGRP) |
CFM-LOOP (ETH) |
HI-TXPOWER (PPM) |
PROTNA (EQPT) |
CFM-MEP-DOWN (ETH) |
HI-TXPOWER (TRUNK) |
PROV-MISMATCH (PPM) |
CFM-XCON-SERVICE (ETH) |
HP-TIM (VCMON-HP) |
PWR-FAIL-A (EQPT) |
COMP-CARD-MISSING (EQPT) |
— |
— |
CONTBUS-IO-A (CONTBUS-A) (EQPT) |
IS-ADJ-FAIL (OCN) |
PWR-FAIL-B (EQPT) |
CONTBUS-IO-B (CONTBUS-B) (EQPT) |
IS-ADJ-FAIL (TRUNK) |
PWR-FAIL-RET-A (EQPT) |
DATAFLT (NE) |
LASERBIAS-DEG (AOTS) |
PWR-FAIL-RET-B (EQPT) |
DCU-LOSS-FAIL (OTS) |
LASERBIAS-DEG (OTS) |
RAMAN-G-NOT-REACHED (OTS) |
DUP-IPADDR (NE) |
LASERTEMP-DEG (AOTS) |
RS-EOC (STMN) |
— |
— |
SEQ_MISMATCH_COUNT (OTU-TRUNK) |
DUP-NODENAME (NE) |
LMP-FAIL (GE) |
SFTWDOWN (EQPT) |
— |
— |
SFTWDOWN-FAIL (EQPT) |
EFM-PEER-MISSING (GE) |
LMP-SD (GE) |
SH-IL-VAR-DEG-HIGH (OTS) |
EOC (OCN) |
LMP-SF (GE) |
SH-IL-VAR-DEG-LOW (OTS) |
EOC (TRUNK) |
LOF (BITS) |
SNTP-HOST (NE) |
EOC-L (OCN) |
LO-LASERBIAS (EQPT) |
SPANLEN-OUT-OF-RANGE (OTS) |
EOC-L (TRUNK) |
LO-LASERBIAS (OCN) |
SSM-FAIL (BITS) |
EQPT-DEGRADE (EQPT) |
LO-LASERBIAS (PPM) |
SSM-FAIL (TRUNK) |
ESMC-FAIL (GE) |
— |
— |
ESMC-FAIL (TRUNK) |
— |
— |
EVAL-LIC (EQPT) |
— |
— |
EXC-BP (OTS) |
LO-LASERTEMP (EQPT) |
SYNCPRI (EXT-SREF) |
EXCCOL (EQPT) |
LO-LASERTEMP (OCN) |
SYNCSEC (EXT-SREF) |
EXT (ENVALRM) |
LO-LASERTEMP (PPM) |
SYNCSEC (NE-SREF) |
FAPS-CONFIG-MISMATCH (EQPT) |
LO-RXPOWER (2R) |
SYNCTHIRD (EXT-SREF) |
FEPRLF (OCN) |
LO-RXPOWER (ESCON) |
SYNCTHIRD (NE-SREF) |
— |
— |
TEMP-LIC (EQPT) |
FIBERTEMP-DEG (AOTS) |
LO-RXPOWER (FC) |
TIM-MON (TRUNK) |
FP-LINK-LOSS (EQPT) |
LO-RXPOWER (GE) |
TIM-P (STSMON) |
UNIT-HIGH-TEMP (EQPT) |
||
GAIN-HDEG (AOTS) |
LO-RXPOWER (ISC) |
VOA-HDEG (AOTS) |
GAIN-LDEG (AOTS) |
LO-RXPOWER (OCN) |
VOA-HDEG (OCH) |
GCC-EOC (TRUNK) |
LO-RXPOWER (TRUNK) |
VOA-HDEG (OMS) |
HELLO (OCN) |
LOS (BITS) |
VOA-HDEG (OTS) |
HELLO (TRUNK) |
LOS-O (OCH) |
VOA-LDEG (AOTS) |
HI-LASERBIAS (2R) |
LOS-O (OMS) |
VOA-LDEG (OCH) |
HI-LASERBIAS (EQPT) |
LOS-O (OTS) |
VOA-LDEG (OMS) |
HI-LASERBIAS (ESCON) |
LO-TXPOWER (2R) |
VOA-LDEG (OTS) |
NA Conditions
Table 1 alphabetically lists Not Alarmed (NA) DWDM conditions.
APC-DISABLED (OCH) |
FORCED-REQ-SPAN (OTS) |
SBYTCC-NEINTCLK (EQPT) |
APC-DISABLED (OMS) |
FORCED-REQ-SPAN (TRUNK) |
SD (TRUNK) |
APC-DISABLED (OTS) |
FRCDSWTOINT (NE-SREF) |
SD-L (OCN) |
APC-DISABLED (SHELF) |
FRNGSYNC (NE-SREF) |
SD-L (OCN) |
APC-END (NE) |
FRCDSWTOPRI (EXT-SREF) |
SD-L (TRUNK) |
APC-WRONG-GAIN (AOTS) |
FRCDSWTOPRI (NE-SREF) |
SD-P (STSMON) |
ALS (2R) |
FRCDSWTOSEC (EXT-SREF) |
SD-P (STSTRM) |
ALS (AOTS) |
FRCDSWTOSEC (NE-SREF) |
SF (TRUNK) |
ALS (ESCON) |
FRCDSWTOTHIRD (EXT-SREF) |
SFBER-EXCEED-HO (VCMON-HP) |
ALS (FC) |
FRCDSWTOTHIRD (NE-SREF) |
SFBER-EXCEED-HO (VCTRM-HP) |
ALS (GE) |
FSTSYNC (NE-SREF) |
SFBER-EXCEED-HO (VCTRM-LP) |
ALS (ISC) |
FTA-MISMATCH (EQPT) |
SF-L (TRUNK) |
ALS (OCN) |
HI-CCVOLT (BITS) |
SF-P (STSMON) |
ALS (TRUNK) |
HLDOVRSYNC (NE-SREF) |
SF-P (STSTRM) |
ALS-DISABLED (EQPT) |
HP-DEG (VCMON-HP) |
SHUTTER-OPEN (OTS) |
APC-DISABLED (AOTS) |
HP-DEG (VCTRM-HP) |
SPAN-NOT-MEASURED (OTS) |
APC-DISABLED (EQPT) |
HP-EXC (VCMON-HP) |
SQUELCHED (2R) |
APC-DISABLED (NE) |
HP-EXC (VCTRM-HP) |
SQUELCHED (ESCON) |
APS-PRIM-FAC (OCN) |
INHSWPR (EQPT) |
SQUELCHED (FC) |
AS-CMD (2R) |
INHSWWKG (EQPT) |
WKSWPR (FC) |
AS-CMD (AOTS) |
INTRUSION-PSWD (NE) |
WKSWPR (GE) |
AS-CMD (BPLANE) |
LAN-POL-REV (NE) |
WKSWPR (ISC) |
AS-CMD (EQPT) |
LASER-APR (AOTS) |
WKSWPR (OTS) |
AS-CMD (ESCON) |
LASER-APR (OTS) |
WTR (2R) |
AS-CMD (FC) |
LMP-UNALLOC (GE) |
WTR (EQPT) |
AS-CMD (GE) |
LOCKOUT-REQ (2R) |
WTR (ESCON) |
AS-CMD (ISC) |
LOCKOUT-REQ (EQPT) |
WTR (FC) |
AS-CMD (NE) |
LOCKOUT-REQ (ESCON) |
WTR (GE) |
AS-CMD (OCH) |
LOCKOUT-REQ (FC) |
WTR (ISC) |
AS-CMD (OCN) |
LOCKOUT-REQ (GE) |
WTR (TRUNK) |
AS-CMD (OMS) |
LOCKOUT-REQ (ISC) |
SSM-LNC (BITS) |
AS-CMD (OTS) |
LOCKOUT-REQ (OCN) |
SSM-LNC (NE-SREF) |
AS-CMD (PPM) |
LOCKOUT-REQ (OTS) |
SSM-LNC (TRUNK) |
AS-CMD (PWR) |
LOCKOUT-REQ (STSMON) |
SSM-OFF (BITS) |
AS-CMD (SHELF) |
LOCKOUT-REQ (TRUNK) |
SSM-OFF (TRUNK) |
AS-CMD (TRUNK) |
LPBKCRS (STSMON) |
SSM-PRC (BITS) |
AS-MT (2R) |
LPBKFACILITY (ESCON) |
SQUELCHED (GE) |
AS-MT (AOTS) |
LPBKFACILITY (FC) |
SQUELCHED (ISC) |
AS-MT (EQPT) |
LPBKFACILITY (GE) |
SQUELCHED (OCN) |
AS-MT (ESCON) |
LPBKFACILITY (ISC) |
SQUELCHED (TRUNK) |
AS-MT (FC) |
LPBKFACILITY (TRUNK) |
SSM-DUS (BITS) |
AS-MT (GE) |
LPBKTERMINAL (ESCON) |
SSM-DUS (TRUNK) |
AS-MT (ISC) |
LPBKTERMINAL (FC) |
SSM-PRC (NE-SREF) |
AS-MT (OCH) |
LPBKTERMINAL (GE) |
SSM-PRC (TRUNK) |
AS-MT (OCN) |
LPBKTERMINAL (ISC) |
SSM-PRS (BITS) |
AS-MT (OMS) |
LPBKTERMINAL (TRUNK) |
SSM-PRS (NE-SREF) |
AS-MT (OTS) |
MAN-REQ (EQPT) |
SSM-PRS (TRUNK) |
AS-MT (PPM) |
MANRESET (EQPT) |
SSM-RES (BITS) |
AS-MT (SHELF) |
MANSWTOINT (NE-SREF) |
SSM-RES (NE-SREF) |
AS-MT (TRUNK) |
MANSWTOPRI (EXT-SREF) |
SSM-RES (TRUNK) |
AS-MT-OOG (STSTRM) |
MANSWTOPRI (NE-SREF) |
SSM-SDH-TN (BITS) |
AUD-LOG-LOSS (NE) |
MANSWTOSEC (EXT-SREF) |
SSM-SDH-TN (NE-SREF) |
AUD-LOG-LOW (NE) |
MANSWTOSEC (NE-SREF) |
SSM-SDH-TN (TRUNK) |
AUTO-SENSE (PPM) |
— |
— |
AUTO-SENSE-DSBLD (PPM) |
— |
— |
AUTOSW-LOP (STSMON) |
MANSWTOTHIRD (EXT-SREF) |
SSM-SETS (BITS) |
AUTOSW-LOP-SNCP (VCMON-HP) |
MANSWTOTHIRD (NE-SREF) |
SSM-SETS (NE-SREF) |
AUTOSW-LOP-SNCP (VCMON-LP) |
MANUAL-REQ-SPAN (2R) |
SSM-SETS (TRUNK) |
AUTOSW-PDI-SNCP (VCMON-HP) |
MANUAL-REQ-SPAN (ESCON) |
SSM-SMC (BITS) |
AUTOSW-PDI (STSMON) |
MANUAL-REQ-SPAN (FC) |
SSM-SMC (NE-SREF) |
AUTOSW-SDBER (STSMON) |
MANUAL-REQ-SPAN (GE) |
SSM-SMC (TRUNK) |
AUTOSW-SFBER (STSMON) |
MANUAL-REQ-SPAN (ISC) |
SSM-ST2 (BITS) |
AUTOSW-SDBER-SNCP (VCMON-HP) |
MANUAL-REQ-SPAN (OCN) |
SSM-ST2 (NE-SREF) |
AUTOSW-SFBER-SNCP (STSMON) |
MANUAL-REQ-SPAN (OTS) |
SSM-ST2 (TRUNK) |
AUTOSW-UNEQ (STSMON) |
MANUAL-REQ-SPAN (TRUNK) |
SSM-ST3 (BITS) |
AUTOSW-UNEQ-SNCP (VCMON-HP) |
MAN-LASER-RESTART (OTS) |
SSM-ST3 (NE-SREF) |
AUTOSW-UNEQ-SNCP (VCMON-LP) |
MAN-LASER-RESTART (AOTS) |
SSM-ST3 (TRUNK) |
AWG-WARM-UP (OTS) |
MS-DEG (STM1E) |
SSM-ST3E (BITS) |
BP-LPBKFACILITY (EQPT) |
— |
— |
BP-LPBKTERMINAL (EQPT) |
— |
— |
CHANLOSS (OCN) |
MS-DEG (STMN) |
SSM-ST3E (NE-SREF) |
CLDRESTART (EQPT) |
MS-EOC (STMN) |
SSM-ST3E (TRUNK) |
CTNEQPT-MISMATCH (EQPT) |
MS-EXC (STM1E) |
SSM-ST4 (BITS) |
EFM-RLBK (GE) |
MS-EXC (STMN) |
SSM-ST4 (NE-SREF) |
ETH-LINKLOSS (NE) |
MT-OCHNC (OTS) |
SSM-ST4 (TRUNK) |
FAILTOSW (2R) |
OCHNC-INC (OCHNC-CONN) |
SSM-STU (BITS) |
FAILTOSW (EQPT) |
OCHTERM-INC (OCH-TERM) |
SSM-STU (NE-SREF) |
FAILTOSW (ESCON) |
ODUK-SD-PM (TRUNK) |
SSM-STU (TRUNK) |
FAILTOSW (GE) |
ODUK-SF-PM (TRUNK) |
SSM-TNC (BITS) |
FAILTOSW (FC) |
OPEN-SLOT (EQPT) |
SSM-TNC (TRUNK) |
FAILTOSW (ISC) |
OSRION (AOTS) |
SW-MISMATCH (EQPT) |
FAILTOSW (OCN) |
OSRION (OTS) |
SWTOPRI (EXT-SREF) |
FAILTOSW (OTS) |
OTUK-SD (TRUNK) |
SWTOPRI (NE-SREF) |
FAILTOSW (TRUNK) |
OTUK-SF (TRUNK) |
SWTOSEC (EXT-SREF) |
FAILTOSW-HO (VCMON-HP) |
OUT-OF-SYNC (ISC) |
SWTOSEC (NE-SREF) |
FAILTOSW-PATH (STSMON) |
PARAM-MISM (AOTS) |
SWTOTHIRD (EXT-SREF) |
FAPS (TRUNK) |
PARAM-MISM (OCH) |
|
FDI (OCH-TERM) |
PARAM-MISM (OCH-TERM) |
TRAIL-SIGNAL-FAIL (OCH) |
FDI (OCH) |
PARAM-MISM (OMS) |
SWTOTHIRD (NE-SREF) |
FE-FRCDWKSWBK-SPAN (OCN) |
PARAM-MISM (OTS) |
SYNC-FREQ (BITS) |
FORCED-REQ (STSMON) |
PDI-P (STSMON) |
SYNC-FREQ (TRUNK) |
FE-FRCDWKSWPR-SPAN (OCN) |
PDI-P (STSTRM) |
TEMP-MISM (NE) |
FE-MANWKSWBK-SPAN (OCN) |
PMI (OMS) |
TRAIL-SIGNAL-FAIL (TRUNK) |
FE-MANWKSWPR-SPAN (OCN) |
PMI (OTS) |
UNC-WORD (TRUNK) |
FORCED-REQ (EQPT) |
PPR-BDI (TRUNK) |
VOLT-MISM (PWR) |
FORCED-REQ (POS) |
PPR-FDI (TRUNK) |
WKSWPR (2R) |
FORCED-REQ-SPAN (2R) |
PPR-MAINT (TRUNK) |
WKSWPR (EQPT) |
FORCED-REQ-SPAN (ESCON) |
PPR-TRIG-EXCD (ETH) |
WKSWPR (ESCON) |
FORCED-REQ-SPAN (FC) |
REP-SEGMENT-FAULT (ETH) |
WKSWPR (FC) |
FORCED-REQ-SPAN (GE) |
REP-SEGMENT-FAULT (GE) |
WKSWPR (GE) |
FORCED-REQ-SPAN (ISC) |
RLS (OTS) |
WKSWPR (ISC) |
FORCED-REQ-SPAN (OCN) |
RUNCFG-SAVENEED (EQPT) |
WKSWPR (OTS) |
NR Conditions
alphabetically lists Not Reported DWDM conditions.
AIS (BITS) |
ERFI-P-SRVR (STSMON) |
ODUK-OCI-PM (TRUNK) |
AIS (TRUNK) |
ERFI-P-SRVR (STSTRM) |
OTUK-AIS (TRUNK) |
AIS-L (OCN) |
HP-RFI (VCMON-HP) |
OTUK-BDI (TRUNK) |
AIS-L (TRUNK) |
MS-AIS (STMN) |
RFI (TRUNK) |
AIS-P (STSMON) |
MS-AIS (STM1E) |
RFI-L (OCN) |
AIS-P (STSTRM) |
MS-RFI (STMN) |
RFI-L (TRUNK) |
AU-AIS (VCTRM-HP) |
MS-RFI (STM1E) |
RFI-P (STSMON) |
AU-AIS (VCMON-HP) |
ODUK-1-AIS-PM (TRUNK) |
RFI-P (STSTRM) |
AUTOSW-AIS (STSMON) |
ODUK-2-AIS-PM (TRUNK) |
TRUNK-ODU-AIS (FC) — |
AUTOSW-AIS-SNCP (VCMON-HP) |
ODUK-3-AIS-PM (TRUNK) |
TRUNK-ODU-AIS (GE) — |
AUTOSW-AIS-SNCP (VCMON-LP) |
ODUK-4-AIS-PM (TRUNK) |
TRUNK-ODU-AIS (OCN) — |
COOL-MISM (FAN) — |
ODUK-AIS-PM (TRUNK) |
TRUNK-ODU-AIS (OTU) — |
ERFI-P-CONN (STSMON) |
ODUK-BDI-PM (TRUNK) |
UNQUAL-PPM |
ERFI-P-CONN (STSTRM) |
ODUK-LCK-PM (TRUNK) |
WVL-DRIFT-CHAN-OFF |
Alarms and Conditions Listed By Alphabetical Entry
Table 1 alphabetically lists all DWDM alarms and conditions.
ACT-SOFT-VERIF-FAIL (EQPT) |
GFP-CSF (GFP-FAC) |
OPWR-LDEG (AOTS) |
AIS (BITS) |
GFP-CSF (ML100T) |
OPWR-LDEG (OCH) |
AIS (TRUNK) |
GFP-CSF (ML1000) |
OPWR-LDEG (OCH-TERM) |
— |
GFP-CSF-SIGLOSS (GFP-FAC) |
— |
— |
GFP-CSF-SYNCLOSS (GFP-FAC) |
— |
AIS-L (OCN) |
GFP-CSF (MLMR) |
OPWR-LDEG (OMS) |
AIS-L (TRUNK) |
GFP-LFD (CE100T) |
OPWR-LDEG (OTS) |
AIS-P (STSMON) |
GFP-LFD (CE1000) |
OPWR-LFAIL (AOTS) |
AIS-P (STSTRM) |
GFP-LFD (CEMR) |
OPWR-LFAIL (OCH) |
ALS (2R) |
GFP-LFD (FCMR) |
OPWR-LFAIL (OCH-TERM) |
ALS (AOTS) |
GFP-LFD (GFP-FAC) |
OPWR-LFAIL (OMS) |
ALS (ESCON) |
GFP-LFD (ML100T) |
OPWR-LFAIL (OTS) |
ALS (FC) |
GFP-LFD (ML1000) |
OSRION (AOTS) |
ALS (GE) |
GFP-LFD (MLMR) |
OSRION (OTS) |
ALS (ISC) |
GFP-LFD (POS) |
OTUK-AIS (TRUNK) |
ALS (OCN) |
GFP-UP-MISMATCH (CE100T) |
OTUK-BDI (TRUNK) |
ALS (TRUNK) |
GFP-UP-MISMATCH (CE1000) |
OTUK-IAE (TRUNK) |
ALS-DISABLED (EQPT) |
GFP-UP-MISMATCH (CEMR) |
OTUK-LOF (TRUNK) |
AMPLI-INIT (AOTS) |
GFP-UP-MISMATCH (FCMR) |
OTUK-SD (TRUNK) |
APC-CORR-SKIPPED (AOTS) |
GFP-UP-MISMATCH (GFP-FAC) |
OTUK-SF (TRUNK) |
APC-CORR-SKIPPED (OCH) |
GFP-UP-MISMATCH (ML100T) |
OTUK-TIM (TRUNK) |
APC-CORR-SKIPPED (OMS) |
GFP-UP-MISMATCH (ML1000) |
OUT-OF-BUNDLE (ETH) |
APC-CORR-SKIPPED (OTS) |
GFP-UP-MISMATCH (MLMR) |
OUT-OF-BUNDLE (CHGRP) |
APC-DISABLED (AOTS) |
GFP-UP-MISMATCH (POS) |
OUT-OF-SYNC (FC) |
APC-DISABLED (EQPT) |
HELLO (TRUNK) |
OUT-OF-SYNC (GE) |
APC-DISABLED (NE) |
HIBATVG (PWR) |
OUT-OF-SYNC (ISC) |
— |
HI-BER2 (DWDM-CLIENT) |
— |
— |
HI-BER2 (DWDM-TRUNK) |
— |
APC-DISABLED (OCH) |
HI-CCVOLT (BITS) |
OUT-OF-SYNC (TRUNK) |
OVER-TEMP-UNIT-PROT) |
||
APC-DISABLED (OMS) |
HI-LASERBIAS (2R) |
PARAM-MISM (AOTS) |
APC-DISABLED (OTS) |
HI-LASERBIAS (EQPT) |
PARAM-MISM (OCH) |
APC-DISABLED (SHELF) |
HI-LASERBIAS (ESCON) |
PARAM-MISM (OCH-TERM) |
APC-END (NE) |
HI-LASERBIAS (FC) |
PARAM-MISM (OMS) |
APC-OUT-OF-RANGE (AOTS) |
HI-LASERBIAS (GE) |
PARAM-MISM (OTS) |
— |
— |
PAYLOAD-UNKNOWN (PPM) |
APC-OUT-OF-RANGE (OCH) |
HI-LASERBIAS (ISC) |
PDI-P (STSMON) |
APC-OUT-OF-RANGE (OMS) |
HI-LASERBIAS (OCN) |
PDI-P (STSTRM) |
— |
— |
PEER-CSF (OCN) |
— |
— |
PEER-CSF (STM) |
APC-OUT-OF-RANGE (OTS) |
HI-LASERBIAS (PPM) |
PEER-NORESPONSE (EQPT) |
APC-WRONG-GAIN (AOTS) |
HI-LASERBIAS (TRUNK) |
PM-TCA |
APS-INV-PRIM (OCN) |
HI-LASERTEMP (EQPT) |
PMD-DEG (TRUNK) |
APS-PRIM-FAC (OCN) |
HI-LASERTEMP (OCN) |
PMI (OMS) |
APS-PRIM-SEC-MISM (OCN) |
HI-LASERTEMP (PPM) |
PMI (OTS) |
— |
— |
PORT-COMM-FAIL (DWDM-CLIENT) |
— |
— |
PORT-COMM-FAIL (DWDM-TRUNK) |
APSB (OCN) |
HI-RXPOWER (2R) |
PPR-BDI (TRUNK) |
APSC-IMP (OCN) |
HI-RXPOWER (ESCON) |
PPR-FDI (TRUNK) |
APSCDFLTK (OCN) |
HI-RXPOWER (FC) |
PPR-MAINT (TRUNK) |
APSCINCON (OCN) |
HI-RXPOWER (GE) |
PPR-TRIG-EXCD (ETH) |
APSCM (OCN) |
HI-RXPOWER (ISC) |
PORT-FAIL (OCH) |
APSCNMIS (OCN) |
HI-RXPOWER (OCN) |
PROT-SOFT-VERIF-FAIL (EQPT) |
APSIMP (OCN) |
HI-RXPOWER (TRUNK) |
PROTNA (EQPT) |
APSMM (OCN) |
HITEMP (EQPT) |
PROV-MISMATCH (PPM) |
AS-CMD (2R) |
HITEMP (NE) |
PROV-MISMATCH (TRUNK) |
AS-CMD (AOTS) |
HI-TXPOWER (2R) |
PTIM (TRUNK) |
AS-CMD (BPLANE) |
HI-TXPOWER (EQPT) |
PWR-FAIL-A (EQPT) |
AS-CMD (EQPT) |
HI-TXPOWER (ESCON) |
PWR-FAIL-B (EQPT) |
AS-CMD (ESCON) |
HI-TXPOWER (FC) |
PWR-FAIL-RET-A (EQPT) |
AS-CMD (FC) |
HI-TXPOWER (GE) |
PWR-FAIL-RET-B (EQPT) |
AS-CMD (GE) |
HI-TXPOWER (ISC) |
PWR-PROT-ON (OTS) |
AS-CMD (ISC) |
HI-TXPOWER (OCN) |
RAMAN-G-NOT-REACHED (OTS) |
AS-CMD (NE) |
HI-TXPOWER (PPM) |
REMOTE-FAULT (ETH) |
AS-CMD (OCH) |
HI-TXPOWER (TRUNK) |
REP-LINK-FLAPPING (ETH) |
AS-CMD (OCN) |
HLDOVRSYNC (NE-SREF) |
REP-NEIHB-ADJ-FAIL (ETH) |
AS-CMD (OMS) |
HP-DEG (VCMON-HP) |
REP-SEGMENT-FAULT (ETH) |
AS-CMD (OTS) |
HP-DEG (VCTRM-HP) |
REP-SEGMENT-FAULT (GE) |
AS-CMD (PPM) |
HP-ENCAP-MISMATCH (VCTRM-HP) |
RFI (TRUNK) |
AS-CMD (PWR) |
HP-EXC (VCMON-HP) |
RFI-L (OCN) |
AS-CMD (SHELF) |
HP-EXC (VCTRM-HP) |
RFI-P (STSMON) |
AS-CMD (TRUNK) |
HP-PLM (VCMON-HP) |
RFI-P (STSTRM) |
AS-MT-OOG (STSTRM) |
HP-PLM (VCTRM-HP) |
RLS (OTS) |
AS-MT (2R) |
HP-RFI (VCMON-HP) |
RMON-ALARM |
AS-MT (AOTS) |
HP-TIM (VCMON-HP) |
RMON-RESET |
AS-MT (EQPT) |
HP-UNEQ (VCMON-HP) |
RING-ID-MIS (OSC-RING) |
AS-MT (ESCON) |
HP-UNEQ (VCTRM-HP) |
RS-EOC (STMN) |
AS-MT (FC) |
I-HITEMP (NE) |
RS-TIM (STMN) |
AS-MT (GE) |
ILK-FAIL (TRUNK) |
RUNCFG-SAVENEED (EQPT) |
AS-MT (ISC) |
IMPROPRMVL (EQPT) |
SBYTCC-NEINTCLK (EQPT) |
AS-MT (OCH) |
IMPROPRMVL (PPM) |
SD (TRUNK) |
AS-MT (OCN) |
INTRUSION-PSWD (NE) |
SD-L (OCN) |
AS-MT (OMS) |
INVMACADR (AIP) |
SD-P (STSMON) |
AS-MT (OTS) |
INHSWPR (EQPT) |
SD-P (STSTRM) |
— |
— |
SEQ_MISMATCH_COUNT |
AS-MT (PPM) |
INHSWWKG (EQPT) |
SF (TRUNK) |
— |
INVALID-MUXCONF (EQPT) |
— |
AS-MT (SHELF) |
ISIS-ADJ-FAIL (OCN) |
SF-L (TRUNK) |
AS-MT (TRUNK) |
ISIS-ADJ-FAIL (TRUNK) |
SF-P (STSMON) |
— |
KEY_EX_FAIL |
— |
— |
KEY_WRITE_FAIL |
— |
AU-AIS (VCTRM-HP) |
LAN-POL-REV (NE) |
SF-P (STSTRM) |
AU-AIS (VCMON-HP) |
LASEREOL (OCN) |
SFBER-EXCEED-HO (VCMON-HP) |
AU-LOP (VCTRM-HP) |
LASER-APR (AOTS) |
SFBER-EXCEED-HO (VCTRM-HP) |
AU-LOP (VCMON-HP) |
LASER-APR (OTS) |
SFBER-EXCEED-HO (VCTRM-LP) |
AUD-LOG-LOSS (NE) |
LASER-OFF-WVL-DRIFT (OCN) |
SFTWDOWN (EQPT) |
— |
SFTWDOWN-FAIL (EQPT) |
|
AUD-LOG-LOW (NE) |
LASER-OFF-WVL-DRIFT (STMN) |
SHELF-COMM-FAIL (SHELF) |
AUTO-SENSE (PPM) |
— |
— |
AUTO-SENSE-DSBLD (PPM) |
— |
— |
AUTORESET (EQPT) |
LASER-OFF-WVL-DRIFT (TRUNK) |
SH-IL-VAR-DEG-HIGH (OTS) |
AUTOLSROFF (OCN) |
LASERBIAS-DEG (AOTS) |
SH-IL-VAR-DEG-LOW (OTS) |
AUTOSW-AIS (STSMON) |
LASERBIAS-DEG (OTS) |
SHUTTER-OPEN (OTS) |
AUTOSW-AIS-SNCP (VCMON-HP) |
LASERBIAS-FAIL (AOTS) |
SIGLOSS (ESCON) |
AUTOSW-AIS-SNCP (VCMON-LP) |
LASERTEMP-DEG (AOTS) |
SIGLOSS (FC) |
— |
LIC-EXPIRING-SHORTLY (EQPT) |
— |
— |
LIC-EXPIRING-SOON (EQPT) |
— |
— |
LIC-MISSING (PORT) |
— |
— |
LICENSE-EXPIRED (EQPT) |
— |
AUTOSW-LOP (STSMON) |
LMP-FAIL (GE) |
SIGLOSS (GE) |
AUTOSW-LOP-SNCP (VCMON-HP) |
LMP-SD (GE) |
SIGLOSS (ISC) |
AUTOSW-LOP-SNCP (VCMON-LP) |
LMP-SF (GE) |
SIGLOSS (TRUNK) |
AUTOSW-PDI (STSMON) |
LMP-UNALLOC (GE) |
SNTP-HOST (NE) |
AUTOSW-PDI-SNCP (VCMON-HP) |
LOCAL-FAULT (ETH) |
SOFT-VERIF-FAIL (EQPT) |
AUTOSW-SDBER (STSMON) |
LOCKOUT-REQ (2R) |
SPANLEN-OUT-OF-RANGE (OTS) |
AUTOSW-SDBER-SNCP (VCMON-HP) |
LOCKOUT-REQ (EQPT) |
SPAN-NOT-MEASURED (OTS) |
AUTOSW-SFBER (STSMON) |
LOCKOUT-REQ (ESCON) |
SQUELCHED (2R) |
AUTOSW-SFBER-SNCP (STSMON) |
LOCKOUT-REQ (FC) |
SQUELCHED (ESCON) |
AUTOSW-UNEQ (STSMON) |
LOCKOUT-REQ (GE) |
SQUELCHED (FC) |
AUTOSW-UNEQ-SNCP (VCMON-HP) |
LOCKOUT-REQ (ISC) |
SQUELCHED (GE) |
AUTOSW-UNEQ-SNCP (VCMON-LP) |
LOCKOUT-REQ (OTS) |
SQUELCHED (ISC) |
AWG-DEG (OTS) |
LOCKOUT-REQ (TRUNK) |
SQUELCHED (OCN) |
AWG-FAIL (OTS) |
LOF (BITS) |
SQUELCHED (TRUNK) |
AWG-OVERTEMP (OTS) |
LOF (TRUNK) |
SSM-DUS (BITS) |
AWG-WARM-UP (OTS) |
LO-LASERBIAS (EQPT) |
SSM-DUS (TRUNK) |
BAT-FAIL (PWR) |
LO-LASERBIAS (OCN) |
SSM-FAIL (BITS) |
BKUPMEMP (EQPT) |
LO-LASERBIAS (PPM) |
SSM-FAIL (TRUNK) |
BP-LPBKFACILITY (EQPT) |
— |
— |
BP-LPBKTERMINAL (EQPT) |
— |
— |
BPV (BITS) |
LO-LASERTEMP (EQPT) |
SSM-LNC (BITS) |
CARLOSS (EQPT) |
LO-LASERTEMP (OCN) |
SSM-LNC (NE-SREF) |
CARLOSS (FC) |
LO-LASERTEMP (PPM) |
SSM-LNC (TRUNK) |
CARLOSS (GE) |
LOM (TRUNK) |
SSM-OFF (BITS) |
CARLOSS (ISC) |
LOP-P (TRUNK) |
SSM-OFF (TRUNK) |
CARLOSS (TRUNK) |
LOP-P (OCH) |
SSM-PRC (BITS) |
CASETEMP-DEG (AOTS) |
LOP-P (OMS) |
SSM-PRC (NE-SREF) |
CD (TRUNK) |
LOP-P (OTS) |
SSM-PRC (TRUNK) |
CHANLOSS (OCN) |
LO-RXPOWER (2R) |
SSM-PRS (BITS) |
CFM-CONFIG-ERROR (ETH) |
LO-RXPOWER (ESCON) |
SSM-PRS (NE-SREF) |
CFM-LOOP (ETH) |
LO-RXPOWER (FC) |
SSM-PRS (TRUNK) |
CFM-MEP-DOWN (ETH) |
LO-RXPOWER (GE) |
SSM-RES (BITS) |
CFM-XCON-SERVICE (ETH) |
LO-RXPOWER (ISC) |
SSM-RES (NE-SREF) |
CLDRESTART (EQPT) |
LO-RXPOWER (OCN) |
SSM-RES (TRUNK) |
COMP-CARD-MISSING (EQPT) |
— |
— |
CONTBUS-DISABLED (EQPT) |
LO-RXPOWER (TRUNK) |
SSM-SDH-TN (BITS) |
CONTBUS-IO-A (CONTBUS-A) (EQPT) |
LOS (2R) |
SSM-SDH-TN (NE-SREF) |
CONTBUS-IO-B (CONTBUS-B) (EQPT) |
LOS (BITS) |
SSM-SDH-TN (TRUNK) |
COOL-MISM (FAN) |
— |
— |
CTNEQPT-MISMATCH (EQPT) |
LOS (ESCON) |
SSM-SETS (BITS) |
DATA-CRC (OCH) |
LOS (ISC) |
SSM-SETS (NE-SREF) |
DATAFLT (NE) |
LOS (OTS) |
|
DBOSYNC (NE) |
LOS (TRUNK) |
SSM-SETS (TRUNK) |
DCU-LOSS-FAIL (OTS) |
— |
SSM-SMC (BITS) |
DSP-COMM-FAIL (TRUNK) |
LOS-O (OCH) |
SSM-SMC (NE-SREF) |
DSP-FAIL (TRUNK) |
LOS-O (OMS) |
SSM-SMC (TRUNK) |
DUP-IPADDR (NE) |
LOS-O (OTS) |
SSM-ST2 (BITS) |
DUP-NODENAME (NE) |
LOS-P (OCH) |
SSM-ST2 (NE-SREF) |
DUP-SHELF-ID (SHELF) |
LOS-P (OMS) |
SSM-ST2 (TRUNK) |
EFM-PEER-MISSING (GE) |
LOS-P (OTS) |
SSM-ST3 (BITS) |
EFM-RFI-DG (GE) |
LOS-P (TRUNK) |
SSM-ST3 (NE-SREF) |
EFM-RLBK (GE) |
LOS-RAMAN (OTS) |
SSM-ST3 (TRUNK) |
EHIBATVG (PWR) |
LO-TXPOWER (2R) |
SSM-ST3E (BITS) |
ELWBATVG (PWR) |
LO-TXPOWER (EQPT) |
SSM-ST3E (NE-SREF) |
ENCAP-MISMATCH-P (STSTRM) |
LO-TXPOWER (ESCON) |
SSM-ST3E (TRUNK) |
ENCAP-MISMATCH-P (POS) |
LO-TXPOWER (FC) |
SSM-ST4 (BITS) |
EOC (OCN) |
LO-TXPOWER (GE) |
SSM-ST4 (NE-SREF) |
EOC (TRUNK) |
LO-TXPOWER (ISC) |
SSM-ST4 (TRUNK) |
EOC-E (OCN) |
LO-TXPOWER (OCN) |
SSM-STU (BITS) |
EOC-E (TRUNK) |
LO-TXPOWER (PPM) |
SSM-STU (NE-SREF) |
EOC-E (FE) |
LO-TXPOWER (TRUNK) |
SSM-STU (TRUNK) |
EOC-E (GE) |
LPBKCRS (STSMON) |
SSM-TNC (BITS) |
EOC-L (OCN) |
LPBKFACILITY (ESCON) |
SSM-TNC (NE-SREF) |
EOC-L (TRUNK) |
LPBKFACILITY (FC) |
SSM-TNC (TRUNK) |
ERFI-P-CONN (STSMON) |
LPBKFACILITY (GE) |
SW-MISMATCH (EQPT) |
ERFI-P-CONN (STSTRM) |
LPBKFACILITY (ISC) |
SWTOPRI (EXT-SREF) |
ERFI-P-SRVR (STSMON) |
LPBKFACILITY (TRUNK) |
SWTOPRI (NE-SREF) |
ERFI-P-SRVR (STSTRM) |
LPBKTERMINAL (ESCON) |
SWTOSEC (EXT-SREF) |
EQPT (AICI-AEP) |
LPBKTERMINAL (FC) |
SWTOSEC (NE-SREF) |
EQPT (AICI-AIE) |
LPBKTERMINAL (GE) |
SWTOTHIRD (EXT-SREF) |
EQPT (EQPT) |
LPBKTERMINAL (ISC) |
SWTOTHIRD (NE-SREF) |
EQPT (PPM) |
LPBKTERMINAL (TRUNK) |
SYNC-FREQ (BITS) |
EQPT-DEGRADE (EQPT) |
LWBATVG (PWR) |
SYNC-FREQ (TRUNK) |
EQPT-DIAG (EQPT) |
MAN-REQ (EQPT) |
SYNCLOSS (FC) |
EQPT-FAIL (EQPT) |
— |
— |
EQPT-MISS (FAN) |
MANRESET (EQPT) |
SYNCLOSS (GE) |
ESMC-FAIL (GE) |
— |
— |
ESMC-FAIL (TRUNK) |
— |
— |
ETH-LINKLOSS (NE) |
MANSWTOINT (NE-SREF) |
SYNCLOSS (ISC) |
EVAL-LIC (EQPT) |
— |
— |
EXC-BP (OTS) |
MANSWTOPRI (EXT-SREF) |
SYNCLOSS (TRUNK) |
EXCCOL (EQPT) |
MANSWTOPRI (NE-SREF) |
SYNCPRI (EXT-SREF) |
EXT (ENVALRM) |
MANSWTOSEC (EXT-SREF) |
SYNCPRI (NE-SREF) |
FAILTOSW (2R) |
MANSWTOSEC (NE-SREF) |
SYNCSEC (EXT-SREF) |
FAILTOSW (EQPT) |
MANSWTOTHIRD (EXT-SREF) |
SYNCSEC (NE-SREF) |
FAILTOSW (ESCON) |
MANSWTOTHIRD (NE-SREF) |
SYNCTHIRD (EXT-SREF) |
FAILTOSW (FC) |
MAN-LASER-RESTART (OTS) |
SYNCTHIRD (NE-SREF) |
FAILTOSW (GE) |
MAN-LASER-RESTART (AOTS) |
SYSBOOT (NE) |
— |
— |
TEMP-LIC (EQPT) |
FAILTOSW (ISC) |
MANUAL-REQ-SPAN (2R) |
TEMP-MISM (NE) |
FAILTOSW (OCN) |
MANUAL-REQ-SPAN (ESCON) |
TIM (TRUNK) |
FAILTOSW (OTS) |
MANUAL-REQ-SPAN (FC) |
TIM-MON (TRUNK) |
FAILTOSW (TRUNK) |
MANUAL-REQ-SPAN (GE) |
TIM-P (TRUNK) |
FAILTOSW-HO (STSMON) |
MANUAL-REQ-SPAN (ISC) |
TIM-S (TRUNK) |
FAILTOSW-PATH (STSMON) |
MANUAL-REQ-SPAN (OCN) |
TRAIL-SIGNAL-FAIL (OCH) |
FAN (FAN) |
MANUAL-REQ-SPAN (OTS) |
TRAIL-SIGNAL-FAIL (TRUNK) |
— |
— |
TRUNK-ODU-AIS (FC) |
— |
— |
TRUNK-ODU-AIS (GE) |
— |
— |
TRUNK-ODU-AIS (OCN) |
— |
— |
TRUNK-ODU-AIS (OTU) |
— |
— |
TRUNK-PAYLOAD-MISM (FC) |
— |
— |
TRUNK-PAYLOAD-MISM (GE) |
— |
— |
TRUNK-PAYLOAD-MISM (OCN) |
— |
— |
TRUNK-PAYLOAD-MISM (OTU) |
FAPS (TRUNK) |
MANUAL-REQ-SPAN (TRUNK) |
TX-OFF-NON-CISCO-PPM (PPM) |
FAPS-CONFIG-MISMATCH (EQPT) |
MANWKSWBK-NO-TRFSW (OCN) |
UNC-WORD (TRUNK) |
FC-NO-CREDITS (FC) |
MANWKSWPR-NO-TRFSW (OCN) |
UNEQ-P (STSMON, STSTRM) |
UNIT-HIGH-TEMP |
||
FC-NO-CREDITS (TRUNK) |
MEA (AIP) |
UNQUAL-PPM (PPM) |
FDI (OCH) |
MEA (EQPT) |
USBSYNC (USB) |
FDI (OCH-TERM) |
MEA (FAN) |
USB-WRITE-FAIL (USB) |
FE-FRCDWKSWBK-SPAN (OCN) |
MEA (PPM) |
UT-COMM-FAIL (TRUNK) |
FE-FRCDWKSWPR-SPAN (OCN) |
MEA (SHELF) |
UT-FAIL (TRUNK) |
FE-MANWKSWBK-SPAN (OCN) |
MEM-GONE (EQPT) |
VOA-DISABLED (EQPT) |
FE-MANWKSWPR-SPAN (OCN) |
MEM-LOW (EQPT) |
VOA-HDEG (AOTS) |
FEC-MISM (TRUNK) |
MFGMEM (AICI-AEP) |
VOA-HDEG (OCH) |
FEPRLF (OCN) |
MFGMEM (AICI-AIE) |
VOA-HDEG (OMS) |
FIBERTEMP-DEG (AOTS) |
MFGMEM (AIP) |
VOA-HDEG (OTS) |
FIPS_TEST_FAILED |
— |
— |
FORCED-REQ (EQPT) |
MFGMEM (BPLANE) |
VOA-HFAIL (AOTS) |
FORCED-REQ (STSMON) |
MFGMEM (FAN) |
VOA-HFAIL (OCH) |
FORCED-REQ (POS) |
MFGMEM (PPM) |
VOA-HFAIL (OMS) |
FORCED-REQ-SPAN (2R) |
MS-AIS (STMN) |
VOA-HFAIL (OTS) |
FORCED-REQ-SPAN (ESCON) |
MS-AIS (STM1E) |
VOA-LDEG (AOTS) |
FORCED-REQ-SPAN (FC) |
MS-DEG (STMN) |
VOA-LDEG (OCH) |
FORCED-REQ-SPAN (GE) |
MS-DEG (STM1E) |
VOA-LDEG (OMS) |
FORCED-REQ-SPAN (ISC) |
MS-EOC (STMN) |
VOA-LDEG (OTS) |
FORCED-REQ-SPAN (OCN) |
MS-EXC (STMN) |
VOA-LFAIL (AOTS) |
FORCED-REQ-SPAN (OTS) |
MS-EXC (STM1E) |
VOA-LFAIL (OCH) |
FORCED-REQ-SPAN (TRUNK) |
MS-RFI (STMN) |
VOA-LFAIL (OMS) |
FP-LINK-LOSS (EQPT) |
MS-RFI (STM1E) |
VOA-LFAIL (OTS) |
FRCDSWTOINT (NE-SREF) |
MT-OCHNC (OTS) |
VOLT-MISM (PWR) |
FRCDSWTOPRI (EXT-SREF) |
NON-CISCO-PPM (PPM) |
WKSWBK (EQPT) |
FRCDSWTOPRI (NE-SREF) |
OCHNC-INC (OCHNC-CONN) |
WKSWBK (OCN) |
FRCDSWTOSEC (EXT-SREF) |
OCHTERM-INC (OCH-TERM) |
WKSWBK (OTS) |
FRCDSWTOSEC (NE-SREF) |
ODUK-1-AIS-PM (TRUNK) |
WKSWPR (2R) |
FRCDSWTOTHIRD (EXT-SREF) |
ODUK-2-AIS-PM (TRUNK) |
WKSWPR (EQPT) |
FRCDSWTOTHIRD (NE-SREF) |
ODUK-3-AIS-PM (TRUNK) |
WKSWPR (ESCON) |
FRCDWKSWBK-NO-TRFSW (OCN) |
ODUK-4-AIS-PM (TRUNK) |
WKSWPR (FC) |
FRCDWKSWPR-NO-TRFSW (OCN) |
ODUK-AIS-PM (TRUNK) |
WKSWPR (GE) |
FRNGSYNC (NE-SREF) |
ODUK-BDI-PM (TRUNK) |
WKSWPR (ISC) |
FSTSYNC (NE-SREF) |
ODUK-LCK-PM (TRUNK) |
WKSWPR (OTS) |
FTA-MISMATCH (EQPT) |
ODUK-OCI-PM (TRUNK) |
WORK-QUEUE-FULL (EQPT) |
GAIN-HDEG (AOTS) |
ODUK-SD-PM (TRUNK) |
WTR (2R) |
GAIN-HFAIL (AOTS) |
ODUK-SF-PM (TRUNK) |
WTR (EQPT) |
GAIN-LDEG (AOTS) |
ODUK-TIM-PM (TRUNK) |
WTR (ESCON) |
GAIN-LFAIL (AOTS) |
OPEN-SLOT (EQPT) |
WTR (FC) |
GCC-EOC (TRUNK) |
OPWR-HDEG (AOTS) |
WTR (GE) |
GE-OOSYNC (FC) |
OPWR-HDEG (OCH) |
WTR (ISC) |
GE-OOSYNC (GE) |
OPWR-HDEG (OCH-TERM) |
WTR (TRUNK) |
GE-OOSYNC (ISC) |
OPWR-HDEG (OMS) |
WAN-SYNCLOSS (STSMON) |
GE-OOSYNC (TRUNK) |
OPWR-HDEG (OTS) |
WAN-SYNCLOSS (STSTRM) |
GFP-CSF (CE100T) |
OPWR-HFAIL (AOTS) |
WAN-SYNCLOSS (VCMON-HP) |
GFP-CSF (CE1000) |
OPWR-HFAIL (OCH) |
WAN-SYNCLOSS (VCTRM-HP) |
GFP-CSF (CEMR) |
OPWR-HFAIL (OMS) |
WVL-DRIFT-CHAN-OFF (OCH) |
GFP-CSF (FCMR) |
SOFT-VERIF-FAIL (EQPT) |
USBSYNC (USB) |
ACT-SOFT-VERIF-FAIL (EQPT) |
EFM-RFI-CE (GE) |
USB-WRITE-FAIL (USB) |
PROT-SOFT-VERIF-FAIL (EQPT) |
OPWR-HFAIL (OTS) |
EFM-RFI-LF (GE) |
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 or ITU-T G.709 optical overhead bits. One alarm can appear in multiple entries. It can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (OC-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both OCN: LOS and OTN: LOS appear in the list (as well as the other objects).
Alarm profile list objects are defined in Table 1.
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. |
Alarm Logical Objects
Table 1 lists all logical alarm objects used in this chapter.
Logical Object |
Definition |
|---|---|
2R |
Reshape and retransmit (used for transponder [TXP] cards). |
AICI-AEP |
Alarm Interface ControllerInternational/alarm expansion panel. A combination term that refers to this platform AIC-I card. |
AICI-AIE |
Alarm Interface Controller-International/Alarm Interface Extension. A combination term that refers to this platform's AIC-I card. |
AIP |
Alarm Interface Panel. |
AOTS |
Amplified optical transport section. |
BITS |
Building integrated timing supply incoming references (BITS-1, BITS-2). |
BPLANE |
The backplane. |
ENVALRM |
An environmental alarm port. |
EQPT |
A card, its physical objects, and its logical objects as they are located in any of the eight noncommon card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signals (STS), and virtual tributaries (VT). |
ESCON |
Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G. |
EXT-SREF |
BITS outgoing references (SYNC-BITS1, SYNC-BITS2). |
FAN |
Fan-tray assembly. |
FC |
Fibre channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, GE_XP, 10GE_XP, ADM-10G, and OTU2_XP. |
GE |
Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10G, TXP_MR_10E,TXP_MR_10E_C, TXP_MR_10E_L, MXP_MR_10DME_C, MXP_MR_10DME_L, GE-XP, 10GE-XP, ADM-10G, and OTU2_XP. |
ISC |
Inter-service channel, referring to TXPP_MR_2.5G or TXP_MR_2.5G cards. |
NE |
The entire network element. |
NE-SREF |
The timing status of the NE. |
OCH |
The optical channel, referring to dense wavelength division multiplexing (DWDM) cards. |
OCH-TERM |
The optical channel termination node, referring to DWDM cards. |
OCHNC-CONN |
The optical channel network connection, referring to DWDM cards. |
OMS |
Optical multiplex section. |
OSC-RING |
Optical service channel ring. |
OTS |
Optical transport section. |
PPM |
Pluggable port module (PPM, also called SFP), referring to MXP and TXP cards. |
PWR |
Power equipment. |
SHELF |
The shelf assembly. |
TRUNK |
The optical or DWDM card carrying the high-speed signal; referring to MXP or TXP cards. |
Alarm List by Logical Object Type
Lists all the alarms and logical objects as they are given in the system alarm profile. The list entries are organized by logical object name and then by alarm or condition name. Where appropriate, the alarm entries also contain troubleshooting procedures.
Note |
In a mixed network containing different types of nodes (for example, ONS 15310-CL, ONS 15454, and ONS 15600), the initially displayed alarm list in the node view (single-shelf mode) or shelf view (multishelf mode) Provisioning > Alarm Profiles tabs > Alarm Profile Editor tab lists all conditions that are applicable to all nodes in the network. However, when you load the default severity profile from a node, only applicable alarms will display severity levels. Nonapplicable alarms can display use default or unset. |
Note |
In some cases this list does not follow alphabetical order, but it does reflect the order shown in CTC. |
2R: ALS (NA) |
GE: LMP-FAIL (MN) |
OTS: WKSWBK (NA) |
2R: AS-CMD (NA) |
GE: LMP-SD (MN) |
OTS: WKSWPR (NA) |
— |
— |
OTU: TRUNK-ODU-AIS (NR) |
— |
— |
OTU: TRUNK-PAYLOAD-MISM (MJ) |
— |
— |
OTU-TRUNK: KEY-EX-FAIL (MJ) |
— |
— |
OTU-TRUNK: KEY-WRITE-FAIL (MJ) |
— |
— |
OTU-TRUNK: SEQ-MISMATCH-COUNT (MN) |
— |
— |
PORT: LIC-MISSING (CR) |
2R: AS-MT (NA) |
GE: LMP-SF (MN) |
POS: ENCAP-MISMATCH-P (CR) |
2R: FAILTOSW (NA) |
GE: LMP-UNALLOC (NA) |
POS: FORCED-REQ (NA) |
2R: FORCED-REQ-SPAN (NA) |
GE: LO-RXPOWER (MN) |
POS: GFP-CSF (MJ) |
2R: HI-LASERBIAS (MN) |
GE: LO-TXPOWER (MN) |
POS: GFP-LFD (MJ) |
2R: HI-RXPOWER (MN) |
GE: LOCKOUT-REQ (NA) |
PPM: AS-CMD (NA) |
2R: HI-TXPOWER (MN) |
GE: LPBKFACILITY (NA) |
PPM: AS-MT (NA) |
— |
— |
PPM: AUTO-SENSE (NA) |
— |
— |
PPM: AUTO-SENSE-DSBLD (NA) |
2R: LO-RXPOWER (MN) |
GE: LPBKTERMINAL (NA) |
PPM: EQPT (CR) |
2R: LO-TXPOWER (MN) |
GE: MANUAL-REQ-SPAN (NA) |
PPM: HI-LASERBIAS (MN) |
2R: LOCKOUT-REQ (NA) |
GE: OUT-OF-SYNC (MJ) |
PPM: HI-LASERTEMP (MN) |
2R: LOS (CR) |
GE: SIGLOSS (MJ) |
PPM: HI-TXPOWER (MN) |
2R: MANUAL-REQ-SPAN (NA) |
GE: SQUELCHED (NA) |
PPM: IMPROPRMVL (CR) |
2R: SQUELCHED (NA) |
GE: SYNCLOSS (MJ) |
PPM: LO-LASERBIAS (MN) |
— |
GE: TRUNK-ODU-AIS (NR) |
— |
— |
GE: TRUNK-PAYLOAD-MISM (MJ) |
— |
2R: WKSWPR (NA) |
GE: WKSWPR (NA) |
PPM: LO-LASERTEMP (MN) |
2R: WTR (NA) |
GE: WTR (NA) |
PPM: LO-TXPOWER (MN) |
AICI-AEP: EQPT (CR) |
GFP-FAC: GFP-CSF (MJ) |
PPM: MEA (CR) |
AICI-AEP: MFGMEM (CR) |
GFP-FAC: GFP-LFD (MJ) |
PPM: MFGMEM (CR) |
AICI-AIE: EQPT (CR) |
GFP-FAC: GFP-UP-MISMATCH (MJ) |
PPM: NON-CISCO-PPM (MN) |
— |
GFP-FAC: GFP-CSF-SIGLOSS (MJ) |
PPM: PAYLOAD-UNKNOWN (NA) |
— |
GFP-FAC: GFP-CSF-SYNCLOSS (MJ) |
— |
AICI-AIE: MFGMEM (CR) |
ISC: ALS (NA) |
PPM: PROV-MISMATCH (MN) |
AIP: INVMACADR (MJ) |
ISC: AS-CMD (NA) |
PPM: TX-OFF-NON-CISCO-PPM (MJ) |
AIP: MEA (CR) |
ISC: AS-MT (NA) |
PPM: UNQUAL-PPM (NR) |
AIP: MFGMEM (CR) |
ISC: CARLOSS (MJ) |
PWR: AS-CMD (NA) |
AOTS: ALS (NA) |
ISC: FAILTOSW (NA) |
PWR: BAT-FAIL (MJ) |
AOTS: AMPLI-INIT (NA) |
ISC: FORCED-REQ-SPAN (NA) |
PWR: EHIBATVG (MJ) |
AOTS: APC-CORR-SKIPPED (MN) |
ISC: GE-OOSYNC (CR) |
PWR: ELWBATVG (MJ) |
AOTS: APC-DISABLED (MN) |
ISC: HI-LASERBIAS (MN) |
PWR: HIBATVG (MJ) |
AOTS: APC-OUT-OF-RANGE (MN) |
ISC: HI-RXPOWER (MN) |
PWR: LWBATVG (MJ) |
AOTS: APC-WRONG-GAIN (NA) |
ISC: HI-TXPOWER (MN) |
PWR: VOLT-MISM (NA) |
AOTS: AS-CMD (NA) |
ISC: LO-RXPOWER (MN) |
SHELF: APC-DISABLED (MN) |
AOTS: AS-MT (NA) |
ISC: LO-TXPOWER (MN) |
SHELF: AS-CMD (NA) |
AOTS: CASETEMP-DEG (MN) |
ISC: LOCKOUT-REQ (NA) |
SHELF: AS-MT (NA) |
AOTS: FIBERTEMP-DEG (MN) |
ISC: LOS (CR) |
SHELF: DUP-SHELF-ID (MJ) |
AOTS: GAIN-HDEG (MN) |
ISC: LPBKFACILITY (NA) |
SHELF: MEA (MJ) |
AOTS: GAIN-HFAIL (CR) |
ISC: LPBKTERMINAL (NA) |
SHELF: SHELF-COMM-FAIL (MJ) |
AOTS: GAIN-LDEG (MN) |
ISC: MANUAL-REQ-SPAN (NA) |
STM1E: MS-AIS (NR) |
AOTS: GAIN-LFAIL (CR) |
ISC: OUT-OF-SYNC (NA) |
STM1E: MS-DEG (NA) |
AOTS: LASER-APR (NA) |
ISC: SIGLOSS (MJ) |
STM1E: MS-EXC (NA) |
AOTS: LASERBIAS-DEG (MN) |
ISC: SQUELCHED (NA) |
STM1E: MS-RFI (NR) |
AOTS: LASERBIAS-FAIL (MJ) |
ISC: SYNCLOSS (MJ) |
STM1E: SD-L (NA) |
AOTS: LASERTEMP-DEG (MN) |
ISC: WKSWPR (NA) |
STM1E: SF-L (NA) |
AOTS: MAN-LASER-RESTART (NA) |
ISC: WTR (NA) |
STMN: APSB (MN) |
AOTS: OPWR-HDEG (MN) |
ML100T: GFP-CSF (MJ) |
STMN: APSC-IMP (MN) |
AOTS: OPWR-HFAIL (CR) |
ML100T: GFP-LFD (MJ) |
STMN: APSCDFLTK (MN) |
AOTS: OPWR-LDEG (MN) |
ML100T: GFP-UP-MISMATCH (MJ) |
STMN: APSCINCON (MN) |
AOTS: OPWR-LFAIL (CR) |
ML1000: GFP-CSF (MJ) |
STMN: APSCM (MN) |
AOTS: OSRION (NA) |
ML1000: GFP-LFD (MJ) |
STMN: APSCNMIS (MJ) |
AOTS: PARAM-MISM (NA) |
ML1000: GFP-UP-MISMATCH (MJ) |
STMN: APSMM (MN) |
AOTS: VOA-HDEG (MN) |
MLMR: GFP-CSF (MJ) |
STMN: AUTOLSROFF (CR) |
AOTS: VOA-HFAIL (CR) |
MLMR: GFP-LFD (MJ) |
STMN: FE-FRCDWKSWBK-SPAN (NA) |
AOTS: VOA-LDEG (MN) |
MLMR: GFP-UP-MISMATCH (MJ) |
STMN: FE-FRCDWKSWPR-SPAN (NA) |
AOTS: VOA-LFAIL (CR) |
NE-SREF: FRCDSWTOINT (NA) |
STMN: FE-MANWKSWBK-SPAN (NA) |
BITS: AIS (NR) |
NE-SREF: FRCDSWTOPRI (NA) |
STMN: FE-MANWKSWPR-SPAN (NA) |
BITS: BPV (MN) |
NE-SREF: FRCDSWTOSEC (NA) |
STMN: FEPRLF (MN) |
BITS: HI-CCVOLT (NA) |
NE-SREF: FRCDSWTOTHIRD (NA) |
STMN: HELLO (MN) |
BITS: LOF (MN) |
NE-SREF: FRNGSYNC (NA) |
STMN: ISIS-ADJ-FAIL (MN) |
BITS: LOS (MN) |
NE-SREF: FSTSYNC (NA) |
STMN: LASER-OFF-WVL-DRIFT (MJ) |
BITS: SSM-DUS (NA) |
NE-SREF: HLDOVRSYNC (NA) |
STMN: LASEREOL (MN) |
BITS: SSM-FAIL (MN) |
NE-SREF: MANSWTOINT (NA) |
STMN: LOCKOUT-REQ (NA) |
BITS: SSM-LNC (NA) |
NE-SREF: MANSWTOPRI (NA) |
STMN: MANWKSWBK-NO-TRFSW (NA) |
BITS: SSM-OFF (NA) |
NE-SREF: MANSWTOSEC (NA) |
STMN: MANWKSWPR-NO-TRFSW (NA) |
BITS: SSM-PRC (NA) |
NE-SREF: MANSWTOTHIRD (NA) |
STMN: MS-AIS (NR) |
BITS: SSM-PRS (NA) |
NE-SREF: SSM-LNC (NA) |
STMN: MS-DEG (NA) |
BITS: SSM-RES (NA) |
NE-SREF: SSM-PRC (NA) |
STMN: MS-EOC (MN) |
BITS: SSM-SDH-TN (NA) |
NE-SREF: SSM-PRS (NA) |
STMN: MS-EXC (NA) |
BITS: SSM-SETS (NA) |
NE-SREF: SSM-RES (NA) |
STMN: MS-RFI (NR) |
BITS: SSM-SMC (NA) |
NE-SREF: SSM-SDH-TN (NA) |
STMN: RS-EOC |
BITS: SSM-ST2 (NA) |
NE-SREF: SSM-SETS (NA) |
STMN: RS-TIM |
BITS: SSM-ST3 (NA) |
NE-SREF: SSM-SMC (NA) |
STSMON: AIS-P (NR) |
BITS: SSM-ST3E (NA) |
NE-SREF: SSM-ST2 (NA) |
STSMON: AUTOSW-AIS (NR) |
BITS: SSM-ST4 (NA) |
NE-SREF: SSM-ST3 (NA) |
STSMON: AUTOSW-LOP (NA) |
BITS: SSM-STU (NA) |
NE-SREF: SSM-ST3E (NA) |
STSMON: AUTOSW-PDI (NA) |
BITS: SSM-TNC (NA) |
NE-SREF: SSM-ST4 (NA) |
STSMON: AUTOSW-SDBER (NA) |
BITS: SYNC-FREQ (NA) |
NE-SREF: SSM-STU (NA) |
STSMON: AUTOSW-SFBER (NA) |
BPLANE: AS-CMD (NA) |
NE-SREF: SSM-TNC (NA) |
STSMON: AUTOSW-UNEQ (NA) |
BPLANE: MFGMEM (CR) |
NE-SREF: SWTOPRI (NA) |
STSMON: ERFI-P-CONN (NR) |
CE100T: GFP-CSF (MJ) |
NE-SREF: SWTOSEC (NA) |
STSMON: ERFI-P-SRVR (NR) |
CE100T: GFP-LFD (MJ) |
NE-SREF: SWTOTHIRD (NA) |
STSMON: FAILTOSW-PATH (NA) |
CE100T: GFP-UP-MISMATCH (MJ) |
NE-SREF: SYNCPRI (MJ) |
STSMON: FORCED-REQ (NA) |
CE1000: GFP-CSF (MJ) |
NE-SREF: SYNCSEC (MN) |
STSMON: LOCKOUT-REQ (NA) |
CE1000: GFP-LFD (MJ) |
NE-SREF: SYNCTHIRD (MN) |
STSMON: LOP-P (CR) |
CE1000: GFP-UP-MISMATCH (MJ) |
NE: APC-DISABLED (MN) |
STSMON: LPBKCRS (NA) |
CEMR: GFP-CSF (MJ) |
NE: APC-END (NA) |
STSMON: PDI-P (NA) |
CEMR: GFP-LFD (MJ) |
NE: AS-CMD (NA) |
STSMON: RFI-P (NA) |
CEMR: GFP-UP-MISMATCH (MJ) |
NE: AUD-LOG-LOSS (NA) |
STSMON: SD-P (NA) |
DWDM-CLIENT: HI-BER3 (MJ) |
— |
— |
DWDM-CLIENT: PORT-COMM-FAIL (CR) |
— |
— |
DWDM-TRUNK: HI-BER3 (MJ) |
— |
— |
DWDM-TRUNK: PORT-COMM-FAIL (CR) |
— |
— |
ENVALRM: EXT (MN) |
NE: AUD-LOG-LOW (NA) |
STSMON: SF-P (NA) |
EQPT: ACT-SOFT-VERIF-FAIL (CR) |
NE: DATAFLT (MN) |
STSMON: TIM-P (NA) |
EQPT: ALS-DISABLED (NA) |
NE: DBOSYNC (MJ) |
STSMON: UNEQ-P (CR) |
EQPT: APC-DISABLED (MN) |
NE: DUP-IPADDR (MN) |
STSMON: WAN-SYNCLOSS (MJ) |
EQPT: AS-CMD (NA) |
NE: DUP-NODENAME (MN) |
STSTRM: AIS-P (NR) |
EQPT: AS-MT (NA) |
NE: ETH-LINKLOSS (NA) |
STSTRM: AS-MT-OOG (NA) |
EQPT: AUTORESET (MN) |
NE: HITEMP (CR) |
STSTRM: ENCAP-MISMATCH-P (CR) |
EQPT: BKUPMEMP (CR) |
NE: I-HITEMP (CR) |
STSTRM: ERFI-P-CONN (NR) |
EQPT: BP-LPBKFACILITY (NA) |
— |
— |
EQPT: BP-LPBKTERMINAL (NA) |
— |
— |
EQPT: CARLOSS (MJ) |
NE: INTRUSION-PSWD (NA) |
STSTRM: ERFI-P-SRVR (NR) |
EQPT: CLDRESTART (NA) |
NE: LAN-POL-REV (NA) |
STSTRM: LOP-P (CR) |
EQPT: COMP-CARD-MISSING (MN) |
— |
— |
EQPT: CONTBUS-DISABLED (CR) |
NE: SNTP-HOST (MN) |
STSTRM: PDI-P (NA) |
EQPT: CONTBUS-IO-A (CONTBUS-A) (MN) |
NE: SYSBOOT (MJ) |
STSTRM: RFI-P (NA) |
EQPT: CONTBUS-IO-B (CONTBUS-B) (MN) |
NE: TEMP-MISM (NA) |
STSTRM: SD-P (NA) |
EQPT: CTNEQPT-MISMATCH (NA) |
OCH-TERM: FDI (NA) |
STSTRM: SF-P (NA) |
EQPT: DIAG (CR) |
OCH-TERM: OCHTERM-INC (NA) |
STSTRM: TIM-P (NA) |
EQPT: EQPT (CR) |
OCH-TERM: OPWR-HDEG (MN) |
STSTRM: UNEQ-P (CR) |
EQPT: EQPT-DEGRADE (MN) |
OCH-TERM: OPWR-LDEG (MN) |
STSTRM: WAN-SYNCLOSS (MJ) |
EQPT: EVAL-LIC (MN) |
— |
— |
EQPT: EXCCOL (MN) |
OCH-TERM: OPWR-LFAIL (CR) |
TRUNK: AIS (NR) |
EQPT: FAILTOSW (NA) |
OCH-TERM: PARAM-MISM (NA) |
TRUNK: AIS-L (NR) |
EQPT: FAPS-CONFIG-MISMATCH (MN) |
OCH: APC-CORR-SKIPPED (MN) |
TRUNK: ALS (NA) |
EQPT: FIPS-TEST-FAILED (CR) |
||
EQPT: FORCED-REQ (NA) |
OCH: APC-DISABLED (MN) |
TRUNK: AS-CMD (NA) |
EQPT: FP-LINK-LOSS (MN) |
OCH: APC-OUT-OF-RANGE (MN) |
TRUNK: AS-MT (NA) |
EQPT: FTA-MISMATCH (NA) |
OCH: AS-CMD (NA) |
TRUNK: CARLOSS (MJ) |
— |
— |
TRUNK: CD (CR) |
EQPT: HI-LASERBIAS (MN) |
OCH: AS-MT (NA) |
TRUNK: DSP-COMM-FAIL (MJ) |
EQPT: HI-LASERTEMP (MN) |
OCH: DATA-CRC (MJ) |
TRUNK: DSP-FAIL (MJ) |
EQPT: HI-TXPOWER (MN) |
OCH: FDI (NA) |
TRUNK: EOC (MN) |
EQPT: HITEMP (MN) |
OCH: LOS-O (MN) |
TRUNK: EOC-L (MN) |
— |
— |
TRUNK: ESMC-FAIL (MN) |
EQPT: IMPROPRMVL (CR) |
OCH: LOS-P (CR) |
TRUNK: FAILTOSW (NA) |
EQPT: INHSWPR (NA) |
OCH: OPWR-HDEG (MN) |
TRUNK: FAPS (NA) |
EQPT: INHSWWKG (NA) |
OCH: OPWR-HFAIL (CR) |
TRUNK: FC-NO-CREDITS (MJ) |
EQPT: INVALID-MUXCONF (CR) |
— |
— |
EQPT: LIC-EXPIRING-SHORTLY (MJ) |
— |
— |
EQPT: LIC-EXPIRING-SOON (MJ) |
— |
— |
EQPT: LICENSE-EXPIRED (CR) |
— |
— |
EQPT: LO-LASERBIAS (MN) |
OCH: OPWR-LDEG (MN) |
TRUNK: FEC-MISM (MJ) |
EQPT: LO-LASERTEMP (MN) |
OCH: OPWR-LFAIL (CR) |
TRUNK: FORCED-REQ-SPAN (NA) |
EQPT: LO-TXPOWER (MN) |
OCH: PARAM-MISM (NA) |
TRUNK: GCC-EOC (MN) |
EQPT: LOCKOUT-REQ (NA) |
OCH: PORT-FAIL (CR) |
TRUNK: GE-OOSYNC (CR) |
EQPT: MAN-REQ (NA) |
OCH: TRAIL-SIGNAL-FAIL (NA) |
TRUNK: HELLO (MN) |
EQPT: MANRESET (NA) |
OCH: VOA-HDEG (MN) |
TRUNK: HI-LASERBIAS (MN) |
EQPT: MEA (CR) |
OCH: VOA-HFAIL (CR) |
TRUNK: HI-RXPOWER (MN) |
EQPT: MEM-GONE (MJ) |
OCH: VOA-LDEG (MN) |
TRUNK: HI-TXPOWER (MN) |
EQPT: MEM-LOW (MN) |
OCH: VOA-LFAIL (CR) |
TRUNK: ILK-FAIL (CR) |
EQPT: OPEN-SLOT (NA) |
OCH: WVL-DRIFT-CHAN-OFF (NR) |
TRUNK: ISIS-ADJ-FAIL (MN) |
EQPT: OVER-TEMP-UNIT-PROT (CR) |
||
EQPT: PEER-NORESPONSE (MJ) |
OCHNC-CONN: OCHNC-INC (NA) |
TRUNK: LASER-OFF-WVL-DRIFT (MJ) |
EQPT: PROT-SOFT-VERIF-FAIL (MJ) |
OCN: AIS-L (NR) |
TRUNK: LO-RXPOWER (MN) |
EQPT: PROTNA (MN) |
OCN: ALS (NA) |
TRUNK: LO-TXPOWER (MN) |
EQPT: PWR-FAIL-A (MN) |
OCN: APS-INV-PRIM (MN) |
TRUNK: LOCKOUT-REQ (NA) |
EQPT: PWR-FAIL-B (MN) |
OCN: APS-PRIM-FAC (NA) |
TRUNK: LOF (CR) |
EQPT: PWR-FAIL-RET-A (MN) |
OCN: APS-PRIM-SEC-MISM (MN) |
TRUNK: LOM (CR) |
EQPT: PWR-FAIL-RET-B (MN) |
OCN: APSB (MN) |
TRUNK: LOS (CR) |
EQPT: RS-EOC (MN) |
OCN: APSC-IMP (MN) |
TRUNK: LOS-P (CR) |
EQPT: RS-TIM (CR) |
OCN: APSCDFLTK (MN) |
TRUNK: LPBKFACILITY (NA) |
EQPT: RUNCFG-SAVENEED (NA) |
OCN: APSCINCON (MN) |
TRUNK: LPBKTERMINAL (NA) |
EQPT: SBYTCC-NEINTCLK (NA) |
OCN: APSCM (MN) |
TRUNK: MANUAL-REQ-SPAN (NA) |
EQPT: SFTWDOWN (MN) |
OCN: APSCNMIS (MJ) |
TRUNK: ODUK-1-AIS-PM (NR) |
EQPT: SFTWDOWN-FAIL (MN) |
— |
— |
EQPT: SOFT-VERIF-FAIL (CR) |
OCN: APSIMP (MN) |
TRUNK: ODUK-2-AIS-PM (NR) |
EQPT: SW-MISMATCH (NA) |
OCN: APSMM (MN) |
TRUNK: ODUK-3-AIS-PM (NR) |
EQPT: TEMP-LIC (MN) |
— |
— |
EQPT: UNEQ-P (CR) |
OCN: AS-CMD (NA) |
TRUNK: ODUK-4-AIS-PM (NR) |
EQPT: UNIT-HIGH-TEMP (MN) |
||
EQPT: VOA-DISABLED (CR) |
OCN: AS-MT (NA) |
TRUNK: ODUK-AIS-PM (NR) |
EQPT: WKSWBK (NA) |
OCN: AUTOLSROFF (CR) |
TRUNK: ODUK-BDI-PM (NR) |
EQPT: WKSWPR (NA) |
OCN: CHANLOSS (NA) |
TRUNK: ODUK-LCK-PM (NR) |
EQPT: WORK-QUEUE-FULL (NA) |
OCN: EOC (MN) |
TRUNK: ODUK-OCI-PM (NR) |
EQPT: WTR (NA) |
OCN: EOC-E (MN) |
TRUNK: ODUK-SD-PM (NA) |
ESCON: ALS (NA) |
OCN: EOC-L (MN) |
TRUNK: ODUK-SF-PM (NA) |
ESCON: AS-CMD (NA) |
OCN: FAILTOSW (NA) |
TRUNK: ODUK-TIM-PM (MJ) |
ESCON: AS-MT (NA) |
OCN: FE-FRCDWKSWBK-SPAN (NA) |
TRUNK: OTUK-AIS (NR) |
ESCON: FAILTOSW (NA) |
OCN: FE-FRCDWKSWPR-SPAN (NA) |
TRUNK: OTUK-BDI (NR) |
ESCON: FORCED-REQ-SPAN (NA) |
OCN: FE-MANWKSWBK-SPAN (NA) |
TRUNK: OTUK-IAE (MN) |
ESCON: HI-LASERBIAS (MN) |
OCN: FE-MANWKSWPR-SPAN (NA) |
TRUNK: OTUK-LOF (CR) |
ESCON: HI-RXPOWER (MN) |
OCN: FEPRLF (MN) |
TRUNK: OTUK-SD (NA) |
ESCON: HI-TXPOWER (MN) |
OCN: FORCED-REQ-SPAN (NA) |
TRUNK: OTUK-SF (NA) |
ESCON: LO-RXPOWER (MN) |
OCN: FRCDWKSWBK-NO-TRFSW (NA) |
TRUNK: OTUK-TIM (CR) |
ESCON: LO-TXPOWER (MN) |
OCN: FRCDWKSWPR-NO-TRFSW (NA) |
TRUNK: OUT-OF-SYNC (MJ) |
— |
OCN: HELLO (MN) |
TRUNK: PMD-DEG (MJ) |
ESCON: LOCKOUT-REQ (NA) |
OCN: HI-LASERBIAS (MN) |
TRUNK: PPR-BDI (NA) |
ESCON: LOS (CR) |
OCN: HI-LASERTEMP (MN) |
TRUNK: PPR-FDI (NA) |
ESCON: LPBKFACILITY (NA) |
OCN: HI-RXPOWER (MN) |
TRUNK: PPR-MAINT (NA) |
ESCON: LPBKTERMINAL (NA) |
OCN: HI-TXPOWER (MN) |
TRUNK: PROV-MISMATCH (MJ) |
ESCON: MANUAL-REQ-SPAN (NA) |
OCN: ISIS-ADJ-FAIL (MN) |
TRUNK: PTIM (MJ) |
ESCON: SIGLOSS (MJ) |
OCN: LASER-OFF-WVL-DRIFT (MJ) |
TRUNK: RFI (NR) |
ESCON: SQUELCHED (NA) |
OCN: LASEREOL (MN) |
TRUNK: RFI-L (NR) |
ESCON: WKSWPR (NA) |
OCN: LOCKOUT-REQ (NA) |
TRUNK: SD (NA) |
ESCON: WTR (NA) |
OCN: LO-LASERBIAS (MN) |
TRUNK: SD-L (NA) |
ETH: CFM-CONFIG-ERROR (MN) |
OCN: LO-LASERTEMP (MN) |
TRUNK: SF (NA) |
ETH: CFM-LOOP (MN) |
OCN: LO-RXPOWER (MN) |
TRUNK: SF-L (NA) |
ETH: CFM-MEP-DOWN (MN) |
OCN: LO-TXPOWER (MN) |
TRUNK: SIGLOSS (MJ) |
ETH: CFM-XCON-SERVICE (MN) |
OCN: MANUAL-REQ-SPAN (NA) |
TRUNK: SQUELCHED (NA) |
ETH: LOCAL-FAULT (MJ) |
OCN: MANWKSWBK-NO-TRFSW (NA) |
TRUNK: SSM-DUS (NA) |
ETH: OUT-OF-BUNDLE |
OCN: MANWKSWPR-NO-TRFSW (NA) |
TRUNK: SSM-FAIL (MN) |
— |
OCN: PEER-CSF (MJ) |
— |
ETH: PPR-TRIG-EXCD (NA) |
OCN: RFI-L (NA) |
TRUNK: SSM-LNC (NA) |
ETH: REMOTE-FAULT (MJ) |
OCN: SD-L (NA) |
TRUNK: SSM-OFF (NA) |
ETH: REP-LINK-FLAPPING (MJ) |
OCN: SF-L (NA) |
TRUNK: SSM-PRC (NA) |
ETH: REP-NEIHB-ADJ-FAIL (MJ) |
OCN: SQUELCHED (NA) |
TRUNK: SSM-PRS (NA) |
— |
OCN: TRUNK-ODU-AIS (NR) |
— |
— |
OCN: TRUNK-PAYLOAD-MISM (MJ) |
— |
ETH: REP-SEGMENT-FAULT (NA) |
OCN: TIM-S (CR) |
TRUNK: SSM-RES (NA) |
EXT-SREF: FRCDSWTOPRI (NA) |
OMS: APC-DISABLED (MN) |
TRUNK: SSM-SDH-TN (NA) |
EXT-SREF: FRCDSWTOSEC (NA) |
OMS: APC-CORR-SKIPPED (MN) |
TRUNK: SSM-SETS (NA) |
EXT-SREF: FRCDSWTOTHIRD (NA) |
OMS: APC-OUT-OF-RANGE (MN) |
TRUNK: SSM-SMC (NA) |
EXT-SREF: MANSWTOPRI (NA) |
OMS: AS-CMD (NA) |
TRUNK: SSM-ST2 (NA) |
EXT-SREF: MANSWTOSEC (NA) |
OMS: AS-MT (NA) |
TRUNK: SSM-ST3 (NA) |
EXT-SREF: MANSWTOTHIRD (NA) |
OMS: LOS-O (MN) |
TRUNK: SSM-ST3E (NA) |
EXT-SREF: SWTOPRI (NA) |
OMS: LOS-P (CR) |
TRUNK: SSM-ST4 (NA) |
EXT-SREF: SWTOSEC (NA) |
OMS: OPWR-HDEG (MN) |
TRUNK: SSM-STU (NA) |
EXT-SREF: SWTOTHIRD (NA) |
OMS: OPWR-HFAIL (CR) |
TRUNK: SSM-TNC (NA) |
EXT-SREF: SYNCPRI (MN) |
OMS: OPWR-LDEG (MN) |
TRUNK: SYNC-FREQ (NA) |
EXT-SREF: SYNCSEC (MN) |
OMS: OPWR-LFAIL (CR) |
TRUNK: SYNCLOSS (MJ) |
EXT-SREF: SYNCTHIRD (MN) |
OMS: PARAM-MISM (NA) |
TRUNK: TIM (CR) |
FAN: EQPT-MISS (CR) |
OMS: PMI (NA) |
TRUNK: TIM-MON (MN) |
FAN: FAN (CR) |
OMS: VOA-HDEG (MN) |
TRUNK: TRAIL-SIGNAL-FAIL (NA) |
FAN: COOL-MISM (NR) |
— |
— |
FAN: MEA (CR) |
OMS: VOA-HFAIL (CR) |
TRUNK: UNC-WORD (NA) |
FAN: MFGMEM (CR) |
OMS: VOA-LDEG (MN) |
TRUNK: UT-COMM-FAIL (MJ) |
FC: ALS (NA) |
OMS: VOA-LFAIL (CR) |
TRUNK: UT-FAIL (MJ) |
FC: AS-CMD (NA) |
OSC-RING: RING-ID-MIS (MJ) |
TRUNK: WTR (NA) |
FC: AS-MT (NA) |
OTS: APC-CORR-SKIPPED (MN) |
TRUNK: WVL-MISMATCH (MJ) |
FC: CARLOSS (MJ) |
OTS: APC-DISABLED (MN) |
USB:USBSYNC (CR) |
FC: FAILTOSW (NA) |
OTS: APC-OUT-OF-RANGE (MN) |
USB: USB-WRITE-FAIL (CR) |
FC: FC-NO-CREDITS (MJ) |
OTS: AS-CMD (NA) |
VCMON-HP: AU-AIS (NR) |
FC: FORCED-REQ-SPAN (NA) |
OTS: AS-MT (NA) |
VCMON-HP: AU-LOP (NA) |
FC: GE-OOSYNC (CR) |
OTS: AWG-DEG (MN) |
VCMON-HP: AUTOSW-AIS-SNCP (NR) |
FC: HI-LASERBIAS (MN) |
OTS: AWG-FAIL (CR) |
VCMON-HP: AUTOSW-LOP-SNCP (NA) |
FC: HI-RXPOWER (MN) |
OTS: AWG-OVERTEMP (CR) |
VCMON-HP: AUTOSW-PDI-SNCP (NA) |
FC: HI-TXPOWER (MN) |
OTS: AWG-WARM-UP (NA) |
VCMON-HP: AUTOSW-SDBER-SNCP (NA) |
FC: LO-RXPOWER (MN) |
OTS: DCU-LOSS-FAIL (MN) |
VCMON-HP: AUTOSW-SFBER-SNCP (NA) |
FC: LO-TXPOWER (MN) |
OTS: EXC-BP (MN) |
VCMON-HP: AUTOSW-UNEQ-SNCP (NA) |
FC: LOCKOUT-REQ (NA) |
OTS: FAILTOSW (NA) |
VCMON-HP: FAILTOSW-HO (NA) |
FC: LPBKFACILITY (NA) |
OTS: FORCED-REQ-SPAN (NA) |
VCMON-HP: FORCED-REQ (NA) |
FC: LPBKTERMINAL (NA) |
OTS: LASERBIAS-DEG (MN) |
VCMON-HP: HP-DEG (NA) |
FC: MANUAL-REQ-SPAN (NA) |
OTS: LOS (CR) |
VCMON-HP: HP-EXC (NA) |
FC: OUT-OF-SYNC (MJ) |
— |
VCMON-HP: HP-PLM (CR) |
FC: SIGLOSS (MJ) |
OTS: LOS-O (MN) |
VCMON-HP: HP-RFI (NR) |
FC: SQUELCHED (NA) |
OTS: LOS-P (CR) |
VCMON-HP: HP-TIM (MN) |
FC: SYNCLOSS (MJ) |
OTS: LOS-RAMAN (CR) |
VCMON-HP: HP-UNEQ (CR) |
FC: TRUNK-ODU-AIS (NR) |
— |
— |
FC: TRUNK-PAYLOAD-MISM (MJ) |
— |
— |
FC: WKSWPR (NA) |
OTS: LOCKOUT-REQ (NA) |
VCMON-HP: WAN-SYNCLOSS (MJ) |
FC: WTR (NA) |
OTS: MAN-LASER-RESTART (NA) |
VCMON-HP: LOCKOUT-REQ (NA) |
FCMR: GFP-CSF (MJ) |
OTS: MANUAL-REQ-SPAN (NA) |
VCMON-HP: LPBKCRS (NA) |
FCMR: GFP-LFD (MJ) |
OTS: MT-OCHNC (NA) |
VCMON-HP: SFBER-EXCEED-HO (NA) |
FCMR: GFP-UP-MISMATCH (MJ) |
OTS: OPWR-HDEG (MN) |
VCMON-LP: AUTOSW-AIS-SNCP (NR) |
FE: EOC-E (MN) |
OTS: OPWR-HFAIL (CR) |
VCMON-LP: AUTOSW-LOP-SNCP (NA) |
GE: ALS (NA) |
OTS: OPWR-LDEG (MN) |
VCMON-LP: AUTOSW-UNEQ-SNCP (NA) |
GE: AS-CMD (NA) |
OTS: OPWR-LFAIL (CR) |
VCMON-LP: FORCED-REQ (NA) |
GE: AS-MT (NA) |
OTS: OSRION (NA) |
VCMON-LP: LOCKOUT-REQ (NA) |
GE: CARLOSS (MJ) |
OTS: PARAM-MISM (NA) |
VCTRM-HP: AS-MT-OOG (NA) |
GE: EFM-PEER-MISSING (MN) |
OTS: PMI (NA) |
VCTRM-HP: AU-AIS (NR) |
GE: EFM-RFI-CE(MJ) |
OTS: PWR-PROT-ON (MJ) |
VCTRM-HP: AU-LOP (CR) |
GE: EFM-RFI-DG (MJ) |
OTS: RAMAN-G-NOT-REACHED (MN) |
VCTRM-HP: HP-DEG (NA) |
GE: EFM-RFI-LF (MJ) |
OTS: RLS (NA) |
VCTRM-HP: HP-ENCAP-MISMATCH (CR) |
GE: EFM-RLBK (NA) |
OTS: SH-IL-VAR-DEG-HIGH (MN) |
VCTRM-HP: HP-EXC (NA) |
GE: EOC-E (MN) |
OTS: SH-IL-VAR-DEG-LOW (MN) |
VCTRM-HP: HP-PLM (CR) |
GE: ESMC-FAIL (MN) |
— |
— |
GE: REP-SEGMENT-FAULT (NA) |
OTS: SHUTTER-OPEN (NA) |
VCTRM-HP: HP-TIM (CR) |
GE: FAILTOSW (NA) |
OTS: SPAN-NOT-MEASURED (NA) |
VCTRM-HP: HP-UNEQ (CR) |
GE: FORCED-REQ-SPAN (NA) |
OTS: SPANLEN-OUT-OF-RANGE (MN) |
VCTRM-HP: SFBER-EXCEED-HO (NA) |
GE: GE-OOSYNC (CR) |
OTS: VOA-HDEG (MN) |
VCTRM-LP: AS-MT-OOG (NA) |
GE: HI-LASERBIAS (MN) |
OTS: VOA-HFAIL (CR) |
VCTRM-LP: SFBER-EXCEED-HO (NA) |
GE: HI-RXPOWER (MN) |
OTS: VOA-LDEG (MN) |
VCMON-HP: WAN-SYNCLOSS (MJ) |
GE: HI-TXPOWER (MN) |
OTS: VOA-LFAIL (CR) |
— |
Trouble Characterizations
The ONS DWDM system reports trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253-CORE, and graphical user interface (GUI) state indicators. These notifications are described in the following paragraphs.
The ONS System 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.
Note |
Unless otherwise noted, ONS 15454 refers to the ANSI and ETSI versions of the platform. |
Note |
For a description of CTC-view terminology, refer to the CTC Enhancements, Operations, and Shortcuts. |
Alarm Characteristics
The ONS DWDM system 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.)
Condition Characteristics
Conditions include any problem detected on an ONS DWDM 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. For information about transients, see Transient Conditions.
Note |
When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. You can retrieve alarms and events on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab. |
Severity
The ONS DWDM system uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), and Not Reported (NR). These are described below:
- A Critical (CR) alarm generally indicates severe, Service-Affecting trouble that needs immediate correction. Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.
- A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, loss of traffic on more than five DS-1 circuits is Critical (CR), but loss of traffic on one to four DS-1 circuits is Major (MJ).
- Minor (MN) alarms generally are those that do not affect service. For example, the automatic protection switching (APS) byte failure (APSB) alarm indicates that line terminating equipment (LTE) detects a byte failure on the signal that could prevent traffic from properly executing a traffic switch.
- Not Alarmed (NA) conditions are information indicators, such as for free-run synchronization state (FRNGSYNC) or a forced-switch to primary (FRCSWTOPRI) timing event. They could or could not require troubleshooting, as indicated in the entries.
- Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be expected in the presence of primary alarms.
Severities can be customized for an entire network or for single nodes, from the network level down to the port level by changing or downloading customized alarm profiles. These custom severities are subject to the standard severity-demoting rules given in Telcordia GR-474-CORE. Procedures for customizing alarm severities are located in the Alarm and TCA Monitoring and Management document.
Service Effect
Service-Affecting (SA) alarmsthose that interrupt servicecould be Critical (CR), Major (MJ), or Minor (MN) severity alarms. Service-Affecting (SA) alarms indicate service is affected. Non-Service-Affecting (NSA) alarms always have a Minor (MN) default severity.
State
The Alarms or History tab State (ST) column indicate the disposition of the alarm or condition as follows:
- A raised (R) event is one that is active.
- A cleared (C) event is one that is no longer active.
- A transient (T) event is one that is automatically raised and cleared in CTC during system changes such as user login, logout, loss of connection to node/shelf view, etc. Transient events do not require user action. These are listed in the chapter, Transient Conditions.
Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS DWDM system. Personnel should not perform any procedures in this chapter unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances users should pay close attention to the following caution.
 Caution |
Hazardous voltage or energy could be present on the backplane when the system is operating. Use caution when removing or installing cards. |
Some troubleshooting procedures require installation or removal of OC-192 cards; in these instances users should pay close attention to the following warnings.
 Warning |
The laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 |
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Warning |
Class 1 laser product. Statement 1008 |
Warning |
Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206 |
Warning |
The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207 |
Trouble-Clearing Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.
Note |
When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner of the GUI is not indented. If it is, click it to turn it off. When you are done checking for alarms, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the Alarm and TCA Monitoring and Management document. |
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 Alarm and TCA Monitoring and Management document. |
Note |
When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab. |
- ACT-SOFT-VERIF-FAIL
- AIS
- AIS-L
- AIS-P
- ALS
- ALS-DISABLED
- AMPLI-INIT
- APC-CORR-SKIPPED
- APC-DISABLED
- APC-END
- APC-OUT-OF-RANGE
- APC-WRONG-GAIN
- APSB
- APSCM
- APSIMP
- APS-INV-PRIM
- APSMM
- APS-PRIM-FAC
- APS-PRIM-SEC-MISM
- AS-CMD
- AS-MT
- AU-AIS
- AU-LOP
- AUTO-SENSE
- AUTO-SENSE-DSBLD
- AUTOLSROFF
- AUTORESET
- AUTOSW-AIS
- AUTOSW-AIS-SNCP
- AUTOSW-LOP (STSMON)
- AUTOSW-LOP-SNCP
- AUTOSW-PDI
- AUTOSW-PDI-SNCP
- AUTOSW-SDBER
- AUTOSW-SDBER-SNCP
- AUTOSW-SFBER
- AUTOSW-SFBER-SNCP
- AUTOSW-UNEQ (STSMON)
- AUTOSW-UNEQ-SNCP (VCMON-HP)
- AWG-DEG
- AWG-FAIL
- AWG-OVERTEMP
- AWG-WARM-UP
- BAT-FAIL
- BKUPMEMP
- BP-LPBKFACILITY
- BP-LPBKTERMINAL
- BPV
- CARLOSS (EQPT)
- CARLOSS (FC)
- CARLOSS (GE)
- CARLOSS (ISC)
- CARLOSS (TRUNK)
- CASETEMP-DEG
- CD
- CFM-CONFIG-ERROR
- CFM-LOOP
- CFM-MEP-DOWN
- CFM-XCON-SERVICE
- CHANLOSS
- CLDRESTART
- COMP-CARD-MISSING
- COMM-FAIL
- CONTBUS-DISABLED
- CONTBUS-IO-A
- CONTBUS-IO-B
- COOL-MISM
- CP-UNVER-CLEARED Alarm
- CTNEQPT-MISMATCH
- DATA-CRC
- DATAFLT
- DBOSYNC
- DCU-LOSS-FAIL
- DISCONNECTED
- DSP-COMM-FAIL
- DSP-FAIL
- DUP-IPADDR
- DUP-NODENAME
- DUP-SHELF-ID
- EFM-PEER-MISSING
- EFM-RFI-CE
- EFM-RFI-DG
- EFM-RFI-LF
- EFM-RLBK
- EHIBATVG
- ELWBATVG
- ENCAP-MISMATCH-P
- EOC
- EOC-E
- EOC-L
- EQPT
- EQPT-DEGRADE
- EQPT-DIAG
- EQPT-FAIL
- EQPT-MISS
- ERFI-P-CONN
- ERFI-P-SRVR
- ESMC-FAIL
- EVAL-LIC
- EXC-BP
- EXCCOL
- EXT EXT
- FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS)
- FAILTOSW (TRUNK)
- FAILTOSW-HO
- FAILTOSW-PATH FAILTOSW-PATH
- FAN
- FAPS
- FAPS-CONFIG-MISMATCH
- FC-NO-CREDITS
- FDI
- FE-FRCDWKSWBK-SPAN
- FE-FRCDWKSWPR-SPAN
- FE-MANWKSWBK-SPAN
- FE-MANWKSWPR-SPAN
- FEC-MISM
- FEPRLF
- FIBERTEMP-DEG
- FIPS_TEST_FAILED
- FORCED-REQ
- FORCED-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN, OTS)
- FORCED-REQ-SPAN (TRUNK)
- FP-LINK-LOSS
- FRCDSWTOINT
- FRCDSWTOPRI
- FRCDSWTOSEC
- FRCDSWTOTHIRD
- FRNGSYNC
- FSTSYNC
- FTA-MISMATCH
- GAIN-HDEG
- GAIN-HFAIL
- GAIN-LDEG
- GAIN-LFAIL
- GCC-EOC
- GE-OOSYNC (FC, GE, ISC)
- GE-OOSYNC (TRUNK)
- GFP-CSF
- GFP-CSF-SIGLOSS
- GFP-CSF-SYNCLOSS
- GFP-LFD
- GFP-UP-MISMATCH
- HELLO
- HIBATVG
ACT-SOFT-VERIF-FAIL
Default Severity: Critical (CR) Non-Service-Affecting (NSA)
Logical Object: EQPT
Clear the ACT-SOFT-VERIF-FAIL Alarm
| Step 1 | To clear the ACT-SOFT-VERIF-FAIL alarm, download the Cisco ONS Release software (Release 9.2 or later, as applicable) on the protect (standby) flash. |
| Step 2 | Activate the protect (standby) flash. |
| Step 3 |
After the TNC/TSC card is actived, download the Cisco ONS Release software (Release 9.2 or later, as applicable) on the standby partition or the standby code volume on the protect flash. If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html or call the Cisco Technical Assistance Center (1 800 553-2447) to report the problem. |
AIS
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Objects: BITS, FUDC, MSUDC
The Alarm Indication Signal (AIS) condition indicates that this node is detecting an alarm indication signal in the incoming signal SONET overhead.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolve the problem on the upstream node.
Clear the AIS Condition
| Step 1 | Determine whether there are alarms such as LOS on the upstream nodes and equipment or if there are OOS,MT (or Locked,maintenance), or OOS,DSBLD (or Locked,disabled) ports. |
| Step 2 |
Clear the upstream alarms using the applicable procedures in this chapter. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AIS-L
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA),
logical Objects: OCN, TRUNK
The AIS Line condition indicates that this node is detecting line-level AIS in the incoming signal. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
This condition can also be raised in conjunction with the TIM-S alarm if AIS-L is enabled. (For more information about the TIM-S alarm, refer to the Alarm Troubleshooting chapter in the Cisco ONS 15454 DWDM Troubleshooting Guide.
Note |
ONS 15454 DS-3 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided. A DS3/EC1-48 card can be provisioned to transmit AIS for a terminal loopback. |
Clear the AIS-L Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AIS-P
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: STSMON, STSTRM
The AIS Path condition means that this node is detecting AIS in the incoming path. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
Clear the AIS-P Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
ALS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCN, TRUNK
The Automatic Laser Shutdown (ALS) condition on the amplifier cards, 40-SMR1-C, or 40-SMR2-C cards indicate that the ALS safety feature on the card port is switched ON. This condition is accompanied by a corresponding LOS alarm in the reverse direction of the same port.
Note |
ALS is an informational condition and does not require troubleshooting. |
ALS-DISABLED
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Automatic Laser Shutdown (ALS) condition occurs when a DWDM Optical Preamplifier or Optical Booster (OPT-BST) Amplifier card ALS is changed to Disabled from any other state (such as Enabled) by user command.
Clear the ALS-DISABLED Condition
| Step 1 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the OPT-BST, or OPT-PRE, OPT-AMP-C, or OMP-AMP-17-C card to display the card view. |
| Step 2 | Click the Maintenance > ALS tabs. |
| Step 3 |
In the ALS Mode column, change the entry from Disabled to your required state. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AMPLI-INIT
Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: AOTS
The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition typically accompanies the APC-DISABLED alarm.
Note |
For basic information about amplifier cards and to change their settings, refer to the Optical Amplifier Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the AMPLI-INIT Condition
| Step 1 | Complete the Delete a Circuit procedure on the most recently created circuit. |
| Step 2 |
Recreate this circuit using the procedures in the Create Optical Channel Circuits and Provisionable Patchcords chapter in the Cisco ONS 15454 DWDM Configuration Guide. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APC-CORR-SKIPPED
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: AOTS, OCH, OMS, OTS
The Automatic Power Control (APC) Correction Skipped condition occurs when the actual power level of a DWDM channel exceeds the expected setting by 3 dBm or more. APC compares actual power levels with previous power levels every hour or after any channel allocation is performed. If the power difference to be compensated by APC exceeds the range of + 3 dBm or 3 dBm compared with the previous value set, APC is designed not to correct the level and the APC-CORR-SKIPPED condition is raised.
For more information about APC, refer to the Network Reference chapter in the Cisco ONS 15454 DWDM Configuration Guide, and the System Restart after a Fiber Cut.
The APC Correction Skipped alarm strongly limits network management (for example, a new circuit cannot be turned into IS). The Force APC Correction button helps to restore normal conditions by clearing the APC Correction Skipped alarm. For more information about the Force APC Correction button, refer to the Managing APC section in Network Reference chapter of the Cisco ONS 15454 DWDM Configuration Guide
APC-DISABLED
Default Severity:Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: NE, SHELF, AOTS, OTS, OMS, OCH, EQPT
The APC Disabled alarm occurs when the information related to the number of DWDM channels is not reliable. The condition can occur when any of the following related alarms also occur: the EQPT alarm, the IMPROPRMVL alarm, or the MEA (EQPT) alarm. If the condition occurs with the creation of the first circuit, delete and recreate the circuit. (See the Create Optical Channel Circuits and Provisionable Patchcords chapter of the Cisco ONS 15454 DWDM Configuration Guidefor information about this.) For more information about APC, refer to the Network Reference chapter in the Cisco ONS 15454 DWDM Configuration Guide.
APC Disabled alarm is raised under the following conditions:
- When APC is manually disabled in a domain to prevent unexpected power regulations during maintenance or troubleshooting.
- When an abnormal event impacting optical regulation occurs.
- When an EQPT, MEA or IMPROPRMVL alarm is raised by any MSTP unit in a network.
- When gain or power degrade occurs or when the Power Fail alarm is raised by the output port of any amplifier in the network.
- When a VOA degrade or a VOA Fail alarm is raised by any MSTP unit in a network.
- When signalling protocol detects that one of the APC instances in a network is no longer reachable.
-
When all nodes in a network do not belong to metro core.
Note
The MEA and IMPROPRMVL alarms does not disable APC when raised on OSCM, OSC-CSM, or MXP/TXP cards.
Clear the APC-DISABLED Alarm
| Step 1 | Complete the appropriate procedure to clear the main alarm: |
| Step 2 |
If the condition does not clear, complete the Delete a Circuit procedure and then recreate it using procedures in the Create Optical Channel Circuits and Provisionable Patchcords chapter in the Cisco ONS 15454 DWDM Configuration Guide. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APC-END
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: NE
The APC Terminated on Manual Request condition is raised when APC terminates after it is manually launched from CTC or TL1. APC-END is an informational condition that is raised and cleared spontaneously by the system and is not visible in the CTC Condition window. It is visible only by retrieving it in the Conditions or History tabs. For more information about APC, refer to the Network Reference chapter in the Cisco ONS 15454 DWDM Configuration Guide.
Note |
APC-END is an informational condition and does not require troubleshooting. |
APC-OUT-OF-RANGE
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: AOTS, OCH, OMS, OTS
The APC-OUT-OF-RANGE condition is raised on amplifier cards OPT-PRE, OPT-BST-L, OPT-PRE, OPT-AMP-17-C, OPT-AMP-C, OPT-RAMP-C, OPT-AMP-L, and OPT-BST-E); demultiplexer cards (32-DMX, 40-DMX-C, and 32-DMX-L) having a single variable optical attenuator (VOA); and optical add/drop multiplexer cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x) when the requested gain or attenuation setpoint cannot be set because it exceeds the port parameter range. For example, this condition is raised when APC attempts to set the OPT-BST gain higher than 20 dBm (the card maximum setpoint) or to set the attenuation on the express VOA lower than 0 dBm (its minimum setpoint).
Note |
A common cause of an amplifier trying to attain a value higher than the maximum setpoint or an attenuator trying to attain a value lower than the minimum setpoint is the low input power. |
Note |
For general information about the amplifier cards and changing their settings, refer to the Optical Amplifier Cards chapter of the Cisco ONS 15454 DWDM Configuration Guide. For more information about APC, refer to the Network Reference chapter in the same manual. |
Clear the APC-OUT-OF-RANGE Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APC-WRONG-GAIN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: AOTS
The APC-WRONG-GAIN condition is raised on the amplifier card (OMP-AMP-17-C), when the actual gain of the card (17dB) does not match the expected gain calculated by APC. There is a margin of +1 or -1 dB before the condition is raised.
Note |
The APC-WRONG-GAIN condition indicates a system issue and not the card problem. |
Clear the APC-WRONG-GAIN Alarm
The condition can be cleared by recovering the power at the input port:
| Step 1 | Check the incoming fiber connection and clean them. |
| Step 2 |
Check the regulation points (VOA and amplifiers) along the optical path upstream of the OMP-AMP-17-C card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APSB
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OCN, STMN
The APS Channel Byte Failure alarm occurs when LTE detects protection switching byte failure or an invalid switching code in the incoming APS signal. Some older SONET not manufactured by Cisco send invalid APS codes if they are configured in a 1+1 protection group with newer SONET nodes, such as the ONS 15454. These invalid codes cause an APSB alarm on an ONS 15454.
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 15454. |
| Step 2 |
If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you could need to replace the upstream cards for protection switching to operate properly. Complete the Physically Replace a Card procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APSCM
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OCN, STMN
The APS Channel Mismatch alarm occurs when the ONS 15454 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 15454 when bidirectional protection is used on OC-N cards in a 1+1 protection group configuration. The APSCM alarm does not occur in an optimized 1+1 protection configuration.
Warning |
The laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 |
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Clear the APSCM Alarm
Caution |
Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly. |
| Step 1 | Verify that the working-card channel fibers are physically connected directly to the adjoining node working-card channel fibers. |
| Step 2 |
If the fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node protection-card channel fibers. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APSIMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OCN, STMN
The APS Invalid Code alarm occurs if a 1+1 protection group is not properly configured at both nodes to send or receive the correct APS byte. A node that is either configured for no protection or is configured for path protection or BLSR protection does not send the right K2 APS byte anticipated by a system configured for 1+1 protection. The 1+1 protect port monitors the incoming K2 APS byte and raises this alarm if it does not receive the byte.
The alarm is superseded by an APSCM or APSMM alarm, but not by an AIS condition. It clears when the port receives a valid code for 10 ms.
Clear the APSIMP Alarm
| Step 1 | Check the configuration of the other node in the 1+1 protection group. If the far end is not configured for 1+1 protection, create the group. For procedures, refer to the Turn Up Node chapter in the Cisco ONS 15454 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. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APS-INV-PRIM
Default Severity: Minor (MN), Non-Service Affecting (NSA)
Logical Object: OCN
The Optimized 1+1 APS Primary Facility condition 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 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. |
APSMM
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: STMN
An APS Mode Mismatch failure alarm occurs on OC-N cards when there is a mismatch of the protection switching schemes at the two ends of the span, such as being bidirectional at one end and unidirectional at the other. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional. APSMM can also occur if third-party equipment is provisioned as 1:N and the ONS 15454 is provisioned as 1+1.
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 15454 that is provisioned for 1+1 protection switching.
Clear the APSMM Alarm
| Step 1 |
For the reporting ONS 15454, display node view and verify the protection scheme provisioning:
|
| Step 2 | Click OK in the Edit Protection Group dialog box. |
| Step 3 | Log into the far-end node and verify that the OC-N 1+1 protection group is provisioned. |
| Step 4 | Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in 1. If not, change it to match. |
| Step 5 |
Click Apply. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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.
Note |
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. |
Clear the APS-PRIM-FAC Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
APS-PRIM-SEC-MISM
Default Severity: Minor (MN), Non-Service Affecting (NSA)
Logical Object: OCN
The Optimized 1+1 APS Primary Section Mismatch condition occurs on OC-N cards in an optimized 1+1 protection system if there is a mismatch between the primary section of the local node facility and the primary section of the remote-node facility.
Clear the APS-PRIM-SEC-MISM Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AS-CMD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA
Logical Objects: 2R, AOTS, BPLANE, EQPT, ESCON, FC, GE, ISC, NE, OCH, OCN/STMN, OMS, OTS, PPM, PWR, SHELF, TRUNK
The Alarms Suppressed by User Command condition applies to the network element (NE object), backplane (BPLANE object), a single MXP or TXP card, or a port on one of these cards. It occurs when alarms are suppressed for that object and its subordinate objects. For example, suppressing alarms on a card also suppresses alarms on its ports.
Note |
For more information about suppressing alarms, refer to the Alarm and TCA Monitoring and Management document. |
Note |
This condition is not raised for multiservice transport platform (MSTP) cards such as amplifiers, multiplexers, or demultiplexers. |
Clear the AS-CMD Condition
| Step 1 | For all nodes, in node view (single-shelf mode) or shelf view (multishelf mode), 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. |
| Step 3 |
Determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:
|
| Step 4 | If the AS-CMD condition is reported for a card and not an individual port, in node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Alarm Profiles > Alarm Behavior tabs. |
| Step 5 | Locate the row number for the reported card slot. |
| Step 6 | Click the Suppress Alarms column check box to deselect the option for the card row. |
| Step 7 | If the condition is reported for the backplane, the alarms are suppressed for cards such as the ONS 15454 AIP that are not in the optical or electrical slots. To clear the alarm, complete the following steps: |
| Step 8 |
If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm, complete the following steps:
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AS-MT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: 2R, AOTS, EQPT, ESCON, FC, GE, ISC, OCH, OCN/STMN, OMS, OTS, PPM, SHELF, TRUNK
The Alarms Suppressed for Maintenance Command condition applies to MXP or TXP cards and occurs when a client or trunk port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations.
While provisioning traffic between two MXP-MR-10DME, MXP-MR-2.5G, or MXPP-MR-2.5G cards, putting the trunk port (09) of the card OOS-MT (initially IS) results in the AS-MT alarm being reported on both trunk and client port. This is because all the GFP interfaces derive their state from the trunk state if the trunk is not IS-NR. If the Trunk port state is IS-NR, then all the GFP interfaces derive their state from the corresponding client port. When the trunk is moved to AS-MT, which is not IS, the GFP of the client port also moves to the AS-MT state. The FAC of the client does not change state.
Clear the AS-MT Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AU-AIS
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCTRM-HP
An AU AIS condition applies to the administration unit, which consists of the virtual container (VC) capacity and pointer bytes (H1, H2, and H3) in the SDH frame.
Generally, any AIS is a special SDH 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 it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AU-AIS Condition
| Step 1 | Complete the Clear the AIS Condition procedure. |
| Step 2 |
If the condition does not clear, complete the Clear the APSB Alarm procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AU-LOP
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Objects: VCMON-HP, VCTRM-HP
An AU-LOP alarm indicates that the SDH high order path overhead section of the administration unit has detected a loss of path. AU-LOP occurs when there is a mismatch between the expected and provisioned circuit size. For the TXP card, an AU-LOP is raised if a port is configured for an SDH signal but receives a SDH signal instead. (This information is contained in the H1 byte bits 5 and 6.)
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
For more information about MXP and TXP cards, refer to the Cisco ONS 15454 SDH Reference Manual. |
Clear the AU-LOP Alarm
| Step 1 | In node view, click the Circuits tab and view the alarmed circuit. |
| Step 2 | Verify that the correct circuit size is listed in the Size column. If the size is different from what is expected, such as a VC4-4c instead of a VC4, this causes the alarm. |
| Step 3 | If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm. Ensure that the test set monitoring is set up for the same size as the circuit provisioning. For specific procedures to use the test set equipment, consult the manufacturer. |
| 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 procedures, refer to the Create Circuits and Tunnels chapter in the Cisco ONS 15454 Procedure Guide. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
AUTO-SENSE
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: PPM
The AUTO-SENSE alarm is raised when the port detects an incoming signal on the port. The alarm clears automatically after detecting the signal.
AUTO-SENSE-DSBLD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: PPM
The AUTO-SENSE-DSBLD alarm is raised when the port is configured as an AUTO port, but auto-sensing is disabled.
Clear the AUTO-SENSE-DSBLD Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOLSROFF
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: STMN
The Auto Laser Shutdown alarm occurs when the STM-64 card temperature exceeds 194 degrees F (90 degrees C). The internal equipment automatically shuts down the STM-64 laser when the card temperature rises to prevent the card from self-destructing.
On the OC192 LR/STM64 LH 1550 card:Warning |
The laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 |
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Clear the AUTOLSROFF Alarm
| Step 1 |
View the temperature displayed on the ONS 15454 LCD front panel (Figure 1). Figure 1 shows the shelf LCD panel. 
|
||
| Step 2 | If the temperature of the shelf exceeds 194 degrees F (90 degrees C), the alarm should clear if you solve the ONS 15454 temperature problem. Complete the Clear the HITEMP Alarm procedure. | ||
| Step 3 |
If the temperature of the shelf is under 194 degrees F (90 degrees C), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the Physically Replace a Card procedure for the OC-192 card.
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
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).
Resets performed during a software upgrade also prompt the condition. This condition clears automatically when the card finishes resetting. If the alarm does not clear, complete the following procedure.
Clear the AUTORESET Alarm
| Step 1 | Determine whether there are additional alarms that could have triggered an automatic reset. If there are, troubleshoot these alarms using the applicable section of this chapter. | ||
| Step 2 |
If the card automatically resets more than once a month with no apparent cause, complete the Physically Replace a Card procedure.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-AIS
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: STSMON, VT-MON
The Automatic Path Protection Switch Caused by an AIS condition indicates that automatic path protection switching occurred because of an AIS condition. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-AIS-SNCP
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCMON-LP
The Automatic UPSR Switch Caused by an AIS condition indicates that automatic UPSR protection switching occurred because of the TU-AIS condition. If the UPSR ring is configured for revertive switching, it switches back to the working path after the fault clears. The AUTOSW-AIS-UPSR clears when you clear the primary alarm on the upstream node.
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it detects the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS-UPSR Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-LOP (STSMON)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON
The Automatic Path Protection Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the LOP-P alarm. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Clear the AUTOSW-LOP (STSMON) Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-LOP-SNCP
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCMON-LP
An Automatic UPSR Switch Caused by LOP alarm indicates that an automatic UPSR protection switching occurred because of the AU-LOP. If the UPSR ring is configured for revertive switching, it switches back to the working path after the fault clears.
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Clear the AUTOSW-LOP-SNCP Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-PDI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON, VT-MON
The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a PDI-P alarm. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Clear the AUTOSW-PDI Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-PDI-SNCP
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCMON-LP
The Automatic UPSR Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic UPSR protection switching occurred because of a PDI alarm. If the UPSR is configured for revertive switching, it reverts to the working path after the fault clears.
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Clear the AUTOSW-PDI-SNCP Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-SDBER
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON, VT-MON
The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a SD-P condition caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SD-P is resolved.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Clear the AUTOSW-SDBER Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-SDBER-SNCP
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCMON-LP
The Automatic UPSR Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade caused automatic UPSR protection switching to occur. If the UPSR ring is configured for revertive switching, it reverts to the working path when the SD is resolved.
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Clear the AUTOSW-SDBER-SNCP Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-SFBER
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STSMON, VT-MON
The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a SF-P condition caused automatic path protection switching to occur. If the path protection is configured for revertive switching, the path protection reverts to the working path when the SF-P is resolved.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Clear the AUTOSW-SFBER Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-SFBER-SNCP
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP, VCMON-LP
The Automatic UPSR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail caused automatic UPSR protection switching to occur. If the UPSR ring is configured for revertive switching, it reverts to the working path when the SF is resolved.
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Clear the AUTOSW-SFBER-SNCP Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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-P, caused automatic path protection switching to occur. If the path protection is configured for revertive switching, it reverts to the working path after the fault clears.
Note |
This condition is only reported if the path protection is set up for revertive switching. |
Clear the AUTOSW-UNEQ (STSMON) Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AUTOSW-UNEQ-SNCP (VCMON-HP)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP
The Automatic UPSR Switch Caused by an Unequipped condition indicates that an HP-UNEQ alarm caused automatic UPSR protection switching to occur (see the HP-UNEQ). If the UPSR ring is configured for revertive switching, it reverts to the working path after the fault clears.
Warning |
Class 1 laser product. Statement 1008 |
Warning |
Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 1053 |
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
This condition is only reported if the SNCP is set up for revertive switching. |
Clear the AUTOSW-UNEQ-SNCP (VCMON-HP) Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AWG-DEG
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OTS
The Arrayed Waveguide Gratings (AWG) Degrade alarm occurs when a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX card heater-control circuit degrades. The heat variance can cause slight wavelength drift.
Note |
For general information about 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, and 40DMX cards and about changing their settings, refer to the Reconfigurable Optical Add/Drop Cards chapter of the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the AWG-DEG Alarm
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
AWG-FAIL
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: OTS
The AWG Failure alarm occurs when a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX card heater-control circuit completely fails. The circuit failure disables wavelength transmission. The card must be replaced to restore traffic.
Note |
For general information about 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, and 40DMX cards and about changing their settings, refer to the Reconfigurable Optical Add/Drop Cards chapter of the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the AWG-FAIL Alarm
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
AWG-OVERTEMP
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: OTS
The AWG Over Temperature alarm is raised if a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX card having an AWG-FAIL alarm is not replaced and its heater-control circuit temperature exceeds 212 degrees F (100 degrees C). The card goes into protect mode and the heater is disabled.
Note |
For general information about 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, and 40DMX cards and about changing their settings, refer to the Reconfigurable Optical Add/Drop Cards chapter of the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the AWG-OVERTEMP Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
AWG-WARM-UP
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: OTS
The AWG Warm-Up condition occurs when a 32MUX-O, 40MUX, 32WSS-O, 40WSSC-C, 32DMX-O, 32DMX, or 40DMX card heater-control circuit is attaining its operating temperature during startup. The condition lasts approximately 10 minutes but can vary somewhat from this period due to environmental temperature.
Note |
AWG-WARM-UP is an informational condition and does not require troubleshooting. |
BAT-FAIL
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: PWR
The Battery Fail alarm occurs when one of the two power supplies (A or B) is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so onsite information about the conditions is necessary for troubleshooting.
Clear the BAT-FAIL Alarm
| Step 1 | At the site, determine which battery is not present or operational. |
| Step 2 |
Remove the power cable from the faulty supply. For procedures, refer to the Install the Cisco ONS 15454, ONS 15454 M2, and ONS 15454 M6 Shelf chapter in the Cisco ONS 15454 DWDM Configuration Guide. Reverse the power cable installation procedure. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
BKUPMEMP
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P/TCC3 flash memory. The alarm occurs when the TCC2/TCC2P/TCC3 is in use and has one of four problems:
- Flash manager fails to format a flash partition.
- Flash manager fails to write a file to a flash partition.
- Problem at the driver level.
- Code volume fails cyclic redundancy checking (CRC, which is a method to verify for errors in data transmitted to the TCC2/TCC2P/TCC3).
The BKUPMEMP alarm can also cause the EQPT. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Caution |
A software update on a standby TCC2/TCC2P/TCC3 can take up to 30 minutes. |
Clear the BKUPMEMP Alarm
| Step 1 | Verify that both TCC2/TCC2P/TCC3s are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2/TCC2P/TCC3s. | ||
| Step 2 | Determine whether the active or standby TCC2/TCC2P/TCC3 has the alarm. | ||
| Step 3 | If both TCC2/TCC2P/TCC3s are powered and enabled, reset the TCC2/TCC2P/TCC3 where the alarm is raised. If the card is the active TCC2/TCC2P/TCC3, complete the Reset an Active TCC2/TCC2P/TCC3 Card and Activate the Standby Card procedure. If the card is the standby TCC2/TCC2P/TCC3: | ||
| Step 4 |
If the TCC2/TCC2P/TCC3 you reset does not reboot successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reset the card, complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the Physically Replace a Card procedure.
|
BP-LPBKFACILITY
Default Severity: Not alarmed (NA)
Logical Object: EQPT
The BP-LPBKFACILITY alarm is raised when the backplane facility loopback is configured on the 100G-LC-C or 10x10G-LC card.
Clear the BP-LPBKFACILTIY Alarm
Remove the backplane facility loopback on the 100G-LC-C or 10x10G-LC card.
| Step 1 | Log in to a node on the network. |
| Step 2 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the 100G-LC-C or 10x10G-LC card in CTC to open the card view. |
| Step 3 | Click the Maintenance > Card tabs. |
| Step 4 | Click on the card port that is in IS (or Unlocked) state in the Admin State column, and change the state to OOS,MT. |
| Step 5 |
Click Apply. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
BP-LPBKTERMINAL
Default Severity: Not alarmed (NA)
Logical Object: EQPT
The BP-LPBKTERMINAL alarm is raised when the backplane terminal loopback is configured on the 100G-LC-C or 10x10G-LC card.
Clear the BP-LPBKTERMINAL Alarm
Remove the backplane terminal loopback on the 100G-LC-C or 10x10G-LC card.
| Step 1 | Log in to a node on the network. |
| Step 2 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the 100G-LC-C or 10x10G-LC card in CTC to open the card view. |
| Step 3 | Click the Maintenance > Card tabs. |
| Step 4 | Click on the card port that is in IS (or Unlocked) state in the Admin State column, and change the state to OOS,MT. |
| Step 5 |
Click Apply. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
BPV
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: BITS
The 64K Clock Bipolar Density Violation alarm is raised on the TCC2P card if there is a frequency variation in the 8K BITS clock.
The TCC2P card contains an 8K clock and a 64K clock. Each has some bipolar variation, which is normal. This alarm is raised on the 8K clock if that variation discontinues. The BPV alarm is demoted by an LOF or LOS against the BITS clock.
Note |
This alarm is not raised on the TCC2 card. |
Clear the BPV Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CARLOSS (EQPT)
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: EQPT
A Carrier Loss on the LAN Equipment alarm generally occurs on MXP, TXP, or ADM-10G cards when the ONS system and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the TCC2/TCC2P/TCC3 or the LAN backplane pin connection. This 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.
On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, and MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 encapsulation is turned off.
A TXP_MR_2.5G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data types.
The CARLOSS alarm is also raised against multishelf management (MSM) ports of the external connection unit (ECU) when the connection to the shelf subtending the node is improper.
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
For more information about provisioning MXP or TXP PPMs (also called SFPs), refer to the Turn Up a Node chapter of the Cisco ONS 15454 DWDM Configuration Guide. For PPM (SFP) specifications, refer to the Installing the GBIC, SFP, SFP+, and XFP Optical Modules in Cisco ONS Platforms document. |
Note |
For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the CARLOSS (EQPT) Alarm
| Step 1 |
If the reporting card is an MXP or TXP card in an ONS 15454 node, verify the data rate configured on the PPM (also called SFP):
|
||
| Step 2 | If the reporting card is an OC-N/STM-N card, verify connectivity by pinging the ONS system that is reporting the alarm by completing the Verify PC Connection to the ONS 15454 (ping) procedure. | ||
| Step 3 | If the ping is successful, it demonstrates that an active TCP/IP connection exists. Restart CTC: | ||
| Step 4 |
Using optical test equipment, verify that proper receive levels are achieved. (For instructions about using optical test equipment, refer to the manufacturer documentation.)
|
||
| 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 Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 6 | If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N/STM-N card. | ||
| 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 Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration 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, and troubleshoot any routers between the node and CTC. To verify cable continuity, follow site practices. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CARLOSS (FC)
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: FC
The Carrier Loss for Fibre Channel (FC) alarm occurs on the client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, supporting 1-Gb Fibre Channel (FC1G), 2-Gb FC (FC2G), or 10Gb Fiber Channel (10G Fiber Channel) traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.
Note |
For general information and provisioning MXP and TXP cards, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the CARLOSS (FC) Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CARLOSS (GE)
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GE
The Carrier Loss for Gigabit Ethernet (GE) alarm occurs on the client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, GE-XP, 10GE-XP, or ADM-10G cards supporting 1-Gbps or 10-Gbps traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.
Note |
For general information and provisioning MXP and TXP cards, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the CARLOSS (GE) Alarm
| Step 1 |
Ensure that the GE client is correctly configured:
|
| Step 2 | If there is no PPM (SFP) misprovisioning, check for a fiber cut. An LOS alarm would also be present. If there is an alarm, complete the Clear the LOS (OCN/STMN) Alarm procedure located in Chapter 2, Alarm Troubleshooting, of the Cisco ONS 15454 Troubleshooting Guide or Cisco ONS 15454 SDH Troubleshooting Guide. |
| Step 3 |
If there is no fiber cut or provisioning error, check the client-side equipment for any transmission errors on the line. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CARLOSS (ISC)
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: ISC
The Carrier Loss for Inter-Service Channel (ISC) alarm occurs on:
- The client port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, or MXPP_MR_2.5G card supporting ISC traffic.
The loss can be due to a misconfiguration, fiber cut, or client equipment problem.
Note |
For general information and provisioning MXP and TXP cards, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the CARLOSS (ISC) Alarm
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CARLOSS (TRUNK)
Default Severity:Major (MJ), Service-Affecting (SA)
Logical Object: TRUNK
A Carrier Loss alarm is raised on the optical Trunk-RX port of a TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, and MXPP_MR_2.5G when the Ethernet payload is lost. This alarm only occurs when ITU-T G.709 encapsulation is disabled.
Note |
For general information and provisioning MXP and TXP cards, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the CARLOSS (TRUNK) Alarm
| Step 1 |
Check for any upstream equipment failures:
|
||
| Step 2 | If there is no cause upstream, verify cabling continuity from the transmitting port of the DWDM card (AD-xC-xx.x-xx.x, 32DMX-O, 32DMX, or 40DMX) connected to the TXP receiving port reporting this alarm. | ||
| Step 3 | If a patch panel is used, ensure that the LC-LC adapter managing the connection is in good working order. | ||
| Step 4 | If the continuity is good, clean the fiber according to site practice. If none exists, complete the fiber cleaning procedure in the Manage the Node document. | ||
| Step 5 | If the signal is valid, ensure that the transmit and receive outputs from the patch panel to your equipment are properly connected (that is, the correct wavelength is coming from the patch panel). For more information about fiber connections and terminations, refer to the Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 6 | If the correct port is in service but the alarm has not cleared, use an optical test set to confirm that a valid signal exists on the input port of the alarmed TXP. For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible. | ||
| Step 7 |
If the alarm does not clear, complete the Physically Replace a Card procedure for the reporting card.
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CASETEMP-DEG
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: AOTS
The Case Temperature Degrade alarm is raised when a DWDM card (AD-1B-xx.x, AD-4B-xx.x, 32DMX, 32DMX-O, 40DMX-C, 40DMX-CE, OPT-PRE, OPT-BST, OPT-AMP-C, OPT-AMP-17-C, 40SMR1-C, 40-SMR2-C, and OSC-CSM cards) temperature sensor detects an out-of-range external temperature at the shelf level. The working range for DWDM cards is from 23 degrees F (5 degrees C) to 149 degrees F (65 degrees C).
Note |
For specific temperature and environmental information about each DWDM card, refer to the Hardware Specifications document. |
Clear the CASETEMP-DEG Alarm
| Step 1 | Determine whether the air filter needs replacement. Complete the Inspect, Clean, and Replace the Reusable Air Filter procedure. |
| Step 2 | If the filter is clean, complete the Remove and Reinsert a Fan-Tray Assembly procedure. |
| Step 3 |
If the fan does not run or the alarm persists, complete the Replace the Fan-Tray Assembly procedure. The fan should run immediately when correctly inserted. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CD
Default Severity: Critical (CR) , Service-Affecting (SA)
Logical Object: Trunk port (dir RX)
The Chromatic Dispersion value alarm is raised when the device experiences CD in excess of 3000 ps/nm for 40ME-MXP-C and 40-ME-TXP-C cards, and 29000 ps/nm for 40E-MXP-C and 40E-TXP-C cards.
Clear the CD Alarm
CFM-CONFIG-ERROR
Default Severity: MInor (MN), Non-Service-Affecting (NSA)
Logical Objects: ETH
Clear the CFM-CONFIG-ERROR Condition
CFM-LOOP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: ETH
The Connectivity Fault Management Loop (CFM-LOOP) alarm occurs on GE_XP or 10GE_XP cards when a continuity check (CC) packet is reused in a loop and consequently the same packet is returned to the source.
Clear the CFM-LOOP Condition
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
CFM-MEP-DOWN
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: ETH
The Connectivity Fault Management Maintenance End-Point Down (CFM-MEP-DOWN) alarm occurs in GE_XP, 10GE_XP, GE_XPE or 10GE_XPE cards when two maintenance end points cannot communicate with each other.
Clear the CFM-MEP-DOWN Condition
| Step 1 | Make sure that there are no fiber cuts or other CFM alarms present. |
| Step 2 | In card view, click the Provisioning > CFM > CCDB > Counters tabs. |
| Step 3 |
Ensure that the counter values in the CCM Received field is equivalent to the counter values in the CCM Transmitted field and that the counter is incrementing appropriately. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CFM-XCON-SERVICE
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: ETH
The Connectivity Fault Management Cross-Connect Service (CFM-XCON-SERVICE) occurs in GE_XP, 10GE_XP, GE_XPE and 10GE_XPE cards when the domain are configured incorrectly, and a packet meant for a one domain goes to the other.
Clear the CFM-XCON-SERVICE Condition
| Step 1 | In card view, click the Provisioning > CFM > Configuration > MEP tabs. |
| Step 2 |
Do the following to ensure that the maintenance association and the domain names are the same.
The maintenance profile name and the domain profile name must be the same on both the maintenance end points. |
| Step 3 |
Verify that the MA-Domain Mapping is correct. Click Provisioning > CFM > Configuration > MA-Domain Mapping If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CHANLOSS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: OCN
The SONET Section Layer DCC Termination Failure condition occurs when the ONS 15454 receives unrecognized data in the section layer DCC bytes.
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Clear the CHANLOSS Condition
| Step 1 | In the absence of other alarms, determine whether the alarmed port is connected to another vendor equipment. If so, you can mask the alarm on this path using a custom alarm profile. For more information about custom profiles, refer to the Manage Alarms chapter in the Cisco ONS 15454 Procedure Guide. | ||
| Step 2 |
If alternate vendor equipment is not the cause of the alarm, complete the Reset a Card in CTC procedure for the traffic card.
|
||
| Step 3 |
If the alarm does not clear, complete the Physically Replace a Card procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CLDRESTART
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 power is initialized.
Clear the CLDRESTART Condition
| Step 1 | Complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. |
| Step 2 | If the condition fails to clear after the card reboots, complete the Remove and Reinsert (Reseat) Any Card procedure. |
| Step 3 |
If the condition does not clear, complete the Physically Replace a Card procedure for the card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
COMP-CARD-MISSING
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
When the 100G-LC-C and CFP-LC cards work in a combination, the COMP-CARD-MISSING alarm is raised under any of the following conditions:
Clear the COMP-Card-Missing Alarm
| Step 1 | Add the missing 100G-LC-C or CFP-LC card. If the card is reset, wait for it to boot up. To add a card, see the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
| Step 2 |
Complete the appropriate procedure to clear the following alarms:
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
COMM-FAIL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2/TCC2P/TCC3/TNC/TSC/TNCE/TSCE and the traffic card. The failure could indicate a broken card interface.
Clear the COMM-FAIL Alarm
| Step 1 | Complete the Remove and Reinsert (Reseat) Any Card procedure for the reporting card. |
| Step 2 |
If the alarm does not clear, complete the Physically Replace a Card procedure for the card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CONTBUS-DISABLED
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: EQPT
The CONTBUS-DISABLED alarm is a function of the enhanced cell bus verification feature. This alarm occurs when a card is defective upon insertion into the chassis or when a card already present in the chassis becomes defective. (That is, the card fails the enhanced cell bus verification test.) The alarm persists as long as the defective card remains in the chassis. When the card is removed, CONTBUS-DISABLED will remain raised for a one-minute wait time. This wait time is designed as a guard period so that the system can distinguish this outage from a briefer card reset communication outage.
If no card is reinserted into the original slot during the wait time, the alarm clears. After this time, a different, nondefective card (not the original card) should be inserted.
When CONTBUS-DISABLED is raised, no message-oriented communication is allowed to or from this slot to the TCC2/TCC2P/TCC3 (thus avoiding node communication failure).
Caution |
CONTBUS-DISABLED clears only when the faulty card is removed for one minute. If any card at all is reinserted before the one-minute guard period expires, the alarm does not clear. |
CONTBUS-DISABLED overrides the IMPROPRMVL alarm during the one-minute wait period, but afterward IMPROPRMVL can be raised because it is no longer suppressed. IMPROPRMVL is raised after CONTBUS-DISABLED clears if the card is in the node database. If CONTBUS-DISABLED has cleared but IMPROPRMVL is still active, inserting a card will clear the IMPROPRMVL alarm.
Clear the CONTBUS-DISABLED Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CONTBUS-IO-A
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
A TCCA to Shelf A Slot Communication Failure alarm occurs when the active Slot 7 TCC2/TCC2P/TCC3 (TCC A) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 switches to the protect TCC2/TCC2P/TCC3. In the case of a TCC2/TCC2P/TCC3 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P/TCC3. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P/TCC3 to the reporting card. The physical path of communication includes the TCC2/TCC2P/TCC3, the other card, and the backplane.
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 for the reporting card. |
||
| Step 2 | If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P/TCC3, perform a CTC reset of the object card. Complete the Reset a Card in CTC procedure. For the LED behavior, see the Typical Traffic Card LED Activity During Reset section. | ||
| Step 3 |
If the alarm object is the standby Slot 11 TCC2/TCC2P/TCC3, complete the Reset a Card in CTC procedure for it. The procedure is similar. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.) |
||
| Step 4 |
If CONTBUS-IO-A is raised on several cards at once, complete the Reset an Active TCC2/TCC2P/TCC3 Card and Activate the Standby Card procedure. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. |
||
| Step 5 | Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card. | ||
| Step 6 |
If the CTC reset does not clear the alarm, complete the Remove and Reinsert (Reseat) Any Card procedure for the reporting card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the Technical Support technician tells you to reseat the card, complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the Physically Replace a Card procedure. |
CONTBUS-IO-B
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
A TCC B to Shelf Communication Failure alarm occurs when the active Slot 11 TCC2/TCC2P/TCC3 (TCC B) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-B alarm could appear briefly when the ONS 15454 switches to the protect TCC2/TCC2P/TCC3. In the case of a TCC2/TCC2P/TCC3 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P/TCC3. If the alarm persists, the problem lies with the physical path of communication from the TCC2/TCC2P/TCC3 to the reporting card. The physical path of communication includes the TCC2/TCC2P/TCC3, the other card, and the backplane.
Clear the CONTBUS-IO-B Alarm
| Step 1 |
Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab and view the Eqpt Type column to reveal the provisioned type. If the actual card type and the provisioned card type do not match, see the MEA (EQPT) alarm for the reporting card. |
||
| Step 2 | If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P/TCC3, perform a CTC reset of the object card. Complete the Reset a Card in CTC procedure. For the LED behavior, see the Typical Traffic Card LED Activity During Reset section. | ||
| Step 3 |
If the alarm object is the standby Slot 7 TCC2/TCC2P/TCC3, complete the Reset a Card in CTC procedure for it. The procedure is similar. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.) |
||
| Step 4 |
If CONTBUS-IO-B is raised on several cards at once, complete the Reset an Active TCC2/TCC2P/TCC3 Card and Activate the Standby Card procedure. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. |
||
| Step 5 | Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card. | ||
| Step 6 |
If the CTC reset does not clear the alarm, complete the Remove and Reinsert (Reseat) Any Card procedure for the reporting card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the Technical Support technician tells you to reseat the card, complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the Physically Replace a Card procedure. |
COOL-MISM
Default Severity: Not Reported (NR), Service-Affecting (SA)
Logical Object: FAN
The Cool Mismatch (COOL-MISM) condition is raised when an incorrect cooling profile is chosen for the ONS 15454 M6 shelf. To determine the cooling profile values for the cards, see the "Cooling Profile" section in the "Installing the ONS 15454 M6 Shelf" chapter of the Cisco ONS 15454 Hardware Installation Guide.
Clear the COOL-MISM Alarm
Set the correct cooling profile for the ONS 15454 M6 shelf depending on the cards used.
| Step 1 | Log in to a node on the network. |
| Step 2 | Navigate to Shelf view > Provisioning > General > Voltage/Temperature tabs. |
| Step 3 | From the Cooling Profile drop-down list, choose the correct cooling profile value for the shelf. |
| Step 4 |
Click Apply. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
CP-UNVER-CLEARED Alarm
Default Severity: Minor (MN)
Logical Object: NE
The CP-UNVER-CLEARED alarm is raised under the following conditions:
- When there is a failure in the original path and it is not fixed.
- After all the circuits are moved to the restored path, the port on the original path moves to OOS,DSBLD (ANSI) or Locked,disabled (ETSI) state. These alarms disappear on the original path and unverified alarms appear in Maintenance > DWDM > WSON tabs.
The CP-UNVER-CLEARED alarm is automatically cleared after acknowledging the unverified alarms in the WSON tab.
CTNEQPT-MISMATCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Connection Equipment Mismatch condition is raised when there is a mismatch between the cross-connect card preprovisioned in the slot and the card actually present in the shelf. For example, an XC-VXL card could be preprovisioned in Slot 10, but another card could be physically installed.
Note |
Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation could briefly occur during the upgrade process. |
Note |
The cross-connect card you are replacing should not be the active card. (It can be in SBY state or otherwise not in use.) |
Note |
During an upgrade, this condition occurs and is raised as its default severity, Not Alarmed (NA). However, after the upgrade has occurred, if you wish to change the condition severity so that it is Not Reported (NR), you can do this by modifying the alarm profile used at the node. For more information about modifying alarm severities, refer to the Manage Alarms chapter in the Cisco ONS 15454 Procedure Guide. |
Clear the CTNEQPT-MISMATCH Condition
| Step 1 |
Determine what kind of card is preprovisioned in the slot by completing the following steps:
|
| Step 2 |
Complete the Physically Replace a Card procedure for the mismatched card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DATA-CRC
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: OCH, MSISC
A data cyclic redundancy check (CRC) bad packet count condition occurs when excessive CRC errors are received on the trunk ports of the GE-XP, GE-XPE, 10GE-XP, and 10GE-XPE cards. The DATA-CRC alarm also indicates that frame check sequence (FCS) errors are received on the MS-ISC card port.
The CRC error rate is measured and compared against a configured threshold. The system can be configured to perform an automatic FAPS switch when the DATA-CRC alarm occurs.
Clear the DATA-CRC Alarm
| Step 1 |
For GE-XP, GE-XPE, 10GE-XP, and 10GE-XPE cards, perform the following:
|
| Step 2 |
For MS-ISC cards—Verify the cabling between the TCC2/TCC2P/TCC3 and the MS-ISC card. Correct it if necessary. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
DATAFLT
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: NE
The Software Data Integrity Fault alarm occurs when the TCC2/TCC2P/TCC3 exceeds its flash memory capacity.
Caution |
When the system reboots, the last configuration entered is not saved. |
Clear the DATAFLT Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DBOSYNC
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: NE
The Standby Database Out Of Synchronization alarm occurs when the standby controller card database does not synchronize with the active database on the active controller card.
See the table Table 1 for controller card compatibility matrix.
Caution |
If you reset the active controller card while this alarm is raised, you lose current provisioning. |
Clear the DBOSYNC Alarm
| Step 1 |
Save a backup copy of the active controller card database. Refer to the Maintain the Node chapter in the Cisco ONS 15454 DWDM Configuration Guide. See the table Table 1 for controller card compatibility matrix. |
| Step 2 |
Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm:
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DCU-LOSS-FAIL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OTS
The DCU-LOSS-FAIL condition occurs when the DCU loss monitored value exceeds the maximum acceptable DCU loss of the board (OPT-PRE, OPT-PRE-L, OPT-AMP-L, 40-SMR1-C, or 40-SMR2-C).
Clear the DCU-LOSS-FAIL Condition
| Step 1 | Verify that the optical fibers connecting the board (OPT-PRE, OPT-PRE-L, OPT-AMP-L, 40-SMR1-C, or 40-SMR2-C) and the DCU unit are clean, correctly plugged in, and not damaged. |
| Step 2 | If the condition does not clear, verify that appropriate DCU unit, according to the installation requirements, is connected to the board and is correctly working. |
| Step 3 | If the condition still does not clear, verify that the optical power signal is present on the DCU-TX port. |
| Step 4 | If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DISCONNECTED
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: SYSTEM
The Disconnected alarm is raised when CTC has been disconnected from the node. The alarm is cleared when CTC is reconnected to the node.
Clear the DISCONNECTED Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DSP-COMM-FAIL
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: TRUNK
The Digital Signal Processor (DSP) Communication Failure alarm indicates that there is a communication failure between an MXP or TXP card microprocessor and the on-board DSP chip that controls the trunk (or DWDM) port. This alarm typically occurs after a DSP code upgrade.
The alarm is temporary and does not require user action. The MXP or TXP card microprocessor attempts to restore communication with the DSP chip until the alarm is cleared. (For general information about MXP and TXP cards, refer to the Provision Transponder and Muxponder Cards chapter of the Cisco ONS 15454 DWDM Configuration Guide.)
If the alarm is raised for an extended period, the MXP or TXP card raises the DUP-IPADDR condition and could affect traffic.
Note |
DSP-COMM-FAIL is an informational alarm and does not require troubleshooting. |
DSP-FAIL
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: TRUNK
The DSP Failure alarm indicates that a DSP-COMM-FAIL, has persisted for an extended period on an MXP or TXP card. It indicates that the card is faulty.
Clear the DSP-FAIL Alarm
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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 data communications channel (DCC) area. When this happens, CTC no longer reliably connects to either node. Depending on how the packets are routed, CTC could connect to either node (having the same IP address). If CTC has connected to both nodes before they shared the same address, it has two distinct NodeModel instances (keyed by the node ID portion of the MAC address).
Clear the DUP-IPADDR Alarm
| Step 1 | Isolate the alarmed node from the other node having the same address: |
| Step 2 | In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network > General tabs. |
| Step 3 | In the IP Address field, change the IP address to a unique number. |
| Step 4 | Click Apply. |
| Step 5 |
Restart any CTC sessions that are logged into either of the duplicate IP addresses. (For procedures to log in or log out, refer to the Connect the PC and Log into the GUI document. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DUP-NODENAME
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: NE
The Duplicate Node Name alarm indicates that the alarmed node alphanumeric name is already being used within the same DCC area.
Clear the DUP-NODENAME Alarm
| Step 1 | In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > General > General tabs. |
| Step 2 | In the Node Name field, enter a unique name for the node. |
| Step 3 |
Click Apply. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
DUP-SHELF-ID
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: SHELF
The Duplicated Shelf Identifier alarm applies to a shelf that has multishelf management enabled when the TCC2/TCC2P/TCC3 detects that you have programmed an ID already in use by another shelf. For more information about provisioning an NC shelf or SS shelf for multishelf configurations, refer to the Turn Up a Node and Node Reference chapters in the Cisco ONS 15454 DWDM Configuration Guide.
Clear the DUP-SHELF-ID Alarm
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
EFM-PEER-MISSING
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: GE
The EFM Peer Missing (EFM-PEER-MISSING) alarm occurs in GE_XP or 10GE_XP cards under the following conditions:
Clear the EFM-PEER-MISSING Condition
|
|
EFM-RFI-CE
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GE
The EFM Remote Failure Indication Critical Event (EFM-RFI-CE) alarm is raised if the peer interface defines the RFI CE.
Clear the EFM-RFI-CE Alarm
EFM-RFI-DG
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GE
The EFM Remote Failure Indication Dying Gasp alarm indicates one of the following:
Clear the EFM-RFI-DG Alarm
EFM-RFI-LF
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GE
The EFM Remote Failure Indication Link Fault (EFM-RFI-LF) alarm indicates that the peer interface has a carrier loss.
Clear the EFM-RFI-LF Alarm
|
EFM-RLBK
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: GE
TThe EFM Remote Loopback (EFM-RLBK) alarm indicates that the EFM port is participating in an EFM remote loopback.
Clear the EFM-RLBK Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EHIBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: PWR
The Extreme High Voltage Battery alarm occurs in a 48 VDC environment when a battery lead input voltage exceeds the extreme high power threshold. This threshold, with a default value of 56.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the Turn Up Node chapter in the Cisco ONS 15454 DWDM Configuration Guide.)
Clear the EHIBATVG Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
ELWBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: PWR
The Extreme Low Voltage Battery alarm occurs in a 48 VDC environment when a battery lead input voltage falls below the extreme low power threshold. This threshold, with a default value of 40.5 VDC, is user-provisionable. The alarm remains raised until the voltage remains over the threshold for 120 seconds. (For information about changing this threshold, refer to the Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration Guide.
Clear the ELWBATVG Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
ENCAP-MISMATCH-P
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: STSTRM
The Encapsulation C2 Byte Mismatch Path alarm applies to ML-Series Ethernet cards or the CE-1000 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).
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.
For example, an ENCAP-MISMATCH-P alarm is raised if a circuit created between two ML-Series or two CE-1000 cards has generic framing procedure (GFP) framing provisioned on one end and 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:
This alarm is demoted by a PLM-P condition or a PLM-V condition.
Note |
By default, an ENCAP-MISMATCH-P alarm causes an ML-Series or CE-1000 card data link to go down. This behavior can be modified using the command line interface (CLI) command in interface configuration mode: no pos trigger defect encap. |
Note |
For more information about the ML-Series or CE-1000 Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the ENCAP-MISMATCH-P Alarm
| Step 1 | Ensure that the correct framing mode is in use on the receive card: |
| Step 2 | Ensure that the correct framing mode is in use on the transmit card, and that it is identical to the receiving card: |
| Step 3 |
If the alarm does not clear, use the CLI to ensure that the remaining settings are correctly configured on the ML-Series or CE-1000 card:
To open the interface, click the IOS tab and click Open IOS Command Line Interface (CLI). Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide entries on all three of these topics to obtain the full configuration command sequences. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
EOC
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: OCN/STMN, TRUNK
The SONET DCC Termination Failure alarm occurs when the ONS system loses its DCC. Although this alarm is primarily SONET, it can apply to DWDM. For example, the OSCM card can raise this alarm on its OC-3 section overhead.
The SDCC consists of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS system uses the DCC on the SONET section layer to communicate network management information.
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
If a circuit shows a partial state when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm. |
Note |
For general information about OSCM card, refer to the Setup Optical Service Channel Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. For information about changing their settings, refer to the Change DWDM Card Settings chapter in the same manual.For more information about the SONET (ANSI) or SDH (ETSI) overhead, refer to the SONET Topologies and Upgrades chapter of the Cisco ONS 15454 Procedure Guide or the SDH Topologies and Upgrades chapter of the Cisco ONS 15454 SDH Procedure Guide. |
Note |
The EOC alarm is raised on the DWDM trunk in MSTP systems. Its SDH (ETSI) counterpart, MS-EOC, is not raised against the trunk port. |
Clear the EOC Alarm
| Step 1 |
If the LOS (DS1) alarm or SF-L alarm is reported, complete the appropriate troubleshooting procedure in the Alarm Troubleshooting chapter of the Cisco ONS 15454 Troubleshooting Guide.
|
||
| Step 2 | If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry SDCC traffic. For more information about fiber connections and terminations, refer to the Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 3 | If the physical connections are correct and configured to carry DCC traffic, ensure that both ends of the fiber span have in-service (IS) ports. Verify that the ACT/SBY LED on each card is green. | ||
| Step 4 | When the LEDs on the cards are correctly illuminated, complete the Verify or Create Node Section DCC Terminations procedure to verify that the DCC is provisioned for the ports at both ends of the fiber span. | ||
| Step 5 | Repeat Clear the EOC Alarm procedure at the adjacent nodes. | ||
| Step 6 |
If DCC is provisioned for the ends of the span, verify that the port is active and in service by completing the following steps:
|
||
| 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.
|
||
| Step 8 | If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. Refer to the Hardware Specifications document for card power levels. | ||
| Step 9 | If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information about cabling, refer to the Turn Up a Node chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 10 |
If fiber connectors are properly fastened and terminated, complete the Reset an Active TCC2/TCC2P/TCC3 Card and Activate the Standby Card procedure. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. Resetting the active TCC2/TCC2P/TCC3 switches control to the standby TCC2/TCC2P/TCC3. If the alarm clears when the ONS system node switches to the standby TCC2/TCC2P/TCC3, the user can assume that the previously active card is the cause of the alarm. |
||
| Step 11 |
If the TCC2/TCC2P/TCC3 reset does not clear the alarm, delete the problematic SDCC termination:
|
||
| Step 12 | Recreate the SDCC termination. Refer to the Turn Up a Node chapter of the Cisco ONS 15454 DWDM Configuration Guide for procedures. | ||
| Step 13 |
Verify that both ends of the DCC have been recreated at the optical ports. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the Physically Replace a Card procedure.
|
EOC-E
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: OCN/STMN, FE, GE
The SONET DCC Termination Failure alarm occurs when the ONS system loses its DCC. Although this alarm is primarily SONET, it can apply to DWDM. For example, the OSCM card can raise this alarm on its OC-3 section overhead.
The SDCC consists of three bytes, D1 through D3, in the SONET overhead. The bytes convey information about operation, administration, maintenance, and provisioning (OAM&P). The ONS system uses the DCC on the SONET section layer to communicate network management information.
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
If a circuit shows a partial state when this alarm is raised, the logical circuit is in place. The circuit is able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm. |
Note |
For general information about OSCM card, refer to the Setup Optical Service Channel Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. For information about changing their settings, refer to the Change DWDM Card Settings chapter in the same manual. For more information about the SONET (ANSI) or SDH (ETSI) overhead, refer to the “SONET Topologies and Upgrades” chapter of the Cisco ONS 15454 Procedure Guide or the “SDH Topologies and Upgrades” chapter of the Cisco ONS 15454 SDH Procedure Guide. |
Note |
The EOC alarm is raised on the DWDM trunk in MSTP systems. Its SDH (ETSI) counterpart, MS-EOC, is not raised against the trunk port. |
Clear the EOC-E Alarm
| Step 1 |
If the LOS (DS1) alarm or SF-L alarm is reported, complete the appropriate troubleshooting procedure in the “Alarm Troubleshooting” chapter of the Cisco ONS 15454 Troubleshooting Guide.
|
||
| Step 2 | If the alarm does not clear on the reporting node, verify the physical connections between the cards and that the fiber-optic cables are configured to carry SDCC traffic. For more information about fiber connections and terminations, refer to the “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 3 | If the physical connections are correct and configured to carry DCC traffic, ensure that both ends of the fiber span have in-service (IS) ports. Verify that the ACT/SBY LED on each card is green. | ||
| Step 4 | When the LEDs on the cards are correctly illuminated, complete the “Verify or Create Node Section 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 procedure at the adjacent nodes. | ||
| Step 6 |
If DCC is provisioned for the ends of the span, verify that the port is active and in service by completing the following steps:
|
||
| 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.
|
||
| Step 8 | If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. Refer to the Hardware Specifications document for card power levels. | ||
| Step 9 | If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information about cabling, refer to the “Turn Up a Node” chapter in the Cisco ONS 15454 DWDM Configuration Guide. | ||
| Step 10 |
If fiber connectors are properly fastened and terminated, complete the “Reset an Active TCC2/TCC2P/TNC/TSC Card and Activate the Standby Card” procedure. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. Resetting the active TCC2/TCC2P/TCC3 switches control to the standby TCC2/TCC2P/TCC3. If the alarm clears when the ONS system node switches to the standby TCC2/TCC2P/TCC3, the user can assume that the previously active card is the cause of the alarm. |
||
| Step 11 |
If the TCC2/TCC2P/TCC3 reset does not clear the alarm, delete the problematic SDCC termination:
|
||
| Step 12 | Recreate the SDCC termination. Refer to the “Turn Up a Node” chapter of the Cisco ONS 15454 DWDM Configuration Guide for procedures. | ||
| Step 13 |
Verify that both ends of the DCC have been recreated at the optical ports. If the alarm has not cleared, call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, If the Cisco TAC technician tells you to reseat the card, complete the “Reset an Active TCC2/TCC2P/TNC/TSC Card and Activate the Standby Card” procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the “Physically Replace a Card” procedure.
|
EOC-L
Default Severity: Minor (MN), Non-Service-Affecting (NSA) for OCN/STMN
Logical Object: TRUNK
The Line DCC (LDCC) Termination Failure alarm occurs when the ONS system loses its line data communications channel (LDCC) termination. For example, the OSCM card can raise this alarm on its OC-3 line overhead.
The LDCC consists of nine bytes, D4 through D12, in the SONET overhead. The bytes convey information about OAM&P. The ONS system uses the LDCCs on the SONET line layer to communicate network management information.
Warning |
The laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0). Statement 293 |
Warning |
Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056 |
Warning |
Use of controls, adjustments, or performing procedures other than those specified could result in hazardous radiation exposure. Statement 1057 |
Note |
If a circuit shows a partial status when the EOC or EOC-L alarm is raised, it occurs when the logical circuit is in place. The circuit is able to carry traffic when the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm. |
Note |
For general information about OSCM card, refer to the Setup Optical Service Channel Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. For information about changing their settings, refer to the Change DWDM Card Settings chapter in the same manual. For more information about the SONET (ANSI) or SDH (ETSI) overhead, refer to the SONET Topologies and Upgrades chapter of the Cisco ONS 15454 Procedure Guide or the SDH Topologies and Upgrades chapter of the Cisco ONS 15454 SDH Procedure Guide. |
Clear the EOC-L Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, complete the Remove and Reinsert (Reseat) the Standby TCC2/TCC2P/TCC3 Card procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the Physically Replace a Card procedure.
|
EQPT
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Objects: AICI-AEP, AICI-AIE, 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, refer to the procedure to clear the alarm. (Clearing a BKUPMEMP alarm also clears an EQPT alarm.)
This alarm is also invoked if a diagnostic circuit detects a card application-specific integrated circuit (ASIC) failure. In this case, if the card is part of a protection group, an APS switch occurs. If the card is the protect card, switching is inhibited and a PROTNA, is raised. The standby path generates a path-type alarm. For more information about provisioning PPMs (SFPs), refer to the Installing the GBIC, SFP, SFP+, and XFP Optical Modules in Cisco ONS Platforms document.
Clear the EQPT Alarm
| Step 1 | If traffic is active on the alarmed port, you could need to switch traffic away from it. See the Protection Switching, Lock Initiation, and Clearing procedure for commonly used traffic-switching procedures. | ||
| Step 2 | Complete the Reset a 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/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card. | ||
| Step 4 |
If the CTC reset does not clear the alarm, complete the Remove and Reinsert (Reseat) Any Card procedure for the reporting card.
|
||
| Step 5 |
If the physical reseat of the card fails to clear the alarm, complete the Physically Replace a Card procedure for the reporting card. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
EQPT-DEGRADE
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: EQPT
The Equipment Degrade condition is raised when a permanent failure that limits or compromises the normal behavior of the card (without impact on traffic) is detected.
Clear the EQPT-DEGRADE Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EQPT-DIAG
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: EQPT
An Equipment-Diagnostic Failure alarm indicates that a software or hardware failure has occurred on the reporting card. This alarm can be raised against a traffic card or a cross-connect card.
Clear the EQPT-DIAG Alarm
| Step 1 | If traffic is active on the alarmed card, you could need to switch traffic away from it. Refer to the Protection Switching, Lock Initiation, and Clearing section for procedures. |
| Step 2 | Complete the Remove and Reinsert (Reseat) Any Card procedure for the alarmed card |
| Step 3 |
If the alarm does not clear, complete the Physically Replace a Card procedure if it is raised against a traffic card, or complete the Generic Signal and Circuit Procedures procedure if the alarm is raised against the cross-connect card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EQPT-FAIL
Default Severity: Major (MJ), Non-Service-Affecting (NSA)
Logical Object: EQPT
An Equipment Failure (EQPT-FAIL) alarm is raised when diagnostic circuit detects a card ASIC failure. This alarm indicates that a hardware or communication failure has occurred on the reporting card.
Clear the EQPT-FAIL Alarm
| Step 1 | Complete the "Protection Switching, Lock Initiation, and Clearing" procedure on page 388 if traffic is active on the alarmed port so that you can switch traffic away from it. | ||
| Step 2 | Complete the Reset a 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/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card. | ||
| Step 4 |
If CTC reset does not clear the alarm, complete the Remove and Reinsert (Reseat) Any Card procedure for the reporting card.
|
||
| Step 5 |
If the physical reseat of the card fails to clear the alarm, complete the Physically Replace a Card procedure for the reporting card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EQPT-MISS
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: FAN
The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or is not fully inserted. It could also indicate that the ribbon cable connecting the AIP to the system board is bad.
Caution |
Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly. |
Clear the EQPT-MISS Alarm
| Step 1 | If the alarm is reported against the fan, verify that the fan-tray assembly is present. |
| Step 2 | If the fan-tray assembly is present, complete the Replace the Fan-Tray Assembly procedure. |
| Step 3 | If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the Install the Fan-Tray Assembly procedure in the Cisco ONS 15454 Hardware Installation Guide. |
| Step 4 |
If the alarm does not clear, replace the ribbon cable from the AIP to the system board with a known-good ribbon cable. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
ERFI-P-CONN
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Objects: STSMON, STSTRM
The Three-Bit (Enhanced) Remote Failure Indication (ERFI) Path Connectivity condition is triggered on DS-1, DS-3, or VT circuits when the UNEQ-P and the TIM-P are raised on the transmission signal.
Clear the ERFI-P-CONN Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
ERFI-P-SRVR
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: STSMON, STSTRM
The Three-Bit ERFI Path Server condition is triggered on DS-1, DS-3, or VT circuits when the AIS-P or the LOP-P is raised on the transmission signal.
Clear the ERFI-P-SRVR Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
ESMC-FAIL
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: GE, TRUNK
An Ethernet Synchronization Messaging Channel Fail (ESMC-FAIL) alarm is raised when a SyncE port fails to receive the ESMC protocol data units (PDU) for 5 seconds.
Clear the ESMC-FAIL Alarm
| Step 1 | Verify if the far end port is enabled for SyncE and is sending ESMC PDUs. |
| Step 2 |
Verify if the Ethernet link is up on the client and SA alarms are not present on it. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EVAL-LIC
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Evaluation License (EVAL-LIC) alarm is raised to indicate that an valid evaluation license is in use.
Clear the EVAL-LIC Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EXC-BP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: OTS
The Excessive Back Propagation condition occurs due to excessive backscattered Raman pump power at the LINE-RX connector. This condition is caused either due to a dirty connector, bad optical patch panel connection, or disconnected LINE-RX connector. When the EXC-BP alarm is raised, the level of backscattered power is at a hazardous level, with the risk of possible damage to the unit and/or the external equipment.
Clear the EXC-BP Condition
| Step 1 | Clean the connectors using site practices or, if none exists, complete the procedure in the Maintain the Node chapter of the Cisco ONS 15454 Procedure Guide. |
| Step 2 |
If cleaning the connector does not clear the condition, verify that the power level of the optical signal is within the OC-N card receiver specifications. Refer to the General Troubleshooting chapter in Cisco ONS 15454 Procedure Guide for these specifications. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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 system and CTC could be affected. The network management LAN is the data network connecting the workstation running the CTC software to the TCC2/TCC2P/TCC3. The problem causing the alarm is external to the ONS system.
Troubleshoot the network management LAN connected to the TCC2/TCC2P/TCC3 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 TCC2/TCC2P/TCC3 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 TCC2/TCC2P/TCC3 and the network management LAN. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
EXT
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: ENVALRM
A Failure Detected External to the NE alarm occurs because an environmental alarm is present. For example, a door could be open or flooding could have occurred.
Clear the EXT Alarm
| Step 1 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the AIC-I card to open the card view. |
| Step 2 | Double-click the Maintenance > External Alarms tabs. |
| Step 3 |
Follow your standard operating procedure to remedy environmental conditions that cause alarms. The alarm clears when the situation is remedied. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS
The Failure to Switch to Protection Facility condition for MXP and TXP client ports occurs in a Y-cable protection group when a working or protect facility switches to its companion port by using a MANUAL command. For example, if you attempt to manually switch traffic from an unused protect port to an in-service working port, the switch will fail (because traffic is already present on the working port) and you will see the FAILTOSW condition.
Note |
For more information about protection schemes, refer to the Manage the Node document. |
Clear the FAILTOSW (2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, OTS) Condition
| Step 1 | Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the card and clears the FAILTOSW. |
| Step 2 |
If the condition does not clear, replace the working card that is reporting the higher-priority alarm by following the Physically Replace a Card procedure. This card is the working facility using the protect facility and not reporting FAILTOSW. Replacing the working card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAILTOSW (TRUNK)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: TRUNK
The Failure to Switch to Protection Facility condition applies to MXP and TXP trunk ports in splitter protection groups and occurs when a working or protect trunk port switches to its companion port by using a MANUAL command.
Note |
For more information about protection schemes, refer to the Manage the Node document. |
Clear the FAILTOSW (TRUNK) Condition
| Step 1 | Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the card and clears the FAILTOSW. |
| Step 2 |
If the condition does not clear, replace the working card that is reporting the higher-priority alarm by following the Physically Replace a Card procedure. This card is the working facility using the protect facility and not reporting FAILTOSW. Replacing the working card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAILTOSW-HO
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP
The High-Order Path Failure to Switch to Protection condition occurs when a high-order path circuit fails to switch to the working or protect electrical circuit using the MANUAL command.
Clear the FAILTOSW-HO Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAILTOSW-PATH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: 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 configuration. 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, the LOP-P alarm, the SD-P condition, the SF-P condition, and the UNEQ-P alarm.
The SD-L condition, or the SF-L condition can also occur on the failed path.
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
| Step 1 |
Look up and clear the higher-priority alarm. Clearing this alarm frees the standby card and clears the FAILTOSW-PATH condition. If the AIS-P condition, the LOP-P alarm, the UNEQ-P alarm, the SF-P condition, the SD-P condition, the SD-L condition, or the SF-L condition are also occurring on the reporting port, complete the applicable alarm clearing procedure.
|
||
| Step 2 |
If the condition does not clear, replace the active OC-N card that is reporting the higher-priority alarm. Complete the Physically Replace a Card procedure. Replacing the active OC-N card that is reporting the higher-priority alarm allows traffic to revert to the active slot. Reverting frees the standby card, which can then take over traffic from the card reporting the lower-priority alarm and the FAILTOSW-PATH condition. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAN
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: FAN
The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS system can rise above its normal operating range.
The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the shelf. However, even with five working fans, the fan-tray assembly could need replacement because a sixth working fan is required for extra protection against overheating.
Caution |
Always use the supplied electrostatic discharge wristband when working with a powered ONS system. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly. |
Clear the FAN Alarm
| Step 1 | Determine whether the air filter needs replacement. Complete the Inspect, Clean, and Replace the Reusable Air Filter procedure. |
| Step 2 | If the filter is clean, complete the Remove and Reinsert a Fan-Tray Assembly procedure. |
| Step 3 |
If the fan does not run or the alarm persists, complete the Replace the Fan-Tray Assembly procedure. The fan should run immediately when correctly inserted. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
FAPS
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: TRUNK
The Fast Automatic Protection Switching condition is applicable to GEXP/10GEXP cards. This condition occurs when the protection port, on the master card, switches from blocking to forwarding state.
Clear the FAPS Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FAPS-CONFIG-MISMATCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Fast Automatic Protection Switching (FAPS) Config Mismatch condition is raised when a GE-XP or 10GE-XP card that is provisioned as a master card in a FAPS ring, resets or when one of the master card’s trunk port is not set to Blocking.
Clear the FAPS-CONFIG-MISMATCH Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FC-NO-CREDITS
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Objects: Client port
The Fibre Channel Distance Extension Credit Starvation alarm occurs on storage access networking (SAN) Fibre Channel/Fiber Connectivity (FICON) DWDM cards when the congestion prevents the GFP transmitter from sending frames to the DWDM card port. For example, the alarm can be raised when an operator configures a card to autodetect framing credits but the card is not connected to an interoperable FC-SW-standards-based Fibre Channel/FICON port.
FC-NO-CREDITS is raised only if transmission is completely prevented. (If traffic is slowed but still passing, this alarm is not raised.)
Clear the FC-NO-CREDITS Alarm
| Step 1 | If the port is connected to a Fibre Channel/FICON switch, make sure it is configured for interoperation mode using the manufacturer's instructions. | ||
| Step 2 |
If the port is not connected to a switch, turn off Autodetect Credits by completing the following steps:
|
||
| Step 3 |
Program the Credits Available value based on the buffers available on the connected equipment by completing the following steps:
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
FDI
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: OCH, OCH-TERM, OMS, OTS, EQPT
The Forward Defect Indication (FDI) condition is part of MSTP network-level alarm correlation in R7.0. It is raised at the far end when the OCH optical payload is missing due to an optical channel signal (LOS), light (LOS-P), or optical power (OPWR-LFAIL) alarm root cause.
An LOS, LOS-P, or OPWR-LFAIL alarm on an MSTP circuit causes multiple alarms for each channel. Correlation simplifies troubleshooting by reporting a single alarm for multiple alarms having one root cause, then demoting the root alarms so that they are only visible in the Conditions window (showing their original severity.)
FDI clears when the optical channel is working on the aggregated or single-channel optical port.
Note |
Network-level alarm correlation is only supported for MSTP communication alarms. It is not supported for equipment alarms. |
Clear the FDI Condition
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FE-FRCDWKSWBK-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STMN
The Far End Forced Switch Back to WorkingSpan condition is raised on a far-end 1+1 protect port when it is Force switched to the working port.
Note |
WKSWBK-type conditions apply only to nonrevertive circuits. |
Clear the FE-FRCDWKSWBK-SPAN Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FE-FRCDWKSWPR-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STMN
The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber BLSR is forced from working to protect using the Force Span command. This condition is only visible on the network view Conditions tab. The port where the Force Switch occurred is indicated by an F on the network view detailed circuit map. This condition is accompanied by WKSWPR.
Clear the FE-FRCDWKSWPR-SPAN Condition
| Step 1 | To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the OC-48 card in Slot 12 of Node 1 could link to the main AIS condition from an OC-48 card in Slot 6 of Node 2. |
| Step 2 | Log into the node that links directly to the card reporting the FE condition. |
| Step 3 | Clear the main alarm. |
| Step 4 |
If the FE-FRCDWKSWPR-SPAN condition does not clear, complete the Clear a BLSR External Switching Commandprocedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FE-MANWKSWBK-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STMN
The Far End Manual Switch Back to WorkingSpan condition occurs when a far-end span is Manual switches back to working.
Note |
WKSWBK-type conditions apply only to nonrevertive circuits. |
Clear the FE-MANWKSWBK-SPAN Condition
| Step 1 | To troubleshoot the FE condition, determine which node and card is linked directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2. |
| Step 2 | Log into the node that is linked directly to the card reporting the FE condition. |
| Step 3 |
Complete the Clear a BLSR External Switching Command procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FE-MANWKSWPR-SPAN
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: STMN
The Far-End Span Manual Switch Working Facility to Protect condition occurs when a four-fiber BLSR span is switched from working to protect at the far-end node using the Manual Span command. This condition is only visible on the network view Conditions tab and is accompanied by WKSWPR. The port where the Manual Switch occurred is indicated by an M on the network view detailed circuit map.
Clear the FE-MANWKSWPR-SPAN Condition
| Step 1 | To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE condition on a card in Slot 12 of Node 1 could link to the main condition from a card in Slot 6 of Node 2. |
| Step 2 | Log into the node that links directly to the card reporting the FE condition. |
| Step 3 |
Complete the Clear a BLSR External Switching Command procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FEC-MISM
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: TRUNK
The Forward Error Correction (FEC) Mismatch alarm applies to all cards featuring FEC/E-FEC capability: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_10G, MXP_MR_10E, ADM-10G, and OTU2_XP. FEC-MISMATCH is reported only on the card configured in Standard FEC mode or with FEC disabled. A card configured in enhanced FEC mode will report an OTUK-LOF alarm.
The alarm is related to ITU-T G.709 encapsulation and is only raised against a trunk port.
Note |
For general information about MXP and TXP cards and their monitoring capabilities and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the FEC-MISM Alarm
| Step 1 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_10G, MXP_MR_10E, ADM-10G, and OTU2_XP card. |
| Step 2 | Click the Provisioning > OTN > OTN Lines tabs. |
| Step 3 | In the FEC column, click Enable to activate the FEC feature. This causes a different OTN frame to be transmitted. Alternately, in the E-FEC column (TXP_MR_10E and MXP_MR_10E), click Enable to activate the Enhanced FEC feature. |
| Step 4 |
Verify that the far-end card is configured the same way by repeating 1 through 3. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
FEPRLF
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: OCN
The Far-End Protection Line Failure alarm occurs when there was an SF (TRUNK) condition on the protect card APS channel coming into the node.
Note |
The FEPRLF alarm occurs on the ONS 15454 only when bidirectional protection is used on optical (traffic) cards in a 1+1 protection group configuration. |
Clear the FEPRLF Alarm on an BLSR
| Step 1 | To troubleshoot the FE alarm, determine which node and card is linked directly to the card reporting the FE alarm. For example, an FE alarm or condition on a card in Slot 16 of Node 1 could relate to a main alarm from a card in Slot 16 in Node 2. |
| Step 2 | Log into the node that is linked directly to the card reporting the FE alarm. |
| Step 3 |
Clear the main alarm. Refer to the appropriate alarm section in this chapter for procedures. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FIBERTEMP-DEG
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: AOTS
The Fiber Temperature Degrade alarm occurs when a DWDM card (AD-1B-xx.x, AD-4B-xx.x, 32DMX, 32DMX-O, 40DMX-C, 40DMX-CE, OPT-PRE, OPT-BST, OPT-AMP-C, OPT-AMP-17-C, 40SMR1-C, 40-SMR2-C, and OSC-CSM cards) internal heater-control circuit fails. Degraded temperature can cause some signal drift.
Clear the FIBERTEMP-DEG Alarm
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FIPS_TEST_FAILED
Default Severity: Critical (CR)
Logical Object: EQPT
The FIPS Test Failed alarm is raised on the WSE card. This alarm is raised when the FIPS test fails on the WSE card.
A secure library is used for the FIPS test. A self-test is run on the card during startup to check that the library works with all the algorithms that are supported by FIPS. The FIPS TEST Failed alarm is raised when there is an issue during the self-test on the card.
Clearing the FIPS_TEST_FAILED Alarm
You must have Security super user privileges to clear the alarm.
| Step 1 |
Complete the Reset a Card in CTC procedure for the card.
|
||
| Step 2 |
If the alarm does not clear, complete the Physically Replace a Card procedure. If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html or call the Cisco Technical Assistance Center (1 800 553-2447) to report the problem. |
FORCED-REQ
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT, ML1000, ML100T, MLFX, STSMON, VT-MON
The Force Switch Request on Facility or Port condition occurs when you enter the Force command on a port to force traffic from a working port to a protect port or protection span (or from a protect port to a working port or span). You do not need to clear the condition if you want the Force switch to remain.
FORCED-REQ is raised for an IEEE 802.17b-based RPR span if the force was requested in the Cisco IOS CLI using the rpr-ieee protection request force-switch {east | west} command. It clears from the RPR-IEEE span when you remove the switch in the CLI. For the IEEE 802.17b-based RPR interface, FORCED-REQ is suppressed by the RPR-PASSTHR alarm. It also suppresses the following alarms:
Clear the FORCED-REQ Condition
| Step 1 | Complete the Clear a 1+1 Force or Manual Switch Command procedure. |
| Step 2 |
If the condition is raised on an IEEE 802.17b-based RPR span, enter the following command in the CLI in RPR-IEEE interface configuration mode: router(config-if)#no rpr-ieee protection request force-switch {east | west} If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html or call the Cisco Technical Assistance Center (1 800 553-2447) to report the problem. |
FORCED-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN, OTS)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: 2R, ESCON, FC, GE, ISC, OCN/STMN, OTS
The Force Switch Request Span condition applies to Y-cable-protected TXP configurable clients (OC-3, OC-12/STM-4,OC-48/STM-16, OC-192/STM-64, FC, ESCON, or FICON). If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by FORCED TO WORKING), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.
Note |
For more information about protection schemes, refer to the Manage the Node document. |
FORCED-REQ-SPAN (TRUNK)
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: TRUNK
The Force Switch Request Span condition applies to MXP and TXP trunk ports in splitter protection groups. If traffic is present on a working port and you use the FORCE command to prevent it from switching to the protect port (indicated by FORCED TO WORKING), FORCED-REQ-SPAN indicates this force switch. In this case, the force is affecting not only the facility, but the span.
Note |
For more information about protection schemes, refer to the Manage the Node document. |
FP-LINK-LOSS
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Front Port Link Loss condition occurs when a LAN cable is not connected to the front port of the TCC2/TCC2P/TCC3 card.
Clear the FP-LINK-LOSS Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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 and does not require troubleshooting. |
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 and does not require troubleshooting. |
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 and does not require troubleshooting. |
FRCDSWTOTHIRD
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: EXT-SREF, NE-SREF
The Force Switch to Third Timing Source condition occurs when the user issues a Force command to switch to a third timing source.
Note |
FRCDSWTOTHIRD is an informational condition and does not require troubleshooting. |
FRNGSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: NE-SREF
The Free Running Synchronization Mode condition occurs when the reporting ONS system 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 building integrated timing supply (BITS) timing source. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS system node relying on an internal clock.
Note |
If the ONS system is configured to operate from its internal clock, disregard the FRNGSYNC condition. |
Clear the FRNGSYNC Condition
| Step 1 | If the ONS system is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the Timing chapter in the Cisco ONS 15454 Reference Manual for more information. |
| 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 and the SYNCSEC alarm. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
FSTSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: NE-SREF
A Fast Start Synchronization Mode condition occurs when the node is choosing a new timing reference. The previous timing reference has failed.
The FSTSYNC alarm disappears after approximately 30 seconds.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447).
Note |
FSTSYNC is an informational condition. It does not require troubleshooting. |
FTA-MISMATCH
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: EQPT
The Fan Tray Mismatch condition is raised on the ADM-10G card and OTU2_XP. It indicates that an unsupported version of the fan tray assembly (15454-FTA3 or 15454-FTA2) is installed in the shelf. The ADM-10G and OTU2_XP card must be installed in a shelf that has FTA version 4 or higher.
Clear the FTA-MISMATCH Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GAIN-HDEG
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: AOTS
The Gain High Degrade alarm is raised on an amplifier card (OPT-BST, OPT-PRE, or OPT-AMP-x-C), 40-SMR1-C, or 40-SMR2-C card when the amplifier reaches the Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 2 dBm higher than the setpoint.
Note |
This alarm is applicable only when the amplifier working mode is set to Control Gain. |
Note |
For basic information about amplifier cards and to change their settings, refer to the Optical Amplifier Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GAIN-HDEG Alarm
| Step 1 | Verify that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card. | ||||||
| Step 2 | Complete the Reset a Card in CTC procedure on the failing amplifier. | ||||||
| Step 3 |
If the alarm does not clear, identify all the OCHNC circuits applying to the failing card. Force all the protected circuits on the optical path that the faulty amplifier does not belong to. Switch the OCHNC administrative state of all these circuits to OOS,DSBLD (or Locked,disabled).
|
||||||
| Step 4 | Switch the administrative state of only one of the OCHNC circuits to IS,AINS (or Unlocked,automaticInService). This forces the amplifier to recalculate its gain setpoint and value. | ||||||
| Step 5 | If the alarm does not clear and no other alarms exist that could be the source of the GAIN-HDEG alarm, or if clearing an alarm did not clear the GAIN-HDEG, place all of the card ports in OOS,DSBLD (or Locked,disabled) administrative state. | ||||||
| Step 6 |
Complete the Physically Replace a Card procedure for the reporting card.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GAIN-HFAIL
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: AOTS
The Gain High Degrade alarm is raised on an amplifier card (OPT-BST, OPT-PRE, or OPT-AMP-x-C) when the amplifier reaches the Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 5 dBm higher than the setpoint.) The GAIN-HFAIL alarm is also raised on the 40-SMR1-C and 40-SMR2-C cards. If the alarm cannot be cleared, the card must be replaced.
Note |
This alarm is applicable only when the amplifier working mode is set to Control Gain. |
Note |
For basic information about amplifier cards and to change their settings, refer to the Optical Amplifier Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GAIN-HFAIL Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
GAIN-LDEG
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: AOTS
The Gain High Degrade alarm is raised on an amplifier card (OPT-BST, OPT-PRE, or OPT-AMP-x-C), 40-SMR1-C, or 40-SMR2-C card when the amplifier does not reach Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 2 dBm lower than the setpoint.)
Note |
This alarm is applicable only when the amplifier working mode is set to Control Gain. |
Note |
For basic information about amplifier cards and to change their settings, refer to the Optical Amplifier Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GAIN-LDEG Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GAIN-LFAIL
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: AOTS
The Gain High Degrade alarm is raised on an amplifier card (OPT-BST, OPT-PRE, or OPT-AMP-x-C) when the amplifier does not reach Gain High Degrade Threshold. (This value is automatically provisioned with the gain setpoint, but the alarm threshold is 5 dBm lower than the setpoint. If the alarm cannot be cleared, the card must be replaced.
Note |
This alarm is applicable only when the amplifier working mode is set to Control Gain. |
Note |
For basic information about amplifier cards and to change their settings, refer to the Optical Amplifier Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GAIN-LFAIL Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GCC-EOC
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Object: TRUNK, EQPT
The GCC Embedded Operation Channel Failure alarm applies to the optical transport network (OTN) communication channel for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, MXP_2.5G_10E, ADM-10G, and OTU2_XP cards. The GCC-EOC alarm is raised when the channel cannot operate.
This alarm applies to trunk ports only when ITU-T G.709 encapsulation is enabled and a general communication channel (GCC) has been provisioned between the two TXP/MXP cards.
Note |
For more information about GCC circuits, refer to the Create Optical Channel Circuits and Provisionable Patchcords chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GCC-EOC Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GE-OOSYNC (FC, GE, ISC)
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Objects: FC, GE, ISC
The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G,TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G,TXPP_MR_2.5G,MXP_MR_2.5G, MXPP_MR_2.5G, GE-XP, 10GE, and ADM-10G cards when the Ethernet signal incoming on the Client-Rx port is out of synchronization.
Note |
For general information about MXP and TXP cards and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GE-OOSYNC (FC, GE, ISC) Alarm
| Step 1 | Ensure that the incoming signal from the Client-Rx port is provisioned with the correct physical-layer protocol (Ethernet). |
| Step 2 | Ensure that the line is provisioned with the correct line speed (10G or 1G Ethernet). |
| Step 3 |
Verify that the optical power and the optical signal-to-noise range (OSNR) of the incoming Client-Rx port optical signal are within the accepted ranges. You can find XFP/SFP ranges in the Installing the GBIC, SFP, SFP+, and XFP Optical Modules in Cisco ONS Platforms document. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
GE-OOSYNC (TRUNK)
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Objects: TRUNK
The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G,TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G,TXPP_MR_2.5G,MXP_MR_2.5G, MXPP_MR_2.5G, GE-XP, 10GE, and ADM-10G cards only when the ITU-T G.709 encapsulation framer is disabled.
Note |
For general information about MXP and TXP cards and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the GE-OOSYNC (TRUNK) Alarm
| Step 1 | Verify that ITU-T G.709 encapsulation is disabled: |
| Step 2 | For the TRUNK-RX port, double-click the card and click the Performance > OTN PM > FEC PM tabs. If post-FEC errors are present, troubleshoot this problem first. If not, move to next step. |
| Step 3 |
Verify the status of far-end TXP/MXP connected to the faulty near-end card. Look for any alarms reported by the Client-Rx port of far-end card. If these alarms exist, troubleshoot them. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
GFP-CSF
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: CEMR, CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP Client Signal Fail Detected alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on CE-100T-8, CE-1000-4, CE-MR-10, FC_MR-4, ML100T, ML1000, ML100X-8, ML-MR-10, MXP_MR_25G, and MXPP_MR_25G GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a CARLOSS, LOS, or SYNCLOSS alarm caused by an event such as a pulled receive cable is affecting a remote data port's transmission capability. This alarm can be demoted when a facility loopback is placed on the FC_MR-4 port.
Note |
For general information about MXP and TXP cards and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Note |
For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the GFP-CSF Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
GFP-CSF-SIGLOSS
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GFP-FAC
The GFP Client Signal Fail due to Sigloss is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on AR_MXP and AR_XP GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a SIGLOSS alarm caused by an event is affecting a remote data port's transmission capability.
Clear the GFP-CSF-SIGLOSS Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GFP-CSF-SYNCLOSS
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: GFP-FAC
The GFP Client Signal Fail Due to Syncloss alarm is a secondary alarm raised on local GFP data ports when a remote Service-Affecting (SA) alarm causes invalid data transmission. The alarm is raised locally on AR_MXP and AR_XP GFP data ports and does not indicate that a Service-Affecting (SA) failure is occurring at the local site, but that a SYNCLOSS alarm caused by an event such as a pulled receive cable is affecting a remote data port's transmission capability.
Clear the GFP-CSF-SYNCLOSS Alarm
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
GFP-LFD
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: CEMR, CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP Loss of Frame Delineation alarm applies to Fibre Channel, FICON GFP, and Ethernet ports. This alarm occurs if there is a faulty SONET connection, if SONET path errors cause GFP header errors in the check sum calculated over payload length (PLI/cHEC) combination, or if the GFP source port sends an invalid PLI/cHEC combination. This loss causes traffic stoppage.
Note |
For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the GFP-LFD Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
GFP-UP-MISMATCH
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: CEMR, CE1000, CE100T, FCMR, GFP-FAC, ML1000, ML100T, MLFX
The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the remote port media type. For example, the local port media type could be set to Fibre Channel—1 Gbps ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL or FICON—2 Gbps ISL.
Note |
For more information about Ethernet cards, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the GFP-UP-MISMATCH Alarm
| Step 1 | Ensure that the transmit port and receive port are identically provisioned for distance extension by completing the following steps: |
| Step 2 |
Ensure that both ports are set for the correct media type. For each port, complete the following steps:
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
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 OSPF HELLO packet loss over the DCC.
Clear the HELLO Alarm
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HIBATVG
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: PWR
The High Voltage Battery alarm occurs in a –48 VDC environment when a battery lead input voltage exceeds the high power threshold. This threshold, with a default value of –52 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds.
Clear the HIBATVG Alarm
|
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
Trouble-Clearing Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.
Note |
When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner of the GUI is not indented. If it is, click it to turn it off. When you are done checking for alarms, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the Alarm and TCA Monitoring and Management document. |
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 Alarm and TCA Monitoring and Management document. |
Note |
When an entity is put in the OOS,MT administrative state, the ONS 15454 suppresses all standing alarms on that entity. All alarms and events appear on the Conditions tab. You can change this behavior for the LPBKFACILITY and LPBKTERMINAL alarms. To display these alarms on the Alarms tab, set the NODE.general.ReportLoopbackConditionsOnPortsInOOS-MT to TRUE on the NE Defaults tab. |
- HI-BER
- HI-CCVOLT
- HI-LASERBIAS
- HI-LASERTEMP
- HI-RXPOWER
- HITEMP
- HI-TXPOWER
- HLDOVRSYNC
- HP-DEG
- HP-ENCAP-MISMATCH
- HP-EXC
- HP-PLM
- HP-RFI
- HP-TIM
- HP-UNEQ
- I-HITEMP
- ILK-FAIL
- IMPROPRMVL
- INHSWPR
- INHSWWKG
- INCOMPATIBLE-SEND-PDIP
- INCOMPATIBLE-SW
- INTRUSION-PSWD
- INVALID-MUXCONF
- INVMACADR
- ISIS-ADJ-FAIL
- KEY_EX_FAIL
- KEY_WRITE_FAIL
- LASER-APR
- LASER-OFF-WVL-DRIFT
- LASERBIAS-DEG
- LASERBIAS-FAIL
- LASEREOL
- LASERTEMP-DEG
- LICENSE-EXPIRED
- LIC-EXPIRING-SHORTLY
- LIC-EXPIRING-SOON
- LIC-MISSING
- LMP-FAIL
- LMP-SD
- LMP-SF
- LMP-UNALLOC
- LOCAL-FAULT
- LOCKOUT-REQ
- LOCKOUT-REQ (2R, EQPT, ESCON, FC, GE, ISC)
- LOCKOUT-REQ (TRUNK)
- LOF (BITS)
- LOF (TRUNK)
- LOGBUFR90
- LOGBUFROVFL
- LO-LASERBIAS
- LO-LASERTEMP
- LOM
- LOP-P
- LO-RXPOWER
- LOS (2R)
- LOS (BITS)
- LOS (ESCON)
- LOS (ISC)
- LOS (OTS)
- LOS (TRUNK)
- LOS-O
- LOS-P (AOTS, OMS, OTS)
- LOS-P (OCH)
- LOS-P (TRUNK)
- LOS-RAMAN (OTS)
- LO-TXPOWER
- LPBKCRS
- LPBKFACILITY (ESCON)
- LPBKFACILITY (FC)
- LPBKFACILITY (GE)
- LPBKFACILITY (ISC)
- LPBKFACILITY (TRUNK)
- LPBKTERMINAL (ESCON)
- LPBKTERMINAL (FC)
- LPBKTERMINAL (GE)
- LPBKTERMINAL (ISC)
- LPBKTERMINAL (TRUNK)
- LWBATVG
- MAN-LASER-RESTART
- MAN-REQ
- MANRESET
- MANSWTOINT
- MANSWTOPRI
- MANSWTOSEC
- MANSWTOTHIRD
- MANUAL-REQ-SPAN (2R, ESCON, FC, GE, ISC, OCN/STMN, OTS)
- MANUAL-REQ-SPAN (TRUNK)
- MEA (AIP)
- MEA (EQPT)
- MEA (FAN)
- MEA (PPM)
- MEA (SHELF)
- MEM-GONE
- MEM-LOW
- MFGMEM
- MS-AIS
- MS-DEG
- MS-EOC
- MS-EXC
- MS-RFI
- MT-OCHNC
- NON-CISCO-PPM
- NOT-AUTHENTICATED
- OCHNC-INC
- OCHTERM-INC
- ODUK-1-AIS-PM
- ODUK-2-AIS-PM
- ODUK-3-AIS-PM
- ODUK-4-AIS-PM
- ODUK-AIS-PM
- ODUK-BDI-PM
- ODUK-LCK-PM
- ODUK-OCI-PM
- ODUK-SD-PM
- ODUK-SF-PM
- ODUK-TIM-PM
- OPEN-SLOT
- OPTNTWMIS
- OPWR-HDEG
- OPWR-HFAIL
- OPWR-LDEG
- OPWR-LFAIL
- OSRION
- OTUK-AIS
- OTUK-BDI
- OTUK-IAE
- OTUK-LOF
- OTUK-SD
- OTUK-SF
- OTUK-TIM
- OUT-OF-BUNDLE
- OUT-OF-SYNC
- OVER-TEMP-UNIT-PROT
- PARAM-MISM
- PAYLOAD-UNKNOWN
- PDI-P
- PEER-CSF
- PEER-NORESPONSE
- PMD-DEG
- PMI
- PORT-COMM-FAIL
- PORT-FAIL
- PPR-BDI
- PPR-FDI
- PPR-MAINT
- PPR-TRIG-EXCD
- PROT-SOFT-VERIF-FAIL
- PROTNA
- PROV-MISMATCH
- PTIM
- PWR-CON-LMT
- PWR-FAIL-A
- PWR-FAIL-B
- PWR-FAIL-RET-A
- PWR-FAIL-RET-B
- PWR-PROT-ON
- RAMAN-G-NOT-REACHED
- REMOTE-FAULT
- REP-LINK-FLAPPING
- REP-NEIHB-ADJ-FAIL
- REP-SEGMENT-FAULT
- RFI
- RFI-L
- RFI-P
- RLS
- ROUTE-OVERFLOW
- RS-EOC
- RS-TIM
- SBYTCC-NEINTCLK
- SD (TRUNK)
- SD-L
- SD-L (TRUNK)
- SD-P
- SDBER-EXCEED-HO
- SEQ_MISMATCH_COUNT
- SF (TRUNK)
- SF-L
- SF-L (TRUNK)
- SF-P
- SFTWDOWN
- SFTWDOWN-FAIL
- SHELF-COMM-FAIL
- SH-IL-VAR-DEG-HIGH
- SH-IL-VAR-DEG-LOW
- SHUTTER-OPEN SHUTTER-OPEN
- SIGLOSS SIGLOSS
- SNTP-HOST
- SOFT-VERIF-FAIL
- SPANLEN-OUT-OF-RANGE
- SPAN-NOT-MEASURED
- SQUELCHED
- SSM-DUS
- SSM-FAIL
- SSM-LNC
- SSM-OFF
- SSM-PRC
- SSM-PRS
- SSM-RES
- SSM-SMC
- SSM-ST2
- SSM-ST3
- SSM-ST3E
- SSM-ST4
- SSM-STU
- SSM-TNC
- SW-MISMATCH
- SWTOPRI
- SWTOSEC
- SWTOTHIRD
- SYNC-FREQ
- SYNCLOSS
- SYNCPRI
- SYNCSEC
- SYNCTHIRD
- SYSBOOT
- TEMP-LIC
- TEMP-MISM
- TIM
- TIM-MON
- TIM-P
- TIM-S
- TRAIL-SIGNAL-FAIL
- TRUNK-ODU-AIS
- TRUNK-PAYLOAD-MISM
- TX-OFF-NON-CISCO-PPM
- UNC-WORD
- UNEQ-P
- UNIT-HIGH-TEMP
- UNQUAL-PPM
- UNREACHABLE-TARGET-POWER
- USBSYNC
- USB-WRITE-FAIL
- UT-COMM-FAIL
- UT-FAIL
- VOA-DISABLED
- VOA-HDEG
- VOA-HFAIL
- VOA-LMDEG
- VOA-LFAIL
- VOLT-MISM
- WAN-SYNCLOSS
- WKSWPR (2R, EQPT, ESCON, FC, GE, ISC, OTS)
- WKSWPR (TRUNK)
- WTR (2R, ESCON, FC, GE, ISC)
- WTR (TRUNK)
- WVL-DRIFT-CHAN-OFF
- WVL-MISMATCH
HI-BER
Default Severity: Major (MJ), Service-Affecting (SA)
SONET Logical Objects: FC, GE
The High Bit Error Rate (HI-BER) alarm is raised on the OTU2_XP card when the client and trunk ports receive 16 or more invalid sync-headers in 125 microseconds. The HI-BER alarm occurs when the OTU2_XP card is configured with 10 GE or 10 G FC payloads.
Clear the HI-BER Alarm
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
HI-CCVOLT
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: BITS
The 64K Composite Clock High NE Voltage alarm occurs when the 64K signal peak voltage exceeds 1.1 VDC.
Clear the HI-CCVOLT Condition
| Step 1 | Lower the source voltage to the clock. |
| Step 2 |
If the condition does not clear, add more cable length or add a 5 dBm attenuator to the cable. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
HI-LASERBIAS
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, PPM, TRUNK
The Equipment High Transmit Laser Bias Current alarm is raised against TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, OC192-XFP, ADM-10G, and OTU2_XP card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.
Laser bias typically starts at about 30 percent of the manufacturer maximum laser bias specification and increases as the laser ages. If the HI-LASERBIAS alarm threshold is set at 100 percent of the maximum, the laser usability has ended. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.
Note |
For general information about MXP and TXP cards and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. Specific values are listed in the Hardware Specifications document. |
Clear the HI-LASERBIAS Alarm
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HI-LASERTEMP
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: EQPT, OCN/STMN, PPM
The Equipment High Laser Optical Transceiver Temperature alarm applies to the TXP, MXP, and ADM-10G cards. HI-LASERTEMP occurs when the internally measured transceiver temperature exceeds the card setting by 35.6 degrees F (2 degrees C). A laser temperature change affects the transmitted wavelength.
When the TXP or MXP card raises this alarm, the laser is automatically shut off. The LOS (OCN/STMN) alarm is raised at the far-end node and the DUP-IPADDR alarm, is raised at the near end. (For instructions to clear either of these alarms, you can also refer to the Alarm Troubleshooting chapter in the Cisco ONS 15454 Troubleshooting Guide or Cisco ONS 15454 SDH Troubleshooting Guide.)
Note |
For general information about MXP and TXP cards and PPMs (SFPs) and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the HI-LASERTEMP Alarm
| Step 1 | In node view (single-shelf mode) or shelf view (multishelf mode), double-click the TXP or MXP card to open the card view. |
| Step 2 | Click the Performance > Optics PM > Current Values tabs. |
| Step 3 | Verify the card laser temperature levels. Maximum, minimum, and average laser temperatures are shown in the Current column entries in the Laser Temp rows. |
| Step 4 | Complete the Reset a Card in CTC procedure for the MXP or TXP card. |
| Step 5 |
If the alarm does not clear, complete the Physically Replace a Card procedure for the reporting MXP or TXP card. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HI-RXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: 2R, ESCON, FC, GE, ISC, OCN/STMN, TRUNK, EQPT
The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G, OC192-XFP, GE-XP, 10GE-XP, ADM-10G, or OTU2_XP card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.
Note |
For general information about MXP and TXP cards, their power levels, and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the HI-RXPOWER Alarm
| Step 1 |
Check the PM of the TRUNK-RX port. Verify that received power is above the optics threshold:
|
| Step 2 | Verify that the Trunk-Rx port is cabled correctly, and clean the fiber connecting the faulty TXP/MXP to the Drop port of the DWDM card (32DMX, 32DMX-O, 40DMX, or AD-xC-xx.x). If no site cleaning practices are available, refer to the fiber cleaning procedure in the Maintain the Node chapter of the Cisco ONS 15454 DWDM Configuration Guide. |
| Step 3 | Determine whether a bulk attenuator is specified by the Cisco Transport Planner design. If so, verify that the proper fixed attenuation value has been used. |
| Step 4 | Using a test set, check the optical power value of the Drop port of the DWDM card (32DMX, 32DMX-O, 40DMX, or AD-xC-xx.x) connected to the faulty TXP/MXP. If the read value is different (+1 dBm or 1 dBm) from the ANS setpoint for Padd&drop-Drop power, move to next step. |
| Step 5 |
Look for and troubleshoot any alarm reported by the DWDM cards belonging to the OCHNC circuit destinating at the faulty TXP/MXP. Possible alarms include amplifier Gain alarms (the GAIN-HDEG alarm, the GAIN-HFAIL alarm, the GAIN-LDEG alarm, or GAIN-LFAIL) alarm; APC alarms (APC-CORR-SKIPPED alarm or APC-OUT-OF-RANGE alarm), or LOS-P alarms on the Add or Drop ports involved in the OCHNC circuit. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
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 system is above 122 degrees F (50 degrees C).
Clear the HITEMP Alarm
| Step 1 |
View the temperature displayed on the ONS system LCD front panel. For example, the ONS 15454 front panel is illustrated in Figure 1.
|
||
| Step 2 | Verify that the environmental temperature of the room is not abnormally high. | ||
| Step 3 | If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS system shelf. | ||
| Step 4 | If airflow is not blocked, physically ensure that blank faceplates fill the ONS system shelf empty slots. Blank faceplates help airflow. | ||
| Step 5 | If faceplates fill the empty slots, determine whether the air filter needs replacement. Refer to the Inspect, Clean, and Replace the Reusable Air Filter procedure. | ||
| Step 6 |
If the fan does not run or the alarm persists, complete the Replace the Fan-Tray Assembly procedure.
If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
HI-TXPOWER
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
Logical Objects: 2R, EQPT, ESCON, FC, GE, ISC, OCN/STMN, PPM, TRUNK
The Equipment High Transmit Power alarm is an indicator on the TXP_MR_E, TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, OC192-XFP, ADM-10G, or OTU2_XP card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold.
Note |
For general information about MXP and TXP cards and provisioning them, refer to the Provision Transponder and Muxponder Cards chapter in the Cisco ONS 15454 DWDM Configuration Guide. |
Clear the HI-TXPOWER Alarm
| Step 1 |
Check the PM of the Trunk-Tx port. Verify that received power is above the optics threshold:
|
||
| Step 2 |
Physically verify, by using a standard power meter that the optical output power is overcoming the expected power threshold. If so, the card should be replaced at first opportunity
|
||
| Step 3 |
Complete the Physically Replace a Card procedure. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HLDOVRSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: NE-SREF
The Holdover Synchronization Mode condition is caused by loss of the primary and second timing references in the node. Timing reference loss occurs when line coding on the timing input is different from the configuration on the node, and it often occurs during the selection of a new node reference clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS system relying on an internal clock.
Clear the HLDOVRSYNC Condition
| Step 1 | Clear additional alarms that relate to timing, such as: |
| Step 2 |
Reestablish a primary and secondary timing source according to local site practice. If none exists, refer to the Turn Up the Network chapter in the Cisco ONS 15454 DWDM Configuration Guide. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HP-DEG
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: VMMON-HP, VCTRM-HP
An HP-DEG condition is similar to the SD (TRUNK) condition, but it applies to the HP layer of the SDH overhead. A HP-DEG alarm travels on the B3 byte of the SDH overhead.
For path protection protected circuits, the BER threshold is user-provisionable and has a range for HP-DEG from 1E–9 dBm to 1E–5 dBm. For MS-SPRing 1+1 and unprotected circuits, the BER threshold value is not user-provisionable and the error rate is hard-coded to 1E–6 dBm.
On path protection configurations, an HP-DEG condition causes a switch from the working card to the protect card at the path level. On MS-SPRing, 1+1, and on unprotected circuits, an HP-DEG condition does not cause switching.
The BER increase that causes the condition is sometimes caused by a physical fiber problem such as a poor fiber connection, a bend in the fiber that exceeds the permitted bend radius, or a bad fiber splice.
HP-DEG clears when the BER level falls to one-tenth of the threshold level that triggered the alarm.
Clear the HP-DEG Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HP-ENCAP-MISMATCH
Default Severity: Critical (CR), Service-Affecting (SA)
Logical Object: VCTRM-HP
The High-Order Path Encapsulation C2 Byte Mismatch alarm applies to ML-Series Ethernet cards. 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 LP-PLM, which must meet all five criteria.) For an HP-ENCAP-MISMATCH 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 situation that would raise an HP-ENCAP-MISMATCH alarm is if a circuit created between two ML-Series cards has 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:
This alarm is demoted by a path label mismatch (PLM) such as LP-PLM.
Note |
By default, an HP-ENCAP-MISMATCH alarm causes an ML-Series 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-Series Ethernet card, refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. |
Clear the HP-ENCAP-MISMATCH Alarm
| Step 1 | Ensure that the correct framing mode is in use on the receiving card by completing the following steps: |
| Step 2 | Ensure that the correct framing mode is in use on the transmit card, and that it is identical to the framing mode used on the receiving card by completing the following steps: |
| Step 3 |
If the alarm does not clear, use the ML-Series card CLI to ensure that the remaining settings are correctly configured:
To open the interface, click the card view IOS tab and click Open IOS Connection. Refer to the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide entries on all three of these topics to obtain the full configuration command sequences. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |
HP-EXC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Objects: VCMON-HP, VCTRM-HP
An HP-EXC condition is similar to the SF (TRUNK) condition, but it applies to the path layer B3 byte of the SONET overhead. It can trigger a protection switch.
The HP-EXC 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 HP-EXC Condition
|
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HP-PLM
The HP-PLM condition is not used in this platform in this release. It is reserved for development.
HP-RFI
Default Severity: Not Reported (NR), Non-Service-Affecting (NSA)
Logical Object: VCMON-HP
The High-Order Remote Failure Indication (RFI) condition indicates that there is a remote failure indication in the high-order (VC-4 or VC-3) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The HP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the HP-RFI condition in the reporting node.
Clear the HP-RFI Condition
| Step 1 | Log into the node at the far end of the reporting ONS 15454. |
| Step 2 | Determine whether there are any related alarms, especially the LOS(STM1E, STMN). |
| Step 3 |
Clear the main alarm. See the appropriate alarm section in this chapter for procedures. If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1 800 553-2447). |
HP-TIM
Default Severities: Critical (CR), Service-Affecting (SA) for VCTRM-HP; Minor (MN), Non-Service-Affecting (NSA) for VCMON-HP
Logical Objects: VCMON-HP, VCTRM-HP
The TIM High-Order TIM Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. HP-TIM occurs when there is a mismatch between the transmitted and received J1 identifier byte in the SONET path overhead. The error can originate at the transmit end or the receive end.
Clear the HP-TIM Alarm
| Step 1 | Use an optical test set capable of viewing SONET path overhead to determine the validity of the J1 byte. For specific procedures to use the test set equipment, consult the manufacturer. Examine the signal as near to the reporting card as possible. |
| Step 2 |
If the output card signal is valid, complete the Clear the SYNCPRI Alarm procedure. If the alarm does not get cleared, you need to report a Service-Affecting (SA) problem. Log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or log into http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html to obtain a directory of toll-free Technical Support numbers for your country. |