Table Of Contents
Alarm Troubleshooting
2.1 Alarm Indexes by Default Severity
2.1.1 Critical Alarms (CR)
2.1.2 Major Alarms (MJ)
2.1.3 Minor Alarms (MN)
2.1.4 NA Conditions
2.1.5 NR Conditions
2.2 Alarms and Conditions Indexed By Alphabetical Entry
2.3 Alarm Logical Objects
2.4 Alarm Index by Logical Object Type
2.5 DS3-12 E Line Alarms
2.6 Trouble Notifications
2.6.1 Alarm Characteristics
2.6.2 Condition Characteristics
2.6.3 Severities
2.6.4 Service Effect
2.6.5 States
2.7 Safety Summary
2.8 Alarm Procedures
2.8.1 AIS
Clear the AIS Condition
2.8.2 AIS-L
Clear the AIS-L Condition
2.8.3 AIS-P
Clear the AIS-P Condition
2.8.4 AIS-V
Clear the AIS-V Condition
2.8.5 ALS
2.8.6 AMPLI-INIT
Clear the AMPLI-INIT Condition
2.8.7 APC-CORRECTION-SKIPPED
2.8.8 APC-DISABLED
Clear the APC-DISABLED Condition
2.8.9 APC-END
2.8.10 APC-OUT-OF-RANGE
Clear the APC-OUT-OF-RANGE Condition
2.8.11 APSB
2.8.12 APSCDFLTK
Clear the APSCDFLTK Alarm
2.8.13 APSC-IMP
Clear the APSC-IMP Alarm
2.8.14 APSCINCON
Clear the APSCINCON Alarm
2.8.15 APSCM
Clear the APSCM Alarm
2.8.16 APSCNMIS
Clear the APSCNMIS Alarm
2.8.17 APSIMP
Clear the APSIMP Condition
2.8.18 APS-INV-PRIM
2.8.19 APS-PRIM-FAC
Clear the APS-PRIM-FAC Condition
2.8.20 APSMM
Clear the APSMM Alarm
2.8.21 APS-PRIM-SEC-MISM
Clear the APS-PRIM-SEC-MISM Alarm
2.8.22 AS-CMD
Clear the AS-CMD Condition
2.8.23 AS-MT
Clear the AS-MT Condition
2.8.24 AS-MT-OOG
Clear the AS-MT-OOG Condition
2.8.25 AUD-LOG-LOSS
Clear the AUD-LOG-LOSS Condition
2.8.26 AUD-LOG-LOW
2.8.27 AU-LOF
2.8.28 AUTOLSROFF
Clear the AUTOLSROFF Alarm
2.8.29 AUTORESET
Clear the AUTORESET Alarm
2.8.30 AUTOSW-AIS
Clear the AUTOSW-AIS Condition
2.8.31 AUTOSW-LOP (STSMON)
Clear the AUTOSW-LOP (STSMON) Condition
2.8.32 AUTOSW-LOP (VT-MON)
Clear the AUTOSW-LOP (VT-MON) Condition
2.8.33 AUTOSW-PDI
Clear the AUTOSW-PDI Condition
2.8.34 AUTOSW-SDBER
Clear the AUTOSW-SDBER Condition
2.8.35 AUTOSW-SFBER
Clear the AUTOSW-SFBER Condition
2.8.36 AUTOSW-UNEQ (STSMON)
Clear the AUTOSW-UNEQ (STSMON) Condition
2.8.37 AUTOSW-UNEQ (VT-MON)
Clear the AUTOSW-UNEQ (VT-MON) Condition
2.8.38 AWG-DEG
Clear the AWG-DEG Alarm
2.8.39 AWG-FAIL
Clear the AWG-FAIL Alarm
2.8.40 AWG-OVERTEMP
Clear the AWG-OVERTEMP Alarm
2.8.41 AWG-WARM-UP
2.8.42 BAT-FAIL
Clear the BAT-FAIL Alarm
2.8.43 BKUPMEMP
Clear the BKUPMEMP Alarm
2.8.44 BLSROSYNC
Clear the BLSROSYNC Alarm
2.8.45 BPV
Clear the BPV Alarm
2.8.46 CARLOSS (CE100T)
Clear the CARLOSS (CE100T) Alarm
2.8.47 CARLOSS (E100T, E1000F)
Clear the CARLOSS (E100T, E1000F) Alarm
2.8.48 CARLOSS (EQPT)
Clear the CARLOSS (EQPT) Alarm
2.8.49 CARLOSS (FC)
2.8.50 CARLOSS (G1000)
Clear the CARLOSS (G1000) Alarm
2.8.51 CARLOSS (GE)
Clear the CARLOSS (GE) Alarm
2.8.52 CARLOSS (ISC)
Clear the CARLOSS (ISC) Alarm
2.8.53 CARLOSS (ML100T, ML1000)
Clear the CARLOSS (ML100T, ML1000) Alarm
2.8.54 CARLOSS (TRUNK)
Clear the CARLOSS (TRUNK) Alarm
2.8.55 CASETEMP-DEG
Clear the CASETEMP-DEG Alarm
2.8.56 CLDRESTART
Clear the CLDRESTART Condition
2.8.57 COMIOXC
Clear the COMIOXC Alarm
2.8.58 COMM-FAIL
Clear the COMM-FAIL Alarm
2.8.59 CONTBUS-A-18
Clear the CONTBUS-A-18 Alarm
2.8.60 CONTBUS-B-18
Clear the CONTBUS-B-18 Alarm
2.8.61 CONTBUS-IO-A
Clear the CONTBUS-IO-A Alarm
2.8.62 CONTBUS-IO-B
Clear the CONTBUS-IO-B Alarm
2.8.63 CTNEQPT-MISMATCH
Clear the CTNEQPT-MISMATCH Condition
2.8.64 CTNEQPT-PBPROT
Clear the CTNEQPT-PBPROT Alarm
2.8.65 CTNEQPT-PBWORK
Clear the CTNEQPT-PBWORK Alarm
2.8.66 DATAFLT
Clear the DATAFLT Alarm
2.8.67 DBOSYNC
Clear the DBOSYNC Alarm
2.8.68 DS3-MISM
Clear the DS3-MISM Condition
2.8.69 DSP-COMM-FAIL
2.8.70 DSP-FAIL
Clear the DSP-FAIL Alarm
2.8.71 DUP-IPADDR
Clear the DUP-IPADDR Alarm
2.8.72 DUP-NODENAME
Clear the DUP-NODENAME Alarm
2.8.73 EHIBATVG
Clear the EHIBATVG Alarm
2.8.74 ELWBATVG
Clear the ELWBATVG Alarm
2.8.75 ENCAP-MISMATCH-P
Clear the ENCAP-MISMATCH-P Alarm
2.8.76 EOC
Clear the EOC Alarm
2.8.77 EOC-L
Clear the EOC-L Alarm
2.8.78 EQPT
Clear the EQPT Alarm
2.8.79 EQPT-DIAG
Clear the EQPT-DIAG Alarm
2.8.80 EQPT-MISS
Clear the EQPT-MISS Alarm
2.8.81 ERFI-P-CONN
Clear the ERFI-P-CONN Condition
2.8.82 ERFI-P-PAYLD
Clear the ERFI-P-PAYLD Condition
2.8.83 ERFI-P-SRVR
Clear the ERFI-P-SRVR Condition
2.8.84 ERROR-CONFIG
Clear the ERROR-CONFIG Alarm
2.8.85 ETH-LINKLOSS
Clear the ETH-LINKLOSS Condition
2.8.86 E-W-MISMATCH
Clear the E-W-MISMATCH Alarm with a Physical Switch
Clear the E-W-MISMATCH Alarm in CTC
2.8.87 EXCCOL
Clear the EXCCOL Alarm
2.8.88 EXERCISE-RING-FAIL
Clear the EXERCISE-RING-FAIL Condition
2.8.89 EXERCISE-SPAN-FAIL
Clear the EXERCISE-SPAN-FAIL Condition
2.8.90 EXT
Clear the EXT Alarm
2.8.91 EXTRA-TRAF-PREEMPT
Clear the EXTRA-TRAF-PREEMPT Alarm
2.8.92 FAILTOSW
Clear the FAILTOSW Condition
2.8.93 FAILTOSW-PATH
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
2.8.94 FAILTOSWR
Clear the FAILTOSWR Condition in a BLSR Configuration
2.8.95 FAILTOSWS
Clear the FAILTOSWS Condition
2.8.96 FAN
Clear the FAN Alarm
2.8.97 FC-NO-CREDITS
Clear the FC-NO-CREDITS Alarm
2.8.98 FE-AIS
Clear the FE-AIS Condition
2.8.99 FEC-MISM
Clear the FEC-MISM Alarm
2.8.100 FE-DS1-MULTLOS
Clear the FE-DS1-MULTLOS Condition
2.8.101 FE-DS1-NSA
Clear the FE-DS1-NSA Condition
2.8.102 FE-DS1-SA
Clear the FE-DS1-SA Condition
2.8.103 FE-DS1-SNGLLOS
Clear the FE-DS1-SNGLLOS Condition
2.8.104 FE-DS3-NSA
Clear the FE-DS3-NSA Condition
2.8.105 FE-DS3-SA
Clear the FE-DS3-SA Condition
2.8.106 FE-EQPT-NSA
Clear the FE-EQPT-NSA Condition
2.8.107 FE-FRCDWKSWBK-SPAN
Clear the FE-FRCDWKSWBK-SPAN Condition
2.8.108 FE-FRCDWKSWPR-RING
Clear the FE-FRCDWKSWPR-RING Condition
2.8.109 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-SPAN Condition
2.8.110 FE-IDLE
Clear the FE-IDLE Condition
2.8.111 FE-LOCKOUTOFPR-SPAN
Clear the FE-LOCKOUTOFPR-SPAN Condition
2.8.112 FE-LOF
Clear the FE-LOF Condition
2.8.113 FE-LOS
Clear the FE-LOS Condition
2.8.114 FE-MANWKSWBK-SPAN
Clear the FE-MANWKSWBK-SPAN Condition
2.8.115 FE-MANWKSWPR-RING
Clear the FE-MANWKSWPR-RING Condition
2.8.116 FE-MANWKSWPR-SPAN
Clear the FE-MANWKSWPR-SPAN Condition
2.8.117 FEPRLF
Clear the FEPRLF Alarm on a Four-Fiber BLSR
2.8.118 FIBERTEMP-DEG
Clear the FIBERTEMP-DEG Alarm
2.8.119 FORCED-REQ
Clear the FORCED-REQ Condition
2.8.120 FORCED-REQ-RING
Clear the FORCED-REQ-RING Condition
2.8.121 FORCED-REQ-SPAN
Clear the FORCED-REQ-SPAN Condition
2.8.122 FRCDSWTOINT
2.8.123 FRCDSWTOPRI
2.8.124 FRCDSWTOSEC
2.8.125 FRCDSWTOTHIRD
2.8.126 FRNGSYNC
Clear the FRNGSYNC Condition
2.8.127 FSTSYNC
2.8.128 FULLPASSTHR-BI
Clear the FULLPASSTHR-BI Condition
2.8.129 GAIN-HDEG
Clear the GAIN-HDEG Alarm
2.8.130 GAIN-HFAIL
Clear the GAIN-HFAIL Alarm
2.8.131 GAIN-LDEG
Clear the GAIN-LDEG Alarm
2.8.132 GAIN-LFAIL
Clear the GAIN-LFAIL Alarm
2.8.133 GCC-EOC
Clear the GCC-EOC Alarm
2.8.134 GE-OOSYNC
Clear the GE-OOSYNC Alarm
2.8.135 GFP-CSF
Clear the GFP-CSF Alarm
2.8.136 GFP-DE-MISMATCH
Clear the GFP-DE-MISMATCH Alarm
2.8.137 GFP-EX-MISMATCH
Clear the GFP-EX-MISMATCH Alarm
2.8.138 GFP-LFD
Clear the GFP-LFD Alarm
2.8.139 GFP-NO-BUFFERS
Clear the GFP-NO-BUFFERS Alarm
2.8.140 GFP-UP-MISMATCH
Clear the GFP-UP-MISMATCH Alarm
2.8.141 HELLO
Clear the HELLO Alarm
2.8.142 HIBATVG
Clear the HIBATVG Alarm
2.8.143 HI-CCVOLT
Clear the HI-CCVOLT Condition
2.8.144 HI-LASERBIAS
Clear the HI-LASERBIAS Alarm
2.8.145 HI-LASERTEMP
Clear the HI-LASERTEMP Alarm
2.8.146 HI-RXPOWER
Clear the HI-RXPOWER Alarm
2.8.147 HITEMP
Clear the HITEMP Alarm
2.8.148 HI-TXPOWER
Clear the HI-TXPOWER Alarm
2.8.149 HLDOVRSYNC
Clear the HLDOVRSYNC Condition
2.8.150 I-HITEMP
Clear the I-HITEMP Alarm
2.8.151 IMPROPRMVL
Clear the IMPROPRMVL Alarm
2.8.152 INC-ISD
2.8.153 INHSWPR
Clear the INHSWPR Condition
2.8.154 INHSWWKG
Clear the INHSWWKG Condition
2.8.155 INTRUSION-PSWD
Clear the INTRUSION-PSWD Condition
2.8.156 INVMACADR
Clear the INVMACADR Alarm
2.8.157 IOSCFGCOPY
2.8.158 KB-PASSTHR
Clear the KB-PASSTHR Condition
2.8.159 KBYTE-APS-CHANNEL-FAILURE
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
2.8.160 LAN-POL-REV
Clear the LAN-POL-REV Condition
2.8.161 LASER-APR
2.8.162 LASERBIAS-DEG
Clear the LASERBIAS-DEG Alarm
2.8.163 LASERBIAS-FAIL
Clear the LASERBIAS-FAIL Alarm
2.8.164 LASEREOL
Clear the LASEREOL Alarm
2.8.165 LASERTEMP-DEG
Clear the LASERTEMP-DEG Alarm
2.8.166 LCAS-CRC
Clear the LCAS-CRC Condition
2.8.167 LCAS-RX-FAIL
Clear the LCAS-RX-FAIL Condition
2.8.168 LCAS-TX-ADD
2.8.169 LCAS-TX-DNU
2.8.170 LKOUTPR-S
Clear the LKOUTPR-S Condition
2.8.171 LOA
Clear the LOA Alarm
2.8.172 LOCKOUT-REQ
Clear the LOCKOUT-REQ Condition
2.8.173 LOF (BITS)
Clear the LOF (BITS) Alarm
2.8.174 LOF (DS1)
Clear the LOF (DS1) Alarm
2.8.175 LOF (DS3)
Clear the LOF (DS3) Alarm
2.8.176 LOF (EC1)
Clear the LOF (EC1, EC1-12) Alarm
2.8.177 LOF (OCN)
Clear the LOF (OCN) Alarm
2.8.178 LOF (TRUNK)
Clear the LOF (TRUNK) Alarm
2.8.179 LO-LASERTEMP
Clear the LO-LASERTEMP Alarm
2.8.180 LOM
Clear the LOM Alarm
2.8.181 LOP-P
Clear the LOP-P Alarm
2.8.182 LOP-V
Clear the LOP-V Alarm
2.8.183 LO-RXPOWER
Clear the LO-RXPOWER Alarm
2.8.184 LOS (2R)
Clear the LOS (2R) Alarm
2.8.185 LOS (BITS)
Clear the LOS (BITS) Alarm
2.8.186 LOS (DS1)
Clear the LOS (DS1) Alarm
2.8.187 LOS (DS3)
Clear the LOS (DS3) Alarm
2.8.188 LOS (EC1, EC1-12)
Clear the LOS (EC1, EC1-12) Alarm
2.8.189 LOS (ESCON)
2.8.190 LOS (FUDC)
Clear the LOS (FUDC) Alarm
2.8.191 LOS (ISC)
Clear the LOS (ISC) Alarm
2.8.192 LOS (MSUDC)
2.8.193 LOS (OCN)
Clear the LOS (OCN) Alarm
2.8.194 LOS (OTS)
Clear the LOS (OTS) Alarm
2.8.195 LOS (TRUNK)
Clear the LOS (TRUNK) Alarm
2.8.196 LOS-O
Clear the LOS-O Alarm
2.8.197 LOS-P (OCH)
Clear the LOS-P (OCH) Alarm
2.8.198 LOS-P (OMS, OTS)
Clear the LOS-P (OMS, OTS) Alarm
2.8.199 LOS-P (TRUNK)
Clear the LOS-P (TRUNK) Alarm
2.8.200 LO-TXPOWER
Clear the LO-TXPOWER Alarm
2.8.201 LPBKCRS
Clear the LPBKCRS Condition
2.8.202 LPBKDS1FEAC
Clear the LPBKDS1FEAC Condition
2.8.203 LPBKDS1FEAC-CMD
2.8.204 LPBKDS3FEAC
Clear the LPBKDS3FEAC Condition
2.8.205 LPBKDS3FEAC-CMD
2.8.206 LPBKFACILITY (CE100T)
Clear the LPBKFACILITY (CE100T) Condition
2.8.207 LPBKFACILITY (DS1, DS3)
Clear the LPBKFACILITY (DS1, DS3) Condition
2.8.208 LPBKFACILITY (EC1)
Clear the LPBKFACILITY (EC1, EC1-12) Condition
2.8.209 LPBKFACILITY (ESCON)
2.8.210 LPBKFACILITY (FC)
Clear the LPBKFACILITY (FC) Condition
2.8.211 LPBKFACILITY (FCMR)
Clear the LPBKFACILITY (FCMR) Condition
2.8.212 LPBKFACILITY (G1000)
Clear the LPBKFACILITY (G1000) Condition
2.8.213 LPBKFACILITY (GE)
Clear the LPBKFACILITY (GE) Condition
2.8.214 LPBKFACILITY (ISC)
Clear the LPBKFACILITY (ISC) Condition
2.8.215 LPBKFACILITY (OCN)
Clear the LPBKFACILITY (OCN) Condition
2.8.216 LPBKFACILITY (TRUNK)
Clear the LPBKFACILITY (TRUNK) Condition
2.8.217 LPKTERMINAL (CE100T)
Clear the LPBKTERMINAL (CE100T) Condition
2.8.218 LPBKTERMINAL (DS1, DS3)
Clear the LPBKTERMINAL (DS1, DS3) Condition
2.8.219 LPBKTERMINAL (EC1)
Clear the LPBKTERMINAL (EC1, EC1-12) Condition
2.8.220 LPBKTERMINAL (ESCON)
2.8.221 LPBKTERMINAL (FC)
Clear the LPBKTERMINAL (FC) Condition
2.8.222 LPBKTERMINAL (FCMR)
Clear the LPBKTERMINAL (FCMR) Condition
2.8.223 LPBKTERMINAL (G1000)
Clear the LPBKTERMINAL (G1000) Condition
2.8.224 LPBKTERMINAL (GE)
Clear the LPBKTERMINAL (GE) Condition
2.8.225 LPBKTERMINAL (ISC)
Clear the LPBKTERMINAL (ISC) Condition
2.8.226 LPBKTERMINAL (OCN)
Clear the LPBKTERMINAL (OCN) Condition
2.8.227 LPBKTERMINAL (TRUNK)
Clear the LPBKTERMINAL (TRUNK) Condition
2.8.228 LWBATVG
Clear the LWBATVG Alarm
2.8.229 MAN-REQ
Clear the MAN-REQ Condition
2.8.230 MANRESET
2.8.231 MANSWTOINT
2.8.232 MANSWTOPRI
2.8.233 MANSWTOSEC
2.8.234 MANSWTOTHIRD
2.8.235 MANUAL-REQ-RING
Clear the MANUAL-REQ-RING Condition
2.8.236 MANUAL-REQ-SPAN
Clear the MANUAL-REQ-SPAN Condition
2.8.237 MEA (AIP)
Clear the MEA (AIP) Alarm
2.8.238 MEA (BIC)
Clear the MEA (BIC) Alarm
2.8.239 MEA (EQPT)
Clear the MEA (EQPT) Alarm
2.8.240 MEA (FAN)
Clear the MEA (FAN) Alarm
2.8.241 MEA (PPM)
Clear the MEA (PPM) Alarm
2.8.242 MEM-GONE
2.8.243 MEM-LOW
2.8.244 MFGMEM
Clear the MFGMEM Alarm
2.8.245 NO-CONFIG
Clear the NO-CONFIG Condition
2.8.246 NOT-AUTHENTICATED
2.8.247 OCHNC-INC
2.8.248 ODUK-1-AIS-PM
Clear the ODUK-1-AIS-PM Condition
2.8.249 ODUK-2-AIS-PM
Clear the ODUK-2-AIS-PM Condition
2.8.250 ODUK-3-AIS-PM
Clear the ODUK-3-AIS-PM Condition
2.8.251 ODUK-4-AIS-PM
Clear the ODUK-4-AIS-PM Condition
2.8.252 ODUK-AIS-PM
Clear the ODUK-AIS-PM Condition
2.8.253 ODUK-BDI-PM
Clear the ODUK-BDI-PM Condition
2.8.254 ODUK-LCK-PM
Clear the ODUK-LCK-PM Condition
2.8.255 ODUK-OCI-PM
Clear the ODUK-OCI-PM Condition
2.8.256 ODUK-SD-PM
Clear the ODUK-SD-PM Condition
2.8.257 ODUK-SF-PM
Clear the ODUK-SF-PM Condition
2.8.258 ODUK-TIM-PM
Clear the ODUK-TIM-PM Condition
2.8.259 OOU-TPT
Clear the OOT-TPT Condition
2.8.260 OPTNTWMIS
Clear the OPTNTWMIS Alarm
2.8.261 OPWR-HDEG
Clear the OPWR-HDEG Alarm
2.8.262 OPWR-HFAIL
Clear the OPWR-HFAIL Alarm
2.8.263 OPWR-LDEG
Clear the OPWR-LDEG Alarm
2.8.264 OPWR-LFAIL
Clear the OPWR-LFAIL Alarm
2.8.265 OSRION
Clear the OSRION Condition
2.8.266 OTUK-AIS
Clear the OTUK-AIS Condition
2.8.267 OTUK-BDI
Clear the OTUK-BDI Condition
2.8.268 OTUK-IAE
Clear the OTUK-IAE Alarm
2.8.269 OTUK-LOF
Clear the OTUK-LOF Alarm
2.8.270 OTUK-SD
Clear the OTUK-SD Condition
2.8.271 OTUK-SF
Clear the OTUK-SF Condition
2.8.272 OTUK-TIM
Clear the OTUK-TIM Condition
2.8.273 OUT-OF-SYNC
Clear the OUT-OF-SYNC Condition
2.8.274 PARAM-MISM
2.8.275 PDI-P
Clear the PDI-P Condition
2.8.276 PEER-NORESPONSE
Clear the PEER-NORESPONSE Alarm
2.8.277 PLM-P
Clear the PLM-P Alarm
2.8.278 PLM-V
Clear the PLM-V Alarm
2.8.279 PORT-ADD-PWR-DEG-HI
2.8.280 PORT-ADD-PWR-DEG-LOW
2.8.281 PORT-ADD-PWR-FAIL-HI
2.8.282 PORT-ADD-PWR-FAIL-LOW
Clear the PORT-ADD-PWR-FAIL-LOW Alarm
2.8.283 PORT-MISMATCH
2.8.284 PRC-DUPID
Clear the PRC-DUPID Alarm
2.8.285 PROTNA
Clear the PROTNA Alarm
2.8.286 PTIM
Clear the PTIM Alarm
2.8.287 PWR-FAIL-A
Clear the PWR-FAIL-A Alarm
2.8.288 PWR-FAIL-B
Clear the PWR-FAIL-B Alarm
2.8.289 PWR-FAIL-RET-A
Clear the PWR-FAIL-RET-A Alarm:
2.8.290 PWR-FAIL-RET-B
Clear the PWR-FAIL-RET-A Alarm
2.8.291 RAI
Clear the RAI Condition
2.8.292 RCVR-MISS
Clear the RCVR-MISS Alarm
2.8.293 RFI
Clear the RFI Condition
2.8.294 RFI-L
Clear the RFI-L Condition
2.8.295 RFI-P
Clear the RFI-P Condition
2.8.296 RFI-V
Clear the RFI-V Condition
2.8.297 RING-ID-MIS
Clear the RING-ID-MIS Alarm
2.8.298 RING-MISMATCH
Clear the RING-MISMATCH Alarm
2.8.299 RING-SW-EAST
2.8.300 RING-SW-WEST
2.8.301 RPRW
Clear the RPRW Condition
2.8.302 RUNCFG-SAVENEED
2.8.303 SD (DS1, DS3)
Clear the SD (DS1, DS3) Condition
2.8.304 SD (TRUNK)
Clear the SD (TRUNK) Condition
2.8.305 SD-L
Clear the SD-L Condition
2.8.306 SD-P
Clear the SD-P Condition
2.8.307 SD-V
Clear the SD-V Condition
2.8.308 SF (DS1, DS3)
Clear the SF (DS1, DS3) Condition
2.8.309 SF (TRUNK)
Clear the SF (TRUNK) Condition
2.8.310 SF-L
Clear the SF-L Condition
2.8.311 SF-P
Clear the SF-P Condition
2.8.312 SF-V
Clear the SF-V Condition
2.8.313 SFTWDOWN
2.8.314 SH-INS-LOSS-VAR-DEG-HIGH
2.8.315 SH-INS-LOSS-VAR-DEG-LOW
2.8.316 SHUTTER-OPEN
Clear the SHUTTER-OPEN Condition
2.8.317 SIGLOSS
Clear the SIGLOSS Alarm
2.8.318 SNTP-HOST
Clear the SNTP-HOST Alarm
2.8.319 SPAN-SW-EAST
2.8.320 SPAN-SW-WEST
2.8.321 SQUELCH
Clear the SQUELCH Condition
2.8.322 SQUELCHED
Clear the SQUELCHED Condition
2.8.323 SQM
Clear the SQM Alarm
2.8.324 SSM-DUS
2.8.325 SSM-FAIL
Clear the SSM-FAIL Alarm
2.8.326 SSM-LNC
2.8.327 SSM-OFF
Clear the SSM-OFF Condition
2.8.328 SSM-PRC
2.8.329 SSM-PRS
2.8.330 SSM-RES
2.8.331 SSM-SDN-TN
2.8.332 SSM-SETS
2.8.333 SSM-SMC
2.8.334 SSM-ST2
2.8.335 SSM-ST3
2.8.336 SSM-ST3E
2.8.337 SSM-ST4
2.8.338 SSM-STU
Clear the SSM-STU Condition
2.8.339 SSM-TNC
2.8.340 SWMTXMOD
Clear the SWMTXMOD Alarm
2.8.341 SWTOPRI
2.8.342 SWTOSEC
Clear the SWTOSEC Condition
2.8.343 SWTOTHIRD
Clear the SWTOTHIRD Condition
2.8.344 SYNC-FREQ
Clear the SYNC-FREQ Condition
2.8.345 SYNCLOSS
Clear the SYNCLOSS Alarm
2.8.346 SYNCPRI
Clear the SYNCPRI Alarm
2.8.347 SYNCSEC
Clear the SYNCSEC Alarm
2.8.348 SYNCTHIRD
Clear the SYNCTHIRD Alarm
2.8.349 SYSBOOT
2.8.350 TEMP-MISM
Clear the TEMP-MISM Condition
2.8.351 TIM
Clear the TIM Alarm
2.8.352 TIM-MON
Clear the TIM-MON Alarm
2.8.353 TIM-P
Clear the TIM-P Alarm
2.8.354 TIM-V
Clear the TIM-V Alarm
2.8.355 TPTFAIL (CE100T)
Clear the TPTFAIL (CE100T) Alarm
2.8.356 TPTFAIL (FCMR)
Clear the TPTFAIL (FCMR) Alarm
2.8.357 TPTFAIL (G1000)
Clear the TPTFAIL (G1000) Alarm
2.8.358 TPTFAIL (ML100T, ML1000)
Clear the TPTFAIL (ML100T, ML1000) Alarm
2.8.359 TRMT
Clear the TRMT Alarm
2.8.360 TRMT-MISS
Clear the TRMT-MISS Alarm
2.8.361 TX-AIS
Clear the TX-AIS Condition
2.8.362 TX-RAI
Clear the TX-RAI Condition
2.8.363 UNC-WORD
Clear the UNC-WORD Condition
2.8.364 UNEQ-P
Clear the UNEQ-P Alarm
2.8.365 UNEQ-V
Clear the UNEQ-V Alarm
2.8.366 UNREACHABLE-TARGET-POWER
2.8.367 UT-COMM-FAIL
Clear the UT-COMM-FAIL Alarm
2.8.368 UT-FAIL
Clear the UT-FAIL Alarm
2.8.369 VCG-DEG
Clear the VCG-DEG Condition
2.8.370 VCG-DOWN
Clear the VCG-DOWN Condition
2.8.371 VOA-HDEG
Clear the VOA-HDEG Alarm
2.8.372 VOA-HFAIL
Clear the VOA-HFAIL Alarm
2.8.373 VOA-LDEG
Clear the VOA-LDEG Alarm
2.8.374 VOA-LFAIL
Clear the VOA-LFAIL Alarm
2.8.375 VOLT-MISM
Clear the VOLT-MISM Condition
2.8.376 WKSWPR
Clear the WKSWPR Condition
2.8.377 WTR
2.8.378 WVL-MISMATCH
Clear the WVL-MISMATCH alarm
2.9 DWDM Card LED Activity
2.9.1 DWDM Card LED Activity After Insertion
2.9.2 DWDM Card LED Activity During Reset
2.10 Traffic Card LED Activity
2.10.1 Typical Traffic Card LED Activity After Insertion
2.10.2 Typical Traffic Card LED Activity During Reset
2.10.3 Typical Card LED State After Successful Reset
2.10.4 Typical Cross-Connect LED Activity During Side Switch
2.11 Frequently Used Alarm Troubleshooting Procedures
2.11.1 Node and Ring Identification, Change, Visibility, and Termination
Identify a BLSR Ring Name or Node ID Number
Change a BLSR Ring Name
Change a BLSR Node ID Number
Verify Node Visibility for Other Nodes
2.11.2 Protection Switching, Lock Initiation, and Clearing
Initiate a 1+1 Protection Port Force Switch Command
Initiate a 1+1 Protection Port Manual Switch Command
Clear a 1+1 Protection Port Force or Manual Switch Command
Initiate a Card or Port Lock On Command
Initiate a Card or Port Lock Out Command
Clear a Card or Port Lock On or Lock Out Command
Initiate a 1:1 Card Switch Command
Initiate a Force Switch for All Circuits on a Path Protection Span
Initiate a Manual Switch for All Circuits on a Path Protection Span
Initiate a Lock Out of Protect-Switch for All Circuits on a Path Protection Span
Clear a Path Protection Span External Switching Command
Initiate a Force Ring Switch on a BLSR
Initiate a Force Span Switch on a Four-Fiber BLSR
Initiate a Manual Ring Switch on a BLSR
Initiate a Lock Out on a BLSR Protect Span
Initiate an Exercise Ring Switch on a BLSR
Initiate an Exercise Ring Switch on a Four Fiber BLSR
Clear a BLSR External Switching Command
2.11.3 CTC Card Resetting and Switching
Reset a Traffic Card in CTC
Reset an Active TCC2/TCC2P and Activate the Standby Card
Side Switch the Active and Standby XC10G Cross-Connect Cards
2.11.4 Physical Card Reseating, Resetting, and Replacement
Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card
Remove and Reinsert (Reseat) Any Card
Physically Replace a Traffic Card
Physically Replace an In-Service Cross-Connect Card
2.11.5 Generic Signal and Circuit Procedures
Verify the Signal BER Threshold Level
Delete a Circuit
Verify or Create Node Section DCC Terminations
Clear an OC-N Card Facility or Terminal Loopback Circuit
Clear an OC-N Card Cross-Connect (XC) Loopback Circuit
Clear a DS3XM-6 or DS3XM-12 Card Loopback Circuit
Clear Other DS-N Card, EC-1, or G1000 Card Loopbacks
Clear an MXP, TXP, or FC_MR Card Loopback Circuit
Clear an Ethernet Card Loopback Circuit
2.11.6 Air Filter and Fan Procedures
Inspect, Clean, and Replace the Reusable Air Filter
Remove and Reinsert a Fan-Tray Assembly
Replace the Fan-Tray Assembly
2.11.7 Interface Procedures
Replace the Electrical Interface Assembly
Replace the Alarm Interface Panel
Alarm Troubleshooting
Note 
The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables 2-1 through 2-5 provide lists of ONS 15454 alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-7 gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in Table 2-8. For a comprehensive list of all conditions, refer to the Cisco ONS SONET TL1 Command Guide.
An alarm's troubleshooting procedure applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call the Cisco Technical Assistance Center (1 800 553-2447).
More information about alarm profile information modification and downloads are located in the Cisco ONS 15454 Procedure Guide Chapter 7, "Manage Alarms."
2.1 Alarm Indexes by Default Severity
The following tables group alarms and conditions by their default severities in the ONS 15454 system. These severities are the same whether they are reported in the CTC Alarms window severity (SEV) column or in TL1.
Note The CTC default alarm profile contains some alarms or conditions that are not currently implemented but are reserved for future use.
Note The CTC default alarm profile in some cases contains two severities for one alarm (for example, MJ/MN). The ONS 15454 platform default severity comes first (in this example, MJ), but the alarm can be demoted to the second severity in the presence of a higher-ranking alarm. This is in accordance with Telcordia GR-474.
2.1.1 Critical Alarms (CR)
Table 2-1 alphabetically lists ONS 15454 Critical alarms.
2.1.2 Major Alarms (MJ)
Table 2-2 alphabetically lists ONS 15454 Major alarms.
2.1.3 Minor Alarms (MN)
Table 2-3 alphabetically lists ONS 15454 Minor alarms.
2.1.4 NA Conditions
Table 2-4 alphabetically lists ONS 15454 Not Alarmed conditions.
2.1.5 NR Conditions
Table 2-5 alphabetically lists ONS 15454 Not Reported conditions.
2.2 Alarms and Conditions Indexed By Alphabetical Entry
Table 2-6 alphabetically lists all ONS 15454 alarms and conditions.
2.3 Alarm Logical Objects
The CTC alarm profile list organizes all alarms and conditions according to the logical objects they are raised against. These logical objects represent physical objects such as cards, logical objects such as circuits, or transport and signal monitoring entities such as the SONET or ITU-T G.709 optical overhead bits. One alarm might appear in multiple entries when it can be raised against multiple objects. For example, the loss of signal (LOS) alarm can be raised against the optical signal (OC-N) or the optical transport layer overhead (OTN) as well as other objects. Therefore, both OCN:LOS and OTN:LOS appear in the list (as well as the other objects).
Alarm profile list objects are defined in Table 2-7.
Note Alarm logical object names can appear as abbreviated versions of standard terms used in the system and the documentation. For example, the "OCN" logical object refers to the OC-N signal. Logical object names or industry-standard terms are used within the entries as appropriate.
Table 2-7 Alarm Logical Object Type Definition
Logical Object
|
Definition
|
2R
|
Reshape and retransmit (used for transponder [TXP] cards).
|
AICI-AEP
|
Alarm Interface Controller-International/alarm expansion panel. A combination term that refers to this platform's AIC card.
|
AIP
|
Auxiliary interface protection module.
|
AOTS
|
Amplified optical transport section.
|
BIC
|
Backplane interface connector.
|
BITS
|
Building integrated timing supply incoming references (BITS-1, BITS-2).
|
BPLANE
|
The backplane.
|
CE100T
|
CE-100T-8 card.
|
DS1
|
A DS-1 line on a DS-1 or DS-3 electrical card (DS1-14, DS1N-14, DS3N-12E, DS3XM-6, DS3XM-12).
|
DS3
|
A DS-3 line on a DS-3 electrical card (DS3-12, DS3N-12, DS3-12E, DS3XM-6, and DS3XM-12).
|
E1000F
|
An E1000 Ethernet card (E1000-2, E1000-2G).
|
E100T
|
An E100 Ethernet card (E100T-12, E100T-G).
|
EC1
|
Any EC1 port (including EC1-12 card ports).
|
EC1-12
|
An EC1-12 electrical card.
|
ENVALRM
|
An environmental alarm port.
|
EQPT
|
A card, its physical objects, and its logical objects as they are located in any of the eight non-common card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, synchronous transport signals (STS), and virtual tributaries (VT).
|
ESCON
|
Enterprise System Connection fiber optic technology, referring to the following TXP cards: TXP_MR_2.5G, TXPP_MR_2.5G.
|
EXT-SREF
|
BITS outgoing references (SYNC-BITS1, SYNC-BITS2).
|
FAN
|
Fan-tray assembly.
|
FC
|
Fibre channel data transfer architecture, referring to the following muxponder (MXP) or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E.
|
FCMR
|
An FC_MR-4 Fibre Channel card.
|
FUDC
|
SONET F1 byte user data channel for ONS 15454 ML-Series Ethernet cards.
|
G1000
|
A G1000 Ethernet card (G1000-4).
|
GE
|
Gigabit Ethernet, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10G.
|
GFP-FAC
|
Generic framing procedure facility port, referring to all MXP and TXP cards.
|
ISC
|
Inter-service channel, referring to MXP and TXP cards.
|
ML1000
|
An ML1000 Ethernet card (ML1000-2).
|
ML100T
|
An ML100 card (ML100T-12).
|
MSUDC
|
Multiplex section user data channel.
|
NE
|
The entire network element.
|
NE-SREF
|
The timing status of the NE.
|
OCH
|
The optical channel, referring to dense wavelength division multiplexing (DWDM) cards.
|
OCHNC-CONN
|
The optical channel connection, referring to DWDM cards.
|
OCN
|
An OC-N line on any OC-N card.
|
OMS
|
Optical multiplex section.
|
OSC-RING
|
Optical service channel ring.
|
OTS
|
Optical transport section.
|
PPM
|
Pluggable port module, referring to MXP and TXP cards.
|
PWR
|
Power equipment.
|
STSMON
|
STS alarm detection at the monitor point (upstream from the cross-connect).
|
STSTRM
|
STS alarm detection at termination (downstream from the cross-connect).
|
TRUNK
|
The optical or DWDM card carrying the high-speed signal; referring to MXP or TXP cards.
|
VCG
|
A virtual concatenation group of VTs.
|
VT-MON
|
VT1 alarm detection at the monitor point (upstream from the cross-connect).
|
VT-TERM
|
VT1 alarm detection at termination (downstream from the cross-connect).
|
2.4 Alarm Index by Logical Object Type
Table 2-8 lists all ONS 15454 Release 5.0 alarms and logical objects as they are given in the system alarm profile. The list entries are organized by logical object name and then by alarm or condition name. Each entry contains a page number that refers to an alarm description in this chapter. Where appropriate, the alarm entries also contain troubleshooting procedures.
Note In a mixed network containing different types of nodes (such as ONS 15310, ONS 15454, and ONS 15600), the initially displayed alarm list in the Provisioning > Alarm Profiles > Alarm Profile Editor tab lists all conditions applicable to all nodes in the network. However, when you load the default severity profile from a node, only applicable alarms will display severity levels. Nonapplicable alarms can display "use default" or "unset."
Note In some cases this list does not follow alphabetical order, but it does reflect the order shown in CTC.
Table 2-8 Alarm Index by Logical Object
2R: ALS
|
FC: LOCKOUT-REQ
|
OCN: SF-L
|
2R: AS-CMD
|
FC: LPBKFACILITY (FC)
|
OCN: SPAN-SW-EAST
|
2R: AS-MT
|
FC: LPBKTERMINAL (FC)
|
OCN: SPAN-SW-WEST
|
2R: FAILTOSW
|
FC: MANUAL-REQ-SPAN
|
OCN: SQUELCH
|
2R: FORCED-REQ-SPAN
|
FC: OUT-OF-SYNC
|
OCN: SQUELCHED
|
2R: HI-LASERBIAS
|
FC: SIGLOSS
|
OCN: SSM-DUS
|
2R: HI-RXPOWER
|
FC: SQUELCHED
|
OCN: SSM-FAIL
|
2R: HI-TXPOWER
|
FC: SYNCLOSS
|
OCN: SSM-OFF
|
2R: LO-RXPOWER
|
FC: WKSWPR
|
OCN: SSM-PRS
|
2R: LO-TXPOWER
|
FC: WTR
|
OCN: SSM-RES
|
2R: LOCKOUT-REQ
|
FCMR: AS-CMD
|
OCN: SSM-SMC
|
2R: LOS (2R)
|
FCMR: AS-MT
|
OCN: SSM-ST2
|
2R: MANUAL-REQ-SPAN
|
FCMR: FC-NO-CREDITS
|
OCN: SSM-ST3
|
2R: SQUELCHED
|
FCMR: GFP-CSF
|
OCN: SSM-ST3E
|
2R: WKSWPR
|
FCMR: GFP-DE-MISMATCH
|
OCN: SSM-ST4
|
2R: WTR
|
FCMR: GFP-EX-MISMATCH
|
OCN: SSM-STU
|
AICI-AEP: EQPT
|
FCMR: GFP-LFD
|
OCN: SSM-TNC
|
AICI-AEP: MFGMEM
|
FCMR: GFP-NO-BUFFERS
|
OCN: SYNC-FREQ
|
AICI-AIE: EQPT
|
FCMR: GFP-UP-MISMATCH
|
OCN: TIM
|
AICI-AIE: MFGMEM
|
FCMR: LPBKFACILITY (FCMR)
|
OCN: TIM-MON
|
AIP: INVMACADR
|
FCMR: LPBKTERMINAL (FCMR)
|
OCN: WKSWPR
|
AIP: MEA (AIP)
|
FCMR: PORT-MISMATCH
|
OCN: WTR
|
AIP: MFGMEM
|
FCMR: SIGLOSS
|
OMS: APC-CORRECTION-SKIPPED
|
AOTS: ALS
|
FCMR: SYNCLOSS
|
OMS: APC-OUT-OF-RANGE
|
AOTS: AMPLI-INIT
|
FCMR: TPTFAIL (FCMR)
|
OMS: AS-CMD
|
AOTS: APC-CORRECTION-SKIPPED
|
FUDC: AIS
|
OMS: AS-MT
|
AOTS: APC-OUT-OF-RANGE
|
FUDC: LOS (FUDC)
|
OMS: LOS-O
|
AOTS: AS-CMD
|
G1000: AS-CMD
|
OMS: LOS-P (OMS, OTS)
|
AOTS: AS-MT
|
G1000: AS-MT
|
OMS: OPWR-HDEG
|
AOTS: CASETEMP-DEG
|
G1000: CARLOSS (G1000)
|
OMS: OPWR-HFAIL
|
AOTS: FIBERTEMP-DEG
|
G1000: LPBKFACILITY (G1000)
|
OMS: OPWR-LDEG
|
AOTS: GAIN-HDEG
|
G1000: LPBKTERMINAL (G1000)
|
OMS: OPWR-LFAIL
|
AOTS: GAIN-HFAIL
|
G1000: TPTFAIL (G1000)
|
OMS: PARAM-MISM
|
AOTS: GAIN-LDEG
|
GE: ALS
|
OMS: VOA-HDEG
|
AOTS: GAIN-LFAIL
|
GE: AS-CMD
|
OMS: VOA-HFAIL
|
AOTS: LASER-APR
|
GE: AS-MT
|
OMS: VOA-LDEG
|
AOTS: LASERBIAS-DEG
|
GE: CARLOSS (GE)
|
OMS: VOA-LFAIL
|
AOTS: LASERBIAS-FAIL
|
GE: FAILTOSW
|
OSC-RING: RING-ID-MIS
|
AOTS: LASERTEMP-DEG
|
GE: FORCED-REQ-SPAN
|
OTS: APC-CORRECTION-SKIPPED
|
AOTS: OPWR-HDEG
|
GE: GE-OOSYNC
|
OTS: APC-OUT-OF-RANGE
|
AOTS: OPWR-HFAIL
|
GE: HI-LASERBIAS
|
OTS: AS-CMD
|
AOTS: OPWR-LDEG
|
GE: HI-RXPOWER
|
OTS: AS-MT
|
AOTS: OPWR-LFAIL
|
GE: HI-TXPOWER
|
OTS: AWG-DEG
|
AOTS: OSRION
|
GE: LO-RXPOWER
|
OTS: AWG-FAIL
|
AOTS: PARAM-MISM
|
GE: LO-TXPOWER
|
OTS: AWG-OVERTEMP
|
AOTS: VOA-HDEG
|
GE: LOCKOUT-REQ
|
OTS: AWG-WARM-UP
|
AOTS: VOA-HFAIL
|
GE: LPBKFACILITY (GE)
|
OTS: LASERBIAS-DEG
|
AOTS: VOA-LDEG
|
GE: LPBKTERMINAL (GE)
|
OTS: LOS (OTS)
|
AOTS: VOA-LFAIL
|
GE: MANUAL-REQ-SPAN
|
OTS: LOS-O
|
BIC: MEA (BIC)
|
GE: OUT-OF-SYNC
|
OTS: LOS-P (OMS, OTS)
|
BITS: AIS
|
GE: SIGLOSS
|
OTS: OPWR-HDEG
|
BITS: BPV
|
GE: SQUELCHED
|
OTS: OPWR-HFAIL
|
BITS: HI-CCVOLT
|
GE: SYNCLOSS
|
OTS: OPWR-LDEG
|
BITS: LOF (BITS)
|
GE: WKSWPR
|
OTS: OPWR-LFAIL
|
BITS: LOS (BITS)
|
GE: WTR
|
OTS: OSRION
|
BITS: SSM-DUS
|
GFP-FAC: AS-CMD
|
OTS: PARAM-MISM
|
BITS: SSM-FAIL
|
GFP-FAC: AS-MT
|
OTS: SH-INS-LOSS-VAR-DEG-HIGH
|
BITS: SSM-OFF
|
GFP-FAC: GFP-CSF
|
OTS: SH-INS-LOSS-VAR-DEG-LOW
|
BITS: SSM-PRS
|
GFP-FAC: GFP-DE-MISMATCH
|
OTS: SHUTTER-OPEN
|
BITS: SSM-RES
|
GFP-FAC: GFP-EX-MISMATCH
|
OTS: VOA-HDEG
|
BITS: SSM-SMC
|
GFP-FAC: GFP-LFD
|
OTS: VOA-HFAIL
|
BITS: SSM-ST2
|
GFP-FAC: GFP-NO-BUFFERS
|
OTS: VOA-LDEG
|
BITS: SSM-ST3
|
GFP-FAC: GFP-UP-MISMATCH
|
OTS: VOA-LFAIL
|
BITS: SSM-ST3E
|
ISC: ALS
|
PPM: AS-CMD
|
BITS: SSM-ST4
|
ISC: AS-CMD
|
PPM: AS-MT
|
BITS: SSM-STU
|
ISC: AS-MT
|
PPM: EQPT
|
BITS: SSM-TNC
|
ISC: CARLOSS (ISC)
|
PPM: HI-LASERBIAS
|
BITS: SYNC-FREQ
|
ISC: FAILTOSW
|
PPM: HI-LASERTEMP
|
BPLANE: AS-CMD
|
ISC: FORCED-REQ-SPAN
|
PPM: HI-TXPOWER
|
BPLANE: MFGMEM
|
ISC: GE-OOSYNC
|
PPM: IMPROPRMVL
|
CE100T: AS-CMD
|
ISC: HI-LASERBIAS
|
PPM: LO-TXPOWER
|
CE100T: AS-MT
|
ISC: HI-RXPOWER
|
PPM: MEA (PPM)
|
CE100T: CARLOSS (CE100T)
|
ISC: HI-TXPOWER
|
PPM: MFGMEM
|
CE100T: GFP-CSF
|
ISC: LO-RXPOWER
|
PWR: AS-CMD
|
CE100T: GFP-LFD
|
ISC: LO-TXPOWER
|
PWR: BAT-FAIL
|
CE100T: LPBKFACILITY (CE100T)
|
ISC: LOCKOUT-REQ
|
PWR: EHIBATVG
|
CE100T: LPKTERMINAL (CE100T)
|
ISC: LOS (ISC)
|
PWR: ELWBATVG
|
CE100T: RPRW
|
ISC: LPBKFACILITY (ISC)
|
PWR: HIBATVG
|
CE100T: TPTFAIL (CE100T)
|
ISC: LPBKTERMINAL (ISC)
|
PWR: LWBATVG
|
DS1: AIS
|
ISC: MANUAL-REQ-SPAN
|
PWR: VOLT-MISM
|
DS1: AS-CMD
|
ISC: OUT-OF-SYNC
|
STSMON: AIS-P
|
DS1: AS-MT
|
ISC: SIGLOSS
|
STSMON: AUTOSW-AIS
|
DS1: LOF (DS1)
|
ISC: SQUELCHED
|
STSMON: AUTOSW-LOP (STSMON)
|
DS1: LOS (DS1)
|
ISC: SYNCLOSS
|
STSMON: AUTOSW-PDI
|
DS1: LPBKDS1FEAC
|
ISC: WKSWPR
|
STSMON: AUTOSW-SDBER
|
DS1: LPBKDS1FEAC-CMD
|
ISC: WTR
|
STSMON: AUTOSW-SFBER
|
DS1: LPBKFACILITY (DS1, DS3)
|
ML1000: AS-CMD
|
STSMON: AUTOSW-UNEQ (STSMON)
|
DS1: LPBKTERMINAL (DS1, DS3)
|
ML1000: AS-MT
|
STSMON: ERFI-P-CONN
|
DS1: RAI
|
ML1000: CARLOSS (ML100T, ML1000)
|
STSMON: ERFI-P-PAYLD
|
DS1: RCVR-MISS
|
ML1000: GFP-CSF
|
STSMON: ERFI-P-SRVR
|
DS1: SD (DS1, DS3)
|
ML1000: GFP-DE-MISMATCH
|
STSMON: FAILTOSW-PATH
|
DS1: SF (DS1, DS3)
|
ML1000: GFP-EX-MISMATCH
|
STSMON: FORCED-REQ
|
DS1: TRMT
|
ML1000: GFP-LFD
|
STSMON: LOCKOUT-REQ
|
DS1: TRMT-MISS
|
ML1000: GFP-NO-BUFFERS
|
STSMON: LOP-P
|
DS1: TX-AIS
|
ML1000: GFP-UP-MISMATCH
|
STSMON: LPBKCRS
|
DS1: TX-RAI
|
ML1000: RPRW
|
STSMON: MAN-REQ
|
DS3: AIS
|
ML1000: TPTFAIL (ML100T, ML1000)
|
STSMON: PDI-P
|
DS3: AS-CMD
|
ML100T: AS-CMD
|
STSMON: PLM-P
|
DS3: AS-MT
|
ML100T: AS-MT
|
STSMON: RFI-P
|
DS3: DS3-MISM
|
ML100T: CARLOSS (ML100T, ML1000)
|
STSMON: SD-P
|
DS3: FE-AIS
|
ML100T: GFP-CSF
|
STSMON: SF-P
|
DS3: FE-DS1-MULTLOS
|
ML100T: GFP-DE-MISMATCH
|
STSMON: TIM-P
|
DS3: FE-DS1-NSA
|
ML100T: GFP-EX-MISMATCH
|
STSMON: UNEQ-P
|
DS3: FE-DS1-SA
|
ML100T: GFP-LFD
|
STSMON: WKSWPR
|
DS3: FE-DS1-SNGLLOS
|
ML100T: GFP-NO-BUFFERS
|
STSMON: WTR
|
DS3: FE-DS3-NSA
|
ML100T: GFP-UP-MISMATCH
|
STSTRM: AIS-P
|
DS3: FE-DS3-SA
|
ML100T: RPRW
|
STSTRM: AS-MT-OOG
|
DS3: FE-EQPT-NSA
|
ML100T: TPTFAIL (ML100T, ML1000)
|
STSTRM: AU-LOF
|
DS3: FE-IDLE
|
MSUDC: AIS
|
STSTRM: ENCAP-MISMATCH-P
|
DS3: FE-LOF
|
MSUDC: LOS (MSUDC)
|
STSTRM: ERFI-P-CONN
|
DS3: FE-LOS
|
NE-SREF: FRCDSWTOINT
|
STSTRM: ERFI-P-PAYLD
|
DS3: INC-ISD
|
NE-SREF: FRCDSWTOPRI
|
STSTRM: ERFI-P-SRVR
|
DS3: LOF (DS3)
|
NE-SREF: FRCDSWTOSEC
|
STSTRM: LCAS-CRC
|
DS3: LOS (DS3)
|
NE-SREF: FRCDSWTOTHIRD
|
STSTRM: LCAS-RX-FAIL
|
DS3: LPBKDS1FEAC
|
NE-SREF: FRNGSYNC
|
STSTRM: LCAS-TX-ADD
|
DS3: LPBKDS3FEAC
|
NE-SREF: FSTSYNC
|
STSTRM: LCAS-TX-DNU
|
DS3: LPBKDS3FEAC-CMD
|
NE-SREF: HLDOVRSYNC
|
STSTRM: LOM
|
DS3: LPBKFACILITY (DS1, DS3)
|
NE-SREF: MANSWTOINT
|
STSTRM: LOP-P
|
DS3: LPBKTERMINAL (DS1, DS3)
|
NE-SREF: MANSWTOPRI
|
STSTRM: OOU-TPT
|
DS3: RAI
|
NE-SREF: MANSWTOSEC
|
STSTRM: PDI-P
|
DS3: SD (DS1, DS3)
|
NE-SREF: MANSWTOTHIRD
|
STSTRM: PLM-P
|
DS3: SF (DS1, DS3)
|
NE-SREF: SSM-PRS
|
STSTRM: RFI-P
|
DS3: TX-AIS
|
NE-SREF: SSM-RES
|
STSTRM: SD-P
|
DS3: TX-RAI
|
NE-SREF: SSM-SMC
|
STSTRM: SF-P
|
E1000F: AS-CMD
|
NE-SREF: SSM-ST2
|
STSTRM: SQM
|
E1000F: CARLOSS (E100T, E1000F)
|
NE-SREF: SSM-ST3
|
STSTRM: TIM-P
|
E100T: AS-CMD
|
NE-SREF: SSM-ST3E
|
STSTRM: UNEQ-P
|
E100T: CARLOSS (E100T, E1000F)
|
NE-SREF: SSM-ST4
|
TRUNK: AIS
|
EC1-12: AIS-L
|
NE-SREF: SSM-STU
|
TRUNK: ALS
|
EC1-12: AS-CMD
|
NE-SREF: SSM-TNC
|
TRUNK: AS-CMD
|
EC1-12: AS-MT
|
NE-SREF: SWTOPRI
|
TRUNK: AS-MT
|
EC1-12: LOF (EC1)
|
NE-SREF: SWTOSEC
|
TRUNK: CARLOSS (TRUNK)
|
EC1-12: LOS (EC1, EC1-12)
|
NE-SREF: SWTOTHIRD
|
TRUNK: DSP-COMM-FAIL
|
EC1-12: LPBKFACILITY (EC1)
|
NE-SREF: SYNCPRI
|
TRUNK: DSP-FAIL
|
EC1-12: LPBKTERMINAL (EC1)
|
NE-SREF: SYNCSEC
|
TRUNK: EOC
|
EC1-12: RFI-L
|
NE-SREF: SYNCTHIRD
|
TRUNK: EOC-L
|
EC1-12: SD-L
|
NE: APC-DISABLED
|
TRUNK: FAILTOSW
|
EC1-12: SF-L
|
NE: APC-END
|
TRUNK: FEC-MISM
|
EC1: AIS-L
|
NE: AS-CMD
|
TRUNK: FORCED-REQ-SPAN
|
EC1: AS-CMD
|
NE: AUD-LOG-LOSS
|
TRUNK: GCC-EOC
|
EC1: AS-MT
|
NE: AUD-LOG-LOW
|
TRUNK: GE-OOSYNC
|
EC1: LOF (EC1)
|
NE: DATAFLT
|
TRUNK: HI-LASERBIAS
|
EC1: LOS (EC1, EC1-12)
|
NE: DBOSYNC
|
TRUNK: HI-RXPOWER
|
EC1: LPBKFACILITY (EC1)
|
NE: DUP-IPADDR
|
TRUNK: HI-TXPOWER
|
EC1: LPBKTERMINAL (EC1)
|
NE: DUP-NODENAME
|
TRUNK: LO-RXPOWER
|
EC1: RFI-L
|
NE: ETH-LINKLOSS
|
TRUNK: LO-TXPOWER
|
EC1: SD-L
|
NE: HITEMP
|
TRUNK: LOCKOUT-REQ
|
EC1: SF-L
|
NE: I-HITEMP
|
TRUNK: LOF (TRUNK)
|
ENVALRM: EXT
|
NE: INTRUSION-PSWD
|
TRUNK: LOM
|
EQPT: AS-CMD
|
NE: LAN-POL-REV
|
TRUNK: LOS (TRUNK)
|
EQPT: AS-MT
|
NE: OPTNTWMIS
|
TRUNK: LOS-P (TRUNK)
|
EQPT: AUTORESET
|
NE: SNTP-HOST
|
TRUNK: LPBKFACILITY (TRUNK)
|
EQPT: BKUPMEMP
|
NE: SYSBOOT
|
TRUNK: LPBKTERMINAL (TRUNK)
|
EQPT: CARLOSS (EQPT)
|
NE: TEMP-MISM
|
TRUNK: MANUAL-REQ-SPAN
|
EQPT: CLDRESTART
|
OCH: APC-CORRECTION-SKIPPED
|
TRUNK: ODUK-1-AIS-PM
|
EQPT: COMIOXC
|
OCH: APC-OUT-OF-RANGE
|
TRUNK: ODUK-2-AIS-PM
|
EQPT: COMM-FAIL
|
OCH: AS-CMD
|
TRUNK: ODUK-3-AIS-PM
|
EQPT: CONTBUS-A-18
|
OCH: AS-MT
|
TRUNK: ODUK-4-AIS-PM
|
EQPT: CONTBUS-B-18
|
OCH: LOS-O
|
ODUK-AIS-PM
|
EQPT: CONTBUS-IO-A
|
OCH: LOS-P (OCH)
|
TRUNK: ODUK-BDI-PM
|
EQPT: CONTBUS-IO-B
|
OCH: OPWR-HDEG
|
TRUNK: ODUK-LCK-PM
|
EQPT: CTNEQPT-MISMATCH
|
OCH: OPWR-HFAIL
|
TRUNK: ODUK-OCI-PM
|
EQPT: CTNEQPT-PBPROT
|
OCH: OPWR-LDEG
|
TRUNK: ODUK-SD-PM
|
EQPT: CTNEQPT-PBWORK
|
OCH: OPWR-LFAIL
|
TRUNK: ODUK-SF-PM
|
EQPT: EQPT
|
OCH: PARAM-MISM
|
TRUNK: ODUK-TIM-PM
|
EQPT: ERROR-CONFIG
|
OCH: PORT-ADD-PWR-DEG-HI
|
TRUNK: OTUK-AIS
|
EQPT: EXCCOL
|
OCH: PORT-ADD-PWR-DEG-LOW
|
TRUNK: OTUK-BDI
|
EQPT: FAILTOSW
|
OCH: PORT-ADD-PWR-FAIL-HI
|
TRUNK: OTUK-IAE
|
EQPT: FORCED-REQ
|
OCH: PORT-ADD-PWR-FAIL-LOW
|
TRUNK: OTUK-LOF
|
EQPT: HITEMP
|
OCH: UNREACHABLE-TARGET-POWER
|
TRUNK: OTUK-SD
|
EQPT: IMPROPRMVL
|
OCH: VOA-HDEG
|
TRUNK: OTUK-SF
|
EQPT: INHSWPR
|
OCH: VOA-HFAIL
|
TRUNK: OTUK-TIM
|
EQPT: INHSWWKG
|
OCH: VOA-LDEG
|
TRUNK: OUT-OF-SYNC
|
EQPT: IOSCFGCOPY
|
OCH: VOA-LFAIL
|
TRUNK: PTIM
|
EQPT: LOCKOUT-REQ
|
OCHNC-CONN: OCHNC-INC
|
TRUNK: RFI
|
EQPT: MAN-REQ
|
OCN: AIS-L
|
TRUNK: SD (TRUNK)
|
EQPT: MANRESET
|
OCN: ALS
|
TRUNK: SF (TRUNK)
|
EQPT: MEA (EQPT)
|
OCN: APS-INV-PRIM
|
TRUNK: SIGLOSS
|
EQPT: MEM-GONE
|
OCN: APS-PRIM-FAC
|
TRUNK: SQUELCHED
|
EQPT: MEM-LOW
|
OCN: APS-PRIM-SEC-MISM
|
TRUNK: SSM-DUS
|
EQPT: NO-CONFIG
|
OCN: APSB
|
TRUNK: SSM-FAIL
|
EQPT: PEER-NORESPONSE
|
OCN: APSCDFLTK
|
TRUNK: SSM-LNC
|
EQPT: PROTNA
|
OCN: APSC-IMP
|
TRUNK: SSM-OFF
|
EQPT: PWR-FAIL-A
|
OCN: APSCINCON
|
TRUNK: SSM-PRC
|
EQPT: PWR-FAIL-B
|
OCN: APSCM
|
TRUNK: SSM-PRS
|
EQPT: PWR-FAIL-RET-A
|
OCN: APSCNMIS
|
TRUNK: SSM-RES
|
EQPT: PWR-FAIL-RET-B
|
OCN: APSIMP
|
TRUNK: SSM-SDN-TN
|
EQPT: RUNCFG-SAVENEED
|
OCN: APSMM
|
TRUNK: SSM-SETS
|
EQPT: SFTWDOWN
|
OCN: AS-CMD
|
TRUNK: SSM-SMC
|
EQPT: SWMTXMOD
|
OCN: AS-MT
|
TRUNK: SSM-ST2
|
EQPT: WKSWPR
|
OCN: AUTOLSROFF
|
TRUNK: SSM-ST3
|
EQPT: WTR
|
OCN: BLSROSYNC
|
TRUNK: SSM-ST3E
|
ESCON: ALS
|
OCN: E-W-MISMATCH
|
TRUNK: SSM-ST4
|
ESCON: AS-CMD
|
OCN: EOC
|
TRUNK: SSM-STU
|
ESCON: AS-MT
|
OCN: EOC-L
|
TRUNK: SSM-TNC
|
ESCON: FAILTOSW
|
OCN: EXERCISE-RING-FAIL
|
TRUNK: SYNC-FREQ
|
ESCON: FORCED-REQ-SPAN
|
OCN: EXERCISE-SPAN-FAIL
|
TRUNK: SYNCLOSS
|
ESCON: HI-LASERBIAS
|
OCN: EXTRA-TRAF-PREEMPT
|
TRUNK: TIM
|
ESCON: HI-RXPOWER
|
OCN: FAILTOSW
|
TRUNK: TIM-MON
|
ESCON: HI-TXPOWER
|
OCN: FAILTOSWR
|
TRUNK: UNC-WORD
|
ESCON: LO-RXPOWER
|
OCN: FAILTOSWS
|
TRUNK: UT-COMM-FAIL
|
ESCON: LO-TXPOWER
|
OCN: FE-FRCDWKSWBK-SPAN
|
TRUNK: UT-FAIL
|
ESCON: LOCKOUT-REQ
|
OCN: FE-FRCDWKSWPR-RING
|
TRUNK: WKSWPR
|
ESCON: LOS (ESCON)
|
OCN: FE-FRCDWKSWPR-SPAN
|
TRUNK: WTR
|
ESCON: LPBKFACILITY (ESCON)
|
OCN: FE-LOCKOUTOFPR-SPAN
|
TRUNK: WVL-MISMATCH
|
ESCON: LPBKTERMINAL (ESCON)
|
OCN: FE-MANWKSWBK-SPAN
|
VCG: LOA
|
ESCON: MANUAL-REQ-SPAN
|
OCN: FE-MANWKSWPR-RING
|
VCG: VCG-DEG
|
ESCON: SQUELCHED
|
OCN: FE-MANWKSWPR-SPAN
|
VCG: VCG-DOWN
|
ESCON: WKSWPR
|
OCN: FEPRLF
|
VT-MON: AIS-V
|
ESCON: WTR
|
OCN: FORCED-REQ-RING
|
VT-MON: AUTOSW-AIS
|
EXT-SREF: FRCDSWTOPRI
|
OCN: FORCED-REQ-SPAN
|
VT-MON: AUTOSW-LOP (VT-MON)
|
EXT-SREF: FRCDSWTOSEC
|
OCN: FULLPASSTHR-BI
|
VT-MON: AUTOSW-UNEQ (VT-MON)
|
EXT-SREF: FRCDSWTOTHIRD
|
OCN: HELLO
|
VT-MON: FAILTOSW-PATH
|
EXT-SREF: MANSWTOPRI
|
OCN: HI-LASERBIAS
|
VT-MON: FORCED-REQ
|
EXT-SREF: MANSWTOSEC
|
OCN: HI-LASERTEMP
|
VT-MON: LOCKOUT-REQ
|
EXT-SREF: MANSWTOTHIRD
|
OCN: HI-RXPOWER
|
VT-MON: LOP-V
|
EXT-SREF: SWTOPRI
|
OCN: HI-TXPOWER
|
VT-MON: MAN-REQ
|
EXT-SREF: SWTOSEC
|
OCN: KB-PASSTHR
|
VT-MON: SD-V
|
EXT-SREF: SWTOTHIRD
|
OCN: KBYTE-APS-CHANNEL-FAILURE
|
VT-MON: SF-V
|
EXT-SREF: SYNCPRI
|
OCN: LASEREOL
|
VT-MON: UNEQ-V
|
EXT-SREF: SYNCSEC
|
OCN: LKOUTPR-S
|
VT-MON: WKSWPR
|
EXT-SREF: SYNCTHIRD
|
OCN: LO-LASERTEMP
|
VT-MON: WTR
|
FAN: EQPT-MISS
|
OCN: LO-RXPOWER
|
VT-TERM: AIS-V
|
FAN: FAN
|
OCN: LO-TXPOWER
|
VT-TERM: AS-MT-OOG
|
FAN: MEA (FAN)
|
OCN: LOCKOUT-REQ
|
VT-TERM: LCAS-CRC
|
FAN: MFGMEM
|
OCN: LOF (OCN)
|
VT-TERM: LCAS-RX-FAIL
|
FC: ALS
|
OCN: LOS (OCN)
|
VT-TERM: LCAS-TX-ADD
|
FC: AS-CMD
|
OCN: LPBKFACILITY (OCN)
|
VT-TERM: LCAS-TX-DNU
|
FC: AS-MT
|
OCN: LPBKTERMINAL (OCN)
|
VT-TERM: LOM
|
FC: CARLOSS (FC)
|
OCN: MANUAL-REQ-RING
|
VT-TERM: LOP-V
|
FC: FAILTOSW
|
OCN: MANUAL-REQ-SPAN
|
VT-TERM: OOU-TPT
|
FC: FC-NO-CREDITS
|
OCN: PRC-DUPID
|
VT-TERM: PLM-V
|
FC: FORCED-REQ-SPAN
|
OCN: RFI-L
|
VT-TERM: RFI-V
|
FC: GE-OOSYNC
|
OCN: RING-ID-MIS
|
VT-TERM: SD-P
|
FC: HI-LASERBIAS
|
OCN: RING-MISMATCH
|
VT-TERM: SF-P
|
FC: HI-RXPOWER
|
OCN: RING-SW-EAST
|
VT-TERM: SQM
|
FC: HI-TXPOWER
|
OCN: RING-SW-WEST
|
VT-TERM: TIM-V
|
FC: LO-RXPOWER
|
OCN: SD-L
|
VT-TERM: UNEQ-V
|
FC: LO-TXPOWER
|
—
|
—
|
2.5 DS3-12 E Line Alarms
Unlike the standard DS-3 card, which uses the unframed format exclusively, the DS3-12E card provides three choices: unframed, M13, or C Bit. The choice of framing format determines the line alarms that the DS3-12E card reports. The following table lists the line alarms reported under each format.
The choice of framing format does not affect the reporting of STS alarms. Regardless of format, the DS3-12E card reports the same STS alarms and conditions, listed in Table 2-9, as the standard DS-3 card reports.
Table 2-9 DS3-12E Line Alarms
Alarm
|
UNFRAMED
|
M13
|
CBIT
|
LOS DS1 or DS3)
|
Yes
|
Yes
|
Yes
|
AIS
|
Yes
|
Yes
|
Yes
|
LOF (DS1 or DS3)
|
No
|
Yes
|
Yes
|
FE-IDLW
|
No
|
Yes
|
Yes
|
RAI
|
No
|
Yes
|
Yes
|
Terminal Lpbk (LPBKTERMINAL for DS1 or DS3)
|
Yes
|
Yes
|
Yes
|
Facility Lpbk (LPBKFACILITY for DS1 or DS3)
|
Yes
|
Yes
|
Yes
|
LPBKDS1FEAC or LPBKDS3FEAC
|
No
|
No
|
Yes
|
FE Common Equipment Failure-NSA (FE-DS1-NSA or FE-DS3-NSA)
|
No
|
No
|
Yes
|
FE Equipment Failure-SA (FE-DS3-SA)
|
No
|
No
|
Yes
|
FE-LOS
|
No
|
No
|
Yes
|
FE-LOF
|
No
|
No
|
Yes
|
FE-AIS
|
No
|
No
|
Yes
|
FE-IDLE
|
No
|
No
|
Yes
|
FE Equipment Failure-NSA (FE-EQPT-NSA)
|
No
|
No
|
Yes
|
2.6 Trouble Notifications
The ONS 15454 system reports trouble by utilizing standard alarm and condition characteristics, standard severities following the rules in Telcordia GR-253, and graphical user interface (GUI) state indicators.These notifications are described in the following paragraphs.
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and status or descriptive notifications (if configured to do so) as conditions in the CTC Alarms window. Alarms typically signify a problem that the user needs to remedy, such as a loss of signal. Conditions do not necessarily require troubleshooting.
2.6.1 Alarm Characteristics
The ONS 15454 uses standard alarm entities to identify what is causing trouble. All alarms stem from hardware, software, environment, or operator-originated problems whether or not they affect service. Current alarms for the network, CTC session, node, or card are listed in the Alarms tab. (In addition, cleared alarms are also found in the History tab.)
2.6.2 Condition Characteristics
Conditions include any problem detected on an ONS 15454 shelf. They can include standing or transient notifications. A snapshot of all current raised, standing conditions on the network, node, or card can be retrieved in the CTC Conditions window or using TL1's set of RTRV-COND commands. (In addition, some but not all cleared conditions are also found in the History tab.)
For a comprehensive list of all conditions, refer to the Cisco ONS SONET TL1 Command Guide.
2.6.3 Severities
The ONS 15454 uses Telcordia-devised standard severities for alarms and conditions: Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA) and Not Reported (NR). These are described below:
•A Critical alarm generally indicates severe, service-affecting trouble that needs immediate correction. Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.
•A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For example, loss of traffic on more than five DS-1 circuits is Critical, but loss of traffic on one to five DS-1 circuits is Major (MJ).
•Minor (MN) alarms generally are those that do not affect service. For example, the APS byte failure (APSB) alarm indicates that line terminating equipment detects a byte failure on the signal that could prevent traffic from properly executing a traffic switch.
•Not Alarmed (NA) conditions are information indicators, such as for free-run synchronization state (FRNGSYNC) or a forced-switch to primary (FRCSWTOPRI) timing event. They might or might not require troubleshooting, as indicated in the entries.
•Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be expected in the presence of primary alarms.
All alarm, condition, and unreported event severities listed in this manual are default profile settings. However in situations when traffic is not lost—such as when the alarm occurs on protected ports or circuits—alarms having Critical (CR) or Major (MJ) default severities can be demoted to lower severities such as Minor (MN) or Non-Service Affecting (NSA) as defined in Telcordia GR-474.
Severities can also be customized for an entire network or for single nodes, from the network level down to the port level by changing or downloading customized alarm profiles. These custom severities are subject to the standard severity-demoting rules given in Telcordia GR-474. Procedures for customizing alarm severities are located in the Cisco ONS 15454 Procedure Guide Chapter 7, "Manage Alarms."
2.6.4 Service Effect
Service-Affecting (SA) alarms—those that interrupt service—might be Critical (CR), Major (MJ), or Minor (MN) severity alarms. In some cases the severity of an alarm might not correspond to its service effect. For example, the AUTOSW-LOP alarm for the VTMON object is minor but service-affecting because it indicates a traffic switch has occurred directing traffic away from a loss of circuit path. Non-Service Affecting (NSA) alarms always have a Minor (MN) default severity.
2.6.5 States
The Alarms or History tab state (ST) column indicate the disposition of the alarm or condition as follows:
•A raised (R) event is one that is active.
•A cleared (C) event is one that is no longer active.
•A transient (T) event is one that is automatically raised and cleared in CTC during system changes such as user login, logout, loss of connection to node view, etc. Transient events do not require user action.
Note Transient events are not defined in this documentation release.
2.7 Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS 15454. Personnel should not perform any procedures in this chapter unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances users should pay close attention to the following caution.
Caution Hazardous voltage or energy could be present on the backplane when the system is operating. Use caution when removing or installing cards.
Some troubleshooting procedures require installation or removal of OC-192 cards; in these instances users should pay close attention to the following warning.
Warning On the OC-192 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). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Warning Class 1 laser product. Statement 1008
Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206
Warning The power supply circuitry for the equipment can constitute an energy hazard. Before you install or replace the equipment, remove all jewelry (including rings, necklaces, and watches). Metal objects can come into contact with exposed power supply wiring or circuitry inside the DSLAM equipment. This could cause the metal objects to heat up and cause serious burns or weld the metal object to the equipment. Statement 207
2.8 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 are done checking for alarms, you can click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, refer to the Cisco ONS 15454 Procedure Guide Chapter 7, "Manage Alarms."
Note When checking alarms, ensure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, refer to the Cisco ONS 15454 Procedure Guide Chapter 7, "Manage Alarms."
2.8.1 AIS
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: BITS, DS1, DS3, FUDC, MSUDC, TRUNK
The Alarm Indication Signal (AIS) condition indicates that this node is detecting AIS in the incoming signal SONET overhead.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Note ONS 15454 DS-3 and EC-1 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided.
Clear the AIS Condition
Step 1 Determine whether there are alarms on the upstream nodes and equipment, especially the "LOS (OCN)" alarm on page 2-144, or out-of-service (OOS,MT or OOS,DSBLD) ports.
Step 2 Clear the upstream alarms using the applicable procedures in this chapter.
Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.2 AIS-L
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: EC1, EC1-12, OCN
The AIS Line condition indicates that this node is detecting line-level AIS in the incoming signal. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-L Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.3 AIS-P
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
The AIS Path condition means that this node is detecting AIS in the incoming path. This alarm is secondary to another alarm occurring simultaneously in an upstream node.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-P Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.4 AIS-V
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: VT-MON, VT-TERM
The AIS VT condition means that this node is detecting AIS in the incoming VT-level path.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
See the "AIS-V on DS3XM-6 or DS3XM-12 Unused VT Circuits" section for more information.
Clear the AIS-V Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.5 ALS
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: 2R, AOTS, ESCON, FC, GE, ISC, OCN, TRUNK
The Automatic Laser Shutdown (ALS) condition occurs when a DWDM Optical Preamplifier (OPT-PRE) or Optical Booster (OPT-BST) Amplifier card 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 and does not require troubleshooting.
2.8.6 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 typically accompanies the "APC-DISABLED" alarm on page 2-25.
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 Procedure Guide.
Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1 800 553-2447).
2.8.7 APC-CORRECTION-SKIPPED
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: AOTS, OCH, OMS, OTS
The Automatic Power Control (APC) Correction Skipped condition occurs when the actual power level of a DWDM channel exceeds the threshold setting by 3 dBm or more. The APC compares actual power levels with power level thresholds every 10 minutes or after any channel allocation is performed. If the actual power level is above or below the setting within 3 dBm, APC corrects the level. If the actual power level exceeds the threshold by +3 dBm or -3 dBm, APC cannot correct the level and the APC-CORRECTION-SKIPPED condition is raised.
There is no operator action to resolve this condition. It stays raised until the power level problem is resolved and APC takes a normal reading. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
Note APC-CORRECTION-SKIPPED is an informational condition and does not require troubleshooting.
2.8.8 APC-DISABLED
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The APC Disabled alarm occurs when the information related to the number of DWDM channels is not reliable. The alarm can occur when the any related alarms also occur: the "AMPLI-INIT" condition on page 2-24, the "EQPT" alarm on page 2-74, the "IMPROPRMVL" alarm on page 2-118, or the "MEA (EQPT)" alarm on page 2-172. If the alarm occurs with the creation of the first circuit, delete and recreate the circuit. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
Clear the APC-DISABLED Condition
Step 1 Complete the appropriate procedure to clear the main alarm:
•Clear the EQPT Alarm
•Clear the IMPROPRMVL Alarm
•Clear the MEA (EQPT) Alarm
Step 2 If the alarm does not clear, complete the "Delete a Circuit" procedure and then recreate it using procedures in the Cisco ONS 15454 DWDM Installation and Operations Guide.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.9 APC-END
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The APC Terminated on Manual Request condition is raised when the APC application terminates after being manually launched from CTC or TL1. It is an informational condition. For more information about APC, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
Note APC-END is an informational condition and does not require troubleshooting.
2.8.10 APC-OUT-OF-RANGE
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: AOTS, OCH, OMS, OTS
The APC Out of Range condition is raised on DWDM amplifier cards (OPT-PRE and OPT-BST); optical service channel cards (OSCM and OSC-CSM); multiplexer cards (32MUX-O); demultiplexer cards (32DMX, 32DMX-O), and optical add/drop multiplexer cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, and AD-4B-xx.x) when the requested gain or attenuation setpoint cannot be set because it exceeds the port parameter range. For example, this condition is raised when APC attempts to set the OPT-BST gain higher than 20 dBm (the maximum set-point) or set the attenuation on the express variable optical attenuation (VOA) lower than 0dBm (the minimum set-point).
Clear the APC-OUT-OF-RANGE Condition
Step 1 Provision the correct setpoint. For instructions, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide. The condition clears when the APC setting is corrected and after APC does not detect any errors in its next cycle.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.11 APSB
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure or an invalid switching code in the incoming APS signal. Some older non-Cisco SONET nodes send invalid APS codes if they are configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15454. These invalid codes cause an APSB on an ONS 15454.
Step 1 Use an optical test set to examine the incoming SONET overhead to confirm inconsistent or invalid K bytes. For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15454.
Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you might need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Traffic Card" procedure.
Caution For the ONS 15454, removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the
"Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.12 APSCDFLTK
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The APS Default K Byte Received alarm occurs during bidirectional line switched ring (BLSR) provisioning or when a BLSR is not properly configured, for example, when a four-node BLSR has one node configured as a path protection. When this misconfiguration occurs, a node in a path protection or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "BLSROSYNC" alarm on page 2-45.
Clear the APSCDFLTK Alarm
Step 1 Complete the "Identify a BLSR Ring Name or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 Repeat Step 1 for all nodes in the ring.
Step 3 If two nodes have the same node ID number, complete the "Change a BLSR Node ID Number" procedure to change one node ID number so that each node ID is unique.
Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" alarm on page 2-78.) West port fibers must connect to east port fibers and vice versa. The Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," provides a procedure for fibering BLSRs.
Step 5 If the alarm does not clear and the network is a four-fiber BLSR, ensure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if a working fiber is incorrectly attached to a protect fiber.
Step 6 If the alarm does not clear, complete the "Verify Node Visibility for Other Nodes" procedure.
Step 7 If nodes are not visible, complete the "Verify or Create Node Section DCC Terminations" procedure to ensure that SONET data communications channel (SDCC) terminations exist on each node.
Step 8 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.13 APSC-IMP
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An Improper SONET APS Code alarm indicates three consecutive, identical frames containing:
•Unused code in bits 6 through 8 of byte K2.
•Codes that are irrelevant to the specific protection switching operation being requested.
•Requests that are irrelevant to the ring state of the ring (such as a span protection switch request in a two-fiber ring NE).
•ET code in K2 bits 6 through 8 received on the incoming span, but not sourced from the outgoing span.
Note This alarm can occur on a VT tunnel when it does not have VT circuits provisioned. It can also occur when the exercise command or a lockout is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal. For specific procedures to use the test set equipment, consult the manufacturer.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.
Step 2 If the K byte is valid, verify that each node has a ring name that matches the other node ring names. Complete the "Identify a BLSR Ring Name or Node ID Number" procedure.
Step 3 Repeat Step 2 for all nodes in the ring.
Step 4 If a node has a ring name that does not match the other nodes, make that node's ring name identical to the other nodes. Complete the "Change a BLSR Ring Name" procedure.
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.14 APSCINCON
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An APS Inconsistent alarm means that an inconsistent APS byte is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the SONET signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.
Clear the APSCINCON Alarm
Step 1 Look for other alarms, especially the "LOS (OCN)" alarm on page 2-144, the "LOF (OCN)" alarm on page 2-134, or the "AIS" condition on page 2-22. Clearing these alarms clears the APSCINCON alarm.
Step 2 If an APSINCON alarm occurs with no other alarms, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.15 APSCM
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
The APS Channel Mismatch alarm occurs when the ONS 15454 expects a working channel but receives a protect channel. In many cases, the working and protect channels are crossed and the protect channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. The APSCM alarm occurs only on the ONS 15454 when bidirectional protection is used on OC-N cards in a 1+1 configuration.
Warning On the ONS 15454 OC-192 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). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Clear the APSCM Alarm
Step 1 Verify that the working-card channel fibers are physically connected directly to the adjoining node working-card channel fibers.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the fibers are correctly connected, verify that the protection-card channel fibers are physically connected directly to the adjoining node protection-card channel fibers.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.16 APSCNMIS
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
The APS Node ID Mismatch alarm occurs when the source node ID contained in the incoming APS channel K2 byte is not present in the ring map. The APSCNMIS alarm could occur and clear when a BLSR is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains, the alarm clears when a K byte with a valid source node ID is received.
Clear the APSCNMIS Alarm
Step 1 Complete the "Identify a BLSR Ring Name or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.
Step 3 Click Close in the Ring Map dialog box.
Step 4 If two nodes have the same node ID number, complete the "Change a BLSR Node ID Number" procedure to change one node ID number so that each node ID is unique.
Note If the node names shown in the network view do not correlate with the node IDs, log into each node and click the Provisioning > BLSR tabs. The BLSR window shows the node ID of the login node.
Note Applying and removing a lockout on a span causes the ONS node to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.
Step 5 If the alarm does not clear, use the "Initiate a Lock Out on a BLSR Protect Span" procedure to lockout the span.
Step 6 Complete the "Clear a BLSR External Switching Command" procedure to clear the lockout.
Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.17 APSIMP
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The APS Invalid Mode condition occurs if a 1+1 protection group is not properly configured at both nodes to send or receive the correct APS byte. A node that is either configured for no protection or is configured for path protection or BLSR protection does not send the right K2 APS byte anticipated by a system configured for 1+1 protection. The 1+1 protect port monitors the incoming K2 APS byte and raises this alarm if it does not receive the byte.
The condition is superseded by an APS, APSCM, or APSMM. It is not superseded by AIS or remote defect indication (RDI) line alarms. It clears when the port receives a valid code for 10 ms.
Clear the APSIMP Condition
Step 1 Check the configuration of the other node in the 1+1 protection group. If the remote node is not configured for 1+1 protection, create the group. For instructions, refer to the Cisco ONS 15454 Procedure Guide Chapter 4, "Turn Up Node."
Step 2 If the other end of the group is properly configured or the alarm does not clear after you have provisioned the group correctly, verify that the working ports and protect ports are cabled correctly.
Step 3 Ensure that both protect ports are configured for SONET.
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.18 APS-INV-PRIM
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The Optimized 1+1 APS Primary Facility condition occurs on OC-N cards in an optimized 1+1 protection system if the incoming primary section header does not indicate whether it is primary or secondary.
Note APS-INV-PRIM is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.
2.8.19 APS-PRIM-FAC
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
The Optimized 1+1 APS Invalid Primary Section condition occurs on OC-N cards in an optimized 1+1 protection system if there is an APS status switch between the primary and secondary facilities to identify which port is primary.
Note APS-INV-PRIM is an informational condition and does not require troubleshooting. If the APS switch is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.
Clear the APS-PRIM-FAC Condition
Step 1 This condition clears when the card receives a valid primary section indication (1 or 2).
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.20 APSMM
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An APS Mode Mismatch failure alarm occurs on OC-N cards when there is a mismatch of the protection switching schemes at the two ends of the span, such as being bidirectional and unidirectional at each end. Each end of a span must be provisioned the same way: bidirectional and bidirectional, or unidirectional and unidirectional. APSMM can also occur if a non-Cisco vendor's equipment is provisioned as 1:N and the ONS 15454 is provisioned as 1+1.
If one end is provisioned for 1+1 protection switching and the other is provisioned for path protection protection switching, an APSMM alarm occurs in the ONS 15454 that is provisioned for 1+1 protection switching.
Clear the APSMM Alarm
Step 1 For the reporting ONS 15454, display node view and verify the protection scheme provisioning:
a. Click the Provisioning > Protection tabs.
b. Click the 1+1 protection group configured for the OC-N cards.
The chosen protection group is the protection group optically connected (with data communications channel, or DCC, connectivity) to the remote node.
c. Click Edit.
d. Record whether the Bidirectional Switching check box is checked.
Step 2 Click OK in the Edit Protection Group dialog box.
Step 3 Log into the remote-node node and verify that the OC-N 1+1 protection group is provisioned.
Step 4 Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in Step 1. If not, change it to match.
Step 5 Click Apply.
Step 6 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.21 APS-PRIM-SEC-MISM
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The Optimized 1+1 APS Primary Section Mismatch condition occurs on OC-N cards in an optimized 1+1 protection system if there is a mismatch between the primary section of the local node facility and the primary section of the remote-node facility.
Clear the APS-PRIM-SEC-MISM Alarm
Step 1 Ensure that the local node and remote-node ports are correctly provisioned with the same way. For more information about optimized 1+1 configurations, refer to the Cisco ONS 15454 Procedure Guide Chapter 4, "Turn Up Node."
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.22 AS-CMD
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: 2R, AOTS, BPLANE, CE100T, DS1, DS3, E100T, E1000F, EC1, EC1-12, EQPT, ESCON, FC, FCMR, G1000, GE, GFP-FAC, ISC, ML100T, ML1000, NE, OCH, OCN, OMS, OTS, PPM, PWR, TRUNK
The Alarms Suppressed by User Command condition applies to the network element (NE object), backplane, a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects. For example, suppressing alarms on a card also suppresses alarms on its ports.
Clear the AS-CMD Condition
Step 1 For all nodes, in node view, click the Conditions tab.
Step 2 Click Retrieve. If you have already retrieved conditions, look under the Object column and Eqpt Type column and note what entity the condition is reported against, such as a port, slot, or shelf.
•If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with Step 3.
•If the condition is reported against the backplane, go to Step 7.
•If the condition is reported against the NE object, go to Step 8.
Step 3 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 Profiles > Alarm Behavior tabs.
•If the Suppress Alarms column check box is checked for a port row, deselect it and click Apply.
•If the Suppress Alarms column check box is not checked for a port row, click View > Go to Previous View.
Step 4 If the AS-CMD condition is reported for a card and not an individual port, in node view click the Provisioning > Alarm Profiles > Alarm Behavior tabs.
Step 5 Locate the row number for the reported card slot.
Step 6 Click the Suppress Alarms column check box to deselect the option for the card row.
Step 7 If the condition is reported for the backplane, the alarms are suppressed for cards such as the ONS 15454 AIP that are not in the optical or electrical slots. To clear the alarm:
a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.
b. In the backplane row, uncheck 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 Profiles > Alarm Behavior tabs if you have not already done so.
b. Click the Suppress Alarms check box located at the bottom of the window to deselect the option.
c. Click Apply.
Step 9 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.23 AS-MT
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: 2R, AOTS, BPLANE, CE100T, DS1, DS3, E100T, E1000F, EC1, EC1-12, EQPT, ESCON, FC, FCMR, GE, GFP-FAC, G1000, ISC, ML100T, ML1000, NE, OCH, OCN, OMS, OTS, PPM, PWR, TRUNK
The Alarms Suppressed for Maintenance Command condition applies to OC-N and electrical cards and occurs when a port is placed in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state for loopback testing operations.
Clear the AS-MT Condition
Step 1 Complete the "Clear an OC-N Card Facility or Terminal Loopback Circuit" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.24 AS-MT-OOG
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: STSTRM, VT-TERM
The Alarms Suppressed on an Out-Of-Group VCAT Member condition is raised on an STS or VT member of a VCAT group whenever the member is in the IDLE (AS-MT-OOG) admin state. This condition can be raised when a member is initially added to a group. In IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.
Clear the AS-MT-OOG Condition
Step 1 The AS-MT-OOG condition clears when an STS or VT member transitions to a different state from IDLE (AS-MT-OOG) or when it is removed completely from the VCAT group. It does not require troubleshooting unless it does not clear.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.25 AUD-LOG-LOSS
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The Audit Trail Log Loss condition occurs when the log is 100 percent full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries. The log must be off-loaded using the following procedure to make room for more entries.
Clear the AUD-LOG-LOSS Condition
Step 1 In node view, click the Maintenance > Audit tabs.
Step 2 Click Retrieve.
Step 3 Click Archive.
Step 4 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.
Step 5 Enter a name in the File Name field.
You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.
Step 6 Click Save.
The 640 entries are saved in this file. New entries continue with the next number in the sequence, rather than starting over.
Step 7 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.26 AUD-LOG-LOW
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The Audit Trail Log Low condition occurs when the audit trail log is 80 percent full.
Note AUD-LOG-LOW is an informational condition and does not require troubleshooting.
2.8.27 AU-LOF
The Administrative Unit Loss of Multiframe alarm is not supported in this platform release. It is reserved for future development.
2.8.28 AUTOLSROFF
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: OCN
The Auto Laser Shutdown alarm occurs when the OC-192 card temperature exceeds 194 degrees F (90 degrees C). The internal equipment automatically shuts down the OC-192 laser when the card temperature rises to prevent the card from self-destructing.
Warning On the ONS 15454 OC-192 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). Statement 293
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Clear the AUTOLSROFF Alarm
Step 1 View the temperature displayed on the ONS 15454 LCD front panel (Figure 2-1).
Figure 2-1 Shelf LCD Panel
Step 2 If the temperature of the shelf exceeds 194 degrees F (90 degrees C), the alarm should clear if you solve the ONS 15454 temperature problem. Complete the "Clear the HITEMP Alarm" procedure.
Step 3 If the temperature of the shelf is under 194 degrees F (90 degrees C), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Traffic Card" procedure for the OC-192 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 4 If card replacement does not clear the alarm, call Cisco TAC (1 800 553-2447) to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.
2.8.29 AUTORESET
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Automatic System Reset alarm occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.
AUTORESET typically clears after a card reboots (up to ten minutes). If the alarm does not clear, complete the following procedure.
Clear the AUTORESET Alarm
Step 1 Determine whether there are additional alarms that could have triggered an automatic reset. If there are, troubleshoot these alarms using the applicable section of this chapter.
Step 2 If the card automatically resets more than once a month with no apparent cause, complete the "Physically Replace a Traffic Card" procedure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Caution For the ONS 15454, removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the
"Protection Switching, Lock Initiation, and Clearing" section for commonly used traffic-switching procedures.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.30 AUTOSW-AIS
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, VT-MON
The Automatic Path Protection Switch Caused by AIS condition indicates that automatic path protection switching occurred because of an AIS condition. The path protection is configured for revertive switching and reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.
Generally, any AIS is a special SONET signal that communicates to the receiving node when the transmit node does not send a valid signal. AIS is not considered an error. It is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.31 AUTOSW-LOP (STSMON)
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by LOP condition for the STS monitor (STSMON) indicates that automatic path protection switching occurred because of the "LOP-P" alarm on page 2-136. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-LOP (STSMON) Condition
Step 1 Complete the "Clear the LOP-P Alarm" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.32 AUTOSW-LOP (VT-MON)
•Default Severity: Not Alarmed (NA), Service-Affecting (SA)
•Logical Object: VT-MON
The AUTOSW-LOP alarm for the virtual tributary monitor (VT-MON) indicates that automatic path protection switching occurred because of the "LOP-V" alarm on page 2-136. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-LOP (VT-MON) Condition
Step 1 Complete the "Clear the LOP-V Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.33 AUTOSW-PDI
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a "PDI-P" alarm on page 2-192. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-PDI Condition
Step 1 Complete the "Clear the PDI-P Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.34 AUTOSW-SDBER
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade (SD) caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SD is resolved.
Clear the AUTOSW-SDBER Condition
Step 1 Complete the "Clear the SD (DS1, DS3) Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.35 AUTOSW-SFBER
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal failure (SF) caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SF is resolved.
Clear the AUTOSW-SFBER Condition
Step 1 Complete the "Clear the SF (DS1, DS3) Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.36 AUTOSW-UNEQ (STSMON)
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Unequipped condition indicates that an UNEQ alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-UNEQ (STSMON) Condition
Step 1 Complete the "Clear the UNEQ-P Alarm" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.37 AUTOSW-UNEQ (VT-MON)
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: VT-MON
AUTOSW-UNEQ (VT-MON) indicates that the "UNEQ-V" alarm on page 2-241 alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-UNEQ (VT-MON) Condition
Step 1 Complete the "Clear the UNEQ-V Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.38 AWG-DEG
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OTS
The Arrayed Waveguide Gratings (AWG) Degrade alarm occurs when a DWDM card heater-control circuit degrades. The heat variance can cause slight wavelength drift. The card does not need to be replaced immediately, but it should be at the next opportunity.
Clear the AWG-DEG Alarm
Step 1 For the alarmed DWDM card, complete the "Physically Replace a Traffic Card" procedure at the next opportunity.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.39 AWG-FAIL
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: OTS
The AWG Failure alarm occurs when a DWDM card heater-control circuit completely fails. The circuit failure disables wavelength transmission. The card must be replaced to restore traffic.
Clear the AWG-FAIL Alarm
Step 1 For the alarmed DWDM card, complete the "Physically Replace a Traffic Card" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a service-affecting problem.
2.8.40 AWG-OVERTEMP
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: OTS
The AWG Over Temperature alarm is raised if a card having an AWG-FAIL alarm is not replaced and its heater-control circuit temperature exceeds 212 degrees F (100 degrees C). The card goes into protect mode and the heater is disabled.
Clear the AWG-OVERTEMP Alarm
Step 1 Complete the "Clear the AWG-FAIL Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) to report a service-affecting problem.
2.8.41 AWG-WARM-UP
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OTS
The AWG Warm-Up condition occurs when a DWDM card heater-control circuit is attaining its operating temperature during startup. The condition lasts approximately 10 minutes but can vary somewhat from this period due to environmental temperature.
Note AWG-WARM-UP is an informational condition and does not require troubleshooting.
2.8.42 BAT-FAIL
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: PWR
The Battery Fail alarm occurs when one of the two power supplies (A or B) is not detected. This could be because the supply is removed or is not operational. The alarm does not distinguish between the individual power supplies, so on-site information about the conditions is necessary for troubleshooting.
Clear the BAT-FAIL Alarm
Step 1 At the site, determine which battery is not present or operational.
Step 2 Remove the power cable from the faulty supply. For instructions, refer to the Cisco ONS 15454 Procedure Guide Chapter 1, "Install the Shelf and Backplane Cable," and reverse the power cable installation procedure.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.43 BKUPMEMP
•Default Severity: Critical (CR), Service Affecting (SA)
•Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P card flash memory. The alarm occurs when the TCC2/TCC2P is in use and has one of four problems:
•The flash manager fails to format a flash partition.
•The flash manager fails to write a file to a flash partition.
•There is a problem at the driver level.
•The code volume fails cyclic redundancy checking (CRC). CRC is a method to verify for errors in data transmitted to the TCC2/TCC2P.
The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-74. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Caution Software updating on a standby TCC2/TCC2P can take up to 30 minutes.
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/TCCP card has the alarm.
Step 3 If both TCC2/TCCP cards are powered and enabled, reset the TCC2/TCCP card against which the alarm is raised. If the card is the active TCC2/TCCP card, complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure. If the card is the standby TCC2/TCCP, use the substeps below.
a. Right-click the standby TCC2/TCCP card in CTC.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the Are You Sure dialog box. The card resets, the FAIL LED blinks on the physical card.
d. Wait ten minutes to verify that the card you reset completely reboots.
Step 4 If the TCC2/TCC2P card you reset does not reboot successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
2.8.44 BLSROSYNC
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
The BLSR Out Of Synchronization alarm occurs during BLSR setup when you attempt to add or delete a circuit, and a working ring node loses its DCC connection because all transmit and receive fiber has been removed. CTC cannot generate the ring table and causes the BLSROSYNC alarm.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Note This alarm can also be expected when upgrading to Release 5.0 when the ring identifier is updated.
Clear the BLSROSYNC Alarm
Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," for cabling information to reestablish the DCC.
Note To verify cable continuity, follow site practices.
When the DCC is established between the node and the rest of the BLSR, it becomes visible to the BLSR and should be able to function on the circuits.
Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" section.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.45 BPV
•Default Severity: Minor (MN), Service-Affecting (SA)
•Logical Object: BITS
The 64K Clock Bipolar Density Violation alarm is raised on the TCC2P card if there is a frequency variation in the 8K BITS clock. The TCC2P card contains an 8K clock and a 64K clock. Each has some bipolar variation, which is normal. This alarm is raised on the 8K clock if that variation discontinues. The BPV alarm is demoted by an LOF or LOS against the BITS clock.
Note This alarm is not raised on the TCC2 card.
Clear the BPV Alarm
Step 1 Reestablishing a normal BITS input signal clears the alarm. Clear any alarms on the incoming signal or against the BITS timing sources.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.46 CARLOSS (CE100T)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Objects: CE100T
The Carrier Loss alarm is raised on CE-100T-8 cards in Mapper mode when there is a circuit failure due to link integrity. It does not get raised when a user simply puts the port In-Service. It has to be IS with circuit or loopback.
Clear the CARLOSS (CE100T) Alarm
Step 1 Complete the "Clear the CARLOSS (G1000) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.47 CARLOSS (E100T, E1000F)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Objects: E100T, E1000F
A Carrier Loss alarm on the LAN E-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-144. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of the CARLOSS alarm are a disconnected cable, an Ethernet Gigabit Interface Converter (GBIC) fiber connected to an optical card rather than an Ethernet device, or an improperly installed Ethernet card. Ethernet card ports must be enabled for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
The CARLOSS alarm also occurs after a node database is restored. After restoration, the alarm clears in approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP).
Clear the CARLOSS (E100T, E1000F) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 3 If no misconnection to an OC-N card exists, 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 fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 6 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the Ethernet card.
Step 7 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the Ethernet card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 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.
An Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454s, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 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.
Step 9 If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm may be a result of mismatched STS circuit sizes in the set up of the manual cross-connect. If the Ethernet circuit is not part of a manual cross-connect, the following steps do not apply.
a. Right-click anywhere in the row of the CARLOSS alarm.
b. Click Select Affected Circuits in the shortcut menu that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. From the examination of the layout of your network, determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect by completing the following substeps:
•Log into the ONS 15454 at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The Ethernet manual cross-connect circuit connects the Ethernet card to an OC-N card at the same node.
e. Use the information you recorded to determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size.
If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. For more information, refer to the Cisco ONS 15454 Procedure Guide Chapter 6, "Create Circuits and Tunnels."
Step 10 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.48 CARLOSS (EQPT)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: EQPT
A Carrier Loss on the LAN Equipment alarm generally occurs on OC-N cards when the ONS 15454 and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the TCC2/TCC2P, or for the ONS 15454, the LAN backplane pin connection. The CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the node.
On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G or MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 monitoring is turned off.
A TXP_MR_2.5G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data type.
Warning Invisible laser radiation could be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm could pose an eye hazard. Statement 1056
Warning Use of controls, adjustments, or performing procedures other than those specified may result in hazardous radiation exposure. Statement 1057
Clear the CARLOSS (EQPT) Alarm
Step 1 If the reporting card is an MXP or TXP card in an ONS 15454 node, verify the data rate configured on the pluggable port module (PPM):
a. Double-click the reporting MXP or TXP card.
b. Click the Provisioning > Pluggable Port Modules tabs.
c. View the Pluggable Port Modules area port listing in the Actual Equipment column and compare this with the contents of the Selected PPM area Rate column for the MXP or TXP multirate port.
d. If the rate does not match the actual equipment, you must delete and recreate the selected PPM. Select the PPM, click Delete, then click Create and choose the correct rate for the port rate.
Step 2 If the reporting card is an OC-N card, verify connectivity by pinging the ONS 15454 that is reporting the alarm:
a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Accessories > Command Prompt.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
c. For both the Sun and Microsoft operating systems, at the prompt type:
ping ONS-15454-IP-address
For example:
If the workstation has connectivity to the ONS 15454, it shows a "reply from IP-Address" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.
Step 3 If the ping is successful, an active TCP/IP connection exists. Restart CTC:
a. Exit from CTC.
b. Reopen the browser.
c. Log into CTC.
Step 4 Using optical test equipment, verify that proper receive levels are achieved. (For instructions to use optical test equipment, refer to the manufacturer documentation.)
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 6 If the fiber cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 7 If you are unable to establish connectivity, replace the fiber cable with a new known-good cable. To do this, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 8 If you are unable to establish connectivity, perform standard network or LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node and CTC.
Note To verify cable continuity, follow site practices.
Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.49 CARLOSS (FC)
The Carrier Loss alarm for Fibre Channel is not used in this platform in this release. It is reserved for future development.
2.8.50 CARLOSS (G1000)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: G1000
A Carrier Loss alarm on the LAN G-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-144. The Ethernet card has lost its link and is not receiving a valid signal.
CARLOSS on the G1000-4 card is 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 remote-node G1000-4 card), it causes the reporting card to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the remote-node 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, other alarms such as the "TPTFAIL (G1000)" alarm on page 2-236 or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G1000s) alarm.
Refer to the <I_Ital>Cisco ONS 15454 Reference Manual for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-237 for more information about alarms that occur when a point-to-point circuit exists between two cards.
Ethernet card ports must be enabled for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
Clear the CARLOSS (G1000) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
Step 3 If no misconnection to the OC-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.
Step 4 Verify that optical receive levels are within the normal range. The correct specifications are listed in the "OC-N Card Transmit and Receive Levels" section.
Step 5 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port. For specific procedures to use the test set equipment, consult the manufacturer.
Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port. To do this, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the card turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, determine whether there are conditions that could cause autonegotiation to fail:
a. Confirm that the attached Ethernet device has autonegotiation enabled and is configured for compatibility with the asymmetric flow control on the card.
b. Confirm that the attached Ethernet device configuration allows reception of flow control frames.
Step 8 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. (The autonegotiation process restarts.)
Step 9 If the alarm does not clear and the "TPTFAIL (G1000)" alarm on page 2-236 is also reported, complete the "Clear the TPTFAIL (G1000) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.
Note When the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition could be the G1000-4 card's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 10 If the TPTFAIL alarm was not reported, determine whether a terminal (inward) loopback has been provisioned on the port:
a. In node view, click the card to go to card view.
b. Click the Maintenance > Loopback tabs.
c. If the service state is listed as OOS-MA, LPBK&MT, a loopback is provisioned. Go to Step 11.
Step 11 If a loopback was provisioned, complete the "Clear Other DS-N Card, EC-1, or G1000 Card Loopbacks" procedure.
On the G1000-4, provisioning a terminal (inward) loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.
If the does not have a loopback condition, continue to Step 12.
Step 12 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm could be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps if the Ethernet circuit is part of a manual cross-connect:
Note An ONS 15454 Ethernet manual cross-connect is used when another vendors' equipment sits between ONS nodes, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere in the row of the CARLOSS alarm.
b. Right-click or left-click Select Affected Circuits in the shortcut menu that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. Examine the layout of your network and determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect by completing the following substeps:
•Log into the node at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross-connect circuit connects the Ethernet card to an OC-N card at the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide Chapter 6, "Create Circuits and Tunnels," for detailed procedures to create circuits.
Step 13 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) Any Card" procedure.
Step 14 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the Ethernet card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 15 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.51 CARLOSS (GE)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: GE
The Carrier Loss for Gigabit Ethernet (GE) alarm occurs on MXP and TXP card PPM clients supporting 1-Gbps or 10-Gbps traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.
Clear the CARLOSS (GE) Alarm
Step 1 Ensure that the GE client is correctly configured:
a. Double-click the card to display the card view.
b. Click the Provisioning > Pluggable Port Modules tabs.
c. View the Pluggable Port Modules area port listing in the Actual Equipment column and compare this with the client equipment. If no PPM is provisioned, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable," for provisioning instructions.
d. If a PPM has been created, view the contents of the Selected PPM area Rate column for the MXP or TXP MR card and compare this rate with the client equipment data rate. If the PPM rate is differently provisioned, select the PPM, click Delete, then click Create and choose the correct rate for the equipment type.
Step 2 If there is no PPM misprovisioning, check for a fiber cut. An LOS alarm is also present. If there is an alarm, complete the "Clear the LOS (OCN) Alarm" procedure.
Step 3 If there is no fiber cut or provisioning error, check the client-side equipment for any transmission errors on the line.
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.52 CARLOSS (ISC)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: ISC
The Carrier Loss for Inter-Service Channel (ISC) alarm occurs on TXP card PPM clients supporting ISC client traffic. The loss can be due to a misconfiguration, fiber cut, or client equipment problem.
Clear the CARLOSS (ISC) Alarm
Step 1 Complete the "Clear the CARLOSS (GE) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.53 CARLOSS (ML100T, ML1000)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Objects: ML100T, ML1000
A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-144. The Ethernet port has lost its link and is not receiving a valid signal.
A CARLOSS alarm occurs when the Ethernet port has been configured from the Cisco IOS command line interface (CLI) as a no-shutdown port and one of the following problems 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 Cisco IOS interface, refer to the <I_Ital>Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Clear the CARLOSS (ML100T, ML1000) 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. For more information about fiber connections and terminations, refer to the Cisco ONS 15454 Procedure Guide Chapter 2, "Install Cards and Fiber-Optic Cable."
Step 2 If the alarm does not clear, verify that autonegotiation is set properly on the ML-Series 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-Series 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 Cisco IOS CLI. Autonegotiation restarts.
Step 6 If the alarm does not clear, complete the Create the Facility (Line) Loopback on the Source DS-1, DS-3, DS3N-12, DS3i-N-12, or EC1 Port and test the loopback.
Step 7 If the problem persists with the loopback installed, complete the "Remove and Reinsert (Reseat) Any Card" procedure.
Step 8 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 9 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.54 CARLOSS (TRUNK)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Object: TRUNK
A Carrier Loss alarm on the optical trunk connecting to TXP_MR_10G, TXP_MR_2.5G, TXP_MR_10E, TXPP_MR_2.5G, or MXP_2.5G_10G, MXP_2.5G_10E cards is raised when ITU-T G.709 monitoring is disabled.
Clear the CARLOSS (TRUNK) Alarm
Step 1 Complete the "Clear the LOS (2R) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.55 CASETEMP-DEG
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: AOTS
The Case Temperature Degrade alarm is raised when a DWDM card temperature sensor detects an out-of-range external temperature at the shelf level. The working range for DWDM cards is from 23 degrees F (-5 degrees C) to 149 degrees F (65 degrees C).
Clear the CASETEMP-DEG Alarm
Step 1 Check for and resolve the "FAN" alarm on page 2-89 if it is raised against the shelf.
Step 2 If the alarm does not clear, complete the "Inspect, Clean, and Replace the Reusable Air Filter" procedure.
Step 3 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.56 CLDRESTART
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Cold Restart condition occurs when a card is physically removed and inserted, replaced, or when the ONS 15454 power is initialized.
Clear the CLDRESTART Condition
Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 If the condition fails to clear after the card reboots, complete the "Remove and Reinsert (Reseat) Any Card" procedure.
Step 3 If the condition does not clear, complete the "Physically Replace a Traffic Card" procedure for the card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 4 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.57 COMIOXC
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: EQPT
The Input/Output Slot To Cross-Connect Communication Failure alarm is caused by the XC10G cross-connect card. It occurs when there is a communication failure for a traffic slot.
Clear the COMIOXC Alarm
Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the reporting XC10G cross-connect card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 3 If the CTC reset does not clear the alarm, move traffic off the reporting cross-connect card. Complete the "Side Switch the Active and Standby XC10G Cross-Connect Cards" procedure.
Step 4 Complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting cross-connect card.
Step 5 If the alarm does not clear, complete the "Physically Replace an In-Service Cross-Connect 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 the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.58 COMM-FAIL
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2/TCC2P and the card. The failure could indicate a broken card interface.
Clear the COMM-FAIL Alarm
Step 1 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card.
Step 2 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the card.
Caution Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the
"CTC Card Resetting and Switching" section for commonly used traffic-switching procedures.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.59 CONTBUS-A-18
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2/TCC2P slot to TCC2/TCC2P slot occurs when the main processor on the TCC2/TCC2P in the first slot (TCC A) loses communication with the coprocessor on the same card. This applies to the Slot 7 TCC2/TCC2P.
Clear the CONTBUS-A-18 Alarm
Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure to make the Slot 11 TCC2/TCC2P active.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 2 Wait approximately 10 minutes for the Slot 7 TCC2/TCC2P to reset as the standby TCC2/TCC2P. Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 3 Position the cursor over the Slot 11 TCC2/TCC2P and complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure to return the card to the active state.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
2.8.60 CONTBUS-B-18
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2/TCC2P slot to TCC2/TCC2P slot occurs when the main processor on the TCC2/TCC2P in the second slot (TCC B) loses communication with the coprocessor on the same card. This applies to the Slot 11 TCC2/TCC2P.
Clear the CONTBUS-B-18 Alarm
Step 1 Complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure to make the Slot 7 TCC2/TCC2P active.
Step 2 Wait approximately 10 minutes for the Slot 11 TCC2/TCC2P to reset as the standby TCC2/TCC2P. Verify that the ACT/SBY LED is correctly illuminated before proceeding to the next step. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 3 Position the cursor over the Slot 7 TCC2/TCC2P and complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure to return the Slot 11 TCC2/TCC2P card to the active state.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1-800-553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
2.8.61 CONTBUS-IO-A
•Default Severity: Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCCA to Shelf A Slot Communication Failure alarm occurs when the active Slot 7 TCC2/TCC2P (TCC A) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 switches to the protect TCC2/TCC2P. In the case of a TCC2/TCC2P protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P. If the alarm persists, the problem is with the physical path of communication from the TCC2/TCC2P card to the reporting card. The physical path of communication includes the TCC2/TCC2P, the other card, and the backplane.
Clear the CONTBUS-IO-A Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab and view the Eqpt Type column to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm on page 2-172 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby Slot 11 TCC2/TCC2P, perform a CTC reset of the object card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby Slot 11 TCC2/TCC2P, complete the "Reset a Traffic Card in CTC" procedure for it. The procedure is similar.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.)
If CONTBUS-IO-A is raised on several cards at the same time, complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 4 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 5 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
2.8.62 CONTBUS-IO-B
•Default Severity: Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCC B to Shelf Communication Failure alarm occurs when the active Slot 11 TCC2/TCC2P (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 switches to the protect TCC2/TCC2P. In the case of a TCC2/TCC2P protection switch, the alarm clears after the other cards establish communication with the newly active TCC2/TCC2P. If the alarm persists, the problem is with the physical path of communication from the TCC2/TCC2P card to the reporting card. The physical path of communication includes the TCC2/TCC2P, the other card, and the backplane.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab and view the Eqpt Type column to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm on page 2-172 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby Slot 7 TCC2/TCC2P, perform a CTC reset of the object card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby Slot 7 TCC2/TCC2P, complete the "Reset a Traffic Card in CTC" procedure for it. The procedure is similar.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. (A reset standby card remains standby.)
Step 4 If CONTBUS-IO-B is raised on several cards at the same time, complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 5 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 6 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Step 7 If the reset card has not rebooted successfully, or the alarm has not cleared, call Cisco TAC (1 800 553-2447). If the Cisco TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure. If the Cisco TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
2.8.63 CTNEQPT-MISMATCH
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Connection Equipment Mismatch (CTNEQPT-MISMATCH) condition is raised when there is a mismatch between the cross-connect card preprovisioned in the slot and the card actually present in the shelf. For example, one type of cross-connect card might be preprovisioned in Slot 10, but another might be physically installed. Or a card that is mismatched with the card. For example, CTNEQPT-MISMATCH is raised in when an XCVT card is replaced with an XC10G card.
Note Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation may briefly occur during the upgrade process.
Note The cross-connect card you are replacing should not be the active card. (It can be in SBY state or otherwise not in use.)
If you upgrade a node to R5.0 and replace an XC with XCVT or XC10G, or an XCVT with an XC10G, the CTNEQPT-MISMATCH condition is raised but it is cleared when the upgrade process ends.
Note During an upgrade, this condition occurs and is raised as its default severity, Not Alarmed (NA). However, after the upgrade has occurred, if you wish to change the condition's severity so that it is Not Reported (NR), you can do this by modifying the alarm profile used at the node. For more information about modifying alarm severities, refer to the Cisco ONS 15454 Procedure Guide.
Clear the CTNEQPT-MISMATCH Condition
Step 1 Verify what kind of card is preprovisioned in the slot:
a. In node view, click the Inventory tab.
b. View the slot's row contents in the Eqpt Type and Actual Eqpt Type columns.
The Eqpt Type column contains the equipment that is provisioned in the slot. The Actual Eqpt Type contains the equipment that is physically present in the slot. For example, Slot 8 might be provisioned for an XCVT card, which is shown in the Eqpt Type column, but an XC10G card could be physically present in the slot. The XC10G would be shown in the Actual Eqpt Type column.
Step 2 Complete the "Physically Replace a Traffic Card" procedure for the mismatched card.
Step 3 If the condition does not clear, log onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.8.64 CTNEQPT-PBPROT
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: EQPT
The Interconnection Equipment Failure Protect Cross-Connect Card Payload Bus Alarm indicates a failure of the main payload between the protect ONS 15454 Slot 10 XC10G 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 and the reporting traffic card, or the TCC2/TCC2P and the backplane.
Note This alarm automatically raises and clears when the Slot 8 XC10G cross-connect card is reseated.
Caution Software update on a standby TCC2/TCC2P can take up to 30 minutes.
Clear the CTNEQPT-PBPROT Alarm
Step 1 If all traffic cards show CTNEQPT-PBPROT alarm:
a. Complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure for the standby TCC2/TCC2P card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
b. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the standby TCC2/TCC2P.
Caution Do not physically reseat an active TCC2/TCC2P. Doing so disrupts traffic.
Step 2 If not all cards show the alarm, perform a CTC reset on the standby XC10G card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
If the cross-connect reset is not complete and error-free or if the TCC2/TCC2P reboots automatically, call Cisco TAC (1 800 553-2447).
Step 4 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the standby XC10G card.
Step 5 Determine whether the card is an active card or standby card in a protection group. Click the node view Maintenance > Protection tabs, then click the protection group. The cards and their statuses are displayed in the list.
Step 6 If the reporting traffic card is the active card in the protection group, complete the "Initiate a 1:1 Card Switch Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.
Step 7 Complete the "Reset a Traffic Card in CTC" procedure on the reporting card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 8 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 9 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting card.
Step 10 Complete the "Initiate a 1:1 Card Switch Command" procedure to switch traffic back.
Step 11 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting traffic 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, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.65 CTNEQPT-PBWORK
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: EQPT
The Interconnection Equipment Failure Working Cross-Connect Card Payload Bus alarm indicates a failure in the main payload bus between the ONS 15454 Slot 8 XC10G 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 and the reporting traffic card, or the TCC2/TCC2P and the backplane.
Note This alarm automatically raises and clears when the ONS 15454 Slot 10 XC10G cross-connect card is reseated.
Clear the CTNEQPT-PBWORK Alarm
Step 1 If all traffic cards show CTNEQPT-PBWORK alarm:
a. Complete the "Reset an Active TCC2/TCC2P and Activate the Standby Card" procedure for the active TCC2/TCC2P and then complete the "Remove and Reinsert (Reseat) the Standby TCC2/TCC2P Card" procedure.
b. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the TCC2/TCC2P card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Caution Do not physically reseat an active TCC2/TCC2P card; it disrupts traffic.
Step 2 If not all traffic cards show the alarm, complete the "Side Switch the Active and Standby XC10G Cross-Connect Cards" procedure for the active XC10G cross-connect card.
Step 3 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Typical Traffic Card LED Activity During Reset" section.
Step 4 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates a standby card.
Step 5 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the standby cross-connect card.
Step 6 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Initiate a 1:1 Card Switch Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.
Step 7 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the
