Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación

Descargar
Página de 50
 
25
Release Notes for Cisco ONS 15454 Release 4.1.5
OL-6410-01
  Resolved Software Caveats for Release 4.1.5
Resolved Software Caveats for Release 4.1.5
The following items are resolved in Release 4.1.5.
Hardware
DDTS # CSCdv05723 and DDTS # CSCdw37046
DS-3 traffic hits can occur during synchronization changes (frequency offsets applied) on the node's 
timing.  
A specific scenario under which this has been seen involves configurations with multiple nodes 
line-timed off each other in series. If a network configuration has a DS-3 circuit routed over a chain of 
nodes that are line-timed off each other in sequence (more than 1 line-timed “hop”), the DS-3 traffic 
might exhibit errors on timing disturbances applied on the source node.
The other scenario involves an abrupt change in reference frequency between two nodes. This can result 
in test set errors.
This issue is resolved in Release 4.1.
ML-Series Cards
DDTS # CSCdz87944
Error messages indicating “Stuck Ucode” and “MDA_INTERNAL_ERROR” occur when routing 
64-byte VLAN tagged frames at line rate. For VLANs, use bridging instead of routing. This issue is 
resolved in Release 4.0.
DDTS # CSCed31946
An STS-24C circuit with oversubscription (more than 1 GigE of traffic) can incur possible loss of some 
high priority packets (such as VoIP) when using an STS-24C POS circuit between ML-series cards. The 
input error count can be seen in “show int pos.” To avoid this issue, limit total ring traffic to 1 Gbit, or 
upgrade to Maintenance release 4.1.4. This issue is resolved in Release 4.1.4.
DDTS # CSCed13435
When overloading ML-1000 with Gig rate 64 byte traffic in both directions over RPR, traffic in one 
direction might get only about 20% throughput. This occurs only during heavy oversubscription of the 
processing rate of the card, as described above, and only for specific traffic patterns over RPR, where 
RPR circuits are all created from POS 0 to POS 1, and all traffic has even-numbered MAC addresses at 
one end and odd-numbered MAC addresses at the other end. Generally, such heavy packets-per-second 
on a Gig link are not normal network behavior, and so this should not be a traffic affecting issue in a 
deployed network. This issue is resolved in Release 4.1.4.