Guide For 6500 Alarm Troubleshooting
Guide For 6500 Alarm Troubleshooting
The document is signed by the originator, the recipients and the authorizing body to certify that the information
herein is correct and has been accepted by the recipients.
The Issue Number is incremented whenever a change or set of changes is made to the content of the document.
A history table is included to detail the increment and the reason for the change. Whenever a change is made to
the document all authorized recipients will be asked to amend their copy or will be issued with a new copy.
Any previously issued copies of this document are uncontrolled and unauthorized and should be discarded.
Checked and
Version Date Comments Author
Approved By
v1.0 Feb 16, 2020 Draft for Internal review
Disclaimer:
This Method of Procedure (MOP) is specific to this Project, to the included CIENA Product, CIENA Software
Release, and must be executed by a CIENA trained Engineer.
This is a CIENA Controlled Document and CIENA will not be liable if Customer decides to use this Method of
Procedure (MOP) for another Network Reconfiguration that it was not originally designed for.
Equipment alarms
1. Circuit Pack Missing. 2. Circuit Pack Mismatch.
3. Circuit Pack Failed. 4. Inter-card Suspected.
5. Internal Mgmt. Comms Suspected 6. Circuit Pack Upgrade Failed.
7. Software Auto-Upgrade in Progress. 8. Circuit Pack Unknown.
9. Circuit Pack Latch Open. 10. Slot Empty.
Photonic alarms
1. Adjacency Far End Not Discovered. 2. Adjacency Mismatch
3. High Fiber Loss. 4. Duplicate Adjacency Discovered.
5. Fiber Type Manual Provisioning Required. 6. Shutoff Threshold Crossed.
7. Optical Line Failed. 8. Input Loss of Signal.
9. Minimum Gain. 10. Automatic Shutoff.
11. Gauge Threshold Crossing Alert Summary 12. Optical return loss.
13. High Received Span Loss 14. Automatic Power reduction Active.
➢ Resolution: - (!) Identify the Card & module raising the alarm.
➢ (!!) If card is inserted in Mux then need to Perform Warm & Cold Restart to Card (Module).
➢ (!!!) If the alarm persists after 10 minutes then replace the Card & module (Same Pack code).
➢ (V) If the alarm does not clear, contact your next level of support.
2. Circuit Pack Mismatch: - This alarm is raised When the physical inventory in a shelf do not match the
provisioned part number, a mismatch icon appears in the Equipment and Facility Provisioning and Shelf
Level View applications in Site Manager.
➢ Resolution: - (!) Identify the Card & module raising the alarm.
➢ (!!) Select Inventory from the Equipment & Facility Provisioning Configuration menu.
➢ (!!!) Path: - Go to Configuration →Equipment & Facility Provisioning →Than Select Inventory.
➢ (!V) Mismatched modules can be the same type, but have different PECs. In these cases, ensure PECs match or an
incorrect module is installed.
➢ (V) If you have identified the mismatched, Then Replace the mismatched Card & module.
➢ (V!) If the alarm clears, the module you identified and If the alarm does not clear, contact your next level of support.
➢ Resolution: - (!) Identify the Card & module raising the alarm.
➢ (!!) Card physically Jack out & Properly Jack in. (!!!) Perform Warm Restart to Card. (!V) Perform Cold Restart to
Card.
➢ (!!!) Path for Cold Restart: - Ne Login →Fault →Restart →Select Card →Select Warm or Cold →OK
➢ (!V) If the alarm persists after 10 minutes then replace the Card & module (Same Pack code).
➢ (V) If the alarm does not clear, contact your next level of support.
4. Intercard Suspected: - This alarm is raised when a data path or communications path fault is detected
within the product, but the fault is unable to be isolated to a specific interface module or backplane.
Because the fault cannot be isolated to a specific interface module, the alarm will be raised against more
than one interface module. Examples are:
• An interface module that has a loss of traffic or degraded signal integrity on a backplane link which
interfaces to another interface module in the shelf. The alarm would be raised against both interface
modules.
5. Internal Mgmt Comms Suspected: - This alarm is raised when the communication channel failure
between two modules is suspected. The alarm is raised against both modules suspected of being the cause
of the failure.
6. Circuit Pack Upgrade Failed: - This alarm is raised against a circuit pack when the upgrade process of the
circuit pack fails.
➢ Resolution: - (!) Identify the pluggable module raising the alarm
➢ (!!)Check the upgrade state of all the circuit packs from Site Manager or check the software version and clear
software upgrade is done.
➢ (!!!) Card physically Jack out & Properly Jack in.
➢ (!V) Perform Warm Restart to Card & Perform Cold Restart to Card
➢ (V) Path: - Ne Login →Fault →Restart →Select Card →Select Warm or Cold →OK.
7. Software Auto-Upgrade in Progress: - This alarm is raised if a newly inserted module is being auto-
upgraded/downgraded to the active software release of the network element.
➢ Resolution: - (!) Wait for the auto-upgrade of the module to complete. & The auto-upgrade of the module can take
up to 10 minutes.
➢ (!!) If the alarm persists after 10 minutes then Card physically Jack out & Properly Jack in.
➢ (!!!) If the original alarm has cleared then the procedure is complete.
➢ (!V) If the alarm does not clear, contact your next level of support.
8. Circuit Pack Unknown: - This alarm is raised When the on-board processor of a circuit pack cannot
communicate with the CTM after you insert the circuit pack into the shelf & When an unknown circuit pack
is inserted into an un-provisioned slot.
9. Circuit Pack Latch Open: - This alarm is raised when the bottom/lower locking lever on the module is not
fully closed and the module is inserted into a slot, or the latch on the module is broken.
10. Slot Empty: - This alarm is raised when an un-provisioned or out-of-service slot is empty.
➢ Resolution: - (!) Using the network planning diagram (SFD), verify if the Expected far-end address adjacency
parameter is correct.
➢ (!!) Edit the Expected far-end address and Expected far-end address format adjacency parameters so that they
match the Actual far-end address and Actual far-end address Format listed for the ADJ-LINE facility.
➢ Path: - Go to Configuration →Equipment facility provisioning →Select Direction respective card →Select Facility
type choose ADJ →fiber- Select slot & Port for Adjacency.
3. High Fiber Loss: - This alarm is raised against the originating ADJ-FIBER facility when the measured loss
between this port and the far-end port is greater than either of the provisioned loss thresholds. A 0.5 dB
hysteresis is also applied, which prevents the alarm from clearing until the measured loss has gone below
the threshold(s) by more than 0.5 dB. The calculated fiber loss is reported against the ADJ-FIBER facility.
➢ Resolution: - (!) Check High Fiber Loss alarm (all fibers between the port where the alarm is raised and the port
specified as the Far End Address for this adjacency).
➢ (!!) Check that the LC-LC cable is connected properly to the FIM or Far End connector, Check that the loopback
connector is connected properly.
➢ (!!!) If the alarm did not clear five minutes after insertion of the fiber, clean the LC-LC cables between the Amplifier
and the WSS on both ends.
➢ (!V) If the alarm did not clear than Clean the Equipment port and replace the LC-LC Cable and check again alarm.
➢ (V) after complete troubleshooting please check HFL on ADJ fiber.
➢ Path: - Go to Configuration →Equipment facility provisioning →Select Direction respective card →Select Facility
type choose ADJ →fiber →Select slot & Port.
5. Fiber Type Manual Provisioning Required: - This alarm is raised against an ADJ-LINE facility when the
fiber type for the line adjacency is set to ‘Unknown fiber type’ (not provisioned), putting the line adjacency
out of service.
➢ Resolution: - (!) Provision the Fiber Type value of the alarmed line adjacency to a value other than ‘Unknown fiber
type’.
➢ (!!) Go to Configuration →Equipment facility provisioning →Select Direction Amplifier card →Select Facility type
choose ADJ-LINE →Select NDSF fiber and ok.
6. Shutoff Threshold Crossed: - This alarm is raised against an AMP facility when the total input optical
power to the amplifier has fallen below the provisioned Shutoff Threshold level. Or A disconnected fiber,
A pinched fiber connection, A dirty optical fiber connector.
7. Optical Line Failed: - This alarm is usually raised when there is a fiber break or an intermediate
connector disconnect between neighboring sites. And the alarm is raised against AMP facilities optically
downstream of the fiber cut/disconnect.
➢ Resolution: - (!) In the Facility Type drop-down box, select “ADJ-LINE”. Record the node name (TID) reported for
the “Actual Far-End Address” of this facility. This is the neighboring (upstream) node.
➢ (!!) Use a separate power source and power meter to measure the loss between the fiber plant ingress and port 8 of
the AMP.
➢ (!!!) Check the fiber connection manually at the downstream node. At the downstream node, systematically clean
each optical connection between the fiber plant egress/patch panel towards port 8 of the AMP showing the OLF
alarm. Replace any obviously damaged patch cords.
8. Input Loss of Signal: - This alarm is raised against an AMP facility when the total input optical power to
the amplifier has fallen below the provisioned input LOS threshold level, And a disconnected fiber, a dirty
optical fiber connector at the receiver or adjacent transmitter, a failure of the transmitting laser at the
adjacent Tx.
9. Minimum Gain: - This alarm is raised when the actual span loss is less than designed value.
➢ (V!!) Path: - Go to Configuration →Equipment facility provisioning →Select Direction Amplifier card →Select
Facility type choose ADJ-LINE → Click Edit open will new window →Select Target Span loss →Put the target value
according to LDT and ok.
10. Automatic Shutoff: - This alarm is raised against an AMP facility when an ALSO condition is triggered, and
is raised against any amplifier that has been shut off. An ALSO condition is cleared when the OSC receives a
clean signal from an upstream network element.
➢ Resolution: - (!) In the Facility Type drop-down box, select “ADJ-LINE”. Record the node name (TID) reported for
the “Actual Far-End Address” of this facility. This is the neighboring (upstream) node.
➢ (!!) Use a separate power source and power meter to measure the loss between the fiber plant ingress and port 8 of
the AMP.
➢ (!!!) Check the fiber connection manually at the downstream node. At the downstream node, systematically clean
each optical connection between the fiber plant egress/patch panel towards port 8 of the AMP showing the OLF
alarm. Replace any obviously damaged patch cords.
➢ (!V) Check the fiber connections at the upstream node. At the upstream node, systematically clean each optical
connection between port 5 of the AMP showing the Automatic Shutoff alarm and the fiber plant ingress / patch
panel. Replace any obviously damaged patch cords.
➢ Verify if the alarm has cleared. If the alarm does not clear and the special case above has been ruled out, contact
your next level of support or your Ciena tech team.
➢ Resolution: - (!) If this alarm was raised as a result of a maintenance activity Window or during activity and it is
expected no action is required.
➢ (!!) The alarm will clear when the maintenance activity or SLAT is completed.
➢ (!!!) Verify that the PM threshold values for the alarmed facility are correctly provisioned. Adjust the value if
required).
➢ (!V)If the alarm does not clear, contact your next level of support.
12. Optical return loss: - The ORL alarm is raised against the input or Line A output port of an AMP facility.
The ORL condition is caused by a reflection somewhere downstream from the AMP facility.
➢ This reflection can be caused by: - Dirty optical connectors (2) Improper optical cable mating (3) A
disconnected optical fiber at the amplifier output (4)A degraded optical fiber.
➢ (V!) After alarm confirm then Ensure that all LC/SC connectors located after the amplifier output are properly
mated. Verify this on both ends of the connector-mating.
13. High Received Span Loss: - This alarm is raised when the actual span loss is higher than designed value
➢ (V) If actual span loss is higher than designed value than next step.
➢ (V!) Disconnect the Direction Input fiber of the alarmed optical amplifier, and clean the output fiber and connectors
at the amplifier, then reconnect the fiber and check Span loss again.
➢ (V!!) If the alarm does not clear after Clean patch cord & connector, then replace the Fiber cable.
➢ (V!!!) Please check again actual span loss & If alarm still not clear than please check Far End Site Transmit power.
➢ (!X) If Far END site transmit power is not ok than replace fiber cable and check Near END Span loss.
➢ (X) If alarm is cleared then procedure is completed.
➢ (X!) If the alarm does not clear, contact your next level of support Ciena group.
14. Automatic Power reduction Active: - The APR alarm is raised against the input or Line A output port of
an AMP facility. The APR condition is caused by a reflection somewhere downstream from the AMP facility.
➢ This reflection can be caused by: - Dirty optical connectors (2) Improper optical cable mating (3) A
disconnected optical fiber at the amplifier output (4)A degraded optical fiber.
➢ (V!) After alarm confirm then Ensure that all LC/SC connectors located after the amplifier output are properly
mated. Verify this on both ends of the connector-mating.
➢ (V!!) Disconnect the output fiber of the alarmed optical amplifier, clean the output fiber and connectors at the
amplifier, then reconnect the fiber and check PM.
➢ (!X) If the alarm does not clear after Clean patch cord & connector, Then replace the Fiber cable.
➢ (X) Please go to Performance monitoring and check again, ORL value is up to 23dB
than alarm is cleared.
© Copyright Ciena
© Copyright 2019.
Ciena All All
2019. Rights Reserved.
Rights Reserved.
The information
The information contained
contained herein
hereinis the property
is the propertyof Ciena and
of Ciena is strictly
and confidential.
is strictly confidential. Except
Except as as
expressly
expresslyauthorized in writing
authorized by by
in writing
Ciena, thethe
Ciena, holder
holdershall keep
shall keepall all
information
information contained
containedherein confidential,
herein shall
confidential, disclose
shall it only
disclose to its
it only employees
to its employees with a need
with to know,
a need to know,andand
shall
shall
protect it, in
protect it, whole
in whole or in
or part, from
in part, fromdisclosure andand
disclosure dissemination to third
dissemination parties
to third with
parties thethe
with same samedegree
degree of care it uses
of care to protect
it uses its its
to protect own own
Confidential
Confidential Information,
Information, butbut
withthnonoless
lessthan
thanreasonable
reasonablecare.
care.Except
Exceptas asexpressly
expresslyauthorized
authorizedininwriting
writingbybyCiena,
Ciena,the theholder
holderisisgranted
grantednono
rights to use
rights to use thethe
information
information contained
contained herein.
herein.