Troubleshooting guide

Release Notes for Cisco ONS 15454 Release 7.0.2

OL-11368-01

Caveats

CSCdz74432

Issuing a “clear IP route *” command can result in high CPU utilization, causing other processes to be

delayed in their execution. To avoid this issue do not clear a large number of route table entries at once,

or, if you must use the “clear IP route *” command, do not install more than 5000 EIGRP network routes.

DWDM Cards

CSCse47817

When you attempt to change the MinExpSpan or MaxExpSpan values the wrong error message might be

displayed as follows:

“EID-6151” the Min Span loss must be less than the max loss

This message appears even if the measured value is in the correct range. This issue is resolved in

Releases 7.0.2 and 8.0.

CSCse41468

The GE interface remains down on a switch connected to an MXP_MR_2.5G card. This can occur during

failure recovery with AUTO NEGOTIATION enabled on a connected switch. To work around this issue

disable AUTO NEGOTIATION or set sync-restart-delay 10000 on the port of the switch. This issue will

not be resolved.

CSCeh22604

When an MXP_MR_2.5G card is in MIXED or ESCON mode, TCA and alarm optical thresholds of Tx

power for laser bias are configurable for ESCON payload, though not supported. This issue will be

resolved in the future release.

CSCei19148

When a port is placed in-service while the conditions necessary to squelch the port are present, as in

when the trunk port on a DWDM card is OOS,DSBLD and a client port is placed in-service, the client

will momentarily enable, emitting light, before squelching due to the trunk OOS,DSBLD condition. The

pulse is approximately 500 ms. This issue will not be resolved.

CSCei87554

When using a 1GE payload over the TXP_MR_2.5G the IfInErrors counter does not report oversized,

undersized, or CRC errored frames, but rather, reports frame coding only. This issue will not be resolved.

CSCsb47323

For MXP_MR_10DME-C and MXP_MR_10DME-L cards, an unexpected RFI condition might be

raised along with an OTUk-BDI. When there is an LOS downstream, the node receives OTUk-BDI.

Because of the placement of dual OTN and SONET wrappers, it can also receive an RFI. This issue will

not be resolved.