
432
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S2
Conditions: This symptom may be observed with the following sequence of operation:
1. The router is booted without configuring the ip multicast-routing distributed command.
2. The ip multicast-routing distributed command is configured.
The issue will not be seen if the ip multicast-routing distributed command is present in the startup
configuration when the router is reloaded.
Workaround: Enter the clear ip mds linecard slot- number command.
• CSCsq02883
Symptoms: A device crashes with ACL configurations.
Conditions: The RP will crash when the device is running low on memory or in a highly fragmented
situation if an ACL/ACE is added/deleted.
Workaround: There is no workaround.
• CSCsq08131
Symptoms: Ping packets of 8180 or larger cause sourcing POS linecard/SIP to reload and remain in
a boot state waiting for IPC connection.
Conditions: This symptom is observed with ping packets that are sourced from PRP2 with part
number 800-27058-03.
Workaround: Reload the router.
Further Problem Description: This symptom is observed only on PRP2 with part number
800-27058-03.
• CSCsq09917
Symptoms: A crash occurs when BGP graceful restart is configured.
Conditions: In the following configuration:
ip vrf vfifteen
rd 15:15
import ipv4 unicast map rfifteen
route-target export 150:15
route-target import 150:15
Delete the RD, and then the unicast map, and then the VRF.
Workaround: There is no feasible workaround. Try to avoid doing such an operation as explained
above.
• CSCsq15994
Symptoms: Low CPS may be observed.
Conditions: The symptoms are seen with PPPoA and PPPoE sessions.
Workaround: There is no workaround.
• CSCsq18916
Symptoms: A copy tftp operation failed with a Socket error when the FPD of an SPA was updated
or when the SPA was reloaded, OIRed.
Conditions: This symptom is related to the number of (nnets) non-virtual interfaces on the box.
Depending on that, a number of SPA reloads must be done.
Workaround:
1. Reload the SPA or the router.
Comentarios a estos manuales