Table Of Contents
Alarm Troubleshooting
2.1 Alarm Index by Default Severity
2.1.1 Critical Alarms (CR)
2.1.2 Major Alarms (MJ)
2.1.3 Minor Alarms (MN)
2.1.4 Conditions (NA or NR)
2.2 Alarms and Conditions Indexed By Alphabetical Entry
2.3 Alarm Index by Alarm Type
2.3.1 Alarm Type/Object Definition
2.4 Trouble Notifications
2.4.1 Conditions
2.4.2 Severities
2.5 Safety Summary
2.6 Alarm Procedures
2.6.1 AIS
Clear the AIS Condition
2.6.2 ALS
2.6.3 AMPLI-INIT
Clear the AMPLI-INIT Condition
2.6.4 APC-DISABLED
Clear the APC-DISABLED Alarm
2.6.5 APC-FAIL
Clear the APC-FAIL Alarm
2.6.6 APSB
Clear the APSB Alarm
2.6.7 APSCDFLTK
Clear the APSCDFLTK Alarm
2.6.8 APSC-IMP
Clear the APSC-IMP Alarm
2.6.9 APSCINCON
Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing
2.6.10 APSCM
Clear the APSCM Alarm
2.6.11 APSCNMIS
Clear the APSCNMIS Alarm
2.6.12 AS-CMD
Clear the AS-CMD Condition
2.6.13 AS-MT
Clear the AS-MT Condition
2.6.14 AU-AIS
Clear the AU-AIS Condition
2.6.15 AUD-LOG-LOSS
Clear the AUD-LOG-LOSS Condition
2.6.16 AUD-LOG-LOW
2.6.17 AU-LOF
Clear the AU-LOF Alarm
2.6.18 AU-LOP
Clear the AU-LOP Alarm
2.6.19 AUTOLSROFF
Clear the AUTOLSROFF Alarm
2.6.20 AUTORESET
Clear the AUTORESET Alarm
2.6.21 AUTOSW-AIS-SNCP
Clear the AUTOSW-AIS-SNCP Condition
2.6.22 AUTOSW-LOP-SNCP
Clear the AUTOSW-LOP-SNCP Alarm
2.6.23 AUTOSW-SDBER-SNCP
Clear the AUTOSW-SDBER-SNCP Condition
2.6.24 AUTOSW-SFBER-SNCP
Clear the AUTOSW-SFBER-SNCP Condition
2.6.25 AUTOSW-UNEQ-SNCP (HPMON)
Clear the AUTOSW-UNEQ-SNCP (HPMON) Condition
2.6.26 AUTOSW-UNEQ-SNCP (LPMON)
Clear the AUTOSW-UNEQ-SNCP (LPMON) Alarm
2.6.27 AWG-DEG
Clear the AWG-DEG Alarm
2.6.28 AWG-FAIL
Clear the AWG-FAIL Alarm
2.6.29 AWG-OVERTEMP
Clear the AWG-OVERTEMP Alarm
2.6.30 AWG-WARM-UP
2.6.31 BKUPMEMP
Clear the BKUPMEMP Alarm
2.6.32 CARLOSS (EQPT)
Clear the CARLOSS (EQPT) Alarm
2.6.33 CARLOSS (E-Series)
Clear the CARLOSS (E-Series) Alarm
2.6.34 CARLOSS (G-Series)
Clear the CARLOSS (G-Series) Alarm
2.6.35 CARLOSS (ML-Series)
Clear the CARLOSS (ML-Series) Alarm
2.6.36 CASETEMP-DEG
Clear the CASETEMP-DEG Alarm
2.6.37 CKTDOWN
Clear the CKTDOWN Alarm
2.6.38 CLDRESTART
Clear the CLDRESTART Condition
2.6.39 COMIOXC
Clear the COMIOXC Alarm
2.6.40 COMM-FAIL
Clear the COMM-FAIL Alarm
2.6.41 CONTBUS-A-18
Clear the CONTBUS-A-18 Alarm
2.6.42 CONTBUS-B-18
Clear the CONTBUS-B-18 Alarm
2.6.43 CONTBUS-IO-A
Clear the CONTBUS-IO-A Alarm
2.6.44 CONTBUS-IO-B
Clear the CONTBUS-IO-B Alarm
2.6.45 CTNEQPT-PBPROT
Clear the CTNEQPT-PBPROT Alarm
2.6.46 CTNEQPT-PBWORK
Clear the CTNEQPT-PBWORK Alarm
2.6.47 DATAFLT
Clear the DATAFLT Alarm
2.6.48 DBOSYNC
Clear the DBOSYNC Alarm
2.6.49 DS3-MISM
Clear the DS3-MISM Condition
2.6.50 DSP-COMM-FAIL
2.6.51 DSP-FAIL
Clear the DSP-FAIL Alarm
2.6.52 E3-ISD
2.6.53 EHIBATVG-A
Clear the EHIBATVG-A Alarm
2.6.54 EHIBATVG-B
Clear the EHIBATVG-B Alarm
2.6.55 ELWBATVG-A
Clear the ELWBATVG-A Alarm
2.6.56 ELWBATVG-B
Clear the ELWBATVG-B Alarm
2.6.57 EOC
Clear the EOC Alarm
2.6.58 EQPT
Clear the EQPT Alarm
2.6.59 EQPT-MISS
Clear the EQPT-MISS Alarm
2.6.60 ERROR-CONFIG
Clear the ERROR-CONFIG Alarm
2.6.61 E-W-MISMATCH
Clear the E-W-MISMATCH Alarm with a Physical Switch
Clear the E-W-MISMATCH Alarm in CTC
2.6.62 EXCCOL
Clear the EXCCOL Alarm
2.6.63 EXERCISE-RING-FAIL
Clear the EXERCISE-RING-FAIL Condition
2.6.64 EXERCISE-RING-REQ
2.6.65 EXERCISE-SPAN-FAIL
Clear the EXERCISE-SPAN-FAIL Condition
2.6.66 EXERCISE-SPAN-REQ
2.6.67 EXT
Clear the EXT Alarm
2.6.68 EXTRA-TRAF-PREEMPT
Clear the EXTRA-TRAF-PREEMPT Alarm
2.6.69 FAILTOSW
Clear the FAILTOSW Condition
2.6.70 FAILTOSW-HO
Clear the FAILTOSW-HO Condition
2.6.71 FAILTOSW-LO
Clear the FAILTOSW-LO Condition
2.6.72 FAILTOSWR
Clear the FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration
2.6.73 FAILTOSWS
Clear the FAILTOSWS Condition
2.6.74 FAN
Clear the FAN Alarm
2.6.75 FANDEGRADE
Clear the FANDEGRADE Alarm
2.6.76 FE-AIS
Clear the FE-AIS Condition
2.6.77 FEC-MISM
Clear the FEC-MISM Alarm
2.6.78 FE-DS1-MULTLOS
Clear the FE-DS1-MULTLOS Condition
2.6.79 FE-DS1-NSA
Clear the FE-DS1-NSA Condition
2.6.80 FE-DS1-SA
Clear the FE-DS1-SA Condition
2.6.81 FE-DS1-SNGLLOS
Clear the FE-DS1-SNGLLOS Condition
2.6.82 FE-DS3-NSA
Clear the FE-DS3-NSA Condition
2.6.83 FE-DS3-SA
Clear the FE-DS3-SA Condition
2.6.84 FE-E1-MULTLOS
Clear the FE-E1-MULTLOS Condition
2.6.85 FE-E1-NSA
Clear the FE-E1-NSA Condition
2.6.86 FE-E1-SA
Clear the FE-E1-SA Condition
2.6.87 FE-E1-SNGLLOS
Clear the FE-E1-SNGLLOS Condition
2.6.88 FE-E3-NSA
Clear the FE-E3-NSA Condition
2.6.89 FE-E3-SA
Clear the FE-E3-SA Condition
2.6.90 FE-EQPT-NSA
Clear the FE-EQPT-NSA Condition
2.6.91 FE-EXERCISING-RING
2.6.92 FE-EXERCISING-SPAN
2.6.93 FE-FRCDWKSWPR-RING
Clear the FE-FRCDWKSWPR-RING Condition
2.6.94 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-SPAN Condition
2.6.95 FE-IDLE
Clear the FE-IDLE Condition
2.6.96 FE-LOCKOUTOFPR-SPAN
Clear the FE-LOCKOUTOFPR-SPAN Condition
2.6.97 FE-LOF
Clear the FE-LOF Condition
2.6.98 FE-LOS
Clear the FE-LOS Condition
2.6.99 FE-MANWKSWPR-RING
Clear the FE-MANWKSWPR-RING Condition
2.6.100 FE-MANWKSWPR-SPAN
Clear the FE-MANWKSWPR-SPAN Condition
2.6.101 FEPRLF
Clear the FEPRLF Alarm on an MS-SPRing
2.6.102 FIBERTEMP-DEG
Clear the FIBERTEMP-DEG Alarm
2.6.103 FORCED-REQ
Clear the FORCED-REQ Condition
2.6.104 FORCED-REQ-RING
Clear the FORCED-REQ-RING Condition
2.6.105 FORCED-REQ-SPAN
Clear the FORCED-REQ-SPAN Condition
2.6.106 FRCDSWTOINT
2.6.107 FRCDSWTOPRI
2.6.108 FRCDSWTOSEC
2.6.109 FRCDSWTOTHIRD
2.6.110 FRNGSYNC
Clear the FRNGSYNC Condition
2.6.111 FSTSYNC
2.6.112 FULLPASSTHR-BI
Clear the FULLPASSTHR-BI Condition
2.6.113 GAIN-HDEG
Clear the GAIN-HDEG Alarm
2.6.114 GAIN-LDEG
Clear the GAIN-LDEG Alarm
2.6.115 GCC-EOC
Clear the GCC-EOC Alarm
2.6.116 HI-LASERBIAS
Clear the HI-LASERBIAS Alarm
2.6.117 HI-LASERTEMP
Clear the HI-LASERTEMP Alarm
2.6.118 HI-RXPOWER
Clear the HI-RXPOWER Alarm
2.6.119 HI-RXTEMP
Clear the HI-RXTEMP Alarm
2.6.120 HITEMP
Clear the HITEMP Alarm
2.6.121 HI-TXPOWER
Clear the HI-TXPOWER Alarm
2.6.122 HLDOVRSYNC
Clear the HLDOVRSYNC Alarm
2.6.123 HP-RFI
Clear the HP-RFI Condition
2.6.124 HP-TIM
Clear the HP-TIM Alarm
2.6.125 HP-UNEQ
Clear the HP-UNEQ Alarm
2.6.126 IMPROPRMVL
Clear the IMPROPRMVL Alarm
2.6.127 INC-ISD
2.6.128 INHSWPR
Clear the INHSWPR Condition
2.6.129 INHSWWKG
Clear the INHSWWKG Condition
2.6.130 INTRUSION-PSWD
Clear the INTRUSION-PSWD Condition
2.6.131 INVMACADR
2.6.132 IOSCFGCOPY
2.6.133 KB-PASSTHR
Clear the KB-PASSTHR Condition
2.6.134 LAN-POL-REV
Clear the LAN-POL-REV Condition
2.6.135 LASER-APR
2.6.136 LASERBIAS-DEG
Clear the LASERBIAS-DEG Alarm
2.6.137 LASERBIAS-FAIL
Clear the LASERBIAS-FAIL Alarm
2.6.138 LASEREOL
Clear the LASEREOL Alarm
2.6.139 LASERTEMP-DEG
Clear the LASERTEMP-DEG Alarm
2.6.140 LKOUTPR-S
Clear the LKOUTPR-S Condition
2.6.141 LMP-HELLODOWN
Clear the LMP-HELLODOWN Alarm
2.6.142 LMP-NDFAIL
Clear the LMP-NDFAIL Alarm
2.6.143 LOC
Clear the LOC Alarm
2.6.144 LOCKOUT-REQ
Clear the LOCKOUT-REQ Condition
2.6.145 LOF (BITS)
Clear the LOF (BITS) Alarm
2.6.146 LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
Clear the LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N) Alarm
2.6.147 LO-LASERBIAS
Clear the LO-LASERBIAS Alarm
2.6.148 LO-LASERTEMP
Clear the LO-LASERTEMP Alarm
2.6.149 LOM
Clear the LOM Alarm
2.6.150 LO-RXPOWER
Clear the LO-RXPOWER Alarm
2.6.151 LO-RXTEMP
Clear the LO-RXTEMP Alarm
2.6.152 LOS (BITS)
Clear the LOS (BITS) Alarm
2.6.153 LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
Clear the LOS (DS-3, E-1, E-3, EC-N, STM1E, STM-N) Alarm
2.6.154 LO-TXPOWER
Clear the LO-TXPOWER Alarm
2.6.155 LPBKCRS
Clear the LBKCRS Condition
2.6.156 LPBKDS1FEAC
Clear the LPBKDS1FEAC Condition
2.6.157 LPBKDS3FEAC
Clear the LPBKDS3FEAC Condition
2.6.158 LPBKDS3FEAC-CMD
2.6.159 LPBKFACILITY (DS-3, E-N, STM-N)
Clear the LPBKFACILITY (DS-3, E-N, STM-N) Condition
2.6.160 LPBKFACILITY (G-Series)
Clear the LPBKFACILITY (G-Series) Condition
2.6.161 LPBKTERMINAL (DS-3, E-N, STM-N)
Clear the LPBKTERMINAL (DS-3, E-N, STM-N) Condition
2.6.162 LPBKTERMINAL (G1000-4)
Clear the LPBKTERMINAL (G-Series) Condition
2.6.163 LP-PLM
Clear the LP-PLM Alarm
2.6.164 LP-RFI
Clear the LP-RFI Condition
2.6.165 LP-TIM
Clear the LP-TIM Alarm
2.6.166 LP-UNEQ
Clear the LP-UNEQ Alarm
2.6.167 MAN-REQ
Clear the MAN-REQ Condition
2.6.168 MANRESET
2.6.169 MANSWTOINT
2.6.170 MANSWTOPRI
2.6.171 MANSWTOSEC
2.6.172 MANSWTOTHIRD
2.6.173 MANUAL-REQ-RING
Clear the MANUAL-REQ-RING Condition
2.6.174 MANUAL-REQ-SPAN
Clear the MANUAL-REQ-SPAN Condition
2.6.175 MEA (BP)
Clear the MEA (BP) Alarm
2.6.176 MEA (EQPT)
Clear the MEA (EQPT) Alarm
2.6.177 MEA (FAN)
Clear the MEA (FAN) Alarm
2.6.178 MEM-GONE
2.6.179 MEM-LOW
2.6.180 MFGMEM (Backplane or Fan-Tray Assembly)
Clear the MFGMEM (Backplane or Fan-Tray Assembly) Alarm
2.6.181 MS-AIS
Clear the MS-AIS Condition
2.6.182 MS-RFI
Clear the MS-RFI Condition
2.6.183 MSSP-OOSYNC
Clear the MSSP-OOSYNC Alarm
2.6.184 NO-CONFIG
Clear the NO-CONFIG Alarm
2.6.185 NOT-AUTHENTICATED
2.6.186 ODUK-AIS-PM
Clear the ODUK-AIS-PM Condition
2.6.187 ODUK-BDI-PM
Clear the ODUK-BDI-PM Condition
2.6.188 ODUK-LCK-PM
Clear the ODUK-LCK-PM Condition
2.6.189 ODUK-OCI-PM
Clear the ODUK-OCI-PM Condition
2.6.190 ODUK-SD-PM
Clear the ODUK-SD-PM Condition
2.6.191 ODUK-SF-PM
Clear the ODUK-SF-PM Condition
2.6.192 ODUK-TIM-PM
Clear the ODUK-TIM-PM Condition
2.6.193 OPTNTWMIS
Clear the OPTNTWMIS Alarm
2.6.194 OPWR-HDEG
Clear the OPWR-HDEG Alarm
2.6.195 OPWR-LDEG
Clear the OPWR-LDEG Alarm
2.6.196 OPWR-LFAIL
Clear the OPWR-LFAIL Alarm
2.6.197 OTUK-AIS
Clear the OTUK-AIS Condition
2.6.198 OTUK-BDI
Clear the OTUK-BDI Condition
2.6.199 OTUK-LOF
Clear the OTUK-LOF Alarm
2.6.200 OTUK-SD
Clear the OTUK-SD Condition
2.6.201 OTUK-SF
Clear the OTUK-SF Condition
2.6.202 OTUK-TIM
Clear the OTUK-TIM Alarm
2.6.203 PEER-NORESPONSE
Clear the PEER-NORESPONSE Alarm
2.6.204 PORT-CODE-MISM
Clear the PORT-CODE-MISM Alarm
2.6.205 PORT-COMM-FAIL
Clear the PORT-COMM-FAIL Alarm
2.6.206 PORT-MISMATCH
2.6.207 PORT-MISSING
Clear the PORT-MISSING Alarm
2.6.208 PRC-DUPID
Clear the PRC-DUPID Alarm
2.6.209 PROTNA
Clear the PROTNA Alarm
2.6.210 PTIM
Clear the PTIM Alarm
2.6.211 PWR-A
Clear the PWR-A Alarm
2.6.212 PWR-B
Clear the PWR-B Alarm
2.6.213 PWR-REDUN
Clear the PWR-REDUN Alarm
2.6.214 RAI
Clear the RAI Condition
2.6.215 RCVR-MISS
Clear the RCVR-MISS Alarm
2.6.216 RFI
Clear the RFI Condition
2.6.217 RING-ID-MIS
Clear the RING-ID-MIS Alarm
2.6.218 RING-MISMATCH
Clear the RING-MISMATCH Alarm
2.6.219 RING-SW-EAST
2.6.220 RING-SW-WEST
2.6.221 RSVP-HELLODOWN
Clear the RSVP-HELLODOWN Alarm
2.6.222 RUNCFG-SAVENEED
2.6.223 SD
Clear the SD Condition
2.6.224 SDBER-EXCEED-HO
Clear the SDBER-EXCEED-HO Condition
2.6.225 SF
Clear the SF Condition
2.6.226 SFBER-EXCEED-HO
Clear the SFBER-EXCEED-HO Condition
2.6.227 SFTWDOWN
2.6.228 SH-INS-LOSS-VAR-DEG-HIGH
Clear the SH-INS-LOSS-VAR-DEG-HIGH Alarm
2.6.229 SH-INS-LOSS-VAR-DEG-LOW
Clear the SH-INS-LOSS-VAR-DEG-LOW Alarm
2.6.230 SHUTTER-OPEN
Clear the SHUTTER-OPEN Condition
2.6.231 SNTP-HOST
Clear the SNTP-HOST Alarm
2.6.232 SPAN-SW-EAST
2.6.233 SPAN-SW-WEST
2.6.234 SQUELCH
Clear the SQUELCH Condition
2.6.235 SQUELCHED
Clear the SQUELCHED Condition
2.6.236 SSM-DUS
2.6.237 SSM-FAIL (BITS, STM-N)
Clear the SSM-FAIL (BITS, STM-N) Alarm
2.6.238 SSM-LNC
2.6.239 SSM-OFF (BITS, STM-N)
2.6.240 SSM-PRC
2.6.241 SSM-SETS
2.6.242 SSM-STU (BITS, STM-N)
Clear the SSM-STU (BITS, STM-N) Condition
2.6.243 SSM-TNC (BITS, STM-N)
2.6.244 SWMTXMOD
Clear the SWMTXMOD Alarm
2.6.245 SWTOPRI
2.6.246 SWTOSEC
2.6.247 SWTOTHIRD
2.6.248 SYNC-FREQ (BITS, STM-N)
Clear the SYNC-FREQ (BITS, STM-N) Condition
2.6.249 SYNCPRI
Clear the SYNCPRI Alarm
2.6.250 SYNCSEC
Clear the SYNCSEC Alarm
2.6.251 SYNCTHIRD
Clear the SYNCTHIRD Alarm
2.6.252 SYSBOOT
2.6.253 TIM
Clear the TIM Alarm or Condition
2.6.254 TIM-MON
Clear the TIM-MON Alarm
2.6.255 TPTFAIL (G-Series)
Clear the TPTFAIL (G-Series) Alarm
2.6.256 TPTFAIL (ML-Series)
Clear the TPTFAIL (ML-Series) Alarm
2.6.257 TRMT
Clear the TRMT Alarm on the E1-N-14 Card
2.6.258 TRMT-MISS
Clear the TRMT-MISS Alarm
2.6.259 TU-AIS
Clear the TU-AIS Condition
2.6.260 TU-LOP
Clear the TU-LOP Alarm
2.6.261 TUNDERRUN
Clear the TUNDERRUN Alarm
2.6.262 UNC-WORD
Clear the UNC-WORD Condition
2.6.263 VOA-HDEG
Clear the VOA-HDEG Alarm
2.6.264 VOA-HFAIL
Clear the VOA-HFAIL Alarm
2.6.265 VOA-LDEG
Clear the VOA-LDEG Alarm
2.6.266 VOA-LFAIL
Clear the VOA-LFAIL Alarm
2.6.267 WKSWPR
Clear the WKSWPR Condition
2.6.268 WTR
2.6.269 WVL-MISMATCH
Clear the WVL-MISMATCH alarm
2.7 DWDM and Non-DWDM Card LED Activity
2.7.1 DWDM Card LED Activity After Insertion
2.7.2 Non-DWDM Card LED Activity After Insertion
2.7.3 DWDM Card LED Activity During Reset
2.7.4 Non-DWDM Card LED Activity During Reset
2.7.5 Non-DWDM Cross-Connect LED Activity During Side Switch
2.7.6 Non-DWDM Card LED State After Successful Reset
2.8 Common Procedures in Alarm Troubleshooting
Identify a Ring ID or Node ID Number
Change a Ring ID Number
Change a Node ID Number
Verify Node Visibility for Other Nodes
Verify or Create Node DCC Terminations
Lock Out an MS-SPRing Span
Clear an MS-SPRing Span Lock Out
Clear an SNCP Lockout
Switch Protection Group Traffic with an External Switching Command
Side Switch the Active and Standby Cross-Connect Cards
Clear an External Switching Command
Delete a Circuit
Clear a Loopback
Reset Active TCC2 Card and Activate Standby Card
Reset the Standby TCC2/TCC2P Card
Remove and Reinsert (Reseat) the Standby TCC2
Reset a Traffic Card or Cross-Connect Card in CTC
Verify BER Threshold Level
Physically Replace a Card
Remove and Reinsert (Reseat) a Card
Remove and Reinsert Fan-Tray Assembly
Alarm Troubleshooting
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 SDH alarm and condition. Tables 2-1 through 2-4 provide lists of ONS 15454 SDH alarms organized by severity. Table 2-5 provides a list of alarm organized alphabetically. Table 2-6 provides a list of alarms organized by alarm type.
The troubleshooting procedure for an alarm applies to the Cisco Transport Controller (CTC) version of that alarm. If the troubleshooting procedure does not clear the alarm, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.
For alarm profile information, refer to the Cisco ONS 15454 SDH Procedure Guide.
2.1 Alarm Index by Default Severity
The following tables group alarms and conditions by the severity displayed in the CTC Alarms window in the severity (SEV) column. All severities listed in this manual are the default profile settings. Alarm severities can be altered from default settings for individual alarms or groups of alarms by creating a non-default alarm profile and applying it on a port, card, or shelf basis. All settings (default or user-defined) that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations that do not affect service.
2.1.1 Critical Alarms (CR)
Table 2-1 lists critical alarms.
Table 2-1 Critical Alarm Index
AU-LOP
|
HITEMP (NE)
|
MFGMEM (Backplane or Fan-Tray Assembly)
|
AUTOLSROFF
|
HP-TIM (HpTerm)
|
OPWR-LFAIL
|
AWG-FAIL
|
HP-UNEQ
|
OTUK-LOF
|
AWG-OVERTEMP
|
IMPROPRMVL
|
PORT-CODE-MISM (Release 4.5)
|
BKUPMEMP
|
LOC
|
PORT-COMM-FAIL (Release 4.5)
|
CKTDOWN
|
LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N) (DS-3, EC-N, DWDM client, DWDM trunk, STM1E, E-4)
|
PORT-MISMATCH (Release 4.5)
|
COMIOXC
|
LOM
|
PORT-MISSING (Release 4.5)
|
CTNEQPT-PBPROT
|
LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N) (STM-N, DS-3, E-3, EC-N, DWDM client, DWDM trunk, STM1E, E-4)
|
SWMTXMOD
|
CTNEQPT-PBWORK
|
MEA (BP)
|
TIM Release 4.5)
|
EQPT
|
MEA (EQPT)
|
VOA-HFAIL
|
EQPT-MISS
|
MEA (FAN)
|
VOA-LFAIL
|
FAN
|
|
|
2.1.2 Major Alarms (MJ)
Table 2-2 lists major alarms.
Table 2-2 Major Alarm Index
APC-DISABLED
|
EXTRA-TRAF-PREEMPT
|
PORT-CODE-MISM (Release 4.1)
|
APC-FAIL
|
FANDEGRADE
|
PORT-COMM-FAIL (Release 4.1)
|
APSCM
|
FEC-MISM
|
PORT-MISMATCH (Release 4.1)
|
APSCNMIS
|
GCC-EOC
|
PORT-MISSING (Release 4.1)
|
AU-LOF (for HPTERM)
|
HLDOVRSYNC (Release 4.5)
|
PRC-DUPID
|
CARLOSS (EQPT)
|
INVMACADR
|
RCVR-MISS
|
CARLOSS (E-Series)
|
LASERBIAS-FAIL
|
RING-ID-MIS
|
CARLOSS (G-Series)
|
LOF (BITS)
|
RING-MISMATCH
|
CARLOSS (ML-Series)
|
LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N) (E-1)
|
SYSBOOT
|
CONTBUS-A-18
|
LOS (BITS)
|
TIM for STM1E
|
CONTBUS-B-18
|
LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N) (E-1)
|
TPTFAIL (G-Series)
|
CONTBUS-IO-A
|
LP-PLM (Release 4.1)
|
TPTFAIL (ML-Series)
|
CONTBUS-IO-B
|
LP-TIM (Release 4.1)
|
TRMT
|
DBOSYNC
|
LP-UNEQ
|
TRMT-MISS
|
DSP-COMM-FAIL
|
MEM-GONE
|
TU-LOP
|
DSP-FAIL
|
MSSP-OOSYNC
|
TUNDERRUN
|
EOC
|
OPTNTWMIS
|
WVL-MISMATCH
|
E-W-MISMATCH
|
PEER-NORESPONSE
|
|
2.1.3 Minor Alarms (MN)
Table 2-3 lists minor alarms.
Table 2-3 Minor Alarm Index
APSB
|
GAIN-LDEG
|
MEM-LOW
|
APSCDFLTK
|
HI-LASERBIAS
|
NOT-AUTHENTICATED
|
APSC-IMP
|
HI-LASERTEMP
|
OPWR-HDEG
|
APSCINCON
|
HI-RXPOWER
|
OPWR-LDEG
|
AUTORESET
|
HI-RXTEMP
|
PROTNA
|
AUTOSW-LOP-SNCP
|
HITEMP (for Eqpt)
|
PTIM
|
AUTOSW-UNEQ-SNCP (LPMON)
|
HI-TXPOWER
|
PWR-A
|
AWG-DEG
|
HP-TIM (for HpMon)
|
PWR-B
|
CASETEMP-DEG
|
LASERBIAS-DEG
|
PWR-REDUN
|
COMM-FAIL
|
LASEREOL
|
RSVP-HELLODOWN
|
DATAFLT
|
LASERTEMP-DEG
|
SFTWDOWN
|
EHIBATVG-A
|
LMP-HELLODOWN
|
SH-INS-LOSS-VAR-DEG-HIGH
|
EHIBATVG-B
|
LMP-NDFAIL
|
SH-INS-LOSS-VAR-DEG-LOW
|
ELWBATVG-A
|
LO-LASERBIAS
|
SNTP-HOST
|
ELWBATVG-B
|
LO-LASERTEMP
|
SSM-FAIL (BITS, STM-N) (DWDM client, DWDM trunk, STM1E)
|
ERROR-CONFIG
|
LO-RXPOWER
|
SYNCPRI
|
EXCCOL
|
LO-RXTEMP
|
SYNCSEC
|
EXT
|
LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N) (FUDC, MSUDC)
|
SYNCTHIRD
|
FEPRLF
|
LO-TXPOWER
|
TIM-MON
|
FIBERTEMP-DEG
|
LP-PLM (Release 4.5)
|
VOA-HDEG
|
FSTSYNC
|
LP-TIM (Release 4.5)
|
VOA-LDEG
|
GAIN-HDEG
|
|
|
2.1.4 Conditions (NA or NR)
Table 2-4 lists Not Alarmed or Not Reported conditions.
2.2 Alarms and Conditions Indexed By Alphabetical Entry
Table 2-5 lists alarms and conditions by the name displayed on the CTC Alarms window or Conditions window.
Table 2-5 Alphabetical Alarm Index
AIS
|
FE-EXERCISING-RING
|
MS-AIS
|
ALS
|
FE-EXERCISING-SPAN
|
MS-RFI
|
AMPLI-INIT
|
FE-FRCDWKSWPR-RING
|
MSSP-OOSYNC
|
APC-DISABLED
|
FE-FRCDWKSWPR-SPAN
|
NO-CONFIG
|
APC-FAIL
|
FE-IDLE
|
NOT-AUTHENTICATED
|
APSB
|
FE-LOCKOUTOFPR-SPAN
|
ODUK-AIS-PM
|
APSCDFLTK
|
FE-LOF
|
ODUK-BDI-PM
|
APSC-IMP
|
FE-LOS
|
ODUK-LCK-PM
|
APSCINCON
|
FE-MANWKSWPR-RING
|
ODUK-OCI-PM
|
APSCM
|
FE-MANWKSWPR-SPAN
|
ODUK-SD-PM
|
APSCNMIS
|
FEPRLF
|
ODUK-SF-PM
|
AS-CMD
|
FIBERTEMP-DEG
|
ODUK-TIM-PM
|
AS-MT
|
FORCED-REQ
|
OPTNTWMIS
|
AU-AIS
|
FORCED-REQ-RING
|
OPWR-HDEG
|
AUD-LOG-LOSS
|
FORCED-REQ-SPAN
|
OPWR-LDEG
|
AUD-LOG-LOW
|
FRCDSWTOINT
|
OPWR-LFAIL
|
AU-LOF
|
FRCDSWTOPRI
|
OTUK-AIS
|
AU-LOP
|
FRCDSWTOSEC
|
OTUK-BDI
|
AUTOLSROFF
|
FRCDSWTOTHIRD
|
OTUK-LOF
|
AUTORESET
|
FRNGSYNC
|
OTUK-SD
|
AUTOSW-AIS-SNCP
|
FSTSYNC
|
OTUK-SF
|
AUTOSW-LOP-SNCP
|
FULLPASSTHR-BI
|
OTUK-TIM
|
AUTOSW-SDBER-SNCP
|
GAIN-HDEG
|
PEER-NORESPONSE
|
AUTOSW-SFBER-SNCP
|
GAIN-LDEG
|
PORT-CODE-MISM
|
AUTOSW-UNEQ-SNCP (HPMON)
|
GCC-EOC
|
PORT-COMM-FAIL
|
AUTOSW-UNEQ-SNCP (LPMON)
|
HI-LASERBIAS
|
PORT-MISMATCH
|
AWG-DEG
|
HI-LASERTEMP
|
PORT-MISSING
|
AWG-FAIL
|
HI-RXPOWER
|
PRC-DUPID
|
AWG-OVERTEMP
|
HI-RXTEMP
|
PROTNA
|
AWG-WARM-UP
|
HITEMP
|
PTIM
|
BKUPMEMP
|
HI-TXPOWER
|
PWR-A
|
CARLOSS (EQPT)
|
HLDOVRSYNC
|
PWR-B
|
CARLOSS (E-Series)
|
HP-RFI
|
PWR-REDUN
|
CARLOSS (G-Series)
|
HP-TIM
|
RAI
|
CARLOSS (ML-Series)
|
HP-UNEQ
|
RCVR-MISS
|
CASETEMP-DEG
|
IMPROPRMVL
|
RFI
|
CKTDOWN
|
INC-ISD
|
RING-ID-MIS
|
CLDRESTART
|
INHSWPR
|
RING-MISMATCH
|
COMIOXC
|
INHSWWKG
|
RING-SW-EAST
|
COMM-FAIL
|
INTRUSION-PSWD
|
RING-SW-WEST
|
CONTBUS-A-18
|
INVMACADR
|
RSVP-HELLODOWN
|
CONTBUS-B-18
|
IOSCFGCOPY
|
RUNCFG-SAVENEED
|
CONTBUS-IO-A
|
KB-PASSTHR
|
SD
|
CONTBUS-IO-B
|
LAN-POL-REV
|
SDBER-EXCEED-HO
|
CTNEQPT-PBPROT
|
LASER-APR
|
SF
|
CTNEQPT-PBWORK
|
LASERBIAS-DEG
|
SFBER-EXCEED-HO
|
DATAFLT
|
LASERBIAS-FAIL
|
SFTWDOWN
|
DBOSYNC
|
LASEREOL
|
SH-INS-LOSS-VAR-DEG-HIGH
|
DS3-MISM
|
LASERTEMP-DEG
|
SH-INS-LOSS-VAR-DEG-LOW
|
DSP-COMM-FAIL
|
LKOUTPR-S
|
SHUTTER-OPEN
|
DSP-FAIL
|
LMP-HELLODOWN
|
SNTP-HOST
|
E3-ISD
|
LMP-NDFAIL
|
SPAN-SW-EAST
|
EHIBATVG-A
|
LOC
|
SPAN-SW-WEST
|
EHIBATVG-B
|
LOCKOUT-REQ
|
SQUELCH
|
ELWBATVG-A
|
LOF (BITS)
|
SQUELCHED
|
ELWBATVG-B
|
LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
SSM-DUS
|
EOC
|
LO-LASERBIAS
|
SSM-FAIL (BITS, STM-N)
|
EQPT
|
LO-LASERTEMP
|
SSM-LNC
|
EQPT-MISS
|
LOM
|
SSM-OFF (BITS, STM-N)
|
ERROR-CONFIG
|
LO-RXPOWER
|
SSM-PRC
|
E-W-MISMATCH
|
LO-RXTEMP
|
SSM-SETS
|
EXCCOL
|
LOS (BITS)
|
SSM-STU (BITS, STM-N)
|
EXERCISE-RING-FAIL
|
LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
SSM-TNC (BITS, STM-N)
|
EXERCISE-RING-REQ
|
LO-TXPOWER
|
SWMTXMOD
|
EXERCISE-SPAN-FAIL
|
LPBKCRS
|
SWTOPRI
|
EXERCISE-SPAN-REQ
|
LPBKDS1FEAC
|
SWTOSEC
|
EXT
|
LPBKDS3FEAC
|
SWTOTHIRD
|
EXTRA-TRAF-PREEMPT
|
LPBKDS3FEAC-CMD
|
SYNC-FREQ (BITS, STM-N)
|
FAILTOSW
|
LPBKFACILITY (DS-3, E-N, STM-N)
|
SYNCPRI
|
FAILTOSW-HO
|
LPBKFACILITY (G-Series)
|
SYNCSEC
|
FAILTOSW-LO
|
LPBKTERMINAL (DS-3, E-N, STM-N)
|
SYNCTHIRD
|
FAILTOSWR
|
LPBKTERMINAL (G1000-4)
|
SYSBOOT
|
FAILTOSWS
|
LP-PLM
|
TIM
|
FAN
|
LP-RFI
|
TIM-MON
|
FANDEGRADE
|
LP-TIM
|
TPTFAIL (G-Series)
|
FE-AIS
|
LP-UNEQ
|
TPTFAIL (ML-Series)
|
FEC-MISM
|
MAN-REQ
|
TRMT
|
FE-DS1-MULTLOS
|
MANRESET
|
TRMT-MISS
|
FE-DS1-NSA
|
MANSWTOINT
|
TU-AIS
|
FE-DS1-SA
|
MANSWTOPRI
|
TU-LOP
|
FE-DS1-SNGLLOS
|
MANSWTOSEC
|
TUNDERRUN
|
FE-DS3-NSA
|
MANSWTOTHIRD
|
UNC-WORD
|
FE-DS3-SA
|
MANUAL-REQ-RING
|
VOA-HDEG
|
FE-E1-MULTLOS
|
MANUAL-REQ-SPAN
|
VOA-HFAIL
|
FE-E1-NSA
|
MEA (BP)
|
VOA-LDEG
|
FE-E1-SA
|
MEA (EQPT)
|
VOA-LFAIL
|
FE-E1-SNGLLOS
|
MEA (FAN)
|
WKSWPR
|
FE-E3-NSA
|
MEM-GONE
|
WTR
|
FE-E3-SA
|
MEM-LOW
|
WVL-MISMATCH
|
FE-EQPT-NSA
|
MFGMEM (Backplane or Fan-Tray Assembly)
|
|
2.3 Alarm Index by Alarm Type
Table 2-6 provides the name and page number of every alarm in the chapter organized by alarm type.
Table 2-6 Alarm Index by Alarm Type
AIE:: EQPT
|
AIE:: MFGMEM (Backplane or Fan-Tray Assembly)
|
BITS:: AISx
|
BITS:: LOF (BITS)
|
BITS:: LOS (BITS)
|
BITS:: SSM-DUS
|
BITS:: SSM-FAIL (BITS, STM-N)
|
BITS:: SSM-LNC
|
BITS:: SSM-OFF (BITS, STM-N)
|
BITS:: SSM-PRC
|
BITS:: SSM-SETS
|
BITS:: SSM-STU (BITS, STM-N)
|
BITS:: SSM-TNC (BITS, STM-N)
|
BITS:: SYNC-FREQ (BITS, STM-N)
|
BITS:: SYNCSEC
|
BP:: AS-CMD
|
BP:: INVMACADR
|
BP:: MEA (BP)
|
BP:: MFGMEM (Backplane or Fan-Tray Assembly)
|
CC:: LMP-HELLODOWN
|
CC:: LMP-NDFAIL
|
CKT:: CKTDOWN
|
DS3:: AIS
|
DS3:: AS-CMD
|
DS3:: AS-MT
|
DS3:: DS3-MISM
|
DS3:: FE-AIS
|
DS3:: FE-DS1-MULTLOS
|
DS3:: FE-DS1-NSA
|
DS3:: FE-DS1-SA
|
DS3:: FE-DS1-SNGLLOS
|
DS3:: FE-DS3-NSA
|
DS3:: FE-DS3-SA
|
DS3:: FE-EQPT-NSA
|
DS3:: FE-IDLE
|
DS3:: FE-LOF
|
DS3:: FE-LOS
|
DS3:: IMPROPRMVL
|
DS3:: INC-ISD
|
DS3:: LPBKDS1FEAC
|
DS3:: LPBKDS3FEAC
|
DS3:: LPBKDS3FEAC-CMD
|
DS3:: LPBKFACILITY (DS-3, E-N, STM-N)
|
DS3::LPBKTERMINAL (DS-3, E-N, STM-N)
|
DS3:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
DS3:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
DS3:: RAI
|
DS3:: SD
|
DS3:: SF
|
DWDM Client:: AIS
|
DWDM Client:: ALS
|
DWDM Client:: AS-CMD
|
DWDM Client:: AS-MT
|
DWDM Client:: AUTOLSROFF
|
DWDM Client:: CARLOSS (ML-Series)
|
DWDM Client:: EOC
|
DWDM Client:: FAILTOSW
|
DWDM Client:: FORCED-REQ-SPAN
|
DWDM Client:: GCC-EOC
|
DWDM Client:: HI-LASERBIAS
|
DWDM Client:: HI-LASERTEMP
|
DWDM Client:: HI-RXPOWER
|
DWDM Client:: HI-TXPOWER
|
DWDM Client:: LOCKOUT-REQ
|
DWDM Client:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
DWDM Client:: LO-LASERBIAS
|
DWDM Client:: LO-LASERTEMP
|
DWDM Client:: LO-RXPOWER
|
DWDM Client:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
DWDM Client:: LO-TXPOWER
|
DWDM Client:: LPBKFACILITY (DS-3, E-N, STM-N)
|
DWDM Client:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
DWDM Client:: MANUAL-REQ-SPAN
|
DWDM Client:: PORT-CODE-MISM
|
DWDM Client:: PORT-COMM-FAIL
|
DWDM Client:: PORT-MISMATCH
|
DWDM Client:: PORT-MISSING
|
DWDM Client:: RFI
|
DWDM Client:: SD
|
DWDM Client:: SF
|
DWDM Client:: SQUELCHED
|
DWDM Client:: SSM-DUS
|
DWDM Client:: SSM-FAIL (BITS, STM-N)
|
DWDM Client:: SSM-LNC
|
DWDM Client:: SSM-OFF (BITS, STM-N)
|
DWDM Client::SSM-PRC
|
DWDM Client:: SSM-SETS
|
DWDM Client:: SSM-TNC (BITS, STM-N)
|
DWDM Client:: TIM
|
DWDM Client:: TIM-MON
|
DWDM Client:: WKSWPR
|
DWDM Client:: WTR
|
DWDM Trunk:: AIS
|
DWDM Trunk:: ALS
|
DWDM Trunk:: AS-CMD
|
DWDM Trunk:: AS-MT
|
DWDM Trunk:: CARLOSS (EQPT)
|
DWDM Trunk:: DSP-COMM-FAIL
|
DWDM Trunk:: DSP-FAIL
|
DWDM Trunk:: EOC
|
DWDM Trunk:: FAILTOSW
|
DWDM Trunk:: FEC-MISM
|
DWDM Trunk:: FORCED-REQ-SPAN
|
DWDM Trunk:: GCC-EOC
|
DWDM Trunk:: HI-LASERBIAS
|
DWDM Trunk:: HI-LASERTEMP
|
DWDM Trunk:: HI-RXPOWER
|
DWDM Trunk:: HI-RXTEMP
|
DWDM Trunk:: HI-TXPOWER
|
DWDM Trunk:: LOC
|
DWDM Trunk:: LOCKOUT-REQ
|
DWDM Trunk:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
DWDM Trunk:: LO-LASERBIAS
|
DWDM Trunk:: LO-LASERTEMP
|
DWDM Trunk:: LO-RXPOWER
|
DWDM Trunk:: LO-RXTEMP
|
DWDM Trunk:: LO-TXPOWER
|
DWDM Trunk:: LOM
|
DWDM Trunk:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
DWDM Trunk:: LPBKFACILITY (DS-3, E-N, STM-N)
|
DWDM Trunk:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
DWDM Trunk:: MANUAL-REQ-SPAN
|
DWDM Trunk:: ODUK-AIS-PM
|
DWDM Trunk:: ODUK-BDI-PM
|
DWDM Trunk:: ODUK-LCK-PM
|
DWDM Trunk:: ODUK-OCI-PM
|
DWDM Trunk:: ODUK-SD-PM
|
DWDM Trunk:: ODUK-SF-PM
|
DWDM Trunk:: ODUK-TIM-PM
|
DWDM Trunk:: OTUK-AIS
|
DWDM Trunk:: OTUK-BDI
|
DWDM Trunk:: OTUK-LOF
|
DWDM Trunk:: OTUK-SD
|
DWDM Trunk:: OTUK-SF
|
DWDM Trunk:: OTUK-TIM
|
DWDM Trunk:: PTIM
|
DWDM Trunk:: RFI
|
DWDM Trunk:: SD
|
DWDM Trunk:: SF
|
DWDM Trunk:: SSM-DUS
|
DWDM Trunk:: SSM-FAIL (BITS, STM-N)
|
DWDM Trunk:: SSM-LNC
|
DWDM Trunk:: SSM-OFF (BITS, STM-N)
|
DWDM Trunk:: SSM-PRC
|
DWDM Trunk:: SSM-SETS
|
DWDM Trunk:: SSM-STU (BITS, STM-N)
|
DWDM Trunk:: SSM-TNC (BITS, STM-N)
|
DWDM Trunk:: TIM
|
DWDM Trunk:: TIM-MON
|
DWDM Trunk:: UNC-WORD
|
DWDM Trunk:: WKSWPR
|
DWDM Trunk:: WTR
|
DWDM Trunk:: WVL-MISMATCH
|
E1:: AIS
|
E1:: AS-CMD
|
E1:: AS-MT
|
E1:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
E1:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
E1:: LPBKFACILITY (DS-3, E-N, STM-N)
|
E1:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
E1:: RAI
|
E1:: RCVR-MISS
|
E1:: SD
|
E1:: SF
|
E1:: TRMT
|
E1:: TRMT-MISS
|
E3:: AIS
|
E3:: AS-CMD
|
E3:: AS-MT
|
E3:: DS3-MISM
|
E3:: E3-ISD
|
E3:: FE-AIS
|
E3:: FE-EQPT-NSA
|
E3:: FE-E1-MULTLOS
|
E3:: FE-E1-NSA
|
E3:: FE-E1-SA
|
E3:: FE-E1-SNGLLOS
|
E3:: FE-E3-NSA
|
E3:: FE-E3-SA
|
E3:: FE-IDLE
|
E3:: FE-LOF
|
E3:: FE-LOS
|
E3:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
E3:: LPBKFACILITY (DS-3, E-N, STM-N)
|
E3:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
E3:: SD
|
E3:: SF
|
E4:: AIS
|
E4:: AMPLI-INIT
|
E4:: AS-CMD
|
E4:: AS-MT
|
E4:: AWG-DEG
|
E4:: AWG-FAIL
|
E4:: AWG-OVERTEMP
|
E4:: AWG-WARM-UP
|
E4:: CASETEMP-DEG
|
E4:: FIBERTEMP-DEG
|
E4:: GAIN-HDEG
|
E4:: GAIN-LDEG
|
E4:: LASER-APR
|
E4:: LASERBIAS-DEG
|
E4:: LASERBIAS-FAIL
|
E4:: LASERTEMP-DEG
|
E4:: LOC
|
E4:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
E4:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
E4:: LPBKFACILITY (DS-3, E-N, STM-N)
|
E4:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
E4:: OPWR-HDEG
|
E4:: OPWR-LDEG
|
E4:: OPWR-LFAIL
|
E4:: SH-INS-LOSS-VAR-DEG-HIGH
|
E4:: SH-INS-LOSS-VAR-DEG-LOW
|
E4:: SHUTTER-OPEN
|
E4:: SD
|
E4:: SF
|
E4:: VOA-HDEG
|
E4:: VOA-HFAIL
|
E4:: VOA-LDEG
|
E4:: VOA-LFAIL
|
ECN:: AS-CMD
|
ECN:: AS-MT
|
ECN:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
ECN:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
ECN:: LPBKFACILITY (DS-3, E-N, STM-N)
|
ECN:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
ENV:: EXT
|
EQPT:: AS-CMD
|
EQPT:: AUTORESET
|
EQPT:: BKUPMEMP
|
EQPT:: CARLOSS (EQPT)
|
EQPT:: CLDRESTART
|
EQPT:: COMIOXC
|
EQPT:: COMM-FAIL
|
EQPT:: CONTBUS-A-18
|
EQPT:: CONTBUS-B-18
|
EQPT:: CONTBUS-IO-A
|
EQPT:: CONTBUS-IO-B
|
EQPT:: CTNEQPT-PBPROT
|
EQPT:: CTNEQPT-PBWORK
|
EQPT:: EQPT
|
EQPT:: ERROR-CONFIG
|
EQPT:: EXCCOL
|
EQPT:: FAILTOSW
|
EQPT:: FORCED-REQ
|
EQPT::HITEMP
|
EQPT:: IMPROPRMVL
|
EQPT:: INHSWPR
|
EQPT:: INHSWWKG
|
EQPT:: IOSCFGCOPY
|
EQPT:: LOCKOUT-REQ
|
EQPT:: MAN-REQ
|
EQPT:: MANRESET
|
EQPT:: MEA (EQPT)
|
EQPT:: MEM-GONE
|
EQPT:: MEM-LOW
|
EQPT:: NO-CONFIG
|
EQPT:: PEER-NORESPONSE
|
EQPT:: PROTNA
|
EQPT:: PWR-REDUN
|
EQPT:: RUNCFG-SAVENEED
|
EQPT:: SFTWDOWN
|
EQPT:: SWMTXMOD
|
EQPT:: WKSWPR
|
EQPT:: WTR
|
ETHER:: AS-CMD
|
ETHER:: CARLOSS (E-Series)
|
ETHER:: CARLOSS (G-Series)
|
EXTSYNCH:: FRCDSWTOPRI
|
EXTSYNCH:: FRCDSWTOSEC
|
EXTSYNCH:: FRCDSWTOTHIRD
|
EXTSYNCH:: MANSWTOPRI
|
EXTSYNCH:: MANSWTOSEC
|
EXTSYNCH:: MANSWTOTHIRD
|
EXTSYNCH:: SWTOPRI
|
EXTSYNCH:: SWTOSEC
|
EXTSYNCH:: SWTOTHIRD
|
EXTSYNCH:: SYNC-FREQ (BITS, STM-N)
|
EXTSYNCH:: SYNCPRI
|
EXTSYNCH:: SYNCSEC
|
EXTSYNCH:: SYNCTHIRD
|
FAN:: EQPT-MISS
|
FAN:: FAN
|
FAN:: FANDEGRADE
|
FAN:: MEA (FAN)
|
FAN:: MFGMEM (Backplane or Fan-Tray Assembly)
|
FUDC:: AIS
|
FUDC:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
HDGE [G1000]:: AS-CMD
|
HDGE [G1000]:: AS-MT
|
HDGE [G1000]:: CARLOSS (G-Series)
|
HDGE [G1000]:: LPBKFACILITY (G-Series)
|
HDGE [G1000]:: LPBKTERMINAL (G1000-4)
|
HDGE [G1000]:: TPTFAIL (G-Series)
|
HDGE [G1000]:: TUNDERRUN
|
HPMON:: AU-AIS
|
HPMON:: AU-LOP
|
HPMON:: AUTOSW-AIS-SNCP
|
HPMON:: AUTOSW-LOP-SNCP
|
HPMON:: AUTOSW-SDBER-SNCP
|
HPMON:: AUTOSW-SFBER-SNCP
|
HPMON:: AUTOSW-UNEQ-SNCP (HPMON)
|
HPMON:: FAILTOSW-HO
|
HPMON:: FORCED-REQ
|
HPMON:: HP-RFI
|
HPMON:: HP-TIM
|
HPMON:: HP-UNEQ
|
HPMON:: LOCKOUT-REQ
|
HPMON:: LPBKCRS
|
HPMON:: MAN-REQ
|
HPMON:: SDBER-EXCEED-HO
|
HPMON:: SFBER-EXCEED-HO
|
HPMON:: WKSWPR
|
HPMON:: WTR
|
HPTERM: AU-AIS
|
HPTERM: AU-LOF
|
HPTERM: AU-LOP
|
HPTERM: HP-TIM
|
HPTERM: HP-UNEQ
|
HPTERM: SDBER-EXCEED-HO
|
HPTERM: SFBER-EXCEED-HO
|
LPMON: AUTOSW-AIS-SNCP
|
LPMON: AUTOSW-LOP-SNCP
|
LPMON: AUTOSW-SDBER-SNCP
|
LPMON: AUTOSW-SFBER-SNCP
|
LPMON: AUTOSW-UNEQ-SNCP (LPMON)
|
LPMON: FAILTOSW-LO
|
LPMON: FORCED-REQ
|
LPMON: LOCKOUT-REQ
|
LPMON: LP-UNEQ
|
LPMON: MAN-REQ
|
LPMON: TU-AIS
|
LPMON: TU-LOP
|
LPMON: WKSWPR
|
LPMON: WTR
|
LPTERM: AU-LOF
|
LPTERM: LP-PLM
|
LPTERM: LP-RFI
|
LPTERM: LP-TIM
|
LPTERM: LP-UNEQ
|
LPTERM: SD
|
LPTERM: SF
|
LPTERM: TU-AIS
|
LPTERM: TU-LOP
|
ML1000:: AS-CMD
|
ML1000:: CARLOSS (ML-Series)
|
ML1000:: TPTFAIL (ML-Series)
|
MSUDC:: AIS
|
MSUDC:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
NBR:: RSVP-HELLODOWN
|
NE:: APC-DISABLED
|
NE:: APC-FAIL
|
NE:: AS-CMD
|
NE:: AUD-LOG-LOSS
|
NE:: AUD-LOG-LOW
|
NE:: DATAFLT
|
NE:: DBOSYNC
|
NE:: EHIBATVG-A
|
NE:: EHIBATVG-B
|
NE:: ELWBATVG-A
|
NE:: ELWBATVG-B
|
NE:: HITEMP
|
NE:: INTRUSION-PSWD
|
NE:: LAN-POL-REV
|
NE:: OPTNTWMIS
|
NE:: PRC-DUPID
|
NE:: PWR-A
|
NE:: PWR-B
|
NE:: SNTP-HOST
|
NE:: SYSBOOT
|
NERING:: FULLPASSTHR-BI
|
NERING:: KB-PASSTHR
|
NERING:: MSSP-OOSYNC
|
NERING:: PRC-DUPID
|
NERING:: RING-MISMATCH
|
NESYNCH:: FRCDSWTOINT
|
NESYNCH:: FRCDSWTOPRI
|
NESYNCH:: FRCDSWTOSEC
|
NESYNCH:: FRCDSWTOTHIRD
|
NESYNCH:: FRNGSYNC
|
NESYNCH:: FSTSYNC
|
NESYNCH:: HLDOVRSYNC
|
NESYNCH:: MANSWTOINT
|
NESYNCH:: MANSWTOPRI
|
NESYNCH:: MANSWTOSEC
|
NESYNCH:: MANSWTOTHIRD
|
NESYNCH:: SSM-LNC
|
NESYNCH:: SSM-PRC
|
NESYNCH:: SSM-SETS
|
NESYNCH:: SSM-STU (BITS, STM-N)
|
NESYNCH:: SSM-TNC (BITS, STM-N)
|
NESYNCH:: SWTOPRI
|
NESYNCH:: SWTOSEC
|
NESYNCH:: SWTOTHIRD
|
NESYNCH:: SYNCPRI
|
NESYNCH:: SYNCSEC
|
NESYNCH:: SYNCTHIRD
|
STM1E:: AS-CMD
|
STM1E:: AS-MT
|
STM1E:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
STM1E:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
STM1E:: MS-AIS
|
STM1E:: SD
|
STM1E:: MS-RFI
|
STM1E:: LPBKFACILITY (DS-3, E-N, STM-N)
|
STM1E:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
STM1E:: SD
|
STM1E:: SSM-DUS
|
STM1E:: SSM-FAIL (BITS, STM-N)
|
STM1E:: SSM-LNC
|
STM1E:: SSM-OFF (BITS, STM-N)
|
STM1E:: SSM-PRC
|
STM1E:: SSM-SETS
|
STM1E:: SSM-STU (BITS, STM-N)
|
STM1E:: TIM
|
STMN:: APSB
|
STMN:: APSCDFLTK
|
STMN:: APSC-IMP
|
STMN:: APSCINCON
|
STMN:: APSCM
|
STMN:: AS-CMD
|
STMN:: APSCNMIS
|
STMN:: AS-MT
|
STMN:: AUTOLSROFF
|
STMN:: EOC
|
STMN:: E-W-MISMATCH
|
STMN:: EXERCISE-RING-FAIL
|
STMN:: EXERCISE-RING-REQ
|
STMN:: EXERCISE-SPAN-FAIL
|
STMN:: EXERCISE-SPAN-REQ
|
STMN:: EXTRA-TRAF-PREEMPT
|
STMN:: FAILTOSW
|
STMN:: FAILTOSWR
|
STMN:: FAILTOSWS
|
STMN:: FE-EXERCISING-RING
|
STMN:: FE-EXERCISING-SPAN
|
STMN:: FE-FRCDWKSWPR-RING
|
STMN:: FE-FRCDWKSWPR-SPAN
|
STMN:: FE-LOCKOUTOFPR-SPAN
|
STMN:: FE-LOF
|
STMN:: FE-MANWKSWPR-RING
|
STMN:: FE-MANWKSWPR-SPAN
|
STMN:: FEPRLF
|
STMN:: FORCED-REQ-RING
|
STMN:: FORCED-REQ-SPAN
|
STMN:: LASEREOL
|
STMN:: LKOUTPR-S
|
STMN:: LMP-HELLODOWN
|
STMN:: LOCKOUT-REQ
|
STMN:: LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)
|
STMN:: LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)
|
STMN:: LPBKFACILITY (DS-3, E-N, STM-N)
|
STMN:: LPBKTERMINAL (DS-3, E-N, STM-N)
|
STMN:: MANUAL-REQ-RING
|
STMN:: MANUAL-REQ-SPAN
|
STMN:: MS-AIS
|
STMN:: MS-RFI
|
STMN:: RING-SW-EAST
|
STMN:: RING-SW-WEST
|
STMN:: SD
|
STMN:: SF
|
STMN:: SPAN-SW-EAST
|
STMN:: SPAN-SW-WEST
|
STMN:: SQUELCH
|
STMN:: SSM-DUS
|
STMN:: SSM-FAIL (BITS, STM-N)
|
STMN:: SSM-LNC
|
STMN:: SSM-OFF (BITS, STM-N)
|
STMN:: SSM-PRC
|
STMN:: SSM-SETS
|
STMN:: SSM-STU (BITS, STM-N)
|
STMN:: SSM-TNC (BITS, STM-N)
|
STMN:: SYNC-FREQ (BITS, STM-N)
|
STMN:: TIM
|
STMN:: WKSWPR
|
STMN:: WTR
|
2.3.1 Alarm Type/Object Definition
Table 2-7 defines abbreviations used in the alarm troubleshooting procedures.
Table 2-7 Alarm Type/Object Definition
AIE
|
Alarm expansion panel
|
BITS
|
Building integration timing supply (BITS) incoming references (BITS-1, BITS-2)
|
BP
|
Backplane
|
DWDM
Client
|
The port (such as STM-N) where the client signal is plugged in
|
DWDM
Trunk
|
The main span of the link; from the card point of view, it is the port operating in the 100-GHz spacing frequency grid
|
E1
|
E1-42 card
|
E3
|
E3-12 card
|
E-N
|
E-1 or E-3
|
EQPT
|
A card in any of the 17 card slots. This object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, and VC
|
ETHER
|
Ethernet
|
FAN
|
Fan-tray assembly
|
NE
|
The entire network element (node)
|
NERINGSDH
|
SDH NE1 ring
|
NESYNCHSDH
|
SDH NE synchronization
|
STM-1E
|
Synchronous Transfer Mode 1 (speed) Electrical Interface
|
STMN
|
Synchronous Transfer Mode (speed)
|
2.4 Trouble Notifications
The ONS 15454 SDH uses standard ITU-T x.733 categories to characterize levels of trouble. The ONS 15454 SDH reports alarmed trouble notifications and Not-Alarmed (NA) notifications, if selected, in the CTC Alarms window. Alarms typically signify a problem that the user needs to fix, such as the "LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)" alarm on page 2-118, while Not-Alarmed (NA) notifications do not necessarily need immediate troubleshooting.
The ITU further divides alarms into Service-Affecting (SA) and NSA status. A Service-Affecting (SA) failure affects a provided service or the network's ability to provide service. For example, the "TRMT-MISS" alarm on page 2-174 is characterized by default as an SA failure. TRMT-MISS occurs when a cable connector is removed from an active DS-1 card port. The default severity assumes that service has been interrupted or moved. If the DS-1 card is in a protection group and the traffic is on the protect card rather than the working card, or if the port with the TRMT-MISS alarm has no circuits provisioned, TRMT-MISS would be raised as NSA because traffic was not interrupted or moved.
2.4.1 Conditions
The term "Condition" refers to any problem detected on an ONS 15454 SDH shelf, whether or not the problem is reported (that is, whether or not it generates a trouble notification). Reported conditions include alarms, Not-Alarmed conditions, and Not-Reported (NR) conditions. A snapshot of all current raised conditions on a node, whether they are reported or not, can be retrieved using the CTC Conditions window. You can see the actual reporting messages for alarms and NAs in the CTC History tab. ONS 15454 SDH condition reporting is not ITU-compliant.
2.4.2 Severities
The ONS 15454 SDH uses the following ITU severities: Critical (CR), Major (MJ), and Minor (MN). Non-Service Affecting (NSA) alarms always have a Minor (MN) severity. Service-Affecting (SA) alarms may be Critical (CR), Major (MJ), or Minor (MN). Critical alarms generally indicate severe, service-affecting trouble that needs immediate correction. A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network.
An example of a Non-Service Affecting (NSA) alarm is the "FSTSYNC" condition on page 2-94 (Fast Start Synchronization Mode), which indicates the ONS 15454 SDH is choosing a new timing reference because the previously used reference has failed. The user needs to troubleshoot the loss of the prior timing source, but the loss is not immediately disruptive to service.
ITU standard severity types are the default settings for the ONS 15454 SDH. A user may customize ONS 15454 SDH alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the Cisco ONS 15454 SDH Procedure Guide.
This chapter lists the default profile alarm severity for the Service- Affecting (SA) case of each alarm when it is applicable. Any alarm with a profile value of Critical (CR) or Major (MJ) will — if reported as Non-Service Affecting (NSA) because no traffic is lost — be reported with a Minor (MN) severity instead.
2.5 Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS 15454 SDH. Do not perform any procedures in this chapter unless you understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards, in these instances pay close attention to the following caution and warnings:
Caution 
Hazardous voltage or energy might 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 STM-16 cards. In these instances, pay close attention to the following warnings.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Warning Class 1 laser product.
Warning Class 1M laser radiation when open. Do not view directly with optical instruments.
2.6 Alarm Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.
Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner is not indented. If it is, click it to turn it off. When you're done checking for alarms, click the alarm filter icon again to turn filtering back on.
Note When checking alarms, make sure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, see the Cisco ONS 15454 SDH Procedure Guide.
2.6.1 AIS
•Not Reported (NR), Non-Service Affecting (NSA)
The Alarm Indication Signal (AIS) condition indicates that this node is detecting AIS in the incoming signal SDH overhead.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Note DS-3 facility and terminal loopbacks do not transmit DS-3 AIS in the direction away from the loopback. Instead of DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.
Clear the AIS Condition
Step 1 Verify whether the upstream nodes and equipment have alarms, especially the "LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)" alarm on page 2-118, or OOS ports.
Step 2 Clear the upstream alarms using the applicable procedure(s) in this chapter.
Step 3 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.2 ALS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Automatic Laser Shutdown condition occurs when an amplifier (OPT-BST or OPT-PRE) is switched on. The turn-on process lasts approximately nine seconds, and the condition clears after approximately 10 seconds.
Note ALS is an informational condition. It does not require troubleshooting.
2.6.3 AMPLI-INIT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition is typically raised with the "APC-DISABLED" alarm on page 2-24.
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 Cisco ONS 15454 SDH Procedure Guide.
Step 3 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.4 APC-DISABLED
•Major (MJ), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Automatic Power Control (APC) Disabled alarm occurs when the information related to the number of channels is not reliable. The alarm can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-65, the "IMPROPRMVL" alarm on page 2-104, or the "MEA (EQPT)" alarm on page 2-130. If the alarm occurs with the creation of the first circuit, delete and then recreate it.
Clear the APC-DISABLED Alarm
Step 1 Complete the appropriate procedure to clear the primary alarm:
•Clear the EQPT Alarm
•Clear the IMPROPRMVL Alarm
•Clear the MEA (FAN) Alarm
Step 2 If the alarm does not clear, complete the "Delete a Circuit" procedure and then recreate it.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.5 APC-FAIL
•Major (MJ), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The APC Failure alarm occurs when APC has not been able to create a setpoint on a node because it has consumed all allocated power margins. These power margins (from 0 dB to 3 dB) are allocated when the network is installed. Margins can be consumed due to fiber aging or the insertion of unexpected extra loss in the span after a fiber cut.
Clear the APC-FAIL Alarm
Step 1 Isolate the cause of increased margin use:
•If it is due to fiber aging, replace the indicated fiber. (You can test the integrity of the fiber using optical testing equipment.)
•If it is due to a fiber cut, resolve this issue to resolve this alarm.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.6 APSB
•Minor (MN), Non-Service Affecting (NSA)
The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming APS signal. The failure occurs when an inconsistent APS byte or invalid code is detected. Some older, non-Cisco SDH nodes send invalid APS codes if configured in a 1+1 protection scheme with newer SDH nodes, such as the ONS 15454 SDH. These invalid codes cause an APSB alarm on an ONS node.
Clear the APSB Alarm
Step 1 Use an optical test set to examine the incoming SDH 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 SDH.
Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you might need to replace the upstream cards for protection switching to operate properly.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.7 APSCDFLTK
•Minor (MN), Non-Service Affecting (NSA)
The APS Default K Byte Received alarm occurs when a multiplex section-shared protection ring (MS-SPRing) is not properly configured, for example, when a four-node MS-SPRing has one node configured as a subnetwork connection protection (SNCP) ring. A node in an SNCP ring or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for MS-SPRing. One of the bytes sent is considered invalid by the MS-SPRing configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "MSSP-OOSYNC" alarm on page 2-135.
Clear the APSCDFLTK Alarm
Step 1 Complete the "Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 Repeat Step 1 for all nodes in the ring.
Step 3 If two nodes have the same node ID number, complete the "Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "EXCCOL" alarm on page 2-69.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 SDH Procedure Guide provides information for fibering MS-SPRings.
Step 5 If the alarm does not clear and if the network is a four-fiber MS-SPRing, make sure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if a working fiber is incorrectly attached to a protection fiber.
Step 6 If the alarm does not clear, complete the "Verify Node Visibility for Other Nodes" procedure to verify that each node is visible to the other nodes while in network view.
Step 7 If nodes are not visible, complete the "Verify or Create Node DCC Terminations" procedure to ensure that SDH DCC terminations exist on each node.
Step 8 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.8 APSC-IMP
•Minor (MN), Non-Service Affecting (NSA)
An Improper APS Code alarm indicates invalid K bytes. APSC-IMP occurs on STM-N cards in an MS-SPRing configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. APSC-IMP occurs when these bits indicate a bad or invalid K byte. The alarm clears when the node receives valid K bytes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.
For specific procedures to use the test set equipment, consult the manufacturer.
If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454 SDH. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454 SDHs, consult the appropriate user documentation.
Step 2 If the K byte is valid, complete the "Identify a Ring ID or Node ID Number" procedure.
Step 3 Repeat Step 2 for all nodes in the ring.
Step 4 If a node has a ring ID number that does not match the other nodes, complete the "Change a Ring ID Number" procedure to make the ring ID numbers identical.
Step 5 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.9 APSCINCON
•Minor (MN), Non-Service Affecting (NSA)
An Inconsistent APS Code alarm indicates that the APS code contained in the SDH overhead is inconsistent. The SDH overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454 SDH, to switch the SDH signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.
Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing
Step 1 Look for other alarms, especially a "LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)" alarm on page 2-118, an "LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)" alarm on page 2-114, or the "AIS" alarm on page 2-23. If they are present, complete the troubleshooting procedure(s) for the alarm(s). Clearing the other alarm clears the APSCINCON alarm.
Step 2 If an APSINCON alarm occurs with no other alarms, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.10 APSCM
•Major (MJ), Service-Affecting (SA)
The APS Channel Mismatch alarm occurs when the ONS 15454 SDH expects a working channel but receives a protection channel. In many cases, the working and protection channels are crossed and the protection channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. APSCM occurs in a 1+1 configuration. The APSCM alarm only occurs on the ONS 15454 SDH when bidirectional protection is used on STM-N cards in a 1+1 configuration.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the APSCM Alarm
Step 1 Verify that the working-card channel fibers are physically connected directly to the adjoining node's working-card channel fibers.
Step 2 If the alarm does not clear, verify that the protection-card channel fibers are physically connected directly to the adjoining node's protection-card channel fibers.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.11 APSCNMIS
•Major (MJ), Service-Affecting (SA)
The Node ID Mismatch alarm occurs when the source node ID contained in the K2 byte of the incoming APS channel is not present in the ring map. APSCNMIS might occur and clear when an MS-SPRing is being provisioned. If so, the user can disregard the temporary occurrence. If the APSCNMIS occurs and stays, the alarm clears when a K byte with a valid source node ID is received.
Clear the APSCNMIS Alarm
Step 1 Complete the "Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.
Step 3 Click Close in the Ring Map dialog box.
Step 4 If two nodes have the same node ID number, complete the "Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Note If the node names shown on the network view do not correlate with the node IDs, log into each node and click the Provisioning > MS-SPRing tabs. The MS-SPRing window displays the node ID of the login node.
Note Applying and removing a lockout on a span causes the ONS 15454 SDH to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.
Step 5 If the alarm does not clear, use the "Lock Out an MS-SPRing Span" procedure to lock out the span.
Step 6 Complete the "Clear an MS-SPRing Span Lock Out" procedure to clear the lock out.
Step 7 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.12 AS-CMD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Portions of this procedure do not apply to DWDM
The Alarms Suppressed by User Command condition applies to the network element (SYSTEM object), backplane, a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects; that is, suppressing alarms on a card also suppresses alarms on its ports.
Clear the AS-CMD Condition
Step 1 For all nodes, in the node view, click the Conditions tab.
Step 2 Click Retrieve. If you have already retrieved conditions, look under the Object column and Eqpt Type column, note what entity the condition is reported against, such as a port, slot, or shelf.
If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with Step 3.
If the condition is reported against the backplane, go to Step 7.
If the condition is reported against a "system," go to Step 8.
Step 3 If the AS-CMD condition is reported for a card in a non-DWDM (Software R4.1 or earlier) node, determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:
a. Double-click the card to display the card view.
b. Click the Provisioning > Alarm Behavior tabs.
•If the Suppress Alarms column check box is checked for a port row, deselect it and click Apply.
•If the Suppress Alarms column check box is not checked for a port row, click View > Go to Previous View.
Step 4 In node view for a non-DWDM (Software R4.1 or earlier) node, if the AS-CMD condition is reported for a card and not an individual port, click the Provisioning > Alarm Behavior tabs.
Step 5 Locate the row for the reported card slot. (The slot number information was in the Object column in the Conditions window that you noted in Step 2.)
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 AIP that are not in the optical or electrical slots. To clear the alarm:
a. In node view, click the Provisioning > Alarm Behavior tabs.
b. In the Backplane row, deselect the Suppress Alarms column check box.
c. Click Apply.
Step 8 If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm:
a. In node view, click the Provisioning > Alarm Behavior tabs.
b. Click the Suppress Alarms check box located at the bottom of the window to deselect the option.
c. Click Apply.
Step 9 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.13 AS-MT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The Alarms Suppressed for Maintenance Command condition applies to OC-N and electrical (traffic) cards and occurs when a port is placed in the out-of-service maintenance (OOS-MT) state for loopback testing operations.
Clear the AS-MT Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.14 AU-AIS
•Not Reported (NR), Non-Service Affecting (NSA)
An Administration Unit (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 tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you 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.
Step 3 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.15 AUD-LOG-LOSS
•Not Alarmed (NA), Non-Service Affecting (NSA)
The Audit Trail Log Loss condition occurs when the log is 100% full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries.
Clear the AUD-LOG-LOSS Condition
Step 1 In the node view, click the Maintenance > Audit tabs.
Step 2 Click Retrieve.
Step 3 Click Archive.
Step 4 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.
Step 5 Enter a name in the File Name field.
You do not need to assign an extension to the file. The file is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.
Step 6 Click Save.
The 640 entries will be saved in this file. New entries will continue with the next number in the sequence, rather than starting over.
Step 7 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.16 AUD-LOG-LOW
•Not Reported (NR), Non-Service Affecting (NSA)
The Audit Trail Log Loss condition occurs when the audit trail log is 80% full.
Note AUD-LOG-LOW is an informational condition. The condition does not require troubleshooting.
2.6.17 AU-LOF
•Major (MJ), Service-Affecting (SA) for HPTERM
The Administrative Unit (AU) Loss of Frame (LOF) alarm indicates that the ONS 15454 SDH detects frame loss in the regenerator section of the SDH overhead.
Clear the AU-LOF Alarm
Step 1 Complete the "Clear the LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N) Alarm" procedure.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.18 AU-LOP
•Critical (CR), Service-Affecting (SA)
An AU Loss of Pointer (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.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation might be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AU-LOP Alarm
Step 1 In the 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 will cause the alarm.
Step 3 If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm. Ensure that the test set monitoring is set up for the same size as the circuit provisioning.
For instructions to use the optical test set, consult the manufacturer.
Step 4 If you have not been using a test set, or if the test set is correctly set up, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.
Step 5 Recreate the circuit for the correct size. For instructions, see the Cisco ONS 15454 SDH Procedure Guide.
Step 6 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.19 AUTOLSROFF
•Critical (CR), Service-Affecting (SA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The Auto Laser Shutdown alarm occurs when the STM-64 card temperature exceeds 194° F (90 ° C). The internal equipment automatically shuts down the STM-64 laser when the card temperature rises to prevent the card from self-destructing.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Clear the AUTOLSROFF Alarm
Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, refer to "View Alarm Counts on the LCD for a Slot or Port" procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 2 Verify whether there is a HITEMP alarm present. If the temperature of the shelf exceeds 90° C (194° F), the alarm should clear if you solve the ONS 15454 SDH temperature problem. Complete the "Clear the HITEMP Alarm" procedure.
Step 3 If the temperature of the shelf is under 90° C (194° F), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Card" procedure for the STM-64 card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 4 If card replacement does not clear the alarm, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.20 AUTORESET
•Minor (MN), Non-Service Affecting (NSA)
The Automatic System Reset alarm occurs when a card is performing an automatic warm reboot. An AUTORESET occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the AUTORESET Alarm
Step 1 Verify whether there are additional alarms that might have triggered an automatic reset.
Step 2 If the card automatically resets more than one time per month with no apparent cause, complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, you do not need to change the CTC database.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.21 AUTOSW-AIS-SNCP
•Not Reported (NR), Non-Service Affecting (NSA)
The Automatic SNCP Switch Caused by AIS condition indicates that automatic SNCP protection switching occurred because of the "TU-AIS" condition on page 2-174. The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears. The AUTOSW-AIS-SNCP clears when you clear the primary alarm on the upstream node.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS-SNCP Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.22 AUTOSW-LOP-SNCP
•Minor (MN), Non-Service Affecting (NSA)
An Automatic SNCP Switch Caused by LOP alarm indicates that an automatic SNCP protection switching occurred because of the "AU-LOP" alarm on page 2-33. The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears.
Clear the AUTOSW-LOP-SNCP Alarm
Step 1 Complete the "Clear the AU-LOP Alarm" procedure.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.23 AUTOSW-SDBER-SNCP
•Not Alarmed (NA), Non-Service Affecting (NSA)
The Automatic SNCP Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade (see the "SD" condition on page 2-155), caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SD is resolved.
Clear the AUTOSW-SDBER-SNCP Condition
Step 1 Complete the "Clear the SD Condition" procedure.
Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.24 AUTOSW-SFBER-SNCP
•Not Alarmed (NA), Non-Service Affecting (NSA)
The Automatic SNCP Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail (see the "SF" condition on page 2-157) caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SF is resolved.
Clear the AUTOSW-SFBER-SNCP Condition
Step 1 Complete the "Clear the SF Condition" procedure.
Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.25 AUTOSW-UNEQ-SNCP (HPMON)
•Not Alarmed (NA), Non-Service Affecting (NSA)
The Automatic SNCP Switch Caused by an Unequipped indicates that an HP-UNEQ alarm caused automatic SNCP protection switching to occur (see the "HP-UNEQ" alarm on page 2-102). The SNCP ring is configured for revertive switching and reverts to the working path after the fault clears.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation might be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AUTOSW-UNEQ-SNCP (HPMON) Condition
Step 1 Complete the "Clear the HP-UNEQ Alarm" procedure.
Step 2 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.26 AUTOSW-UNEQ-SNCP (LPMON)
•Minor (MN), Service-Affecting (SA)
AUTOSW-UNEQ indicates that the "LP-UNEQ" alarm on page 2-126 caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path after the fault clears.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation might be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AUTOSW-UNEQ-SNCP (LPMON) Alarm
Step 1 Display the CTC network view and right-click the span reporting AUTOSW-UNEQ. Select Circuits from the shortcut menu.
Step 2 If the specified circuit is a low-order path tunnel, verify whether low-order paths are assigned to the tunnel.
Step 3 If the low-order path tunnel does not have assigned low-order paths, delete the low-order path tunnel from the list of circuits.
Step 4 If you have complete visibility to all nodes, Verify whether there are incomplete circuits such as stranded bandwidth from circuits that were not completely deleted.
Step 5 If you find incomplete circuits, verify whether they are working circuits and if they are still passing traffic.
Step 6 If the incomplete circuits are not needed or are not passing traffic, delete them and log out of CTC. Log back in and for incomplete circuits again. Recreate any needed circuits.
Step 7 If the alarm does not clear, verify that all circuits terminating in the reporting card are active:
a. In the node view, click the Circuits tab.
b. Verify that the State column lists the port as active.
c. If the State column lists the port as incomplete, and the incomplete does not change after a full initialization, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
Step 8 After you determine that the port is active, verify the signal source received by the card reporting the alarm.
Step 9 If the alarm does not clear, verify that the far-end STM-N card providing payload to the card is working properly.
Step 10 If the alarm does not clear, verify the far-end cross-connect between the STM-N card and the E-N card.
Step 11 If the alarm does not clear, clean the far-end optical fiber cable ends according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Step 12 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.27 AWG-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The AWG Temperature Degrade alarm indicates that an internal failure on the multiplexer or demultiplexer heater control circuit causes the AWG temperature to rise above or fall below the degrade threshold.
Clear the AWG-DEG Alarm
Step 1 This alarm does not immediately affect traffic. But eventually, you will need to complete the "Physically Replace a Card" procedure on the reporting card to clear the alarm.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.28 AWG-FAIL
•Critical (CR), Service-Affecting (SA)
•Occurs only on DWDM (Software R4.5) nodes
The AWG Temperature Fail alarm indicates that a heater control circuit on the multiplexer or demultiplexer card has failed.
Clear the AWG-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.29 AWG-OVERTEMP
•Critical (CR), Service-Affecting (SA)
•Applies only to non-DWDM (Software R4.1 or earlier) nodes
The AWG Over Temperature alarm occurs in conjunction with the "AWG-FAIL" alarm on page 2-39 when the AWG temperature exceeds 100 deg. C (212 F). The multiplexer or demultiplexer goes into protection mode, disabling the AWG chip heater.
Clear the AWG-OVERTEMP Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.30 AWG-WARM-UP
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The AWG Warm-up condition occurs during AWG startup. The length of time needed for the condition to clear varies, depending upon environmental conditions. It may last up to approximately 10 minutes.
Note AWG-WARM-UP is an informational condition, and does not require troubleshooting unless it does not clear.
2.6.31 BKUPMEMP
Default Severity: Critical (CR), Service-Affecting (SA)
Note The severity is Minor (MN), Non-Service-Affecting (NSA) for SBY TCC2/TCC2P card.
SDH Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P card flash memory. This alarm is raised on ACT/SBY TCC2/TCC2P cards. The alarm occurs when the TCC2/TCC2P card is in active or standby state and has one of four problems:
•Failure to format a flash partition.
•Failure to write a file to a flash partition.
•Problem at the driver level.
•Code volume fails cyclic redundancy checking (CRC, a method to verify for errors in data transmitted to the TCC2/TCC2P card).
The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-65. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Clear the BKUPMEMP Alarm
Step 1 Verify that both TCC2/TCC2P cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2/TCC2P cards.
Step 2 Determine whether the active or standby TCC2/TCC2P card has the alarm.
Step 3 If both cards are powered and enabled, reset the TCC2/TCC2P card where the alarm is raised. If the card is the active TCC2/TCC2P card, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2/TCC2P card LED should be green.
If the card is the standby TCC2/TCC2P card, complete the "Reset the Standby TCC2/TCC2P Card" procedure.
Step 4 If the reset TCC2/TCC2P card has not rebooted successfully, or the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a 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.
2.6.32 CARLOSS (EQPT)
•Major (MJ), Service-Affecting (SA)
The Carrier Loss Equipment alarm occurs when the ONS 15454 SDH and the workstation hosting CTC do not have a TCP/IP connection. CARLOSS is a problem involving the LAN or data circuit used by the RJ-45 connector on the TCC2 card or the LAN backplane pin connection on the back of the ONS 15454 SDH. The alarm does not involve an Ethernet circuit connected to a port on an Ethernet (traffic) card. The problem is in the connection (usually a LAN problem) and not the CTC or the ONS 15454 SDH.
On TXP and MXP cards, CARLOSS is also raised against trunk ports when G.709 monitoring is turned off.
A TXP 2.5 G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data type.
Clear the CARLOSS (EQPT) Alarm
Step 1 If the reporting card is a TXP card, verify the type of payload configured:
a. Double-click the reporting TXP card.
b. Click the Provisioning > Card tabs.
c. From the Payload type list choose the correct payload for the card and click Apply.
Step 2 Verify connectivity by pinging the ONS 15454 SDH that is reporting the alarm:
a. If you are using a Microsoft Windows operating system, choose Start > Programs > Command Prompt.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
c. For both the Sun and Microsoft operating systems, at the prompt type:
ping [ONS 15454 SDH IP address]
For example, ping 192.1.0.2.
If the workstation has connectivity to the ONS 15454 SDH, the workstation displays "Reply from [IP Address]" after the ping. If the workstation does not have connectivity, a "Request timed out" message displays.
Step 3 Verify that the straight-through (CAT-5) LAN cable is properly connected and attached to the correct port.
Step 4 If the straight-through (CAT-5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 5 If you are unable to establish connectivity, replace the straight-through cable with a new known-good cable.
Step 6 If you are unable to establish connectivity, perform standard network/LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.33 CARLOSS (E-Series)
•Major (MJ), Service-Affecting (SA)
A Carrier Loss on the LAN alarm is the data equivalent of the SDH "LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)" alarm on page 2-118. The Ethernet (traffic) card has lost its link and is not receiving a valid signal. The most common causes of this alarm are a disconnected straight-through (Category 5) LAN cable or an improperly installed Ethernet card. Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
CARLOSS also occurs after the restoration of a node database. In this instance, the alarm will clear in approximately 30 seconds after the node reestablishes spanning-tree protocol (STP). Reestablishment applies to the E-series Ethernet cards but not to the G1000-4 card. The G1000-4 card does not use Spanning Tree Protocol (STP) and is unaffected by STP reestablishment.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CARLOSS (E-Series) Alarm
Step 1 Verify that the straight-through (Category 5) LAN cable is properly connected and attached to the correct port.
Step 2 If the straight-through (Category 5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 3 If there is no misconnection to an STM-N card, verify that the transmitting device is operational. If not, troubleshoot the device.
Step 4 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the straight-through (Category 5) LAN cable connecting the transmitting device to the Ethernet port.
Step 6 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet (traffic) card.
Step 7 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the Ethernet (traffic) card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 8 If a CARLOSS alarm repeatedly appears and clears, use the following steps to examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect.
Step 9 If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm might be a result of mismatched circuit sizes in the setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Click the Select Affected Circuits dialog box that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. Examine the layout of your network and determine which ONS 15454 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 SDH at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet (traffic) card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross connect circuit will connect the Ethernet card to an STM-N card on the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 10 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.34 CARLOSS (G-Series)
•Major (MJ), Service-Affecting (SA)
A Carrier Loss on the LAN alarm is the data equivalent of the "LOS (DS-3, E-1, E-3, E-4, EC-N, STM1E, STM-N)" alarm on page 2-118. The Ethernet (traffic) card has lost its link and is not receiving a valid signal.
CARLOSS on the G1000-4 card can be caused by one of two situations:
•The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. The CARLOSS can be caused by an improperly connected Ethernet cable or a problem with the signal between the Ethernet device and the G1000-4 port.
•If a problem exists in the end-to-end path (including possibly the far-end G1000-4 card), the problem causes the reporting G1000-4 to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, a TPTFAIL (G-Series) alarm, or STM-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G-Series) alarm.
Refer to the Cisco ONS 15454 SDH Reference Guide for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. See also the "TRMT" alarm on page 2-173 for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.
Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CARLOSS (G-Series) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port.
Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 3 If no misconnection to the STM-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.
Step 4 Verify that optical receive levels are within the normal range.
Step 5 If the alarm does not clear, use an Ethernet test set to determine that a valid signal is coming into the Ethernet port.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port.
Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the G1000-4 turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, verify whether there are conditions that could cause autonegotiation to fail:
a. Confirm that the attached Ethernet device has auto-negotiation enabled and is configured for compatibility with the asymmetric flow control on the G1000-4 card.
b. Confirm that the attached Ethernet device configuration allows reception of flow control frames.
Step 8 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. Autonegotiation restarts.
Step 9 If the TPTFAIL is also reported, complete the "Clear the TPTFAIL (G-Series) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.
Note When both alarms are reported, the reason for the condition might be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 10 If the TPTFAIL alarm was not reported, verify whether a terminal loopback has been provisioned on the port:
a. In the node view, click the card to go to card view.
b. Click the Conditions tab and then click Retrieve Conditions.
c. If LPBKTERMINAL is listed for the port, a loopback is provisioned. Go to Step 11. If IS is listed, go to Step 12.
Step 11 If a loopback was provisioned, clear the loopback by following the "Clear a Loopback" procedure.
On the G1000-4 card, provisioning a terminal loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.
If the port is not set in LPBKTERMINAL, continue to Step 12.
Step 12 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm might be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps if the Ethernet circuit is part of a manual cross-connect.
Note A Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454 SDHs, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 SDH TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Click Select Affected Circuits from the shortcut menu.
c. Record the information in the type and size columns of the highlighted circuit.
d. Examine the layout of your network and determine which ONS 15454 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 SDH at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet (traffic) card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross connect circuit will connect the Ethernet card to an STM-N card on the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 13 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet card.
Step 14 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the Ethernet card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 15 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.35 CARLOSS (ML-Series)
•Major (MJ), Service-Affecting (SA)
A CARLOSS alarm on the ML-series Ethernet (traffic) card is the data equivalent of the "LOF (DS-3, E-1, E-4, EC-N, STM1E, STM-N)" alarm on page 2-114. The Ethernet port has lost its link and is not receiving a valid signal.
CARLOSS for an ML-Series card occurs when the Ethernet port has been configured from the IOS command line interface (CLI) as a no-shutdown port and one of the following items also occurs:
•The cable is not properly connected to the near or far port
•Auto-negotiation is failing
•The speed (10/100 ports only) is set incorrectly
For information about provisioning ML-series Ethernet cards from the internal operating system (IOS) interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.1.
Clear the CARLOSS (ML-Series) Alarm
Step 1 Verify that the LAN cable is properly connected and attached to the correct port on the ML-series card and on the peer Ethernet port.
Step 2 If the alarm does not clear, verify that autonegotiation is set properly on the ML card port and the peer Ethernet port.
Step 3 If the alarm does not clear, verify that the speed is set properly on the ML card port and the peer Ethernet port if you are using 10/100 ports.
Step 4 If the alarm does not clear, the Ethernet signal is not valid, but the transmitting device is operational, replace the LAN cable connecting the transmitting device to the Ethernet port.
Step 5 If the alarm does not clear, disable and reenable the Ethernet port by performing a "shutdown" and then a "no shutdown" on the IOS CLI. Autonegotiation restarts.
Step 6 If the alarm does not clear, perform a facility loopback on the ML card using the "Create a Facility (Line) Loopback Circuit on a Destination E3-12 Port" procedure on page 1-21.
Step 7 If the problem persists with the loopback installed, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 8 If the alarm does not clear, complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 9 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.36 CASETEMP-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Case Temperature Degrade alarm occurs when a card detects a case temperature value outside the desired range (-5 to 65 deg. C).
Clear the CASETEMP-DEG Alarm
Step 1 If a FAN alarm is also reported, complete the "Clear the FAN Alarm" procedure.
Step 2 If no FAN alarm is reported, complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.37 CKTDOWN
•Critical (CR), Service-Affecting (SA)
The Unified Control Plane (UCP) Circuit Down alarm applies to logical circuits created within the UCP between devices. CKTDOWN occurs when the there is signaling failure across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 SDH edge device.
Clear the CKTDOWN Alarm
Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:
a. In the node view, click the Provisioning > UCP > Neighbor tabs.
b. View the entries to find out whether the node you are trying to contact is listed.
c. The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that physical and logical accessibility.
d. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.
e. At the command prompt (C:\>), type:
ping [node DNS name or node IP address]
If you typed the domain name services (DNS) name and the ping was successful, you will see:
pinging [node dns name].[domain name].com. [node IP address] with 32 bytes of data:
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Ping statistics for [IP address]:
Packets sent = 4 Received = 4 Lost = 0 (0% lost),
Approximate round trip time in milli-seconds:
Minimum = [minimum ms], Maximum = [maximum ms], Average = [average ms]
If you typed the IP address and the ping command is successful, the result will look similar but will not include the DNS name in the first line.
f. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.
g. If the ping was unsuccessful, you will get the following reply repeated for each try:
A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.
Step 2 If the channel to neighbor has not been provisioned, or if you had to delete the channel, create one:
a. Click the Provisioning > UCP > Neighbor tabs.
b. Click Create.
c. In the Neighbor Discovery window, enter the node's DNS node name in the Neighbor Name field. Leave the Enable Discovery check box checked (default setting) if you want the neighbor to be discovered through the network.
d. Click OK.
The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If discovery is not successful, the column will say 0.0.0.0.
Step 3 If neighbor discovery is enabled, make sure that the neighbor node ID, remote IPCC have been discovered correctly.
Step 4 Click the Provisioning > UCP > IPCC tabs and view the IPCC listing. If the IPCC has been created correctly, the Remote IP column contains the neighbor's IP address.
Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.
a. Click the entry to select the neighbor IP address and click Delete.
b. If you get an error that will not allow you to delete the IPCC, you will need to delete the neighbor and recreate it. Click the Neighbor tab.
c. Click to select the neighbor and click Delete.
d. Then go back to Step 2 to recreate the neighbor.
Step 6 If remote IPCC has not been discovered, or if IPCC had to be deleted, create the connection:
a. In the Provisioning > UCP > IPCC tabs, click Create.
b. In the Unified Control Plane Provisioning window, click Next.
c. If no IPCCs are listed, click Create.
d. In the Create New IPCC window, click one of the Regenerator Section DCC (SDCC) terminations in the SDCC list.
Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.
e. Click OK. The IPCC is listed as CCID 1 in the Unified Control Plane Provisioning window.
f. Click the neighbor to select it, and click Next.
g. Choose a UCP interface (for example Slot 5 for an STM-16 card, port 1) from the pull-down menu. The field default is the node where you are logged in.
h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.
i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab will contain the neighbor's IP address.
Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:
a. Click the Interface tab. View the slot and port listed in the Interface column (for example, Slot 5 for an STM-16 card, port 1).
b. Compare the listed interface listed with the IPCC tab SDCC column entry.
Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.
Step 9 Click Next.
Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.
The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.
Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.
Step 12 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.38 CLDRESTART
•Not Alarmed (NA), Non-Service Affecting (NSA)
The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 is first powered up.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Clear the CLDRESTART Condition
Step 1 If the condition fails to clear after the card reboots, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 2 If the condition does not clear, complete the "Physically Replace a Card" procedure for the card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.39 COMIOXC
•Critical (CR), Service-Affecting (SA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The Input/Output Slot To Cross-Connect Communication Failure alarm can be caused by the cross-connect card. COMIOXC occurs when there is a communication failure for a traffic (multispeed or high-speed) slot.
Clear the COMIOXC Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure on the reporting cross connect card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 3 If the CTC reset does not clear the alarm, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure.
Step 4 Complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting cross connect card.
Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting cross connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 6 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.40 COMM-FAIL
•Minor (MN), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2 and the card. The failure could indicate a broken card interface.
Clear the COMM-FAIL Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card.
Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.41 CONTBUS-A-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 7 (termed TCC A) loses communication with the coprocessor on the same card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge
of the shelf assembly.
Clear the CONTBUS-A-18 Alarm
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 11 active.
Step 2 Wait approximately 10 minutes for the TCC2 in Slot 7 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 7 active.
Step 4 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.6.42 CONTBUS-B-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 11 (termed TCC B) loses communication with the coprocessor on the same card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge
of the shelf assembly.
Clear the CONTBUS-B-18 Alarm
Step 1 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 7 active.
Step 2 Wait approximately 10 minutes for the TCC2 in Slot 11 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC2 card in Slot 7 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 11 active.
Step 4 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country. If the TAC technician tells you to reseat the card, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.6.43 CONTBUS-IO-A
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCC A to Shelf Slot Communication Failure alarm occurs when the active TCC2 card in Slot 7 (TCC A) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-A alarm might appear briefly when the ONS 15454 SDH switches to the protect TCC2 card. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2 card, the other card, and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge
of the shelf assembly.
Clear the CONTBUS-IO-A Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (BP)" alarm on page 2-130 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby TCC2 in Slot 11, perform a CTC reset of the object card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby TCC2 in Slot 11, perform a soft reset of this card:
a. Right-click the Slot 11 TCC2 card.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 4 If CONTBUS-IO-A is raised on several cards at once, complete the "Reset Active TCC2 Card and Activate 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. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 6 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 7 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.6.44 CONTBUS-IO-B
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCC B to Shelf Slot Communication Failure alarm occurs when the active TCC2 card in Slot 11 (TCC B) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-B alarm might appear briefly when the ONS 15454 SDH switches to the protect TCC2 card. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2 card, the other card, and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge
of the shelf assembly.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (BP)" alarm on page 2-130 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby TCC2 in Slot 7, perform a CTC reset of the object card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby TCC2 in Slot 7, perform a soft reset of this card:
a. Right-click the Slot 7 TCC2 card.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 4 If CONTBUS-IO-B is raised on several cards at once, complete the "Reset Active TCC2 Card and Activate 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. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 6 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 7 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.6.45 CTNEQPT-PBPROT
•Critical (CR), Service-Affecting (SA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the Slot 10 cross-connect card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, the TCC2 card, or the backplane.
Note If all traffic cards show CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the standby TCC2 card. Do not physically reseat an active TCC2 card. Reseating the TCC2 disrupts traffic.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note This alarm automatically raises and clears when the Slot 10 cross-connect card is reseated.
Clear the CTNEQPT-PBPROT Alarm
Step 1 Perform a CTC reset on the standby cross-connect card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
If the cross-connect reset is not complete and error-free or if the TCC2 card reboots itself, log into http://www.cisco.com/tac for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
Step 3 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.
Step 4 Determine whether the card is an active card or standby card in a protection group. Click the node view Maintenance > Protection tabs, then click the protection group. The cards and their status will be displayed in the list.
Step 5 If the reporting traffic (electrical, optical, or Ethernet) card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.
Step 6 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card.
•While the card resets, the FAIL LED blinks on the physical card and then all LEDs turn off.
•While the card resets, a white LED with the letters "LDG" appears on the reset card in CTC.
Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 Complete the "Clear an External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting card.
Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the standby cross connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 12 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic card.
Step 13 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.46 CTNEQPT-PBWORK
•Critical (CR), Service-Affecting (SA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the Slot 8 cross-connect card the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, or the backplane.
Note If all traffic cards show CTNEEQPT-PBWORK alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure for the active TCC2 card and then complete the "Remove and Reinsert (Reseat) a Card" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card. Do not physically reseat an active TCC2 card; reseating disrupts traffic.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note This alarm automatically raises and clears when the Slot 8 cross-connect card is reseated.
Clear the CTNEQPT-PBWORK Alarm
Step 1 Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to move traffic from the active card to the standby cross connect card.
Step 2 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting traffic (electrical, optical, or Ethernet) card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 4 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the standby cross connect card.
Note The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is amber.
Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.
Step 6 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 If you switched traffic, complete the "Clear an External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the cross connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic card.
Step 12 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.47 DATAFLT
•Minor (MN), Non-Service Affecting (NSA)
The Software Data Integrity Fault alarm occurs when the TCC2 exceeds its flash memory capacity.
Caution When the system reboots, the last configuration entered is not saved.
Clear the DATAFLT Alarm
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.48 DBOSYNC
•Major (MJ), Non-Service Affecting (NSA)
The Standby Database Out Of Synchronization alarm occurs when the standby TCC2 "To be Active" database does not synchronize with the active database on the active TCC2.
Caution If you reset the active TCC2 card while this alarm is raised, you will lose current provisioning.
Clear the DBOSYNC Alarm
Step 1 Save a backup copy of the active TCC2 database. Complete the "Back Up the Database" procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 2 Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm:
a. In the node view, click the Provisioning > General tabs.
b. In the Description field, make a small change such as adding a period to the existing entry.
The change causes a database write but will not affect the node state. The write might take up to a minute.
Step 3 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.49 DS3-MISM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on non-DWDM (Software R4.1 or earlier) nodes
The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on the DS3i-N-12 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C-BIT for a DS3i-N-12 card, and the incoming signal's frame format is detected as M13 or UNFRAMED, then the ONS 15454 SDH reports a DS3-MISM condition. The condition does not occur when the line type is set to AUTO PROVISION or UNFRAMED, so changing the line type to either of these options will clear the condition. DS3-MISM will also clear if the port state is set to OOS.
Setting the line type to AUTO PROVIS ION causes the ONS 15454 SDH to detect the received frame format and provision the port to use the matching frame format, either Unframed, M13 or C-BIT.
Clear the DS3-MISM Condition
Step 1 Display the CTC card view for the reporting DS3i-N-12 card.
Step 2 Click the Provisioning > Line tabs.
Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the entry in the Expected Line Type column.
Step 4 If you want to change the line type because the line type entry does not match the expected incoming type, click the cell to reveal a pull-down menu and select the correct type.
Step 5 Click Apply.
Step 6 If you want to change the port state to OOS, click the Maintenance tab at the card view.
Step 7 Locate the correct port and click the State column to reveal a pull-down menu. Click OOS.
Step 8 If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 SDH matches the expected incoming signal.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 9 If the condition does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.50 DSP-COMM-FAIL
•Major (MJ), Service-Affecting (SA)
The DSP Communication Failure alarm indicates that there is a communications failure between an MXP or TXP card microprocessor and the on-board DSP chip that controls the trunk (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 will attempt to restore communication with the DSP chip until the alarm is cleared.
If the alarm remains for an extended period, The MXP or TXP card will raise the "DSP-FAIL" alarm on page 2-61.
Note If the DSP-COMM-FAIL alarm continues for an extended period, traffic could be affected.
Note DSP-COMM-FAIL is an informational condition. The alarm does not require troubleshooting.
2.6.51 DSP-FAIL
•Major (MJ), Service-Affecting (SA)
The DSP Failure alarm indicates that the "DSP-COMM-FAIL" alarm on page 2-60 has persisted for an extended period on an MXP or TXP card. It indicates that the card is faulty.
Clear the DSP-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country to report a service-affecting problem.
2.6.52 E3-ISD
•Not Alarmed (NA), Non-Service Affecting (NSA)
The E3 Idle condition indicates that the E3-12 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. E3-ISD occurs when the transmitting card is OOS-MNT. E3-ISD is resolved when the OOS condition ends.
Note E3-ISD is an informational condition. The condition does not require troubleshooting.
2.6.53 EHIBATVG-A
•Minor (MN), Non-Service Affecting (NSA)
The Extreme High Voltage on Battery A alarm occurs when the voltage level on battery lead A exceeds -56.7 VDC in -48 VDC systems or -72 VDC in -60 VDC systems. The alarm indicates that the voltage on the battery lead is extremely high and power redundancy is no longer guaranteed. The alarm remains until the voltage remains below the threshold for 120 seconds.
Clear the EHIBATVG-A Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying battery lead A.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.54 EHIBATVG-B
•Minor (MN), Non-Service Affecting (NSA)
The Extreme High Voltage on Battery B alarm occurs when the voltage level on battery lead B exceeds -56.7 VDC in -48 VDC systems or -72 VDC in -60 VDC systems. The alarm indicates that the voltage on the battery lead is extremely high and power redundancy is no longer guaranteed. The alarm remains until the voltage remains below the threshold for 120 seconds.
Clear the EHIBATVG-B Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying battery lead B.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.55 ELWBATVG-A
•Minor (MN), Non-Service Affecting (NSA)
The Extreme Low Voltage on Battery Feed A alarm indicates that the voltage is extremely low or has been lost, and power redundancy is no longer guaranteed. The alarm occurs when the voltage on battery feed A drops below -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage has remained above -40.5 VDC for 120 seconds.
Clear the ELWBATVG-A Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying battery lead A.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.56 ELWBATVG-B
•Minor (MN), Non-Service Affecting (NSA)
The Extreme Low Voltage on Battery Feed B alarm indicates that the voltage is extremely low or has been lost, and power redundancy is no longer guaranteed. The alarm occurs when the voltage on battery feed B drops below -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage has remained above -40.5 VDC for 120 seconds.
Clear the ELWBATVG-B Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying battery lead B.
Step 2 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.57 EOC
•Major (MJ), Non-Service Affecting (NSA)
The Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 SDH loses its DCC. The DCC is three bytes, D1 through D3, in the SDH overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the section layer to communicate network management information.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note If a circuit shows an incomplete state when the EOC alarm is raised, the logical circuit is in place, and will be able to carry traffic after the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the EOC Alarm
Step 1 If an LOS alarm is also reported, complete the "Clear the LOS (DS-3, E-1, E-3, EC-N, STM1E, STM-N) Alarm" procedure.
Step 2 If the alarm does not clear on the reporting node, verify the physical connections between the cards and the fiber-optic cables that are configured to carry DCC traffic.
Step 3 If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have in-service (IS) ports by verifying that the ACT LED on each STM-N card is illuminated.
Step 4 If the ACT LEDs on STM-N cards are illuminated, complete the "Verify or Create Node DCC Terminations" procedure to verify that the DCC is provisioned for the ports at both ends of the fiber span.
Step 5 Repeat Step 4 at the adjacent nodes.
Step 6 If DCC is provisioned for the ends of the span, verify that the STM-N port is active and in service:
a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.
A green LED indicates an active card. An amber LED indicates a standby card.
b. To determine whether the STM-N port is in service, double-click the card in CTC to display the card view.
c. Click the Provisioning > Line tabs.
•Verify that the State column lists the port as IS.
•If the State column lists the port as OOS, click the column and choose IS from the pull-down menu. Click Apply.
Step 7 If the STM-N card is in service, use an optical test set to verify whether or not there are signal failures on fiber terminations.
For specific procedures to use the test set equipment, consult the manufacturer.
Caution Using an optical test might disrupt service on the STM-N card. You might need to externally switch traffic carrying circuits over to a protection path.
Step 8 If no signal failures on terminations exist, measure power levels to verify that the budget loss is within the parameters of the receiver. See the "Optical Card Transmit and Receive Levels" section on page 1-85.
Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.
Resetting the active TCC2 switches control to the standby TCC2. If the alarm clears when the ONS 15454 SDH switches to the standby TCC2, the user can assume that the original active TCC2 is the cause of the alarm.
Step 11 If resetting the TCC2 card does not clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card. If the TCC2 replacement does not clear the alarm, delete the problematic DCC termination:
a. Click the Provisioning > DCC/GCC/OSC tabs.
b. Highlight the problematic DCC termination.
c. Click Delete.
d. Click Yes in the confirmation dialog box.
Step 12 Recreate the DCC termination; refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 13 Verify that both ends of the DCC have been recreated at the optical ports.
Step 14 If the alarm has not cleared, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.6.58 EQPT
•Critical (CR), Service-Affecting (SA)
An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card.
If the EQPT alarm occurs with a BKUPMEMP alarm, see the "BKUPMEMP" alarm on page 2-40. The BKUPMEMP procedure also clears the EQPT alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the EQPT Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 3 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 4 If the physical reseat of the card fails to clear the alarm, complete the "Physically Replace a Card" procedure for the reporting card.
Caution Removing a card that currently caries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. Consult the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When replacing a card with an identical type of card, you do not need to change the CTC database.
Step 5 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.59 EQPT-MISS
•Critical (CR), Service-Affecting (SA)
The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or not fully inserted or that the ribbon cable connecting the AIE to the system board may be bad.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside 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 "Remove and Reinsert 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 SDH Procedure Guide.
Step 4 If the alarm does not clear, replace the ribbon cable from the AIE to the system board with a known-good ribbon cable.
Step 5 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
2.6.60 ERROR-CONFIG
•Minor (MN), Non-Service Affecting (NSA)
The Error in Startup Configuration alarm applies to the ML-series Ethernet cards. These cards process startup configuration files line by line. If one or more lines cannot be executed, the error causes the ERROR-CONFIG alarm. ERROR-CONFIG is not caused by hardware failure.
The typical reasons for an errored startup file are that (1) you stored the configuration for one type of ML card in the database and then installed another type in its slot, and (2) the configuration file contained a syntax error on one of the lines.
For information about provisioning the ML-series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide Release 4.1.
Clear the ERROR-CONFIG Alarm
Step 1 If you have a different type of ML card specified in the startup configuration file than what you have installed, create the correct startup configuration.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.1.
Step 2 Upload the configuration file to the TCC2:
a. In the node view, right-click the ML card graphic.
b. Choose IOS Startup Config from the shortcut menu.
c. Click Upload to TCC and navigate to the file location.
Step 3 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure.
Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start an IOS CLI for the card:
a. Right click the ML card graphic in node view.
b. Choose Open IOS Connection from the shortcut menu.
Note Open IOS Connection is not available unless the ML card is physically installed in the shelf.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.
Step 5 Execute the CLI command copy run start. The command copies the new card configuration into the database and clears the alarm.
Step 6 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country.
2.6.61 E-W-MISMATCH
•Major (MJ), Service-Affecting (SA)
A Procedural Error Misconnect East/West Direction alarm occurs when nodes in a ring have an east slot misconnected to another east slot or a west slot misconnected to another west slot. In most cases, the user did not connect the fibers correctly, or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but might change the traditional east-west node connection pattern of the ring.
Note The E-W-MISMATCH alarm also appears during the initial setup of a ring with its East-West slots and ports configured correctly. In this instance, the alarm clears itself shortly after the ring setup is complete.
Note The lower numbered slot on a node is traditionally labeled as the West slot. The higher numbered slot is traditionally labeled as the East slot. For example, Slot 6 is West and Slot 12 is East.
Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.
Clear the E-W-MISMATCH Alarm with a Physical Switch
Step 1 Diagram the ring setup, including nodes and spans, on a piece of paper or white board.
Step 2 In the node view, click View > Go to Network View.
Step 3 Label each of the nodes on the diagram with the same name that appears on the network map.
Step 4 Right-click each span to reveal the node name/slot/port for each end of the span.
Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1 - Node2/Slot6/Port1 (2F MS-SPRing OC48, Ring ID=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.
Step 6 Repeat Steps 4 and 5 for each span on your diagram.
Step 7 Label the highest slot at each node east and the lowest slot at each node west.
Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span.
Step 9 If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might 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 might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Step 10 If the alarm does not clear, log into http://www.cisco.com/tac for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco TAC toll-free numbers for your country in order to report a service-affecting problem.
Clear the E-W-MISMATCH Alarm in CTC
Step 1 Log into the misconnected node. A misconnected node has both ring fibers to its neighbor nodes misconnected.
Step 2 Click the Maintenance > MS-SPRing tabs.
