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 Logical Object Type Definitions
2.4 Alarm Index by Logical Object Type
2.5 Trouble Notifications
2.5.1 Conditions
2.5.2 Severities
2.6 Safety Summary
2.7 Alarm Procedures
2.7.1 AIS
Clear the AIS Condition
2.7.2 AIS-L
2.7.3 ALS
2.7.4 AMPLI-INIT
Clear the AMPLI-INIT Condition
2.7.5 APC-DISABLED
Clear the APC-DISABLED Alarm
2.7.6 APC-FAIL
Clear the APC-FAIL Alarm
2.7.7 APSB
Clear the APSB Alarm
2.7.8 APSCDFLTK
Clear the APSCDFLTK Alarm
2.7.9 APSC-IMP
Clear the APSC-IMP Alarm
2.7.10 APSCINCON
Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing
2.7.11 APSCM
Clear the APSCM Alarm
2.7.12 APSCNMIS
Clear the APSCNMIS Alarm
2.7.13 APSIMP
Clear the APSIMP Condition
2.7.14 AS-CMD
Clear the AS-CMD Condition
2.7.15 AS-MT
Clear the AS-MT Condition
2.7.16 AU-AIS
Clear the AU-AIS Condition
2.7.17 AUD-LOG-LOSS
Clear the AUD-LOG-LOSS Condition
2.7.18 AUD-LOG-LOW
2.7.19 AU-LOF
Clear the AU-LOF Alarm
2.7.20 AU-LOP
Clear the AU-LOP Alarm
2.7.21 AUTOLSROFF
Clear the AUTOLSROFF Alarm
2.7.22 AUTORESET
Clear the AUTORESET Alarm
2.7.23 AUTOSW-AIS-SNCP
Clear the AUTOSW-AIS-SNCP Condition
2.7.24 AUTOSW-LOP-SNCP
Clear the AUTOSW-LOP-SNCP Alarm
2.7.25 AUTOSW-PDI-SNCP
Clear the AUTOSW-PDI-SNCP Condition
2.7.26 AUTOSW-SDBER-SNCP
Clear the AUTOSW-SDBER-SNCP Condition
2.7.27 AUTOSW-SFBER-SNCP
Clear the AUTOSW-SFBER-SNCP Condition
2.7.28 AUTOSW-UNEQ-SNCP (HPMon)
Clear the AUTOSW-UNEQ-SNCP (HPMon) Condition
2.7.29 AUTOSW-UNEQ-SNCP (LPMon)
Clear the AUTOSW-UNEQ-SNCP (LPMon) Alarm
2.7.30 AWG-DEG
Clear the AWG-DEG Alarm
2.7.31 AWG-FAIL
Clear the AWG-FAIL Alarm
2.7.32 AWG-OVERTEMP
Clear the AWG-OVERTEMP Alarm
2.7.33 AWG-WARM-UP
2.7.34 BATFAIL
Clear the BATFAIL Alarm
2.7.35 BKUPMEMP
Clear the BKUPMEMP Alarm
2.7.36 CARLOSS (DWDM Client)
Clear the CARLOSS (DWDM Client) Alarm
2.7.37 CARLOSS (DWDM Trunk)
Clear the CARLOSS (DWDM Trunk) Alarm
2.7.38 CARLOSS (EQPT)
Clear the CARLOSS (EQPT) Alarm
2.7.39 CARLOSS (E-Series Ethernet)
Clear the CARLOSS (E-Series Ethernet) Alarm
2.7.40 CARLOSS (G-Series Ethernet)
Clear the CARLOSS (G-Series Ethernet) Alarm
2.7.41 CARLOSS (ML-Series Ethernet)
Clear the CARLOSS (ML-Series Ethernet) Alarm
2.7.42 CASETEMP-DEG
Clear the CASETEMP-DEG Alarm
2.7.43 CKTDOWN
Clear the CKTDOWN Alarm
2.7.44 CLDRESTART
Clear the CLDRESTART Condition
2.7.45 COMIOXC
Clear the COMIOXC Alarm
2.7.46 COMM-FAIL
Clear the COMM-FAIL Alarm
2.7.47 CONTBUS-A-18
Clear the CONTBUS-A-18 Alarm
2.7.48 CONTBUS-B-18
Clear the CONTBUS-B-18 Alarm on the TCC2 Card
2.7.49 CONTBUS-IO-A
Clear the CONTBUS-IO-A Alarm
2.7.50 CONTBUS-IO-B
Clear the CONTBUS-IO-B Alarm
2.7.51 CTNEQPT-MISMATCH
Clear the CTNEQPT-MISMATCH Condition
2.7.52 CTNEQPT-PBPROT
Clear the CTNEQPT-PBPROT Alarm
2.7.53 CTNEQPT-PBWORK
Clear the CTNEQPT-PBWORK Alarm
2.7.54 DATAFLT
Clear the DATAFLT Alarm
2.7.55 DBOSYNC
Clear the DBOSYNC Alarm
2.7.56 DSP-COMM-FAIL
2.7.57 DSP-FAIL
Clear the DSP-FAIL Alarm
2.7.58 DS3-MISM
Clear the DS3-MISM Condition
2.7.59 DUP-IPADDR
Clear the DUP-IPADDR Alarm
2.7.60 DUP-NODENAME
Clear the DUP-NODENAME Alarm
2.7.61 EHIBATVG
Clear the EHIBATVG Alarm
2.7.62 ELWBATVG
Clear the ELWBATVG Alarm
2.7.63 EOC
Clear the EOC Alarm
2.7.64 EOC-L
2.7.65 EQPT
Clear the EQPT Alarm
2.7.66 EQPT-MISS
Clear the EQPT-MISS Alarm
2.7.67 ERROR-CONFIG
Clear the ERROR-CONFIG Alarm
2.7.68 ETH-LINKLOSS
Clear the ETH-LINKLOSS Condition
2.7.69 E-W-MISMATCH
Clear the E-W-MISMATCH Alarm with a Physical Switch
Clear the E-W-MISMATCH Alarm in CTC
2.7.70 EXCCOL
Clear the EXCCOL Alarm
2.7.71 EXERCISE-RING-FAIL
Clear the EXERCISE-RING-FAIL Condition
2.7.72 EXERCISE-SPAN-FAIL
Clear the EXERCISE-SPAN-FAIL Condition
2.7.73 EXT
Clear the EXT Alarm
2.7.74 EXTRA-TRAF-PREEMPT
Clear the EXTRA-TRAF-PREEMPT Alarm
2.7.75 E3-ISD
2.7.76 FAILTOSW
Clear the FAILTOSW Condition
2.7.77 FAILTOSW-HO
Clear the FAILTOSW-HO Condition
2.7.78 FAILTOSW-LO
Clear the FAILTOSW-LO Condition
2.7.79 FAILTOSWR
Clear the FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration
2.7.80 FAILTOSWS
Clear the FAILTOSWS Condition
2.7.81 FAN
Clear the FAN Alarm
2.7.82 FANDEGRADE
Clear the FANDEGRADE Alarm
2.7.83 FE-AIS
Clear the FE-AIS Condition
2.7.84 FE-DS1-MULTLOS
2.7.85 FE-DS1-NSA
2.7.86 FE-DS1-SA
2.7.87 FE-DS1-SNGLLOS
2.7.88 FE-DS3-NSA
2.7.89 FE-DS3-SA
2.7.90 FEC-MISM
Clear the FEC-MISM Alarm
2.7.91 FE-EQPT-NSA
Clear the FE-EQPT-NSA Condition
2.7.92 FE-E1-MULTLOS
Clear the FE-E1-MULTLOS Condition
2.7.93 FE-E1-NSA
Clear the FE-E1-NSA Condition
2.7.94 FE-E1-SA
Clear the FE-E1-SA Condition
2.7.95 FE-E1-SNGLLOS
Clear the FE-E1-SNGLLOS Condition
2.7.96 FE-E3-NSA
Clear the FE-E3-NSA Condition
2.7.97 FE-E3-SA
Clear the FE-E3-SA Condition
2.7.98 FE-FRCDWKSWPR-RING
Clear the FE-FRCDWKSWPR-RING Condition
2.7.99 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-SPAN Condition
2.7.100 FE-IDLE
Clear the FE-IDLE Condition
2.7.101 FE-LOCKOUTOFPR-ALL
2.7.102 FE-LOCKOUTOFPR-RING
2.7.103 FE-LOCKOUTOFPR-SPAN
Clear the FE-LOCKOUTOFPR-SPAN Condition
2.7.104 FE-LOCKOUTOFWK-RING
2.7.105 FE-LOCKOUTOFWK-SPAN
2.7.106 FE-LOF
Clear the FE-LOF Condition
2.7.107 FE-LOS
Clear the FE-LOS Condition
2.7.108 FE-MANWKSWPR-RING
Clear the FE-MANWKSWPR-RING Condition
2.7.109 FE-MANWKSWPR-SPAN
Clear the FE-MANWKSWPR-SPAN Condition
2.7.110 FEPRLF
Clear the FEPRLF Alarm on an MS-SPRing
2.7.111 FE-SDPRLF
Clear the FE-SDPRLF Alarm on an MS-SPRing
2.7.112 FIBERTEMP-DEG
Clear the FIBERTEMP-DEG Alarm
2.7.113 FORCED-REQ
Clear the FORCED-REQ Condition
2.7.114 FORCED-REQ-RING
Clear the FORCED-REQ-RING Condition
2.7.115 FORCED-REQ-SPAN
Clear the FORCED-REQ-SPAN Condition
2.7.116 FRCDSWTOINT
2.7.117 FRCDSWTOPRI
2.7.118 FRCDSWTOSEC
2.7.119 FRCDSWTOTHIRD
2.7.120 FRNGSYNC
Clear the FRNGSYNC Condition
2.7.121 FSTSYNC
2.7.122 FULLPASSTHR-BI
Clear the FULLPASSTHR-BI Condition
2.7.123 GAIN-HDEG
Clear the GAIN-HDEG Alarm
2.7.124 GAIN-HFAIL
Clear the GAIN-HFAIL Alarm
2.7.125 GAIN-LDEG
Clear the GAIN-LDEG Alarm
2.7.126 GAIN-LFAIL
Clear the GAIN-LFAIL Alarm
2.7.127 GCC-EOC
Clear the GCC-EOC Alarm
2.7.128 GE-OOSYNC
Clear the GE-OOSYNC Alarm
2.7.129 HIBATVG
Clear the HIBATVG Alarm
2.7.130 HI-LASERBIAS
Clear the HI-LASERBIAS Alarm
2.7.131 HI-RXPOWER
Clear the HI-RXPOWER Alarm
2.7.132 HITEMP
Clear the HITEMP Alarm
2.7.133 HI-TXPOWER
Clear the HI-TXPOWER Alarm
2.7.134 HLDOVRSYNC
Clear the HLDOVRSYNC Alarm
2.7.135 HP-RFI
Clear the HP-RFI Condition
2.7.136 HP-TIM
Clear the HP-TIM Alarm
2.7.137 HP-UNEQ
Clear the HP-UNEQ Alarm
2.7.138 I-HITEMP
Clear the I-HITEMP Alarm
2.7.139 IMPROPRMVL
Clear the IMPROPRMVL Alarm
2.7.140 INC-GFP-OUTOFFRAME
Clear the INC-GFP-OUTOFFRAME Condition
2.7.141 INC-GFP-SIGLOSS
Clear the INC-GFP-SIGLOSS Condition
2.7.142 INC-GFP-SYNCLOSS
Clear the INC-GFP-SYNCLOSS Condition
2.7.143 INC-ISD
2.7.144 INC-SIGLOSS
Clear the INC-SIGLOSS Alarm
2.7.145 INC-SYNCLOSS
Clear the INC-SYNCLOSS Alarm
2.7.146 INHSWPR
Clear the INHSWPR Condition
2.7.147 INHSWWKG
Clear the INHSWWKG Condition
2.7.148 INTRUSION-PSWD
Clear the INTRUSION-PSWD Condition
2.7.149 INVMACADR
2.7.150 IOSCFGCOPY
2.7.151 KB-PASSTHR
Clear the KB-PASSTHR Condition
2.7.152 KBYTE-APS-CHANNEL-FAILURE
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
2.7.153 LAN-POL-REV
Clear the LAN-POL-REV Condition
2.7.154 LASER-APR
2.7.155 LASERBIAS-DEG
Clear the LASERBIAS-DEG Alarm
2.7.156 LASERBIAS-FAIL
Clear the LASERBIAS-FAIL Alarm
2.7.157 LASEREOL
Clear the LASEREOL Alarm
2.7.158 LASERTEMP-DEG
Clear the LASERTEMP-DEG Alarm
2.7.159 LKOUTPR-R
2.7.160 LKOUTPR-S
Clear the LKOUTPR-S Condition
2.7.161 LKOUTWK-R
2.7.162 LKOUTWK-S (NA)
2.7.163 LMP-HELLODOWN
Clear the LMP-HELLODOWN Alarm
2.7.164 LMP-NDFAIL
Clear the LMP-NDFAIL Alarm
2.7.165 LOA
Clear the LOA Alarm
2.7.166 LOC
Clear the LOC Alarm
2.7.167 LOCKOUTOFPR
2.7.168 LOCKOUT-REQ
Clear the LOCKOUT-REQ Condition
2.7.169 LOCKOUT-REQ-RING
2.7.170 LOF (BITS)
Clear the LOF (BITS) Alarm
2.7.171 LOF (DS-3, E-1, E-4, STM-N, STM1-E)
Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm
2.7.172 LOF (DWDM Client)
Clear the LOF (DWDM Client) Alarm
2.7.173 LOF (DWDM Trunk)
Clear the LOF (DWDM Trunk) Alarm
2.7.174 LOM
Clear the LOM Alarm
2.7.175 LO-RXPOWER
Clear the LO-RXPOWER Alarm
2.7.176 LOS (BITS)
Clear the LOS (BITS) Alarm
2.7.177 LOS (DS-3, E-1, E-3, STM-N, STM-1E)
Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm
2.7.178 LOS (DWDM Client)
Clear the LOS (DWDM Client) Alarm
2.7.179 LOS (FUDC)
Clear the LOS (FUDC) Alarm
2.7.180 LOS (OTN)
Clear the LOS (OTN) Alarm
2.7.181 LOS-P (TRUNK)
2.7.182 LO-TXPOWER
Clear the LO-TXPOWER Alarm
2.7.183 LPBKCRS
Clear the LBKCRS Condition
2.7.184 LPBKDS1FEAC
2.7.185 LPBKDS1FEAC-CMD
2.7.186 LPBKDS3FEAC
Clear the LPBKDS3FEAC Condition
2.7.187 LPBKDS3FEAC-CMD
2.7.188 LPBKE1FEAC
2.7.189 LPBKE3FEAC
2.7.190 LPBKE3FEAC-CMD
2.7.191 LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
Clear the LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E) Condition
2.7.192 LPBKFACILITY (DWDM Client)
2.7.193 LPBKFACILITY (G-Series)
Clear the LPBKFACILITY (G-Series) Condition
2.7.194 LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
Clear the LPBKTERMINAL (DS-3, D-1, E-3, E-4, STM-N, STM-1E) Condition
2.7.195 LPBKTERMINAL (DWDM)
2.7.196 LPBKTERMINAL(G-Series Ethernet)
Clear the LPBKTERMINAL (G-Series) Condition
2.7.197 LP-PLM
Clear the LP-PLM Alarm
2.7.198 LP-RFI
Clear the LP-RFI Condition
2.7.199 LP-TIM
Clear the LP-TIM Alarm
2.7.200 LP-UNEQ
Clear the LP-UNEQ Alarm
2.7.201 LWBATVG
Clear the LWBATVG Alarm
2.7.202 MAN-REQ
Clear the MAN-REQ Condition
2.7.203 MANRESET
2.7.204 MANSWTOINT
2.7.205 MANSWTOPRI
2.7.206 MANSWTOSEC
2.7.207 MANSWTOTHIRD
2.7.208 MANUAL-REQ-RING
Clear the MANUAL-REQ-RING Condition
2.7.209 MANUAL-REQ-SPAN
Clear the MANUAL-REQ-SPAN Condition
2.7.210 MEA (BP)
Clear the MEA (BP) Alarm
2.7.211 MEA (EQPT)
Clear the MEA (EQPT) Alarm
2.7.212 MEA (FAN)
Clear the MEA (FAN) Alarm
2.7.213 MEM-GONE
2.7.214 MEM-LOW
2.7.215 MFGMEM (AEP, AIE)
Clear the MFGMEM Alarm
2.7.216 MFGMEM (Backplane or Fan-Tray Assembly)
Clear the MFGMEM Alarm on the Backplane or Fan-Tray Assembly
2.7.217 MS-AIS
Clear the MS-AIS Condition
2.7.218 MS-EOC
Clear the MS-EOC Alarm
2.7.219 MS-RFI
Clear the MS-RFI Condition
2.7.220 MSSP-OOSYNC
Clear the MSSP-OOSYNC Alarm
2.7.221 NO-CONFIG
Clear the NO-CONFIG Alarm
2.7.222 NOT-AUTHENTICATED
2.7.223 NTWTPINC
2.7.224 OCHNC-ACTIV-FAIL
2.7.225 OCHNC-DEACTIV-FAIL
2.7.226 OCHNC-FAIL
2.7.227 OCHNC-INC
2.7.228 ODUK-AIS-PM
Clear the ODUK-AIS-PM Condition
2.7.229 ODUK-BDI-PM
Clear the ODUK-BDI-PM Condition
2.7.230 ODUK-LCK-PM
Clear the ODUK-LCK-PM Condition
2.7.231 ODUK-OCI-PM
Clear the ODUK-OCI-PM Condition
2.7.232 ODUK-SD-PM
Clear the ODUK-SD-PM Condition
2.7.233 ODUK-SF-PM
Clear the ODUK-SF-PM Condition
2.7.234 ODUK-TIM-PM
Clear the ODUK-TIM-PM Condition
2.7.235 OOU-TPT
Clear the OOT-TPT Condition
2.7.236 OPTNTWMIS
Clear the OPTNTWMIS Alarm
2.7.237 OPWR-HDEG
Clear the OPWR-HDEG Alarm
2.7.238 OPWR-HFAIL
Clear the OPWR-HFAIL Alarm
2.7.239 OPWR-LDEG
Clear the OPWR-LDEG Alarm
2.7.240 OPWR-LFAIL
Clear the OPWR-LFAIL Alarm
2.7.241 OTUK-AIS
Clear the OTUK-AIS Condition
2.7.242 OTUK-BDI
Clear the OTUK-BDI Condition
2.7.243 OTUK-LOF
Clear the OTUK-LOF Alarm
2.7.244 OTUK-SD
Clear the OTUK-SD Condition
2.7.245 OTUK-SF
Clear the OTUK-SF Condition
2.7.246 OTUK-TIM
Clear the OTUK-TIM Alarm
2.7.247 OUT-OF-SYNC
Clear the OUT-OF-SYNC Condition
2.7.248 PEER-NORESPONSE
Clear the PEER-NORESPONSE Alarm
2.7.249 PORT-CODE-MISM
Clear the PORT-CODE-MISM Alarm
2.7.250 PORT-COMM-FAIL
Clear the PORT-COMM-FAIL Alarm
2.7.251 PORT-MISMATCH
2.7.252 PORT-MISSING
Clear the PORT-MISSING Alarm
2.7.253 PRC-DUPID
Clear the PRC-DUPID Alarm
2.7.254 PROTNA
Clear the PROTNA Alarm
2.7.255 PTIM
Clear the PTIM Alarm
2.7.256 PWR-A
2.7.257 PWR-B
2.7.258 PWR-REDUN
Clear the PWR-REDUN Alarm
2.7.259 RAI
Clear the RAI Condition
2.7.260 RCVR-MISS
Clear the RCVR-MISS Alarm
2.7.261 RFI
Clear the RFI Condition
2.7.262 RING-ID-MIS
Clear the RING-ID-MIS Alarm
2.7.263 RING-MISMATCH
Clear the RING-MISMATCH Alarm
2.7.264 RING-SW-EAST
2.7.265 RING-SW-WEST
2.7.266 RSVP-HELLODOWN
Clear the RSVP-HELLODOWN Alarm
2.7.267 RUNCFG-SAVENEED
2.7.268 SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition
2.7.269 SD (DWDM Client)
Clear the SD (DWDM Client) Condition
2.7.270 SDBER-EXCEED-HO
Clear the SDBER-EXCEED-HO Condition
2.7.271 SD-L
2.7.272 SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
Clear the SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N) Condition
2.7.273 SF (DWDM Client)
Clear the SF (DWDM Client) Condition
2.7.274 SFBER-EXCEED-HO
Clear the SFBER-EXCEED-HO Condition
2.7.275 SF-L
2.7.276 SFTWDOWN
2.7.277 SH-INS-LOSS-VAR-DEG-HIGH
Clear the SH-INS-LOSS-VAR-DEG-HIGH Alarm
2.7.278 SH-INS-LOSS-VAR-DEG-LOW
Clear the SH-INS-LOSS-VAR-DEG-LOW Alarm
2.7.279 SHUTTER-OPEN
Clear the SHUTTER-OPEN Condition
2.7.280 SNTP-HOST
Clear the SNTP-HOST Alarm
2.7.281 SPAN-SW-EAST
2.7.282 SPAN-SW-WEST
2.7.283 SQUELCH
Clear the SQUELCH Condition
2.7.284 SQUELCHED
Clear the SQUELCHED Condition
2.7.285 SQM
Clear the SQM Alarm
2.7.286 SSM-DUS
2.7.287 SSM-FAIL
Clear the SSM-FAIL (BITS, STM-N) Alarm
2.7.288 SSM-LNC
2.7.289 SSM-OFF
2.7.290 SSM-PRC
2.7.291 SSM-PRS
2.7.292 SSM-RES
2.7.293 SSM-SDH-TN
2.7.294 SSM-SETS
2.7.295 SSM-SMC
2.7.296 SSM-STU
Clear the SSM-STU Condition
2.7.297 SSM-ST2
2.7.298 SSM-ST3
2.7.299 SSM-ST3E
2.7.300 SSM-ST4
2.7.301 SSM-TNC
2.7.302 SWMTXMOD
Clear the SWMTXMOD Alarm
2.7.303 SWTOPRI
2.7.304 SWTOSEC
2.7.305 SWTOTHIRD
2.7.306 SYNC-FREQ
Clear the SYNC-FREQ Condition
2.7.307 SYNCPRI
Clear the SYNCPRI Alarm
2.7.308 SYNCSEC
Clear the SYNCSEC Alarm
2.7.309 SYNCTHIRD
Clear the SYNCTHIRD Alarm
2.7.310 SYSBOOT
2.7.311 TIM
Clear the TIM Alarm or Condition
2.7.312 TIM-MON
Clear the TIM-MON Alarm
2.7.313 TPTFAIL (FC_MR-4)
Clear the TPTFAIL (FC_MR-4) Alarm
2.7.314 TPTFAIL (G-Series)
Clear the TPTFAIL (G-Series) Alarm
2.7.315 TPTFAIL (ML-Series)
Clear the TPTFAIL (ML-Series) Alarm
2.7.316 TRMT
Clear the TRMT Alarm on the E1-N-14 Card
2.7.317 TRMT-MISS
Clear the TRMT-MISS Alarm
2.7.318 TU-AIS
Clear the TU-AIS Condition
2.7.319 TU-LOP
Clear the TU-LOP Alarm
2.7.320 TUNDERRUN
Clear the TUNDERRUN Alarm
2.7.321 TX-AIS
Clear the TX-AIS Condition
2.7.322 TX-RAI
Clear the TX-RAI Condition
2.7.323 UNC-WORD
Clear the UNC-WORD Condition
2.7.324 VCG-DEG
Clear the VCG-DEG Condition
2.7.325 VCG-DOWN
Clear the VCG-DOWN Condition
2.7.326 VOA-HDEG
Clear the VOA-HDEG Alarm
2.7.327 VOA-HFAIL
Clear the VOA-HFAIL Alarm
2.7.328 VOA-LDEG
Clear the VOA-LDEG Alarm
2.7.329 VOA-LFAIL
Clear the VOA-LFAIL Alarm
2.7.330 WKSWPR
Clear the WKSWPR Condition
2.7.331 WTR
2.7.332 WVL-MISMATCH
Clear the WVL-MISMATCH alarm
2.8 DWDM and Non-DWDM Card LED Activity
2.8.1 DWDM Card LED Activity After Insertion
2.8.2 Non-DWDM Card LED Activity After Insertion
2.8.3 DWDM Card LED Activity During Reset
2.8.4 Non-DWDM Card LED Activity During Reset
2.8.5 Non-DWDM Cross-Connect LED Activity During Side Switch
2.8.6 Non-DWDM Card LED State After Successful Reset
2.9 Common Procedures in Alarm Troubleshooting
Identify a Ring Name or Node ID Number
Change a Ring Name Number
Change a Node ID Number
Verify Node Visibility for Other Nodes
Verify or Create Node DCC Terminations
Lock Out an MS-SPRing Span
Clear a Ring or Span External Switching Command
Clear an SNCP Lockout
Switch Protection Group Traffic with an External Switching Command
Side Switch the Active and Standby Cross-Connect Cards
Clear a Protection Group External Switching Command
Delete a Circuit
Clear a Loopback
Reset Active TCC2 Card and Activate Standby Card
Reset the Standby TCC2/TCC2P Card
Remove and Reinsert (Reseat) the Standby TCC2
Reset a Traffic Card in CTC
Verify BER Threshold Level
Physically Replace a Card
Remove and Reinsert (Reseat) a Card
Remove and Reinsert Fan-Tray Assembly
Alarm Troubleshooting
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 SDH alarm and condition. Tables 2-1 through 2-4 provide lists of ONS 15454 SDH alarms organized by severity. Table 2-6 provides a list of alarms organized alphabetically. Table 2-8 provides a list of alarms organized by alarm type.
The troubleshooting procedure for an alarm applies to the Cisco Transport Controller (CTC) version of that alarm. If the troubleshooting procedure does not clear the alarm, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of Cisco Technical Assistance Center (TAC) toll-free numbers for your country to obtain more information.
For alarm profile information, refer to the Cisco ONS 15454 SDH Procedure Guide.
2.1 Alarm Index by Default Severity
The following tables group alarms and conditions by the severity displayed in the CTC Alarms window in the severity (SEV) column. All severities listed in this manual are the default profile settings. Alarm severities can be altered from default settings for individual alarms or groups of alarms by creating a nondefault alarm profile and applying it on a port, card, or shelf basis. All settings (default or user-defined) that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in situations that do not affect service.
2.1.1 Critical Alarms (CR)
Table 2-1 lists critical alarms.
Table 2-1 Critical Alarm Index
AU-LOP
|
HITEMP (for NE)
|
MEA (FAN)
|
AUTOLSROFF
|
HP-TIM (for HPTerm)
|
MFGMEM (AEP, AIE)
|
AWG-FAIL
|
HP-UNEQ
|
MFGMEM (Backplane or Fan-Tray Assembly)
|
AWG-OVERTEMP
|
IMPROPRMVL
|
OPWR-HFAIL
|
BKUPMEMP
|
LOA
|
OPWR-LFAIL
|
CKTDOWN
|
LOC
|
OTUK-LOF
|
COMIOXC
|
LOF (DS-3, E-1, E-4, STM-N, STM1-E) (for DS-3, E-4, STM-N, STM-1E only)
|
PORT-CODE-MISM
|
CTNEQPT-PBPROT
|
LOF (DWDM Client)
|
PORT-COMM-FAIL
|
CTNEQPT-PBWORK
|
LOF (DWDM Trunk)
|
PORT-MISMATCH (for DWDM Client only)
|
EQPT
|
LOM (for DWDM Trunk, HPTerm only)
|
PORT-MISSING
|
EQPT-MISS
|
LOS (DS-3, E-1, E-3, STM-N, STM-1E) (for DS-3, E-3, E-4, STM-N, STM-1E only)
|
SQM (for HPTerm only)
|
FAN
|
LOS (DWDM Client)
|
SWMTXMOD
|
GAIN-HFAIL
|
LOS (OTN)
|
TIM (for DWDM Client, DWDM Trunk only)
|
GAIN-LFAIL
|
MEA (BP)
|
VOA-HFAIL
|
GE-OOSYNC
|
MEA (EQPT)
|
VOA-LFAIL
|
2.1.2 Major Alarms (MJ)
Table 2-2 lists major alarms.
2.1.3 Minor Alarms (MN)
Table 2-3 lists minor alarms.
2.1.4 NA Conditions
Table 2-4 lists not alarmed conditions.
Table 2-4 NA Conditions Index
ALS
|
FORCED-REQ-RING
|
OOU-TPT
|
AMPLI-INIT
|
FORCED-REQ-SPAN
|
OUT-OF-SYNC
|
AS-CMD
|
FRCDSWTOPRI
|
OTUK-SD
|
AS-MT
|
FRCDSWTOSEC
|
OTUK-SF
|
AUD-LOG-LOSS
|
FRCDSWTOTHIRD
|
OTUK-TIM
|
AUD-LOG-LOW
|
FRNGSYNC
|
PORT-MISMATCH (for FC_MR-4 only)
|
AUTOSW-LOP-SNCP (for HPMon)
|
FULLPASSTHR-BI
|
RAI
|
AUTOSW-SDBER-SNCP
|
INC-GFP-OUTOFFRAME
|
RING-ID-MIS (for STM-N only)
|
AUTOSW-SFBER-SNCP
|
INC-GFP-SIGLOSS
|
RING-SW-EAST
|
AUTOSW-UNEQ-SNCP (HPMon)
|
INC-GFP-SYNCLOSS
|
RING-SW-WEST
|
AWG-WARM-UP
|
INC-ISD
|
RUNCFG-SAVENEED
|
CLDRESTART
|
INHSWPR
|
SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
CTNEQPT-MISMATCH
|
INHSWWKG
|
SD (DWDM Client)
|
DS3-MISM
|
INTRUSION-PSWD
|
SDBER-EXCEED-HO
|
ETH-LINKLOSS
|
IOSCFGCOPY
|
SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
EXERCISE-RING-FAIL
|
KB-PASSTHR
|
SF (DWDM Client)
|
EXERCISE-SPAN-FAIL
|
LASER-APR
|
SFBER-EXCEED-HO
|
E3-ISD
|
LKOUTPR-S
|
SHUTTER-OPEN
|
FAILTOSW
|
LOCKOUT-REQ
|
SPAN-SW-EAST
|
FAILTOSW-HO
|
LPBKCRS
|
SPAN-SW-WEST
|
FAILTOSW-LO
|
LPBKDS3FEAC
|
SQUELCH
|
FAILTOSWR
|
LPBKDS3FEAC-CMD
|
SQUELCHED
|
FAILTOSWS
|
LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
SSM-DUS
|
FE-AIS
|
LPBKFACILITY (DWDM Client)
|
SSM-LNC
|
FE-EQPT-NSA
|
LPBKFACILITY (G-Series)
|
SSM-OFF
|
FE-E1-MULTLOS
|
LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
SSM-PRC
|
FE-E1-NSA
|
LPBKTERMINAL (DWDM)
|
SSM-SETS
|
FE-E1-SA
|
LPBKTERMINAL(G-Series Ethernet)
|
SSM-STU
|
FE-E1-SNGLLOS
|
MAN-REQ
|
SSM-TNC
|
FE-E3-NSA
|
MANRESET
|
SWTOPRI
|
FE-E3-SA
|
MANSWTOINT
|
SWTOSEC
|
FE-FRCDWKSWPR-RING
|
MANSWTOPRI
|
SWTOTHIRD
|
FE-FRCDWKSWPR-SPAN
|
MANSWTOSEC
|
SYNC-FREQ
|
FE-IDLE
|
MANSWTOTHIRD
|
TIM (for STM-N only)
|
FE-LOCKOUTOFPR-SPAN
|
MANUAL-REQ-RING
|
TX-RAI
|
FE-LOF
|
MANUAL-REQ-SPAN
|
UNC-WORD
|
FE-LOS
|
NO-CONFIG
|
VCG-DEG
|
FE-MANWKSWPR-RING
|
ODUK-SD-PM
|
VCG-DOWN
|
FE-MANWKSWPR-SPAN
|
ODUK-SF-PM
|
WKSWPR
|
FORCED-REQ
|
ODUK-TIM-PM
|
WTR
|
2.1.5 NR Conditions
Table 2-4 lists not reported conditions.
2.2 Alarms and Conditions Indexed By Alphabetical Entry
Table 2-6 lists alarms and conditions by the name displayed on the CTC Alarms window or Conditions window.
Table 2-6 Alphabetical Alarm Index
AIS
|
FIBERTEMP-DEG
|
NO-CONFIG
|
ALS
|
FORCED-REQ
|
NOT-AUTHENTICATED
|
AMPLI-INIT
|
FORCED-REQ-RING
|
ODUK-AIS-PM
|
APC-DISABLED
|
FORCED-REQ-SPAN
|
ODUK-BDI-PM
|
APC-FAIL
|
FRCDSWTOINT
|
ODUK-LCK-PM
|
APSB
|
FRCDSWTOPRI
|
ODUK-OCI-PM
|
APSCDFLTK
|
FRCDSWTOSEC
|
ODUK-SD-PM
|
APSC-IMP
|
FRCDSWTOTHIRD
|
ODUK-SF-PM
|
APSCINCON
|
FRNGSYNC
|
ODUK-TIM-PM
|
APSCM
|
FSTSYNC
|
OOU-TPT
|
APSCNMIS
|
FULLPASSTHR-BI
|
OPTNTWMIS
|
AS-CMD
|
GAIN-HDEG
|
OPWR-HDEG
|
AS-MT
|
GAIN-HFAIL
|
OPWR-HFAIL
|
AU-AIS
|
GAIN-LDEG
|
OPWR-LDEG
|
AUD-LOG-LOSS
|
GAIN-LFAIL
|
OPWR-LFAIL
|
AUD-LOG-LOW
|
GCC-EOC
|
OTUK-AIS
|
AU-LOF
|
GE-OOSYNC
|
OTUK-BDI
|
AU-LOP
|
HIBATVG
|
OTUK-LOF
|
AUTOLSROFF
|
HI-LASERBIAS
|
OTUK-SD
|
AUTORESET
|
HI-RXPOWER
|
OTUK-SF
|
AUTOSW-AIS-SNCP
|
HITEMP
|
OTUK-TIM
|
AUTOSW-LOP-SNCP
|
HI-TXPOWER
|
OUT-OF-SYNC
|
AUTOSW-SDBER-SNCP
|
HLDOVRSYNC
|
PEER-NORESPONSE
|
AUTOSW-SFBER-SNCP
|
HP-RFI
|
PORT-CODE-MISM
|
AUTOSW-UNEQ-SNCP (HPMon)
|
HP-TIM
|
PORT-COMM-FAIL
|
AUTOSW-UNEQ-SNCP (LPMon)
|
HP-UNEQ
|
PORT-MISMATCH
|
AWG-DEG
|
IMPROPRMVL
|
PORT-MISSING
|
AWG-FAIL
|
INC-GFP-OUTOFFRAME
|
PRC-DUPID
|
AWG-OVERTEMP
|
INC-GFP-SIGLOSS
|
PROTNA
|
AWG-WARM-UP
|
INC-GFP-SYNCLOSS
|
PTIM
|
BATFAIL
|
INC-ISD
|
PWR-REDUN
|
BKUPMEMP
|
INC-SIGLOSS
|
RAI
|
CARLOSS (DWDM Client)
|
INC-SYNCLOSS
|
RCVR-MISS
|
CARLOSS (DWDM Trunk)
|
INHSWPR
|
RFI
|
CARLOSS (EQPT)
|
INHSWWKG
|
RING-ID-MIS
|
CARLOSS (E-Series Ethernet)
|
INTRUSION-PSWD
|
RING-MISMATCH
|
CARLOSS (G-Series Ethernet)
|
INVMACADR
|
RING-SW-EAST
|
CARLOSS (ML-Series Ethernet)
|
IOSCFGCOPY
|
RING-SW-WEST
|
CASETEMP-DEG
|
KB-PASSTHR
|
RSVP-HELLODOWN
|
CKTDOWN
|
KBYTE-APS-CHANNEL-FAILURE
|
RUNCFG-SAVENEED
|
CLDRESTART
|
LASER-APR
|
SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
COMIOXC
|
LASERBIAS-DEG
|
SD (DWDM Client)
|
COMM-FAIL
|
LASERBIAS-FAIL
|
SDBER-EXCEED-HO
|
CONTBUS-A-18
|
LASEREOL
|
SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
CONTBUS-A-18
|
LASERTEMP-DEG
|
SF (DWDM Client)
|
CONTBUS-IO-B
|
LKOUTPR-S
|
SFBER-EXCEED-HO
|
CONTBUS-B-18
|
LMP-HELLODOWN
|
SFTWDOWN
|
CTNEQPT-MISMATCH
|
LMP-NDFAIL
|
SH-INS-LOSS-VAR-DEG-HIGH
|
CTNEQPT-PBPROT
|
LOA
|
SH-INS-LOSS-VAR-DEG-LOW
|
CTNEQPT-PBWORK
|
LOC
|
SHUTTER-OPEN
|
DATAFLT
|
LOCKOUT-REQ
|
SNTP-HOST
|
DBOSYNC
|
LOF (BITS)
|
SPAN-SW-EAST
|
DSP-COMM-FAIL
|
LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
SPAN-SW-WEST
|
DSP-FAIL
|
LOF (DWDM Client)
|
SQUELCH
|
DS3-MISM
|
LOF (DWDM Trunk)
|
SQUELCHED
|
DUP-IPADDR
|
LOM
|
SQM
|
DUP-NODENAME
|
LO-RXPOWER
|
SSM-DUS
|
EHIBATVG
|
LOS (BITS)
|
SSM-FAIL
|
ELWBATVG
|
LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
SSM-LNC
|
EOC
|
LOS (DWDM Client)
|
SSM-OFF
|
EQPT
|
LOS (FUDC)
|
SSM-PRC
|
EQPT-MISS
|
LOS (OTN)
|
SSM-SETS
|
ERROR-CONFIG
|
LO-TXPOWER
|
SSM-STU
|
ETH-LINKLOSS
|
LPBKCRS
|
SSM-TNC
|
E-W-MISMATCH
|
LPBKDS3FEAC
|
SWMTXMOD
|
EXCCOL
|
LPBKDS3FEAC-CMD
|
SWTOPRI
|
EXERCISE-RING-FAIL
|
LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
SWTOSEC
|
EXERCISE-SPAN-FAIL
|
LPBKFACILITY (DWDM Client)
|
SWTOTHIRD
|
EXT
|
LPBKFACILITY (G-Series)
|
SYNC-FREQ
|
EXTRA-TRAF-PREEMPT
|
LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
SYNCPRI
|
E3-ISD
|
LPBKTERMINAL (DWDM)
|
SYNCSEC
|
FAILTOSW
|
LPBKTERMINAL(G-Series Ethernet)
|
SYNCTHIRD
|
FAILTOSW-HO
|
LP-PLM
|
SYSBOOT
|
FAILTOSW-LO
|
LP-RFI
|
TIM
|
FAILTOSWR
|
LP-TIM
|
TIM-MON
|
FAILTOSWS
|
LP-UNEQ
|
TPTFAIL (FC_MR-4)
|
FAN
|
LWBATVG
|
TPTFAIL (G-Series)
|
FANDEGRADE
|
MAN-REQ
|
TPTFAIL (ML-Series)
|
FE-AIS
|
MANRESET
|
TRMT
|
FEC-MISM
|
MANSWTOINT
|
TRMT-MISS
|
FE-EQPT-NSA
|
MANSWTOPRI
|
TU-AIS
|
FE-E1-MULTLOS
|
MANSWTOSEC
|
TU-LOP
|
FE-E1-NSA
|
MANSWTOTHIRD
|
TUNDERRUN
|
FE-E1-SA
|
MANUAL-REQ-RING
|
TX-AIS
|
FE-E1-SNGLLOS
|
MANUAL-REQ-SPAN
|
TX-RAI
|
FE-E3-NSA
|
MEA (BP)
|
UNC-WORD
|
FE-E3-SA
|
MEA (EQPT)
|
VCG-DEG
|
FE-FRCDWKSWPR-RING
|
MEA (FAN)
|
VCG-DOWN
|
FE-FRCDWKSWPR-SPAN
|
MEM-GONE
|
VOA-HDEG
|
FE-IDLE
|
MEM-LOW
|
VOA-HFAIL
|
FE-LOCKOUTOFPR-SPAN
|
MFGMEM (AEP, AIE)
|
VOA-LDEG
|
FE-LOF
|
MFGMEM (Backplane or Fan-Tray Assembly)
|
VOA-LFAIL
|
FE-LOS
|
MS-AIS
|
WKSWPR
|
FE-MANWKSWPR-RING
|
MS-EOC
|
WTR
|
FE-MANWKSWPR-SPAN
|
MS-RFI
|
WVL-MISMATCH
|
FEPRLF
|
MSSP-OOSYNC
|
|
2.3 Logical Object Type Definitions
ONS 15454 SDH alarms are grouped according to their logical object types in alarm profile listings (for example: L2SC: CARLOSS). Each alarm entry in this chapter lists its type. These are defined in Table 2-7.
Table 2-7 Alarm Type/Object Definition
|
|
Alarm interface extension
|
BITS
|
Building integration timing supply (BITS) incoming references (BITS-1, BITS-2)
|
BP
|
Backplane
|
CC
|
Unified control plane (UCP) communication channel
|
CTK
|
UCP circuit
|
DS-3
|
A DS-3 line on a DS-3 card
|
DWDM Client
|
The low-speed port, such as a TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G where the optical signal is dropped
|
DWDM Trunk
|
The optical or DWDM card carrying the high-speed signal
|
E1
|
E1-42 card
|
E3
|
E3-12 card
|
EQPT
|
A card in any of the 17 card slots. This object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, and VC
|
ETHER
|
Ethernet, such as for LAN cables
|
EXTSYNC
|
BITS outgoing references (SYNC-BITS1, SYNC-BITS2)
|
FAN
|
Fan-tray assembly
|
FCMR
|
Fiber channel
|
FUDC
|
SDH F1 User Data Channel
|
HDGE
|
High-density Gigabit Ethernet
|
L2SC
|
Layer 2 switching card (and Layer 3 for ML-Series) switching device
|
NE
|
The entire network element (node)
|
NERING
|
SDH NE2 ring
|
NESYNCH
|
SDH NE synchronization
|
PWR
|
Power equipment
|
STM-1E
|
Synchronous transfer mode 1 (speed) electrical interface
|
STM-N
|
Synchronous transfer mode (speed)
|
VCatGROUP
|
Virtual concatenation group
|
2.4 Alarm Index by Logical Object Type
Table 2-8 gives the name and page number of every alarm in the chapter, organized by logical object type.
Table 2-8 Alarm Index by Alarm Type
AIE: EQPT
|
AIE: MFGMEM (AEP, AIE)
|
BITS: AIS
|
BITS: LOF (BITS)
|
BITS: LOS (BITS)
|
BITS: SSM-DUS
|
BITS: SSM-FAIL
|
BITS: SSM-LNC
|
BITS: SSM-OFF
|
BITS: SSM-PRC
|
BITS: SSM-SETS
|
BITS: SSM-STU
|
BITS: SSM-TNC
|
BITS: SYNC-FREQ
|
BP: AS-CMD
|
BP: INVMACADR
|
BP: MEA (BP)
|
BP: MFGMEM (Backplane or Fan-Tray Assembly)
|
CC: LMP-HELLODOWN
|
CC: LMP-NDFAIL
|
CKT: CKTDOWN
|
DS3: AIS
|
DS3: AS-CMD
|
DS3: AS-MT
|
DS3: DS3-MISM
|
DS3: FE-AIS
|
DS3: FE-EQPT-NSA
|
DS3: FE-IDLE
|
DS3: FE-LOF
|
DS3: FE-LOS
|
DS3: INC-ISD
|
DS3: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
DS3: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
DS3: LPBKDS3FEAC
|
DS3: LPBKDS3FEAC-CMD
|
DS3: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
DS3: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
DS3: RAI
|
DS3: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
DS3: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
DWDM Client: AIS
|
DWDM Client: ALS
|
DWDM Client: AS-CMD
|
DWDM Client: AS-MT
|
DWDM Client: CARLOSS (DWDM Client)
|
DWDM Client: EOC
|
DWDM Client: FAILTOSW
|
DWDM Client: FORCED-REQ-SPAN
|
DWDM Client: GE-OOSYNC
|
DWDM Client: HI-LASERBIAS
|
DWDM Client: HI-RXPOWER
|
DWDM Client: HI-TXPOWER
|
DWDM Client: LOCKOUT-REQ
|
DWDM Client: LOF (DWDM Client)
|
DWDM Client: LO-RXPOWER
|
DWDM Client: LOS (DWDM Client)
|
DWDM Client: LO-TXPOWER
|
DWDM Client: LPBKFACILITY (DWDM Client)
|
DWDM Client: LPBKTERMINAL (DWDM)
|
DWDM Client: MANUAL-REQ-SPAN
|
DWDM Client: OUT-OF-SYNC
|
DWDM Client: PORT-CODE-MISM
|
DWDM Client: PORT-COMM-FAIL
|
DWDM Client: PORT-MISMATCH
|
DWDM Client: PORT-MISSING
|
DWDM Client: RFI
|
DWDM Client: SD (DWDM Client)
|
DWDM Client: SF (DWDM Client)
|
DWDM Client: SQUELCHED
|
DWDM Client: SSM-DUS
|
DWDM Client: SSM-FAIL
|
DWDM Client: SSM-LNC
|
DWDM Client: SSM-OFF
|
DWDM Client: SSM-PRC
|
DWDM Client: SSM-SETS
|
DWDM Client: SSM-STU
|
DWDM Client: SSM-TNC
|
DWDM Client: SYNC-FREQ
|
DWDM Client: TIM
|
DWDM Client: TIM-MON
|
DWDM Client: WKSWPR
|
DWDM Client: WTR
|
DWDM Trunk: AIS
|
DWDM Trunk: ALS
|
DWDM Trunk: AS-CMD
|
DWDM Trunk: AS-MT
|
DWDM Trunk: CARLOSS (DWDM Trunk)
|
DWDM Trunk: DSP-COMM-FAIL
|
DWDM Trunk: DSP-FAIL
|
DWDM Trunk: EOC
|
DWDM Trunk: FAILTOSW
|
DWDM Trunk: FEC-MISM
|
DWDM Trunk: FORCED-REQ-SPAN
|
DWDM Trunk: GCC-EOC
|
DWDM Trunk: GE-OOSYNC
|
DWDM Trunk: HI-LASERBIAS
|
DWDM Trunk: HI-RXPOWER
|
DWDM Trunk: HI-TXPOWER
|
DWDM Trunk: LOC
|
DWDM Trunk: LOCKOUT-REQ
|
DWDM Trunk: LOF (DWDM Trunk)
|
DWDM Trunk: LOM
|
DWDM Trunk: LO-RXPOWER
|
DWDM Trunk: LO-TXPOWER
|
DWDM Trunk: MANUAL-REQ-SPAN
|
DWDM Trunk: ODUK-AIS-PM
|
DWDM Trunk: ODUK-BDI-PM
|
DWDM Trunk: ODUK-LCK-PM
|
DWDM Trunk: ODUK-OCI-PM
|
DWDM Trunk: ODUK-SD-PM
|
DWDM Trunk: ODUK-SF-PM
|
DWDM Trunk: ODUK-TIM-PM
|
DWDM Trunk: OTUK-AIS
|
DWDM Trunk: OTUK-BDI
|
DWDM Trunk: OTUK-LOF
|
DWDM Trunk: OTUK-SD
|
DWDM Trunk: OTUK-SF
|
DWDM Trunk: OTUK-TIM
|
DWDM Trunk: OUT-OF-SYNC
|
DWDM Trunk: PTIM
|
DWDM Trunk: RFI
|
DWDM Trunk: SSM-DUS
|
DWDM Trunk: SSM-FAIL
|
DWDM Trunk: SSM-LNC
|
DWDM Trunk: SSM-OFF
|
DWDM Trunk: SSM-PRC
|
DWDM Trunk: SSM-SETS
|
DWDM Trunk: SSM-STU
|
DWDM Trunk: SSM-TNC
|
DWDM Trunk: SYNC-FREQ
|
DWDM Trunk: TIM
|
DWDM Trunk: TIM-MON
|
DWDM Trunk: UNC-WORD
|
DWDM Trunk: WKSWPR
|
DWDM Trunk: WTR
|
DWDM Trunk: WVL-MISMATCH
|
ECN: AS-CMD
|
ECN: AS-MT
|
ECN: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
ECN: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
ECN: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
ECN: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
ENV: EXT
|
EQPT: AS-CMD
|
EQPT: AUTORESET
|
EQPT: BKUPMEMP
|
EQPT: CARLOSS (EQPT)
|
EQPT: CLDRESTART
|
EQPT: COMIOXC
|
EQPT: COMM-FAIL
|
EQPT: CONTBUS-A-18
|
EQPT: CONTBUS-A-18
|
EQPT: CONTBUS-IO-B
|
EQPT: CONTBUS-B-18
|
EQPT: CTNEQPT-MISMATCH
|
EQPT: CTNEQPT-PBPROT
|
EQPT: CTNEQPT-PBWORK
|
EQPT: EQPT
|
EQPT: ERROR-CONFIG
|
EQPT: EXCCOL
|
EQPT: FAILTOSW
|
EQPT: FORCED-REQ
|
EQPT: HITEMP
|
EQPT: IMPROPRMVL
|
EQPT: INHSWPR
|
EQPT: INHSWWKG
|
EQPT: IOSCFGCOPY
|
EQPT: LOCKOUT-REQ
|
EQPT: MAN-REQ
|
EQPT: MANRESET
|
EQPT: MEA (EQPT)
|
EQPT: MEM-GONE
|
EQPT: MEM-LOW
|
EQPT: NO-CONFIG
|
EQPT: PEER-NORESPONSE
|
EQPT: PROTNA
|
EQPT: PWR-REDUN
|
EQPT: RUNCFG-SAVENEED
|
EQPT: SFTWDOWN
|
EQPT: SWMTXMOD
|
EQPT: WKSWPR
|
EQPT: WTR
|
ETHER: AS-CMD
|
ETHER: CARLOSS (E-Series Ethernet)
|
EXTSYNCH: FRCDSWTOPRI
|
EXTSYNCH: FRCDSWTOSEC
|
EXTSYNCH: FRCDSWTOTHIRD
|
EXTSYNCH: MANSWTOPRI
|
EXTSYNCH: MANSWTOSEC
|
EXTSYNCH: MANSWTOTHIRD
|
EXTSYNCH: SWTOPRI
|
EXTSYNCH: SWTOSEC
|
EXTSYNCH: SWTOTHIRD
|
EXTSYNCH: SYNCPRI
|
EXTSYNCH: SYNCSEC
|
EXTSYNCH: SYNCTHIRD
|
E1: AIS
|
E1: AS-CMD
|
E1: AS-MT
|
E1: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
E1: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
E1: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E1: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E1: RAI
|
E1: RCVR-MISS
|
E1: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
E1: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
E1: TRMT
|
E1: TRMT-MISS
|
E1: TX-AIS
|
E1: TX-RAI
|
E3: AIS
|
E3: AS-CMD
|
E3: AS-MT
|
E3: DS3-MISM
|
E3: E3-ISD
|
E3: FE-AIS
|
E3: FE-EQPT-NSA
|
E3: FE-E1-MULTLOS
|
E3: FE-E1-NSA
|
E3: FE-E1-SA
|
E3: FE-E1-SNGLLOS
|
E3: FE-E3-NSA
|
E3: FE-E3-SA
|
E3: FE-IDLE
|
E3: FE-LOF
|
E3: FE-LOS
|
E3: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
E3: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E3: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E3: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
E3: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
E4: AIS
|
E4: AMPLI-INIT
|
E4: AS-CMD
|
E4: AS-MT
|
E4: AWG-DEG
|
E4: AWG-OVERTEMP
|
E4: AWG-WARM-UP
|
E4: CASETEMP-DEG
|
E4: FIBERTEMP-DEG
|
E4: GAIN-HDEG
|
E4: GAIN-HFAIL
|
E4: GAIN-LDEG
|
E4: GAIN-LFAIL
|
E4: LASER-APR
|
E4: LASERBIAS-DEG
|
E4: LASERBIAS-FAIL
|
E4: LASERTEMP-DEG
|
E4: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
E4: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
E4: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E4: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
E4: OPWR-HDEG
|
E4: OPWR-HFAIL
|
E4: OPWR-LDEG
|
E4: OPWR-LFAIL
|
E4: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
E4: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
E4: SH-INS-LOSS-VAR-DEG-HIGH
|
E4: SH-INS-LOSS-VAR-DEG-LOW
|
E4: SHUTTER-OPEN
|
E4: VOA-HDEG
|
E4: VOA-HFAIL
|
E4: VOA-LDEG
|
E4: VOA-LFAIL
|
FAN: EQPT-MISS
|
FAN: FAN
|
FAN: FANDEGRADE
|
FAN: MEA (FAN)
|
FAN: MFGMEM (Backplane or Fan-Tray Assembly)
|
FCMR: AS-CMD
|
FCMR: AS-MT
|
FCMR: INC-GFP-OUTOFFRAME
|
FCMR: INC-GFP-SIGLOSS
|
FCMR: INC-GFP-SYNCLOSS
|
FCMR: INC-SIGLOSS
|
FCMR: INC-SYNCLOSS
|
FCMR: PORT-MISMATCH
|
FCMR: TPTFAIL (FC_MR-4)
|
FUDC: AIS
|
FUDC: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
HDGE [G1000]: AS-CMD
|
HDGE [G1000]: AS-MT
|
HDGE [G1000]: CARLOSS (G-Series Ethernet)
|
HDGE [G1000]: LPBKFACILITY (G-Series)
|
HDGE [G1000]: LPBKTERMINAL(G-Series Ethernet)
|
HDGE [G1000]: TPTFAIL (G-Series)
|
HDGE [G1000]: TUNDERRUN
|
HPMON: AU-AIS
|
HPMON: AU-LOP
|
HPMON: AUTOSW-AIS-SNCP
|
HPMON: AUTOSW-LOP-SNCP
|
HPMON: AUTOSW-SDBER-SNCP
|
HPMON: AUTOSW-SFBER-SNCP
|
HPMON: AUTOSW-UNEQ-SNCP (HPMon)
|
HPMON: FAILTOSW-HO
|
HPMON: FORCED-REQ
|
HPMON: HP-RFI
|
HPMON: HP-TIM
|
HPMON: HP-UNEQ
|
HPMON: LOCKOUT-REQ
|
HPMON: LPBKCRS
|
HPMON: MAN-REQ
|
HPMON: SDBER-EXCEED-HO
|
HPMON: SFBER-EXCEED-HO
|
HPMON: WKSWPR
|
HPMON: WTR
|
HPTERM: AU-AIS
|
HPTERM: AU-LOF
|
HPTERM: AU-LOP
|
HPTERM: HP-TIM
|
HPTERM: HP-UNEQ
|
HPTERM: LOM
|
HPTERM: OOU-TPT
|
HPTERM: SDBER-EXCEED-HO
|
HPTERM: SFBER-EXCEED-HO
|
HPTERM: SQM
|
LPMON: AUTOSW-AIS-SNCP
|
LPMON: AUTOSW-LOP-SNCP
|
LPMON: AUTOSW-SDBER-SNCP
|
LPMON: AUTOSW-SFBER-SNCP
|
LPMON: AUTOSW-UNEQ-SNCP (LPMon)
|
LPMON: FAILTOSW-LO
|
LPMON: FORCED-REQ
|
LPMON: LOCKOUT-REQ
|
LPMON: LOM
|
LPMON: LP-UNEQ
|
LPMON: MAN-REQ
|
LPMON: SQM
|
LPMON: TU-AIS
|
LPMON: TU-LOP
|
LPMON: WKSWPR
|
LPMON: WTR
|
LPTERM: LOM
|
LPTERM: LP-PLM
|
LPTERM: LP-RFI
|
LPTERM: LP-TIM
|
LPTERM: LP-UNEQ
|
LPTERM: OOU-TPT
|
LPTERM: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
LPTERM: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
LPTERM: TU-LOP
|
L2SC: AS-CMD
|
L2SC: CARLOSS (ML-Series Ethernet)
|
L2SC: TPTFAIL (ML-Series)
|
NBR: RSVP-HELLODOWN
|
NE: APC-DISABLED
|
NE: APC-FAIL
|
NE: AS-CMD
|
NE: AUD-LOG-LOSS
|
NE: AUD-LOG-LOW
|
NE: AWG-FAIL
|
NE: DATAFLT
|
NE: DBOSYNC
|
NE: DUP-IPADDR
|
NE: DUP-NODENAME
|
NE: ETH-LINKLOSS
|
NE: HITEMP
|
NE: INTRUSION-PSWD
|
NE: OPTNTWMIS
|
NE: SNTP-HOST
|
NE: SYSBOOT
|
NESYNCH: FRCDSWTOINT
|
NESYNCH: FRCDSWTOPRI
|
NESYNCH: FRCDSWTOSEC
|
NESYNCH: FRCDSWTOTHIRD
|
NESYNCH: FRNGSYNC
|
NESYNCH: FSTSYNC
|
NESYNCH: HLDOVRSYNC
|
NESYNCH: MANSWTOINT
|
NESYNCH: MANSWTOPRI
|
NESYNCH: MANSWTOSEC
|
NESYNCH: MANSWTOTHIRD
|
NESYNCH: SSM-LNC
|
NESYNCH: SSM-PRC
|
NESYNCH: SSM-SETS
|
NESYNCH: SSM-STU
|
NESYNCH: SSM-TNC
|
NESYNCH: SWTOPRI
|
NESYNCH: SWTOSEC
|
NESYNCH: SWTOTHIRD
|
NESYNCH: SYNC-FREQ
|
NESYNCH: SYNCPRI
|
NESYNCH: SYNCSEC
|
NESYNCH: SYNCTHIRD
|
OSCRING: RING-ID-MIS
|
PWR: AS-CMD
|
PWR: BATFAIL
|
PWR: EHIBATVG
|
PWR: ELWBATVG
|
PWR: HIBATVG
|
PWR: LWBATVG
|
STM-N: ALS
|
STM-N: APSB
|
STM-N: APSCDFLTK
|
STM-N: APSC-IMP
|
STM-N: APSCNMIS
|
STM-N: APSCINCON
|
STM-N: APSCM
|
STM-N: AS-CMD
|
STM-N: APSCNMIS
|
STM-N: AS-MT
|
STM-N: AUTOLSROFF
|
STM-N: EOC
|
STM-N: E-W-MISMATCH
|
STM-N: EXERCISE-RING-FAIL
|
STM-N: EXERCISE-SPAN-FAIL
|
STM-N: EXTRA-TRAF-PREEMPT
|
STM-N: FAILTOSW
|
STM-N: FAILTOSWR
|
STM-N: FAILTOSWS
|
STM-N: FE-FRCDWKSWPR-RING
|
STM-N: FE-FRCDWKSWPR-SPAN
|
STM-N: FE-LOCKOUTOFPR-SPAN
|
STM-N: FE-MANWKSWPR-RING
|
STM-N: FE-MANWKSWPR-SPAN
|
STM-N: FEPRLF
|
STM-N: FORCED-REQ-RING
|
STM-N: FORCED-REQ-SPAN
|
STM-N: FULLPASSTHR-BI
|
STM-N: HI-LASERBIAS
|
STM-N: HI-RXPOWER
|
STM-N: HI-TXPOWER
|
STM-N: KB-PASSTHR
|
STM-N: KBYTE-APS-CHANNEL-FAILURE
|
STM-N: LASEREOL
|
STM-N: LKOUTPR-S
|
STM-N: LOCKOUT-REQ
|
STM-N: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
STM-N: LO-RXPOWER
|
STM-N: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
STM-N: LO-TXPOWER
|
STM-N: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
STM-N: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
STM-N: MANUAL-REQ-RING
|
STM-N: MANUAL-REQ-SPAN
|
STM-N: MS-AIS
|
STM-N: MS-EOC
|
STM-N: MS-RFI
|
STM-N: MSSP-OOSYNC
|
STM-N: PRC-DUPID
|
STM-N: RING-ID-MIS
|
STM-N: RING-MISMATCH
|
STM-N: RING-SW-EAST
|
STM-N: RING-SW-WEST
|
STM-N: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
STM-N: SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)
|
STM-N: SPAN-SW-EAST
|
STM-N: SPAN-SW-WEST
|
STM-N: SQUELCH
|
STM-N: SSM-DUS
|
STM-N: SSM-FAIL
|
STM-N: SSM-LNC
|
STM-N: SSM-OFF
|
STM-N: SSM-PRC
|
STM-N: SSM-SETS
|
STM-N: SSM-STU
|
STM-N: SSM-TNC
|
STM-N: SYNC-FREQ
|
STM-N: TIM
|
STM-N: WKSWPR
|
STM-N: WTR
|
STM1E: AS-CMD
|
STM1E: AS-MT
|
STM1E: LOF (DS-3, E-1, E-4, STM-N, STM1-E)
|
STM1E: LOS (DS-3, E-1, E-3, STM-N, STM-1E)
|
STM1E: LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
STM1E: LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
|
STM1E: MS-AIS
|
STM1E: MS-RFI
|
STM1E: SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)
|
STM1E: TIM
|
VCatGROUP: LOA
|
VCatGROUP: VCG-DEG
|
VCatGROUP: VCG-DOWN
|
2.5 Trouble Notifications
The ONS 15454 SDH uses standard ITU-T x.733 categories to characterize levels of trouble. The ONS 15454 SDH reports alarmed trouble notifications and Not-Alarmed (NA) notifications, if selected, in the CTC Alarms window. Alarms typically signify a problem that the user needs to fix, such as the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, while Not-Alarmed (NA) notifications do not necessarily need immediate troubleshooting.
The ITU further divides alarms into Service-Affecting (SA) and NSA status. A Service-Affecting (SA) failure affects a provided service or the network's ability to provide service. For example, the "TRMT-MISS" alarm on page 2-206 is characterized by default as an SA failure. TRMT-MISS occurs when a cable connector is removed from an active E-1 card port. The default severity assumes that service has been interrupted or moved. If the E-1 card is in a protection group and the traffic is on the protect card rather than the working card, or if the port with the TRMT-MISS alarm has no circuits provisioned, TRMT-MISS would be raised as NSA because traffic was not interrupted or moved.
2.5.1 Conditions
The term "Condition" refers to any problem detected on an ONS 15454 SDH shelf whether or not the problem is reported (that is, whether or not it generates a trouble notification). Reported conditions include alarms, Not-Alarmed conditions, and Not-Reported (NR) conditions. A snapshot of all current raised conditions on a node, whether they are reported or not, can be retrieved using the CTC Conditions window. You can see the actual reporting messages for alarms and NAs in the CTC History tab. ONS 15454 SDH condition reporting is not ITU-compliant.
2.5.2 Severities
The ONS 15454 SDH uses the following ITU severities: Critical (CR), Major (MJ), and Minor (MN). Non-Service Affecting (NSA) alarms always have a Minor (MN) severity. Service-Affecting (SA) alarms could be Critical (CR), Major (MJ), or Minor (MN). Critical alarms generally indicate severe, service-affecting trouble that needs immediate correction. A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network.
An example of a Non-Service Affecting (NSA) alarm is the "FSTSYNC" condition on page 2-104 (Fast Start Synchronization Mode), which indicates the ONS 15454 SDH is choosing a new timing reference because the previously used reference has failed. The user needs to troubleshoot the loss of the prior timing source, but the loss is not immediately disruptive to service.
ITU standard severities are the default settings for the ONS 15454 SDH. A user can customize ONS 15454 SDH alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the Cisco ONS 15454 SDH Procedure Guide.
This chapter lists the default profile alarm severity for the Service-Affecting (SA) case of each alarm when it is applicable. Any alarm with a profile value of Critical (CR) or Major (MJ) will—if reported as Non-Service Affecting (NSA) because no traffic is lost—be reported with a Minor (MN) severity instead.
2.6 Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS 15454 SDH. Do not perform any procedures in this chapter unless you understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards; in these instances pay close attention to the following caution.
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 STM-64 cards. In these instances, pay close attention to the following warnings.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation 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.7 Alarm Procedures
This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition.
Note When you check the status of alarms for cards, ensure that the alarm filter icon in the lower right corner is not indented. If it is, click it to turn it off. When you're done checking for alarms, click the alarm filter icon again to turn filtering back on. For more information about alarm filtering, see the Cisco ONS 15454 SDH Procedure Guide.
Note When checking alarms, ensure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, see the Cisco ONS 15454 SDH Procedure Guide.
2.7.1 AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: BITS, DS-3, DWDM Client, DWDM Trunk, E-1, E-3, E-4, and FUDC
The Alarm Indication Signal (AIS) condition indicates that this node is detecting AIS in the incoming signal SDH overhead.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input 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.
Note DS-3 facility and terminal loopbacks do not transmit DS-3 AIS in the direction away from the loopback. Instead of DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.
Clear the AIS Condition
Step 1 Determine whether the upstream nodes and equipment have alarms, especially the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, or out-of-service (OOS) 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.2 AIS-L
The AIS-L condition is not used in this platform in this release. It is reserved for future development.
2.7.3 ALS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Automatic Laser Shutdown condition occurs when an amplifier (OPT-BST or OPT-PRE) is switched on. The turn-on process lasts approximately nine seconds, and the condition clears after approximately 10 seconds.
Note ALS is an informational condition. It does not require troubleshooting.
2.7.4 AMPLI-INIT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-4
The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition is typically raised with the "APC-DISABLED" alarm on page 2-26.
Clear the AMPLI-INIT Condition
Step 1 Complete the "Delete a Circuit" procedure on the most recently created circuit.
Step 2 Recreate this circuit using the procedures in the Cisco ONS 15454 SDH Procedure Guide.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.5 APC-DISABLED
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The Automatic Power Control (APC) Disabled alarm occurs when the information related to the number of channels is not reliable. The alarm can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-74, the "IMPROPRMVL" alarm on page 2-116, or the "MEA (EQPT)" alarm on page 2-152. 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 primary alarm:
•Clear the EQPT Alarm
•Clear the IMPROPRMVL Alarm
•Clear the MEA (FAN) Alarm
Step 2 If the alarm does not clear, complete the "Delete a Circuit" procedure and then recreate it.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.6 APC-FAIL
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The APC Failure alarm occurs when APC has not been able to create a setpoint on a node because it has consumed all allocated power margins. These power margins (from 0 dB to 3 dB) are allocated when the network is installed. Margins can be consumed due to fiber aging or the insertion of unexpected extra loss in the span after a fiber cut.
Clear the APC-FAIL Alarm
Step 1 Isolate the cause of increased margin use:
•If it is due to fiber aging, replace the indicated fiber. (You can test the integrity of the fiber using optical testing equipment.)
•If it is due to a fiber cut, resolve this issue to resolve this alarm.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.7 APSB
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
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 SDH nodes send invalid APS codes if configured in a 1+1 protection scheme with newer SDH nodes, such as the ONS 15454 SDH. These invalid codes cause an APSB alarm on an ONS node.
Clear the APSB Alarm
Step 1 Use an optical test set to examine the incoming SDH overhead to confirm inconsistent or invalid K bytes.
For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment may not interoperate effectively with the ONS 15454 SDH.
Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you may need to replace the upstream cards for protection switching to operate properly. Complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the alarm does not clear, log into log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.8 APSCDFLTK
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
The APS Default K Byte Received alarm occurs when a multiplex section-shared protection ring (MS-SPRing) is not properly configured, for example, when a four-node MS-SPRing has one node configured as a subnetwork connection protection (SNCP) ring. When this misconfiguration occurs, a node in an SNCP ring or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for MS-SPRing. One of the bytes sent is considered invalid by the MS-SPRing configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "MSSP-OOSYNC" alarm on page 2-159.
Note This alarm can also be expected when upgrading to Release 4.6 when the ring identifier is updated.
Clear the APSCDFLTK Alarm
Step 1 Complete the "Identify a 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 Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" section.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 SDH Procedure Guide provides information for fibering MS-SPRings.
Step 5 If the alarm does not clear and if the network is a four-fiber MS-SPRing, 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 to verify that each node is visible to the other nodes while in network view.
Step 7 If nodes are not visible, complete the "Verify or Create Node DCC Terminations" procedure to ensure that SDH data communications channel (DCC) terminations exist on each node.
Step 8 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.9 APSC-IMP
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
An Improper APS Code alarm indicates bad or invalid K bytes. APSC-IMP occurs on STM-N cards in an MS-SPRing configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. The alarm clears when the node receives valid K bytes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note This alarm can occur when the exercise command or a Lock Out is applied to a span. An externally switched span does not raise this alarm because traffic is preempted.
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.
For specific procedures to use the test set equipment, consult the manufacturer.
If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454 SDH. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454 SDHs, consult the appropriate user documentation.
Step 2 If the K byte is valid, complete the "Identify a Ring 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 number that does not match the other nodes, complete the "Change a Ring Name Number" procedure to make the ring names identical.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.10 APSCINCON
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
An Inconsistent APS Code alarm indicates that the APS code contained in the SDH overhead is inconsistent. The SDH overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454 SDH, to switch the SDH signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.
Clear the APSCINCON Alarm on an STM-N Card in an MS-SPRing
Step 1 Look for other alarms, especially a "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, an "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131, or the "AIS" alarm on page 2-25. If they are present, complete the troubleshooting procedures for the alarm(s). Clearing the other alarm clears the APSCINCON alarm.
Step 2 If an APSINCON alarm occurs with no other alarms, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.11 APSCM
•Major (MJ), Service-Affecting (SA)
•Logical Object: STM-N
The APS Channel Mismatch alarm occurs when the ONS 15454 SDH expects a working channel but receives a protection channel. In many cases, the working and protection channels are crossed and the protection channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. APSCM occurs in a 1+1 configuration. The APSCM alarm only occurs on the ONS 15454 SDH when bidirectional protection is used on STM-N cards in a 1+1 configuration.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation 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 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the APSCM Alarm
Step 1 Verify that the working-card channel fibers are physically connected directly to the adjoining node's working-card channel fibers.
Step 2 If the alarm does not clear, verify that the protection-card channel fibers are physically connected directly to the adjoining node's protection-card channel fibers.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.12 APSCNMIS
•Major (MJ), Service-Affecting (SA)
•Logical Object: STM-N
The Node ID Mismatch alarm occurs when the source node ID contained in the K2 byte of the incoming APS channel is not present in the ring map. APSCNMIS could occur and clear when an MS-SPRing is being provisioned. If so, the user can disregard the temporary occurrence. If the APSCNMIS occurs and stays, the alarm clears when a K byte with a valid source node ID is received.
Clear the APSCNMIS Alarm
Step 1 Complete the "Identify a Ring 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 Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Note If the node names shown on the network view do not correlate with the node IDs, log into each node and click the Provisioning > MS-SPRing tabs. The MS-SPRing window displays the node ID of the login node.
Note Applying and removing a Lock Out on a span causes the ONS 15454 SDH to generate a new K byte. The APSCNMIS alarm clears when the node receives a K byte containing the correct node ID.
Step 5 If the alarm does not clear, use the "Lock Out an MS-SPRing Span" procedure to lock out the span.
Step 6 Complete the "Clear a Ring or Span External Switching Command" procedure to clear the Lock Out.
Step 7 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.13 APSIMP
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STMN
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 SNCP or MS-SPRing 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 or APSCM. It is not superseded by AIS or 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.
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 SDH.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.14 AS-CMD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: BP, DS-3, DWDM Client, DWDM Trunk, EQPT, ETHER, E-1, E-3, E-4, FCMR, HDGE, L2SC, NE, PWR, STM-N, STM-1E
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; that is, suppressing alarms on a card also suppresses alarms on its ports.
Clear the AS-CMD Condition
Step 1 For all nodes, in node view, click the Conditions tab.
Step 2 Click Retrieve. If you have already retrieved conditions, look under the Object column and Eqpt Type column and note what entity the condition is reported against, such as a port, slot, or shelf.
If the condition is reported against an STM-N card and slot, 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 8.
If the condition is reported against the NE object, go to Step 9.
Step 3 If the AS-CMD condition is reported for an STM-N card, 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 an amplifier, combiner, or other DWDM card, 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 > Optical Line > Alarm Profiles 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 5 In node view, if the AS-CMD condition is reported for a card and not an individual port, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.
Step 6 Locate the row for the reported card slot.
Step 7 Click the Suppress Alarms column check box to deselect the option for the card row.
Step 8 If the condition is reported for the backplane, the alarms are suppressed for cards such as the AIP that are not in the optical or electrical slots. To clear the alarm:
a. In node view, click the Provisioning > Alarm Profiles > Alarm Behavior tabs.
b. In the backplane row, deselect the Suppress Alarms column check box.
c. Click Apply.
Step 9 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.
b. Click the Suppress Alarms check box located at the bottom of the window to deselect the option.
c. Click Apply.
Step 10 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.15 AS-MT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, DWDM Client, DWDM Trunk, E-1, E-3, E-4, FCMR, HDGE, STM-N, STM-1E
The Alarms Suppressed for Maintenance Command condition applies to STM-N and electrical (traffic) cards and occurs when a port is placed in the out-of-service maintenance (OOS-MT) state for loopback testing operations.
Clear the AS-MT Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.16 AU-AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: HPMon, HPTerm
An Administration Unit (AU) AIS condition applies to the administration unit, which consists of the virtual container (VC) capacity and pointer bytes (H1, H2, and H3) in the SDH frame.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input 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 AU-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, complete the "Clear the APSB Alarm" procedure.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.17 AUD-LOG-LOSS
•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. You will have to off-load (save) the log 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 need to assign an extension to the file. The file is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.
Step 6 Click Save.
The 640 entries are saved in this file. New entries will continue with the next number in the sequence, rather than starting over.
Step 7 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.18 AUD-LOG-LOW
•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. The condition does not require troubleshooting.
2.7.19 AU-LOF
•Major (MJ), Service-Affecting (SA)
•Logical Object: HPTerm
The Administrative Unit (AU) Loss of Frame (LOF) alarm indicates that the ONS 15454 SDH detects frame loss in the regenerator section of the SDH overhead.
Clear the AU-LOF Alarm
Step 1 Complete the "Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.20 AU-LOP
•Critical (CR), Service-Affecting (SA)
•Logical Objects: HPMon, HPTerm
An AU Loss of Pointer (LOP) alarm indicates that the SDH high order path overhead section of the administration unit has detected a loss of path. AU-LOP occurs when there is a mismatch between the expected and provisioned circuit size.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AU-LOP Alarm
Step 1 In node view, click the Circuits tab and view the alarmed circuit.
Step 2 Verify that the correct circuit size is listed in the Size column. If the size is different from what is expected, such as a VC4-4c instead of a VC4, this causes the alarm.
Step 3 If you have been monitoring the circuit with optical test equipment, a mismatch between the provisioned circuit size and the size expected by the test set can cause this alarm. Ensure that the test set monitoring is set up for the same size as the circuit provisioning.
For instructions to use the optical test set, consult the manufacturer.
Step 4 If you have not been using a test set, or if the test set is correctly set up, the error is in the provisioned CTC circuit size. Complete the "Delete a Circuit" procedure.
Step 5 Recreate the circuit for the correct size. For instructions, see the Cisco ONS 15454 SDH Procedure Guide.
Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.21 AUTOLSROFF
•Critical (CR), Service-Affecting (SA)
•Logical Object: STM-N
The Auto Laser Shutdown alarm occurs when the STM-64 card temperature exceeds 194 degrees F (90 degrees C). The internal equipment automatically shuts down the STM-64 laser when the card temperature rises to prevent the card from self-destructing.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation 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 SDH LCD front panel (Figure 2-1).
Figure 2-1 shows the shelf LCD panel.
Figure 2-1 Shelf LCD Panel
Step 2 Determine whether there is a HITEMP alarm present. If the temperature of the shelf exceeds 90 degrees C (194 degrees F), the alarm should clear if you solve the ONS 15454 SDH temperature problem. Complete the "Clear the HITEMP Alarm" procedure.
Step 3 If the temperature of the shelf is under 90 degrees C (194 degrees F), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Card" procedure for the STM-64 card.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 4 If card replacement does not clear the alarm, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.22 AUTORESET
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Automatic System Reset alarm occurs when a card is performing an automatic warm reboot. An AUTORESET occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the AUTORESET Alarm
Step 1 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 one time per month with no apparent cause, complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.23 AUTOSW-AIS-SNCP
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: HPMon, LPMon
The Automatic SNCP Switch Caused by AIS condition indicates that automatic SNCP protection switching occurred because of the "TU-AIS" condition on page 2-206. The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears. The AUTOSW-AIS-SNCP clears when you clear the primary alarm on the upstream node.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input 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-SNCP Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.24 AUTOSW-LOP-SNCP
•Minor (MN), Non-Service Affecting (NSA) for LPMon
•Not Alarmed (NA), Non-Service Affecting (NSA) for HPMon
•Logical Objects: HPMon, LPMon
An Automatic SNCP Switch Caused by LOP alarm indicates that an automatic SNCP protection switching occurred because of the "AU-LOP" alarm on page 2-36. The SNCP ring is configured for revertive switching and will switch back to the working path after the fault clears.
Clear the AUTOSW-LOP-SNCP Alarm
Step 1 Complete the "Clear the AU-LOP Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.25 AUTOSW-PDI-SNCP
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: VCSMON-HP
The Automatic SNCP Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic SNCP protection switching occurred because of a PDI. The SNCP is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-PDI-SNCP Condition
Step 1 Verify that all circuits terminating in the reporting card are DISCOVERED:
a. Click the Circuits tab.
b. Verify that the Status column lists the circuit as active.
c. If the Status column lists the circuit as PARTIAL, wait 10 minutes for the ONS 15454 to initialize fully. If the PARTIAL status does not change after full initialization, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC to report a service-affecting problem (1-800-553-2447).
Step 2 After determining that the circuit is DISCOVERED, ensure that the signal source to the card reporting the alarm is working.
Step 3 If traffic is affected, complete the "Delete a Circuit" procedure.
Caution Deleting a circuit can affect existing traffic.
Step 4 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.
Step 5 If circuit deletion and recreation does not clear the condition, verify that there is no problem stemming from the far-end STM-N card providing STS payload to the reporting card.
Step 6 If the condition does not clear, confirm the cross-connect between the STM-N card and the reporting card.
Step 7 If the condition does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 Procedure Guide.
Step 8 If the condition does not clear, complete the "Physically Replace a Card" procedure for the optical/electrical cards.
Note Removing a card that currently carries traffic on one or more ports can cause a traffic hit. To avoid this, perform an external switch if a switch has not already occurred. See the "Verify or Create Node DCC Terminations" 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 9 If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447).
2.7.26 AUTOSW-SDBER-SNCP
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: HPMon, LPMon
The Automatic SNCP Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade [see the "SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)" condition on page 2-182] caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SD is resolved.
Clear the AUTOSW-SDBER-SNCP Condition
Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.27 AUTOSW-SFBER-SNCP
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: HPMon, LPMon
The Automatic SNCP Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that a signal fail (see the "SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)" condition on page 2-185) caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path when the SF is resolved.
Clear the AUTOSW-SFBER-SNCP Condition
Step 1 Complete the "Clear the SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N) Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.28 AUTOSW-UNEQ-SNCP (HPMon)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: HPMon
The Automatic SNCP Switch Caused by an Unequipped indicates that an HP-UNEQ alarm caused automatic SNCP protection switching to occur (see the "HP-UNEQ" alarm on page 2-114). The SNCP ring is configured for revertive switching and reverts to the working path after the fault clears.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AUTOSW-UNEQ-SNCP (HPMon) Condition
Step 1 Complete the "Clear the HP-UNEQ Alarm" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.29 AUTOSW-UNEQ-SNCP (LPMon)
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: LPMon
AUTOSW-UNEQ indicates that the "LP-UNEQ" alarm on page 2-147 caused automatic SNCP protection switching to occur. The SNCP ring is configured for revertive switching and reverts to the working path after the fault clears.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no cable is connected. Avoid exposure and do not stare into open apertures.
Clear the AUTOSW-UNEQ-SNCP (LPMon) Alarm
Step 1 Display the CTC network view and right-click the span reporting AUTOSW-UNEQ. Select Circuits from the shortcut menu.
Step 2 If the specified circuit is a low-order path tunnel, determine whether low-order paths are assigned to the tunnel.
Step 3 If the low-order path tunnel does not have assigned low-order paths, delete the low-order path tunnel from the list of circuits.
Step 4 If you have complete visibility to all nodes, determine whether there are incomplete circuits such as stranded bandwidth from circuits that were not completely deleted.
Step 5 If you find incomplete circuits, determine whether they are working circuits and if they are still passing traffic.
Step 6 If the incomplete circuits are not needed or are not passing traffic, delete them and log out of CTC. Log back in and for incomplete circuits again. Recreate any needed circuits.
Step 7 If the alarm does not clear, verify that all circuits terminating in the reporting card are active:
a. In node view, click the Circuits tab.
b. Verify that the Status column lists the port as active.
c. If the Status column lists the port as incomplete, and the incomplete does not change after a full initialization, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Step 8 After you determine that the port is active, verify the signal source received by the card reporting the alarm.
Step 9 If the alarm does not clear, verify that the far-end STM-N card providing payload to the card is working properly.
Step 10 If the alarm does not clear, verify the far-end cross-connect between the STM-N card and the E-N card.
Step 11 If the alarm does not clear, clean the far-end optical fiber cable ends according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation 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.
Step 12 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.30 AWG-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The AWG Temperature Degrade alarm indicates that an internal failure on the multiplexer or demultiplexer heater control circuit causes the AWG temperature to rise above or fall below the degrade threshold.
Clear the AWG-DEG Alarm
Step 1 This alarm does not immediately affect traffic. But eventually, you will need to complete the "Physically Replace a Card" procedure on the reporting card to clear the alarm.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.31 AWG-FAIL
•Critical (CR), Service-Affecting (SA)
•Logical Object: NE
The AWG Temperature Fail alarm indicates that a heater control circuit on the multiplexer or demultiplexer card has failed.
Clear the AWG-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.32 AWG-OVERTEMP
•Critical (CR), Service-Affecting (SA)
•Logical Object: E-4
The AWG Over Temperature alarm occurs in conjunction with the "AWG-FAIL" alarm on page 2-44 when the AWG temperature exceeds 100 degrees C (212 degrees F). The multiplexer or demultiplexer goes into protection mode, disabling the AWG chip heater.
Clear the AWG-OVERTEMP Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.33 AWG-WARM-UP
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-4
The AWG Warm-up condition occurs during AWG startup. The length of time needed for the condition to clear varies, depending upon environmental conditions. It can last up to approximately 10 minutes.
Note AWG-WARM-UP is an informational condition, and does not require troubleshooting unless it does not clear.
2.7.34 BATFAIL
•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 BATFAIL Alarm
Step 1 At the site, determine which battery is not present or operational.
Step 2 Remove the power cable from the faulty supply.
If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.35 BKUPMEMP
Default Severity: Critical (CR), Service-Affecting (SA)
Note The severity is Minor (MN), Non-Service-Affecting (NSA) for SBY TCC2/TCC2P card.
SDH Logical Object: EQPT
The Primary Nonvolatile Backup Memory Failure alarm refers to a problem with the TCC2/TCC2P card flash memory. This alarm is raised on ACT/SBY TCC2/TCC2P cards. The alarm occurs when the TCC2/TCC2P card is in active or standby state and has one of four problems:
•Failure to format a flash partition.
•Failure to write a file to a flash partition.
•Problem at the driver level.
•Code volume fails cyclic redundancy checking (CRC, a method to verify for errors in data transmitted to the TCC2/TCC2P card).
The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-74. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Clear the BKUPMEMP Alarm
Step 1 Verify that both TCC2/TCC2P cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC2/TCC2P cards.
Step 2 Determine whether the active or standby TCC2/TCC2P card has the alarm.
Step 3 If both cards are powered and enabled, reset the TCC2/TCC2P card where the alarm is raised. If the card is the active TCC2/TCC2P card, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card. The ACT/STBY LED of this card should be amber and the newly active TCC2/TCC2P card LED should be green.
If the card is the standby TCC2/TCC2P card, complete the "Reset the Standby TCC2/TCC2P Card" procedure.
Step 4 If the reset TCC2/TCC2P card has not rebooted successfully, or the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free Technical Support numbers for your country. If the Technical Support technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the Technical Support technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.36 CARLOSS (DWDM Client)
•Major (MJ), Service-Affecting (SA)
•Logical Object: DWDM Client
A Carrier Loss alarm on the transponder (TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G) or muxponder (MXP_2.5G_10G) card occurs when ITU-T G.709 monitoring is turned off at the client port. It is similar to the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Clear the CARLOSS (DWDM Client) Alarm
Step 1 From node view, double-click the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card to display card view.
Step 2 Click the Provisioning > OTN > OTN Lines tabs.
Step 3 Check the check box under the G.709 OTN column.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.37 CARLOSS (DWDM Trunk)
•Major (MJ), Service-Affecting (SA)
•Logical Object: DWDM Trunk
A Carrier Loss on the optical trunk connecting to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards is raised when ITU-T G.709 monitoring is disabled.
Clear the CARLOSS (DWDM Trunk) Alarm
Step 1 Complete the "Clear the CARLOSS (DWDM Client) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.38 CARLOSS (EQPT)
•Major (MJ), Service-Affecting (SA)
•Logical Object: EQPT
The Carrier Loss Equipment alarm occurs when the ONS 15454 SDH and the workstation hosting CTC do not have a TCP/IP connection. CARLOSS is a problem involving the LAN or data circuit used by the RJ-45 connector on the TCC2 card or the LAN backplane pin connection on the back of the ONS 15454 SDH. The alarm does not involve an Ethernet circuit connected to a port on an Ethernet (traffic) card. The problem is in the connection (usually a LAN problem) and not the CTC or the ONS 15454 SDH.
On TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G or MXP_2.5G_10G cards, CARLOSS is also raised against trunk ports when ITU-T G.709 monitoring is turned off.
A TXP_MR_2.5G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data type.
Clear the CARLOSS (EQPT) Alarm
Step 1 If the reporting card is a TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card, verify the type of payload configured:
a. Double-click the reporting TXP card.
b. Click the Provisioning > Card tabs.
c. From the Payload Data Type list, choose the correct payload for the card and click Apply.
Step 2 Verify connectivity by pinging the ONS 15454 SDH that is reporting the alarm:
a. If you are using a Microsoft Windows operating system, choose Start > Programs > Command Prompt.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
c. For both the Sun and Microsoft operating systems, at the prompt type:
ping ONS-15454-SDH-IP-address
For example, ping 192.1.0.2.
If the workstation has connectivity to the ONS 15454 SDH, the workstation displays "Reply from IP-Address" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.
Step 3 Verify that the straight-through (Category 5) LAN cable is properly connected and attached to the correct port.
Step 4 If the straight-through (Category 5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 5 If you are unable to establish connectivity, replace the straight-through cable with a new known-good cable.
Step 6 If you are unable to establish connectivity, perform standard network/LAN diagnostics. For example, trace the IP route, verify cable continuity, and troubleshoot any routers between the node. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.39 CARLOSS (E-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Logical Object: ETHER
A Carrier Loss on the LAN alarm is the data equivalent of the SDH "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135. The Ethernet (traffic) card has lost its link and is not receiving a valid signal. The most common causes of this alarm are a disconnected straight-through (Category 5) LAN cable or an improperly installed Ethernet card. Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
CARLOSS also occurs after the restoration of a node database. In this instance, the alarm clears approximately 30 seconds after the node reestablishes Spanning Tree Protocol (STP). Reestablishment applies to the E-Series Ethernet cards but not to the G1000-4 card. The G1000-4 card does not use STP and is unaffected by STP reestablishment.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CARLOSS (E-Series Ethernet) Alarm
Step 1 Verify that the straight-through (Category 5) LAN cable is properly connected and attached to the correct port.
Step 2 If the straight-through (Category 5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 3 If there is no misconnection to an STM-N card, verify that the transmitting device is operational. If not, troubleshoot the device.
Step 4 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the straight-through (Category 5) LAN cable connecting the transmitting device to the Ethernet port.
Step 6 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet (traffic) card.
Step 7 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the Ethernet (traffic) card.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 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 circuit sizes in the setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Click 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 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 SDH at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet (traffic) card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross connect circuit will connect the Ethernet card to an STM-N card on the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.40 CARLOSS (G-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Logical Object: HDGE
A Carrier Loss on the LAN alarm is the data equivalent of the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135. The Ethernet (traffic) card has lost its link and is not receiving a valid signal.
CARLOSS on the G1000-4 card can be caused by one of two situations:
•The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. The CARLOSS can be caused by an improperly connected Ethernet cable or a problem with the signal between the Ethernet device and the G1000-4 port.
•If a problem exists in the end-to-end path (including possibly the far-end G1000-4 card), the problem causes the reporting G1000-4 to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, a TPTFAIL (G-Series) alarm, or STM-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G-Series) alarm.
Refer to the Cisco ONS 15454 SDH Reference Guide for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. See also the "TRMT" alarm on page 2-205 for more information about alarms that occur when a point-to-point circuit exists between two G1000-4 cards.
Ethernet card ports must be enabled (in service, IS) for CARLOSS to occur. CARLOSS is declared after no signal is received for approximately 2.5 seconds.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CARLOSS (G-Series Ethernet) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port.
Step 2 If the fiber cable is correctly connected and attached, verify that the cable connects the card to another Ethernet device and is not misconnected to an STM-N card.
Step 3 If no misconnection to the STM-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.
Step 4 Verify that optical receive levels are within the normal range.
Step 5 If the alarm does not clear, use an Ethernet test set to determine that a valid signal is coming into the Ethernet port.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 6 If a valid Ethernet signal is not present and the transmitting device is operational, replace the fiber cable connecting the transmitting device to the Ethernet port.
Step 7 If the alarm does not clear and link autonegotiation is enabled on the G1000-4 port, but the autonegotiation process fails, the G1000-4 turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, 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 G1000-4 card.
b. Confirm that the attached Ethernet device configuration allows reception of flow control frames.
Step 8 If the alarm does not clear, disable and reenable the Ethernet port to attempt to remove the CARLOSS condition. Autonegotiation restarts.
Step 9 If the TPTFAIL is also reported, complete the "Clear the TPTFAIL (G-Series) Alarm" procedure. If the TPTFAIL alarm is not reported, continue to the next step.
Note When both alarms are reported, the reason for the condition could be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 10 If the TPTFAIL alarm was not reported, determine whether a terminal loopback has been provisioned on the port:
a. In node view, click the card to go to card view.
b. Click the Conditions tab and then click Retrieve Conditions.
c. If LPBKTERMINAL is listed for the port, a loopback is provisioned. Go to Step 11. If IS is listed, go to Step 12.
Step 11 If a loopback was provisioned, clear the loopback by following the "Clear a Loopback" procedure.
On the G1000-4 card, provisioning a terminal loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.
If the port is not set in LPBKTERMINAL, continue to Step 12.
Step 12 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm 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 A Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454 SDHs, and the Open System Interconnection/Target Identifier Address Resolution Protocol (OSI/TARP)-based equipment does not allow tunneling of the ONS 15454 SDH TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere on the row of the CARLOSS alarm.
b. Click Select Affected Circuits from the shortcut menu.
c. Record the information in the type and size columns of the highlighted circuit.
d. Examine the layout of your network and determine which ONS 15454 SDH and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 SDH at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet (traffic) card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The cross connect circuit will connect the Ethernet card to an STM-N card on the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 13 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure for the Ethernet card.
Step 14 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the Ethernet card.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 15 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.41 CARLOSS (ML-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Logical Object: L2SC
A CARLOSS alarm on the ML-Series Ethernet (traffic) card is the data equivalent of the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131. The Ethernet port has lost its link and is not receiving a valid signal.
CARLOSS for an ML-Series card occurs when the Ethernet port has been configured from the IOS command line interface (CLI) as a no-shutdown port and one of the following items also occurs:
•The cable is not properly connected to the near or far port
•Autonegotiation is failing
•The speed (10/100 ports only) is set incorrectly
For information about provisioning ML-Series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.
Clear the CARLOSS (ML-Series Ethernet) 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 IOS CLI. Autonegotiation restarts.
Step 6 If the alarm does not clear, perform a facility loopback on the ML-Series card using the "Create a Facility (Line) Loopback Circuit on a Destination DS-N or E-N Port" procedure on page 1-21.
Step 7 If the problem persists with the loopback installed, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 8 If the alarm does not clear, complete the "Physically Replace a Card" procedure.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.42 CASETEMP-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Case Temperature Degrade alarm occurs when a card detects a case temperature value outside the desired range (-5 to 65 degrees C or 23 to 149 degrees F).
Clear the CASETEMP-DEG Alarm
Step 1 If a FAN alarm is also reported, complete the "Clear the FAN Alarm" procedure.
Step 2 If no FAN alarm is reported, complete the "3.2.1 Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.43 CKTDOWN
•Critical (CR), Service-Affecting (SA)
•Logical Object: CKT
The Unified Control Plane (UCP) Circuit Down alarm applies to logical circuits created within the UCP between devices. CKTDOWN occurs when the there is signaling failure across a UCP interface. The failure can be caused by a number of things, such as failure to route the call within the core network. In that case, the alarm cannot be resolved from the ONS 15454 SDH edge device.
Clear the CKTDOWN Alarm
Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:
a. In node view, click the Provisioning > UCP > Neighbor tabs.
b. View the entries to find out whether the node you are trying to contact is listed.
c. The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that physical and logical accessibility.
d. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.
e. At the command prompt (C:\>), type:
ping {node-DNS-name | 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 looks similar but does not include the DNS name in the first line.
f. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.
g. If the ping was unsuccessful, you the following reply is repeated for each try:
A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.
Step 2 If the channel to neighbor has not been provisioned, or if you had to delete the channel, create one:
a. Click the Provisioning > UCP > Neighbor tabs.
b. Click Create.
c. In the Neighbor Discovery window, enter the node's DNS node name in the Neighbor Name field. Leave the Enable Discovery check box checked (default setting) if you want the neighbor to be discovered through the network.
d. Click OK.
The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If discovery is not successful, the column lists 0.0.0.0.
Step 3 If neighbor discovery is enabled, ensure that the neighbor node ID and remote Internet protocol (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's IP address.
Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.
a. Click the entry to select the neighbor IP address and click Delete.
b. If you get an error that does not allow you to delete the IPCC, you need to 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 IPCC had to be deleted, create the connection:
a. In the Provisioning > UCP > IPCC tabs, click Create.
b. In the Unified Control Plane Provisioning window, click Next.
c. If no IPCCs are listed, click Create.
d. In the Create New IPCC window, click one of the Regenerator Section DCC (SDCC) terminations in the SDCC list.
Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.
e. Click OK. The IPCC is listed as CCID 1 in the Unified Control Plane Provisioning window.
f. Click the neighbor to select it, and click Next.
g. Choose a UCP interface (for example Slot 5 for an STM-16 card, port 1) from the pull-down menu. The field default is the node where you are logged in.
h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.
i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab contains the neighbor's IP address.
Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:
a. Click the Interface tab. View the slot and port listed in the Interface column (for example, Slot 5 for an STM-16 card, port 1).
b. Compare the listed interface listed with the IPCC tab SDCC column entry.
Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.
Step 9 Click Next.
Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.
The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.
Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.
Step 12 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.44 CLDRESTART
•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 SDH is first powered up.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Clear the CLDRESTART Condition
Step 1 If the condition fails to clear after the card reboots, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 2 If the condition does not clear, complete the "Physically Replace a Card" procedure for the card.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.45 COMIOXC
•Critical (CR), Service-Affecting (SA)
•Logical Object: EQPT
The Input/Output Slot To Cross-Connect Communication Failure alarm can be caused by the cross-connect card. COMIOXC occurs when there is a communication failure for a traffic slot.
Clear the COMIOXC Alarm
Step 1 Complete the "Reset a Traffic Card in CTC" procedure on the reporting cross-connect card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 3 If the CTC reset does not clear the alarm, complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure.
Step 4 Complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting cross-connect card.
Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting cross-connect card.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.46 COMM-FAIL
•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 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.47 CONTBUS-A-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 7 (termed TCC-A) loses communication with the coprocessor on the same card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CONTBUS-A-18 Alarm
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 11 active.
Step 2 Wait approximately 10 minutes for theTCC2 in Slot 7 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 7 active.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.48 CONTBUS-B-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC2 Slot to TCC2 Slot alarm occurs when the main processor on the TCC2 card in Slot 11 (termed TCC-B) loses communication with the coprocessor on the same card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CONTBUS-B-18 Alarm on the TCC2 Card
Step 1 Position the cursor over the TCC2 card in Slot 11 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the TCC2 in Slot 7 active.
Step 2 Wait approximately 10 minutes for the TCC2 in Slot 11 to reset as the standby TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC2 card in Slot 7 and complete the "Reset Active TCC2 Card and Activate Standby Card" procedure to make the standby TCC2 in Slot 11 active.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.49 CONTBUS-IO-A
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Controller A To Shelf Slot Communication Failure alarm occurs when the TCC2 card in Slot 7 has lost communication with a traffic (electrical, optical, or Ethernet) card.
The CONTBUS-IO-A alarm can appear briefly when the ONS 15454 SDH switches to the standby TCC2 card. In the case of a switch, the alarm clears after the cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 to the reporting card. The physical path of communication includes the TCC2 card, the traffic card, and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CONTBUS-IO-A Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. In node view, click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, complete the "Clear the MEA (EQPT) Alarm" procedure.
Step 2 If only one card slot (other than TCC2 card) is reporting the alarm, complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 4 If the CTC reset does not clear the alarm, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 5 If all traffic (electrical, optical, or Ethernet) cards report this alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the standby TCC2 card does not reset itself.
Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.
Step 6 If the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.50 CONTBUS-IO-B
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Controller B To Shelf Slot Communication Failure alarm occurs when the TCC2 card in Slot 11 loses communication with a traffic (electrical, optical, or Ethernet) card.
The CONTBUS-IO-B alarm may appear briefly when the ONS 15454 SDH switches to the protect TCC2 card. In the case of a TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC2 card to the reporting card. The physical path of communication includes the TCC2 card, the traffic card, and the backplane.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf and that the card matches the type of card identified in that slot on CTC.
Step 2 If the reporting slot is the only one reporting the alarm, perform a CTC reset of the traffic (electrical, optical, or Ethernet) card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 4 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 5 If all cards—with the exception of the active TCC2—report the CONTBUS-B alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 6 If the reset card has not rebooted successfully, or the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into the Cisco Technical Support Website at http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.51 CTNEQPT-MISMATCH
•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 XCVXL card may be preprovisioned in Slot 10, but an XC10G may be physically installed.
Note Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although this situation may briefly occur during the upgrade process.
Note The cross-connect card you are replacing should not be the active card. (It can be in SBY state or otherwise not in use.)
If you upgrade a node to R4.6 and replace an XCVLX 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 SDH Procedure 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 XCVXL 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 Card" procedure for the mismatched card.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.52 CTNEQPT-PBPROT
•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 Slot 10 cross-connect card and the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, the TCC2 card, or the backplane.
Note If all traffic cards show the CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the standby TCC2 card. Do not physically reseat an active TCC2 card. Reseating the TCC2 disrupts traffic.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note This alarm automatically raises and clears when the Slot 10 cross-connect card is reseated.
Note It can take up to 30 minutes for software to be updated on a standby TCC2 card.
Clear the CTNEQPT-PBPROT Alarm
Step 1 Perform a CTC reset on the standby cross-connect card. Complete the "Reset a Traffic Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
If the cross-connect reset is not complete and error-free or if the TCC2 card reboots itself, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Step 3 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.
Step 4 Determine whether the card is an active card or standby card in a protection group. Click the node view Maintenance > Protection tabs, then click the protection group. The cards and their status are displayed in the list.
Step 5 If the reporting traffic (electrical, optical, or Ethernet) card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.
Step 6 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card.
•While the card resets, the FAIL LED blinks on the physical card and then all LEDs turn off.
•While the card resets, a white LED with the letters "LDG" appears on the reset card in CTC.
Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 Complete the "Clear a Protection Group External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the standby cross-connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 12 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic card.
Step 13 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.53 CTNEQPT-PBWORK
•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 Slot 8 cross-connect card the reporting traffic card. The cross-connect card and the reporting card are no longer communicating through the backplane. The problem exists in the cross-connect card, the reporting traffic card, or the backplane.
Note If all traffic cards show the CTNEEQPT-PBWORK alarm, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure for the active TCC2 card and then complete the "Remove and Reinsert (Reseat) a Card" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC2 card. Do not physically reseat an active TCC2 card; reseating disrupts traffic.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note This alarm automatically raises and clears when the Slot 8 cross-connect card is reseated.
Clear the CTNEQPT-PBWORK Alarm
Step 1 Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to move traffic from the active card to the standby cross-connect card.
Step 2 Complete the "Reset a Traffic Card in CTC" procedure for the reporting traffic (electrical, optical, or Ethernet) card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 4 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the standby cross-connect card.
Note The ACT/STBY LED of the active card is green. The ACT/STBY LED of the standby card is amber.
Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.
Step 6 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 7 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 If you switched traffic, complete the "Clear a Protection Group External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the cross-connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic card.
Step 12 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.54 DATAFLT
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Software Data Integrity Fault alarm occurs when the TCC2 exceeds its Flash memory capacity.
Caution When the system reboots, the last configuration entered is not saved.
Clear the DATAFLT Alarm
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of -free TAC numbers for your country.
2.7.55 DBOSYNC
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The Standby Database Out Of Synchronization alarm occurs when the standby TCC2 "To be Active" database does not synchronize with the active database on the active TCC2.
Caution If you reset the active TCC2 card while this alarm is raised, you will lose current provisioning.
Clear the DBOSYNC Alarm
Step 1 Save a backup copy of the active TCC2 database. Complete the "Back Up the Database" procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 2 Make a minor provisioning change to the active database to see if applying a provisioning change clears the alarm:
a. In node view, click the Provisioning > General > General tabs.
b. In the Description field, make a small change such as adding a period to the existing entry.
The change causes a database write but does not affect the node state. The write could take up to a minute.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.56 DSP-COMM-FAIL
•Major (MJ), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The DSP Communication Failure alarm indicates that there is a communications failure between an MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card microprocessor and the on-board DSP chip that controls the trunk (DWDM) port. This alarm typically occurs after a DSP code upgrade.
The alarm is temporary and does not require user action. The MXP card or TXP card microprocessor attempts to restore communication with the DSP chip until the alarm is cleared.
If the alarm remains for an extended period, The MXP card or TXP card raises the "DSP-FAIL" alarm on page 2-68 and could affect traffic.
Note DSP-COMM-FAIL is an informational condition. The alarm does not require troubleshooting.
2.7.57 DSP-FAIL
•Major (MJ), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The DSP Failure alarm indicates that the "DSP-COMM-FAIL" alarm on page 2-68 has persisted for an extended period on an MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card. It indicates that the card is faulty.
Clear the DSP-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure for the reporting MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.58 DS3-MISM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on the DS3i-N-12 card. The condition occurs when the provisioned line type and incoming signal frame format type do not match. For example, if the line type is set to C-BIT for a DS3i-N-12 card, and the incoming signal's frame format is detected as M13 or UNFRAMED, then the ONS 15454 SDH reports a DS3-MISM condition. The condition does not occur when the line type is set to AUTO PROVISION or UNFRAMED, so changing the line type to either of these options clears the condition. DS3-MISM also clears if the port state is set to OOS.
Setting the line type to AUTO PROVIS ION causes the ONS 15454 SDH to detect the received frame format and provision the port to use the matching frame format, either Unframed, M13, or C-BIT.
Clear the DS3-MISM Condition
Step 1 Display the CTC card view for the reporting DS3i-N-12 card.
Step 2 Click the Provisioning > Line tabs.
Step 3 For the row on the appropriate port, verify that the Line Type column is set to match the entry in the Expected Line Type column.
Step 4 If you want to change the line type because the line type entry does not match the expected incoming type, click the cell to reveal a pull-down menu and select the correct type.
Step 5 Click Apply.
Step 6 If you want to change the port state to OOS, click the Maintenance tab at the card view.
Step 7 Locate the correct port and click the State column to reveal a pull-down menu. Click OOS.
Step 8 If the condition does not clear after you verify that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 SDH matches the expected incoming signal.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 9 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.59 DUP-IPADDR
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The Duplicate IP Address alarm indicates that the alarmed node IP address is already in use within the same DCC area. When this happens, TC no longer reliably connects to either node. Depending on how the packets are routed, CTC may connect to either node (having the same IP address). If CTC has connected to both nodes before they shared the same address, it has two distinct NodeModel instances (keyed by the node ID portion of the MAC address).
Clear the DUP-IPADDR Alarm
Step 1 In node view, click the Provisioning > Network > General tabs.
Step 2 In the IP Address field, change the IP address to a unique number.
Step 3 Click Apply.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.60 DUP-NODENAME
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The Duplicate Node Name alarm indicates that the alarmed node's alphanumeric name is already being used within the same DCC area.
Clear the DUP-NODENAME Alarm
Step 1 In node view, click the Provisioning > General > General tabs.
Step 2 In the Node Name field, enter a unique name for the node.
Step 3 Click Apply.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.61 EHIBATVG
•Major (MJ), Service-Affecting (SA)
•Logical Object: PWR
The Extreme High Voltage Battery alarm occurs in a -48 VDC or -60 VDC environment when the voltage on a battery lead input exceeds the extreme high power threshold. This threshold, with a value of -56.7 VDC in -48 VDC systems or -72 VDC in -60 VDC systems, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the Cisco ONS 15454 SDH Procedure Guide.)
Clear the EHIBATVG Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying the battery leads.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting.
2.7.62 ELWBATVG
•Major (MJ), Service Affecting (SA)
•Logical Object: PWR
The Extreme Low Voltage Battery alarm occurs in a -48 VDC environment when the voltage on the battery feeds is extremely low or has been lost, and power redundancy is no longer guaranteed. The threshold for this alarm is -40.5 VDC in -48 VDC systems or -50 VDC in -60 VDC systems. The alarm clears when voltage remains above -40.5 VDC for 120 seconds.
Clear the ELWBATVG Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying the battery leads.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.63 EOC
•Major (MJ), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The DCC Termination Failure alarm occurs when the ONS 15454 SDH loses its DCC. The DCC is three bytes, D1 through D3, in the SDH overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 SDH uses the DCC on the section layer to communicate network management information.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning On the OC192 LR/STM64 LH 1550 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation could be emitted from the end of unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm 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 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note If a circuit shows an incomplete state when this alarm is raised, the logical circuit is in place. The circuit will be able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the EOC Alarm
Step 1 If an LOS alarm is also reported, complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear on the reporting node, verify the physical connections between the cards and the fiber-optic cables that are configured to carry DCC traffic.
Step 3 If the physical connections are correct and configured to carry DCC traffic, verify that both ends of the fiber span have in-service (IS) ports by verifying that the ACT LED on each STM-N card is illuminated.
Step 4 If the ACT LEDs on STM-N cards are illuminated, complete the "Verify or Create Node DCC Terminations" procedure to verify that the DCC is provisioned for the ports at both ends of the fiber span.
Step 5 Repeat Step 4 at the adjacent nodes.
Step 6 If DCC is provisioned for the ends of the span, verify that the STM-N port is active and in service:
a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.
A green LED indicates an active card. An amber LED indicates a standby card.
b. To determine whether the STM-N port is in service, double-click the card in CTC to display the card view.
c. Click the Provisioning > Line tabs.
•Verify that the State column lists the port as IS.
•If the State column lists the port as OOS, click the column and choose IS from the pull-down menu. Click Apply.
Step 7 If the STM-N card is in service, use an optical test set to determine whether or not there are signal failures on fiber terminations.
For specific procedures to use the test set equipment, consult the manufacturer.
Caution Using an optical test could disrupt service on the STM-N card. You may need to externally switch traffic carrying circuits over to a protection path.
Step 8 If no signal failures exist on terminations, measure power levels to verify that the budget loss is within the parameters of the receiver. See the "1.8.3 Optical Card Transmit and Receive Levels" section on page 1-95.
Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.
Resetting the active TCC2 switches control to the standby TCC2. If the alarm clears when the ONS 15454 SDH switches to the standby TCC2, you can assume that the original active TCC2 is the cause of the alarm.
Step 11 If TCC2 card reset does not clear the alarm, delete the problematic DCC termination:
a. Click the Provisioning > DCC/GCC/OSC tabs.
b. Highlight the problematic DCC termination.
c. Click Delete.
d. Click Yes in the confirmation dialog box.
Step 12 Recreate the DCC termination; refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 13 Verify that both ends of the DCC have been recreated at the optical ports.
Step 14 If the alarm has not cleared, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country. If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) a Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.64 EOC-L
The EOC-L alarm is not used in this platform in this release. It is reserved for future development.
2.7.65 EQPT
•Critical (CR), Service-Affecting (SA)
•Logical Objects: AIE, EQPT
An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card.
If the EQPT alarm occurs with a BKUPMEMP alarm, see the "BKUPMEMP" section. The BKUPMEMP procedure also clears the EQPT alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the EQPT Alarm
Step 1 Complete the "Reset a Traffic Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 3 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 4 If the physical reseat of the card fails to clear the alarm, complete the "Physically Replace a Card" procedure for the reporting card.
Caution Removing a card that currently 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.66 EQPT-MISS
•Critical (CR), Service-Affecting (SA)
•Logical Object: FAN
The Replaceable Equipment or Unit Missing alarm is reported against the fan-tray assembly unit. It indicates that the replaceable fan-tray assembly is missing or not fully inserted or that the ribbon cable connecting the AIE to the system board may be bad.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the EQPT-MISS Alarm
Step 1 If the alarm is reported against the fan, verify that the fan-tray assembly is present.
Step 2 If the fan-tray assembly is present, complete the "Remove and Reinsert Fan-Tray Assembly" procedure.
Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and complete the "Install the Fan-Tray Assembly" procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 4 If the alarm does not clear, replace the ribbon cable from the AIE to the system board with a known-good ribbon cable.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.67 ERROR-CONFIG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Error in Startup Configuration alarm applies to the ML-Series Ethernet cards. These cards process startup configuration files line by line. If one or more lines cannot be executed, the error causes the ERROR-CONFIG alarm. ERROR-CONFIG is not caused by hardware failure.
The typical reasons for an errored startup file are:
•The user stored the configuration for one type of ML-Series card in the database and then installed another type in its slot.
•The configuration file contained a syntax error on one of the lines.
For information about provisioning the ML-Series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide Release 4.6.
Clear the ERROR-CONFIG Alarm
Step 1 If you have a different type of ML-Series card specified in the startup configuration file than what you have installed, create the correct startup configuration.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.
Step 2 Upload the configuration file to the TCC2:
a. In node view, right-click the ML-Series card graphic.
b. Choose IOS Startup Config from the shortcut menu.
c. Click Local > TCC and navigate to the file location.
Step 3 Complete the "Reset a Traffic Card in CTC" procedure.
Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start an IOS CLI for the card:
a. Right click the ML-Series card graphic in node view.
b. Choose Open IOS Connection from the shortcut menu.
Note Open IOS Connection is not available unless the ML-Series card is physically installed in the shelf.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.
Step 5 Execute the CLI command copy run start. The command copies the new card configuration into the database and clears the alarm.
Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.68 ETH-LINKLOSS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The Rear Panel Ethernet Link Removed condition, if enabled in the network defaults, is raised under the following conditions:
•The node.network.general.AlarmMissingBackplane LAN field in NE defaults is enabled.
•The node is configured as a gateway network element (GNE).
•The backplane LAN cable is removed.
Clear the ETH-LINKLOSS Condition
Step 1 To clear this alarm, reconnect the backplane cable. Refer to the Cisco ONS 15454 SDH Procedure Guide for instructions to install this cable.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.69 E-W-MISMATCH
•Major (MJ), Service-Affecting (SA)
•Logical Object: STM-N
A Procedural Error Misconnect East/West Direction alarm occurs when nodes in a ring have an east slot misconnected to another east slot or a west slot misconnected to another west slot. In most cases, the user did not connect the fibers correctly or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but could change the traditional east-west node connection pattern of the ring.
Note The E-W-MISMATCH alarm also appears during the initial setup of a ring with its East-West slots and ports configured correctly. In this instance, the alarm clears itself shortly after the ring setup is complete.
Note The lower numbered slot on a node is traditionally labeled as the West slot. The higher numbered slot is traditionally labeled as the East slot. For example, Slot 6 is West and Slot 12 is East.
Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.
Clear the E-W-MISMATCH Alarm with a Physical Switch
Step 1 Diagram the ring setup, including nodes and spans, on a piece of paper or white board.
Step 2 In node view, click View > Go to Network View.
Step 3 Label each of the nodes on the diagram with the same name that appears on the network map.
Step 4 Right-click each span to reveal the node name/slot/port for each end of the span.
Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1 - Node2/Slot6/Port1 (2F MS-SPRing OC48, Ring Name=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.
Step 6 Repeat Steps 4 and 5 for each span on your diagram.
Step 7 Label the highest slot at each node east and the lowest slot at each node west.
Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span. Refer to the Cisco ONS 15454 SDH Procedure Guide for more information about configuring the system.
Step 9 If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation 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.
Step 10 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
Clear the E-W-MISMATCH Alarm in CTC
Step 1 Log into the misconnected node. A misconnected node has both ring fibers to its neighbor nodes misconnected.
Step 2 Click the Maintenance > MS-SPRing tabs.
Step 3 From the row of information for the fiber span, complete the "Identify a Ring Name or Node ID Number" procedure to identify the node ID, ring name, and the slot and port in the East Line list and West Line columns. Record the above information.
Step 4 Click View > Go to Network View.
Step 5 Delete and recreate the MS-SPRing:
a. Click the Provisioning > MS-SPRing tabs.
b. Click the row from Step 3 to select it and click Delete.
c. Click Create MS-SPRing.
d. Fill in the ring name and node ID from the information collected in Step 3.
e. Click Finish in the MS-SPRing Creation window.
Step 6 Display node view and click the Maintenance > MS-SPRing tabs.
Step 7 Change the West Line pull-down menu to the slot you recorded for the East Line in Step 3.
Step 8 Change the East Line pull-down menu to the slot you recorded for the West Line in Step 3.
Step 9 Click OK.
Step 10 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.70 EXCCOL
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Excess Collisions on the LAN alarm indicates that too many collisions are occurring between data packets on the network management LAN, and communications between the ONS 15454 SDH and CTC could be affected. The network management LAN is the data network connecting the workstation running the CTC software to the TCC2 card. The problem causing the alarm is external to the ONS 15454 SDH.
Troubleshoot the network management LAN connected to the TCC2 card for excess collisions. You may need to contact the system administrator of the network management LAN to accomplish the following steps.
Clear the EXCCOL Alarm
Step 1 Verify that the network device port connected to the TCC2 card has a flow rate set to 10 Mb, half-duplex.
Step 2 If the alarm does not clear, troubleshoot the network device connected to the TCC2 card and the network management LAN.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.71 EXERCISE-RING-FAIL
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Exercise Ring command issues ring protection switching of the requested channel without completing the actual bridge and switch. The EXERCISE-RING-FAIL condition is raised if the command was issued and accepted but the exercise did not take place.
Note If the exercise command gets rejected due to the existence of a higher priority condition in the ring, EXERCISE-RING-FAIL is not reported.
Clear the EXERCISE-RING-FAIL Condition
Step 1 Look for and clear, if present, the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131, the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, or MS-SPRing alarms.
Step 2 Reissue the Exercise Ring command:
a. In node view, click the Maintenance > MS-SPRing tabs.
b. Click the row of the affected ring under the West Switch column.
c. Select Exercise Ring in the pull-down menu.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.72 EXERCISE-SPAN-FAIL
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Exercise Span command issues span switching of the requested channel without completing the actual bridge and switch. The EXERCISE-SPAN-FAILED alarm is raised if the command was issued and accepted but the exercise did not take place.
Note If the exercise command gets rejected due to the existence of a higher priority condition in the span or ring, EXERCISE-SPAN-FAIL is not reported.
Clear the EXERCISE-SPAN-FAIL Condition
Step 1 Look for and clear, if present, the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131, the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135, or MS-SPRing alarms.
Step 2 Reissue the Exercise Span command:
a. In node view, click the Maintenance > MS-SPRing tabs.
b. Determine whether the card you would like to exercise is the west card or the east card.
c. Click the row of the affected span under the East Switch or West Switch column.
d. Choose Exercise Span from the pull-down menu.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.73 EXT
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: ENV
An External Facility alarm is detected externally from the node because an environmental alarm is present. For example, an open door or flooding can cause the alarm.
Clear the EXT Alarm
Step 1 In node view, double-click the MIC-A/P card to display the card view.
Step 2 Click the Maintenance tab to gather further information about the EXT alarm.
Step 3 Perform your standard operating procedure for this environmental condition.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.74 EXTRA-TRAF-PREEMPT
•Major (MJ), Service-Affecting (SA)
•Logical Object: STM-N
An Extra Traffic Preempted alarm occurs on STM-N cards in two-fiber and four-fiber MS-SPRings because low-priority traffic directed to the protect system has been preempted by a working system protection switch.
Clear the EXTRA-TRAF-PREEMPT Alarm
Step 1 Verify that the protection switch has occurred by verifying that the Conditions window shows the switch.
Step 2 If a ring switch has occurred, clear the alarm on the working system by following the appropriate alarm procedure in this chapter. For more information about protection switches, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country to report a service-affecting problem.
2.7.75 E3-ISD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The E3 Idle condition indicates that the E3-12 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. E3-ISD occurs when the transmitting card is OOS-MNT. E3-ISD is resolved when the OOS condition ends.
Note E3-ISD is an informational condition. The condition does not require troubleshooting.
2.7.76 FAILTOSW
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, EQPT, STM-N
The Failure to Switch to Protection condition occurs when a working electrical or optical (traffic) card cannot switch to the protect card in a 1:N, Y-cable, or splitter protection group because another working electrical or optical card with a higher priority alarm has switched to the protect card.
Clear the FAILTOSW Condition
Step 1 Look up and troubleshoot the higher-priority alarm. Clearing the higher-priority condition frees the 1:N card and clears the FAILTOSW.
Note A higher priority alarm is an alarm raised on the working electrical or optical (traffic) card using the 1:N card protection group. The working electrical or optical (traffic) card is reporting an alarm but not reporting a FAILTOSW condition.
Step 2 If the condition does not clear, replace the working electrical or optical card that is reporting the higher priority alarm by following the "Physically Replace a Card" procedure. The working card is the one that is using the 1:N card protection and is not reporting FAILTOSW.
Replacing the working electrical or optical card that is reporting the higher-priority alarm allows traffic to revert to the working slot and the card reporting the FAILTOSW to switch to the protect card.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.77 FAILTOSW-HO
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: HPMon
The Failure to Switch to Protection High Order Path condition occurs when an active STM-N card carrying high-order (VC-4) traffic cannot switch to the standby card because another electrical (traffic) card with a higher priority alarm is switched over and is monopolizing the card.
Clear the FAILTOSW-HO Condition
Step 1 Look up and clear the higher priority alarm. Clearing this alarm frees the standby card and clears the FAILTOSW-HO condition.
Note A higher priority alarm is an alarm raised on the active STM-N card using the protection group. The active STM-N card is reporting an alarm, but not reporting a FAILTOSW-HO condition.
Step 2 If the condition does not clear, replace the active STM-N card that is reporting the higher priority alarm. Complete the "Physically Replace a Card" procedure. Replacing the active STM-N card that is reporting the higher priority alarm allows traffic to revert to the active slot. The standby card is freed to take over traffic from the card that reported the lower priority alarm and the FAILTOSW-HO condition.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.78 FAILTOSW-LO
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: LPMon
The Failure to Switch to Protection Low-Order Path condition occurs when a working (or protect) STM-N card carrying low-order (VC-12 or VC-3) traffic cannot switch to the protect (or working) card because another working STM-N card with a higher priority alarm is switched over and is monopolizing the protect card.
Clear the FAILTOSW-LO Condition
Step 1 Complete the "Clear the FAILTOSW-HO Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.79 FAILTOSWR
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Fail to Switch to Protection Ring condition occurs when a ring switch did not complete because of internal APS problems.
FAILTOSWR clears when one of the following situations occurs:
•a physical card pull of the active TCC card (done under TAC supervision)
•a node power cycle
•a higher priority event, such as an external switch command occurs;
•the next ring switch succeeds;
•or, the cause of the APS switch such as the "SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)" condition on page 2-182 or the "SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)" condition on page 2-185 clears.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation 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 FAILTOSWR Condition on a Four-Fiber MS-SPRing Configuration
Step 1 Perform the EXERCISE RING command on the reporting card:
a. Click the Maintenance > MS-SPRing tabs.
b. Click the row of the affected ring under the West Switch column.
c. Select Exercise Ring in the pull-down menu.
Step 2 If the condition does not clear, in node view, click View > Go to Network View.
Step 3 Look for alarms on STM-N cards that make up the ring or span and troubleshoot these alarms.
Step 4 If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node.
Step 5 Click the Maintenance > MS-SPRing tabs.
Step 6 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-N cards and ports are active and in service:
a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.
A green LED indicates an active card. An amber LED indicates a standby card.
b. Double-click the card in CTC to display the card view.
c. Click the Provisioning > Line tabs.
d. Verify that the State column lists the port as IS.
e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.
Step 7 If the STM-N cards and ports are active and in service, verify fiber continuity to the ports on the recorded cards.
Step 8 If fiber continuity to the ports is okay, use an optical test set to verify that a valid signal exists on the line.
For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
Caution Using an optical test set disrupts service on the optical (traffic) card. It could be necessary to manually switch traffic carrying circuits over to a protection path.
Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the STM-N card's receiver specifications. The "1.8.3 Optical Card Transmit and Receive Levels" section on page 1-95 lists these specifications.
Step 11 Repeat Steps 7 to 10 for any other ports on the card.
Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Card" procedure for the protect standby STM-N 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 13 If the condition does not clear after you replace the MS-SPRing cards on the node one by one, repeat
Steps 4 to 12 for each of the nodes in the ring.
Step 14 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.80 FAILTOSWS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber MS-SPRing, a failed span switch initiates a ring switch. If the ring switch occurs, the FAILTOSWS condition does not appear. If the ring switch does not occur, the FAILTOSWS condition appears. FAILTOSWS clears when one of the following situations occurs:
•a physical card pull of the active TCC card (done under TAC supervision)
•a node power cycle
•a higher priority event such as an external switch command occurs;
•the next span switch succeeds;
•or, the cause of the APS switch such as the "SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E)" condition on page 2-182 or the "SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)" condition on page 2-185 clears.
Clear the FAILTOSWS Condition
Step 1 Perform the EXERCISE SPAN command on the reporting card:
a. Click the Maintenance > MS-SPRing tabs.
b. Determine whether the card you would like to exercise is the west card or the east card.
c. Click the row of the affected span under the East Switch or West Switch column.
d. Select Exercise Span in the pull-down menu.
Step 2 If the condition does not clear, in node view, click View > Go to Network View.
Step 3 Look for alarms on STM-N cards that make up the ring or span and troubleshoot these alarms.
Step 4 If clearing other alarms does not clear the FAILTOSWR condition, log into the near-end node.
Step 5 Click the Maintenance > MS-SPRing tabs.
Step 6 Record the STM-N cards listed under West Line and East Line. Ensure that these STM-N cards and ports and port are active and in service:
a. Confirm that the STM-N card shows a green LED in CTC or on the physical card.
A green LED indicates an active card. An amber LED indicates a standby card.
b. Double-click the card in CTC to display the card view.
c. Click the Provisioning > Line tabs.
d. Verify that the State column lists the port as IS.
e. If the State column lists the port as OOS, click the column and choose IS. Click Apply.
Step 7 If the STM-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.
Step 8 If fiber continuity to the ports is okay, use an optical test set to verify that a valid signal exists on the line.
For specific procedures to use the test set equipment, consult the manufacturer. Test the line as close to the receiving card as possible.
Caution Using an optical test set disrupts service on the optical (traffic) card. It could be necessary to manually switch traffic carrying circuits over to a protection path.
Step 9 If the signal is valid, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 10 If cleaning the fiber does not clear the condition, verify that the power level of the optical signal is within the STM-N card's receiver specifications.
Step 11 Repeat Steps 6 through 10 for any other ports on the card.
Step 12 If the optical power level for all STM-N cards is within specifications, complete the "Physically Replace a Card" procedure for the protect standby STM-N 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 13 If the condition does not clear after you replace the MSSP-Ring cards on the node one by one, repeat
Steps 4 through 12 for each of the nodes in the ring.
Step 14 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.81 FAN
•Critical (CR), Service-Affecting (SA)
•Logical Object: FAN
The Fan Failure alarm indicates a problem with the fan-tray assembly. When the fan-tray assembly is not fully functional, the temperature of the ONS 15454 SDH can rise above its normal operating range. The fan-tray assembly contains six fans and needs a minimum of five working fans to properly cool the ONS 15454 SDH. However, even with five working fans, the fan-tray assembly could need replacement because a sixth working fan is required for extra protection against overheating.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the FAN Alarm
Step 1 Determine whether the air filter needs replacement. Complete the "3.2.1 Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.
Step 2 If the filter is clean, complete the "Remove and Reinsert Fan-Tray Assembly" procedure.
Note The fan-tray assembly should run immediately when correctly inserted.
Step 3 If the fan does not run or the alarm persists, complete the "3.4 Replace the Fan-Tray Assembly" procedure on page 3-9.
Step 4 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.82 FANDEGRADE
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: FAN
The Partial Fan Failure Speed Control Degradation alarm occurs if fan speed for one of the fans in the fan-tray assembly falls under 500 RPM when read by a tachometry counter.
Clear the FANDEGRADE Alarm
Step 1 Complete the "Clear the FAN Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.83 FE-AIS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The Far-End AIS condition accompanies the "AIS" condition on page 2-25 at the far-end node. An AIS usually occurs in conjunction with a downstream "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input 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 FE-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.84 FE-DS1-MULTLOS
The FE-DS1-MULTLOS alarm is not used in this platform in this release. It is reserved for future development.
2.7.85 FE-DS1-NSA
The FE-DS1-NSA alarm is not used in this platform in this release. It is reserved for future development.
2.7.86 FE-DS1-SA
The FE-DS1-SA alarm is not used in this platform in this release. It is reserved for future development.
2.7.87 FE-DS1-SNGLLOS
The FE-DS1-SNGLLOS alarm is not used in this platform in this release. It is reserved for future development.
2.7.88 FE-DS3-NSA
The FE-DS3-NSA alarm is not used in this platform in this release. It is reserved for future development.
2.7.89 FE-DS3-SA
The FE-DS3-SA alarm is not used in this platform in this release. It is reserved for future development.
2.7.90 FEC-MISM
•Major (MJ), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The forward error correction (FEC) Mismatch alarm occurs if one end of a span using MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards is configured to use FEC and the other is not. FEC-MISM is related to ITU-T G.709 and is only raised against a trunk port.
Clear the FEC-MISM Alarm
Step 1 Double-click the MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card.
Step 2 Click the Provisioning > OTN > OTN Lines tab.
Step 3 Check the FEC column check box.
Step 4 Verify that the far-end card is configured the same way by repeating Step 1 through Step 3.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.91 FE-EQPT-NSA
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The Far End Common Equipment Failure condition occurs when a non-service affecting equipment failure is detected on the far-end DS-3. The prefix FE occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-EQPT-NSA condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the FE-EQPT-NSA Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.92 FE-E1-MULTLOS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End Multiple E-1 LOS Detected on an E1-42 card condition occurs when multiple inputs detect an E-1 signal loss on a far-end E1-42 port at the far-end node. The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-MULTLOS condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-E1-MULTLOS Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.93 FE-E1-NSA
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End E1 Equipment Failure Non-Service Affecting condition occurs when a far-end E-1 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-NSA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-E1-NSA Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.94 FE-E1-SA
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End E-1 Equipment Failure Service Affecting condition occurs when a far-end E-1 equipment failure occurs and affects service because traffic is unable to switch to the protect port.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-SA alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-E1-SA Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.95 FE-E1-SNGLLOS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End Single E-1 LOS on the E-3 condition occurs when one of the E3-12 ports on the far end detects an LOS. The prefix FE in an alarm or condition means the main alarm is occurring at the far-end node and not at the node reporting the FE-E1-SNGLLOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-E1-SNGLLOS Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.96 FE-E3-NSA
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End E3 Equipment Failure Non-Service Affecting condition occurs when a far-end E-3 equipment failure occurs, but does not affect service because the port is protected and traffic is able to switch to the protect port.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-E3-NSA condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-E3-NSA Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.97 FE-E3-SA
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-3
The Far End E3 Equipment Failure Service Affecting condition occurs when a far-end E-3 equipment failure occurs and affects service because traffic is unable to switch to the protect port.
The prefix FE in an alarm or condition means the main alarm is occurring at the far-end node and not at the node reporting the FE condition. Troubleshoot the FE alarm by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-E3-SA Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the card in Slot 12 of Node 1 could link to the main AIS condition from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for troubleshooting instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.98 FE-FRCDWKSWPR-RING
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far End Ring Working Facility Forced to Switch to Protection condition occurs from a far-end node when a ring is forced from working to protect using the FORCE RING command.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-FRCDWKSWPR-RING Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.99 FE-FRCDWKSWPR-SPAN
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far End Working Facility Forced to Switch to Protection Span condition occurs from a far-end node when a span on a four-fiber MS-SPRing is forced from working to protect using the FORCE SPAN command.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-FRCDWKSWPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-FRCDWKSWPR-SPAN Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could link to the main AIS condition from an STM-16 card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.100 FE-IDLE
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The Far End Idle condition occurs when a far-end node detects an idle DS-3 signal.
The prefix FE in an alarm or condition occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-IDLE condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. Both alarms clear when the main alarm clears.
Clear the FE-IDLE Condition
Step 1 To troubleshoot the FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Clear the main alarm. Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.101 FE-LOCKOUTOFPR-ALL
The FE-LOCKOUTOFPR-ALL condition is not used in this platform in this release. It is reserved for future development.
2.7.102 FE-LOCKOUTOFPR-RING
The FE-LOCKOUTOFPR-RING condition is not used in this platform in this release. It is reserved for future development.
2.7.103 FE-LOCKOUTOFPR-SPAN
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far-End Lockout of Protection Span condition occurs when an MS-SPRing span is locked out of the protection system from a far-end node using the LOCKOUT SPAN command.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-LOCKOUTOFPR-SPAN condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-LOCKOUTOFPR-SPAN Condition
Step 1 To troubleshoot the FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.104 FE-LOCKOUTOFWK-RING
The FE-LOCKOUTOFWK-RING condition is not used in this platform in this release. It is reserved for future development.
2.7.105 FE-LOCKOUTOFWK-SPAN
The FE-LOCKOUTOFWK-RING condition is not used in this platform in this release. It is reserved for future development.
2.7.106 FE-LOF
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The Far End LOF condition occurs when a far-end node reports a DS-3 LOF.
The prefix FE in an alarm or condition occurs when the main alarm is occurring at the far-end node and not at the node reporting the FE-LOF condition. Troubleshoot the FE alarm or condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-LOF Condition
Step 1 To troubleshoot an FE condition, determine which node and card link directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that links directly to the card reporting the FE condition.
Step 3 Complete the "Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm" procedure. The procedure also applies to FE-LOF.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.107 FE-LOS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-3
The Far End LOS condition occurs when a far-end node reports a DS-3 LOS.
The prefix FE occurs when the main alarm is occurring at the far-end node, and not at the node reporting the FE-LOS condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. The secondary alarms or conditions clear when the main alarm clears.
Clear the FE-LOS Condition
Step 1 To troubleshoot the FE condition, determine which node and card is linked directly to the card reporting the FE condition. For example, an FE condition on a card in Slot 12 of Node 1 could relate to a main alarm from a card in Slot 6 of Node 2.
Step 2 Log into the node that is linked directly to the card reporting the FE condition.
Step 3 Complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.108 FE-MANWKSWPR-RING
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far End Ring Manual Switch of Working Facility to Protect condition occurs when an MS-SPRing working ring is switched from working to protect at a far-end node using the MANUAL RING command.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the FE-MANWKSWPR-RING condition. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-MANWKSWPR-RING Condition
Step 1 To troubleshoot an FE condition, determine which node and card is linked directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could relate to the main AIS condition from an STM-16 card in Slot 6 of Node 2.
Step 2 Log into the node that is linked directly to the card reporting the FE condition.
Step 3 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.109 FE-MANWKSWPR-SPAN
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far-End Span Manual Switch Working Facility to Protect condition occurs when an MS-SPRing span is switched from working to protect at the far-end node using the MANUAL SPAN command.
The prefix FE means the main alarm is occurring at the far-end node and not at the node reporting the alarm. Troubleshoot the FE condition by troubleshooting the main alarm at its source. Both the alarms or conditions clear when the main alarm clears.
Clear the FE-MANWKSWPR-SPAN Condition
Step 1 To troubleshoot an FE condition, determine which node and card is linked directly to the card reporting the FE alarm. For example, an FE-AIS condition from the STM-16 card in Slot 12 of Node 1 could relate to the main AIS condition from an STM-16 card in Slot 6 of Node 2.
Step 2 Log into the node that is linked directly to the card reporting the FE condition.
Step 3 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.110 FEPRLF
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Far-End Protection Line Failure alarm occurs when there was an APS channel SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N) condition on the protect card coming into the node.
Note The FEPRLF alarm only occurs on the ONS 15454 SDH when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration.
Clear the FEPRLF Alarm on an MS-SPRing
Step 1 To troubleshoot the FE alarm, determine which node and card is linked directly to the card reporting the FE alarm.
For example, an FE alarm or condition on a card in Slot 16 of Node 1 could relate to a main alarm from a card in Slot 16 in Node 2.
Step 2 Log into the node that is linked directly to the card reporting the FE alarm.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for instructions.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.111 FE-SDPRLF
•Default Severity: Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STMN
The Far-End Protection Signal Degrade Line Failure alarm occurs when there was an APS channel SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) condition on the protect card coming into the node.
Note The FE-SDPRLF alarm only occurs on the ONS 15454 when bidirectional protection is used on optical (traffic) cards in a 1+1 configuration.
Clear the FE-SDPRLF Alarm on an MS-SPRing
Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition" procedure for the reporting node.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.112 FIBERTEMP-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Fiber Temperature Degrade alarm occurs on amplifier cards (OPT-BST and OPT-PRE) when the fiber temperature value rises above or falls below the desired range due to an internal heater control circuit failure.
Clear the FIBERTEMP-DEG Alarm
Step 1 This alarm does not immediately affect traffic. But to clear the alarm, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.113 FORCED-REQ
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EQPT, HPMon, LPMon
The Force Switch Request condition occurs when you enter the FORCE command on a span or card to force traffic from a working card to a protection card or vice versa. You do not need to clear this condition if you want the Force switch to remain.
Clear the FORCED-REQ Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.114 FORCED-REQ-RING
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Force Switch Request Ring condition applies to optical trunk (span) cards when the FORCE RING command is applied to two-fiber and four-fiber MS-SPRings to move traffic from working to protect.
Clear the FORCED-REQ-RING Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.115 FORCED-REQ-SPAN
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Force Switch Request Span condition applies to optical trunk (span) cards in four-fiber MS-SPRings when the FORCE SPAN command is applied to an MS-SPRing to force traffic from working to protect or from protect to working.
Clear the FORCED-REQ-SPAN Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.116 FRCDSWTOINT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NESync
The Force Switch to Internal Timing condition occurs when the user issues a FORCE command to switch to an internal timing source.
Note FRCDSWTOINT is an informational condition. The condition does not require troubleshooting.
2.7.117 FRCDSWTOPRI
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTSync, NESync
The Force Switch to Primary Timing Source condition occurs when the user issues a FORCE command to switch to the primary timing source.
Note FRCDSWTOPRI is an informational condition. The condition does not require troubleshooting.
2.7.118 FRCDSWTOSEC
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTSync, NESync
The Force Switch to Second Timing Source condition occurs when the user issues a FORCE command to switch to the second timing source.
Note FRCDSWTOSEC is an informational condition. The condition does not require troubleshooting.
2.7.119 FRCDSWTOTHIRD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTSync, NESync
The Force Switch to Third Timing Source condition occurs when the user issues a FORCE command to switch to the third timing source.
Note FRCDSWTOTHIRD is an informational condition. The condition does not require troubleshooting.
2.7.120 FRNGSYNC
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NESync
The Free Running Synchronization Mode condition occurs when the reporting ONS 15454 SDH is in free-run synchronization mode. External timing sources have been disabled and the node is using its internal clock, or the ONS 15454 SDH has lost its designated BITS timing source. After the 24-hour holdover period expires, timing slips could begin to occur on an ONS 15454 SDH relying on an internal clock.
Note If the ONS 15454 SDH is configured to operate from its internal clock, disregard the FRNGSYNC condition.
Clear the FRNGSYNC Condition
Step 1 If the ONS 15454 SDH is configured to operate from an external timing source, verify that the BITS timing source is valid. Common problems with a BITS timing source include reversed wiring and bad timing cards. Refer to the Cisco ONS 15454 SDH Reference Manual for more information about timing.
Step 2 Clear alarms related to the failures of the primary and secondary reference sources, such as the "SYNCPRI" alarm on page 2-199 and the "SYSBOOT" alarm on page 2-202.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.121 FSTSYNC
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NESync
A Fast Start Synchronization mode alarm occurs when the ONS 15454 SDH is choosing a new timing reference. The previous timing reference has failed.
The FSTSYNC alarm disappears after approximately 30 seconds. If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Note FSTSYNC is an informational alarm. The condition does not require troubleshooting.
2.7.122 FULLPASSTHR-BI
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Bidirectional Full Pass-Through Active condition occurs on a nonswitching node for an MS-SPRing when the protect channels on the node are active and carrying traffic and there is a change in the receive K byte from No Request.
Clear the FULLPASSTHR-BI Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.123 GAIN-HDEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Optical Amplifier Gain Degrade High alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE cards on the Line-1 TX port when an internal problem in the card keeps the gain level from maintaining the setpoint.
Clear the GAIN-HDEG Alarm
Step 1 This alarm does not immediately affect traffic, but eventually to clear the alarm you will need to complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.124 GAIN-HFAIL
•Critical (CR), Service-Affecting (SA)
•Logical Object: E-4
The Optical Amplifier Gain High Fail alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE cards on the Line-1 TX port when an internal problem causes the card to fail by forcing the gain level to consistently exceed the setpoint.
Clear the GAIN-HFAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.125 GAIN-LDEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Optical Amplifier Gain Degrade Low alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE cards on the Line-1 TX port when an internal problem in the card keeps the gain level from reaching the setpoint.
Clear the GAIN-LDEG Alarm
Step 1 This alarm does not immediately affect traffic. But eventually, to clear the alarm, you will need to complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.126 GAIN-LFAIL
•Critical (CR), Service-Affecting (SA)
•Logical Object: E-4
The Optical Amplifier Gain Fail Low alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE cards on the Line-1 TX port when an internal problem in the card causes the card to fail by preventing the gain level from reaching the setpoint.
Clear the GAIN-LFAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.127 GCC-EOC
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The GCC Embedded Operation Channel Failure alarm applies to the OTN communication channel for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. The GCC-EOC is raised when the channel cannot operate.
Clear the GCC-EOC Alarm
Step 1 Complete the "Clear the EOC Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.128 GE-OOSYNC
•Critical (CR), Service-Affecting (SA)
•Logical Objects: DWDM Client, DWDM Trunk
The Gigabit Ethernet Out of Synchronization alarm applies to TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when the Gigabit Ethernet signal is out of synchronization and is very similar to the SDH LOS alarm. This alarm can occur when you try to input an SDH signal to the TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card. A signal is present, so there is no CARLOSS alarm, but it is not correctly formatted for the card and so will raise the GE-OOSYNC alarm.
Clear the GE-OOSYNC Alarm
Step 1 Ensure that the incoming signal is provisioned with the correct physical-layer protocol.
Step 2 Ensure that the line is provisioned with the correct line speed (10 Gbps).
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.129 HIBATVG
•Major (MJ), Service-Affecting (SA)
•Logical Object: PWR
The High Voltage Battery alarm occurs in a -48 VDC environment when a battery lead's input voltage exceeds the high power threshold. This threshold, with a default value of -52 VDC, is user-provisionable. The alarm remains raised until the voltage remains under the threshold for 120 seconds. (For information about changing this threshold, refer to the Cisco ONS 15454 SDH Procedure Guide.)
Clear the HIBATVG Alarm
Step 1 The problem is external to the ONS equipment. Troubleshoot the power source supplying the battery leads.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.130 HI-LASERBIAS
•Minor (MN), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Equipment High Transmit Laser Bias Current alarm is raised against the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card laser performance. The alarm indicates that the card laser has reached the maximum laser bias tolerance.
Laser bias typically starts at about 30 percent of the manufacturer's maximum laser bias specification and increases as the laser ages. If the HI-LASERBIAS alarm threshold is set at 100 percent of the maximum, the laser's usability has ended. If the threshold is set at 90 percent of the maximum, the card is still usable for several weeks or months before it needs to be replaced.
Clear the HI-LASERBIAS Alarm
Step 1 Complete the "Clear the LASEREOL Alarm" procedure. Replacement is not urgent and can be scheduled during a maintenance window.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.131 HI-RXPOWER
•Minor (MN), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Equipment High Receive Power alarm is an indicator of the optical signal power that is transmitted to the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card. HI-RXPOWER occurs when the measured optical power of the received signal exceeds the threshold. The threshold value is user-provisionable.
Clear the HI-RXPOWER Alarm
Step 1 Find out whether gain (the amplification power) of any amplifiers has been changed. The modification also causes the channel power to need adjustment.
Step 2 Find out whether channels have been dropped from the fiber. Increasing or decreasing channels can affect power. If channels have been dropped, the power levels of all channels must be adjusted.
Note If the card is part of an amplified dense wavelength division multiplexing system, dropping channels on the fiber affects the transmission power of each channel more than dropping would in an unamplified system.
Step 3 At the transmit end of the errored circuit, decrease the transmit power level within safe limits.
Step 4 If neither of these problems cause the HI-RXPOWER alarm, there is a slight possibility that another wavelength is drifting on top of the alarmed signal. In this case, the receiver gets signals from two transmitters at the same time and data alarms would be present. If wavelengths are drifting, the data will be garbled and receive power will increase by about +3 dB.
Step 5 If the alarm does not clear, add fiber attenuators to the receive ports. Start with low-resistance attenuators and use stronger ones as needed, depending on factors such as the transmission distance according to standard practice.
Step 6 If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, do a facility loopback on the transmit and receive ports with known-good loopback cable. Complete the "1.2.1 Perform a Facility (Line) Loopback on a Source DS-N or E-N Port (West to East)" procedure on page 1-7.
Step 7 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 8 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.132 HITEMP
•Critical (CR), Service-Affecting (SA) for NE
•Minor (MN), Non-Service Affecting (NSA) for EQPT
•Logical Objects: EQPT, NE
The High Temperature alarm occurs when the temperature of the ONS 15454 SDH is above 50 degrees C (122 degrees F).
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the HITEMP Alarm
Step 1 View the temperature displayed on the ONS 15454 SDH LCD front panel. For an illustration of the LCD panel, refer to Figure 2-1.
Step 2 Verify that the environmental temperature of the room is not abnormally high.
Step 3 If the room temperature is not abnormal, physically ensure that nothing prevents the fan-tray assembly from passing air through the ONS 15454 SDH.
Step 4 If airflow is not blocked, physically ensure that blank faceplates fill the ONS 15454 SDH empty slots. Blank faceplates help airflow.
Step 5 If faceplates fill the empty slots, determine whether the air filter needs replacement. Complete the "3.2.1 Inspect, Clean, and Replace the Reusable Air Filter" procedure on page 3-5.
Step 6 If the filter is clean, complete the "Remove and Reinsert Fan-Tray Assembly" procedure.
Note The fan-tray assembly should run immediately when correctly inserted.
Step 7 If the fan does not run or the alarm persists, complete the "3.4 Replace the Fan-Tray Assembly" procedure on page 3-9.
Step 8 If the replacement fan-tray assembly does not operate correctly, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information. If the alarm does not clear, log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service affecting problem.
2.7.133 HI-TXPOWER
•Minor (MN), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Equipment High Transmit Power alarm is an indicator on the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G card, or MXP_2.5G_10G card transmitted optical signal power. HI-TXPOWER occurs when the measured optical power of the transmitted signal exceeds the threshold. The threshold value is user-provisionable.
Clear the HI-TXPOWER Alarm
Step 1 In node view, display the card view for the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card.
Step 2 Click the Provisioning > Optical Thresholds tabs.
Step 3 Decrease (change toward the negative direction) the TX Power High column value by 0.5 dBm.
Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.134 HLDOVRSYNC
•Major (MJ), Service-Affecting (SA)
•Logical Object: NESync
The Holdover Synchronization Mode alarm indicates a loss of the primary or secondary timing reference. Timing reference loss occurs when line coding on the timing input is different from the configuration on the ONS 15454 SDH. HLDOVRSYNC also usually occurs during the selection of a new node reference clock. The HLDOVRSYNC alarm indicates that the ONS 15454 SDH has gone into holdover and is using the ONS 15454 SDH internal reference clock, which is a Stratum 3-level timing device. The alarm clears when primary or secondary timing is reestablished.
Clear the HLDOVRSYNC Alarm
Step 1 Clear additional events that relate to timing, such as:
•FRNGSYNC
•FSTSYNC
•HLDOVRSYNC
•LOF (DS-3, E-1, E-4, STM-N, STM1-E)
•LOS (DS-3, E-1, E-3, STM-N, STM-1E)
•MANSWTOINT
•MANSWTOPRI
•MANSWTOSEC
•MANSWTOTHIRD
•SYSBOOT
•SWTOSEC
•SWTOTHIRD
•SYNC-FREQ
•SYNCPRI
•SYSBOOT
Step 2 Reestablish a primary and secondary timing source according to local site practice.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.135 HP-RFI
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: HPMon
The High-Order Remote Failure Indication (RFI) condition indicates that there is a remote failure indication in the high-order (VC-4 or VC-3) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The HP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the HP-RFI condition in the reporting node.
Clear the HP-RFI Condition
Step 1 Log into the node at the far-end node of the reporting ONS 15454 SDH.
Step 2 Determine whether there are any alarms, especially the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for instructions.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.136 HP-TIM
•Critical (CR), Service-Affecting (SA) for HPTerm
•Minor (MN), Non-Service Affecting (NSA) for HPMon
•Logical Objects: HPMon, HPTerm
The TIM High-Order TIM Failure alarm indicates that the trace identifier J1 byte of the high-order (VC-4 or VC-3) overhead is faulty. HP-TIM occurs when there is a mismatch between the transmitted and received J1 identifier byte in the SDH path overhead. The error can originate at the transmit end or the receive end.
Clear the HP-TIM Alarm
Step 1 Use an optical test set capable of viewing SDH path overhead to determine the validity of the J1 byte.
For specific procedures to use the test equipment, consult the manufacturer.
a. Examine the signal as near to the reporting card as possible.
b. Examine the signal as close as possible to the output card.
Step 2 If the output card signal is valid, complete the "Clear the SYNCPRI Alarm" procedure.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers. If the alarm applies to HPTerm, it is a service-affecting problem.
2.7.137 HP-UNEQ
•Critical (CR), Service-Affecting (SA)
•Logical Objects: HPMon, HPTerm
The signal label mismatch fault (SLMF) Unequipped High-Order Path unequipped alarm applies to the C2 path signal label byte in the high-order (VC-4) path overhead. HP-UNEQ occurs when no C2 byte is received in the SDH path overhead.
Clear the HP-UNEQ Alarm
Step 1 From the View menu choose Go to Network View.
Step 2 Right-click the alarm to display the Select Affected Circuits shortcut menu.
Step 3 Click Select Affected Circuits.
Step 4 When the affected circuits appear, look in the Type column for virtual circuit (VC).
Step 5 If the Type column does not contain VC, there are no VCs. Go to Step 7.
Step 6 If the Type column does contain VC, attempt to delete these row(s):
Note The node does not allow you to delete a valid VC.
a. Click the VC row to highlight it. Complete the "Delete a Circuit" procedure.
b. If an error message dialog box appears, the VC is valid and not the cause of the alarm.
c. If any other columns contain VT, repeat Figure 2-1Step 6.
Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:
a. Click the Circuits tab.
b. Verify that INCOMPLETE is not listed in the Status column of any circuits.
Step 8 If you find circuits listed as incomplete, verify that these circuits are not working circuits that continue to pass traffic, using an appropriate optical test set and site-specific procedures.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.
Complete the "Delete a Circuit" procedure.
Step 10 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuits procedures.
Step 11 Log back in and verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the Status column lists all circuits as active.
Step 12 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service 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.
Step 13 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the optical and/or electrical cards.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 14 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.138 I-HITEMP
•Default Severity: Critical (CR), Service-Affecting (SA)
•Logical Object: NE
The Industrial High Temperature alarm occurs when the temperature of the ONS 15454 is above 149 degrees F (65 degrees C) or below -40 degrees F (-40 degrees C). This alarm is similar to the HITEMP alarm but is used for the industrial environment. If this alarm is used, you can customize your alarm profile to ignore the lower-temperature HITEMP alarm.
Clear the I-HITEMP Alarm
Step 1 Complete the "Clear the HITEMP Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.139 IMPROPRMVL
•Critical (CR), Service-Affecting (SA for active card)
•Logical Object: EQPT
The Improper Removal alarm occurs when a card is physically removed from its slot before being deleted from CTC. The card does not need to be in service to cause the IMPROPRMVL alarm; CTC only has to recognize that the card is not present. The alarm does not appear if you delete the card from CTC before you physically remove the card from the node.
Caution Do not remove a card during a card reboot. If CTC begins to reboot a card before you remove the card, allow the card to finish rebooting. After the card reboots, delete the card in CTC again and physically remove the card before it begins to reboot.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Note CTC gives the user approximately 15 seconds to physically remove the card before CTC begins a card reboot.
Note It can take up to 30 minutes for software to be updated on a standby TCC2 card.
Clear the IMPROPRMVL Alarm
Step 1 In node view, right-click the card reporting the IMPROPRMVL.
Step 2 Choose Delete from the shortcut menu.
Note CTC does not allow you to delete this card if the card is in service, has a circuit mapped, is paired in a working/protection scheme, has DCC enabled, or is used as a timing reference.
Step 3 If any ports on the card are in service, place them out of service (OOS):
Caution Before placing the a port out of service, ensure that no live traffic is present.
a. In node view, double-click the reporting card to display the card view.
b. Click the Provisioning > Line tab.
c. Click the State column of any in-service ports.
d. Choose OOS to take the ports out of service.
Step 4 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.
Caution Before deleting the circuit, ensure that the circuit does not carry live traffic.
Step 5 If the card is paired in a protection scheme, delete the protection group:
a. Click View > Go to Previous View to return to node view.
b. If you are already in node view, click the Provisioning > Protection tabs.
c. Click the protection group of the reporting card.
d. Click Delete.
Step 6 If the card is provisioned for DCC, from node view delete the DCC provisioning:
a. Click the Provisioning > DCC/GCC/OSC tabs.
b. Click the slots and ports listed in DCC terminations.
c. Click Delete and click Yes in the dialog box that appears.
Step 7 If the card is used as a timing reference, from node view change the timing reference:
a. Click the Provisioning > Timing tabs.
b. In the NE Reference area, click the pull-down menu for Ref-1.
c. Change Ref-1 from the listed STM-N card to Internal Clock.
d. Click Apply.
Step 8 Right-click the card reporting the IMPROPRMVL alarm and choose Delete.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.140 INC-GFP-OUTOFFRAME
•Not Alarmed (NA), Non-Service Affecting
•Logical Object: FCMR
The Out of Frame Detected by General Framing Procedure (GFP) Receiver condition can be caused by anything that prevents GFP communication across the SDH link, such as typical errors (MS-AIS, TU-LOP, LP-LPM, or HP-UNEQ); virtual concatenation (VCat) member errors (SQM); and VCat group errors. If a VCat is present, the VCG-DOWN, LOA, or LOM alarms are generated if any of the normal SDH errors are generated.
Clear the INC-GFP-OUTOFFRAME Condition
Step 1 Resolve any normal SDH errors also occurring on the errored circuit. See the "MS-AIS" section, the "TU-LOP" section, the "LP-PLM" section, or the "HP-UNEQ" section if these alarms are present.
Step 2 If the errored circuit is a VCat circuit and no other SDH alarms are occurring, look for and clear any VCat alarms. If they are present, see the "SQM" section.
Step 3 If a protection switch occurred on the STS carrying the circuit, the INC-GFP-OUTOFFRAME condition will clear when the working circuit is restored and able to carry traffic. For general information about protection switches, refer to the Cisco ONS 15454 SDH Procedure Guide and the Cisco ONS 15454 SDH Reference Manual.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.141 INC-GFP-SIGLOSS
•Not Alarmed (NA), Non-Service Affecting
•Logical Object: FCMR
The Client Signal Loss Frames Detected by GFP Server condition occurs when the upstream GFP transmitter has no signal from its fiber channel link. This condition occurs in conjunction with the "INC-SIGLOSS" alarm on page 2-120.
Clear the INC-GFP-SIGLOSS Condition
Step 1 Check the fiber channel data port connection at the remote fiber channel card port on the other end of the SONET link.
Step 2 Verify fiber continuity to the port.
Step 3 Check the physical port LED on the fiber channel card. The port LED looks clear (that is, not lit green) if the link is not connected.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.142 INC-GFP-SYNCLOSS
•Not Alarmed (NA), Non-Service Affecting
•Logical Object: FCMR
The Client Synchronization Loss Frames Detected by GFP Receiver condition occurs when the upstream GFP transmitter has no synchronization from its fiber channel link. This alarm is raised in conjunction with the "INC-SYNCLOSS" alarm on page 2-120.
Errors in synchronization can be caused if the fiber channel link is set for a speed that is not compatible with the attached equipment or if the port has a Gigabit Interface Converter (GBIC) connector that is incompatible with the link speed. When the GBIC does not support the line speed, the PORT-MISMATCH alarm could also be raised.
Clear the INC-GFP-SYNCLOSS Condition
Step 1 For the errored circuit, log into both ends of the SONET link where the fiber channel connection is present, and ensure that the fiber channel link is set to run at a compatible speed for the attached equipment (for example, 1 Gbps or 2 Gbps):
a. Double-click the fiber channel card to display the card view.
b. Click the Provisioning > Port tabs.
c. Under the Port Rate column, choose a speed that is compatible with the attached fiber channel equipment (either 1 Gbps or 2 Gbps).
Note You must choose the same line rate on both ends of the fiber channel link.
d. Click Apply.
Step 2 If the line rate is correctly set on both ends of the circuit, the remote card could have an incompatible GBIC for the line speed.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.143 INC-ISD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DS-3
The DS-3 Idle condition indicates that the DS-3 card is receiving an idle signal, meaning that the payload of the signal contains a repeating pattern of bits. The INC-ISD condition occurs when the transmitting port has an OO-MT state. INC-ISD is resolved when the OOS state ends.
Note INC-ISD is an informational condition. The condition does not require troubleshooting.
2.7.144 INC-SIGLOSS
•Major (MJ), Service-Affecting
•Logical Object: FCMR
The Incoming Signal Loss on the fiber channel Interface alarm is raised when there is a signal loss at the local fiber channel port. (The "INC-GFP-SIGLOSS" alarm on page 2-118 is raised at the far-end port in conjunction with this alarm.)
Clear the INC-SIGLOSS Alarm
Step 1 Check the fiber channel data port connection at the near-end fiber channel card port of the SONET link.
Step 2 Verify fiber continuity to the port.
Step 3 Check the physical port LED on the fiber channel card. The port LED looks clear (that is, not lit green) if the link is not connected.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.145 INC-SYNCLOSS
•Major (MJ), Service-Affecting
•Logical Object: FCMR
The Incoming Synchronization Loss on the fiber channel Interface alarm is raised when there is a synchronization error at the local fiber channel port. (The "INC-GFP-SYNCLOSS" alarm on page 2-119 is raised at the far-end port in conjunction with this alarm.)
Clear the INC-SYNCLOSS Alarm
Step 1 Complete the "Clear the INC-GFP-SYNCLOSS Condition" alarm on page 2-119.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.146 INHSWPR
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Inhibit Switch To Protect Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) cards when the ability to switch to protect has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked onto the working system. If the card is part of a 1:N protection scheme, traffic can be switched between working cards when the switch to protect is disabled.
Clear the INHSWPR Condition
Step 1 Complete the "Clear a Protection Group External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.147 INHSWWKG
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Inhibit Switch To Working Request On Equipment condition occurs on traffic (electrical, optical, or Ethernet) cards when the ability to switch to working has been disabled. If the card is part of a 1:1 or 1+1 protection scheme, traffic remains locked on to the protect system. If the card is part of a 1:N protection scheme, traffic can be switched between protect cards when the switched to working is disabled.
Clear the INHSWWKG Condition
Step 1 Complete the "Clear a Protection Group External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.148 INTRUSION-PSWD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The Security Intrusion Incorrect Password condition occurs after a user attempts a settable (by Superuser) number of unsuccessful logins, a login with an expired password, or an invalid password. The alarmed user is locked out of the system, and INTRUSION-PSWD condition is raised. This condition is only shown in Superuser login sessions, not login sessions for lower-level users. The INTRUSION-PSWD condition is automatically cleared when a settable lockout timeout expires, or it can be manually cleared in CTC by the Superuser if lockout is permanent.
Clear the INTRUSION-PSWD Condition
Step 1 Click the Provisioning > Security tabs.
Step 2 Click Clear Security Intrusion Password Alarm.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.149 INVMACADR
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: BP
The Equipment Failure Invalid MAC address alarm occurs when the ONS 15454 SDH Media Access Control layer address (MAC address) is invalid. The MAC address is permanently assigned to the ONS 15454 SDH chassis during manufacture. Do not attempt to troubleshoot an INVMACADR. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.150 IOSCFGCOPY
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The IOS Configuration Copy in Progress condition occurs on ML-Series Ethernet cards when an IOS startup configuration file is being uploaded or downloaded to or from an ML-Series card. (This condition is very similar to the SFTWDOWN condition but it applies to ML-Series Ethernet cards rather than to the TCC2.)
The condition clears after the copy operation is complete. (If it does not complete correctly, the NO-CONFIG condition could be raised.)
Note IOSCFGCOPY is an informational condition.
2.7.151 KB-PASSTHR
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The K Bytes Pass Through Active condition occurs on a nonswitching node in an MS-SPRing when the protect channels on the node are not active and the node is in K Byte Pass-Through State.
Clear the KB-PASSTHR Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.152 KBYTE-APS-CHANNEL-FAILURE
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
The APS Channel Failure alarm is raised when a span is provisioned for different APS channels on each side. For instance, the alarm is raised if K3 is selected on one end and F1, E2, or Z2 is selected on the other end.
This alarm is also raised during checksum. Failure occurs if the K1 and K2 bytes are overwritten by test equipment. It is not raised in bidirectional full pass-through or Kbyte pass-through states. The alarm is overridden by MS-AIS, LOF, LOS, or SF-BER alarms.
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
Step 1 The alarm most frequently is raised due to mismatched span provisioning. In this case, reprovision one side of the span with the same parameters. To do this, refer to the Cisco ONS 15454 SDH Procedure Guide.
Step 2 If the error is not caused by misprovisioning, it is due to checksum errors within an STM-N, cross-connect, or TCC2 card. Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure to allow CTC to resolve the issue.
Step 3 If third-party equipment is involved, ensure that it is configured for the same APS channel as the Cisco ONS equipment.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.153 LAN-POL-REV
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NE
The Lan Connection Polarity Reversed condition is not raised in shelves that contain TCC2 cards. It is raised by the TCC+ card during software upgrade when the card detects that a connected Ethernet cable has reversed receive wire pairs. The TCC+ automatically compensates for this reversal, but LAN-POL-REV stays active.
Clear the LAN-POL-REV Condition
Step 1 Replace the connected Ethernet cable with a cable that has the correct pinout. For correct pin mapping, refer to the Cisco ONS 15454 Procedure Guide.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.154 LASER-APR
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: E-4
The Laser Auto Power Reduction condition occurs on optical amplifiers (OPT-BST and OPT-PRE) when the amplifier works at a reduced power level for a fixed period during the automatic restart. The condition raises and clears within about 10 seconds.
Note LASER-APR is information condition only and does not require troubleshooting.
2.7.155 LASERBIAS-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Laser Bias Degrade alarm occurs on optical amplifiers (OPT-BST and OPT-PRE) and optical service channel cards (OSCM and OSC-CSM) if the card laser crosses the laser bias degrade threshold. This degradation occurs due to laser aging.
Clear the LASERBIAS-DEG Alarm
Step 1 This alarm does not immediately affect traffic, but eventually to clear this alarm, complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.156 LASERBIAS-FAIL
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: E-4
The Laser Bias Failure alarm occurs on optical amplifiers (OPT-BST and OPT-PRE) when a failure occurs on the card laser current control circuit, or if the laser is broken.
Clear the LASERBIAS-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.157 LASEREOL
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Laser Approaching End of Life alarm applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. It is typically accompanied by the "HI-LASERBIAS" alarm on page 2-108. It is an indicator that the laser in the card will need to be replaced. How soon the replacement must happen depends upon the HI-LASERBIAS threshold. If the threshold is set under 100 percent, the laser replacement can usually be done during a maintenance window. But if the HI-LASERBIAS threshold is set at 100 percent and is accompanied by data errors, the card must be replaced sooner.
Clear the LASEREOL Alarm
Step 1 Complete the "Physically Replace a Card" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.158 LASERTEMP-DEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Laser Temperature Degrade condition occurs on optical amplifiers (OPT-BST and OPT-PRE) when a failure occurs on the laser Peltier control circuit that degrades laser performance in the amplifier card.
Clear the LASERTEMP-DEG Alarm
Step 1 This alarm does not immediately affect traffic, but eventually to clear this alarm, complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.159 LKOUTPR-R
The LKOUTPR-R condition is not used in this platform in this release. It is reserved for future development.
2.7.160 LKOUTPR-S
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Lockout of Protection condition occurs on an MS-SPRing node when traffic is locked out of a protect span using the LOCKOUT SPAN command.
Clear the LKOUTPR-S Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.161 LKOUTWK-R
The LKOUTWK-R condition is not used in this platform in this release. It is reserved for future development.
2.7.162 LKOUTWK-S (NA)
The Lockout of Working—Span condition is not supported in this release. It is reserved for future development.
2.7.163 LMP-HELLODOWN
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: CC
The Link Management Protocol (LMP) Hello Down alarm occurs when the Hello protocol, which monitors UCP control channel status, is not available for link management. Loss of Hello protocol can occur when there are physical layer errors (such as cabling) or when a control channel is misconfigured.
Clear the LMP-HELLODOWN Alarm
Step 1 Verify that transmit and receive cables are not crossed at each end (login site and neighbor site).
Step 2 Verify that the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131 is not present on the source or destination nodes. If a LOF is present, complete the "Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm" procedure.
Step 3 If the alarm does not clear, complete the "Clear the CKTDOWN Alarm" procedure to verify that IPCC provisioning is valid on both ends of the UNI.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.164 LMP-NDFAIL
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: CC
The LMP Neighbor Detection Fail alarm occurs when neighbor detection within the unified control plane (UCP) has failed. LMP-NDFAIL can be caused by physical failure (such as cabling) between the neighbors or by control channel misconfiguration.
Clear the LMP-NDFAIL Alarm
Step 1 Complete the "Clear the LMP-HELLODOWN Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.165 LOA
•Critical (CR), Service-Affecting (SA)
•Logical Object: VCatGroup
The Loss of Alignment on a virtual concatenation group (VCG) is a VCat member alarm. (VCat member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm occurs when members of a VCG travel over different paths in the network (due to initial operator provisioning or to protection or restoration events) and the differential delays between the paths cannot be recovered by terminating hardware buffers.
Note This alarm occurs only if you provision circuits outside of CTC, such as by using TL1.
Clear the LOA Alarm
Step 1 In network view, click the Circuits tab.
Step 2 Click the alarmed VCG and then click Edit.
Step 3 In the Edit Circuit dialog box, click Show Detailed Map to see the source and destination circuit slots, ports, and STSs.
Step 4 Identify whether the STS travels across different fibers. If it does, complete the "Delete a Circuit" procedure.
Step 5 Recreate the circuit using the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 6 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.166 LOC
•Critical (CR), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The Loss of Channel cards is raised upon MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when a channel is lost and ITU-T G.709 monitoring is enabled. It is similar to the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Clear the LOC Alarm
Step 1 Complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.167 LOCKOUTOFPR
•Default Severity: Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STMN
•The Lockout of Protection condition is not supported in this release. It is reserved for future development.
2.7.168 LOCKOUT-REQ
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, EQPT, HPMon, LPMon, STM-N
The Lockout Switch Request on Facility or Equipment condition occurs when a user initiates a Lock Out switch request for an STM-N card or a Lock Out switch request on an SNCP ring at the path level. A Lock Out prevents protection switching. Clearing the Lock Out again allows protection switching and clears the LOCKOUT-REQ condition.
Clear the LOCKOUT-REQ Condition
Step 1 Complete the "Clear an SNCP Lockout" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.169 LOCKOUT-REQ-RING
The LOCKOUT-REQ-RING condition is not used in this platform in this release. It is reserved for future development.
2.7.170 LOF (BITS)
•Major (MJ), Service-Affecting (SA)
•Logical Object: BITS
The Loss of Frame (LOF) BITS alarm occurs when a port on the TCC2 BITS input detects an LOF on the incoming BITS timing reference signal. LOF indicates that the receiving ONS 15454 SDH has lost frame delineation in the incoming data.
Note The procedure assumes that the BITS timing reference signal is functioning properly and that the alarm is not appearing during node turnup.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Clear the LOF (BITS) Alarm
Step 1 Verify that the line framing and line coding match between the BITS input and the TCC2 card:
a. In node view or card view, note the slot and port reporting the alarm.
b. Find the coding and framing formats of the external BITS timing source. The formats should be in the user documentation for the external BITS timing source or on the timing source itself.
c. Click the Provisioning > Timing tabs to display the General Timing window.
d. Verify that the value listed in Coding matches the coding of the BITS timing source (either B8ZS or AMI).
e. If the coding does not match, click the BITS-1 or BITS2 Coding and choose the appropriate coding from the pull-down menu.
f. Verify that the value listed in Framing matches the framing of the BITS timing source (either ESF or SF).
g. If the framing does not match, click the BITS-1 or BITS-2 Framing and choose the appropriate framing from the pull-down menu.
Note On the timing subtab, the binary 8-zero substitution (B8ZS) coding field is normally paired with Extended Superframe (ESF) in the Framing field and the alternate mark inversion (AMI) coding field is normally paired with SF (D4) in the Framing field.
Step 2 If the alarm does not clear when the line framing and line coding match between the BITS input and the TCC2 card, replace the TCC2 card. Complete the "Physically Replace a 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.171 LOF (DS-3, E-1, E-4, STM-N, STM1-E)
•Critical (CR), Service-Affecting (SA) for DS-3, E-4, STM-N, STM-1E)
•Major (MJ), Service-Affecting (SA) for E-1
•Logical Objects: DS-3, E-1, E-4, STM-N, STM-1E
An LOF alarm on DS3i-N-12, E1-N-14, or E1-42 cards for these objects means that the receiving ONS 15454 SDH has lost frame delineation in the incoming data. LOF occurs when the SDH overhead loses a valid framing pattern for three seconds. Receiving two consecutive valid patterns clears the alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the middle-right outside edge of the shelf assembly.
Clear the LOF (DS-3, E-1, E-4, STM-N, STM-1E) Alarm
Step 1 Verify that the line framing and line coding match between the port and the signal source:
a. In CTC, note the slot and port reporting the alarm.
b. Find the coding and framing formats of the signal source for the card reporting the alarm. You may need to contact your network administrator for the format information.
c. Display the card view of the reporting card.
d. Click the Provisioning > Line tabs.
e. Verify that the line type of the reporting port matches the line type of the signal source.
f. If the signal source line type does not match the reporting port, click Line Type and choose the appropriate type from the pull-down menu.
g. Verify that the reporting Line Coding matches the signal source's line type.
h. If the signal source line coding does not match the reporting port, click Line Coding and choose the appropriate type from the pull-down menu.
i. Click Apply.
Step 2 If the alarm does not clear when the coding and framing of the ONS 15454 SDH match the coding and framing of the signal source, replace the card.
Note When replacing a card with an identical type of card, you do not need to change the CTC database.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.172 LOF (DWDM Client)
•Critical (CR), Service-Affecting (SA)
•Logical Object: DWDM Client
The Loss of Frame for a DWDM client applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. It is raised when the card port has lost frame delineation in the incoming data. LOF occurs when the SDH overhead loses a valid framing pattern for three milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.
Clear the LOF (DWDM Client) Alarm
Step 1 Complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.173 LOF (DWDM Trunk)
•Critical (CR), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The Loss of Frame for the DWDM trunk applies to the trunk optical or electrical signal that is carried to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. It indicates that the receiving ONS 15454 SDH has lost frame delineation in the incoming data from trunk that serves the cards. LOF occurs when the SDH overhead loses a valid framing pattern for three milliseconds. Receiving two consecutive valid A1/A2 framing patterns clears the alarm.
Clear the LOF (DWDM Trunk) Alarm
Step 1 Complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.174 LOM
•Critical (CR), Service-Affecting (SA) for DWDM Trunk, HPTerm
•Major (MJ), Service-Affecting (SA) for LPTerm
•Logical Objects: DWDM Trunk, HPTerm, LPTerm
The Loss of Multiframe alarm is a VCat member alarm. (VCat member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) The alarm applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when the MFAS overhead field is errored for more than five frames and persists for more than three milliseconds.
Clear the LOM Alarm
Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.175 LO-RXPOWER
•Minor (MN), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Equipment Low Receive Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card received optical signal power. LO-RXPOWER occurs when the measured optical power of the received signal falls under the threshold. The threshold value is user-provisionable.
Clear the LO-RXPOWER Alarm
Step 1 At the transmit end of the errored circuit, increase the transmit power level within safe limits.
Step 2 Find out whether new channels have been added to the fiber. Up to 32 channels can be transmitted on the same fiber, but the number of channels affects power. If channels have been added, power levels of all channels need to be adjusted.
Note If the card is part of an amplified dense wavelength division multiplexing system, adding channels on the fiber affects the transmission power of each channel more than adding them would in an unamplified system.
Step 3 Find out whether gain (the amplification power) of any amplifiers has been changed. A modification also causes channel power to need adjustment.
Step 4 If the alarm does not clear, remove any receive fiber attenuators or replace them with lower-resistance attenuators.
Step 5 If the alarm does not clear, inspect and clean the receive and transmit node fiber connections according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 6 If the alarm does not clear, ensure that the fiber is not broken or damaged by testing it with an optical test set. If no test set is available, use the fiber for a facility loopback on a known-good port. The error readings you get will not be as precise, but you will generally know whether the fiber is faulty.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 7 If the alarm does not clear, and no faults are present on the other port(s) of the transmit or receive card, use a known-good loopback cable to complete the "1.2.1 Perform a Facility (Line) Loopback on a Source DS-N or E-N Port (West to East)" procedure on page 1-7.
Step 8 If a port is bad and you need to use all the port bandwidth, complete the "Physically Replace a Card" procedure. If the port is bad but you can move the traffic to another port, replace the card at the next available maintenance window.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.176 LOS (BITS)
•Major (MJ), Service-Affecting (SA)
•Logical Object: BITS
The LOS (BITS) alarm indicates that the TCC2 card has an LOS from the BITS timing source. An LOS (BITS) occurs when an SDH receiver detects an all-zero pattern for 10 microseconds or longer. An LOS (BITS-N) means the BITS clock or the connection to the BITS clock failed.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Clear the LOS (BITS) Alarm
Step 1 Verify the wiring connection from the BITS clock pin fields on the ONS 15454 SDH backplane to the timing source.
Step 2 If wiring is good, verify that the BITS clock is operating properly.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.177 LOS (DS-3, E-1, E-3, STM-N, STM-1E)
•Critical (CR), Service-Affecting (SA) for DS-3, E-3, E-4, STM-N, STM-1E
•Major (MJ), Service-Affecting (SA) for E-1
•Logical Objects: DS-3, E-1, E-3, E-4, STM-N, STM-1E
A LOS alarm for a DS-3, E-N, or STM-N port occurs when the port on the card is in service but no signal is being received. The cabling is not correctly connected to the card, or no signal exists on the line. Possible causes for no signal on the line include upstream equipment failure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454 SDH. Plug the wristband cable into the ESD jack located on the lower-right outside edge of the shelf assembly.
Note If a circuit shows an incomplete state when this alarm is raised, the logical circuit is in place. The circuit will be able to carry traffic when the connection issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm
Step 1 Verify that the fiber cable is properly connected and attached to the correct port.
If an optical TDM signal such as an STM-1 or STM-4 is plugged into an E1000 or G1000 card GBIC connector, this can trigger an LOS.
Step 2 Consult site records to determine whether the port raising the alarm has been assigned.
Step 3 If the port is not currently assigned, place the port out of service using the following steps. LOS can be caused by a non-assigned port placed in service (IS).
a. Double-click the card to display the card view.
b. For DS-3, E-1, E-3, or STM cards, click the Maintenance > Loopback tabs.
c. Look under the State column to determine the port's status.
Step 4 If the port is assigned, verify that the correct port is in service:
a. To confirm this physically, confirm that the card shows a green LED on the physical card.
A green LED indicates an active card. An amber LED indicates a standby card.
b. To determine this virtually, double-click the card in CTC to display the card view.
•Click the Provisioning > Line tabs.
•Verify that the State column lists the port as IS.
•If the State column lists the port as OOS, click the column and choose IS. Click Apply.
Step 5 Use a test set to confirm that a valid signal exists on the line. Test the line as close to the receiving card as possible. For specific procedures to use the test set equipment, consult the manufacturer.
Step 6 Ensure that the transmit and receive outputs from the DSx panel to your equipment are properly connected.
Step 7 If there is a valid signal, replace the electrical connector on the ONS 15454 SDH.
Step 8 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 9 Repeat Steps 1 to 8 for any other port on the card that reports the LOS.
Step 10 If no other alarms are present that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 11 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.178 LOS (DWDM Client)
•Critical (CR), Service-Affecting (SA)
•Logical Object: DWDM Client
The Loss of Signal for a DWDM client applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. The alarm is raised when the card port is not receiving input. An AIS is sent upstream.
Clear the LOS (DWDM Client) Alarm
Step 1 Complete the "Clear the LOS (DS-3, E-1, E-3, STM-N, STM-1E) Alarm" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.179 LOS (FUDC)
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: FUDC
The LOS (FUDC) alarm is raised if there is a UDC circuit created on the AIC-I DCC port but the port is not receiving signal input. The downstream node will have an AIS condition raised against AIC-I DCC port transmitting the UDC.
Clear the LOS (FUDC) Alarm
Step 1 Verify cable continuity to the AIC-I UDC port.
Step 2 Verify that there is a valid input signal using a test set.
Step 3 If there is a valid signal, clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 Procedure Guide.
Step 4 If the alarm does not clear, verify that the UDC is provisioned:
a. At the network view, click the Provisioning > Overhead Circuits tabs.
b. If no UDC circuit exists, create one. Refer to the Cisco ONS 15454 SDH Procedure Guide.
c. If a user data circuit exists (shown as User Data F1 under the Type column), check the source and destination ports. These must be located on AIC-I cards to function.
Step 5 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.
Step 6 If no other alarms exist that could be the source of the LOS (FUDC), or if clearing another alarm did not clear the LOS, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 7 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.180 LOS (OTN)
•Critical (CR), Service-Affecting (SA)
•Logical Object: DWDM Trunk
The Loss of Signal for the OTN applies to the LINE-3-RX port of the OPT-BST amplifier and the LINE-2-RX port of the OSC-CSM card. It indicates that a fiber cut has occurred and no power is being received from the span.
Clear the LOS (OTN) Alarm
Step 1 Verify fiber continuity to the port.
Step 2 If the cabling is okay, confirm that the LED is correctly illuminated on the physical card. A green ACT/SBY LED indicates an active card. A red ACT/SBY LED indicates a failed card.
Step 3 Verify that the received power (opwrMin value of the Line 4-1-RX port) is within the expected range shown in Cisco MetroPlanner. To check the level:
a. Double-click the amplifier card to display the card view.
b. Click the Provisioning > Opt. Ampli. Line > Optics Thresholds tabs.
c. Compare the opwrMin (dBm) column value with the MetroPlanner-generated value. (For more information about using MetroPlanner, refer to the Cisco MetroPlanner DWDM Operations Guide, Release 2.5.
Step 4 If the optical power level is within specifications, check and modify the channel LOS and OSC LOS thresholds, then run automatic node setup (ANS) to execute the changes:
a. In node view, click the Provisioning > WDM-ANS > Provisioning tabs.
b. Consult the Cisco MetroPlanner DWDM Operations Guide, Release 2.5 to decide what values to use, then modify the following items:
•West Side Rx. Channel OSC LOS Threshold
•West Side Rx. Channel LOS Threshold
c. Click the WDM-ANS > Port Status tabs.
d. Click Launch ANS and click Yes in the confirmation dialog box.
Step 5 If the optical power is outside of the expected range, check the power level transmitted at the other side of the span using CTC:
a. On the transmitting node, double-click the transmitting MXP or TXP to display the card view.
b. Click the Provisioning > Optics Thresholds tab.
c. View the TX Power High and TX Power Low values, comparing them with the MetroPlanner-generated values.
Step 6 If the transmitted power value is within the expected range, clean the receiving node (where the LOS is raised) and clean the fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 7 If the transmitted power value is outside of the expected range, troubleshoot using the DWDM acceptance tests in the Cisco ONS 15454 SDH Procedure Guide.
Step 8 If the alarm does not clear, look for and troubleshoot any other alarm that could identify the source of the problem.
Step 9 If no other alarms exist that could be the source of the LOS, or if clearing an alarm did not clear the LOS, complete the "Physically Replace a Card" procedure for the reporting 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
"Alarm Procedures" section for commonly used lockout and traffic-switching procedures. For detailed information and guidelines for traffic switching, refer to the
Cisco ONS 15454 SDH Procedure Guide.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 10 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.181 LOS-P (TRUNK)
The LOS-P alarm is not used in this platform in this release. It is reserved for future development.
2.7.182 LO-TXPOWER
•Minor (MN), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Equipment Low Transmit Power alarm is an indicator for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G card transmitted optical signal power. LO-TXPOWER occurs when the measured optical power of the transmitted signal falls under the threshold. The threshold value is user-provisionable.
Clear the LO-TXPOWER Alarm
Step 1 Display the MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G card view.
Step 2 Click the Provisioning > Optical Thresholds tabs.
Step 3 Increase the TX Power Low column value by 0.5 dBm.
Step 4 If the card transmit power setting cannot be increased without affecting the signal, complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 5 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.183 LPBKCRS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: HPMon
The Loopback Cross-Connect condition indicates that there is a software cross-connect loopback active between an STM-N card and a cross-connect card. A cross-connect loopback is a sub-line speed test that does not affect traffic.
For more information on loopbacks, see the "1.2 Identify Points of Failure on a DS-N or E-N Circuit Path" section on page 1-6.
Note XC loopbacks are sub-line speed and do not affect traffic.
Clear the LBKCRS Condition
Step 1 To remove the loopback cross-connect condition, double-click the traffic (optical) card in CTC to display the card view.
Step 2 Click the Provisioning > VC4 tabs.
Step 3 Under the XC Loopback column, deselect the check box for the port.
Step 4 Click Apply.
Step 5 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.184 LPBKDS1FEAC
The LPBKDS1FEAC condition is not used in this platform in this release. It is reserved for future development.
2.7.185 LPBKDS1FEAC-CMD
The LPBKDS1FEAC-CMD condition is not used in this platform in this release. It is reserved for future development.
2.7.186 LPBKDS3FEAC
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DS-3
A Loopback Due to FEAC Command DS-3 condition occurs when a DS3i-N-12 card loopback signal is received from the far-end node because of a FEAC command. An FEAC command is often used with loopbacks. LPBKDS3FEAC is only reported by DS3i-N-12 cards. A DSi3-N-12 card generates and reports FEAC alarms or conditions.
Caution CTC permits loopbacks on an in-service (IS) circuit. Loopbacks are service-affecting.
Note LPBKDS3FEAC is an informational condition. It does not require troubleshooting.
Clear the LPBKDS3FEAC Condition
Step 1 In node view, double-click the DS3-N-12 card to display the card view.
Step 2 Click the Maintenance > Loopback tabs.
Step 3 Click the Loopback Type column, cell for the port and click None from the pull-down menu.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.187 LPBKDS3FEAC-CMD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DS-3
The DS-3 Loopback Command Sent To Far End condition occurs on the near-end node when you send a DS-3 FEAC loopback to a DS3i-N-12 card. For more information about FEAC loopbacks, see the "1.2 Identify Points of Failure on a DS-N or E-N Circuit Path" section on page 1-6.
Note LPBKDS3FEAC-CMD is an informational condition. It does not require troubleshooting.
2.7.188 LPBKE1FEAC
The LPBKE1FEAC condition is not used in this platform in this release. It is reserved for future development.
2.7.189 LPBKE3FEAC
The LPBKE3FEAC condition is not used in this platform in this release. It is reserved for future development.
2.7.190 LPBKE3FEAC-CMD
The LPBKE3FEAC-CMD condition is not used in this platform in this release. It is reserved for future development.
2.7.191 LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-1, E-3,E-4, STM-N, STM-1E
A Loopback Facility condition occurs when a software facility loopback is active for a port on the reporting card.
For more information on loopbacks, see the "1.1 Network Troubleshooting Tests" section on page 1-2 or the "1.2 Identify Points of Failure on a DS-N or E-N Circuit Path" section on page 1-6.
Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are service-affecting.
Note DS-3 facility loopbacks do not transmit the DS-3 "APSB" condition on page 2-27 in the direction away from the loopback. Instead of DS-3 AIS, a continuance of the signal transmitted to the loopback is provided.
Clear the LPBKFACILITY (DS-3, E-1, E-3, E-4, STM-N, STM-1E) Condition
Step 1 In node view, double-click the reporting card to display the card view.
Step 2 Complete the "Clear a Loopback" procedure.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.192 LPBKFACILITY (DWDM Client)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DWDM Client
The LPBKFACILITY for a DWDM client applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when ports on these cards are placed in facility (line) loopbacks.
Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are service-affecting.
2.7.193 LPBKFACILITY (G-Series)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: HDGE
A Loopback Facility condition occurs when a software facility (line) loopback is active for a G1000-4 port on the reporting G-Series Ethernet card.
For more information about loopbacks, see the "1.1 Network Troubleshooting Tests" section on page 1-2.
Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are service-affecting.
Clear the LPBKFACILITY (G-Series) Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.194 LPBKTERMINAL (DS-3, E-1, E-3, E-4, STM-N, STM-1E)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DS-3, E-1, E-3, E-4, STM-N, STM-1E
A Loopback Terminal condition occurs when a software terminal (inward) loopback is active for a port on the reporting card.
For more information on loopbacks, see the "1.1 Network Troubleshooting Tests" section on page 1-2.
Note DS-3 terminal loopbacks do not transmit the "MS-AIS" condition on page 2-157 in the direction away from the loopback. Instead of MS-AIS, a continuance of the signal transmitted into the loopback is provided.
Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are service-affecting.
Clear the LPBKTERMINAL (DS-3, D-1, E-3, E-4, STM-N, STM-1E) Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.195 LPBKTERMINAL (DWDM)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DWDM Client or Trunk
The LPBKTERMINAL for a DWDM client applies to MXP_2.5G_10G, TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G cards when ports on these cards are placed in terminal (inward) loopbacks.
Note The condition clears automatically when you clear the loopback. No troubleshooting is necessary.
2.7.196 LPBKTERMINAL(G-Series Ethernet)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: HDGE
A Loopback Terminal condition occurs when a software terminal loopback is active for a port on the reporting G-Series Ethernet card.
When a port in terminal loopback, its outgoing signal is redirected into the receive direction on the same port, and the externally received signal is ignored. On the G1000-4 card, the outgoing signal is not transmitted; the signal is only redirected in the receive direction.
For more information on loopbacks, see the "1.1 Network Troubleshooting Tests" section on page 1-2.
Caution CTC permits loopbacks to be performed on an in-service (IS) circuit. Loopbacks are service-affecting.
Clear the LPBKTERMINAL (G-Series) Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.197 LP-PLM
•Major (MJ), Service-Affecting (SA) for LPTerm
•Logical Object: LPTerm
The SLMF-PLM Low-Order Path Label Mismatch alarm applies to the V5 byte in low-order (VC-2 or VC-1) path overhead. LP-PLM occurs when there is a mismatch between the transmitted and received V5 byte received in the SDH payload overhead.
The LP-PLM alarm occurs when the optical (traffic) cards cannot detect the value of the C2 byte in the payload. The low-order C2 byte would cause the LP-PLM to occur on terminating cards.
Clear the LP-PLM Alarm
Step 1 Verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the Status column lists the port as active.
c. If the State column lists the port as incomplete, wait 10 minutes for the ONS 15454 SDH to initialize fully. If the incomplete state does not change after full initialization, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Step 2 After determining the port is active, verify the signal source to the traffic (electrical) card reporting the alarm with an optical test set according to site specific practice.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 3 If traffic is being affected, complete the "Delete a Circuit" procedure.
Caution Deleting a circuit can affect traffic.
Step 4 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 5 If the circuit deletion and recreation does not clear the alarm, verify the far-end STM-N card that provides STS payload to the electrical card.
Step 6 If the alarm does not clear, verify the cross-connect between the STM-N card and the electrical card.
Step 7 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Step 8 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.198 LP-RFI
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: LPTerm
The Low-Order RFI condition indicates that there is a remote failure indication in the low-order (VC-2 or VC-1) path, and that the failure has persisted beyond the maximum time allotted for transmission system protection. The LP-RFI is sent as the protection switch is initiated. Resolving the fault in the adjoining node clears the LP-RFI condition in the reporting node.
Clear the LP-RFI Condition
Step 1 Log into the far-end node of the reporting ONS 15454 SDH.
Step 2 Determine whether there are other alarms, especially the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Step 3 Clear the alarms. Refer to the appropriate alarm section in this chapter for the procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.199 LP-TIM
•Major (MJ), Service-Affecting (SA)
•Logical Object: LPTerm
The Low-Order Path Section TIM alarm occurs when the expected J2 path trace string does not match the received string.
If the alarm occurs on a port that has been operating with no alarms, the circuit path has changed or someone entered a new incorrect value into the Current Transmit String field. Follow the procedure below to clear either instance.
LP-TIM also occurs on a port that has previously been operating without alarms if someone switches or removes the electrical cables or optical fibers that connect the ports. TIM is usually accompanied by other alarms, such as the "LP-UNEQ" alarm on page 2-147. If this alarm accompanies the "TIM" alarm on page 2-202, reattach or replace the original cables/fibers to clear the alarms.
Clear the LP-TIM Alarm
Step 1 Complete the "Clear the TIM Alarm or Condition" procedure.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.200 LP-UNEQ
•Major (MJ), Service-Affecting (SA)
•Logical Objects: LPMon, LPTerm
The SLMF Unequipped Low-Order Path Unequipped alarm applies to the V5 byte in low-order (VC-2 or VC-1) path overhead. LP-UNEQ occurs when no V5 byte is received in the SDH payload overhead.
Clear the LP-UNEQ Alarm
Step 1 In node view, click View > Go to Network View.
Step 2 Right-click the alarm to display the Select Affected Circuits shortcut menu.
Step 3 Click Select Affected Circuits.
Step 4 When the affected circuits appear, look in the Type column for VCT, which indicates a VC tunnel Circuit. A VC tunnel with no VCs assigned could be the cause of an LP-UNEQ alarm.
Step 5 If the Type column does not contain VCT, there are no VC tunnels connected with the alarm. Go to
Step 7.
Step 6 If the Type column does contain VCT, attempt to delete these row(s):
Note The node does not allow you to delete a valid VT tunnel or one with a valid VT circuit inside.
a. Click the VC tunnel circuit row to highlight it. Complete the "Delete a Circuit" procedure.
b. If an error message dialog box appears, the VC tunnel is valid and not the cause of the alarm.
c. If any other columns contain VCT, repeat Figure 2-1Step 6.
Step 7 If all ONS nodes in the ring appear in the CTC network view, verify that the circuits are all complete:
a. Click the Circuits tab.
b. Verify that INCOMPLETE is not listed in the Status column of any circuits.
Step 8 If you find circuits listed as incomplete, verify these circuits are not working circuits that continue to pass traffic with an appropriate optical test set and site-specific procedures.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 9 If the incomplete circuits are not needed or are not passing traffic, delete the incomplete circuits.
Complete the "Delete a Circuit" procedure.
Step 10 Recreate the circuit with the correct circuit size. Refer to the Cisco ONS 15454 SDH Procedure Guide for circuit procedures.
Step 11 Log back in and verify that all circuits terminating in the reporting card are active:
a. Click the Circuits tab.
b. Verify that the Status column lists all circuits as active.
Step 12 If the alarm does not clear, clean the far-end optical fiber according to site practice. If no site practice exists, complete the procedure in the Cisco ONS 15454 SDH Procedure Guide.
Warning On the STM-64 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service 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.
Step 13 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the optical and/or electrical cards.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 14 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.201 LWBATVG
•Major (MJ), Service-Affecting (SA)
•Logical Object: PWR
The Low Voltage Battery alarm occurs in a -48 VDC environment when a battery lead's input voltage falls below the low power threshold. This threshold, with a default value of -44 VDC, is user-provisionable. The alarm remains raised until the voltage remains above the threshold for 120 seconds. (For information about changing this threshold, refer to the Cisco ONS 15454 SDH Procedure Guide.)
Clear the LWBATVG Alarm
Step 1 The problem is external to the ONS 15454 SDH. Troubleshoot the power source supplying the battery leads.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.202 MAN-REQ
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EQPT, HPMon, LPMon
The Manual Switch Request condition occurs when a user initiates a Manual switch request on an STM-N card or SNCP path. Clearing the Manual switch clears the MAN-REQ condition.
Clear the MAN-REQ Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.203 MANRESET
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
A User-Initiated Manual Reset condition occurs when you right-click a card in CTC and choose Reset. Resets performed during a software upgrade also prompt the condition. The MANRESET condition clears automatically when the card finishes resetting.
Note MANRESET is an informational condition. The condition does not require troubleshooting.
2.7.204 MANSWTOINT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: NESync
The Manual Switch To Internal Clock condition occurs when the NE timing source is manually switched to the internal timing source.
Note MANSWTOINT is an informational condition. The condition does not require troubleshooting.
2.7.205 MANSWTOPRI
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTsync, NESync
The Manual Switch To Primary Reference condition occurs when the NE timing source is manually switched to the primary timing source.
Note MANSWTOPRI is an informational condition. The condition does not require troubleshooting.
2.7.206 MANSWTOSEC
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTSync NESync
The Manual Switch To Second Reference condition occurs when the NE timing source is manually switched to the secondary timing source.
Note MANSWTOSEC is an informational condition. The condition does not require troubleshooting.
2.7.207 MANSWTOTHIRD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: EXTSync, NESync
The Manual Switch To Third Reference condition occurs when the NE timing source is manually switched to the tertiary timing source.
Note MANSWTOTHIRD is an informational condition. The condition does not require troubleshooting.
2.7.208 MANUAL-REQ-RING
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STM-N
The Manual Switch Request on Ring condition occurs when a user initiates a MANUAL RING command on two-fiber and four-fiber MS-SPRings to switch from working to protect or protect to working.
Clear the MANUAL-REQ-RING Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.209 MANUAL-REQ-SPAN
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: DWDM Client, DWDM Trunk, STM-N
The Manual Switch Request on Ring condition occurs on four-fiber MS-SPRings when a user initiates a MANUAL SPAN command to move MS-SPRing traffic from a working span to a protect span.
Clear the MANUAL-REQ-SPAN Condition
Step 1 Complete the "Clear a Ring or Span External Switching Command" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.210 MEA (BP)
•Critical (CR), Service-Affecting (SA)
•Logical Object: BP
The Mismatch of Equipment Attributes (MEA) alarm for the backplane occurs when the revision of the backplane is incompatible with XC10G equipment.
Clear the MEA (BP) Alarm
Step 1 If the MEA is also raised against other equipment, troubleshoot these alarms first.
Step 2 If alarms are reported directly against the XC10G card, such as SWMTXMOD, troubleshoot these alarms next.
Step 3 Determine whether the ONS 15454 SDH shelf assembly is a newer European Telecommunications Standards Institute (ETSI) 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) or an earlier shelf assembly:
a. In node view, click the Inventory tab.
b. In the HW Part # column, if the part number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454E-SA-ETSI).
c. In the HW Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.
Step 4 If the shelf assembly is not compatible with 10-Gbps equipment, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.211 MEA (EQPT)
•Critical (CR), Service-Affecting (SA)
•Logical Object: EQPT
The MEA alarm for equipment is reported against a card slot when the physical card inserted into a slot does not match the card type that is provisioned for that slot in CTC.
Clear the MEA (EQPT) Alarm
Step 1 In CTC, click the Inventory tab to reveal the provisioned card type.
Step 2 If you prefer the card type depicted by CTC, replace the physical card reporting the mismatch with the card type depicted by CTC (provisioned for that slot). Complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 3 If you prefer the card that physically occupies the slot and the card is not in service, has no circuits mapped, and is not part of a protection group, put the cursor over the provisioned card in CTC and right-click to choose Delete Card.
The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
Note If the card is in service, has a circuit mapped, is paired in a working/protection scheme, has DCC communications enabled, or is used as a timing reference, CTC does not allow you to delete the card.
Step 4 If any ports on the card are in service, place them out of service (OOS):
Caution Before placing ports out of service, ensure that no live traffic.
a. Double-click the reporting card to display the card view.
b. Click the Provisioning > Line tab.
c. Click the State column of any in-service (IS) ports.
d. Choose OOS to take the ports out of service.
Step 5 If a circuit has been mapped to the card, complete the "Delete a Circuit" procedure.
Caution Before deleting the circuit, ensure that live traffic is not present.
Step 6 If the card is paired in a protection scheme, delete the protection group:
a. Click the Provisioning > Protection tabs.
b. Choose the protection group of the reporting card.
c. Click Delete.
d. Click Yes in the Delete Protection Group dialog box.
Step 7 Right-click the card reporting the alarm.
Step 8 Choose Delete.
The card that physically occupies the slot reboots, and CTC automatically provisions the card type into that slot.
Step 9 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.212 MEA (FAN)
•Critical (CR), Service-Affecting (SA)
•Logical Object: FAN
The Mismatch of Equipment Attributes alarm is reported against the fan-tray assembly when an older ONS 15454 SDH fan-tray assembly (FTA2) is used with certain cards that require the newer fan-tray assembly (15454E-FTA-48V). The 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) and fan-tray assembly (15454E-FTA-48V) are required with the ONS 15454 SDH OC192 LR/STM64 LH 1550, E1000-2-G, E100T-G, OC48 IR/STM16 SH AS 1310, or OC48 LR/STM16 AS 1550 cards.
Clear the MEA (FAN) Alarm
Step 1 Determine whether the ONS 15454 SDH shelf assembly is a newer ETSI 10-Gbps-compatible shelf assembly (15454E-SA-ETSI) or an earlier shelf assembly:
a. In node view, click the Inventory tab.
b. In the HW Part # column, if the number is 800-08708-XX, then you have a 10-Gbps-compatible shelf assembly (15454-SA-10G).
c. In the HW Part # column, if the number is not 800-08708-XX, then you are using an earlier shelf assembly.
Step 2 If you have a 10-Gbps-compatible shelf assembly (15454E-SA-ETSI), the alarm indicates that an older, incompatible fan-tray assembly is installed in the shelf assembly. Obtain a newer fan-tray assembly (15454-FTA3) with a 5 A fuse and complete the "3.4 Replace the Fan-Tray Assembly" procedure on page 3-9.
Step 3 If you are using an earlier shelf assembly, the alarm indicates that you are using a newer fan-tray assembly (15454-FTA3), which is incompatible with the earlier version of the shelf assembly. Obtain an earlier version of the fan-tray assembly (15454-FTA2) and complete the "3.4 Replace the Fan-Tray Assembly" procedure on page 3-9.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.213 MEM-GONE
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Memory Gone alarm occurs when data generated by software operations exceeds the memory capacity of the TCC2 card. CTC does not function properly until this alarm clears. The alarm clears when additional memory becomes available.
The alarm does not require user intervention. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.214 MEM-LOW
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Free Memory of Card Almost Gone alarm occurs when data generated by software operations is close to exceeding the memory capacity of the TCC2 card. The alarm clears when additional memory becomes available. If additional memory is not made available and the memory capacity of the TCC2 card is exceeded, CTC ceases to function.
The alarm does not require user intervention. Log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.215 MFGMEM (AEP, AIE)
•Critical (CR), Service-Affecting (SA)
•Logical Objects: AEP, AIE
The Manufacturing Data Memory Failure (MFGMEM) alarm occurs if the ONS 15454 SDH cannot access the data in the electronically erasable programmable read-only memory (EEPROM). Either the memory module on the component failed or the TCC2 card lost the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. Inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.
Clear the MFGMEM Alarm
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the standby TCC2 card does not reset itself. If the TCC2 card reset is not complete and error-free or if the TCC2 card reboots itself, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log in to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.
Step 2 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 3 If the alarm does not clear, physically replace the standby TCC2 card on the ONS 15454 SDH with a new TCC2 card. Complete the "Physically Replace a Card" procedure.
Note The active TCC2 card takes up to 30 minutes to transfer the system software to the newly installed TCC2 card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2 card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2 card reboots and goes into standby mode after approximately three minutes.
Step 4 Reset the active TCC2 card. Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the standby TCC2 card does not reset itself. If the TCC2 card reset is not complete and error-free or if the TCC2 card reboots itself, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
Step 5 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.
The ONS 15454 SDH boots up the second TCC2 card. The second TCC2 card must also copy the system software, which can take up to twenty minutes.
Step 6 If the MFGMEM alarm continues to report after replacing the TCC2 cards, the problem is with the EEPROM.
Step 7 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.216 MFGMEM (Backplane or Fan-Tray Assembly)
•Critical (CR), Service-Affecting (SA)
•Logical Objects: BP, FAN
The Manufacturing Data Memory (EEPROM) failure alarm occurs if the ONS 15454 SDH cannot access the data in the EEPROM. Lack of access occurs when either the memory module on the component fails or the TCC2 card loses the ability to read that module. The EEPROM stores manufacturing data that is needed for both compatibility and inventory issues. An inability to read a valid MAC address disrupts IP connectivity and makes the ONS 15454 SDH icon on the CTC network view unavailable.
Clear the MFGMEM Alarm on the Backplane or Fan-Tray Assembly
Step 1 Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Note If CTC stops responding after performing a reset on the TCC2 card, close the browser and start CTC again on the affected node.
Step 2 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure.
Step 3 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.
Note The active TCC2 card takes up to 30 minutes to transfer the system software to the newly installed TCC2 card. Software transfer occurs in instances where different software versions exist on the two cards. During this operation, the TCC2 card LEDs flash to indicate failure and then the active/standby LED flashes. When the transfer completes, the TCC2 card reboots and goes into standby mode after approximately three minutes.
Step 4 Perform a CTC reset on the TCC2 card. Complete the "Reset Active TCC2 Card and Activate Standby Card" procedure.
Step 5 Verify that the remaining TCC2 card is now in standby mode. (The ACT/STBY LED changes to amber.)
Step 6 Physically replace the remaining TCC2 card with the second TCC2 card. Complete the "Physically Replace a Card" procedure.
Step 7 If the MFGMEM alarm continues to report after replacing the TCC2 cards, the problem is with the EEPROM.
Step 8 If the MFGMEM is reported from the fan-tray assembly, replace the fan-tray assembly. Obtain a fan-tray assembly and complete the "3.4 Replace the Fan-Tray Assembly" procedure on page 3-9.
Step 9 If the MFGMEM is reported from backplane, or if the alarm persists after the fan-tray assembly is replaced, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.217 MS-AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STM-N, STM-1E
The Multiplex Section AIS condition indicates that there is a defect in the multiplexing section layer of the SDH overhead. The line layer refers to the segment between two SDH devices in the circuit and is also known as a maintenance span. The line layer deals with SDH payload transport, and its functions include multiplexing and synchronization.
Generally, any AIS is a special SDH signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input 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.
Note DS-3 facility and terminal loopbacks do not transmit DS-3 MS-AIS in the direction away from the loopback. Instead of DS-3 MS-AIS, a continuance of the signal transmitted to the loopback is provided.
Clear the MS-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.218 MS-EOC
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: STM-N
The SDH Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 SDH loses its data communications channel. The DCC is three bytes, D1 through D3, in the SDH overhead. The bytes convey information about OAM&P. The ONS 15454 SDH uses the DCC on the SONET section layer to communicate network management information.
Clear the MS-EOC Alarm
Step 1 Complete the "Clear the EOC Alarm" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.219 MS-RFI
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STM-N, STM-1E
The Multiplex Section (MS) Remote Fault Indication (RFI) condition indicates that there is an RFI occurring at the SDH overhead multiplexing section level.
An RFI occurs when the ONS 15454 SDH detects an RFI in the SDH overhead because of a fault in another node. Resolving the fault in the adjoining node clears the MS-RFI condition in the reporting node.
Clear the MS-RFI Condition
Step 1 Log into the far-end node of the reporting ONS 15454 SDH.
Step 2 Determine whether there are other alarms, especially the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135.
Step 3 Clear the main alarm. Refer to the appropriate alarm section in this chapter for the procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.220 MSSP-OOSYNC
•Major (MJ), Service-Affecting (SA)
•Logical Object: STM-N
The Procedural Error MS-SPRing Out of Synchronization alarm occurs when you attempt to add or delete a circuit and a node on a working ring loses its DCC connection because all transmit and receive fiber has been removed. The CTC cannot generate a table of the nodes and causes the MSSP-OOSYNC alarm.
Warning The ONS 15454 SDH is a Class I (CDRH) and Class 1M (IEC) laser system.
Warning Invisible laser radiation could be emitted from the aperture ports of the single-mode fiber optic modules when no fiber cable is connected. Avoid exposure and do not stare into open apertures.
Note This alarm can also be expected when upgrading to Release 4.6 when the ring identifier is updated.
Clear the MSSP-OOSYNC Alarm
Step 1 Reestablish cabling continuity to the node reporting the alarm. Refer to the Cisco ONS 15454 SDH Procedure Guide for cabling information.
When the DCC is established between the node and the rest of the MS-SPRing, DCC becomes visible to the MS-SPRing and should be able to function on the circuits.
Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" alarm on page 2-72.
Step 3 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.221 NO-CONFIG
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: EQPT
The No Startup Configuration alarm applies to ML-Series Ethernet (traffic) cards and occurs when you preprovision Slots 5 to 6 and 12 to 13 for the card without inserting the card first, or when you insert a card without preprovisioning. (This is an exception to the usual rule in card provisioning.) Because this is normal operation, you should expect this condition during provisioning. When the startup configuration file is copied to the active TCC2, the alarm clears.
Clear the NO-CONFIG Alarm
Step 1 Create a startup configuration for the card in IOS.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.6.
Step 2 Upload the configuration file to the TCC2:
a. In node view, right-click the ML-Series card graphic.
b. Choose IOS Startup Config from the shortcut menu.
c. Click Local > TCC and navigate to the file location.
Step 3 Complete the "Reset a Traffic Card in CTC" procedure.
Step 4 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.222 NOT-AUTHENTICATED
•Default Severity: Minor (MN), Non-Service-Affecting (NSA)
•Logical Object: SYSTEM
The NOT-AUTHENTICATED alarm is raised by CTC (not by the NE) when it fails to log into a node. This alarm only displays in CTC where the login failure occurred. This alarm differs from the "INTRUSION-PSWD" alarm on page 2-121 in that INTRUSION-PSWD occurs when a user exceeds the login failures threshold.
Note NOT-AUTHENTICATED is an informational alarm and is resolved when CTC successfully logs into the node.
2.7.223 NTWTPINC
The NTWTPINC condition is not used in this platform in this release. It is reserved for future development.
2.7.224 OCHNC-ACTIV-FAIL
The OCHNC-ACTIV-FAIL alarm is not used in this platform in this release. It is reserved for future development.
2.7.225 OCHNC-DEACTIV-FAIL
The OCHNC-DEACTIV-FAIL alarm is not used in this platform in this release. It is reserved for future development.
2.7.226 OCHNC-FAIL
The OCHNC-FAIL alarm is not used in this platform in this release. It is reserved for future development.
2.7.227 OCHNC-INC
The OCHNC-INC alarm is not used in this platform in this release. It is reserved for future development.
2.7.228 ODUK-AIS-PM
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The Optical Data Unit (ODUK) AIS Path Monitoring (PM) condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled for the cards. ODUK-AIS-PM is a secondary condition that indicates that a more serious condition such as the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135 is occurring downstream. ODUK-AIS-PM is reported in the path monitoring area of the optical data unit wrapper overhead and is caused by the upstream "ODUK-OCI-PM" condition on page 2-163.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-AIS-PM Condition
Step 1 Determine whether the upstream nodes and equipment have alarms, especially the "LOF (DS-3, E-1, E-4, STM-N, STM1-E)" alarm on page 2-131, or OOS 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 Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.229 ODUK-BDI-PM
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Backward Defect Indicator (BDI) PM condition applies to TXP_MR_10G, TXP_MR_2.5G, or TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled for the cards. ODUK-BDI-PM indicates that there is a path termination error upstream in the data. The error is read as a BDI bit in the path monitoring area of the digital wrapper overhead. ODUK-BDI-PM occurs when a "PORT-CODE-MISM" alarm on page 2-173 occurs upstream.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-BDI-PM Condition
Step 1 Complete the "Clear the OTUK-BDI Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.230 ODUK-LCK-PM
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Locked Defect (LCK) PM condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled for the cards. ODUK-LCK-PM indicates that a signal is being sent downstream to indicate that the upstream connection is locked, preventing the signal from being passed. The lock is indicated by the STAT bit in the path overhead monitoring fields of the optical transport unit overhead of the digital wrapper.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-LCK-PM Condition
Step 1 Unlock the upstream node signal.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.231 ODUK-OCI-PM
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Open Connection Indication (OCI) PM condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled for the cards. ODUK-OCI-PM indicates that the upstream signal is not connected to a trail termination source. The error is read as a STAT bit in the path monitoring area of the digital wrapper overhead. ODUK-OCI-PM causes an "ODUK-AIS-PM" condition on page 2-161 downstream.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-OCI-PM Condition
Step 1 Verify that upstream nodes do not have fiber connectivity problems.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.232 ODUK-SD-PM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Signal Degrade (SD) PM condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled. ODUK-SD-PM indicates that incoming signal quality is poor, but the incoming line BER has not passed the fail threshold. The BER problem is indicated in the path monitoring area of the optical data unit frame overhead.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-SD-PM Condition
Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.233 ODUK-SF-PM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Signal Fail (SF) PM condition (ODUK-SD-PM) applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled. ODUK-SF-PM indicates that incoming signal quality is poor and the incoming line BER has passed the fail threshold. The BER problem is indicated in the path monitoring area of the optical data unit frame overhead.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-SF-PM Condition
Step 1 Complete the "Clear the SD (DS-3, E-1, E-3, E-4, LPTerm, STM-N, STM-1E) Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.234 ODUK-TIM-PM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The ODUK Trace Identifier Mismatch (TIM) PM condition applies to the path monitoring area of the optical transport network (OTN) overhead for TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards. ODUK-TIM-PM occurs when there is a trace identifier mismatch in the data stream. The condition causes a "BKUPMEMP" alarm on page 2-46 downstream.
The ODUK-TIM-PM condition applies to TXP cards or MXP cards when ITU-T G.709 monitoring is enabled for the cards. ODUK-TIM-PM indicates that there is an error upstream in the optical transport unit overhead of the digital wrapper.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the ODUK-TIM-PM Condition
Step 1 Complete the "Clear the TIM Alarm or Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.235 OOU-TPT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: HPTerm, LPTerm
The Out of Use Transport Failure alarm is a VCat member alarm. (VCat member circuits are independent circuits that are concatenated from different time slots into a higher-rate signal.) This condition is raised when a member circuit in a VCat is unused. It occurs in conjunction with the "VCG-DEG" alarm on page 2-209.
Clear the OOT-TPT Condition
Step 1 Complete the "Clear the VCG-DEG Condition" procedure. Clearing that condition clears this condition as well.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.236 OPTNTWMIS
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The Optical Network Type Mismatch alarm is raised when DWDM nodes are not configured for the same type of network, either MetroCore and MetroAccess. All DWDM nodes on the same network must be configured for the same network type because automatic power control (APC) and automatic node setup (ANS) behave differently on each of these network types.
The "APC-DISABLED" alarm on page 2-26 could accompany the OPTNTWMIS alarm.
Clear the OPTNTWMIS Alarm
Step 1 In node view of the alarmed node, click the Provisioning > WDM-ANS tabs.
Step 2 Choose the correct option from the Network Type list box, and click Apply.
Step 3 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.237 OPWR-HDEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Optical Power Degrade High alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE amplifier cards on the Line-1 TX port when an internal problem on the card prevents the card from maintaining the output power setpoint at the output port. It occurs on optical add/drop cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x); demultiplexers (32 DMX-O); combiners (4MD-xx.x), and optical service channel cards (OSCM and OSC-CSM) when there is a failure on the variable optical attenuator (VOA) circuit.
Clear the OPWR-HDEG Alarm
Step 1 This alarm does not immediately affect traffic, but to clear it, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 2 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.238 OPWR-HFAIL
•Critical (CR), Service-Affecting (SA)
•Logical Object: E-4
The Optical Power Fail High alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE amplifier cards on the Line-1 TX port when an internal card problem on the card prevents the card from maintaining the output power setpoint at the output port and the card fails. It occurs on optical add/drop cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x); demultiplexers (32 DMX-O); combiners (4MD-xx.x), and optical service channel cards (OSCM and OSC-CSM) when there is a failure on the VOA circuit.
Clear the OPWR-HFAIL Alarm
Step 1 If the alarm is raised against an input port, check the cabling placement and check the cable continuity with an optical test set.
Step 2 If the cabling is not the source of the input power problem, decrease the TX output power to the card.
Step 3 If the alarm is raised against an amplifier output port, or if decreasing the incoming TX power does not clear the alarm, it indicates that there a failure on the VOA circuit or an internal problem. Provided that service is affected, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.239 OPWR-LDEG
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: E-4
The Optical Power Degrade Low alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE amplifier cards on the Line-1 TX port when an internal problem prevents the output power on the output port from reaching the setpoint. It occurs on optical add/drop cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x); demultiplexers (32 DMX-O); combiners (4MD-xx.x), and optical service channel cards (OSCM and OSC-CSM) when the incoming power is too low, or there is a failure on the VOA control circuit.
Clear the OPWR-LDEG Alarm
Step 1 If the alarm is raised on an amplifier, it does not immediately affect traffic, but to clear it, complete the "Physically Replace a Card" procedure for the reporting card.
Step 2 If the alarm is raised on an OADM, multiplexer/demultiplexer, or OSC/OSC-CSM card, check the power calibration value of the corresponding port and the Pout value for the OADM:
a. In node view, click the Provisioning > WDM-ANS tabs.
b. Verify that the Power Calibration value and Pout values for the OADM card are consistent with the MetroPlanner configuration output for the node.
c. If the values are not correct, change them and click Apply.
Step 3 If the calibration and output power values are correct, there could be a failure on the card VOA circuit. You do not need to replace the card immediately, but eventually will need to complete the "Physically Replace a Card" procedure.
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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.240 OPWR-LFAIL
•Critical (CR), Service-Affecting (SA)
•Logical Object: E-4
The Optical Power Fail Low alarm is raised by OPT-BST amplifier cards on the Line-3 TX port and OPT-PRE amplifier cards on the Line-1 TX port; on optical add/drop cards (AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x); demultiplexers (32 DMX-O); combiners (4MD-xx.x), and optical service channel cards (OSCM and OSC-CSM) when incoming optical power for the input port or output port is too low.
Clear the OPWR-LFAIL Alarm
Step 1 If the alarm is raised against an input port, check the cabling placement and check the cable continuity with an optical test set.
Step 2 If the cabling is not the source of the input power problem, increase the TX output power to the card.
Step 3 If the alarm is raised against an amplifier output port, or if increasing the incoming TX power does not clear the alarm, it indicates that there a failure on the VOA circuit or an internal problem. Provided that service is affected, complete the "Physically Replace a Card" procedure for the reporting 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. Refer to the
Cisco ONS 15454 SDH Procedure Guide for information.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country in order to report a service-affecting problem.
2.7.241 OTUK-AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The Optical Transport Unit (OTUK) AIS condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled when ITU-T G.709 monitoring is enabled for the cards. The OTUK-AIS is a secondary condition that indicates a more serious condition such as the "LOS (DS-3, E-1, E-3, STM-N, STM-1E)" alarm on page 2-135 is occurring downstream. The OTUK-AIS is reported in the optical transport unit overhead of the digital wrapper.
ITU-T G.709 monitoring refers to a digital data wrapper that is transparent across networking standards (such as SDH) and protocols (such as Ethernet or IP). For information about provisioning the TXP card or MXP card to enable ITU-T G.709 monitoring, refer to the Cisco ONS 15454 SDH Procedure Guide.
Clear the OTUK-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log into the Cisco Technical Support Website at http://www.cisco.com/techsupport for more information or log into http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free TAC numbers for your country.
2.7.242 OTUK-BDI
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: DWDM Trunk
The OTUK-BDI condition applies to TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or MXP_2.5G_10G cards when ITU-T G.709 monitoring is enabled for the cards. OTUK-BDI is indicated by the BDI bit in the section monitoring overhead. The condition accompanies an "SF (DS-3, E-1, E-3, E-4, LPTerm, STM-N)"
Feedback
