Release Notes

11
Release Notes for Cisco ONS 15454 SDH Release 4.1.3
OL-4984-01
Caveats
DDTS # CSCea36829
The broadcast packet count is always 0 for the SPR interface. The ML100 and ML1000 hardware does
not support counting broadcast packets. This issue will not be resolved.
DDTS # CSCeb21996
When the POS interface is removed from SPR due to a defect, while SPR is configured in immediate
mode, the defect type may not be reported. This only occurs if the defect is set and clears in less then 50
ms.
DDTS # CSCdy31775
Packets discarded due to output queue congestion are not included in any discard count. This occurs
under either of the following conditions:
• Traffic on ML-series cards between Ethernet and SDH ports, with oversubscription of available
circuit bandwidth configured, leading to output queue congestion.
• Traffic from SDH to Ethernet, with oversubscription of the available Ethernet bandwidth.
This issue will be resolved in a future release.
DDTS # CSCdz49700
ML-series cards do not appear in the Cisco Discovery Protocol (CDP) adjacencies and do not participate
in the Spanning-Tree Protocol. All packets are counted as multicast.
The ML-series cards always forward Dynamic Trunking protocol (DTP) packets between connected
devices. If DTP is enabled on connected devices (which might be the default), DTP might negotiate
parameters, such as ISL, that are not supported by the ML-series cards. All packets on a link negotiated
to use ISL are always counted as multicast packets by the ML-series card, and STP and CDP packets are
bridged between connected devices using ISL without being processed. To avoid this issue, disable DTP
and ISL on connected devices. This functionality is as designed.
DDTS # CSCdz68649
Under certain conditions, the flow-control status may indicate that flow control is functioning, when it
is not. Flow-control on the ML-series cards only functions when a port-level policer is configured. A
port-level policer is a policer on the default and only class of an input policy-map. Flow-control also only
functions to limit the source rate to the configured policer discard rate, it does not prevent packet
discards due to output queue congestion.
Therefore, if a port-level policer is not configured, or if output queue congestion is occurring, policing
does not function. However, it might still mistakenly display as enabled under these conditions. To avoid
this issue, configure a port-level policer and prevent output queue congestion. This issue will be resolved
in a future release.
DDTS # CSCdz69700
Issuing a shutdown/no shutdown command sequence on an ML1000 port clears the counters. This is a
normal part of the startup process and there are no plans to change this functionality.