Specifications

1234
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S
• CSCed69546
Symptoms: When mixed channels are defined on a channelized OC-12 line card and these channels
include DS3s, T1s, an DS0s, CEF/RIB inconsistency may occur, preventing traffic to be sent over
the correct interfaces.
Conditions: This symptom is observed on a Cisco 10000 series.
Workaround: When you delete interfaces or subinterfaces on the channelized OC-12 line card,
ensure that the adjacency for the deleted interface is deleted before you configuring a new interface.
This can be checked by entering the show adjacency or show adjacency | include interface name
command. When the adjacency no longer appears in the output of the show adjacency command,
it is safe to add new interfaces.
Note that the show adjacency type number command cannot be used to get the required information.
When deleting large numbers of interfaces, a delay of about 2 minutes should be enough to ensure
that all of the adjacencies have been deleted.
• 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.
Conditions: This symptom is observed on Engine 3 line cards that are installed in a Cisco 12000
series that runs Cisco IOS Release 12.0(25)S1 or a later release.
Workaround: There is no workaround.
• CSCed70822
Symptoms: With four fabric cards (one CSC in slot 16 and three SFCs), after a power cycle, the line
cards fail to come up and fabric ping timeouts occur.
Conditions: This symptom is observed on a Cisco 12000 series and affects all E4 and E4+ cards.
Workaround: Place a CSC card in slot 17. The fix for this caveat applies to all types of line cards
(E0, E2, E3, E4 and E4+).
• CSCed71467
This caveat consists of two symptoms, two conditions, and two workarounds:
Symptom 1: When a policy map is applied under an L2VPN (AToM: CRoMPLS) ATM PVC on a
Cisco 12000 series Engine 3 ATM card, it is not possible to get class-map or policy-map statistics.
When you enter the show policy map interface command, the following message is seen:
Class statistics not available.
This message is seen on a policy map without policing, and in this specific case, the policy map uses
a class-default match and sets the MPLS EXP bits.
Condition 1: This problem is seen when a policy map that does not include any policing is applied
to a Cisco 12000 series Engine 3 ATM line card that is configured for AToM/L2VPN.
Workaround 1: Enable policing to get the policy-map and class-map statistics.
Symptom 2: If a policy map that involves policing is applied L2VPN (AToM: CRoMPLS) ATM PVC
on a Cisco 12000 series Engine 3 ATM card, the policy-map statistics are available but the following
incorrect message shows up at the top of the output of the show policy map interface command:
NOTE: Statistics are aggregated for all the VC’s in the subinterface