Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación
9
Release Notes for Cisco ONS 15454 Release 4.0.1
OL-4470-01
Caveats
4.
6c, six STS-1s
5.
3c, 3c, 3c, 3c
6.
3c, 3c, six STS-1s
7.
Twelve STS-1s
When configuring scenario 3, the STS-6c must be provisioned before either of the STS-3c circuits.
Multicard EtherSwitch
When deleting and recreating Ethernet circuits that have different sizes, you must delete all STS circuits
provisioned to the EtherSwitch before you create the new circuit scenario. (See the preceding
provisioned to the EtherSwitch before you create the new circuit scenario. (See the preceding
front ports so that the VLANs for the ports are carried by the largest circuit first. A safe approach is to
enable the front port before you create any circuits and then retain the front port VLAN assignment
afterwards. If you break the rules when creating a circuit, or if you have to delete circuits and recreate
them again, delete all circuits and start over with the largest first.
enable the front port before you create any circuits and then retain the front port VLAN assignment
afterwards. If you break the rules when creating a circuit, or if you have to delete circuits and recreate
them again, delete all circuits and start over with the largest first.
DDTS # CSCds02031 E1000-2/E100
Whenever you drop two 3c multicard EtherSwitch circuits onto an Ethernet card and delete only the first
circuit, you should not provision STS-1 circuits to the card without first deleting the remaining STS-3c
circuit. If you attempt to create an STS-1 circuit after deleting the first STS-3c circuit, the STS-1 circuit
will not work and no alarms will indicate this condition. To avoid a failed STS-1 circuit, delete the
second STS-3c prior to creating any STS-1 circuit.
circuit, you should not provision STS-1 circuits to the card without first deleting the remaining STS-3c
circuit. If you attempt to create an STS-1 circuit after deleting the first STS-3c circuit, the STS-1 circuit
will not work and no alarms will indicate this condition. To avoid a failed STS-1 circuit, delete the
second STS-3c prior to creating any STS-1 circuit.
ML-Series
DDTS # CSCdy31775
Packets discarded due to output queue congestion are not included in any discard count. This occurs
under either of the following conditions:
under either of the following conditions:
•
Traffic on ML-series cards between Ethernet and SONET ports, with oversubscription of available
circuit bandwidth configured, leading to output queue congestion.
circuit bandwidth configured, leading to output queue congestion.
•
Traffic from SONET 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.
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.
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.