Table Of Contents
Alarm Troubleshooting
2.1 Alarm Index by Default Severity
2.1.1 Critical Alarms (CR)
2.1.2 Major Alarms (MJ)
2.1.3 Minor Alarms (MN)
2.1.4 Conditions (NA or NR)
2.2 Alarms and Conditions Indexed By Alphabetical Entry
2.3 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
Clear the AIS-L Condition
2.7.3 AIS-P
Clear the AIS-P Condition
2.7.4 AIS-V
Clear the AIS-V Condition
2.7.5 ALS
2.7.6 AMPLI-INIT
Clear the AMPLI-INIT Condition
2.7.7 APC-DISABLED
Clear the APC-DISABLED Alarm
2.7.8 APC-FAIL
Clear the APC-FAIL Alarm
2.7.9 APSB
Clear the APSB Alarm
2.7.10 APSCDFLTK
Clear the APSCDFLTK Alarm
2.7.11 APSC-IMP
Clear the APSC-IMP Alarm
2.7.12 APSCINCON
Clear the APSCINCON Alarm
2.7.13 APSCM
Clear the APSCM Alarm
2.7.14 APSCNMIS
Clear the APSCNMIS Alarm
2.7.15 APSMM
Clear the APSMM Alarm
2.7.16 AS-CMD
Clear the AS-CMD Condition
2.7.17 AS-MT
Clear the AS-MT Condition
2.7.18 AUD-LOG-LOSS
Clear the AUD-LOG-LOSS Condition
2.7.19 AUD-LOG-LOW
2.7.20 AUTOLSROFF
Clear the AUTOLSROFF Alarm
2.7.21 AUTORESET
Clear the AUTORESET Alarm
2.7.22 AUTOSW-AIS
Clear the AUTOSW-AIS Condition
2.7.23 AUTOSW-LOP (STSMON)
Clear the AUTOSW-LOP (STSMON) Condition
2.7.24 AUTOSW-LOP (VTMON)
Clear the AUTOSW-LOP (VTMON) Alarm
2.7.25 AUTOSW-PDI
Clear the AUTOSW-PDI Condition
2.7.26 AUTOSW-SDBER
Clear the AUTOSW-SDBER Condition
2.7.27 AUTOSW-SFBER
Clear the AUTOSW-SFBER Condition
2.7.28 AUTOSW-UNEQ (STSMON)
Clear the AUTOSW-UNEQ (STSMON) Condition
2.7.29 AUTOSW-UNEQ (VTMON)
Clear the AUTOSW-UNEQ (VTMON) Alarm
2.7.30 BAT-A-HGH-VLT
Clear the BAT-A-HGH-VLT Condition
2.7.31 BAT-A-LOW-VLT
Clear the BAT-A-LOW-VLT Condition
2.7.32 BAT-B-HGH-VLT
Clear the BAT-B-HGH-VLT Condition
2.7.33 BAT-B-LOW-VLT
Clear the BAT-B-LOW-VLT Condition
2.7.34 BKUPMEMP
Clear the BKUPMEMP Alarm
2.7.35 BLSROSYNC
Clear the BLSROSYNC 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 CKTDOWN
Clear the CKTDOWN Alarm
2.7.43 CLDRESTART
Clear the CLDRESTART Condition
2.7.44 COMIOXC
Clear the COMIOXC Alarm
2.7.45 COMM-FAIL
Clear the COMM-FAIL Alarm
2.7.46 CONTBUS-A-18
Clear the CONTBUS-A-18 Alarm
2.7.47 CONTBUS-B-18
Clear the CONTBUS-B-18 Alarm
2.7.48 CONTBUS-IO-A
Clear the CONTBUS-IO-A Alarm
2.7.49 CONTBUS-IO-B
Clear the CONTBUS-IO-B Alarm
2.7.50 CTNEQPT-PBPROT
Clear the CTNEQPT-PBPROT Alarm
2.7.51 CTNEQPT-PBWORK
Clear the CTNEQPT-PBWORK Alarm
2.7.52 DATAFLT
Clear the DATAFLT Alarm
2.7.53 DBOSYNC
Clear the DBOSYNC Alarm
2.7.54 DS3-MISM
Clear the DS3-MISM Condition
2.7.55 DSP-COMM-FAIL
2.7.56 DSP-FAIL
Clear the DSP-FAIL Alarm
2.7.57 EHIBATVG-A
Clear the EHIBATVG-A Alarm
2.7.58 EHIBATVG-B
Clear the EHIBATVG-B Alarm
2.7.59 ELWBATVG-A
Clear the ELWBATVG-A Alarm
2.7.60 ELWBATVG-B
Clear the ELWBATVG-B Alarm
2.7.61 EOC
Clear the EOC Alarm
2.7.62 EQPT
Clear the EQPT Alarm
2.7.63 EQPT-MISS
Clear the EQPT-MISS Alarm
2.7.64 ERFI-P-CONN
Clear the ERFI-P-CONN Condition
2.7.65 ERFI-P-PAYLD
Clear the ERFI-P-PAYLD Condition
2.7.66 ERFI-P-SRVR
Clear the ERFI-P-SRVR Condition
2.7.67 ERROR-CONFIG
Clear the ERROR-CONFIG Alarm
2.7.68 E-W-MISMATCH
Clear the E-W-MISMATCH Alarm with a Physical Switch
Clear the E-W-MISMATCH Alarm in CTC
2.7.69 EXCCOL
Clear the EXCCOL Alarm
2.7.70 EXERCISE-RING-FAIL
Clear the EXERCISE-RING-FAIL Condition
2.7.71 EXERCISE-RING-REQ
2.7.72 EXERCISE-SPAN-FAIL
Clear the EXERCISE-SPAN-FAIL Condition
2.7.73 EXERCISE-SPAN-REQ
2.7.74 EXT
Clear the EXT Alarm
2.7.75 EXTRA-TRAF-PREEMPT
Clear the EXTRA-TRAF-PREEMPT Alarm
2.7.76 FAILTOSW
Clear the FAILTOSW Condition
2.7.77 FAILTOSW-PATH
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
2.7.78 FAILTOSWR
Clear the FAILTOSWR Condition in a Four-Fiber BLSR Configuration
2.7.79 FAILTOSWS
Clear the FAILTOSWS Condition
2.7.80 FAN
Clear the FAN Alarm
2.7.81 FANDEGRADE
Clear the FANDEGRADE Alarm
2.7.82 FE-AIS
Clear the FE-AIS Condition
2.7.83 FEC-MISM
Clear the FEC-MISM Alarm
2.7.84 FE-DS1-MULTLOS
Clear the FE-DS1-MULTLOS Condition
2.7.85 FE-DS1-NSA
Clear the FE-DS1-NSA Condition
2.7.86 FE-DS1-SA
Clear the FE-DS1-SA Condition
2.7.87 FE-DS1-SNGLLOS
Clear the FE-DS1-SNGLLOS Condition
2.7.88 FE-DS3-NSA
Clear the FE-DS3-NSA Condition
2.7.89 FE-DS3-SA
Clear the FE-DS3-SA Condition
2.7.90 FE-EQPT-NSA
Clear the FE-EQPT-NSA Condition
2.7.91 FE-EXERCISING-RING
2.7.92 FE-EXERCISING-SPAN
2.7.93 FE-FRCDWKSWPR-RING
Clear the FE-FRCDWKSWPR-RING Condition
2.7.94 FE-FRCDWKSWPR-SPAN
Clear the FE-FRCDWKSWPR-SPAN Condition
2.7.95 FE-IDLE
Clear the FE-IDLE Condition
2.7.96 FE-LOCKOUTOFPR-SPAN
Clear the FE-LOCKOUTOFPR-SPAN Condition
2.7.97 FE-LOF
Clear the FE-LOF Condition
2.7.98 FE-LOS
Clear the FE-LOS Condition
2.7.99 FE-MANWKSWPR-RING
Clear the FE-MANWKSWPR-RING Condition
2.7.100 FE-MANWKSWPR-SPAN
Clear the FE-MANWKSWPR-SPAN Condition
2.7.101 FEPRLF
Clear the FEPRLF Alarm on a Four-Fiber BLSR
2.7.102 FORCED-REQ
Clear the FORCED-REQ Condition
2.7.103 FORCED-REQ-RING
Clear the FORCED-REQ-RING Condition
2.7.104 FORCED-REQ-SPAN
Clear the FORCED-REQ-SPAN Condition
2.7.105 FRCDSWTOINT
2.7.106 FRCDSWTOPRI
2.7.107 FRCDSWTOSEC
2.7.108 FRCDSWTOTHIRD
2.7.109 FRNGSYNC
Clear the FRNGSYNC Alarm
2.7.110 FSTSYNC
2.7.111 FULLPASSTHR-BI
Clear the FULLPASSTHR-BI Condition
2.7.112 GCC-EOC
Clear the GCC-EOC Alarm
2.7.113 HI-LASERBIAS
Clear the HI-LASERBIAS Alarm
2.7.114 HI-LASERTEMP
Clear the HI-LASERTEMP Alarm
2.7.115 HI-RXPOWER
Clear the HI-RXPOWER Alarm
2.7.116 HI-RXTEMP
Clear the HI-RXTEMP Alarm
2.7.117 HITEMP
Clear the HITEMP Alarm
2.7.118 HI-TXPOWER
Clear the HI-TXPOWER Alarm
2.7.119 HLDOVRSYNC
Clear the HLDOVRSYNC Alarm
2.7.120 IMPROPRMVL
Clear the IMPROPRMVL Alarm
2.7.121 INC-ISD
2.7.122 INHSWPR
Clear the INHSWPR Condition
2.7.123 INHSWWKG
Clear the INHSWWKG Condition
2.7.124 INTRUSION-PSWD
Clear the INTRUSION-PSWD Condition
2.7.125 INVMACADR
Clear the INVMACADR Alarm
2.7.126 IOSCFGCOPY
2.7.127 KB-PASSTHR
Clear the KB-PASSTHR Condition
2.7.128 KBYTE-APS-CHANNEL-FAILURE
Clear the KBYTE-APS-CHANNEL-FAILURE Alarm
2.7.129 LAN-POL-REV
Clear the LAN-POL-REV Condition
2.7.130 LASEREOL
Clear the LASEREOL Alarm
2.7.131 LKOUTPR-S
Clear the LKOUTPR-S Condition
2.7.132 LMP-HELLODOWN
Clear the LMP-HELLODOWN Alarm
2.7.133 LMP-NDFAIL
Clear the LMP-NDFAIL Alarm
2.7.134 LOC
Clear the LOC Alarm
2.7.135 LOCKOUT-REQ
Clear the LOCKOUT-REQ Condition
2.7.136 LOCKOUT-REQ-RING
Clear the LOCKOUT-REQ-RING Condition
2.7.137 LOF (BITS)
Clear the LOF (BITS) Alarm
2.7.138 LOF (DS-1)
Clear the LOF (DS-1) Alarm
2.7.139 LOF (DS-3)
Clear the LOF (DS-3) Alarm
2.7.140 LOF (DWDM Client)
Clear the LOF (DWDM Client) Alarm
2.7.141 LOF (DWDM Trunk)
Clear the LOF (DWDM Trunk) Alarm
2.7.142 LOF (EC1-12)
Clear the LOF (EC1-12) Alarm
2.7.143 LOF (OC-N)
Clear the LOF (OC-N) Alarm
2.7.144 LO-LASERBIAS
Clear the LO-LASERBIAS Alarm
2.7.145 LO-LASERTEMP
Clear the LO-LASERTEMP Alarm
2.7.146 LOM
Clear the LOM Alarm
2.7.147 LOP-P
Clear the LOP-P Alarm
2.7.148 LOP-V
Clear the LOP-V Alarm
2.7.149 LO-RXPOWER
Clear the LO-RXPOWER Alarm
2.7.150 LO-RXTEMP
Clear the LO-RXTEMP Alarm
2.7.151 LOS (BITS)
Clear the LOS (BITS) Alarm
2.7.152 LOS (DS-1)
Clear the LOS (DS-1) Alarm
2.7.153 LOS (DS-3)
Clear the LOS (DS-3) Alarm
2.7.154 LOS (DWDM Client or Trunk)
Clear the LOS (DWDM Client) Alarm
2.7.155 LOS (EC1-12)
Clear the LOS (EC1-12) Alarm
2.7.156 LOS (FUDC)
Clear the LOS (FUDC) Alarm
2.7.157 LOS (MSUDC)
Clear the LOS (MSUDC) Alarm
2.7.158 LOS (OC-N)
Clear the LOS (OC-N) Alarm
2.7.159 LOS (OTN)
Clear the LOS (OTN) Alarm
2.7.160 LO-TXPOWER
Clear the LO-TXPOWER Alarm
2.7.161 LPBKCRS
Clear the LPBKCRS Condition
2.7.162 LPBKDS1FEAC
Clear the LPBKDS1FEAC Condition
2.7.163 LPBKDS1FEAC-CMD
2.7.164 LPBKDS3FEAC
Clear the LPBKDS3FEAC Condition
2.7.165 LPBKDS3FEAC-CMD
2.7.166 LPBKFACILITY (DS-1 or DS-3)
Clear the LPBKFACILITY (DS-1 or DS-3) Condition
2.7.167 LPBKFACILITY (DWDM Client, DWDM Trunk)
Clear the LPBKFACILITY (DWDM Client, DWDM Trunk) Condition
2.7.168 LPBKFACILITY (EC1-12)
Clear the LPBKFACILITY (EC1-12) Condition
2.7.169 LPBKFACILITY (G-Series Ethernet)
Clear the LPBKFACILITY (G-Series Ethernet) Condition
2.7.170 LPBKFACILITY (OC-N)
Clear the LPBKFACILITY (OC-N) Condition
2.7.171 LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
Clear the LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N) Condition
2.7.172 LPBKTERMINAL (DWDM Client, DWDM Trunk)
Clear the LPBKTERMINAL (DWDM Client) Condition
2.7.173 LPBKTERMINAL (G-Series Ethernet)
Clear the LPBKTERMINAL (G-Series Ethernet) Condition
2.7.174 MAN-REQ
Clear the MAN-REQ Condition
2.7.175 MANRESET
2.7.176 MANSWTOINT
2.7.177 MANSWTOPRI
2.7.178 MANSWTOSEC
2.7.179 MANSWTOTHIRD
2.7.180 MANUAL-REQ-RING
Clear the MANUAL-REQ-RING Condition
2.7.181 MANUAL-REQ-SPAN
Clear the MANUAL-REQ-SPAN Condition
2.7.182 MEA (AIP)
Clear the MEA (AIP) Alarm
2.7.183 MEA (BPLANE)
Clear the MEA (BPLANE) Alarm
2.7.184 MEA (EQPT)
Clear the MEA (EQPT) Alarm
2.7.185 MEA (FAN)
Clear the MEA (FAN) Alarm
2.7.186 MEM-GONE
2.7.187 MEM-LOW
2.7.188 MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
Clear the MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly) Alarm
2.7.189 NO-CONFIG
Clear the NO-CONFIG Condition
2.7.190 NOT-AUTHENTICATED
2.7.191 ODUK-AIS-PM
Clear the ODUK-AIS-PM Condition
2.7.192 ODUK-BDI-PM
Clear the ODUK-BDI-PM Condition
2.7.193 ODUK-LCK-PM
Clear the ODUK-LCK-PM Condition
2.7.194 ODUK-OCI-PM
Clear the ODUK-OCI-PM Condition
2.7.195 ODUK-SD-PM
Clear the ODUK-SD-PM Condition
2.7.196 ODUK-SF-PM
Clear the ODUK-SF-PM Condition
2.7.197 ODUK-TIM-PM
Clear the ODUK-TIM-PM Condition
2.7.198 OPTNTWMIS
Clear the OPTNTWMIS Alarm
2.7.199 OTUK-AIS
Clear the OTUK-AIS Condition
2.7.200 OTUK-BDI
Clear the OTUK-BDI condition
2.7.201 OTUK-LOF
Clear the OTUK-LOF Alarm
2.7.202 OTUK-SD
Clear the OTUK-SD Condition
2.7.203 OTUK-SF
Clear the OTUK-SF Condition
2.7.204 OTUK-TIM
Clear the OTUK-TIM Condition
2.7.205 PDI-P
Clear the PDI-P Condition
2.7.206 PEER-NORESPONSE
Clear the PEER-NORESPONSE Alarm
2.7.207 PLM-P
Clear the PLM-P Alarm
2.7.208 PLM-V
Clear the PLM-V Alarm
2.7.209 PORT-CODE-MISM
Clear the PORT-CODE-MISM Alarm
2.7.210 PORT-COMM-FAIL
Clear the PORT-COMM-FAIL Alarm
2.7.211 PORT-MISMATCH
2.7.212 PORT-MISSING
Clear the PORT-MISSING Alarm
2.7.213 PRC-DUPID
Clear the PRC-DUPID Alarm
2.7.214 PROTNA
Clear the PROTNA Alarm
2.7.215 PTIM
Clear the PTIM Alarm
2.7.216 PWR-A
Clear the PWR-A Alarm
2.7.217 PWR-B
Clear the PWR-B Alarm
2.7.218 PWR-REDUN
Clear the PWR-REDUN Alarm
2.7.219 RAI
Clear the RAI Condition
2.7.220 RCVR-MISS
Clear the RCVR-MISS Alarm
2.7.221 RFI
.Clear the RFI Condition
2.7.222 RFI-L
Clear the RFI-L Condition
2.7.223 RFI-P
Clear the RFI-P Condition
2.7.224 RFI-V
Clear the RFI-V Condition
2.7.225 RING-ID-MIS
Clear the RING-ID-MIS Alarm
2.7.226 RING-MISMATCH
Clear the RING-MISMATCH Alarm
2.7.227 RING-SW-EAST
2.7.228 RING-SW-WEST
2.7.229 RSVP-HELLODOWN
Clear the RSVP-HELLODOWN Alarm
2.7.230 RUNCFG-SAVENEED
2.7.231 SD (DS-1, DS-3)
Clear the SD (DS-1, DS-3) Condition
2.7.232 SD (DWDM Client, DWDM Trunk)
Clear the SD (DWDM Client or Trunk) Condition
2.7.233 SD-L
Clear the SD-L Condition
2.7.234 SD-P
Clear the SD-P Condition
2.7.235 SF (DS-1, DS-3)
Clear the SF (DS-1, DS-3) Condition
2.7.236 SF (DWDM Client, Trunk)
Clear the SF (DWDM Client, Trunk) Condition
2.7.237 SF-L
Clear the SF-L Condition
2.7.238 SF-P
Clear the SF-P Condition
2.7.239 SFTWDOWN
2.7.240 SNTP-HOST
Clear the SNTP-HOST Alarm
2.7.241 SPAN-SW-EAST
2.7.242 SPAN-SW-WEST
2.7.243 SQUELCH
Clear the SQUELCH Condition
2.7.244 SQUELCHED
Clear the SQUELCHED Alarm
2.7.245 SSM-DUS
2.7.246 SSM-FAIL
Clear the SSM-FAIL Alarm
2.7.247 SSM-LNC
2.7.248 SSM-OFF
Clear the SSM-OFF Condition
2.7.249 SSM-PRC
2.7.250 SSM-PRS
2.7.251 SSM-RES
2.7.252 SSM-SMC
2.7.253 SSM-ST2
2.7.254 SSM-ST3
2.7.255 SSM-ST3E
2.7.256 SSM-ST4
2.7.257 SSM-STU
Clear the SSM-STU Condition
2.7.258 SSM-TNC
2.7.259 SWMTXMOD
Clear the SWMTXMOD Alarm
2.7.260 SWTOPRI
2.7.261 SWTOSEC
Clear the SWTOSEC Condition
2.7.262 SWTOTHIRD
Procedure: Clear the SWTOTHIRD Condition
2.7.263 SYNC-FREQ
Clear the SYNC-FREQ Condition
2.7.264 SYNCPRI
Clear the SYNCPRI Alarm
2.7.265 SYNCSEC
Clear the SYNCSEC Alarm
2.7.266 SYNCTHIRD
Clear the SYNCTHIRD Alarm
2.7.267 SYSBOOT
2.7.268 TIM
Clear the TIM Alarm or Condition
2.7.269 TIM-MON
Clear the TIM-MON Alarm
2.7.270 TIM-P
Clear the TIM-P Alarm
2.7.271 TPTFAIL (G-Series Ethernet)
Clear the TPTFAIL (G-Series) Alarm
2.7.272 TPTFAIL (ML-Series Ethernet)
Clear the TPTFAIL (ML-Series) Alarm
2.7.273 TRMT
Clear the TRMT Alarm
2.7.274 TRMT-MISS
Clear the TRMT-MISS Alarm
2.7.275 TUNDERRUN
Clear the TUNDERRUN Alarm
2.7.276 UNC-WORD
Clear the UNC-WORD Condition
2.7.277 UNEQ-P
Clear the UNEQ-P Alarm
2.7.278 UNEQ-V
Clear the UNEQ-V Alarm
2.7.279 WKSWPR
Clear the WKSWPR Condition
2.7.280 WTR
2.7.281 WVL-MISMATCH
Clear the WVL-MISMATCH alarm
2.8 DS3-12 E Line Alarms
2.9 DWDM and Non-DWDM Card LED Activity
2.9.1 DWDM Card LED Activity After Insertion
2.9.2 Non-DWDM Card LED Activity After Insertion
2.9.3 DWDM Card LED Activity During Reset
2.9.4 Non-DWDM Card LED Activity During Reset
2.9.5 Non-DWDM Cross-Connect LED Activity During Side Switch
2.9.6 Non-DWDM Card LED State After Successful Reset
2.10 Common Procedures in Alarm Troubleshooting
Identify a Ring ID or Node ID Number
Change a Ring ID Number
Change a Node ID Number
Verify Node Visibility for Other Nodes
Verify or Create Node DCC Terminations
Lock Out a BLSR Span
Clear a BLSR Span Lock Out
Clear a Path Protection Lock Out
Switch Protection Group Traffic with an External Switching Command
Side Switch the Active and Standby Cross-Connect Cards
Clear an External Switching Command
Delete a Circuit
Clear a Loopback
Reset Active TCC+/TCC2 Card and Activate Standby Card
Remove and Reinsert (Reseat) the Standby TCC+/TCC2
Reset a Traffic Card or Cross-Connect Card in CTC
Verify BER Threshold Level
Physically Replace a Card
Remove and Reinsert (Reseat) a Card
Remove and Reinsert Fan-Tray Assembly
Alarm Troubleshooting
Note 
The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.
This chapter gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ONS 15454 alarm and condition. Tables 2-1 through 2-4 provide lists of ONS 15454 alarms organized by severity. Table 2-5 provides a list of alarm organized alphabetically. Table 2-7 provides a list of alarms organized by alarm type. For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.
The troubleshooting procedure for an alarm applies to both the Cisco Transport Controller (CTC) and TL1 version of that alarm. If the troubleshooting procedure does not clear the alarm, log onto http://www.cisco.com/tac for more information or call the Cisco Technical Assistance Center (TAC) to report a service-affecting problem (1-800-553-2447).
For alarm profile information, refer to the Cisco ONS 15454 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, which is the same severity used when reported by TL1. All severities listed in this manual are the default profile settings. Alarm severities can be altered from default settings for individual alarms or groups of alarms by creating a non-default alarm profile and applying it on a port, card, or shelf basis. All settings (default or user-defined) that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.
Note The CTC default alarm profile contains alarms that apply to multiple product platforms. The alarms that apply to this product are listed in the following tables and sections.
2.1.1 Critical Alarms (CR)
Table 2-1 lists Critical alarms.
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 Conditions (NA or NR)
Table 2-4 lists Not Alarmed or Not Reported conditions.
Table 2-4 Conditions Index
AIS
|
FE-MANWKSWPR-RING
|
ODUK-SF-PM
|
AIS-L
|
FE-MANWKSWPR-SPAN
|
ODUK-TIM-PM
|
AIS-P
|
FORCED-REQ
|
OTUK-AIS
|
AIS-V
|
FORCED-REQ-RING
|
OTUK-BDI
|
ALS
|
FORCED-REQ-SPAN
|
OTUK-SD
|
AMPLI-INIT
|
FRCDSWTOINT
|
OTUK-SF
|
AS-CMD
|
FRCDSWTOPRI
|
OTUK-TIM
|
AS-MT
|
FRCDSWTOSEC
|
PDI-P
|
AUD-LOG-LOSS
|
FRCDSWTOTHIRD
|
RAI
|
AUD-LOG-LOW
|
FRNGSYNC
|
RFI
|
AUTOSW-AIS
|
FULLPASSTHR-BI
|
RFI-L
|
AUTOSW-LOP (STSMON)
|
HLDOVRSYNC, for Release 4.1
|
RFI-P
|
AUTOSW-PDI
|
INC-ISD
|
RFI-V
|
AUTOSW-SDBER
|
INHSWPR
|
RING-SW-EAST
|
AUTOSW-SFBER
|
INHSWWKG
|
RING-SW-WEST
|
AUTOSW-UNEQ (STSMON)
|
INTRUSION-PSWD
|
RUNCFG-SAVENEED
|
BAT-A-HGH-VLT
|
IOSCFGCOPY
|
SD (DS-1, DS-3)
|
BAT-A-LOW-VLT
|
KB-PASSTHR
|
SD (DWDM Client, DWDM Trunk)
|
BAT-B-HGH-VLT
|
LAN-POL-REV
|
SD-L
|
BAT-B-LOW-VLT
|
LKOUTPR-S
|
SD-P
|
CLDRESTART
|
LOCKOUT-REQ
|
SF (DS-1, DS-3)
|
DS3-MISM
|
LOCKOUT-REQ-RING
|
SF (DWDM Client, Trunk)
|
ERFI-P-CONN
|
LPBKCRS
|
SF-L
|
ERFI-P-PAYLD
|
LPBKDS1FEAC
|
SF-P
|
ERFI-P-SRVR
|
LPBKDS1FEAC-CMD
|
SPAN-SW-EAST
|
EXERCISE-RING-FAIL
|
LPBKDS3FEAC
|
SPAN-SW-WEST
|
EXERCISE-RING-REQ
|
LPBKDS3FEAC-CMD
|
SQUELCH
|
EXERCISE-SPAN-FAIL
|
LPBKFACILITY (DS-1 or DS-3)
|
SQUELCHED
|
EXERCISE-SPAN-REQ
|
LPBKFACILITY (DWDM Client, DWDM Trunk)
|
SSM-DUS
|
FAILTOSW
|
LPBKFACILITY (EC1-12)
|
SSM-LNC
|
FAILTOSW-PATH
|
LPBKFACILITY (G-Series Ethernet)
|
SSM-OFF
|
FAILTOSWR
|
LPBKFACILITY (OC-N)
|
SSM-PRC
|
FAILTOSWS
|
LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
SSM-PRS
|
FE-AIS
|
LPBKTERMINAL (DWDM Client, DWDM Trunk)
|
SSM-RES
|
FE-DS1-MULTLOS
|
LPBKTERMINAL (G-Series Ethernet)
|
SSM-SMC
|
FE-DS1-NSA
|
MAN-REQ
|
SSM-ST2
|
FE-DS1-SA
|
MANRESET
|
SSM-ST3
|
FE-DS1-SNGLLOS
|
MANSWTOINT
|
SSM-ST3E
|
FE-DS3-NSA
|
MANSWTOPRI
|
SSM-ST4
|
FE-DS3-SA
|
MANSWTOSEC
|
SSM-STU
|
FE-EQPT-NSA
|
MANSWTOTHIRD
|
SSM-TNC
|
FE-EXERCISING-RING
|
MANUAL-REQ-RING
|
SWTOPRI
|
FE-EXERCISING-SPAN
|
MANUAL-REQ-SPAN
|
SWTOSEC
|
FE-FRCDWKSWPR-RING
|
NO-CONFIG
|
SWTOTHIRD
|
FE-FRCDWKSWPR-SPAN
|
ODUK-AIS-PM
|
SYNC-FREQ
|
FE-IDLE
|
ODUK-BDI-PM
|
TIM for OC-N and Release 4.1 DWDM
|
FE-LOCKOUTOFPR-SPAN
|
ODUK-LCK-PM
|
UNC-WORD
|
FE-LOF
|
ODUK-OCI-PM
|
WKSWPR
|
FE-LOS
|
ODUK-SD-PM
|
WTR
|
2.2 Alarms and Conditions Indexed By Alphabetical Entry
Table 2-5 lists alarms and conditions by the name displayed on the CTC Alarms window or Conditions window.
Table 2-5 Alphabetical Alarm Index
AIS
|
FE-IDLE
|
NO-CONFIG
|
AIS-L
|
FE-LOCKOUTOFPR-SPAN
|
NOT-AUTHENTICATED
|
AIS-P
|
FE-LOF
|
ODUK-AIS-PM
|
AIS-V
|
FE-LOS
|
ODUK-BDI-PM
|
ALS
|
FE-MANWKSWPR-RING
|
ODUK-LCK-PM
|
AMPLI-INIT
|
FE-MANWKSWPR-SPAN
|
ODUK-OCI-PM
|
APC-DISABLED
|
FEPRLF
|
ODUK-SD-PM
|
APC-FAIL
|
FORCED-REQ
|
ODUK-SF-PM
|
APSB
|
FORCED-REQ-RING
|
ODUK-TIM-PM
|
APSCDFLTK
|
FORCED-REQ-SPAN
|
OPTNTWMIS
|
APSC-IMP
|
FRCDSWTOINT
|
OTUK-AIS
|
APSCINCON
|
FRCDSWTOPRI
|
OTUK-BDI
|
APSCM
|
FRCDSWTOSEC
|
OTUK-LOF
|
APSCNMIS
|
FRCDSWTOTHIRD
|
OTUK-SD
|
APSMM
|
FRNGSYNC
|
OTUK-SF
|
AS-CMD
|
FSTSYNC
|
OTUK-TIM
|
AS-MT
|
FULLPASSTHR-BI
|
PDI-P
|
AUD-LOG-LOSS
|
GCC-EOC
|
PEER-NORESPONSE
|
AUD-LOG-LOW
|
HI-LASERBIAS
|
PLM-P
|
AUTOLSROFF
|
HI-LASERTEMP
|
PLM-V
|
AUTORESET
|
HI-RXPOWER
|
PORT-CODE-MISM
|
AUTOSW-AIS
|
HI-RXTEMP
|
PORT-COMM-FAIL
|
AUTOSW-LOP (STSMON)
|
HITEMP
|
PORT-MISMATCH
|
AUTOSW-LOP (VTMON)
|
HI-TXPOWER
|
PORT-MISSING
|
AUTOSW-PDI
|
HLDOVRSYNC
|
PRC-DUPID
|
AUTOSW-SDBER
|
IMPROPRMVL
|
PROTNA
|
AUTOSW-SFBER
|
INC-ISD
|
PTIM
|
AUTOSW-UNEQ (STSMON)
|
INHSWPR
|
PWR-A
|
AUTOSW-UNEQ (VTMON)
|
INHSWWKG
|
PWR-B
|
BAT-A-HGH-VLT
|
INTRUSION-PSWD
|
PWR-REDUN
|
BAT-A-LOW-VLT
|
INVMACADR
|
RAI
|
BAT-B-HGH-VLT
|
IOSCFGCOPY
|
RCVR-MISS
|
BAT-B-LOW-VLT
|
KB-PASSTHR
|
RFI
|
BKUPMEMP
|
KBYTE-APS-CHANNEL-FAILURE
|
RFI-L
|
BLSROSYNC
|
LAN-POL-REV
|
RFI-P
|
CARLOSS (DWDM Client)
|
LASEREOL
|
RFI-V
|
CARLOSS (DWDM Trunk)
|
LKOUTPR-S
|
RING-ID-MIS
|
CARLOSS (EQPT)
|
LMP-HELLODOWN
|
RING-MISMATCH
|
CARLOSS (E-Series Ethernet)
|
LMP-NDFAIL
|
RING-SW-EAST
|
CARLOSS (G-Series Ethernet)
|
LOC
|
RING-SW-WEST
|
CARLOSS (ML-Series Ethernet)
|
LOCKOUT-REQ
|
RSVP-HELLODOWN
|
CKTDOWN
|
LOCKOUT-REQ-RING
|
RUNCFG-SAVENEED
|
CLDRESTART
|
LOF (BITS)
|
SD (DS-1, DS-3)
|
COMIOXC
|
LOF (DS-1)
|
SD (DWDM Client, DWDM Trunk)
|
COMM-FAIL
|
LOF (DS-3)
|
SD-L
|
CONTBUS-A-18
|
LOF (DWDM Client)
|
SD-P
|
CONTBUS-B-18
|
LOF (DWDM Trunk)
|
SF (DS-1, DS-3)
|
CONTBUS-IO-A
|
LOF (EC1-12)
|
SF (DWDM Client, Trunk)
|
CONTBUS-IO-B
|
LOF (OC-N)
|
SF-L
|
CTNEQPT-PBPROT
|
LO-LASERBIAS
|
SF-P
|
CTNEQPT-PBWORK
|
LO-LASERTEMP
|
SFTWDOWN
|
DATAFLT
|
LOM
|
SNTP-HOST
|
DBOSYNC
|
LOP-P
|
SPAN-SW-EAST
|
DS3-MISM
|
LOP-V
|
SPAN-SW-WEST
|
DSP-COMM-FAIL
|
LO-RXPOWER
|
SQUELCH
|
DSP-FAIL
|
LO-RXTEMP
|
SQUELCHED
|
EHIBATVG-A
|
LOS (BITS)
|
SSM-DUS
|
EHIBATVG-B
|
LOS (DS-1)
|
SSM-FAIL
|
ELWBATVG-A
|
LOS (DS-3)
|
SSM-LNC
|
ELWBATVG-B
|
LOS (DWDM Client or Trunk)
|
SSM-OFF
|
EOC
|
LOS (EC1-12)
|
SSM-PRC
|
EQPT
|
LOS (FUDC)
|
SSM-PRS
|
EQPT-MISS
|
LOS (OC-N)
|
SSM-RES
|
ERFI-P-CONN
|
LOS (OTN)
|
SSM-SMC
|
ERFI-P-PAYLD
|
LO-TXPOWER
|
SSM-ST2
|
ERFI-P-SRVR
|
LPBKCRS
|
SSM-ST3
|
ERROR-CONFIG
|
LPBKDS1FEAC
|
SSM-ST3E
|
E-W-MISMATCH
|
LPBKDS1FEAC-CMD
|
SSM-ST4
|
EXCCOL
|
LPBKDS3FEAC
|
SSM-STU
|
EXERCISE-RING-FAIL
|
LPBKDS3FEAC-CMD
|
SSM-TNC
|
EXERCISE-RING-REQ
|
LPBKFACILITY (DS-1 or DS-3)
|
SWMTXMOD
|
EXERCISE-SPAN-FAIL
|
LPBKFACILITY (DWDM Client, DWDM Trunk)
|
SWTOPRI
|
EXERCISE-SPAN-REQ
|
LPBKFACILITY (EC1-12)
|
SWTOSEC
|
EXT
|
LPBKFACILITY (G-Series Ethernet)
|
SWTOTHIRD
|
EXTRA-TRAF-PREEMPT
|
LPBKFACILITY (OC-N)
|
SYNC-FREQ
|
FAILTOSW
|
LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
SYNCPRI
|
FAILTOSW-PATH
|
LPBKTERMINAL (DWDM Client, DWDM Trunk)
|
SYNCSEC
|
FAILTOSWR
|
LPBKTERMINAL (G-Series Ethernet)
|
SYNCTHIRD
|
FAILTOSWS
|
MAN-REQ
|
SYSBOOT
|
FAN
|
MANRESET
|
TIM
|
FANDEGRADE
|
MANSWTOINT
|
TIM-MON
|
FE-AIS
|
MANSWTOPRI
|
TIM-P
|
FEC-MISM
|
MANSWTOSEC
|
TPTFAIL (G-Series Ethernet)
|
FE-DS1-MULTLOS
|
MANSWTOTHIRD
|
TPTFAIL (ML-Series Ethernet)
|
FE-DS1-NSA
|
MANUAL-REQ-RING
|
TRMT
|
FE-DS1-SA
|
MANUAL-REQ-SPAN
|
TRMT-MISS
|
FE-DS1-SNGLLOS
|
MEA (AIP)
|
TUNDERRUN
|
FE-DS3-NSA
|
MEA (BPLANE)
|
UNC-WORD
|
FE-DS3-SA
|
MEA (EQPT)
|
UNEQ-P
|
FE-EQPT-NSA
|
MEA (FAN)
|
UNEQ-V
|
FE-EXERCISING-RING
|
MEM-GONE
|
WKSWPR
|
FE-EXERCISING-SPAN
|
MEM-LOW
|
WTR
|
FE-FRCDWKSWPR-RING
|
MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
WVL-MISMATCH
|
FE-FRCDWKSWPR-SPAN
|
|
|
2.3 Logical Object Type Definitions
ONS 15454 alarms are grouped according to their logical object types in alarm profile listings (for example: ML1000: CARLOSS). Each alarm entry in this chapter lists its type. These are defined in Table 2-6.
Table 2-6 Alarm Type/Object Definition
AICI-AEP
|
Alarm interface controller-International and/or Alarm expansion panel
|
|
|
Alarm interface controller-international
|
AIP
|
Auxiliary interface protection module
|
BITS
|
Building integration timing supply (BITS) incoming references (BITS-1, BITS-2)
|
BPLANE
|
The backplane
|
CLIENT
|
The low-speed port, such as a TXP or MXP, where the optical signal is dropped
|
DS1
|
A DS-1 line on a DS-1 card
|
DS3
|
A DS-3 line on a DS-3 card
|
E100T
|
An Ethernet line on an E100T-12 card or E100T-G card
|
E1000F
|
An Ethernet line on an E1000-2 card or E1000-2-G card
|
EC1-12
|
An EC1 line on an EC1-12 card
|
ENV ALRM
|
An environmental alarm port
|
EQPT
|
A card in any of the 8 card slots. The EQPT object is used for alarms that refer to the card itself and all other objects on the card including ports, lines, STS and VT
|
EXT-SREF
|
BITS outgoing references (SYNC-BITS1, SYNC-BITS2)
|
FAN
|
Fan-tray assembly
|
FUDC
|
SONET byte user data channel
|
G1000
|
High Density Gigabit Ethernet; applies to G1000-4 cards.
|
ML100T
|
An Ethernet line on an ML100T-12 card
|
ML1000
|
An Ethernet line on an ML1000-2 card
|
MSUDC
|
SONET Multiplex Section User Data Channel
|
NE
|
The entire network element
|
NE-SREF
|
Represents the timing status of the NE
|
OCN
|
An OC-N line on an OC-N card
|
STSMON
|
STS alarm detection at the monitor point (upstream from the cross-connect)
|
STSRNG
|
STS ring
|
STSTRM
|
STS alarm detection at termination (downstream from the cross-connect)
|
TRUNK
|
The optical or DWDM card carrying the high-speed signal
|
UCP-CKT
|
UCP circuit
|
UCP-IPCC
|
Unified control plane (UCP) communication channel
|
VTMON
|
VT1 alarm detection at the monitor point (upstream from the cross-connect)
|
VTTERM
|
VT1 alarm detection at termination (downstream from the cross-connect)
|
2.4 Alarm Index by Logical Object Type
Table 2-7 gives the name and page number of every alarm in the chapter, organized by logical object type.
Note This table includes logical objects and alarms configured for a default node. The alarm profile list contain more alarms or conditions that may be used to customize the alarm profile, or some items that are present but not configurable by the user. Consult Cisco for more information about these alarms and conditions.
Note The items in this table appear in the same order as they do in the alarm profile list. The list contains only Release 4.1 alarms.
Table 2-7 Alarm Index by Alarm Type
AICI-AEP: EQPT
|
AICI-AEP: MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
AICI-AIE1 : EQPT
|
AICI-AIE1: MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
AIP: INVMACADR
|
AIP: MEA (AIP)
|
AIP: MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
BITS: AIS
|
BITS: LOF (BITS)
|
BITS: LOS (BITS)
|
BITS: SSM-DUS
|
BITS: SSM-FAIL
|
BITS: SSM-OFF
|
BITS: SSM-PRS
|
BITS: SSM-RES
|
BITS: SSM-SMC
|
BITS: SSM-ST2
|
BITS: SSM-ST3
|
BITS: SSM-ST3E
|
BITS: SSM-ST4
|
BITS: SSM-STU
|
BITS: SSM-TNC
|
BPLANE: AS-CMD
|
BPLANE: MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
CLIENT: AIS
|
CLIENT: AS-CMD
|
CLIENT: AS-MT
|
CLIENT: AUTOLSROFF
|
CLIENT: CARLOSS (DWDM Client)
|
CLIENT: EOC
|
CLIENT: FAILTOSW
|
CLIENT: FORCED-REQ-SPAN
|
CLIENT: HI-LASERBIAS
|
CLIENT: HI-LASERTEMP
|
CLIENT: HI-RXPOWER
|
CLIENT: HI-TXPOWER
|
CLIENT: LO-LASERBIAS
|
CLIENT: LO-LASERTEMP
|
CLIENT: LO-RXPOWER
|
CLIENT: LO-TXPOWER
|
CLIENT: LOCKOUT-REQ
|
CLIENT: LOF (DWDM Client)
|
CLIENT: LOS (DWDM Client or Trunk)
|
CLIENT: LPBKFACILITY (DWDM Client, DWDM Trunk)
|
CLIENT: LPBKTERMINAL (DWDM Client, DWDM Trunk)
|
CLIENT: MANUAL-REQ-SPAN
|
CLIENT: PORT-CODE-MISM
|
CLIENT: PORT-COMM-FAIL
|
CLIENT: PORT-MISMATCH
|
CLIENT: PORT-MISSING
|
CLIENT: RFI
|
CLIENT: SD (DWDM Client, DWDM Trunk)
|
CLIENT: SF (DWDM Client, Trunk)
|
CLIENT: SQUELCHED
|
CLIENT: SSM-DUS
|
CLIENT: SSM-FAIL
|
CLIENT: SSM-LNC
|
CLIENT: SSM-OFF
|
CLIENT: SSM-PRC
|
CLIENT: SSM-PRS
|
CLIENT: SSM-RES
|
CLIENT: SSM-SDH-TN (not used)
|
CLIENT: SSM-SETS (not used)
|
CLIENT: SSM-SMC
|
CLIENT: SSM-ST2
|
CLIENT: SSM-ST3
|
CLIENT: SSM-ST3E
|
CLIENT: SSM-ST4
|
CLIENT: SSM-STU
|
CLIENT: SSM-TNC
|
CLIENT: TIM
|
CLIENT: WKSWPR
|
CLIENT: WTR
|
DS1: AIS
|
DS1: AS-CMD
|
DS1: AS-MT
|
DS1: LOF (DS-1)
|
DS1: LOS (DS-1)
|
DS1: LPBKDS1FEAC
|
DS1: LPBKDS1FEAC-CMD
|
DS1: LPBKFACILITY (DS-1 or DS-3)
|
DS1: LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
DS1: RAI
|
DS1: RCVR-MISS
|
DS1: SD (DS-1, DS-3)
|
DS1: SF (DS-1, DS-3)
|
DS1: TRMT
|
DS1: TRMT-MISS
|
DS3: AIS
|
DS3: AS-CMD
|
DS3: AS-MT
|
DS3: DS3-MISM
|
DS3: FE-AIS
|
DS3: FE-DS1-MULTLOS
|
DS3: FE-DS1-NSA
|
DS3: FE-DS1-SA
|
DS3: FE-DS1-SNGLLOS
|
DS3: FE-DS3-NSA
|
DS3: FE-DS3-SA
|
DS3: FE-EQPT-NSA
|
DS3: FE-IDLE
|
DS3: FE-LOF
|
DS3: FE-LOS
|
DS3: INC-ISD
|
DS3: LOF (DS-3)
|
DS3: LOS (DS-3)
|
DS3: LPBKDS1FEAC
|
DS3: LPBKDS3FEAC
|
DS3: LPBKDS3FEAC-CMD
|
DS3: LPBKFACILITY (DS-1 or DS-3)
|
DS3: LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
DS3: RAI
|
DS3: SD (DS-1, DS-3)
|
DS3: SF (DS-1, DS-3)
|
E100T: AS-CMD
|
E100T: CARLOSS (E-Series Ethernet)
|
E1000F: AS-CMD
|
E1000F: CARLOSS (E-Series Ethernet)
|
EC1-12: AIS-L
|
EC1-12: AS-CMD
|
EC1-12: AS-MT
|
EC1-12: LOF (EC1-12)
|
EC1-12: LOS (EC1-12)
|
EC1-12: LPBKFACILITY (EC1-12)
|
EC1-12: LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
EC1-12: RFI-L
|
EC1-12: SD-L
|
EC1-12: SF-L
|
ENVALRM: EXT
|
EQPT: AS-CMD
|
EQPT: AUTORESET
|
EQPT: BKUPMEMP
|
EQPT: CARLOSS (EQPT)
|
EQPT: CLDRESTART
|
EQPT: COMIOXC
|
EQPT: CONTBUS-A-18
|
EQPT: CONTBUS-B-18
|
EQPT: CONTBUS-IO-A
|
EQPT: CONTBUS-IO-B
|
EQPT: CTNEQPT-PBPROT
|
EQPT: CTNEQPT-PBWORK
|
EQPT: EQPT
|
EQPT: ERROR-CONFIG
|
EQPT: EXCCOL
|
EQPT: FAILTOSW
|
EQPT: FORCED-REQ
|
EQPT: HITEMP
|
EQPT: IMPROPRMVL
|
EQPT: INHSWPR
|
EQPT: INHSWWKG
|
EQPT: IOSCFGCOPY
|
EQPT: LOCKOUT-REQ
|
EQPT: MAN-REQ
|
EQPT: MANRESET
|
EQPT: MEA (EQPT)
|
EQPT: MEM-GONE
|
EQPT: MEM-LOW
|
EQPT: NO-CONFIG
|
EQPT: PEER-NORESPONSE
|
EQPT: PROTNA
|
EQPT: PWR-REDUN
|
EQPT: RUNCFG-SAVENEED
|
EQPT: SFTWDOWN
|
EQPT: SWMTXMOD
|
EQPT: WKSWPR
|
EQPT: WTR
|
EXT-SREF: FRCDSWTOPRI
|
EXT-SREF: FRCDSWTOSEC
|
EXT-SREF: FRCDSWTOTHIRD
|
EXT-SREF: MANSWTOPRI
|
EXT-SREF: MANSWTOSEC
|
EXT-SREF: MANSWTOTHIRD
|
EXT-SREF: SWTOPRI
|
EXT-SREF: SWTOSEC
|
EXT-SREF: SWTOTHIRD
|
EXT-SREF: SYNCPRI
|
EXT-SREF: SYNCSEC
|
EXT-SREF: SYNCTHIRD
|
FAN: EQPT-MISS
|
FAN: FAN
|
FAN: MEA (FAN)
|
FAN: MFGMEM (AEP, AIP, BPLANE, FAN and Fan-Tray Assembly)
|
FUDC: AIS
|
FUDC: LOS (FUDC)
|
G1000: AS-CMD
|
G1000: AS-MT
|
G1000: CARLOSS (G-Series Ethernet)
|
G1000: LPBKFACILITY (G-Series Ethernet)
|
G1000: LPBKTERMINAL (G-Series Ethernet)
|
G1000: TPTFAIL (G-Series Ethernet)
|
ML1000: AS-CMD
|
ML1000: CARLOSS (ML-Series Ethernet)
|
ML1000: TPTFAIL (ML-Series Ethernet)
|
ML100T: AS-CMD
|
ML100T: CARLOSS (ML-Series Ethernet)
|
ML100T: TPTFAIL (ML-Series Ethernet)
|
MSUDC: AIS
|
MSUDC: LOS (MSUDC)
|
NE-SREF: FRCDSWTOINT
|
NE-SREF: FRCDSWTOPRI
|
NE-SREF: FRCDSWTOSEC
|
NE-SREF: FRCDSWTOTHIRD
|
NE-SREF: FRNGSYNC
|
NE-SREF: FSTSYNC
|
NE-SREF: HLDOVRSYNC
|
NE-SREF: MANSWTOINT
|
NE-SREF: MANSWTOPRI
|
NE-SREF: MANSWTOSEC
|
NE-SREF: MANSWTOTHIRD
|
NE-SREF: SSM-PRS
|
NE-SREF: SSM-RES
|
NE-SREF: SSM-SMC
|
NE-SREF: SSM-ST2
|
NE-SREF: SSM-ST3
|
NE-SREF: SSM-ST3E
|
NE-SREF: SSM-ST4
|
NE-SREF: SSM-STU
|
NE-SREF: SSM-TNC
|
NE-SREF: SWTOPRI
|
NE-SREF: SWTOSEC
|
NE-SREF: SWTOTHIRD
|
NE-SREF: SYNCPRI
|
NE-SREF: SYNCSEC
|
NE-SREF: SYNCTHIRD
|
NE: AS-CMD
|
NE: AUD-LOG-LOSS
|
NE: AUD-LOG-LOW
|
NE: BAT-A-HGH-VLT
|
NE: BAT-A-LOW-VLT
|
NE: BAT-B-HGH-VLT
|
NE: BAT-B-LOW-VLT
|
NE: DATAFLT
|
NE: DBOSYNC
|
NE: EHIBATVG-A
|
NE: EHIBATVG-B
|
NE: ELWBATVG-A
|
NE: ELWBATVG-B
|
NE: HITEMP
|
NE: I-HITEMP (not used for ONS 15454 Release 4.1)
|
NE: INTRUSION-PSWD
|
NE: LAN-POL-REV
|
NE: PRC-DUPID
|
NE: PWR-A
|
NE: PWR-B
|
NE: SNTP-HOST
|
NE: SYSBOOT
|
OCN: AIS-L
|
OCN: APSB
|
OCN: APSC-IMP
|
OCN: APSCDFLTK
|
OCN: APSCINCON
|
OCN: APSCM
|
OCN: APSCNMIS
|
OCN: APSMM
|
OCN: AS-CMD
|
OCN: AS-MT
|
OCN: AUTOLSROFF
|
OCN: BLSROSYNC
|
OCN: E-W-MISMATCH
|
OCN: EOC
|
OCN: EXERCISE-RING-FAIL
|
OCN: EXERCISE-RING-REQ
|
OCN: EXERCISE-SPAN-FAIL
|
OCN: EXERCISE-SPAN-REQ
|
OCN: EXTRA-TRAF-PREEMPT
|
OCN: FAILTOSW
|
OCN: FAILTOSWR
|
OCN: FAILTOSWS
|
OCN: FE-EXERCISING-RING
|
OCN: FE-EXERCISING-SPAN
|
OCN: FE-FRCDWKSWPR-RING
|
OCN: FE-FRCDWKSWPR-SPAN
|
OCN: FE-LOCKOUTOFPR-SPAN
|
OCN: FE-MANWKSWPR-RING
|
OCN: FE-MANWKSWPR-SPAN
|
OCN: FEPRLF
|
OCN: FORCED-REQ-RING
|
OCN: FORCED-REQ-SPAN
|
OCN: KBYTE-APS-CHANNEL-FAILURE
|
OCN: LASEREOL
|
OCN: LKOUTPR-S
|
OCN: LOCKOUT-REQ
|
OCN: LOF (OC-N)
|
OCN: LOS (OC-N)
|
OCN: LPBKFACILITY (OC-N)
|
OCN: LPBKTERMINAL (DS-1, DS-3, EC-1-12, OC-N)
|
OCN: MANUAL-REQ-RING
|
OCN: MANUAL-REQ-SPAN
|
OCN: PRC-DUPID
|
OCN: RFI-L
|
OCN: RING-MISMATCH
|
OCN: RING-SW-EAST
|
OCN: RING-SW-WEST
|
OCN: SD-L
|
OCN: SF-L
|
OCN: SPAN-SW-EAST
|
OCN: SPAN-SW-WEST
|
OCN: SQUELCH
|
OCN: SSM-DUS
|
OCN: SSM-FAIL
|
OCN: SSM-OFF
|
OCN: SSM-PRS
|
OCN: SSM-RES
|
OCN: SSM-SMC
|
OCN: SSM-ST2
|
OCN: SSM-ST3
|
OCN: SSM-ST3E
|
OCN: SSM-ST4
|
OCN: SSM-STU
|
OCN: SSM-TNC
|
OCN: SYNC-FREQ
|
OCN: TIM
|
OCN: WKSWPR
|
OCN: WTR
|
STSMON: AIS-P
|
STSMON: AUTOSW-AIS
|
STSMON: AUTOSW-LOP (STSMON)
|
STSMON: AUTOSW-PDI
|
STSMON: AUTOSW-SDBER
|
STSMON: AUTOSW-SFBER
|
STSMON: AUTOSW-UNEQ (STSMON)
|
STSMON: ERFI-P-CONN
|
STSMON: ERFI-P-PAYLD
|
STSMON: ERFI-P-SRVR
|
STSMON: FAILTOSW-PATH
|
STSMON: FORCED-REQ
|
STSMON: LOCKOUT-REQ
|
STSMON: LOP-P
|
STSMON: LPBKCRS
|
STSMON: MAN-REQ
|
STSMON: PDI-P
|
STSMON: PLM-P
|
STSMON: RFI-P
|
STSMON: SD-P
|
STSMON: SF-P
|
STSMON: TIM-P
|
STSMON: UNEQ-P
|
STSMON: WKSWPR
|
STSMON: WTR
|
STSRNG: BLSROSYNC
|
STSRNG: FULLPASSTHR-BI
|
STSRNG: KB-PASSTHR
|
STSRNG: PRC-DUPID
|
STSRNG: RING-MISMATCH
|
STSTRM: AIS-P
|
STSTRM: AU-LOF (not used for ONS 15454 Release 4.1)
|
STSTRM: ERFI-P-CONN
|
STSTRM: ERFI-P-PAYLD
|
STSTRM: ERFI-P-SRVR
|
STSTRM: LOP-P
|
STSTRM: PDI-P
|
STSTRM: PLM-P
|
STSTRM: RFI-P
|
STSTRM: SD-P
|
STSTRM: SF-P
|
STSTRM: TIM-P
|
STSTRM: UNEQ-P
|
TRUNK: AIS
|
TRUNK: AS-CMD
|
TRUNK: AS-MT
|
TRUNK: AUTOLSROFF
|
TRUNK: CARLOSS (DWDM Trunk)
|
TRUNK: DSP-COMM-FAIL
|
TRUNK: DSP-FAIL
|
TRUNK: EOC
|
TRUNK: FEC-MISM
|
TRUNK: GCC-EOC
|
TRUNK: HI-LASERBIAS
|
TRUNK: HI-LASERTEMP
|
TRUNK: HI-RXPOWER
|
TRUNK: HI-RXTEMP
|
TRUNK: HI-TXPOWER
|
TRUNK: LO-LASERBIAS
|
TRUNK: LO-LASERTEMP
|
TRUNK: LO-RXPOWER
|
TRUNK: LO-RXTEMP
|
TRUNK: LOS (OTN)
|
TRUNK: LO-TXPOWER
|
TRUNK: LOC
|
TRUNK: LOF (DWDM Trunk)
|
TRUNK: LOM
|
TRUNK: LOS (DWDM Client or Trunk)
|
TRUNK: LPBKFACILITY (DWDM Client, DWDM Trunk)
|
TRUNK: LPBKTERMINAL (DWDM Client, DWDM Trunk)
|
TRUNK: ODUK-AIS-PM
|
TRUNK: ODUK-BDI-PM
|
TRUNK: ODUK-LCK-PM
|
TRUNK: ODUK-OCI-PM
|
TRUNK: ODUK-SD-PM
|
TRUNK: ODUK-SF-PM
|
TRUNK: ODUK-TIM-PM
|
TRUNK: OTUK-AIS
|
TRUNK: OTUK-BDI
|
TRUNK: OTUK-IAE (not used for ONS 15454 Release 4.1)
|
TRUNK: OTUK-LOF
|
TRUNK: OTUK-SD
|
TRUNK: OTUK-SF
|
TRUNK: OTUK-TIM
|
TRUNK: RFI
|
TRUNK: SD (DWDM Client, DWDM Trunk)
|
TRUNK: SF (DWDM Client, Trunk)
|
TRUNK: SSM-DUS
|
TRUNK: SSM-FAIL
|
TRUNK: SSM-LNC
|
TRUNK: SSM-OFF
|
TRUNK: SSM-PRC
|
TRUNK: SSM-PRS
|
TRUNK: SSM-RES
|
TRUNK: SSM-SDH-TN (not used for ONS 15454 Release 4.1)
|
TRUNK: SSM-SETS (not used for ONS 15454 Release 4.1)
|
TRUNK: SSM-SMC
|
TRUNK: SSM-ST2
|
TRUNK: SSM-ST3
|
TRUNK: SSM-ST3E
|
TRUNK: SSM-ST4
|
TRUNK: SSM-STU
|
TRUNK: SSM-TNC
|
TRUNK: TIM
|
TRUNK: UNC-WORD
|
TRUNK: WTR
|
TRUNK: WVL-MISMATCH
|
UCP-CKT: CKTDOWN
|
UCP-IPCC: LMP-HELLODOWN
|
UCP-IPCC: LMP-NDFAIL
|
UCP-NBR: RSVP-HELLODOWN
|
VT-MON: AIS-V
|
VT-MON: AUTOSW-AIS
|
VT-MON: AUTOSW-LOP (VTMON)
|
VT-MON: AUTOSW-UNEQ (VTMON)
|
VT-MON: FAILTOSW-PATH
|
VT-MON: FORCED-REQ
|
VT-MON: LOCKOUT-REQ
|
VT-MON: LOP-V
|
VT-MON: MAN-REQ
|
VT-MON: UNEQ-V
|
VT-MON: WKSWPR
|
VT-MON: WTR
|
VT-TERM: AIS-V
|
VT-TERM: LOP-V
|
VT-TERM: PLM-V
|
VT-TERM: RFI-V
|
VT-TERM: SD-P
|
VT-TERM: SF-P
|
VT-TERM: UNEQ-V
|
2.5 Trouble Notifications
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The ONS 15454 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 an LOS, while Not-Alarmed (NA) notifications do not necessarily need immediate troubleshooting.
Telcordia 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-183 is characterized by default as an SA failure. TRMT-MISS occurs when a cable connector is removed from an active DS-1 card port. The default severity assumes that service has been interrupted or moved. If the DS-1 card is in a protection group and the traffic is on the protect card rather than the working card, or if the port with the TRMT-MISS alarm has no circuits provisioned, TRMT-MISS would be raised as NSA because traffic was not interrupted or moved.
2.5.1 Conditions
The term "Condition" refers to any problem detected on an ONS 15454 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 or using TL1's set of RTRV-COND commands. You can see the actual reporting messages for alarms and NAs in the CTC History tab.
For a comprehensive list of all conditions, refer to the Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide.
2.5.2 Severities
The ONS 15454 uses Telcordia standard severities: Critical (CR), Major (MJ), and Minor (MN). Non-Service Affecting (NSA) alarms always have a Minor (MN) severity. Service-Affecting (SA) alarms may be Critical (CR), Major (MJ), or Minor (MN). Critical alarms generally indicate severe, service-affecting trouble that needs immediate correction. A Major (MJ) alarm is a serious alarm, but the trouble has less impact on the network. For SONET signal alarms, traffic loss of traffic on more than five DS-1 circuits is Critical. Loss of traffic on one to five DS-1 circuits is Major (MJ). Loss of traffic on an STS-1, which can hold 28 DS-1 circuits, would be a Critical (CR), Service-Affecting (SA) alarm.
An example of a Non-Service Affecting (NSA) alarm is the "FSTSYNC" condition on page 2-92 (Fast Start Synchronization Mode), which indicates the ONS 15454 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.
Telcordia standard severities are the default settings for the ONS 15454. A user may customize ONS 15454 alarm severities with the alarm profiles feature. For alarm profile procedures, refer to the Cisco ONS 15454 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, in accordance with Telcordia rules.
2.6 Safety Summary
This section covers safety considerations designed to ensure safe operation of the ONS 15454. Personnel should not perform any procedures in this chapter unless they understand all safety precautions, practices, and warnings for the system equipment. Some troubleshooting procedures require installation or removal of cards, in these instances users should pay close attention to the following caution and warnings:
Caution Hazardous voltage or energy might be present on the backplane when the system is operating. Use caution when removing or installing cards.
Some troubleshooting procedures require installation or removal of OC-192 cards, in these instances users should pay close attention to the following warnings:
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Warning Class 1 laser product.
Warning Class 1M laser radiation when open. Do not view directly with optical instruments
2.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 are done checking for alarms, click the alarm filter icon again to turn filtering back on.
Note When checking alarms, make sure that alarm suppression is not enabled on the card or port. For more information about alarm suppression, see the Cisco ONS 15454 Procedure Guide.
Note In this section, alarm logical objects are only given when they appear in the Release 4.1 alarm profile list.
2.7.1 AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: BITS, CLIENT, DS1, DS3, FUDC, MSUDC, TRUNK
The Alarm Indication Signal (AIS) condition indicates that this node is detecting AIS in the incoming signal SONET overhead.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Note DS-3 and EC-1 terminal (inward) loopbacks do not transmit an AIS in the direction away from the loopback. Instead of AIS, a continuance of the signal transmitted into the loopback is provided.
Clear the AIS Condition
Step 1 Verify whether there are alarms on the upstream nodes and equipment, especially the "LOS (OC-N)" alarm on page 2-123, or OOS ports.
Step 2 Clear the upstream alarms using the applicable procedure(s) in this chapter.
Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.2 AIS-L
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: EC1-12, OCN
The AIS Line condition indicates that this node is detecting Line-level AIS in the incoming signal.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-L Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.3 AIS-P
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
The AIS Path condition means that this node is detecting AIS in the incoming path.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AIS-P Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.4 AIS-V
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: VTMON, VTTERM
The AIS Virtual Tributary (VT) condition means that this node is detecting AIS in the incoming VT-level path.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
See the "AIS-V on DS3XM-6 Unused VT Circuits" section on page 1-76 for more information.
Clear the AIS-V Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.5 ALS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Automatic Laser Shutdown condition occurs when an amplifier (OPT-BST or OPT-PRE) is switched on. The turn-on process lasts approximately nine seconds, and the condition clears after approximately 10 seconds.
Note ALS is an informational condition. It does not require troubleshooting.
2.7.6 AMPLI-INIT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Amplifier Initialized condition occurs when an amplifier card (OPT-BST or OPT-PRE) is not able to calculate gain. This condition typically accompanies the "APC-DISABLED" alarm on page 2-26 alarm.
Clear the AMPLI-INIT Condition
Step 1 Complete the "Delete a Circuit" procedure on the most recently created circuit.
Step 2 Recreate this circuit using the procedures in the Cisco ONS 15454 Procedure Guide.
Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.7 APC-DISABLED
•Major (MJ), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Automatic Power Control (APC) Disabled occurs when the information related to the number of channels is not reliable. The alarm can occur when the any of the following alarms also occur: the "EQPT" alarm on page 2-65, the "IMPROPRMVL" alarm on page 2-98, and the "MEA (EQPT)" alarm on page 2-135. If the alarm occurs with the creation of the first circuit, delete and then recreate it.
Clear the APC-DISABLED Alarm
Step 1 Complete the appropriate procedure to clear the primary alarm:
•Clear the EQPT Alarm
•Clear the IMPROPRMVL Alarm
•Clear the MEA (EQPT) 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.8 APC-FAIL
•Major (MJ), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The APC Failure alarm occurs when APC has not been able to create a setpoint on a node because it has consumed all allocated power margins. These power margins (from 0 dB to 3 dB) are allocated when the network is installed. Margins can be consumed due to fiber aging or the insertion of unexpected extra loss in the span after a fiber cut.
Clear the APC-FAIL Alarm
Step 1 Isolate the cause of increased margin use:
•If it is due to fiber aging, replace the indicated fiber. (You can test the integrity of the fiber using optical testing equipment.)
•If it is due to a fiber cut, resolve this issue to resolve this alarm.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.9 APSB
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The Automatic Protection Switching (APS) Channel Byte Failure alarm occurs when line terminating equipment detects protection switching byte failure in the incoming APS signal. The failure occurs when an inconsistent APS byte or invalid code is detected. Some older, non-Cisco SONET nodes send invalid APS codes if they are configured in a 1+1 protection scheme with newer SONET nodes, such as the ONS 15454. These invalid codes causes an APSB on an ONS node.
Clear the APSB Alarm
Step 1 Use an optical test set to examine the incoming SONET overhead to confirm inconsistent or invalid K bytes.
For specific procedures to use the test set equipment, consult the manufacturer. If corrupted K bytes are confirmed and the upstream equipment is functioning properly, the upstream equipment might not interoperate effectively with the ONS 15454.
Step 2 If the alarm does not clear and the overhead shows inconsistent or invalid K bytes, you might need to replace the upstream cards for protection switching to operate properly.
Step 3 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.10 APSCDFLTK
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
The APS Default K Byte Received alarm occurs when a bidirectional line switched ring (BLSR) is not properly configured, for example, when a four-node BLSR has one node configured as path protection. A node in a path protection or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2 byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the "BLSROSYNC" alarm on page 2-41.
Clear the APSCDFLTK Alarm
Step 1 Complete the "Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 Repeat Step 1 for all nodes in the ring.
Step 3 If two nodes have the same node ID number, complete the "Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Step 4 If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the "E-W-MISMATCH" alarm on page 2-69.) West port fibers must connect to east port fibers, and vice versa. The Cisco ONS 15454 Procedure Guide provides a procedure for fibering BLSRs.
Step 5 If the alarm does not clear and if the network is a four-fiber BLSR, make sure that each protect fiber is connected to another protect fiber and each working fiber is connected to another working fiber. The software does not report any alarm if a working fiber is incorrectly attached to a protection fiber.
Step 6 If the alarm does not clear, complete the "Verify Node Visibility for Other Nodes" procedure.
Step 7 If nodes are not visible, complete the "Verify or Create Node DCC Terminations" procedure to ensure that SONET DCC terminations exist on each node.
Step 8 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.11 APSC-IMP
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An Improper SONET APS Code alarm indicates invalid K bytes. The APSC-IMP alarm occurs on OC-N cards in a BLSR configuration. The receiving equipment monitors K bytes or K1 and K2 APS bytes for an indication to switch from the working card to the protect card or vice versa. K1/K2 bytes also contain bits that tell the receiving equipment whether the K byte is valid. APSCIMP occurs when these bits indicate a bad or invalid K byte. The alarm clears when the node receives valid K bytes.
Note This alarm can occur on a VT tunnel when it does not have VT circuits provisioned. It can also occur when the exercise command or a lock out is applied to a span. An externally switched span will not raise this alarm because traffic is pre-empted.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the APSC-IMP Alarm
Step 1 Use an optical test set to determine the validity of the K byte signal by examining the received signal.
For specific procedures to use the test set equipment, consult the manufacturer.
If the K byte is invalid, the problem is with upstream equipment and not in the reporting ONS 15454. Troubleshoot the upstream equipment using the procedures in this chapter, as applicable. If the upstream nodes are not ONS 15454s, consult the appropriate user documentation.
Step 2 If the K byte is valid, verify that each node has a ring ID that matches the other node ring IDs. Complete the "Identify a Ring ID or Node ID Number" procedure.
Step 3 Repeat Step 2 for all nodes in the ring.
Step 4 If a node has a ring ID number that does not match the other nodes, make the ring ID number of that node identical to the other nodes. Complete the "Change a Ring ID Number" procedure.
Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.12 APSCINCON
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An APS Inconsistent alarm means that an inconsistent APS byte is present. The SONET overhead contains K1/K2 APS bytes that notify receiving equipment, such as the ONS 15454, to switch the SONET signal from a working to a protect path. An inconsistent APS code occurs when three consecutive frames do not contain identical APS bytes. Inconsistent APS bytes give the receiving equipment conflicting commands about switching.
Clear the APSCINCON Alarm
Step 1 Look for other alarms, especially the "LOS (OC-N)" alarm on page 2-123, the "LOF (OC-N)" alarm on page 2-111, or the "AIS" alarm on page 2-23. Clearing these alarms clears the APSCINCON alarm.
Step 2 If an APSINCON alarm occurs with no other alarms, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.13 APSCM
•Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
The APS Channel Mismatch alarm occurs when the ONS 15454 expects a working channel but receives a protection channel. In many cases, the working and protection channels are crossed and the protect channel is active. If the fibers are crossed and the working line is active, the alarm does not occur. The APSCM alarm occurs only on the ONS 15454 when bidirectional protection is used on OC-N cards in a 1+1 configuration.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-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 fibers are correctly connected, 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 onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.14 APSCNMIS
•Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
The APS Node ID Mismatch alarm occurs when the source node ID contained in the SONET K2 byte of the incoming APS channel is not present in the ring map. The APSCNMIS alarm might occur and clear when a BLSR is being provisioned. If so, you can disregard the temporary occurrence. If the APSCNMIS remains, the alarm clears when a K byte with a valid source node ID is received.
Clear the APSCNMIS Alarm
Step 1 Complete the "Identify a Ring ID or Node ID Number" procedure to verify that each node has a unique node ID number.
Step 2 If the Node ID column contains any two nodes with the same node ID listed, record the repeated node ID.
Step 3 Click Close in the Ring Map dialog box.
Step 4 If two nodes have the same node ID number, complete the "Change a Node ID Number" procedure to change one node's ID number so that each node ID is unique.
Note If the node names shown in the network view do not correlate with the node IDs, log into each node and click the Provisioning > BLSR tabs. The BLSR window shows the node ID of the login node.
Note Applying and removing a lock out on a span causes the ONS 15454 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 a BLSR Span" procedure to lock out the span.
Step 6 Complete the "Clear a BLSR Span Lock Out" procedure to clear the lock out.
Step 7 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.15 APSMM
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: OCN
An APS Mode Mismatch failure alarm occurs when there is a mismatch of the protection switching schemes at the two ends of the span. If one node is provisioned for bidirectional switching, the node at the other end of the span must also be provisioned for bidirectional switching. If one end is provisioned for bidirectional and the other is provisioned for unidirectional, an APSMM alarm occurs in the ONS node that is provisioned for bidirectional. The APSMM alarm occurs in a 1+1 configuration.
Clear the APSMM Alarm
Step 1 For the reporting ONS 15454, display the node view and verify the protection scheme provisioning.
a. Click the Provisioning > Protection tabs.
b. Choose the 1+1 protection group configured for the OC-N cards.
The chosen protection group is the protection group optically connected (with DCC connectivity) to the far end.
Record whether the Bidirectional Switching check box is checked.
Step 2 Log into the far-end node and verify that the OC-N 1+1 protection group is provisioned.
Step 3 Verify that the Bidirectional Switching check box matches the checked or unchecked condition of the box recorded in Step 1. If not, change it to match.
Step 4 Click Apply.
Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.16 AS-CMD
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Portions of this procedure do not apply to DWDM
•Logical Objects: BPLANE, CLIENT, DS-1, DS3, E100T, E1000F, EC1-12, EQPT, G1000, ML100T, ML1000, NE, OCN, TRUNK
The Alarms Suppressed by User Command condition applies to the network element (SYSTEM object), backplane, a single card, or a port on a card. It occurs when alarms are suppressed for that object and its subordinate objects; that is, suppressing alarms on a card also suppresses alarms on its ports.
Clear the AS-CMD Condition
Step 1 For all nodes, in the node view, click the Conditions tab.
Step 2 Click Retrieve. If you have already retrieved conditions, look under the Object column and Eqpt Type column, note what entity the condition is reported against, such as a port, slot, or shelf.
If the condition is reported against a slot and card, alarms were either suppressed for the entire card or for one of the ports. Note the slot number and continue with Step 3.
If the condition is reported against the backplane, go to Step 7.
If the condition is reported against a "system," go to Step 8.
Step 3 If the AS-CMD condition is reported for a card in a Software R4.1 or earlier node, determine whether alarms are suppressed for a port and if so, raise the suppressed alarms:
a. Double-click the card to display the card view.
b. Click the Provisioning > Alarm Behavior tabs.
•If the Suppress Alarms column check box is checked for a port row, deselect it and click Apply.
•If the Suppress Alarms column check box is not checked for a port row, click View > Go to Previous View.
Step 4 In node view for a Release 4.1 or earlier node, if the AS-CMD condition is reported for a card and not an individual port, click the Provisioning > Alarm Behavior tabs.
Step 5 Locate the row for the reported card slot. (The slot number information was in the Object column in the Conditions window that you noted in Step 2.)
Step 6 Click the Suppress Alarms column check box to deselect the option for the card row.
Step 7 If the condition is reported for the backplane, the alarms are suppressed for cards such as the AIP that are not in the optical or electrical slots. To clear the alarm:
a. In node view, click the Provisioning > Alarm Behavior tabs.
b. In the Backplane row, deselect the Suppress Alarms column check box.
c. Click Apply.
Step 8 If the condition is reported for the shelf, cards and other equipment are affected. To clear the alarm:
a. In node view, click the Provisioning > Alarm Behavior tabs.
b. Click the Suppress Alarms check box located at the bottom of the window to deselect the option.
c. Click Apply.
Step 9 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.17 AS-MT
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Occurs only on Software R4.1 or earlier nodes
•Logical Objects: CLIENT, DS1, DS3, EC1-12, G1000, OCN, TRUNK
The Alarms Suppressed for Maintenance Command condition applies to OC-N and electrical (traffic) cards and occurs when a port is placed in the out-of-service maintenance (OOS-MT) state for loopback testing operations.
Clear the AS-MT Condition
Step 1 Complete the "Clear a Loopback" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.18 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% full and that the oldest entries are being replaced as new entries are generated. The log capacity is 640 entries.
Clear the AUD-LOG-LOSS Condition
Step 1 In the node view, click the Maintenance > Audit tabs.
Step 2 Click Retrieve.
Step 3 Click Archive.
Step 4 In the Archive Audit Trail dialog box, navigate to the directory (local or network) where you want to save the file.
Step 5 Enter a name in the File Name field.
You do not have to assign an extension to the file. It is readable in any application that supports text files, such as WordPad, Microsoft Word (imported), etc.
Step 6 Click Save.
The 640 entries will be saved in this file. New entries will continue with the next number in the sequence, rather than starting over.
Step 7 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.19 AUD-LOG-LOW
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: NE
The Audit Trail Log Loss condition occurs when the audit trail log is 80% full.
Note AUD-LOG-LOW is an informational condition. It does not require troubleshooting.
2.7.20 AUTOLSROFF
•Critical (CR), Service-Affecting (SA)
•Occurs only on Software R4.1 or earlier nodes
•Logical Object: CLIENT, OCN, TRUNK
The Auto Laser Shutdown alarm occurs when the OC-192 card temperature exceeds 194° F (90 ° C). The internal equipment automatically shuts down the OC-192 laser when the card temperature rises to prevent the card from self-destructing.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Clear the AUTOLSROFF Alarm
Step 1 View the temperature displayed on the ONS 15454 LCD front panel (Figure 2-1).
Figure 2-1 Shelf LCD Panel
Step 2 If the temperature of the shelf exceeds 194° F (90° C), the alarm should clear if you solve the ONS 15454 temperature problem. Complete the "Clear the HITEMP Alarm" procedure.
Step 3 If the temperature of the shelf is under 194° F (90° C), the HITEMP alarm is not the cause of the AUTOLSROFF alarm. Complete the "Physically Replace a Card" procedure for the OC-192 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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 4 If card replacement does not clear the alarm, call the Technical Assistance Center (TAC) at (1-800-553-2447) to discuss the case and if necessary open a returned materials authorization (RMA) on the original OC-192 card.
2.7.21 AUTORESET
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Automatic System Reset alarm occurs when you change an IP address or perform any other operation that causes an automatic card-level reboot.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the AUTORESET Alarm
Step 1 Verify that additional alarms that might have triggered an automatic reset.
Step 2 If the card automatically resets more than once a 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. Consult the
Cisco ONS 15454 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.22 AUTOSW-AIS
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, VTMON
The Automatic Path Protection Switch Caused by AIS condition indicates that automatic path protection switching occurred because of an AIS condition. The path protection is configured for revertive switching and reverts to the working path after the fault clears. The AIS also clears when the upstream trouble is cleared.
Generally, any AIS is a special SONET signal that tells the receiving node that the sending node has no valid signal available to send. AIS is not considered an error. The fault condition AIS is raised by the receiving node on each input where it sees the signal AIS instead of a real signal. In most cases when this condition is raised, an upstream node is raising an alarm to indicate a signal failure; all nodes downstream from it only raise some type of AIS. This condition clears when you resolved the problem on the upstream node.
Clear the AUTOSW-AIS Condition
Step 1 Complete the "Clear the AIS Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.23 AUTOSW-LOP (STSMON)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Loss of Pointer (LOP) condition indicates that automatic path protection switching occurred because of the "LOP-P" alarm on page 2-114. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-LOP (STSMON) Condition
Step 1 Complete the "Clear the LOP-P Alarm" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.24 AUTOSW-LOP (VTMON)
•Minor (MN), Service-Affecting (SA)
•Logical Object: VTMON
The AUTOSW-LOP alarm indicates that automatic path protection switching occurred because of the "LOP-V" alarm on page 2-114. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-LOP (VTMON) Alarm
Step 1 Complete the "Clear the LOP-V Alarm" procedure.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.25 AUTOSW-PDI
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Payload Defect Indication (PDI) condition indicates that automatic path protection switching occurred because of a "PDI-P" alarm on page 2-147. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-PDI Condition
Step 1 Complete the "Clear the PDI-P Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.26 AUTOSW-SDBER
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Signal Degrade Bit Error Rate (SDBER) condition indicates that a signal degrade (see the "SD (DS-1, DS-3)" condition on page 2-162) caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SD is resolved.
Clear the AUTOSW-SDBER Condition
Step 1 Complete the "Clear the SD (DS-1, DS-3) Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.27 AUTOSW-SFBER
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic USPR Switch Caused by Signal Fail Bit Error Rate (SFBER) condition indicates that the "SF (DS-1, DS-3)" condition on page 2-165 caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path when the SF is resolved.
Clear the AUTOSW-SFBER Condition
Step 1 Complete the "Clear the SF (DS-1, DS-3) Condition" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.28 AUTOSW-UNEQ (STSMON)
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: STSMON
The Automatic Path Protection Switch Caused by Unequipped condition indicates that an UNEQ alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-UNEQ (STSMON) Condition
Step 1 Complete the "Clear the UNEQ-P Alarm" procedure.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.29 AUTOSW-UNEQ (VTMON)
•Minor (MN), Service-Affecting (SA)
•Logical Object: VTMON
AUTOSW-UNEQ (VTMON) indicates that the "UNEQ-V" alarm on page 2-187 alarm caused automatic path protection switching to occur. The path protection is configured for revertive switching and reverts to the working path after the fault clears.
Clear the AUTOSW-UNEQ (VTMON) Alarm
Step 1 Complete the "Clear the UNEQ-V Alarm" procedure.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.30 BAT-A-HGH-VLT
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: NE
The High Voltage Battery (BAT) A condition occurs when the voltage level on battery lead A is between -52 VDC and -56.7 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains under this range for 120 seconds.
Clear the BAT-A-HGH-VLT Condition
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.31 BAT-A-LOW-VLT
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: NE
The Low Voltage Battery A condition occurs when the voltage on battery feed A is low. The low voltage battery A condition occurs when the voltage on battery feed A is between -44 VDC and -40 VDC. The condition clears when voltage remains above this range for 120 seconds.
Clear the BAT-A-LOW-VLT Condition
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.32 BAT-B-HGH-VLT
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: NE
The High Voltage Battery B condition occurs when the voltage level on battery lead B is between -52 VDC and -56.7 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains under this range for 120 seconds.
Clear the BAT-B-HGH-VLT Condition
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.33 BAT-B-LOW-VLT
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Object: NE
The Low Voltage Battery B condition occurs when the voltage level on battery lead B is between -44 VDC and -40 VDC. The condition indicates that the voltage on the battery lead is high. The condition remains until the voltage remains under this range for 120 seconds.
Clear the BAT-B-LOW-VLT Condition
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.34 BKUPMEMP
•Critical (CR), Non-Service Affecting (NSA)
•Logical Object: EQPT
The Primary Non-Volatile Backup Memory Failure alarm refers to a problem with the TCC+/TCC2 card's flash memory. The alarm occurs when the TCC+/TCC2 card is in use and has one of four problems: the flash manager fails to format a flash partition; the flash manager fails to write a file to a flash partition; there is a problem at the driver level, or the code volume fails cyclic redundancy checking (CRC). CRC is a method to verify for errors in data transmitted to the TCC+/TCC2.
The BKUPMEMP alarm can also cause the "EQPT" alarm on page 2-65. If the EQPT alarm is caused by BKUPMEMP, complete the following procedure to clear the BKUPMEMP and the EQPT alarm.
Caution It can take up to 30 minutes for software to be updated on a standby TCC+/TCC2 card.
Clear the BKUPMEMP Alarm
Step 1 Verify that both TCC+/TCC2 cards are powered and enabled by confirming lighted ACT/SBY LEDs on the TCC+/TCC2 cards.
Step 2 If both TCC+/TCC2 cards are powered and enabled, reset the TCC+/TCC2 card against which the alarm is raised. If the card is the active TCC+/TCC2 card, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure. If the card is the standby TCC+/TCC2, use the substeps below.
a. Right-click the standby TCC+/TCC2 card in CTC.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the Are You Sure dialog box. The card resets, the FAIL LED blinks on the physical card.
d. Wait ten minutes to verify that the card you reset completely reboots.
Step 3 If the TCC+/TCC2 you reset does not reboot successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.35 BLSROSYNC
•Major (MJ), Service-Affecting (SA)
•Logical Object: STSRNG
The BLSR Out Of Synchronization alarm is caused 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. CTC cannot generate the ring table and causes the BLSROSYNC alarm.
Clear the BLSROSYNC Alarm
Step 1 Reestablish cabling continuity to the node reporting the alarm.
When the DCC is established between the node and the rest of the BLSR, it becomes visible to the BLSR and should be able to function on the circuits.
Step 2 If alarms occur when you have provisioned the DCCs, see the "EOC" section.
Step 3 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.36 CARLOSS (DWDM Client)
•Major (MJ), Service-Affecting (SA)
•Logical Object: CLIENT
A Carrier Loss alarm on the TXP_MR_10G, TXP_MR_2.5G, TXPP_MR_2.5G, or 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 (OC-N)" alarm on page 2-123.
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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.
2.7.37 CARLOSS (DWDM Trunk)
•Major (MJ), Service-Affecting (SA)
•Logical Object: TRUNK
A Carrier Loss alarm on the optical trunk connecting to TXP_MR_10G, TXP_MR_2.5G, 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 onto http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) in order to report a service-affecting problem.
2.7.38 CARLOSS (EQPT)
•Major (MJ), Service-Affecting (SA)
•Logical Object: EQPT
A Carrier Loss on the LAN Equipment alarm generally occurs on optical cards when the ONS 15454 and the workstation hosting CTC do not have a TCP/IP connection. The problem involves the LAN or data circuit used by the RJ-45 (LAN) connector on the TCC+/TCC2 card or the LAN backplane pin connection on the ONS 15454. The CARLOSS alarm does not involve an Ethernet circuit connected to an Ethernet port. The problem is in the connection and not CTC or the ONS 15454.
On TXP and MXP cards, CARLOSS is also raised against trunk ports when G.709 monitoring is turned off.
A TXP 2.5 G card can raise a CARLOSS alarm when the payload is incorrectly configured for the 10 Gigabit Ethernet or 1 Gigabit Ethernet payload data type.
Clear the CARLOSS (EQPT) Alarm
Step 1 If the reporting card is a TXP card, verify the type of payload configured:
a. Double-click the reporting TXP card.
b. Click the Provisioning > Card tabs.
c. From the Payload type list choose the correct payload for the card and click Apply.
Step 2 If the reporting card is an optical card, verify connectivity by pinging the ONS 15454 that is reporting the alarm:
a. If you are using a Microsoft Windows operating system, from the Start Menu choose Programs > Accessories > Command Prompt.
b. If you are using a Sun Solaris operating system, from the Common Desktop Environment (CDE) click the Personal Application tab and click Terminal.
c. For both the Sun and Microsoft operating systems, at the prompt type:
ping [ONS 15454 IP address]
For example, ping 198.168.10.10.
If the workstation has connectivity to the ONS 15454, it shows a "reply from [IP Address]" after the ping. If the workstation does not have connectivity, a "Request timed out" message appears.
Step 3 If the ping is successful, an active TCP/IP connection exists. Restart CTC:
a. Exit from CTC.
b. Reopen the browser.
c. Log into CTC.
Step 4 Verify that the straight-through (CAT-5) LAN cable is properly connected and attached to the correct port.
Step 5 If the straight-through (CAT-5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
Step 6 If you are unable to establish connectivity, replace the straight-through cable with a new known-good cable.
Step 7 If you are unable to establish connectivity, perform standard network or LAN diagnostics. For example, trace the IP route, verify cables continuity, and troubleshoot any routers between the node and CTC.
Step 8 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.39 CARLOSS (E-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Occurs only on Software R4.1 or earlier nodes
•Logical Object: E100T, E1000F
A Carrier Loss alarm on the LAN E-Series Ethernet (traffic) card is the data equivalent of the "LOS (OC-N)" alarm on page 2-123. The Ethernet card has lost its link and is not receiving a valid signal. The most common causes of the CARLOSS alarm are a disconnected cable, an Ethernet GBIC fiber connected to an optical (traffic) card rather than an Ethernet device, 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.
The CARLOSS alarm also occurs after a node database is restored. After restoration, the alarm clears in approximately 30 seconds after the node reestablishes spanning tree protocol (STP). The database restoration circumstance applies to the E-series Ethernet cards but not the G1000-4 card, because 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. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CARLOSS (E-Series Ethernet) Alarm
Step 1 Verify that the straight-through (CAT-5) LAN cable is properly connected and attached to the correct port.
Step 2 If the straight-through (CAT-5) LAN cable is properly connected and attached to the port, verify that the cable connects the card to another Ethernet device and is not misconnected to an OC-N card.
Step 3 If no misconnection to an OC-N card exists, verify that the transmitting device is operational. If not, troubleshoot the device.
Step 4 If the alarm does not clear, use an Ethernet test set to determine whether a valid signal is coming into the Ethernet port.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 5 If a valid Ethernet signal is not present and the transmitting device is operational, replace the straight-through (CAT-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 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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 8 If a CARLOSS alarm repeatedly appears and clears, use the following steps to examine the layout of your network to determine whether the Ethernet circuit is part of an Ethernet manual cross-connect.
Step 9 If the reporting Ethernet circuit is part of an Ethernet manual cross-connect, then the reappearing alarm might be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps unless the Ethernet circuit is part of a manual cross-connect:
a. Right-click anywhere in the row of the CARLOSS alarm.
b. Click the Select Affected Circuits dialog box that appears.
c. Record the information in the type and size columns of the highlighted circuit.
d. From the examination of the layout of your network, determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 at the other end of the Ethernet manual cross-connect.
•Double-click the Ethernet card that is part of the Ethernet manual cross-connect.
•Click the Circuits tab.
•Record the information in the type and size columns of the circuit that is part of the Ethernet manual cross-connect. The Ethernet manual cross-connect circuit connects the Ethernet card to an OC-N card at the same node.
e. Use the information you recorded to determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size.
If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. For more information, refer to the Cisco ONS 15454 Procedure Guide.
Step 10 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.40 CARLOSS (G-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Logical Object: G1000
A Carrier Loss alarm on the LAN G-Series Ethernet (traffic) card is the data equivalent of the "LOS (OC-N)" condition on page 2-123. The Ethernet card has lost its link and is not receiving a valid signal.
CARLOSS on the G1000-4 card is caused by one of two situations:
•The G1000-4 port reporting the alarm is not receiving a valid signal from the attached Ethernet device. The CARLOSS can be caused by an improperly connected Ethernet cable or a problem with the signal between the Ethernet device and the G1000-4 port.
•If a problem exists in the end-to-end path (including possibly the far-end G1000-4 card), it causes the reporting G1000-4 card to turn off the Gigabit Ethernet transmitter. Turning off the transmitter typically causes the attached device to turn off its link laser, which results in a CARLOSS on the reporting G1000-4 card. The root cause is the problem in the end-to-end path. When the root cause is cleared, the far-end G1000-4 port turns the transmitter laser back on and clears the CARLOSS on the reporting card. If a turned-off transmitter causes the CARLOSS alarm, other alarms such as the "TPTFAIL (G-Series Ethernet)" alarm on page 2-181 or OC-N alarms or conditions on the end-to-end path normally accompany the CARLOSS (G-Series) alarm.
Refer to the Cisco ONS 15454 Reference Manual for a description of the G1000-4 card's end-to-end Ethernet link integrity capability. Also see the "TRMT" alarm on page 2-183 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. 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 OC-N card.
Step 3 If no misconnection to the OC-N card exists, verify that the attached transmitting Ethernet device is operational. If not, troubleshoot the device.
Step 4 Verify that optical receive levels are within the normal range.
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 card turns off its transmitter laser and reports a CARLOSS alarm. If link autonegotiation has been enabled for the port, verify whether there are conditions that could cause autonegotiation to fail:
a. Confirm that the attached Ethernet device has 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. (The autonegotiation process restarts.)
Step 9 If the alarm does not clear and the "TPTFAIL (G-Series Ethernet)" alarm on page 2-181 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 the CARLOSS and the TPTFAIL alarms are reported, the reason for the condition might be the G1000-4's end-to-end link integrity feature taking action on a remote failure indicated by the TPTFAIL alarm.
Step 10 If the TPTFAIL alarm was not reported, verify whether a terminal (inward) loopback has been provisioned on the port:
a. In the node view, click the card to go to card view.
b. Click the Conditions tab and the Retrieve Conditions button.
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, complete the "Clear a Loopback" procedure.
On the G1000-4 card, provisioning a terminal (inward) loopback causes the transmit laser to turn off. If an attached Ethernet device detects the loopback as a loss of carrier, the attached Ethernet device shuts off the transmit laser to the G1000-4 card. Terminating the transmit laser could raise the CARLOSS alarm because the loopbacked G1000-4 port detects the termination.
If the does not have a LPBKTERMINAL condition, continue to Step 12.
Step 12 If a CARLOSS alarm repeatedly appears and clears, the reappearing alarm might be a result of mismatched STS circuit sizes in the setup of the manual cross-connect. Perform the following steps if the Ethernet circuit is part of a manual cross-connect.
Note An Ethernet manual cross-connect is used when another vendors' equipment sits between ONS 15454s, and the OSI/TARP-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit is manually cross connected to an STS channel riding through the non-ONS network.
a. Right-click anywhere in the row of the CARLOSS alarm.
b. Right-click or left-click the Select Affected Circuits dialog box.
c. Record the information in the type and size columns of the highlighted circuit.
d. Examine the layout of your network and determine which ONS 15454 and card host the Ethernet circuit at the other end of the Ethernet manual cross-connect.
•Log into the ONS 15454 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 connects the Ethernet card to an OC-N card at the same node.
e. Determine whether the two Ethernet circuits on each side of the Ethernet manual cross-connect have the same circuit size from the circuit size information you recorded.
f. If one of the circuit sizes is incorrect, complete the "Delete a Circuit" procedure and reconfigure the circuit with the correct circuit size. Refer to the Cisco ONS 15454 Procedure Guide for detailed procedures to create circuits.
Step 13 If a valid Ethernet signal is present, complete the "Remove and Reinsert (Reseat) a Card" procedure.
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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 15 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.41 CARLOSS (ML-Series Ethernet)
•Major (MJ), Service-Affecting (SA)
•Logical Object: ML100T, ML1000
A Carrier Loss alarm on the ML-series Ethernet (traffic) card is the data equivalent of the "LOS (OC-N)" alarm on page 2-123. The Ethernet port has lost its link and is not receiving a valid signal.
A CARLOSS alarm is caused when the Ethernet port has been configured from the internal operating system (IOS) command line interface (CLI) as a no shutdown port and one of the following items also occurs:
•The cable is not properly connected to the near or far port
•Auto-negotiation is failing
•The speed (10/100 ports only) is set incorrectly
For information about provisioning ML-series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.1.
Clear the CARLOSS (ML-Series 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 card port and the peer Ethernet port.
Step 3 If the alarm does not clear, verify that the speed is set properly on the ML card port and the peer Ethernet port if you are using 10/100 ports.
Step 4 If the alarm does not clear, the Ethernet signal is not valid, but the transmitting device is operational, replace the LAN cable connecting the transmitting device to the Ethernet port.
Step 5 If the alarm does not clear, disable and reenable the Ethernet port by performing a "shutdown" and then a "no shutdown" on the IOS CLI. Autonegotiation will restart.
Step 6 If the alarm does not clear, perform a facility (line) loopback on the ML card. Complete the "1.2.1 Perform a Facility (Line) Loopback on a Source DS-N Port" procedure on page 1-6.
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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Note When replacing a card with an identical type of card, no additional CTC provisioning is required.
Step 9 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.42 CKTDOWN
•Critical (CR), Service-Affecting (SA)
•Logical Object: UCP-CKT
The UCP Circuit Down alarm applies to logical circuits created within the UCP between devices. It 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 because it is an edge device.
Clear the CKTDOWN Alarm
Step 1 Ensure that the channel to neighbor has been provisioned with the correct IP address:
a. In the node view, click the Provisioning > UCP > Neighbor tabs.
b. View the entries to find out whether the node you are trying to contact is listed.
The node name is listed under the Name column and the IP address is listed under the Node ID column. If the Node ID says 0.0.0.0 and the Enable Discovery check box is selected, the node could not automatically identify the IP address. Ping the node to ensure that it is physically and logically accessible.
c. Click Start > Programs > Accessories > Command Prompt to open an MS-DOS command window for pinging the neighbor.
d. At the command prompt (C:\>), type:
ping [node DNS name or node IP address]
If you typed the domain name services (DNS) name and the ping was successful, you will see:
pinging [node dns name].[domain name].com. [node IP address] with 32 bytes of data:
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Reply from [IP address]: bytes=32 time=10ms TTL=60
Ping statistics for [IP address]:
Packets sent = 4 Received = 4 Lost = 0 (0% lost),
Approximate round trip time in milli-seconds:
Minimum = [minimum ms], Maximum = [maximum ms], Average = [average ms]
If you typed the IP address and the ping command is successful, the result will look similar but will not include the DNS name in the first line.
e. If your DNS name or IP address ping was successful, IP access to the node is confirmed, but your neighbor configuration is wrong. Delete the neighbor by selecting it in the window and clicking Delete.
f. If the ping was unsuccessful, you will get the following reply repeated for each try:
A negative reply indicates that the neighbor node is not physically or logically accessible. Resolve the access problem, which is probably a cabling issue.
Step 2 If the neighbor has not been provisioned, or if you had to delete the neighbor, create one:
a. In the Provisioning > UCP > Neighbor tabs, click the Create button.
b. In the Neighbor Discovery window, enter the node'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.
c. Click OK.
The node is listed in the Neighbor column list. If the neighbor discovery worked, the neighbor IP address is listed in the Node ID column. If it is not successful, the column will say 0.0.0.0.
Step 3 If neighbor discovery is enabled, make sure that the neighbor node ID, remote IPCC have been discovered correctly.
Step 4 Click the Provisioning > UCP > IPCC tabs and view the IPCC listing. If the IPCC has been created correctly, the Remote IP column contains the neighbor's IP address.
Step 5 If the neighbor IP address is not correctly discovered, the field contains 0.0.0.0.
a. Click the entry to select the neighbor IP address and click Delete.
b. If you get an error that will not allow you to delete the IPCC, you will have to delete the neighbor and recreate it. Click the Neighbor tab.
c. Click to select the neighbor and click Delete.
d. Then go back to Step 2 to recreate the neighbor.
Step 6 If remote IPCC has not been discovered, or if it had to be deleted, create the connection:
a. In the Provisioning > UCP > IPCC tabs, click Create.
b. In the Unified Control Plane Provisioning window, click Next.
c. If no IPCCs are listed, click Create.
d. In the Create New IPCC window, click on the DCC termination corresponding to the core network interface.
Leave the SDCC radio button selected (as long as DCCs have been created on the node) and leave the Leave Unchanged radio button selected.
e. Click OK. The IPCC is listed in the Unified Control Plane Provisioning window.
f. Click the neighbor to select it, and click Next.
g. Choose the UCP interface [for example Slot 5 (OC-48), port 1] where the core network is connected from the pull-down menu. The field default is the node where you are logged in.
h. Choose the UCP interface TNA address type. The default is IPv4. The address field lists the login node IP address by default.
i. Click Finish. If creation is successful, the Remote ID column in the IPCC tab will contain the neighbor's IP address.
Step 7 Ensure that the local and remote interface IDs have been provisioned correctly:
a. Click the Interface tab. View the slot and port listed in the Interface column (for example, Slot 5 (OC48), port 1).
b. Compare the listed interface listed with the IPCC tab SDCC column entry.
Step 8 If the Interface column is not the same as the SDCC column entry, click the entry in the Interface window to select it and click Delete.
Step 9 Click Next.
Step 10 In the Existing CCIDs list, click the IPCC containing the DCC connection. Click Next.
The correct interface for the selected CCID is shown in the UPC Interface field, and the correct IP address information for the login node is shown by default in the other fields. Click Finish.
Step 11 If you completed all of these steps and verified the information, the alarm could be the result of a misconfiguration in the core network. Contact the core site administrators.
Step 12 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.43 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 is first powered up.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at 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. Consult the
Cisco ONS 15454 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.44 COMIOXC
•Critical (CR), Service-Affecting (SA)
•Occurs only on Software R4.1 or earlier nodes
•Logical Object: EQPT
The Input/Output Slot To Cross-Connect Communication Failure alarm is caused by the cross-connect card. It occurs when there is a communication failure for a traffic (multispeed slots or high-speed) slot.
Clear the COMIOXC Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure on the reporting cross-connect card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. 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, move traffic off the reporting cross-connect card. Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure.
Step 4 Complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting cross-connect card.
Step 5 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting cross-connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 6 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.45 COMM-FAIL
•Minor (MN), Non-Service Affecting (NSA)
•Occurs only on DWDM (Software R4.5) nodes
The Plug-In Module (card) Communication Failure indicates that there is a communication failure between the TCC2 and the card. The failure could indicate a broken card interface.
Clear the COMM-FAIL Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card.
Step 2 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the card.
Caution Removing a card that currently 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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Step 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.46 CONTBUS-A-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC+/TCC2 Slot to TCC+/TCC2 Slot alarm occurs when the main processor on the TCC+/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. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CONTBUS-A-18 Alarm
Step 1 Complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure to make the TCC+/TCC2 in Slot 11 active.
Step 2 Wait approximately 10 minutes for the TCC+/TCC2 in Slot 7 to reset as the standby TCC+/TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC+/TCC2 card in Slot 11 and complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure to make the standby TCC+/TCC2 in Slot 7 active.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.47 CONTBUS-B-18
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A Communication Failure from TCC+/TCC2 Slot to TCC+/TCC2 Slot alarm occurs when the main processor on the TCC+/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. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CONTBUS-B-18 Alarm
Step 1 Position the cursor over the TCC+/TCC2 card in Slot 11 and complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure to make the TCC+/TCC2 in Slot 7 active.
Step 2 Wait approximately 10 minutes for the TCC+/TCC2 in Slot 11 to reset as the standby TCC+/TCC2. Verify that the standby LED is illuminated before proceeding to the next step.
Step 3 Position the cursor over the TCC+/TCC2 card in Slot 7 and complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure to make the standby TCC+/TCC2 in Slot 11 active.
Step 4 If the reset card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.48 CONTBUS-IO-A
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCC A to Shelf Slot Communication Failure alarm occurs when the active TCC+/TCC2 card in Slot 7 (TCC A) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-A alarm might appear briefly when the ONS 15454 switches to the protect TCC+/TCC2 card. In the case of a TCC+/TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC+/TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC+/TCC2 card to the reporting card. The physical path of communication includes the TCC+/TCC2 card, the other card, and the backplane.
This alarm can also appear when you upgrade from TCC+ cards to TCC2 cards. In this case, it clears without intervention within about 13 minutes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CONTBUS-IO-A Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (BPLANE)" alarm on page 2-134 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby TCC+/TCC2 in Slot 11, perform a CTC reset of the object card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby TCC+/TCC2 in Slot 11, perform a soft reset of this card:
a. Right-click the Slot 11 TCC+/TCC2 card.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 4 If CONTBUS-IO-A is raised on several cards at once, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 5 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 6 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 7 If the reseated card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.49 CONTBUS-IO-B
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: EQPT
A TCC B to Shelf Slot Communication Failure alarm occurs when the active TCC+/TCC2 card in Slot 11 (TCC B) has lost communication with another card in the shelf. The other card is identified by the Object column in the CTC alarm window.
The CONTBUS-IO-B alarm might appear briefly when the ONS 15454 switches to the protect TCC+/TCC2 card. In the case of a TCC+/TCC2 protection switch, the alarm clears after the other cards establish communication with the new active TCC+/TCC2 card. If the alarm persists, the problem is with the physical path of communication from the TCC+/TCC2 card to the reporting card. The physical path of communication includes the TCC+/TCC2 card, the other card, and the backplane.
This alarm can also appear when you upgrade from TCC+ cards to TCC2 cards. In this case, it clears without intervention within about 13 minutes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CONTBUS-IO-B Alarm
Step 1 Ensure that the reporting card is physically present in the shelf. Record the card type. Click the Inventory tab to reveal the provisioned type.
If the actual card type and the provisioned card type do not match, see the "MEA (BPLANE)" alarm on page 2-134 for the reporting card.
Step 2 If the alarm object is any single card slot other than the standby TCC+/TCC2 in Slot 7, perform a CTC reset of the object card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 If the alarm object is the standby TCC+/TCC2 in Slot 7, perform a soft reset of this card:
a. Right-click the Slot 7 TCC+/TCC2 card.
b. Choose Reset Card from the shortcut menu.
c. Click Yes in the confirmation dialog box. Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 4 If CONTBUS-IO-B is raised on several cards at once, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Step 5 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 6 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 7 If the reseated card has not rebooted successfully, or the alarm has not cleared, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.50 CTNEQPT-PBPROT
•Critical (CR), Service-Affecting (SA)
•Occurs only on Software R4.1 or earlier nodes
•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 TCC+/TCC2 card, or the backplane.
Note If all traffic cards show CTNEQPT-PBPROT alarm, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure for the standby TCC+/TCC2 card. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the standby TCC+/TCC2 card. Do not physically reseat an active TCC+/TCC2 card. Reseating the TCC+/TCC2 disrupts traffic.
Note This alarm automatically raises and clears when the Slot 8 cross-connect card is reseated.
Caution It can take up to 30 minutes for software to be updated on a standby TCC+/TCC2 card.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CTNEQPT-PBPROT Alarm
Step 1 Perform a CTC reset on the standby cross-connect card. Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. 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 TCC+/TCC2 reboots automatically, call TAC (1-800-553-2447).
Step 3 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.
Step 4 Determine whether the card is an active card or standby card in a protection group. Click the node view Maintenance > Protection tabs, then click the protection group. The cards and their status will be displayed in the list.
Step 5 If the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. After you move traffic off the active card, or if the reporting card is standby, continue with the following steps.
Step 6 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure on 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, and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 Complete the "Clear an External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting 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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Step 11 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.51 CTNEQPT-PBWORK
•Critical (CR), Service-Affecting (SA)
•Occurs only on Software R4.1 or earlier nodes
•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 CTNEEQPT-PBWORK alarm, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure for the active TCC+/TCC2 card and then complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the reseat fails to clear the alarm, complete the "Physically Replace a Card" procedure for the TCC+/TCC2 card. Do not physically reseat an active TCC+/TCC2 card; it disrupts traffic.
Note This alarm automatically raises and clears when the Slot 10 cross-connect card is reseated.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the CTNEQPT-PBWORK Alarm
Step 1 Complete the "Side Switch the Active and Standby Cross-Connect Cards" procedure for the active cross-connect card.
Note After the active cross-connect goes into standby, the original standby slot becomes active. The active card ACT/SBY LED becomes green.
Step 2 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 3 Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 4 If the alarm does not clear, complete the "Remove and Reinsert (Reseat) a Card" procedure for the standby cross-connect card.
Note The ACT/SBY LED of the active card is green. The ACT/SBY LED of the standby card is amber.
Step 5 If the alarm does not clear and the reporting traffic card is the active card in the protection group, complete the "Switch Protection Group Traffic with an External Switching Command" procedure. If the card is standby, or if you have moved traffic off the active card, proceed with the following steps.
Step 6 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 7 Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. For LED appearance, see the "Non-DWDM Card LED State After Successful Reset" section.
Step 8 If the CTC reset does not clear the alarm, complete the "Remove and Reinsert (Reseat) a Card" procedure for the reporting card.
Step 9 If you switched traffic, complete the "Clear an External Switching Command" procedure.
Step 10 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the cross-connect card.
Note When you replace a card with an identical type of card, you do not need to make any changes to the database.
Step 11 If the alarm does not clear, complete the "Physically Replace a Card" procedure for the reporting traffic card.
Step 12 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.52 DATAFLT
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Software Data Integrity Fault alarm occurs when the TCC+/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 TCC+/TCC2 Card and Activate Standby Card" procedure.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.53 DBOSYNC
•Major (MJ), Non-Service Affecting (NSA)
•Logical Object: NE
The standby Database Out Of Synchronization alarm occurs when the standby TCC+/TCC2 "To be Active" database does not synchronize with the active database on the active TCC+/TCC2.
Caution If you reset the active TCC+/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 TCC+/TCC2 database. Complete the "Back Up the Database" procedure in the Cisco ONS 15454 Procedure Guide.
Step 2 Make a minor provisioning change to the active database to see if applying a provisioning change if applying a provisioning change clears the alarm:
a. In the node view, click the Provisioning > General tabs.
b. In the Description field, make a small change such as adding a period to the existing entry.
The change causes a database write but will not affect the node state. The write might take up to a minute.
Step 3 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.54 DS3-MISM
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: DS3
•Occurs only on Software R4.1 or earlier nodes
The DS-3 Frame Format Mismatch condition indicates a frame format mismatch on a signal transiting the DS3XM-6 card. The condition occurs when the provisioned line type and incoming signal frame format type do no match. For example, if the line type is set to C-BIT for a DS3XM-6 card, and the incoming signal's frame format is detected as M13, then the ONS 15454 reports a DS3-MISM condition.
Clear the DS3-MISM Condition
Step 1 Display the CTC card view for the reporting DS3XM-6 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 expected incoming signal.
Step 4 If the Line Type pull-down menu does not match the expected incoming signal, select the correct Line Type in the pull-down menu.
Step 5 Click Apply.
Step 6 If the condition does not clear after the user verifies that the provisioned line type matches the expected incoming signal, use an optical test set to verify that the actual signal coming into the ONS 15454 matches the expected incoming signal.
For specific procedures to use the test set equipment, consult the manufacturer.
Step 7 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.55 DSP-COMM-FAIL
•Major (MJ), Service-Affecting (SA)
•Logical Object: TRUNK
The DSP Communication Failure alarm indicates that there is a communications failure between a muxponder (MXP) or transponder (TXP) card microprocessor and the on-board DSP chip that controls the trunk (DWDM) port. This alarm typically occurs after a DSP code upgrade.
The alarm is temporary and does not require user action. The MXP or TXP card microprocessor will attempt to restore communication with the DSP chip until the alarm is cleared.
If the alarm is raised for an extended period, the MXP or TXP card will raise the "DSP-FAIL" alarm on page 2-61.
Note If the DSP-COMM-FAIL alarm continues for an extended period, traffic could be affected.
Note DSP-COMM-FAIL is informational. The alarm does not require troubleshooting.
2.7.56 DSP-FAIL
•Major (MJ), Service-Affecting (SA)
•Logical Object: TRUNK
The DSP Failure alarm indicates that a "DSP-COMM-FAIL" alarm on page 2-61 has persisted for an extended period on an MXP or TXP card. It indicates that the card is faulty.
Clear the DSP-FAIL Alarm
Step 1 Complete the "Physically Replace a Card" procedure for the reporting MXP or TXP card.
Caution Removing a card that currently 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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.57 EHIBATVG-A
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Extreme High Voltage Battery A alarm occurs when the voltage level on battery lead A exceeds -56.7 VDC. The alarm indicates that the voltage on the battery lead is extremely high, and power redundancy is no longer guaranteed. The alarm remains until the voltage remains under -56.7 VDC in the normal range for 120 seconds.
Clear the EHIBATVG-A Alarm
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.58 EHIBATVG-B
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Extreme High Voltage Battery B alarm occurs when the voltage level on battery lead B exceeds -56.7 VDC. The alarm indicates that the voltage on the battery lead is extremely high, and power redundancy is no longer guaranteed. The alarm remains until the voltage remains under -56.7 VDC in the normal range for 120 seconds.
Clear the EHIBATVG-B Alarm
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.59 ELWBATVG-A
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Extreme Low Voltage Battery A alarm occurs when the voltage on battery feed A is extremely low or has been lost, and power redundancy is no longer guaranteed. The extreme low voltage battery A alarm occurs when the voltage on battery feed A falls under -40.5 VDC. The alarm clears when voltage remains above -40.5 VDC in the normal range for 120 seconds.
Clear the ELWBATVG-A Alarm
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead A.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.60 ELWBATVG-B
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: NE
The Extreme Low Voltage Battery B alarm occurs when the voltage on battery feed B is extremely low or has been lost, and power redundancy is no longer guaranteed. The extreme low voltage battery B alarm occurs when the voltage on battery feed B falls under-40.5 VDC. The alarm clears when voltage remains above -40.5 VDC in the normal range for 120 seconds.
Clear the ELWBATVG-B Alarm
Step 1 The problem is external to the ONS 15454. Troubleshoot the power source supplying battery lead B.
Step 2 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.61 EOC
•Major (MJ), Non-Service Affecting (NSA)
•Portions of this procedure are different for DWDM
•Logical Objects: CLIENT, OCN, TRUNK
The SONET Data Communications Channel (DCC) Termination Failure alarm occurs when the ONS 15454 loses its data communications channel. The DCC is three bytes, D1 through D3, in the SONET overhead. The bytes convey information about Operation, Administration, Maintenance, and Provisioning (OAM&P). The ONS 15454 uses the DCC on the SONET section layer to communicate network management information.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service (IS) for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Note If a circuit shows an incomplete state when the EOC alarm is raised, it occurs when the logical circuit is in place, and will be able to carry traffic when the DCC termination issue is resolved. You do not need to delete the circuit when troubleshooting this alarm.
Clear the EOC Alarm
Step 1 If the "LOS (DS-1)" alarm on page 2-117 is also reported, complete the "Clear the LOS (DS-1) 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 checking that the ACT LED on each OC-N card is illuminated.
Step 4 If the ACT LEDs on OC-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 port is active and in service:
a. Confirm that the OC-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 port is in service, 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 click IS from the pull-down menu. Click Apply.
Step 7 For all nodes, if the card is in service, use an optical test set to verify whether signal failures are present on fiber terminations.
For specific procedures to use the test set equipment, consult the manufacturer.
Caution Using an optical test set disrupts service on the OC-N card. It might be necessary to manually switch traffic carrying circuits over to a protection path.
Step 8 If no signal failures on terminations exist, measure power levels to verify that the budget loss is within the parameters of the receiver. See the "OC-N Card Transmit and Receive Levels" section on page 1-89 for Software Release 4.1 (or earlier) card levels and see the Cisco ONS 15454 Reference Manual for Release 4.5 (DWDM) card levels.
Step 9 If budget loss is within parameters, ensure that fiber connectors are securely fastened and properly terminated. For more information refer to the "Install the Fiber-Optic Cables" procedure in the Cisco ONS 15454 Procedure Guide.
Step 10 If fiber connectors are properly fastened and terminated, complete the "Reset Active TCC+/TCC2 Card and Activate Standby Card" procedure.
Wait ten minutes to verify that the card you reset completely reboots and becomes the standby card.
Resetting the active TCC+/TCC2 switches control to the standby TCC+/TCC2. If the alarm clears when the ONS 15454 switches to the standby TCC+/TCC2, the user can assume that the original active TCC+/TCC2 is the cause of the alarm.
Step 11 If the TCC+/TCC2 replacement does not clear the alarm, delete the problematic DCC termination:
a. For Release 4.5 (DWDM) nodes, click the Provisioning > DCC/GCC/OSC tabs. For Release 4.1 or earlier nodes, click the Provisioning > DCC/GCC tabs.
b. Highlight the problematic DCC termination.
c. Click Delete.
d. Click Yes in the confirmation dialog box.
Step 12 Recreate the DCC termination using the Cisco ONS 15454 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, call TAC (1-800-553-2447). If the TAC technician tells you to reseat the card, complete the "Remove and Reinsert (Reseat) the Standby TCC+/TCC2" procedure. If the TAC technician tells you to remove the card and reinstall a new one, follow the "Physically Replace a Card" procedure.
2.7.62 EQPT
•Critical (CR), Service-Affecting (SA)
•Logical Objects: AICI-AEP, AICI-AIE
An Equipment Failure alarm indicates that a hardware failure has occurred on the reporting card.
If the EQPT alarm occurs with a BKUPMEMP alarm, see the "BKUPMEMP" alarm on page 2-40. The BKUPMEMP procedure also clears the EQPT alarm.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the EQPT Alarm
Step 1 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure for the reporting card. For the LED behavior, see the "Non-DWDM Card LED Activity During Reset" section.
Step 2 Verify that the reset is complete and error-free, and that no new related alarms appear in CTC. 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. Consult the
Cisco ONS 15454 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 onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.63 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 AIP to the system board may be bad.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the EQPT-MISS Alarm
Step 1 If the alarm is reported against the fan, verify that the fan-tray assembly is present.
Step 2 If the fan-tray assembly is present, complete the "Remove and Reinsert Fan-Tray Assembly" procedure.
Step 3 If no fan-tray assembly is present, obtain a fan-tray assembly and refer to the "Install the Fan-Tray Assembly," procedure in the Cisco ONS 15454 Procedure Guide.
Step 4 If the alarm does not clear, replace the ribbon cable from the AIP to the system board with a known-good ribbon cable.
Step 5 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.64 ERFI-P-CONN
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
The three-bit (Enhanced) Remote Failure Indication - Path - Connectivity condition is triggered on DS-1, DS-3, and VT circuits when the "UNEQ-P" alarm on page 2-185 and the "TIM-P" alarm on page 2-180 are raised on the transmission signal.
Clear the ERFI-P-CONN Condition
Step 1 Complete the "Clear the UNEQ-P Alarm" procedure. This should clear the ERFI condition.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.65 ERFI-P-PAYLD
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
The three-bit (Enhanced) Remote Failure Indication - Path - Payload condition is triggered on DS-1, DS-3, and VT circuits when the "PLM-P" alarm on page 2-149 alarm is raised on the transmission signal.
Clear the ERFI-P-PAYLD Condition
Step 1 Complete the "Clear the PLM-P Alarm" procedure. This should clear the ERFI condition.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.66 ERFI-P-SRVR
•Not Reported (NR), Non-Service Affecting (NSA)
•Logical Objects: STSMON, STSTRM
The three-bit (Enhanced) Remote Failure Indication Path Server condition is triggered on DS-1, DS-3, and VT circuits when the "AIS-P" alarm on page 2-24 or the "LOP-P" alarm on page 2-114 is raised on the transmission signal.
Clear the ERFI-P-SRVR Condition
Step 1 Complete the "Clear the LOP-P Alarm" procedure. This should clear the ERFI condition.
Step 2 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
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 (traffic) cards. These cards process startup configuration files line by line. If one or more lines cannot be executed, the error causes the ERROR-CONFIG alarm. ERROR-CONFIG is not caused by hardware failure.
The typical reasons for an errored startup file are that (1) you stored the configuration for one type of ML card in the database and then installed another type in its slot, and (2) the configuration file contained a syntax error on one of the lines.
For information about provisioning the ML-series Ethernet cards from the IOS interface, refer to the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.1.
Clear the ERROR-CONFIG Alarm
Step 1 If you have a different type of ML card specified in the startup configuration file than what you have installed, create the correct startup configuration.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide, Release 4.1.
Step 2 Upload the configuration file to the TCC+/TCC2:
a. In the node view, right-click the ML card graphic.
b. Choose IOS Startup Config from the shortcut menu.
c. Click Upload to TCC and navigate to the file location.
Step 3 Complete the "Reset a Traffic Card or Cross-Connect Card in CTC" procedure.
Step 4 If the alarm does not clear or if your configuration file was correct according to the installed card, start an IOS CLI for the card:
a. Right click the ML card graphic in node view.
b. Choose Open IOS Connection from the shortcut menu.
Note Open IOS Connection is not available unless the ML card is physically installed in the shelf.
Follow the card provisioning instructions in the Cisco ONS 15454 SONET/SDH ML-Series Multilayer Ethernet Card Software Feature and Configuration Guide to correct the errored configuration file line.
Step 5 Execute the CLI command copy run start. The command copies the new card configuration into the database and clears the alarm.
Step 6 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.68 E-W-MISMATCH
•Major (MJ), Service-Affecting (SA)
•Logical Object: OCN
A Procedural Error Misconnect East/West Direction alarm occurs when nodes in a ring have an east slot misconnected to another east slot or a west slot misconnected to another west slot. In most cases, the user did not connect the fibers correctly, or the ring provisioning plan was flawed. You can physically reconnect the cable to the correct slots to clear the E-W-MISMATCH alarm. Alternately, you can delete and recreate the span in CTC to change the west line and east line designations. The CTC method clears the alarm, but might change the traditional east-west node connection pattern of the ring.
Note The E-W-MISMATCH alarm also appears during the initial set up of a ring with its East-West slots configured correctly. If the alarm appears during the initial setup, the alarm clears itself shortly after the ring setup is complete.
Note The lower numbered slot at a node is traditionally labeled as the west slot and the higher numbered slot is labeled as the east slot. For example, Slot 6 is west and Slot 12 is east.
Note The physical switch procedure is the recommend method of clearing the E-W-MISMATCH alarm. The physical switch method reestablishes the logical pattern of connection in the ring. However, you can also use CTC to recreate the span and identify the misconnected slots as east and west. The CTC method is useful when the misconnected node is not geographically near the troubleshooter.
Clear the E-W-MISMATCH Alarm with a Physical Switch
Step 1 Diagram the ring setup, including nodes and spans, on a piece of paper or white board.
Step 2 In the node view, click View > Go to Network View.
Step 3 Label each of the nodes on the diagram with the same name that appears on the network map.
Step 4 Right-click each span to reveal the node name/slot/port for each end of the span.
Step 5 Label the span ends on the diagram with the same information. For example, with Node1/Slot12/Port1 - Node2/Slot6/Port1 (2F BLSR OC48, Ring ID=0), label the end of the span that connects Node 1 and Node 2 at the Node 1 end as Slot 12/Port 1. Label the Node 2 end of that same span Slot 6/ Port 1.
Step 6 Repeat Steps 4 and 5 for each span on your diagram.
Step 7 Label the highest slot at each node east and the lowest slot at each node west.
Step 8 Examine the diagram. You should see a clockwise pattern of west slots connecting to east slots for each span.
Step 9 If any span has an east-to-east or west-to-west connection, physically switching the fiber connectors from the card that does not fit the pattern to the card that continues the pattern should clear the alarm.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Step 10 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
Clear the E-W-MISMATCH Alarm in CTC
Step 1 Log into the misconnected node. A misconnected node has both ring fibers connecting it to its neighbor nodes misconnected.
Step 2 Click the Maintenance > BLSR tabs.
Step 3 From the row of information for the fiber span, complete the "Identify a Ring ID or Node ID Number" procedure to identify the node ID, ring ID, 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 BLSR:
a. Click the Provisioning > BLSR tabs.
b. Click the row from Step 3 to select it and click Delete.
c. Click Create BLSR.
d. Fill in the ring ID and node ID from the information collected in Step 3.
e. Click Finish in the BLSR Creation window.
Step 6 Display the node view and click the Maintenance > BLSR 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 onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.69 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 and CTC might be affected.The network management LAN is the data network connecting the workstation running the CTC software to the TCC+/TCC2 card. The problem causing the alarm is external to the ONS 15454.
Troubleshoot the network management LAN connected to the TCC+/TCC2 card for excess collisions. You might need to contact the system administrator of the network management LAN to accomplish the following steps.
Clear the EXCCOL Alarm
Step 1 Verify that the network device port connected to the TCC+/TCC2 card has a flow rate set to 10 Mb, half-duplex.
Step 2 If the port has the correct flow rate and duplex setting, troubleshoot the network device connected to the TCC+/TCC2 card and the network management LAN.
Step 3 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.70 EXERCISE-RING-FAIL
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
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 will not be reported.
Procedure: Clear the EXERCISE-RING-FAIL Condition
Step 1 Look for and clear, if present, the "LOF (OC-N)" alarm on page 2-111, the "LOS (OC-N)" alarm on page 2-123, or BLSR alarms.
Step 2 Reissue the Exercise Ring command:
a. Click the Provisioning > BLSR 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.71 EXERCISE-RING-REQ
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
The Exercise Request on Ring condition occurs when optical (traffic) cards in two-fiber and four-fiber BLSRs are tested using the EXERCISE RING command.
Note EXERCISE-RING-REQ is an informational condition. It does not require troubleshooting.
2.7.72 EXERCISE-SPAN-FAIL
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
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 will not be reported.
Procedure: Clear the EXERCISE-SPAN-FAIL Condition
Step 1 Look for and clear, if present, the "LOF (OC-N)" alarm on page 2-111, the "LOS (OC-N)" alarm on page 2-123, or a BLSR alarm.
Step 2 Reissue the Exercise Span command:
a. Click the Maintenance > BLSR 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 3 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.73 EXERCISE-SPAN-REQ
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
The Exercise Request on Span condition occurs when optical (traffic) cards in a four-fiber BLSR are tested using the EXERCISE SPAN command.
Note EXERCISE-SPAN-REQ is an informational condition. It does not require troubleshooting.
2.7.74 EXT
•Minor (MN), Non-Service Affecting (NSA)
•Logical Object: ENVALRM
A Failure Detected External to the NE alarm occurs because an environmental alarm is present, for example, a door is open or flooding has occurred.
Clear the EXT Alarm
Step 1 In the node view, double-click the AIC or AIC-I 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 the environmental condition.
Step 4 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.75 EXTRA-TRAF-PREEMPT
•Major (MJ), Service Affecting (NSA)
•Logical Object: OCN
An Extra Traffic Preempted alarm occurs on OC-N cards in two-fiber and four-fiber BLSRs 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 checking the Conditions tab.
Step 2 If a ring switch has occurred, clear the ring switch on the working system by following the appropriate alarm in this chapter.
Step 3 If the alarm occurred on a four-fiber BLSR and the span switch occurred on this OC-N, clear the span switch on the working system.
Step 4 If the alarm does not clear, log onto http://www.cisco.com/tac for more information or call TAC to report a service-affecting problem (1-800-553-2447).
2.7.76 FAILTOSW
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: CLIENT, EQPT, OCN
The Failure to Switch to Protection condition occurs when a working electrical (traffic) card cannot switch to the protect card in a 1:N, Y-cable, or splitter protection group, because another working electrical (traffic) 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 DS-N card using the 1:N card protection group. The working DS-N card is reporting an alarm but not reporting a FAILTOSW condition.
Step 2 If the condition does not clear, replace the working electrical (traffic) card that is reporting the higher priority alarm by following the "Physically Replace a Card" procedure. This card is the working electrical card using the 1:N card protection and not reporting FAILTOSW.
Replacing the working electrical 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. Consult the
Cisco ONS 15454 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.77 FAILTOSW-PATH
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Objects: STSMON, VTMON
The Fail to Switch to Protection Path condition occurs when the working path does not switch to the protection path on a path protection. Common causes of the FAILTOSW-PATH alarm include a missing or defective protection card or a lock out set on one of the path protection nodes.
Caution Always use the supplied electrostatic discharge wristband when working with a powered ONS 15454. Plug the wristband cable into the ESD jack located at the lower-right outside edge of the shelf assembly.
Clear the FAILTOSW-PATH Condition in a Path Protection Configuration
Step 1 Look up and clear the higher priority alarm. Clearing this condition frees the standby card and clears the FAILTOSW-PATH condition.
Step 2 If the condition does not clear, replace the active OC-N card that is reporting the higher priority alarm. Complete the "Physically Replace a Card" procedure. Replacing the active OC-N card that is reporting the higher priority alarm allows traffic to revert to the active slot. Reverting frees the standby card, which can then take over traffic from the card reporting the lower priority alarm and the FAILTOSW-PATH condition.
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. Consult the
Cisco ONS 15454 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 onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.78 FAILTOSWR
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
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 actions occurs: a higher priority event, such as an external switch command, the next ring switch succeeds, or the cause of the APS switch (such as the "SD (DS-1, DS-3)" condition on page 2-162 or the "SF (DS-1, DS-3)" condition on page 2-165) clears.
Warning On the OC-192 card, the laser is on when the card is booted and the safety key is in the on position (labeled 1). The port does not have to be in service for the laser to be on. The laser is off when the safety key is off (labeled 0).
Warning Invisible laser radiation might be emitted from the end of the unterminated fiber cable or connector. Do not stare into the beam directly with optical instruments. Viewing the laser output with certain optical instruments (for example, eye loupes, magnifiers, and microscopes) within a distance of 100 mm might pose an eye hazard. Use of controls or adjustments or performance of procedures other than those specified might result in hazardous radiation exposure.
Clear the FAILTOSWR Condition in a Four-Fiber BLSR Configuration
Step 1 Perform the EXERCISE RING command on the reporting card:
a. Click the Provisioning > BLSR 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 the node view, click View > Go to Network View.
Step 3 Look for alarms on OC-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 and click the Maintenance > BLSR tabs.
Step 5 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards are active and in service:
a. Confirm that the OC-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 OC-N port is in service, 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 6 If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.
Step 7 If fiber continuity to the ports is OK, verify that the correct port is in service:
a. Confirm that the OC-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 OC-N port is in service, 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 8 If the correct port is in service, 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 might 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 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 OC-N card's receiver specifications. The "OC-N Card Transmit and Receive Levels" section on page 1-89 lists these specifications.
Step 11 Repeat Steps 6 through 10 for any other ports on the card.
Step 12 If the optical power level for all OC-N cards is within specifications, complete the "Physically Replace a Card" procedure for the protect standby OC-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. Consult the
Cisco ONS 15454 Procedure Guide for information.
Step 13 If the condition does not clear after you replace the BLSR cards on the node one by one, follow
Steps 4 through 12 for each of the nodes in the ring.
Step 14 If the condition does not clear, log onto http://www.cisco.com/tac for more information or call TAC (1-800-553-2447).
2.7.79 FAILTOSWS
•Not Alarmed (NA), Non-Service Affecting (NSA)
•Logical Object: OCN
The Failure to Switch to Protection Span condition signals an APS span switch failure. For a four-fiber BLSR, 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 actions occur: 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-1, DS-3)" condition on page 2-162 or the "SF (DS-1, DS-3)" condition on page 2-165) clears.
Clear the FAILTOSWS Condition
Step 1 Perform the EXERCISE SPAN command on the reporting card:
a. Click the Maintenance > BLSR 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 the node view, click View > Go to Network View.
Step 3 Look for alarms on OC-N cards that make up the ring or span and troubleshoot these alarms.
Step 4 If clearing other alarms does not clear the FAILTOSWS condition, log into the near-end node and click the Maintenance > BLSR tabs.
Step 5 Record the OC-N cards listed under West Line and East Line. Ensure that these OC-N cards are active and in service:
a. Confirm that the OC-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 OC-N port is in service, 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 6 If the OC-N cards are active and in service, verify fiber continuity to the ports on the recorded cards.
Step 7 If fiber continuity to the ports is OK, verify that the correct port is in service:
a. Confirm that the OC-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 OC-N port is in service, double-click the card in CTC to display the card view.
c. Click the Provisioning > Line tabs.
