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

During an upgrade, all ML-series cards are reset at the same time. This can result in a lengthy disruption 
to local traffic. This issue will be resolved in a future release, in which the upgrade will be altered to 
reset ML cards one at a time, so that L2/L3 protection can be used to minimize loss of local add/drop 
traffic during node upgrade.

If you configure Fast EtherChannel and POS-channel in the same bridge group, during system boot, the 
Fast EtherChannel or POS-channel configuration may be lost and following error message displayed:

Interface FastEthernet1 is attempting to join Port-channel1. But Port-channel1 

belongs to bridge-group 1 which has another FE(C) member in it. FEC + FE(C) is not 

allowed in the same bridge group. Please change your configuration and retry.

This issue will be resolved in a future release.

An unexpected card reload can occur when a card is configured to route IP-Multicast traffic and 
subsequently sends IP-Multicast frames larger than 1649 bytes. To prevent this, avoid routing 
IP-Multicast frames larger than 1649 bytes. This issue is under investigation.

When configuring the same static route over two or more interfaces, use the following command:

ip route a-prefix a-networkmask a.b.c.d

Where a.b.c.d is the address of the outgoing gateway, or, similarly, use the command:

ip route vrf vrf-name

Do not try to configure this type of static route using only the interface instead of the address of the 
outgoing gateway in Release 4.0.x. This issue will be resolved in a future release.

If no BGP session comes up when VRF is configured and all interfaces have VRF enabled ensure that at 
least one IP interface (without VRF) is configured and add an IP loopback interface on each node. This 
issue will be resolved in a future release.

POS ingress classification based on IP precedence does not match the packets when inbound policy map 
classifying based on IP precedence is applied to the POS interface, which is configured for HDLC or 
PPP encapsulation. To avoid this issue, use LEX encapsulation (default) or, at the Ethernet ingress point, 
mark the COS based on an IP precedence classification, then classify based on the COS during POS 
ingress. This issue will be resolved in a future release.