Cisco Cisco IOS Software Release 12.2
41
Caveats for Cisco IOS Release 12.2
OL-3513-16 Rev. G0
Resolved Caveats—Cisco IOS Release 12.2(29)
A combined software table for Cisco IOS is available to aid customers in choosing a software
releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is
available at the following link:
releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is
available at the following link:
Resolved Caveats—Cisco IOS Release 12.2(29)
This section describes possibly unexpected behavior by Cisco IOS Release 12.2(29). All the caveats
listed in this section are resolved in Cisco IOS Release 12.2(29). This section describes severity 1 and 2
caveats and select severity 3 caveats.
listed in this section are resolved in Cisco IOS Release 12.2(29). This section describes severity 1 and 2
caveats and select severity 3 caveats.
The following information is provided for each caveat:
•
Symptoms: A description of what is observed when the caveat occurs.
•
Conditions: The conditions under which the caveat has been known to occur.
•
Workaround: Solutions, if available, to counteract the caveat.
Basic System Services
•
CSCds33629
Symptoms: Closing an existing Telnet session may cause a router to crash.
Conditions: This symptom is platform-independent
Workaround: There is no workaround.
•
CSCeg64124
Symptoms: The operation result of an IP SLA jitter probe shows a high packet MIA that is equal to
the jitter’s number of packets minus one. In the responder router, the responder debug message
shows many error packets.
the jitter’s number of packets minus one. In the responder router, the responder debug message
shows many error packets.
Conditions: This symptom is observed when multiple jitter probes (either from the same router or
from different routers) are configured to send packets to the same destination IP address and the
same destination port number and when the responder is turned off for a short time and turned on
again.
from different routers) are configured to send packets to the same destination IP address and the
same destination port number and when the responder is turned off for a short time and turned on
again.
Workaround: To prevent the symptom from occurring, configure the jitter probe to use a unique
destination port number.
destination port number.
Alternate Workaround: If the symptom has occurred, turn off the responder by entering the no rtr
responder global configuration command, wait until all jitter probes report “No connection,” and
then turn on the responder by entering the rtr responder global configuration command.
responder global configuration command, wait until all jitter probes report “No connection,” and
then turn on the responder by entering the rtr responder global configuration command.
•
CSCeh34983
Symptoms: A Cisco AS5400 gateway might stop unexpectedly, showing the following error
message on the console:
message on the console:
Breakpoint exception, CPU signal 23, PC = 0x603955C0
Conditions: This symptom has been observed with Cisco IOS Release 12.2(27). This symptom has
not seen on releases after Cisco IOS Release 12.2(4)T or on Cisco IOS Release 12.3 and later
releases. This symptom has been seen only if an invalid attribute is configured in profile.
not seen on releases after Cisco IOS Release 12.2(4)T or on Cisco IOS Release 12.3 and later
releases. This symptom has been seen only if an invalid attribute is configured in profile.
Workaround: Configure all valid attributes in the profile.