Datasheet

118
Release Notes for Cisco IOS Release 12.1E on the Catalyst 6500 and Cisco 7600 Supervisor Engine and MSFC
OL-2310-11
Limitations and Restrictions
OSM Limitations and Restrictions
• If you use the Class-Based Weighted Fair Queueing (CBWFQ) shape average command and apply
the configured policy map to an interface on an OSM, traffic-shaping accuracy cannot be guaranteed
if the target bit rate specified is less than 256,000 bits per second. (CSCea06515)
• For the OC-12 ATM OSM, the Common Part Convergence Sub-layer User-to-User (CPCS-UU) field
in the AAL5 CPCS PDU cannot be set, cleared, or transported correctly. This affects custom use of
the field as well as FRF8.1, which uses the CPCS-UU byte to transport the Frame Relay command
response bit. This is a hardware issue that affects all releases. There is no workaround.
(CSCeb36223)
• The PFC2 QoS police command and the PXF-based set command are both used to set IP precedence.
However, when you configure the set ip prec command for an OSM VPN path, the mls qos command
is ignored. (CSCdw83517)
• The Gigabit Ethernet WAN ports on the OSM-4GE-WAN-GBIC and OSM-2+4GE-WAN+
switching modules do not support traffic in the native VLAN of an IEEE 802.1Q trunk. Do not
configure a subinterface with the encapsulation dot1q vlan_id native command. (CSCdx60011)
• When you upgrade from OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, the existing
configuration will not be saved and applied to the new OSM-2+4GE-WAN+. To save your
configuration when upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, perform
this task:
1. Enter the write memory command before removing the OSM-4GE-WAN-GBIC
2. Install the new OSM-2+4GE-WAN+
3. Enter the copy startup-config running-config command
4. Enter the write memory command
(CSCdz80308)
• When you apply the first policy map or remove the last policy map from an interface on an
OSM-1OC48-POS-SS,-SI, -SL module traffic through the interface may be disrupted and the
routing protocol may go up and down. (CSCdx94033)
• The channelized OSMs are not supported in the MPLS core. They support IP traffic on customer
edge (CE) and provider edge (PE) router links only.
• Unless you enter the mls qos command to enable PFC QoS, when you enable MPLS and enter the
random-detect command in the output policy map on an interface, all OSM traffic through the
interface is marked with DSCP 0. (CSCdw79863)
• The OSMs are supported only in systems with a Supervisor Engine 2.
• If you enter an input set command to modify IP precedence for an IP-to-Tag path, the MPLS
experimental bits will continue to be derived from the prior IP-precedence setting. In order to
modify the experimental bits, use the set mpls exp command on the ingress interface.
(CSCdw66785)
Service Module Limitations and Restrictions
• When the NAM is configured as the NDE destination and the NAM is down, the NDE traffic is
flooded.
Workaround: Clear the NDE configuration for the NAM or enter the clear arp-cache command.
(CSCdy55261)