Cisco Cisco IOS Software Release 12.4(4)T

Page de 302
1079
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
  Resolved Caveats—Cisco IOS Release 12.4(9)T7
CSCse71281
Symptoms: A router crashes with crypto tunnels with large transfers such that they cause IP 
fragmentation.
Conditions: Large pings.
Workaround: There is no workaround.
Further Problem Description: The underlying code has been modified to address this and other 
issues. It is unlikely that the same conditions that can cause the crash still exist. 
CSCsg21804
Symptoms: Fast Ethernet interface 4 may not come up if Cisco Discovery Protocol (CDP) is disabled 
on that interface. The interface may get stuck in the “Initializing” phase.
Conditions: This symptom is observed when a Cisco 871 router is upgraded to a Cisco IOS 
Release 12.4(11.1)T image.
Workaround: The interface can be brought up by executing the shutdown command, followed by 
the no shutdown command, on Fast Ethernet interface 4 or by enabling CDP on the interface. 
Enabling CDP will work across reboots, whereas the shutdown/no shutdown method must be done 
after every reboot. 
CSCsg91306
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS 
that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS 
software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities 
addressed in this advisory. 
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from 
disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to 
provide voice over IP services. 
This advisory is posted at 
.
CSCsi80057
Symptoms: Conditional default origination into RIPv2 does not work correctly in the following 
scenarios:
1.
When the watched network is not present, the default route is not deleted from the local RIP 
database. This causes the router to still send the default route.
2.
When the watched network is present, the default route is not added to the local RIP database. 
This causes the router to not send the default route.
The deault behavior can be seen at the following link:
Conditions: This symptom is observed if the default-information originate route-mamap-name 
router RIP configuration command is used in order to generate a default route only when the 
watched network is present.
Workaround: There is no workaround.