
493
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S12
• CSCsx94290
Symptoms:
1) In case of a config where police rate is not taking effect on priority command, as we saw it go
through default queue. This occurs in a QoS policy with a priority queue where the “police”
statement occurs before the priority statement in the policy. Additionally, this occurs only upon the
initial configuration of the policy-map. Editing the policy-map will correct the issue.
2) In case of a config where class is configured as only strict priority (no police) and then modified,
packets go through non-default and non-priority queue.
Conditions: The initial configuration of policy-map was modified.
Workaround: Detach and re-attach the policy-map.
Resolved Caveats—Cisco IOS Release 12.0(32)S12
Cisco IOS Release 12.0(32)S12 is a rebuild of Cisco IOS Release 12.0(32)S. The caveats listed in this
section are resolved in Cisco IOS Release 12.0(32)S12 but may be open in previous Cisco IOS releases.
This section describes only severity 1, severity 2, and select severity 3 caveats.
• CSCdw62064
Symptoms: Inbound data packets that are reassembled from multilink fragments may not be
processed properly on Multilink PPP (MLP) interfaces that are receiving encrypted IP Security
(IPSec) traffic that is terminated locally when a hardware accelerator is used for decryption.
Conditions: This symptom affects all inbound reassembled data frames that are received by the
bundle and not just those data frames that are carrying encrypted IP datagrams. Most significantly,
inbound Internet Security Association and Key Management Protocol (ISAKMP) keepalives are not
processed, leading to the eventual failures of the associated IPSec sessions.
The IPSec sessions are reestablished after each failure, but traffic drops will occur until the session
is renegotiated via the Internet Key Exchange (IKE). Thus, the observable symptoms are an
intermittent failure of IPSec sessions combined with high loss rates in the encrypted data traffic.
Workaround: Disable hardware crypto acceleration, and use software crypto acceleration instead.
• CSCea53765
Symptoms: Adding a /31 netmask route on a Cisco router may not overwrite an existing /32 CEF
entry.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.1(13)E4,
Release 12.2, other 12.1E releases, or Release 12.3. Any 12.2S release past 12.2(20)S is not
affected.
Workaround: There is no workaround.
Further Problem Description: The fix for this caveat enables prefixes that are derived from
adjacencies in the FIB to be periodically validated against covering prefixes that originate from the
RIB. Validation ensures that an adjacency prefix is only active when it points out of the same
interface as a covering attached prefix. To enable this validation, enter the ip cef table
adjacency-prefix validate global configuration command.
Note that because validation is periodic, there could be a time lag between RIB changes and
subsequent validation or withdrawal of covered adjacencies in the FIB.
Kommentare zu diesen Handbüchern