Troubleshooting guide

6
Release Notes for Cisco ONS 15454 Release 7.0.2
OL-11368-01
Caveats
CSCdu82934
When you auto-route a VT circuit on an ONS 15454 node, a path is computed based on the availability
of STSs on the nodes involved. This selection process, when combined with a lack of VT matrix (or
STS-VT connections) on an auto-route selected node, can result in the VT circuit creation failing with
the message “unable to create connection object at node.” To correct this situation, manually route VT
circuits in cases when auto-routing fails. The error message will indicate which node is at issue.
CSCef28522
When you inject errors on a splitter protection card in the node's working port, CVL and ESL are
incremented for the working and protect far end ports. This issue will not be resolved.
CSCuk49106
The amplifier gain set point shown by CTC and the actual measured amplifier gain differ. The following
steps illustrate this issue.
Step 1 Reduce the insertion loss of the span just before the amplifier.
Step 2 Execute the APC procedure.
The APC procedure does not check consistency between the gain set point and the real gain, but rather
only verifies the amplifier total output power. As a workaround, manual setting can be performed to align
these values, although the discrepancy does not impact the normal functioning of the amplifier. This
issue will not be resolved.
CSCef05162
Clearing the displayed statistics for a port will also clear the displayed history for that port. Clearing the
displayed statistics for all ports will also clear the displayed history for all ports. There is no warning
message from the TCC2. If History information is to be retained, do not clear displayed statistics for any
port without first documenting the displayed history information for the associated port. This issue will
not be resolved.
CSCef29516
The ALS pulse recovery minimum value is 60 instead of 100. If this occurs, increase the value to 100.
This issue will not be resolved.
CSCeb36749
In a Y-Cable configuration, if you remove the client standby RX fiber; a non-service affecting LOS is
raised, as expected. However, if you then remove the trunk active RX fiber; a non-service affecting
LOS-P is raised, but the previously non-service affecting LOS on the client port is now escalated to a
service affecting alarm, in spite of no traffic having been affected. This issue will not be resolved.