Specifications

1339
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S2
Also, it is observed that the controller is reset when the following is removed/reapplied:
rx-cos-slot all ToFabTable
!
slot-table-cos ToFabTable
destination-slot 0 OC3
destination-slot 1 GIGE
Conditions: This symptom is observed on a Cisco 12000 series router.
Workaround: Perform the following steps:
1. Remove the RED configuration.
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).
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.
• 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.
• CSCed66160
Symptoms: A Cisco router crashes while verifying if FRR is active at Backup Head.
Conditions: A show display of a large number of FRR Active LSPs (Label Switched Paths) issued
by the show mpls traff fast database int xx command was paused before completing when one of
the LSPs was deleted by an external event. When the display was resumed, the deallocated LSP was
referenced by the show display causing the router to crash.
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.
• CSCed69722
Symptoms: When a recursively resolved adjacency is “discard” (e.g., null0), a packet that is entering
an Engine 3 4-port GE line card and that is destined to the “discard” adjacency is punted to the local
line card CPU, causing high CPU utilization. Punting to the CPU is caused by a wrong adjacency
that is populated for the corresponding route.