Cisco Cisco IOS Software Release 12.2(33)SRE
170
Caveats for Cisco IOS Release 12.2(33)SRE through 12.2(33)SRE13
OL-10394-05 Rev. S1
Workaround: There is no workaround.
•
CSCtb34814
Symptom: The following error message is reported just before a crash:
%DATACORRUPTION-1-DATAINCONSISTENCY: copy error
There may not be any tracebacks given for the crash.
Conditions: This symptom is observed under normal conditions.
Workaround: There is no workaround.
•
CSCtd72271
Symptom: On an L3 port-channel with member interfaces of a 7600-ES+4TG3CXL module, after a
member interface has recovered from a failure or when a shut/no shut is performed, this member
interface starts flapping and the output traffic is dropped.
member interface has recovered from a failure or when a shut/no shut is performed, this member
interface starts flapping and the output traffic is dropped.
Conditions: This symptom occurs when a service policy is attached or VRF is configured on a
port-channel interface and there are two members on it.
port-channel interface and there are two members on it.
Workaround: Remove the service policy from the port-channel interface
•
CSCtf31377
Symptom: IOS crashes due to processor pool memory corruption.
Conditions: This symptom occurs due to processor pool memory corruption. IOS generates one or
more CLUE memory error messages similar to the following messages:
more CLUE memory error messages similar to the following messages:
%CLUE-DFC3-3-SOR_CORRUPT: CLUE record corruption in start of record field, record id
3341, record
starting address 0x5FFFFF90
This issue could also be seen on LAN cards of a Cisco 7600 router.
Workaround: There is no workaround.
•
CSCtj29261
Symptom: Customer received the following error messages on a Cisco ASR router:
%SYS-2-SHARED: Attempt to return buffer with sharecount 0
Conditions: This issue can occur when the Cisco ASR 1000 router receives STP packet because it
is not yet supported on Cisco ASR 1000.
is not yet supported on Cisco ASR 1000.
Workaround: Stop sending STP packet.
•
CSCtj61284
Symptom: NAT overload does not work for non-directly connected destinations in MPLS-VPN
configurations.
configurations.
Conditions: The symptom is observed with NAT overload configured to NAT traffic coming over an
MPLS VPN to internet (via a VRF-enabled interface).
MPLS VPN to internet (via a VRF-enabled interface).
Workaround: There is no workaround.
•
CSCtk32299
Symptom: SVI state remains down.
Conditions: This symptom occurs when scaled MTP and SVI configurations are copied to the router.
Workaround: Unconfigure and configure MTP and SVI configurations.