Troubleshooting guide

19
Release Notes for Cisco ONS 15454 Release 7.0.2
OL-11368-01
Caveats
Step 4 Perform user-initiated manual Y cable switches from CTC.
After a few switchovers, the FC link will go down. SIGLOSS and GFP-CSF alarms are seen on the CTC.
Cisco recommends you provision squelching to be on when interworking with brocade switches. If for
some reason, squelching must be off with brocade switches, Cisco recommends you use a FORCE
command to perform Y cable switches. It is not known when or if this issue will be resolved.
CSCsc55771
When two MXP_MR_10DME cards are interconnected through OC-192/STM-64 cross connects and
traffic is up, if you hard reset one of the MXP_MR_10DME cards, the traffic might fail to recover. To
recover traffic flow, place the client port in OOS,DSBLD state, delete the PPM then recreate it, and
reprovision the port. This issue is resolved in Release 7.2.
CSCsc60472
CTC is not able to discover a TL1 OCHCC circuit provisioned over an ITU-T line card (ITU-T
OC48/STM16 and ITU-T OC192/STM64). This issue can occur when, using the TL1 client interface,
you create the OCHNC layer that will be used by the OCHCC circuit, then create the OCHCC
connections that involve the ITU-T line cards. The result is an OCHNC and two OCHCC partial circuits,
instead of an OCHNC and a single OCHCC complete circuit. This issue will not be resolved.
CSCsc14290
LOW communication between two nodes equipped with TXP-MR-10E and AIC-I cards does not work
with TXP-MR-10E cards in line termination mode, G.709 enabled, GCC present on the trunk port, and
LOW circuits created between the transponders and AIC-I; Cisco recommends that you use EOW
instead. This issue will be resolved in a future release.
CSCsc58941
Trunk ports of the TXPP_MR_2.5G and MXPP_MR_2.5G can be in facility and terminal loopback at
the same time. this can occur if you provision terminal loopback on the protected trunk port after putting
the trunk ports in facility loopback. You can clear this condition by removing loopback provisioning on
the trunk ports. This issue will be resolved in Release 8.0.
CSCeh94567
Setting a Terminal loopback on an MXP-2.5G-10G trunk port causes OTUK alarms.
This can occur under the following conditions.
1. Two MXP-2.5G-10G cards are connected via the trunk ports.
2. The client ports are connected to respective STM16 line cards.
3. SDCC is enabled on the client ports and the line cards' STM16 port.
4. A terminal loopback is set on the MXP-2.5G-10G trunk port.
This terminal loopback causes OTUK-LOF and OTUK-IA alarms to be reported on both MXP-2.5G-10G
trunk ports. This issue will not be resolved.