Specifications

1233
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S
Step 1) Remove the RED configuration.
Step 2) Reload microcode onto the line card (a 2-port OC-3 channelized to DS1/E1 line card or a
6-port channelized T3 line card).
Step 3) Reapply the RED configuration.
• CSCed65027
Symptoms: When the MTU is toggled from 4470 to 9180 or 64, a 4xOC12 ATM line card may enter
the “ERR CARV” state and does not recover. Even reloading the line card does not bring it back up.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of
Cisco IOS Release 12.0 S.
Workaround: Reload the router.
• CSCed65584
Symptoms: A VIP or FlexWAN may reload.
Conditions: This symptom is observed on a Cisco 7500 series or Cisco 7600 series when a service
policy is attached to a multilink Frame Relay interface.
Workaround: There is no workaround.
• CSCed66001
Symptoms: A %LINK-4-TOOBIG error message may appear on the console log of a Cisco 10000
series.
Conditions: This symptom is observed when you send a ping or an L2TP packet across an MPLS
interface that is configured for label imposition.
Workaround: There is no workaround.
• CSCed66388
Symptoms: A 4-port OC-12 ISE ATM card may crash when an L3 PVC is configured on a main
interface, a service policy is attached to the L3 PVC, and there are F4 OAM VCs on the same the
main interface. F4-OAM VCs are created when there are VP tunnels or layer 2 VPs that perform cell
relay/cell packing.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(27)S.
Workaround: There is no workaround.
• CSCed68376
Symptoms: A router may enter a processing loop. This results in CPUHOG messages and may cause
the router to reload.
Conditions: This symptom is observed under some error conditions that are associated with
configuring L2TPv3 tunnels (when the xconnect command is enabled).
Workaround: There is no workaround.
• CSCed68763
Symptoms: Engine 2 line cards may fail upon clearing BGP peers.
Conditions: This symptom is observed on a Cisco 12000 series router that is running Cisco IOS
Release 12.0(27)S.
Workaround: There is no workaround.