Troubleshooting guide

18
Release Notes for Cisco ONS 15454 Release 7.0.2
OL-11368-01
Caveats
CSCsb79548
A long traffic hit can occur when an active TCC2/TCC2P resets while an MXP_MR_10DME-C or
MXP_MR_10DME-L card is rebooting.
This issue can be reproduced as follows:
Step 1 1. Set up two MXP_MR_10DME-C or MXP_MR_10DME-L cards, connected back-to-back in two
different nodes, A and B.
Step 2 2. Ensure that Node A has two TCC2 cards; one is active, and the other is standby.
Step 3 3. Set up any kind of traffic between the two MXP_MR_10DME-C or MXP_MR_10DME-L cards.
Step 4 4. Soft reset the MXP_MR_10DME card in Node A, then soft reset the active TCC2/TCC2P.
OTUk/ODUk-SD, FEC Uncorrected word alarms are raised on the trunk port. Traffic goes down and
does not recover until the MXP_MR_10DME card is able to come up. It is not known when or if this
issue will be resolved.
CSCsb94736
After a fault condition (trunk LOS or Y-cable switch) an MXP_MR_10DME card might fail to detect the
login message and traffic might not start for some minutes (after multiple login trials). This can occur in
an N-F configuration with MDS switch and MXP_MR_10DME distance extension on, where test
equipment traffic is set to 2G Fibre channel (FC) full bandwidth occupancy and started. Stop traffic or
keep bandwidth occupancy below 80% during the login phase to work around this issue. This issue will
not be resolved.
CSCsb95918
All GFP related alarms are raised with their active severities on the standby card after a Y-Cable
protection switch. When a DWDM card (with GFP support) in a Y-Cable protection group becomes
standby as a result of a Y-Cable protection switch, the GFP alarms raised when the card was active retain
their severities instead of assuming standby severities. The alarms can be seen in the alarm pane if not
suppressed, or in the condition pane if suppressed. This issue will be resolved in a future release.
CSCsc36494
Manual Y cable switches with squelching turned off can cause a Fibre channel link with brocade
switches to go down.
This issue can be reproduced as follows:
Step 1 Set up MXP_MR_10DME cards so that they are Y cable protected. Squelching is provisioned to be off.
Distance extension is turned on.
Step 2 The path between the working pair of Y cable protected cards, has no distance introduced. But the
protect path has a delay of 800 km introduced.
Step 3 Start Fibre channel traffic with brocade switches.