Table Of Contents
Alarm Troubleshooting
2.1 Alarm Index by Default Severity
2.1.1 Critical Alarms (CR)
2.1.2 Major Alarms (MJ)
2.1.3 Minor Alarms (MN)
2.1.4 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
2.8.7 APC-CORRECTION-SKIPPED
2.8.8 APC-DISABLED
Clear the APC-DISABLED Alarm
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 Alarm
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) Alarm
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) Alarm
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
2.8.46 CARLOSS (E100T, E1000F)
Clear the CARLOSS (E100T, E1000F) Alarm
2.8.47 CARLOSS (EQPT)
Clear the CARLOSS (EQPT) Alarm
2.8.48 CARLOSS (FC)
2.8.49 CARLOSS (G1000)
Clear the CARLOSS (G1000) Alarm
2.8.50 CARLOSS (GE)
Clear the CARLOSS (GE) Alarm
2.8.51 CARLOSS (ISC)
Clear the CARLOSS (ISC) Alarm
2.8.52 CARLOSS (ML100T, ML1000, ML2)
Clear the CARLOSS (ML100T, ML1000, ML2) Alarm
2.8.53 CARLOSS (TRUNK)
Clear the CARLOSS (TRUNK) Alarm
2.8.54 CASETEMP-DEG
Clear the CASETEMP-DEG Alarm
2.8.55 CKTDOWN
Clear the CKTDOWN 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-MISS
Clear the EQPT-MISS Alarm
2.8.80 ERFI-P-CONN
Clear the ERFI-P-CONN Condition
2.8.81 ERFI-P-PAYLD
Clear the ERFI-P-PAYLD Condition
2.8.82 ERFI-P-SRVR
Clear the ERFI-P-SRVR Condition
2.8.83 ERROR-CONFIG
Clear the ERROR-CONFIG Alarm
2.8.84 ETH-LINKLOSS
Clear the ETH-LINKLOSS Condition
2.8.85 E-W-MISMATCH
Clear the E-W-MISMATCH Alarm with a Physical Switch
Clear the E-W-MISMATCH Alarm in CTC
2.8.86 EXCCOL
Clear the EXCCOL Alarm
2.8.87 EXERCISE-RING-FAIL
Clear the EXERCISE-RING-FAIL Condition
2.8.88 EXERCISE-SPAN-FAIL
Clear the EXERCISE-SPAN-FAIL Condition
2.8.89 EXT
Clear the EXT Alarm
2.8.90 EXTRA-TRAF-PREEMPT
Clear the EXTRA-TRAF-PREEMPT Alarm
2.8.91 FAILTOSW
Clear the FAILTOSW Condition
2.8.92 FAILTOSW-PATH
Clear the FAILTOSW-PATH Alarm in a Path Protection Configuration
2.8.93 FAILTOSWR
Clear the FAILTOSWR Condition in a BLSR Configuration
2.8.94 FAILTOSWS
Clear the FAILTOSWS Condition
2.8.95 FAN
Clear the FAN Alarm
2.8.96 FC-NO-CREDITS
Clear the FC-NO-CREDITS Alarm
2.8.97 FE-AIS
Clear the FE-AIS Condition
2.8.98 FEC-MISM
Clear the FEC-MISM Alarm
2.8.99 FE-DS1-MULTLOS
Clear the FE-DS1-MULTLOS Condition
2.8.100 FE-DS1-NSA
Clear the FE-DS1-NSA Condition
2.8.101 FE-DS1-SA
Clear the FE-DS1-SA Condition
2.8.102 FE-DS1-SNGLLOS
Clear the FE-DS1-SNGLLOS Condition
2.8.103 FE-DS3-NSA
Clear the FE-DS3-NSA Condition
2.8.104 FE-DS3-SA
Clear the FE-DS3-SA Condition
2.8.105 FE-EQPT-NSA
Clear the FE-EQPT-NSA Condition
2.8.106 FE-FRCDWKSWBK-SPAN
Clear the FE-FRCDWKSWBK-SPAN Condition
2.8.107 FE-FRCDWKSWPR-RING
Clear the FE-FRCDWKSWPR-RING Condition
2.8.108 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-SPAN Condition
2.8.109 FE-IDLE
Clear the FE-IDLE Condition
2.8.110 FE-LOCKOUTOFPR-SPAN
Clear the FE-LOCKOUTOFPR-SPAN Condition
2.8.111 FE-LOF
Clear the FE-LOF Condition
2.8.112 FE-LOS
Clear the FE-LOS Condition
2.8.113 FE-MANWKSWBK-SPAN
Clear the FE-MANWKSWBK-SPAN Condition
2.8.114 FE-MANWKSWPR-RING
Clear the FE-MANWKSWPR-RING Condition
2.8.115 FE-MANWKSWPR-SPAN
Clear the FE-MANWKSWPR-SPAN Condition
2.8.116 FEPRLF
Clear the FEPRLF Alarm on a Four-Fiber BLSR
2.8.117 FIBERTEMP-DEG
Clear the FIBERTEMP-DEG Alarm
2.8.118 FORCED-REQ
Clear the FORCED-REQ Condition
2.8.119 FORCED-REQ-RING
Clear the FORCED-REQ-RING Condition
2.8.120 FORCED-REQ-SPAN
Clear the FORCED-REQ-SPAN Condition
2.8.121 FRCDSWTOINT
2.8.122 FRCDSWTOPRI
2.8.123 FRCDSWTOSEC
2.8.124 FRCDSWTOTHIRD
2.8.125 FRNGSYNC
Clear the FRNGSYNC Alarm
2.8.126 FSTSYNC
2.8.127 FULLPASSTHR-BI
Clear the FULLPASSTHR-BI Condition
2.8.128 GAIN-HDEG
Clear the GAIN-HDEG Alarm
2.8.129 GAIN-HFAIL
Clear the GAIN-HFAIL Alarm
2.8.130 GAIN-LDEG
Clear the GAIN-LDEG Alarm
2.8.131 GAIN-LFAIL
Clear the GAIN-LFAIL Alarm
2.8.132 GCC-EOC
Clear the GCC-EOC Alarm
2.8.133 GE-OOSYNC
Clear the GE-OOSYNC Alarm
2.8.134 GFP-CSF
Clear the GFP-CSF Alarm
2.8.135 GFP-DE-MISMATCH
Clear the GFP-DE-MISMATCH Alarm
2.8.136 GFP-EX-MISMATCH
Clear the GFP-EX-MISMATCH Alarm
2.8.137 GFP-LFD
Clear the GFP-LFD Alarm
2.8.138 GFP-NO-BUFFERS
Clear the GFP-NO-BUFFERS Alarm
2.8.139 GFP-UP-MISMATCH
Clear the GFP-UP-MISMATCH Alarm
2.8.140 HELLO
Clear the HELLO Alarm
2.8.141 HIBATVG
Clear the HIBATVG Alarm
2.8.142 HI-CCVOLT
Clear the HI-CCVOLT Condition
2.8.143 HI-LASERBIAS
Clear the HI-LASERBIAS Alarm
2.8.144 HI-LASERTEMP
Clear the HI-LASERTEMP Alarm
2.8.145 HI-RXPOWER
Clear the HI-RXPOWER Alarm
2.8.146 HITEMP
Clear the HITEMP Alarm
2.8.147 HI-TXPOWER
Clear the HI-TXPOWER Alarm
2.8.148 HLDOVRSYNC
Clear the HLDOVRSYNC Alarm
2.8.149 I-HITEMP
Clear the I-HITEMP Alarm
2.8.150 IMPROPRMVL
Clear the IMPROPRMVL Alarm
2.8.151 INC-ISD
2.8.152 INHSWPR
Clear the INHSWPR Condition
2.8.153 INHSWWKG
Clear the INHSWWKG Condition
2.8.154 INTRUSION-PSWD
Clear the INTRUSION-PSWD Condition
2.8.155 INVMACADR
Clear the INVMACADR Alarm
2.8.156 IOSCFGCOPY
2.8.157 KB-PASSTHR
Clear the KB-PASSTHR Condition
2.8.158 KBYTE-APS-CHANNEL-FAILURE
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
2.8.159 LAN-POL-REV
Clear the LAN-POL-REV Condition
2.8.160 LASER-APR
2.8.161 LASERBIAS-DEG
Clear the LASERBIAS-DEG Alarm
2.8.162 LASERBIAS-FAIL
Clear the LASERBIAS-FAIL Alarm
2.8.163 LASEREOL
Clear the LASEREOL Alarm
2.8.164 LASERTEMP-DEG
Clear the LASERTEMP-DEG Alarm
2.8.165 LCAS-CRC
Clear the LCAS-CRC Condition
2.8.166 LCAS-RX-FAIL
Clear the LCAS-RX-FAIL Condition
2.8.167 LCAS-TX-ADD
2.8.168 LCAS-TX-DNU
2.8.169 LKOUTPR-S
Clear the LKOUTPR-S Condition
2.8.170 LMP-HELLODOWN
Clear the LMP-HELLODOWN Alarm
2.8.171 LMP-NDFAIL
Clear the LMP-NDFAIL Alarm
2.8.172 LOA
Clear the LOA Alarm
2.8.173 LOCKOUT-REQ
Clear the LOCKOUT-REQ Condition
2.8.174 LOF (BITS)
Clear the LOF (BITS) Alarm
2.8.175 LOF (DS1)
Clear the LOF (DS1) Alarm
2.8.176 LOF (DS3)
Clear the LOF (DS3) Alarm
2.8.177 LOF (EC1-12)
Clear the LOF (EC1-12) Alarm
2.8.178 LOF (OCN)
Clear the LOF (OCN) Alarm
2.8.179 LOF (TRUNK)
Clear the LOF (TRUNK) Alarm
2.8.180 LO-LASERTEMP
Clear the LO-LASERTEMP Alarm
2.8.181 LOM
Clear the LOM Alarm
2.8.182 LOP-P
Clear the LOP-P Alarm
2.8.183 LOP-V
Clear the LOP-V Alarm
2.8.184 LO-RXPOWER
Clear the LO-RXPOWER Alarm
2.8.185 LOS (2R)
Clear the LOS (2R) Alarm
2.8.186 LOS (BITS)
Clear the LOS (BITS) Alarm
2.8.187 LOS (DS1)
Clear the LOS (DS1) Alarm
2.8.188 LOS (DS3)
Clear the LOS (DS3) Alarm
2.8.189 LOS (EC1-12)
Clear the LOS (EC1-12) Alarm
2.8.190 LOS (ESCON)
2.8.191 LOS (FUDC)
Clear the LOS (FUDC) Alarm
2.8.192 LOS (ISC)
Clear the LOS (ISC) Alarm
2.8.193 LOS (MSUDC)
2.8.194 LOS (OCN)
Clear the LOS (OCN) Alarm
2.8.195 LOS (OTS)
Clear the LOS (OTS) Alarm
2.8.196 LOS (TRUNK)
Clear the LOS (TRUNK) Alarm
2.8.197 LOS-O
Clear the LOS-O Alarm
2.8.198 LOS-P (OCH, OMS, OTS)
Clear the LOS-P (OCH, 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 (TRUNK)
Clear the LPBKFACILITY (TRUNK) Condition
2.8.207 LPBKFACILITY(DS1, DS3)
Clear the LPBKFACILITY (DS1, DS3) Condition
2.8.208 LPBKFACILITY (EC1-12)
Clear the LPBKFACILITY (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 (ML2)
2.8.216 LPBKFACILITY (OCN)
Clear the LPBKFACILITY (OCN) Condition
2.8.217 LPBKTERMINAL (TRUNK)
Clear the LPBKTERMINAL (TRUNK) Condition
2.8.218 LPBKTERMINAL (DS1, DS3)
Clear the LPBKTERMINAL (DS1, DS3) Condition
2.8.219 LPBKTERMINAL (EC1-12)
Clear the LPBKTERMINAL (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 (ML2)
2.8.227 LPBKTERMINAL (OCN)
Clear the LPBKTERMINAL (OCN) 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 OCHNC-INC
2.8.247 ODUK-1-AIS-PM
Clear the ODUK-1-AIS-PM Condition
2.8.248 ODUK-2-AIS-PM
Clear the ODUK-2-AIS-PM Condition
2.8.249 ODUK-3-AIS-PM
Clear the ODUK-3-AIS-PM Condition
2.8.250 ODUK-4-AIS-PM
Clear the ODUK-4-AIS-PM Condition
2.8.251 ODUK-AIS-PM
Clear the ODUK-AIS-PM Condition
2.8.252 ODUK-BDI-PM
Clear the ODUK-BDI-PM Condition
2.8.253 ODUK-LCK-PM
Clear the ODUK-LCK-PM Condition
2.8.254 ODUK-OCI-PM
Clear the ODUK-OCI-PM Condition
2.8.255 ODUK-SD-PM
Clear the ODUK-SD-PM Condition
2.8.256 ODUK-SF-PM
Clear the ODUK-SF-PM Condition
2.8.257 ODUK-TIM-PM
Clear the ODUK-TIM-PM Condition
2.8.258 OOU-TPT
Clear the OOT-TPT Condition
2.8.259 OPTNTWMIS
Clear the OPTNTWMIS Alarm
2.8.260 OPWR-HDEG
Clear the OPWR-HDEG Alarm
2.8.261 OPWR-HFAIL
Clear the OPWR-HFAIL Alarm
2.8.262 OPWR-LDEG
Clear the OPWR-LDEG Alarm
2.8.263 OPWR-LFAIL
Clear the OPWR-LFAIL Alarm
2.8.264 OSRION
Clear the OSRION Condition
2.8.265 OTUK-AIS
Clear the OTUK-AIS Condition
2.8.266 OTUK-BDI
Clear the OTUK-BDI Condition
2.8.267 OTUK-IAE
2.8.268 OTUK-LOF
Clear the OTUK-LOF Alarm
2.8.269 OTUK-SD
Clear the OTUK-SD Condition
2.8.270 OTUK-SF
Clear the OTUK-SF Condition
2.8.271 OTUK-TIM
Clear the OTUK-TIM Condition
2.8.272 OUT-OF-SYNC
Clear the OUT-OF-SYNC Condition
2.8.273 PARAM-MISM
2.8.274 PDI-P
Clear the PDI-P Condition
2.8.275 PEER-NORESPONSE
Clear the PEER-NORESPONSE Alarm
2.8.276 PLM-P
Clear the PLM-P Alarm
2.8.277 PLM-V
Clear the PLM-V Alarm
2.8.278 PORT-ADD-PWR-DEG-HI
2.8.279 PORT-ADD-PWR-DEG-LOW
2.8.280 PORT-ADD-PWR-FAIL-HI
2.8.281 PORT-ADD-PWR-FAIL-LOW
Clear the PORT-ADD-PWR-FAIL-LOW Alarm
2.8.282 PORT-MISMATCH
2.8.283 PRC-DUPID
Clear the PRC-DUPID Alarm
2.8.284 PROTNA
Clear the PROTNA Alarm
2.8.285 PTIM
Clear the PTIM Alarm
2.8.286 PWR-FAIL-A
Clear the PWR-FAIL-A Alarm
2.8.287 PWR-FAIL-B
Clear the PWR-FAIL-B Alarm
2.8.288 PWR-FAIL-RET-A
Clear the PWR-FAIL-RET-A Alarm:
2.8.289 PWR-FAIL-RET-B
Clear the PWR-FAIL-RET-A Alarm
2.8.290 RAI
Clear the RAI Condition
2.8.291 RCVR-MISS
Clear the RCVR-MISS Alarm
2.8.292 RFI
Clear the RFI Condition
2.8.293 RFI-L
Clear the RFI-L Condition
2.8.294 RFI-P
Clear the RFI-P Condition
2.8.295 RFI-V
Clear the RFI-V Condition
2.8.296 RING-ID-MIS
Clear the RING-ID-MIS Alarm
2.8.297 RING-MISMATCH
Clear the RING-MISMATCH Alarm
2.8.298 RING-SW-EAST
2.8.299 RING-SW-WEST
2.8.300 RSVP-HELLODOWN
Clear the RSVP-HELLODOWN Alarm
2.8.301 RUNCFG-SAVENEED
2.8.302 SD (TRUNK)
Clear the SD (TRUNK) Condition
2.8.303 SD (DS1, DS3)
Clear the SD (DS1, DS3) Condition
2.8.304 SD-L
Clear the SD-L Condition
2.8.305 SD-P
Clear the SD-P Condition
2.8.306 SD-V
Clear the SD-V Condition
2.8.307 SF (TRUNK)
Clear the SF (TRUNK) Condition
2.8.308 SF (DS1, DS3)
Clear the SF (DS1, DS3) Condition
2.8.309 SF-L
Clear the SF-L Condition
2.8.310 SF-P
Clear the SF-P Condition
2.8.311 SF-V
2.8.312 SFTWDOWN
2.8.313 SH-INS-LOSS-VAR-DEG-HIGH
2.8.314 SH-INS-LOSS-VAR-DEG-LOW
2.8.315 SHUTTER-OPEN
Clear the SHUTTER-OPEN Alarm
2.8.316 SIGLOSS
Clear the SIGLOSS Alarm
2.8.317 SNTP-HOST
Clear the SNTP-HOST Alarm
2.8.318 SPAN-SW-EAST
2.8.319 SPAN-SW-WEST
2.8.320 SQUELCH
Clear the SQUELCH Condition
2.8.321 SQUELCHED
Clear the SQUELCHED Alarm
2.8.322 SQM
Clear the SQM Alarm
2.8.323 SSM-DUS
2.8.324 SSM-FAIL
Clear the SSM-FAIL Alarm
2.8.325 SSM-LNC
2.8.326 SSM-OFF
Clear the SSM-OFF Condition
2.8.327 SSM-PRC
2.8.328 SSM-PRS
2.8.329 SSM-RES
2.8.330 SSM-SDN-TN
2.8.331 SSM-SETS
2.8.332 SSM-SMC
2.8.333 SSM-ST2
2.8.334 SSM-ST3
2.8.335 SSM-ST3E
2.8.336 SSM-ST4
2.8.337 SSM-STU
Clear the SSM-STU Condition
2.8.338 SSM-TNC
2.8.339 SWMTXMOD
Clear the SWMTXMOD Alarm
2.8.340 SWTOPRI
2.8.341 SWTOSEC
Clear the SWTOSEC Condition
2.8.342 SWTOTHIRD
Clear the SWTOTHIRD Condition
2.8.343 SYNC-FREQ
Clear the SYNC-FREQ Condition
2.8.344 SYNCLOSS
Clear the SYNCLOSS Alarm
2.8.345 SYNCPRI
Clear the SYNCPRI Alarm
2.8.346 SYNCSEC
Clear the SYNCSEC Alarm
2.8.347 SYNCTHIRD
Clear the SYNCTHIRD Alarm
2.8.348 SYSBOOT
2.8.349 TIM
Clear the TIM Alarm or Condition
2.8.350 TIM-MON
Clear the TIM-MON Alarm
2.8.351 TIM-P
Clear the TIM-P Alarm
2.8.352 TPTFAIL (FCMR)
Clear the TPTFAIL (FCMR) Alarm
2.8.353 TPTFAIL (G1000)
Clear the TPTFAIL (G1000) Alarm
2.8.354 TPTFAIL (ML1000, ML100T, ML2)
Clear the TPTFAIL (ML1000, ML100T, ML2) Alarm
2.8.355 TRMT
Clear the TRMT Alarm
2.8.356 TRMT-MISS
Clear the TRMT-MISS Alarm
2.8.357 TX-AIS
Clear the TX-AIS Condition
2.8.358 TX-RAI
Clear the TX-RAI Condition
2.8.359 UNC-WORD
Clear the UNC-WORD Condition
2.8.360 UNEQ-P
Clear the UNEQ-P Alarm
2.8.361 UNEQ-V
Clear the UNEQ-V Alarm
2.8.362 UNREACHABLE-TARGET-POWER
2.8.363 UT-COMM-FAIL
Clear the UT-COMM-FAIL Alarm
2.8.364 UT-FAIL
Clear the UT-FAIL Alarm
2.8.365 VCG-DEG
Clear the VCG-DEG Condition
2.8.366 VCG-DOWN
Clear the VCG-DOWN Condition
2.8.367 VOA-HDEG
Clear the VOA-HDEG Alarm
2.8.368 VOA-HFAIL
Clear the VOA-HFAIL Alarm
2.8.369 VOA-LDEG
Clear the VOA-LDEG Alarm
2.8.370 VOA-LFAIL
Clear the VOA-LFAIL Alarm
2.8.371 WKSWPR
Clear the WKSWPR Condition
2.8.372 WTR
2.8.373 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 Path Protection Span External Switching Command
Initiate a Force Switch a BLSR
Initiate a Force Span Switch 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 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 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 SDCC Terminations
Clear an OC-N Card Facility or Terminal Loopback Circuit
Clear an OC-N Card 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 FCMR 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-8 gives definitions of all ONS 15454 alarm logical objects, which are the basis of the alarm profile list in Table 2-8.
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 (Cisco TAC) to report a service-affecting problem (1 800 553-2447).
More information about alarm profile information modification and downloads are located in the Cisco ONS 15454 DWDM Installation and Operations Guide.
Note Release 4.7 is DWDM only. It supports all DWDM, transponder (TXP), and muxponder (MXP) cards but not optical, electrical, fibre storage, or Ethernet cards.
2.1 Alarm Index 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.
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.
Table 2-6 ONS 15454 Alarm and Condition Alphabetical Index
AIS
|
FULLPASSTHR-BI
|
ODUK-AIS-PM
|
AIS-L
|
GAIN-HDEG
|
ODUK-BDI-PM
|
AIS-P
|
GAIN-HFAIL
|
ODUK-BDI-PM
|
AIS-V
|
GAIN-LDEG
|
ODUK-LCK-PM
|
ALS
|
GAIN-LFAIL
|
ODUK-OCI-PM
|
AMPLI-INIT
|
GCC-EOC
|
ODUK-SD-PM
|
APC-CORRECTION-SKIPPED
|
GE-OOSYNC
|
ODUK-SF-PM
|
APC-DISABLED
|
GFP-CSF
|
ODUK-TIM-PM
|
APC-END
|
GFP-DE-MISMATCH
|
OOU-TPT
|
APC-OUT-OF-RANGE
|
GFP-EX-MISMATCH
|
OPTNTWMIS
|
APSB
|
GFP-LFD
|
OPWR-HDEG
|
APSCDFLTK
|
GFP-NO-BUFFERS
|
OPWR-HFAIL
|
APSC-IMP
|
GFP-UP-MISMATCH
|
OPWR-LDEG
|
APSCINCON
|
HELLO
|
OPWR-LFAIL
|
APSCM
|
HIBATVG
|
OSRION
|
APSCNMIS
|
HI-CCVOLT
|
OTUK-AIS
|
APSIMP
|
HI-LASERBIAS
|
OTUK-BDI
|
APS-INV-PRIM
|
HI-LASERTEMP
|
OTUK-IAE
|
APS-PRIM-FAC
|
HI-RXPOWER
|
OTUK-LOF
|
APSMM
|
HITEMP
|
OTUK-SD
|
APS-PRIM-SEC-MISM
|
HI-TXPOWER
|
OTUK-SF
|
AS-CMD
|
HLDOVRSYNC
|
OTUK-TIM
|
AS-MT
|
I-HITEMP
|
OUT-OF-SYNC
|
AS-MT-OOG
|
IMPROPRMVL
|
PARAM-MISM
|
AUD-LOG-LOSS
|
INC-ISD
|
PDI-P
|
AUD-LOG-LOW
|
INHSWPR
|
PEER-NORESPONSE
|
AU-LOF
|
INHSWWKG
|
PLM-P
|
AUTOLSROFF
|
INTRUSION-PSWD
|
PLM-V
|
AUTORESET
|
INVMACADR
|
PORT-ADD-PWR-DEG-HI
|
AUTOSW-AIS
|
IOSCFGCOPY
|
PORT-ADD-PWR-DEG-LOW
|
AUTOSW-LOP (STSMON)
|
KB-PASSTHR
|
PORT-ADD-PWR-FAIL-HI
|
AUTOSW-LOP (VT-MON)
|
KBYTE-APS-CHANNEL-FAILURE
|
PORT-ADD-PWR-FAIL-LOW
|
AUTOSW-PDI
|
LAN-POL-REV
|
PORT-MISMATCH
|
AUTOSW-SDBER
|
LASER-APR
|
PRC-DUPID
|
AUTOSW-SFBER
|
LASERBIAS-DEG
|
PROTNA
|
AUTOSW-UNEQ (STSMON)
|
LASERBIAS-FAIL
|
PTIM
|
AUTOSW-UNEQ (VT-MON)
|
LASEREOL
|
PWR-FAIL-A
|
AWG-DEG
|
LASERTEMP-DEG
|
PWR-FAIL-B
|
AWG-FAIL
|
LCAS-CRC
|
PWR-FAIL-RET-A
|
AWG-OVERTEMP
|
LCAS-RX-FAIL
|
PWR-FAIL-RET-B
|
AWG-WARM-UP
|
LCAS-TX-ADD
|
RAI
|
BAT-FAIL
|
LCAS-TX-DNU
|
RCVR-MISS
|
BKUPMEMP
|
LKOUTPR-S
|
RFI
|
BLSROSYNC
|
LMP-HELLODOWN
|
RFI-L
|
BPV
|
LMP-NDFAIL
|
RFI-P
|
CARLOSS (E100T, E1000F)
|
LOA
|
RFI-V
|
CARLOSS (EQPT)
|
LOCKOUT-REQ
|
RING-ID-MIS
|
CARLOSS (G1000)
|
LOF (BITS)
|
RING-MISMATCH
|
CARLOSS (GE)
|
LOF (DS1)
|
RING-SW-EAST
|
CARLOSS (ISC)
|
LOF (DS3)
|
RING-SW-WEST
|
CARLOSS (ML100T, ML1000, ML2)
|
LOF (EC1-12)
|
RSVP-HELLODOWN
|
CARLOSS (TRUNK)
|
LOF (OCN)
|
RUNCFG-SAVENEED
|
CASETEMP-DEG
|
LOF (TRUNK)
|
SD (TRUNK)
|
CKTDOWN
|
LO-LASERTEMP
|
SD (DS1, DS3)
|
CLDRESTART
|
LOM
|
SD-L
|
COMIOXC
|
LOP-P
|
SD-P
|
COMM-FAIL
|
LOP-V
|
SD-V
|
CONTBUS-A-18
|
LO-RXPOWER
|
SF (TRUNK)
|
CONTBUS-B-18
|
LOS (2R)
|
SF (DS1, DS3)
|
CONTBUS-IO-A
|
LOS (BITS)
|
SF-L
|
CONTBUS-IO-B
|
LOS (DS1)
|
SF-P
|
CTNEQPT-MISMATCH
|
LOS (DS3)
|
SF-V
|
CTNEQPT-PBPROT
|
LOS (EC1-12)
|
SFTWDOWN
|
CTNEQPT-PBWORK
|
LOS (ESCON)
|
SH-INS-LOSS-VAR-DEG-HIGH
|
DATAFLT
|
LOS (ISC)
|
SH-INS-LOSS-VAR-DEG-LOW
|
DBOSYNC
|
LOS (FUDC)
|
SHUTTER-OPEN
|
DS3-MISM
|
LOS (MSUDC)
|
SIGLOSS
|
DSP-COMM-FAIL
|
LOS (OCN)
|
SNTP-HOST
|
DSP-FAIL
|
LOS (OTS)
|
SPAN-SW-EAST
|
DUP-IPADDR
|
LOS (TRUNK)
|
SPAN-SW-WEST
|
DUP-NODENAME
|
LOS-O
|
SQUELCH
|
EHIBATVG
|
LOS-P (OCH, OMS, OTS)
|
SQUELCHED
|
ELWBATVG
|
LOS-P (TRUNK)
|
SQM
|
EOC
|
LO-TXPOWER
|
SSM-DUS
|
EOC-L
|
LPBKCRS
|
SSM-FAIL
|
EQPT
|
LPBKDS1FEAC
|
SSM-LNC
|
EQPT-MISS
|
LPBKDS1FEAC-CMD
|
SSM-OFF
|
ERFI-P-CONN
|
LPBKDS3FEAC
|
SSM-PRC
|
ERFI-P-PAYLD
|
LPBKDS3FEAC-CMD
|
SSM-PRS
|
ERFI-P-SRVR
|
LPBKFACILITY (TRUNK)
|
SSM-RES
|
ERROR-CONFIG
|
LPBKFACILITY(DS1, DS3)
|
SSM-SDN-TN
|
ETH-LINKLOSS
|
LPBKFACILITY (EC1-12)
|
SSM-SETS
|
E-W-MISMATCH
|
LPBKFACILITY (ESCON)
|
SSM-SMC
|
EXCCOL
|
LPBKFACILITY (FC)
|
SSM-ST2
|
EXERCISE-RING-FAIL
|
LPBKFACILITY (FCMR)
|
SSM-ST3
|
EXERCISE-SPAN-FAIL
|
LPBKFACILITY (G1000)
|
SSM-ST3E
|
EXT
|
LPBKFACILITY (GE)
|
SSM-ST4
|
EXTRA-TRAF-PREEMPT
|
LPBKFACILITY (ISC)
|
SSM-STU
|
FAILTOSW
|
LPBKFACILITY (ML2)
|
SSM-TNC
|
FAILTOSW-PATH
|
LPBKFACILITY (OCN)
|
SWMTXMOD
|
FAILTOSWR
|
LPBKTERMINAL (TRUNK)
|
SWTOPRI
|
FAILTOSWS
|
LPBKTERMINAL (DS1, DS3)
|
SWTOSEC
|
FAN
|
LPBKTERMINAL (EC1-12)
|
SWTOTHIRD
|
FC-NO-CREDITS
|
LPBKTERMINAL (ESCON)
|
SYNC-FREQ
|
FE-AIS
|
LPBKTERMINAL (FC)
|
SYNCLOSS
|
FEC-MISM
|
LPBKTERMINAL (FCMR)
|
SYNCPRI
|
FE-DS1-MULTLOS
|
LPBKTERMINAL (G1000)
|
SYNCSEC
|
FE-DS1-NSA
|
LPBKTERMINAL (GE)
|
SYNCTHIRD
|
FE-DS1-SA
|
LPBKTERMINAL (ISC)
|
SYSBOOT
|
FE-DS1-SNGLLOS
|
LPBKTERMINAL (ML2)
|
TIM
|
FE-DS3-NSA
|
LPBKTERMINAL (OCN)
|
TIM-MON
|
FE-DS3-SA
|
LWBATVG
|
TIM-P
|
FE-EQPT-NSA
|
MAN-REQ
|
TPTFAIL (FCMR)
|
FE-FRCDWKSWBK-SPAN
|
MANRESET
|
TPTFAIL (G1000)
|
FE-FRCDWKSWPR-RING
|
MANSWTOINT
|
TPTFAIL (ML1000, ML100T, ML2)
|
FE-FRCDWKSWPR-SPAN
|
MANSWTOPRI
|
TRMT
|
FE-IDLE
|
MANSWTOSEC
|
TRMT-MISS
|
FE-LOCKOUTOFPR-SPAN
|
MANSWTOTHIRD
|
TX-AIS
|
FE-LOF
|
MANUAL-REQ-RING
|
TX-RAI
|
FE-LOS
|
MANUAL-REQ-SPAN
|
UNC-WORD
|
FE-MANWKSWBK-SPAN
|
MEA (AIP)
|
UNEQ-P
|
FE-MANWKSWPR-RING
|
MEA (BIC)
|
UNEQ-V
|
FE-MANWKSWPR-SPAN
|
MEA (EQPT)
|
UNREACHABLE-TARGET-POWER
|
FEPRLF
|
MEA (FAN)
|
UT-COMM-FAIL
|
FIBERTEMP-DEG
|
MEA (PPM)
|
UT-FAIL
|
FORCED-REQ
|
MEM-GONE
|
VCG-DEG
|
FORCED-REQ-RING
|
MEM-LOW
|
VCG-DOWN
|
FORCED-REQ-SPAN
|
MFGMEM
|
VOA-HDEG
|
FRCDSWTOINT
|
NO-CONFIG
|
VOA-HFAIL
|
FRCDSWTOPRI
|
OCHNC-INC
|
VOA-LDEG
|
FRCDSWTOSEC
|
ODUK-1-AIS-PM
|
VOA-LFAIL
|
FRCDSWTOTHIRD
|
ODUK-2-AIS-PM
|
WKSWPR
|
FRNGSYNC
|
ODUK-3-AIS-PM
|
WTR
|
FSTSYNC
|
ODUK-4-AIS-PM
|
WVL-MISMATCH
|
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.
|
DS1
|
A DS-1 line on a DS-1 or DS-3 electrical card (DS1-14, DS1N-14, DS3-12, DS3N-12, DS3-12E, DS3N-12E, DS3XM-6, DS3XM-12).
|
DS3
|
A DS-3 line on a DS-3 electrical card.
|
E1000F
|
An E1000 Ethernet card (E1000-2, E1000-2G).
|
E100T
|
An E100 Ethernet card (E100T-12, E100T-G).
|
EC1-12
|
An EC1-12 electrical card.
|
ENV
|
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, STS, and VT.
|
ESCON
|
Enterprise System Connection fiber optic technology, referring to the following transponder (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.
|
FICON
|
Fiber Connection fiber optic technology, referring to the following MXP or TXP cards: MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_2.5G, TXPP_MR_2.5G.
|
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).
|
ML2
|
This object is used in the ONS 15310 platform and is reserved for future use in the ONS 15454 platform.
|
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 Multiplexer (DWDM) cards. DWDM cards on the ONS 15454 include the OSCM, OSC-CSM, OPT-PRE, OPT-BST, 32MUX-O, 32DMX-O, 32DMX, 4MD-xx.x,AD-4B-xx.x, AD-1B-xx.x, AD-4C-xx.x, AD-2C-xx.x, AD-1C-xx.x, and the 32WSS.
|
OCHNC_CONN
|
The optical channel connection, referring to DWDM cards.
|
OCN
|
An OC-N line on any OC-N card.
|
OMS
|
Optical multiplex section.
|
OTS
|
Optical transport section.
|
PPM
|
Pluggable port module, referring to MXP and TXP cards.
|
STSTRM
|
STS alarm detection at termination (downstream from the cross-connect).
|
TRUNK
|
The optical or dense wavelength division multiplexing (DWDM) card carrying the high-speed signal; referring to MXP or TXP cards.
|
UCP-CKT
|
Unified control plane circuit.
|
UCP-IPCC
|
Unified control plane IP control channel.
|
UCP-NBR
|
Unified control plane neighbor.
|
VCG
|
A virtual concatenation group of virtual tributaries (VT).
|
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 4.7 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 The list is given here exactly as it is shown in CTC, and in some cases does not follow alphabetical order.
Table 2-8 Alarm Index by Logical Object
2R::ALS
|
FC::LOCKOUT-REQ
|
OCN::SQUELCH
|
2R::AS-CMD
|
FC::LPBKFACILITY (FC)
|
OCN::SQUELCHED
|
2R::AS-MT
|
FC::LPBKTERMINAL (FC)
|
OCN::SSM-DUS
|
2R::FAILTOSW
|
FC::MANUAL-REQ-SPAN
|
OCN::SSM-FAIL
|
2R::FORCED-REQ-SPAN
|
FC::OUT-OF-SYNC
|
OCN::SSM-OFF
|
2R::HI-LASERBIAS
|
FC::SIGLOSS
|
OCN::SSM-PRS
|
2R::HI-RXPOWER
|
FC::SQUELCHED
|
OCN::SSM-RES
|
2R::HI-TXPOWER
|
FC::SYNCLOSS
|
OCN::SSM-SMC
|
2R::LO-RXPOWER
|
FC::WKSWPR
|
OCN::SSM-ST2
|
2R::LO-TXPOWER
|
FC::WTR
|
OCN::SSM-ST3
|
2R::LOCKOUT-REQ
|
FCMR::AS-CMD
|
OCN::SSM-ST3E
|
2R::LOS (2R)
|
FCMR::AS-MT
|
OCN::SSM-ST4
|
2R::MANUAL-REQ-SPAN
|
FCMR::FC-NO-CREDITS
|
OCN::SSM-STU
|
2R::SQUELCHED
|
FCMR::LPBKFACILITY (FCMR)
|
OCN::SSM-TNC
|
2R::WKSWPR
|
FCMR::LPBKTERMINAL (FCMR)
|
OCN::SYNC-FREQ
|
2R::WTR
|
FCMR::PORT-MISMATCH
|
OCN::TIM
|
AICI-AEP::EQPT
|
FCMR::SIGLOSS
|
OCN::TIM-MON
|
AICI-AEP::MFGMEM
|
FCMR::SYNCLOSS
|
OCN::WKSWPR
|
AICI-AIE::EQPT
|
FCMR::TPTFAIL (FCMR)
|
OCN::WTR
|
AICI-AIE::MFGMEM
|
FUDC::AIS
|
OMS::APC-CORRECTION-SKIPPED
|
AIP::INVMACADR
|
FUDC::LOS (FUDC)
|
OMS::APC-OUT-OF-RANGE
|
AIP::MEA (AIP)
|
G1000::AS-CMD
|
OMS::AS-CMD
|
AIP::MFGMEM
|
G1000::AS-MT
|
OMS::AS-MT
|
AOTS::ALS
|
G1000::CARLOSS (G1000)
|
OMS::LOS-O
|
AOTS::AMPLI-INIT
|
G1000::LPBKFACILITY (G1000)
|
OMS::LOS-P (OCH, OMS, OTS)
|
AOTS::APC-CORRECTION-SKIPPED
|
G1000::LPBKTERMINAL (G1000)
|
OMS::OPWR-HDEG
|
AOTS::APC-OUT-OF-RANGE
|
G1000::TPTFAIL (G1000)
|
OMS::OPWR-HFAIL
|
AOTS::AS-CMD
|
GE::ALS
|
OMS::OPWR-LDEG
|
AOTS::AS-MT
|
GE::AS-CMD
|
OMS::OPWR-LFAIL
|
AOTS::CASETEMP-DEG
|
GE::AS-MT
|
OMS::PARAM-MISM
|
AOTS::FIBERTEMP-DEG
|
GE::CARLOSS (GE)
|
OMS::VOA-HDEG
|
AOTS::GAIN-HDEG
|
GE::FAILTOSW
|
OMS::VOA-HFAIL
|
AOTS::GAIN-HFAIL
|
GE::FORCED-REQ-SPAN
|
OMS::VOA-LDEG
|
AOTS::GAIN-LDEG
|
GE::GE-OOSYNC
|
OMS::VOA-LFAIL
|
AOTS::GAIN-LFAIL
|
GE::HI-LASERBIAS
|
OSC-RING::RING-ID-MIS
|
AOTS::LASER-APR
|
GE::HI-RXPOWER
|
OTS::APC-CORRECTION-SKIPPED
|
AOTS::LASERBIAS-DEG
|
GE::HI-TXPOWER
|
OTS::APC-OUT-OF-RANGE
|
AOTS::LASERBIAS-FAIL
|
GE::LO-RXPOWER
|
OTS::AS-CMD
|
AOTS::LASERTEMP-DEG
|
GE::LO-TXPOWER
|
OTS::AS-MT
|
AOTS::OPWR-HDEG
|
GE::LOCKOUT-REQ
|
OTS::AWG-DEG
|
AOTS::OPWR-HFAIL
|
GE::LPBKFACILITY (GE)
|
OTS::AWG-FAIL
|
AOTS::OPWR-LDEG
|
GE::LPBKTERMINAL (GE)
|
OTS::AWG-OVERTEMP
|
AOTS::OPWR-LFAIL
|
GE::MANUAL-REQ-SPAN
|
OTS::AWG-WARM-UP
|
AOTS::OSRION
|
GE::OUT-OF-SYNC
|
OTS::LASERBIAS-DEG
|
AOTS::PARAM-MISM
|
GE::SIGLOSS
|
OTS::LOS (OTS)
|
AOTS::VOA-HDEG
|
GE::SQUELCHED
|
OTS::LOS-O
|
AOTS::VOA-HFAIL
|
GE::SYNCLOSS
|
OTS::LOS-P (OCH, OMS, OTS)
|
AOTS::VOA-LDEG
|
GE::WKSWPR
|
OTS::OPWR-HDEG
|
AOTS::VOA-LFAIL
|
GE::WTR
|
OTS::OPWR-HFAIL
|
BIC::MEA (BIC)
|
GFP-FAC::GFP-CSF
|
OTS::OPWR-LDEG
|
BITS::AIS
|
GFP-FAC::GFP-DE-MISMATCH
|
OTS::OPWR-LFAIL
|
BITS::BPV
|
GFP-FAC::GFP-EX-MISMATCH
|
OTS::OSRION
|
BITS::HI-CCVOLT
|
GFP-FAC::GFP-LFD
|
OTS::PARAM-MISM
|
BITS::LOF (BITS)
|
GFP-FAC::GFP-NO-BUFFERS
|
OTS::SH-INS-LOSS-VAR-DEG-HIGH
|
BITS::LOS (BITS)
|
GFP-FAC::GFP-UP-MISMATCH
|
OTS::SH-INS-LOSS-VAR-DEG-LOW
|
BITS::SSM-DUS
|
ISC::ALS
|
OTS::SHUTTER-OPEN
|
BITS::SSM-FAIL
|
ISC::AS-CMD
|
OTS::VOA-HDEG
|
BITS::SSM-OFF
|
ISC::AS-MT
|
OTS::VOA-HFAIL
|
BITS::SSM-PRS
|
ISC::CARLOSS (ISC)
|
OTS::VOA-LDEG
|
BITS::SSM-RES
|
ISC::FAILTOSW
|
OTS::VOA-LFAIL
|
BITS::SSM-SMC
|
ISC::FORCED-REQ-SPAN
|
PPM::AS-CMD
|
BITS::SSM-ST2
|
ISC::GE-OOSYNC
|
PPM::AS-MT
|
BITS::SSM-ST3
|
ISC::HI-LASERBIAS
|
PPM::EQPT
|
BITS::SSM-ST3E
|
ISC::HI-RXPOWER
|
PPM::HI-LASERBIAS
|
BITS::SSM-ST4
|
ISC::HI-TXPOWER
|
PPM::HI-LASERTEMP
|
BITS::SSM-STU
|
ISC::LO-RXPOWER
|
PPM::HI-TXPOWER
|
BITS::SSM-TNC
|
ISC::LO-TXPOWER
|
PPM::IMPROPRMVL
|
BITS::SYNC-FREQ
|
ISC::LOCKOUT-REQ
|
PPM::LO-TXPOWER
|
BPLANE::AS-CMD
|
ISC::LOS (ISC)
|
PPM::MEA (PPM)
|
BPLANE::MFGMEM
|
ISC::LPBKFACILITY (ISC)
|
PPM::MFGMEM
|
DS1::AIS
|
ISC::LPBKTERMINAL (ISC)
|
PWR::AS-CMD
|
DS1::AS-CMD
|
ISC::MANUAL-REQ-SPAN
|
PWR::BAT-FAIL
|
DS1::AS-MT
|
ISC::OUT-OF-SYNC
|
PWR::EHIBATVG
|
DS1::LOF (DS1)
|
ISC::SIGLOSS
|
PWR::ELWBATVG
|
DS1::LOS (DS1)
|
ISC::SQUELCHED
|
PWR::HIBATVG
|
DS1::LPBKDS1FEAC
|
ISC::SYNCLOSS
|
PWR::LWBATVG
|
DS1::LPBKDS1FEAC-CMD
|
ISC::WKSWPR
|
STSMON::AIS-P
|
DS1::LPBKFACILITY(DS1, DS3)
|
ISC::WTR
|
STSMON::AUTOSW-AIS
|
DS1::LPBKTERMINAL (DS1, DS3)
|
ML1000::AS-CMD
|
STSMON::AUTOSW-LOP (STSMON)
|
DS1::RAI
|
ML1000::AS-MT
|
STSMON::AUTOSW-PDI
|
DS1::RCVR-MISS
|
ML1000::CARLOSS (ML100T, ML1000, ML2)
|
STSMON::AUTOSW-SDBER
|
DS1::SD (DS1, DS3)
|
ML1000::GFP-CSF
|
STSMON::AUTOSW-SFBER
|
DS1::SF (DS1, DS3)
|
ML1000::GFP-DE-MISMATCH
|
STSMON::AUTOSW-UNEQ (STSMON)
|
DS1::SSM-DUS
|
ML1000::GFP-EX-MISMATCH
|
STSMON::ERFI-P-CONN
|
DS1::SSM-FAIL
|
ML1000::GFP-LFD
|
STSMON::ERFI-P-PAYLD
|
DS1::SSM-OFF
|
ML1000::GFP-NO-BUFFERS
|
STSMON::ERFI-P-SRVR
|
DS1::SSM-PRS
|
ML1000::GFP-UP-MISMATCH
|
STSMON::FAILTOSW-PATH
|
DS1::SSM-RES
|
ML1000::TPTFAIL (ML1000, ML100T, ML2)
|
STSMON::FORCED-REQ
|
DS1::SSM-SMC
|
ML100T::AS-CMD
|
STSMON::LOCKOUT-REQ
|
DS1::SSM-ST2
|
ML100T::AS-MT
|
STSMON::LOP-P
|
DS1::SSM-ST3
|
ML100T::CARLOSS (ML100T, ML1000, ML2)
|
STSMON::LPBKCRS
|
DS1::SSM-ST3E
|
ML100T::GFP-CSF
|
STSMON::MAN-REQ
|
DS1::SSM-ST4
|
ML100T::GFP-DE-MISMATCH
|
STSMON::PDI-P
|
DS1::SSM-STU
|
ML100T::GFP-EX-MISMATCH
|
STSMON::PLM-P
|
DS1::SSM-TNC
|
ML100T::GFP-LFD
|
STSMON::RFI-P
|
DS1::SYNC-FREQ
|
ML100T::GFP-NO-BUFFERS
|
STSMON::SD-P
|
DS1::TRMT
|
ML100T::GFP-UP-MISMATCH
|
STSMON::SF-P
|
DS1::TRMT-MISS
|
ML100T::TPTFAIL (ML1000, ML100T, ML2)
|
STSMON::TIM-P
|
DS1::TX-AIS
|
ML2::AS-CMD
|
STSMON::UNEQ-P
|
DS1::TX-RAI
|
ML2::AS-MT
|
STSMON::WKSWPR
|
DS3::AIS
|
ML2::CARLOSS (ML100T, ML1000, ML2)
|
STSMON::WTR
|
DS3::AS-CMD
|
ML2::GFP-CSF
|
STSTRM::AIS-P
|
DS3::AS-MT
|
ML2::GFP-LFD
|
STSTRM::AS-MT-OOG
|
DS3::DS3-MISM
|
ML2::LPBKFACILITY (ML2)
|
STSTRM::AU-LOF
|
DS3::FE-AIS
|
ML2::LPBKTERMINAL (ML2)
|
STSTRM::ENCAP-MISMATCH-P
|
DS3::FE-DS1-MULTLOS
|
ML2::TPTFAIL (ML1000, ML100T, ML2)
|
STSTRM::ERFI-P-CONN
|
DS3::FE-DS1-NSA
|
MSUDC::AIS
|
STSTRM::ERFI-P-PAYLD
|
DS3::FE-DS1-SA
|
MSUDC::LOS (MSUDC)
|
STSTRM::ERFI-P-SRVR
|
DS3::FE-DS1-SNGLLOS
|
NE-SREF::FRCDSWTOINT
|
STSTRM::LCAS-CRC
|
DS3::FE-DS3-NSA
|
NE-SREF::FRCDSWTOPRI
|
STSTRM::LCAS-RX-FAIL
|
DS3::FE-DS3-SA
|
NE-SREF::FRCDSWTOSEC
|
STSTRM::LCAS-TX-ADD
|
DS3::FE-EQPT-NSA
|
NE-SREF::FRCDSWTOTHIRD
|
STSTRM::LCAS-TX-DNU
|
DS3::FE-IDLE
|
NE-SREF::FRNGSYNC
|
STSTRM::LOM
|
DS3::FE-LOF
|
NE-SREF::FSTSYNC
|
STSTRM::LOP-P
|
DS3::FE-LOS
|
NE-SREF::HLDOVRSYNC
|
STSTRM::OOU-TPT
|
DS3::INC-ISD
|
NE-SREF::MANSWTOINT
|
STSTRM::PDI-P
|
DS3::LOF (DS3)
|
NE-SREF::MANSWTOPRI
|
STSTRM::PLM-P
|
DS3::LOS (DS3)
|
NE-SREF::MANSWTOSEC
|
STSTRM::RFI-P
|
DS3::LPBKDS1FEAC
|
NE-SREF::MANSWTOTHIRD
|
STSTRM::SD-P
|
DS3::LPBKDS3FEAC
|
NE-SREF::SSM-PRS
|
STSTRM::SF-P
|
DS3::LPBKDS3FEAC-CMD
|
NE-SREF::SSM-RES
|
STSTRM::SQM
|
DS3::LPBKFACILITY(DS1, DS3)
|
NE-SREF::SSM-SMC
|
STSTRM::TIM-P
|
DS3::LPBKTERMINAL (DS1, DS3)
|
NE-SREF::SSM-ST2
|
STSTRM::UNEQ-P
|
DS3::RAI
|
NE-SREF::SSM-ST3
|
TRUNK::AIS
|
DS3::SD (DS1, DS3)
|
NE-SREF::SSM-ST3E
|
TRUNK::ALS
|
DS3::SF (DS1, DS3)
|
NE-SREF::SSM-ST4
|
TRUNK::AS-CMD
|
E1000F::AS-CMD
|
NE-SREF::SSM-STU
|
TRUNK::AS-MT
|
E1000F::CARLOSS (E100T, E1000F)
|
NE-SREF::SSM-TNC
|
TRUNK::CARLOSS (TRUNK)
|
E100T::AS-CMD
|
NE-SREF::SWTOPRI
|
TRUNK::DSP-COMM-FAIL
|
E100T::CARLOSS (E100T, E1000F)
|
NE-SREF::SWTOSEC
|
TRUNK::DSP-FAIL
|
EC1-12::AIS-L
|
NE-SREF::SWTOTHIRD
|
TRUNK::EOC
|
EC1-12::AS-CMD
|
NE-SREF::SYNCPRI
|
TRUNK::EOC-L
|
EC1-12::AS-MT
|
NE-SREF::SYNCSEC
|
TRUNK::FAILTOSW
|
EC1-12::FE-FRCDWKSWBK-SPAN
|
NE-SREF::SYNCTHIRD
|
TRUNK::FEC-MISM
|
EC1-12::FE-MANWKSWBK-SPAN
|
NE::APC-DISABLED
|
TRUNK::FORCED-REQ-SPAN
|
EC1-12::HELLO
|
NE::APC-END
|
TRUNK::GCC-EOC
|
EC1-12::HI-LASERTEMP
|
NE::AS-CMD
|
TRUNK::GE-OOSYNC
|
EC1-12::LO-LASERTEMP
|
NE::AUD-LOG-LOSS
|
TRUNK::HI-LASERBIAS
|
EC1-12::LOF (EC1-12)
|
NE::AUD-LOG-LOW
|
TRUNK::HI-RXPOWER
|
EC1-12::LOS (EC1-12)
|
NE::DATAFLT
|
TRUNK::HI-TXPOWER
|
EC1-12::LPBKFACILITY (EC1-12)
|
NE::DBOSYNC
|
TRUNK::LO-RXPOWER
|
EC1-12::LPBKTERMINAL (EC1-12)
|
NE::DUP-IPADDR
|
TRUNK::LO-TXPOWER
|
EC1-12::RFI-L
|
NE::DUP-NODENAME
|
TRUNK::LOCKOUT-REQ
|
EC1-12::SD-L
|
NE::ETH-LINKLOSS
|
TRUNK::LOF (TRUNK)
|
EC1-12::SF-L
|
NE::HITEMP
|
TRUNK::LOM
|
EC1-12::SQUELCHED
|
NE::I-HITEMP
|
TRUNK::LOS (TRUNK)
|
EC1-12::TIM-MON
|
NE::INTRUSION-PSWD
|
TRUNK::LOS-P (TRUNK)
|
ENVALRM::EXT
|
NE::LAN-POL-REV
|
TRUNK::LPBKFACILITY (TRUNK)
|
EQPT::AS-CMD
|
NE::OPTNTWMIS
|
TRUNK::LPBKTERMINAL (TRUNK)
|
EQPT::AS-MT
|
NE::SNTP-HOST
|
TRUNK::MANUAL-REQ-SPAN
|
EQPT::AUTORESET
|
NE::SYSBOOT
|
TRUNK::ODUK-AIS-PM
|
EQPT::BKUPMEMP
|
OCH::AS-CMD
|
TRUNK::ODUK-2-AIS-PM
|
EQPT::CARLOSS (EQPT)
|
OCH::AS-MT
|
TRUNK::ODUK-3-AIS-PM
|
EQPT::CLDRESTART
|
OCH::LOS-O
|
TRUNK::ODUK-4-AIS-PM
|
EQPT::COMIOXC
|
OCH::LOS-P (OCH, OMS, OTS)
|
TRUNK::ODUK-BDI-PM
|
EQPT::COMM-FAIL
|
OCH::OPWR-HDEG
|
TRUNK::ODUK-LCK-PM
|
EQPT::CONTBUS-A-18
|
OCH::OPWR-HFAIL
|
TRUNK::ODUK-OCI-PM
|
EQPT::CONTBUS-B-18
|
OCH::OPWR-LDEG
|
TRUNK::ODUK-SD-PM
|
EQPT::CONTBUS-IO-A
|
OCH::OPWR-LFAIL
|
TRUNK::ODUK-SF-PM
|
EQPT::CONTBUS-IO-B
|
OCH::PARAM-MISM
|
TRUNK::ODUK-TIM-PM
|
EQPT::CTNEQPT-MISMATCH
|
OCH::PORT-ADD-PWR-DEG-HI
|
TRUNK::OTUK-AIS
|
EQPT::CTNEQPT-PBPROT
|
OCH::PORT-ADD-PWR-DEG-LOW
|
TRUNK::OTUK-BDI
|
EQPT::CTNEQPT-PBWORK
|
PORT-ADD-PWR-FAIL-HI
|
TRUNK::OTUK-IAE
|
EQPT::EQPT
|
OCH::PORT-ADD-PWR-FAIL-LOW
|
TRUNK::OTUK-LOF
|
EQPT::ERROR-CONFIG
|
OCH::UNREACHABLE-TARGET-POWER
|
TRUNK::OTUK-SD
|
EQPT::EXCCOL
|
OCH::VOA-HDEG
|
TRUNK::OTUK-SD
|
EQPT::FAILTOSW
|
OCH::VOA-HFAIL
|
TRUNK::OTUK-TIM
|
EQPT::FORCED-REQ
|
OCH::VOA-LDEG
|
TRUNK::OUT-OF-SYNC
|
EQPT::HITEMP
|
OCH::VOA-LFAIL
|
TRUNK::PTIM
|
EQPT::IMPROPRMVL
|
OCHNC-CONN::OCHNC-INC
|
TRUNK::RFI
|
EQPT::INHSWPR
|
OCN::AIS-L
|
TRUNK::SD (TRUNK)
|
EQPT::INHSWWKG
|
OCN::ALS
|
TRUNK::SF (TRUNK)
|
EQPT::IOSCFGCOPY
|
OCN::APS-INV-PRIM
|
TRUNK::SIGLOSS
|
EQPT::LOCKOUT-REQ
|
OCN::APS-PRIM-FAC
|
TRUNK::SQUELCHED
|
EQPT::MAN-REQ
|
OCN::APS-PRIM-SEC-MISM
|
TRUNK::SSM-DUS
|
EQPT::MANRESET
|
OCN::APSB
|
TRUNK::SSM-FAIL
|
EQPT::MEA (EQPT)
|
OCN::APSCDFLTK
|
TRUNK::SSM-LNC
|
EQPT::MEM-GONE
|
OCN::APSC-IMP
|
TRUNK::SSM-OFF
|
EQPT::MEM-LOW
|
OCN::APSCINCON
|
TRUNK::SSM-PRC
|
EQPT::NO-CONFIG
|
OCN::APSCM
|
TRUNK::SSM-PRS
|
EQPT::PEER-NORESPONSE
|
OCN::APSCNMIS
|
TRUNK::SSM-RES
|
EQPT::PROTNA
|
OCN::APSIMP
|
TRUNK::SSM-SDN-TN
|
EQPT::PWR-FAIL-A
|
OCN::APSMM
|
TRUNK::SSM-SETS
|
EQPT::PWR-FAIL-B
|
OCN::AS-CMD
|
TRUNK::SSM-SMC
|
EQPT::PWR-FAIL-RET-A
|
OCN::AS-MT
|
TRUNK::SSM-ST2
|
EQPT::PWR-FAIL-RET-B
|
OCN::AUTOLSROFF
|
TRUNK::SSM-ST3
|
EQPT::RUNCFG-SAVENEED
|
OCN::BLSROSYNC
|
TRUNK::SSM-ST3E
|
EQPT::SFTWDOWN
|
OCN::E-W-MISMATCH
|
TRUNK::SSM-ST4
|
EQPT::SWMTXMOD
|
OCN::EOC
|
TRUNK::SSM-STU
|
EQPT::WKSWPR
|
OCN::EOC-L
|
TRUNK::SSM-TNC
|
EQPT::WTR
|
OCN::EXERCISE-RING-FAIL
|
TRUNK::SYNC-FREQ
|
ESCON::ALS
|
OCN::EXERCISE-SPAN-FAIL
|
TRUNK::SYNCLOSS
|
ESCON::AS-CMD
|
OCN::EXTRA-TRAF-PREEMPT
|
TRUNK::TIM
|
ESCON::AS-MT
|
OCN::FAILTOSW
|
TRUNK::TIM-MON
|
ESCON::FAILTOSW
|
OCN::FAILTOSWR
|
TRUNK::UNC-WORD
|
ESCON::FORCED-REQ-SPAN
|
OCN::FAILTOSWS
|
TRUNK::UT-COMM-FAIL
|
ESCON::HI-LASERBIAS
|
OCN::FE-FRCDWKSWBK-SPAN
|
TRUNK::UT-FAIL
|
ESCON::HI-RXPOWER
|
OCN::FE-FRCDWKSWPR-RING
|
TRUNK::WKSWPR
|
ESCON::HI-TXPOWER
|
OCN::FE-FRCDWKSWPR-SPAN
|
TRUNK::WTR
|
ESCON::LO-RXPOWER
|
OCN::FE-LOCKOUTOFPR-SPAN
|
TRUNK::WVL-MISMATCH
|
ESCON::LO-TXPOWER
|
OCN::FE-MANWKSWBK-SPAN
|
UCP-CKT::CKTDOWN
|
ESCON::LOCKOUT-REQ
|
OCN::FE-MANWKSWPR-RING
|
UCP-IPCC::LMP-HELLODOWN
|
ESCON:: LOS (ESCON)
|
OCN::FE-MANWKSWPR-SPAN
|
UCP-IPCC::LMP-NDFAIL
|
ESCON::LPBKFACILITY (ESCON)
|
OCN::FEPRLF
|
UCP-NBR::RSVP-HELLODOWN
|
ESCON::LPBKTERMINAL (ESCON)
|
OCN::FORCED-REQ-RING
|
VCG::LOA
|
ESCON::MANUAL-REQ-SPAN
|
OCN::FORCED-REQ-SPAN
|
VCG::VCG-DEG
|
ESCON::SQUELCHED
|
OCN::FULLPASSTHR-BI
|
VCG::VCG-DOWN
|
ESCON::WKSWPR
|
OCN::HELLO
|
VT-MON::AIS-V
|
ESCON::WTR
|
OCN::HI-LASERBIAS
|
VT-MON::AUTOSW-AIS
|
EXT-SREF::FRCDSWTOPRI
|
OCN::HI-LASERTEMP
|
VT-MON::AUTOSW-LOP (VT-MON)
|
EXT-SREF::FRCDSWTOSEC
|
OCN::HI-RXPOWER
|
VT-MON::AUTOSW-UNEQ (VT-MON)
|
EXT-SREF::FRCDSWTOTHIRD
|
OCN::HI-TXPOWER
|
VT-MON::FAILTOSW-PATH
|
EXT-SREF::MANSWTOPRI
|
OCN::KB-PASSTHR
|
VT-MON::FORCED-REQ
|
EXT-SREF::MANSWTOSEC
|
OCN::KBYTE-APS-CHANNEL-FAILURE
|
VT-MON::LOCKOUT-REQ
|
EXT-SREF::MANSWTOTHIRD
|
OCN::LASEREOL
|
VT-MON::LOP-V
|
EXT-SREF::SWTOPRI
|
OCN::LKOUTPR-S
|
VT-MON::MAN-REQ
|
EXT-SREF::SWTOSEC
|
OCN::LO-LASERTEMP
|
VT-MON::SD-V
|
EXT-SREF::SWTOTHIRD
|
OCN::LO-RXPOWER
|
VT-MON::SF-V
|
EXT-SREF::SYNCPRI
|
OCN::LO-TXPOWER
|
VT-MON::UNEQ-V
|
EXT-SREF::SYNCSEC
|
OCN::LOCKOUT-REQ
|
VT-MON::WKSWPR
|
EXT-SREF::SYNCTHIRD
|
OCN::LOF (OCN)
|
VT-MON::WTR
|
FAN::EQPT-MISS
|
OCN::LOS (OCN)
|
VT-TERM::AIS-V
|
FAN::FAN
|
OCN::LPBKFACILITY (OCN)
|
VT-TERM::AS-MT-OOG
|
FAN::MEA (FAN)
|
OCN::LPBKTERMINAL (OCN)
|
VT-TERM::LCAS-CRC
|
FAN::MFGMEM
|
OCN::MANUAL-REQ-RING
|
VT-TERM::LCAS-RX-FAIL
|
FC::ALS
|
OCN::MANUAL-REQ-SPAN
|
VT-TERM::LCAS-TX-ADD
|
FC::AS-CMD
|
OCN::PRC-DUPID
|
VT-TERM::LCAS-TX-DNU
|
FC::AS-MT
|
OCN::RFI-L
|
VT-TERM::LOM
|
FC::CARLOSS (FC)
|
OCN::RING-ID-MIS
|
VT-TERM::LOP-V
|
FC::FAILTOSW
|
OCN::RING-MISMATCH
|
VT-TERM::OOU-TPT
|
FC::FORCED-REQ-SPAN
|
OCN::RING-SW-EAST
|
VT-TERM::PLM-V
|
FC::GE-OOSYNC
|
OCN::RING-SW-WEST
|
VT-TERM::RFI-V
|
FC::HI-LASERBIAS
|
OCN::SD-L
|
VT-TERM::SD-P
|
FC::HI-RXPOWER
|
OCN::SF-L
|
VT-TERM::SF-P
|
FC::HI-TXPOWER
|
OCN::SPAN-SW-EAST
|
VT-TERM::SQM
|
FC::LO-RXPOWER
|
OCN::SPAN-SW-WEST
|
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.
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 (LOS). 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.)
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):
•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.
•Not Alarmed (NA) conditions are information indicators, such as for state (FRNGSYNC) or an event (FRCSWTOPRI). They might or might not require troubleshooting, as indicated in the entries.
•Not Reported (NR) conditions occur as a secondary result of another event. For example, the alarm indication signal (AIS), with severity NR, is inserted by a downstream node when an LOS (CR or MJ) alarm occurs upstream. These conditions do not in themselves require troubleshooting, but are to be expected in the presence of primary alarms.
All alarm, condition, and not-reported 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, 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.
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) columns 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 warnings.
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 (IS-NR) for the laser to be on. The laser is off when the safety key is off (labeled 0).
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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
Warning Class 1 laser product.
Warning Class 1M laser radiation when open. Do not view directly with optical instruments.
2.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 DWDM Installation and Operations Guide.
Note When checking alarms, ensure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
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 tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you 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-142, or out-of-service (OOS,MT or OOS,DSBLD) ports.
Step 2 Clear the upstream alarms using the applicable procedures in this chapter.
Step 3 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).
2.8.2 AIS-L
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: 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 tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-L Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).
2.8.3 AIS-P
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
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 tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-P Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).
2.8.4 AIS-V
•Default Severity: Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: VT-MON, VT-TERM
The AIS Virtual Tributary (VT) condition means that this node is detecting AIS in the incoming VT-level path.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
See the "1.8.2 AIS-V on DS3XM-6 Unused VT Circuits" section on page 1-59 for more information.
Clear the AIS-V Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call TAC (1 800 553-2447).
2.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 an 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
The AMPLI-INIT condition is not used in this platform in this release. It is reserved for future development.
2.8.7 APC-CORRECTION-SKIPPED
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: AOTS, 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 dB 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 dB, APC corrects the level. If the actual power level exceeds the threshold by +3 dB or -3 dB, 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.
Note APC-CORRECTION-SKIPPED is an informational condition and does not require troubleshooting.
2.8.8 APC-DISABLED
•Default Severity: Major (MJ), 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-72, the "IMPROPRMVL" alarm on page 2-115, or the "MEA (EQPT)" alarm on page 2-166. If the alarm occurs with the creation of the first circuit, delete and recreate it.
Clear the APC-DISABLED Alarm
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.
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, OMS, OTS
The APC Out of Range condition is raised on 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.
Clear the APC-OUT-OF-RANGE Condition
Step 1 Provision the correct setpoint. For instructions, refer to the "Turn Up a Node" chapter in the Cisco ONS 15454 DWDM Installation and Operations Guide. The condition clears when the APC setting is corrected, and 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 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 causes 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 alarm troubleshooting 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-43.
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-77.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 DWDM Installation and Operations Guide 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 protection 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 SDCC 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 bad or invalid K bytes. The APSC-IMP alarm occurs on OC-N cards in a BLSR configuration and can occur during BLSR configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located on the lower-right edge of the shelf assembly.
Note This alarm can occur on a virtual tributary (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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal. For specific procedures to use the test set equipment, consult the manufacturer.
If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454. 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 the ring name of that node 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 system, 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-142, the "LOF (OCN)" alarm on page 2-132, or the "AIS" alarm 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 protection channel. In many cases, the working and protection 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 (IS-NR) for the laser to be on. The laser is off when the safety key is off (labeled 0).
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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
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.
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.
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 SONET K2 byte of the incoming APS channel 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: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
The APS Invalid Code 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 proper type of 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 far end is not configured for 1+1 protection, create the group. For instructions, refer to the Cisco ONS 15454 DWDM Installation and Operations Guide.
Step 2 If the other end of the group is properly configured or the alarm does not clear after you have provisioned the group correctly, verify that the working ports and protect ports are cabled correctly.
Step 3 Ensure that both protect ports are configured for SONET.
Step 4 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.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 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 DCC connectivity) to the far end.
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 far-end node and verify that the OC-N 1+1 protection group is provisioned.
Step 4 Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in 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 match between the primary section of the near end facility and the primary section of the far-end facility.
Clear the APS-PRIM-SEC-MISM Alarm
Step 1 Ensure that the near end and far-end ports are correctly provisioned with the same way. For more information about optimized 1+1 configurations, refer to the Cisco ONS 15454 Procedure Guide.
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, DS1, DS3, E1000F, E100T, EC1-12, EQPT, ESCON, FC, ML2, 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. Suppressing alarms on a card also suppresses alarms on its ports.
Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.
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, deselect the Suppress Alarms column check box.
c. Click Apply.
Step 8 If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm:
a. In node view, click the Provisioning > Alarm 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 TAC (1 800 553-2447).
2.8.23 AS-MT
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: 2R, AOTS, DS1, DS3, EC1-12, EQPT, ESCON, FC, FCMR, G1000, GE, ISC, ML1000, ML100T, ML2, OCH, OCN, OMS, OTS, PPM, 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.
Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.
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: Critical (CR), Service-Affecting (SA) if all VCAT members on an STS are placed OOS; Major (MJ), Service-Affecting (SA) for a single VT
•Logical Object: VT-TERM
The Alarms Suppressed on an Out-Of-Group VCAT Member alarm is raised on an STS or VT member of a VCAT group whenever the member is in the IDLE (AS-MT-OOG) admin state. This alarm can be raised when a member is initially added to a group. In IDLE (AS-MT-OOG) state, all other alarms for the STS or VT are suppressed.
Clear the AS-MT-OOG Alarm
Step 1 The AS-MT-OOG alarm clears when an STS or VT member transitions to a different state from IDLE (AS-MT-OOG) or when it is removed completely from the VCAT group. It does not require troubleshooting unless it does not clear.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447).
2.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 will be saved in this file. New entries will continue with the next number in the sequence, rather than starting over.
Step 7 If the 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 used in this platform in this 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 (IS-NR) for the laser to be on. The laser is off when the safety key is off (labeled 0).
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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
Clear the AUTOLSROFF Alarm
Step 1 View the temperature displayed on the ONS 15454 LCD front panel (Figure 2-2).
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.
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.
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.
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 tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The AIS condition is raised by the receiving node on each input when it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS 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-134. 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: Minor (MN), Service-Affecting (SA)
•Logical Object: VT-MON
The AUTOSW-LOP alarm for the virtual tributary monitor (VT-MON) indicates that automatic path protection switching occurred because of the "LOP-V" alarm on page 2-135. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-LOP (VT-MON) Alarm
Step 1 Complete the "Clear the LOP-V Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.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-186. 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 USPR 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: Minor (MN), Service-Affecting (SA)
•Logical Object: VT-MON
AUTOSW-UNEQ (VT-MON) indicates that the "UNEQ-V" alarm on page 2-231 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) Alarm
Step 1 Complete the "Clear the UNEQ-V Alarm" procedure.
Step 2 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.38 AWG-DEG
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OTS
The Arrayed Waveguide Gratings (AWG) Degrade alarm occurs when an 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 an 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 raising 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 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) in order to report a service-affecting problem.
2.8.43 BKUPMEMP
•Default Severity: Critical (CR), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2 card flash memory. The alarm occurs when the TCC2 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.
The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-72. 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 can take up to 30 minutes.
Clear the BKUPMEMP Alarm
Step 1 Verify that both TCC2 cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2 cards.
Step 2 If both cards are powered and enabled, reset the active TCC2 to make the standby TCC2 active. Complete the "Reset an Active TCC2 and Activate the Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2 LED should be green.
Step 3 If the TCC2 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 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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
Clear the BLSROSYNC Alarm
Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the Cisco ONS 15454 DWDM Installation and Operations Guide for cabling information.
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
The BPV alarm is not used in this release.
2.8.46 CARLOSS (E100T, E1000F)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Objects: E1000F, E100T
A Carrier Loss alarm on the LAN E-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-142. 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).
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.
Clear the CARLOSS (E100T, E1000F) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port.
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.
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.
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.
If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm could be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:
a. Right-click anywhere 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.
•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.
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.47 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, 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.
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. Use of controls or adjustments or performance of procedures other than those specified could result in hazardous radiation exposure.
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.
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.
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.
Step 5 Verify that the optical LAN cable is properly connected and attached to the correct port.
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.
Step 7 If you are unable to establish connectivity, replace the fiber cable with a new known-good 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.
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.48 CARLOSS (FC)
The Carrier Loss alarm for Fibre Channel is not used in this release. It is reserved for future development.
2.8.49 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-142. 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 far-end 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 far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, other alarms such as the "TPTFAIL (G1000)" alarm on page 2-225 or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G1000s) alarm.
Refer to the 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-227 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.
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.
Clear the CARLOSS (G1000) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port.
Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device and is not misconnected to an 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 "1.9.3 OC-N Card Transmit and Receive Levels" section on page 1-71.
Step 5 If the alarm does not clear, use an Ethernet test set to determine that a valid signal is coming into the Ethernet port. For specific procedures to use the test set equipment, consult the manufacturer.
Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port.
Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the 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-225 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 13.
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.
•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 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.50 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 DWDM Installation and Operations Guide for provisioning instructions.
d. If a PPM has been created, view the contents of the Selected PPM area Rate column 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 will also be 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.51 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.52 CARLOSS (ML100T, ML1000, ML2)
•Default Severity: Major (MJ), Service-Affecting (SA)
•Logical Objects:ML1000, ML100T, ML2
A Carrier Loss alarm on an ML-Series Ethernet card is the data equivalent of the "LOS (OCN)" alarm on page 2-142. 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 items also occurs:
•The cable is not properly connected to the near or far port.
•Auto-negotiation is failing.
•The speed (10/100 ports only) is set incorrectly.
For information about provisioning ML-Series Ethernet cards from the Cisco IOS interface, refer to the Ethernet Card Software Feature and Configuration Guide for the Cisco ONS 15454, Cisco ONS 15454 SDH, and Cisco ONS 15327.
Note The ML2 object is currently used only in the ONS 15310 platform and is reserved for future development in the ONS 15454 platform.
Clear the CARLOSS (ML100T, ML1000, ML2) Alarm
Step 1 Verify that the LAN cable is properly connected and attached to the correct port on the ML-Series card and on the peer Ethernet port.
Step 2 If the alarm does not clear, verify that autonegotiation is set properly on the ML-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 will restart.
Step 6 If the alarm does not clear, complete the "Create the Facility (Line) Loopback on the Source-Node MXP or TXP Port" procedure on page 1-7 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.53 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.54 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-86 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.55 CKTDOWN
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: UCP-CKT
The unified control plane (UCP) Circuit Down alarm applies to logical circuits created within the UCP between devices. It occurs when there is signaling failure across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 because it is an edge device.
Clear the CKTDOWN Alarm
Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:
a. In node view, click the Provisioning > UCP > Neighbor tabs.
b. View the entries to find out whether the node you are trying to contact is listed.
The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that it is physically and logically accessible.
c. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.
d. At the command prompt (C:\>), type:
ping {node-DNS-name | node-IP-address}
If you typed the domain name services (DNS) name and the ping was successful, you will see:
pinging node-dns-name.domain-name.com. node-IP-address with 32 bytes of data:
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Reply from IP-address: bytes=32 time=10ms TTL=60
Ping statistics for IP-address:
Packets sent = 4 Received = 4 Lost = 0 (0% lost),
Approximate round trip time in milli-seconds:
Minimum = minimum-ms, Maximum = maximum-ms, Average = average-ms
If you typed the IP address and the ping command is successful, the result will look similar but will not include the DNS name in the first line.
e. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.
f. If the ping was unsuccessful, you will receive the following reply for each try:
A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.
Step 2 If the neighbor has not been provisioned, or if you had to delete the neighbor, create one:
a. In the Provisioning > UCP > Neighbor tabs, click the Create button.
b. In the Neighbor Discovery window, enter the node DNS node name in the Neighbor Name field. Leave the Enable Discovery check box checked (default setting) if you want the neighbor to be discovered through the network.
c. Click OK.
The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If it is not successful, the column lists 0.0.0.0.
Step 3 If neighbor discovery is enabled, ensure that the neighbor node ID and remote IP control channel (IPCC) have been discovered correctly.
Step 4 Click the Provisioning > UCP > IPCC tabs and view the IPCC listing. If the IPCC has been created correctly, the Remote IP column contains the neighbor IP address.
Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.
a. Click the entry to select the neighbor IP address and click Delete.
b. If you get an error that will not allow you to delete the IPCC, you must delete the neighbor and recreate it. Click the Neighbor tab.
c. Click to select the neighbor and click Delete.
d. Go back to Step 2 to recreate the neighbor.
Step 6 If remote IPCC has not been discovered, or if it had to be deleted, create the connection:
a. In the Provisioning > UCP > IPCC tabs, click Create.
b. In the Unified Control Plane Provisioning window, click Next.
c. If no IPCCs are listed, click Create.
d. In the Create New IPCC window, click the DCC termination corresponding to the core network interface.
Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.
e. Click OK. The IPCC is listed in the Unified Control Plane Provisioning window.
f. Click the neighbor to select it, and click Next.
g. Choose the UCP interface [for example, Slot 5 (OC-48), port 1] where the core network is connected from the drop-down list. The field default is the node where you are logged in.
h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.
i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab will contain the neighbor IP address.
Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:
a. Click the Interface tab. View the slot and port listed in the Interface column [for example, Slot 5 (OC48), port 1].
b. Compare the listed interface listed with the IPCC tab SDCC column entry.
Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.
Step 9 Click Next.
Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.
The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.
Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.
Step 12 If the alarm does not clear, log into 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.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.
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.
Clear the CLDRESTART Condition
Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure.
Step 2 If the condition fails to clear after the card reboots, complete the "Remove and Reinsert (Reseat) Any Card" procedure.
Step 3 If the condition does not clear, complete the "Physically Replace a 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 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 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: Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2 slot to TCC2 slot occurs when the main processor on the TCC2 in the first slot ("TCC A") loses communication with the coprocessor on the same card. This applies to the Slot 7 TCC2.
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.
Clear the CONTBUS-A-18 Alarm
Step 1 Complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure to make the Slot 11 TCC2 active.
Step 2 Wait approximately 10 minutes for the Slot 7 TCC2 to reset as the standby TCC2. 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 and complete the "Reset an Active TCC2 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 TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Reset an Active TCC2 and Activate the Standby Card" procedure. If the 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: Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from Controller Slot to Controller Slot alarm for the TCC2 slot to TCC2 slot occurs when the main processor on the TCC2 in the second slot ("TCC B") loses communication with the coprocessor on the same card. This applies to the Slot 11 TCC2.
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.
Clear the CONTBUS-B-18 Alarm
Step 1 Complete the "Reset an Active TCC2 and Activate the Standby Card" procedure to make the Slot 7 TCC2 active.
Step 2 Wait approximately 10 minutes for the Slot 11 TCC2 to reset as the standby TCC2. 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 and complete the "Reset an Active TCC2 and Activate the Standby Card" procedure to return the Slot 11 TCC2 card to the active state.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Traffic Card" procedure.
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 (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. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2, the other card, and the backplane.
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.
Clear the CONTBUS-IO-A Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm on page 2-166 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby Slot 11 TCC2, 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, 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 will remain standby.)
If CONTBUS-IO-A is raised on several cards at the same time, complete the "Reset an Active TCC2 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.
Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1 800 553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure. If the 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 (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. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the newly active TCC2. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2, the other card, and the backplane.
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.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (EQPT)" alarm on page 2-166 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby Slot 7 TCC2, 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, 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-A is raised on several cards at the same time, complete the "Reset an Active TCC2 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.
Step 7 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1 800 553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure. If the 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, an XC card may be preprovisioned in Slot 10, but an XCVT may be physically installed.
The alarm is raised against a card that is mismatched with the card. For example, CTNEQPT-MISMATCH is raised in the following situations:
•An XC card is replaced with an XCVT or XC10G card.
•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. (For example, you might have an XC in Slot 8 and an XC10G in Slot 10 while you are upgrading Slot 10.)
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 R4.6 and replace an XC with XCVT or XC10G, or an XCVT with an XC10G, the CTNEQPT-MISMATCH condition is raised but it will be 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 DWDM Installation and Operations Guide.
Clear the CTNEQPT-MISMATCH Condition
Step 1 Verify what 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 into the Technical Support Website at 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 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 can take up to 30 minutes.
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.
Clear the CTNEQPT-PBPROT Alarm
Step 1 If all traffic cards show CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure for the standby TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the standby TCC2. Do not physically reseat an active TCC2. 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 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 OC-192 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 status 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 and the backplane.
Note This alarm automatically raises and clears when the ONS 15454 Slot 10 XC10G cross-connect card is reseated.
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.
Clear the CTNEQPT-PBWORK Alarm
Step 1 If all traffic cards show CTNEEQPT-PBWORK alarm, complete the "Reset an Active TCC2 and Activate the Standby Card" procedure for the active TCC2 and then complete the "Remove and Reinsert (Reseat) the Standby TCC2 Card" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Traffic Card" procedure for the TCC2 card. Do not physically reseat an active TCC2 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 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 CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) Any Card" procedure for the reporting card.
Step 10 If you switched traffic, complete the "Initiate a 1:1 Card Switch Command" procedure to switch it back.
Step 11 If the alarm does not clear, 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 12 If the alarm does not clear, complete the "Physically Replace a Traffic Card" procedure for the reporting traffic card.
Step 13 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1 800 553-2447) in order to report a service-affecting problem.
2.8.66 DATAFLT
•
