2-230
Cisco ONS 15454 Troubleshooting Guide, R8.5
November 2009
Chapter 2 Alarm Troubleshooting
2.7.381 SQUELCHED
In an example situation, an upstream MXP_2.5G_10G client port receive experiences a “loss of light,”
and this port raises CARLOSS, SIGLOSS, or LOS (determined by the payload type) locally. The port
also sends client signal fail to its downstream card. The downstream card raises a “GFP-CSF” alarm on
page 2-117, turns off the client transmit laser, and raises the SQUELCHED condition.
The local client raises SQUELCHED if it also raises one of the following alarms for the client, all of
which are signalled by the upstream node:
• 2.7.151 GFP-CSF, page 2-117
• 2.7.154 GFP-LFD, page 2-119
• 2.7.155 GFP-NO-BUFFERS, page 2-119
• 2.7.152 GFP-DE-MISMATCH, page 2-117
• 2.7.153 GFP-EX-MISMATCH, page 2-118
• 2.7.288 ODUK-1-AIS-PM, page 2-189
• 2.7.289 ODUK-2-AIS-PM, page 2-189
• 2.7.290 ODUK-3-AIS-PM, page 2-189
• 2.7.291 ODUK-4-AIS-PM, page 2-189
On the MXP_MR_10G, the local client raises a SQUELCHED condition if the upstream client detects
one of the following alarms. Note that no corresponding local alarm is raised to indicate which of these
conditions is present upstream.
• LOS for the clients including the “LOS (2R)” alarm on page 2-157, the “LOS (ESCON)” alarm on
page 2-163, and the “LOS (ISC)” alarm on page 2-164
• CARLOSS for the clients including the “CARLOSS (FC)” alarm on page 2-62, the “CARLOSS
(GE)” alarm on page 2-65, and the “CARLOSS (ISC)” alarm on page 2-65.
The local client raises a SQUELCHED condition if the local trunk raises one of the following alarms:
• 2.7.307 OTUK-AIS, page 2-192
• 2.7.310 OTUK-LOF, page 2-192
• 2.7.228 LOS (TRUNK), page 2-166
• 2.7.313 OTUK-TIM, page 2-192 (squelching enabled)
• 2.7.292 ODUK-AIS-PM, page 2-189
• 2.7.294 ODUK-LCK-PM, page 2-189
• 2.7.298 ODUK-TIM-PM, page 2-190 (squelching enabled)
• 2.7.413 TIM, page 2-244 (for the OC-N, squelching enabled)
• 2.7.205 LOF (OCN), page 2-151
• 2.7.226 LOS (OCN), page 2-164
• 2.7.58 CARLOSS (TRUNK), page 2-66
• 2.7.444 WVL-MISMATCH, page 2-259 (client or trunk)
When troubleshooting the SQUELCHED condition locally, look for failures progressing upstream in the
following order. (If you are troubleshooting this alarm remotely, reverse the order of progress.)
• Local client alarms, as above
• Local trunk alarms, as above
• Remote (upstream) client receive alarms, as above
To Next Page
Loading...
