Specifications

1049
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
Conditions: This symptom is observed on a router that runs Cisco IOS Release 12.3 T when an
application or a CLI command overwrites a file on the disk.
Workaround: Reload the router.
6) Symptoms: A router that runs Cisco IOS Release 12.3 T crashes.
Conditions: This symptom is observed when an application creates or opens a file without the
“O_TRUNC” mode and attempts to delete the file, as in the following example:
show version | append disk0:redirect.out" and issuing
delete disk0:disk0:redirect.out
Workaround: Reload the router and delete the file.
• CSCed67734
Symptoms: Packet processing at the remote end of a link may fail.
Conditions: This symptom is observed when a service policy that includes the set atm-clp command
is enabled on an output interface via the service-policy output command; the platform that links to
this output interface at the remote end drops the packets.
Workaround: Remove the set atm-clp command from the service policy on the output interface.
• CSCed70198
Symptoms: The line protocol may go down.
Conditions: This symptom is observed when Frame Relay fragmentation is enabled on the main
interface.
Workaround: There is no workaround.
• CSCed75108
Symptoms: When an IP VRF is configured on an SDCC interface of a Cisco 10720 router, all MPLS
packets which are to be forwarded through the SDCC interface are instead dropped by the PXF
forwarding engine.
Conditions: This problem is observed when setting up an MPLS-VPN in which the PE-CE interface
is an SDCC interface on the Cisco 10720 router.
Workaround: Disable the PXF forwarding path via the no service pxf command.
Further Problem Description: The forwarding path must deal with MPLS packets that are destined
for the SDCC interface by punting them rather than dropping them.
• CSCed76109
Symptoms: On a Cisco 7500 series that is equipped with Versatile Interface Processors (VIPs) with
ATM port adapters, the ATM PVCs may not come back up after the ATM interface flaps. This occurs
because the interfaces in the VIP do not transmit any packets but still process incoming traffic.
Conditions: This symptom is observed in a dLFIoATM environment in which distributed Class
Based Weighted Fair Queueing (dCBWFQ) is configured on PPPoATM virtual templates.
Workaround: Apply any kind of distributed queueing on any interface or subinterface of the affected
VIP. Doing so triggers all interfaces to start transmitting again, enabling the ATM PVCs to come
back up.
• CSCed78519
Symptoms: SCR continues to filter CLP(0) cells and tag CLP(1) cells when the CLP(0) filter is
removed from the class-map command.
Conditions: This symptom is observed when there are multiple PVCs and when the class map filters
are globally removed.