
368
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S8
Conditions: This symptom is observed on an ISE ATM LC that is running Cisco IOS
Release 12.0(32)SY11.
Workaround: Stop any excessive interface flapping to prevent the encapsulation table from filling
up. If it is full, a microcode reload of the affected LC will clear the table.
• CSCth95192
Symptoms: On a Cisco router loaded with Cisco IOS Release 12.0(33)S6, when LSP changes, the
CEF table may become stuck with old label information.
Conditions: This symptom occurs when there are two outgoing links to the BGP next hop for the
prefix received via BGP.
The following is a snapshot of how the CEF table will be during the time of the issue:
R1# show ip cef 10.150.150.150 detail
10.150.150.150/32, version 26, epoch 0, cached adjacency 10.1.15.5 0 packets, 0 bytes
tag information from 10.100.100.0/30, shared, all rewrites owned local tag: 33 fast
tag rewrite with Et0/0.12, 10.1.1.1, tags imposed {16} via 10.100.100.2, 0
dependencies, recursive next hop 10.1.15.5, Ethernet0/0.15 via 10.100.100.0/30
(Default) valid cached adjacency tag rewrite with Et0/0.15, 10.1.15.5, tags imposed
{502}
Workaround: Issue the “clear ip route” command.
• CSCti08185
Symptoms: WRED Min and Max threshold values appear as “0” in “show policy-map interface”
output on an RP.
Conditions:
1. There are many multilink interfaces on a Cisco 12000 node bearing policies that have class maps
sharing the same WRED min/max threshold configuration.
2. The multilink interfaces must have multiple members (the more members, the more the
probability to hit the issue).
3. There must be a series of member addition/deletion events at the same time, such as during a
reload.
4. The order in which the interfaces (the members of these multilink interfaces) come up also plays
a role in hitting the issue.
Workaround:
1. Remove and re-apply the service policy (this will surely resolve the issue; however this is more
of a recovery procedure).
2. Perform a shut/no shut on the interface (again, a recovery procedure; traffic impacting as well).
3. Before the upgrade, you can identify the policy (with the WRED configuration) that is attached
to more than one multilink interface (with more than one member link). Remove that policy from
the interface and apply it back after the upgrade after all member links of the interface have come up.
• CSCti24849
Symptoms: Available interface bandwidth goes down for the Jag48/FB type of interfaces even when
there is no policy on the main or subinterfaces.
Conditions:
1. The Jag48/FB card which will fall in to types which share same conga port per main interface and
its subinterfaces.
Comentarios a estos manuales