Cisco Cisco IOS Software Release 12.4(4)T

Page de 340
280
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
  Resolved Caveats—Cisco IOS Release 12.4(22)T2
Workaround: Clear VPDN again or reload the router. 
CSCta91556
Symptoms: Packets are getting SSS switched on the LAC towards LNS.
Conditions: The symptom is observed when bringing up any PPPoE or PPPoA session.
Workaround: There is no workaround. 
CSCtb14400
Symptoms: Packets received from the virtual-access CE-facing interface are not CEF-switched into 
the MPLS cloud.
Conditions: The symptom is observed on a MPLS/VPN PE router.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.4(22)T2
Cisco IOS Release 12.4(22)T2 is a rebuild release for Cisco IOS Release 12.4(22)T. The caveats in this 
section are resolved in Cisco IOS Release 12.4(22)T2 but may be open in previous Cisco IOS releases. 
CSCsi43340
Symptoms: DSMP is not programming the DSP for supervisory tone while alerting tone is there, 
which leads to FXO disconnect supervision issue.
Conditions: Occurs on routers running Cisco IOS Release 12.3(14)T and later releases.
Workaround: Downgrade to Cisco IOS Release 12.3(11)T. 
CSCsj17977
Symptoms: The GETVPN rekey fails. The following error message shows in the syslog:
%GDOI-3-GM_NO_IPSEC_FLOWS: IPSec FLOW limit possibly reached
The show crypto engine connections flow will show that all flows are used. For 
hardware-accelerated platforms, use the show crypto eli command to see how many Phase IIs are 
supported.
Conditions: This problem is seen when the registration is not successful on a group member and then 
the flow IDs allocated for that incomplete registration are not cleaned up.
Workaround: Reload the router, if all the flow IDs are leaked. 
CSCsj46707
Symptoms: A CPU may hang and give traceback during boot up.
Conditions: The crash is the result of a race condition caused by the order of operations in 
console_init().
Workaround: There is no workaround. 
CSCsk43926
Symptoms: High CPU usage may occur interrupt context on an RP, and spurious memory accesses 
may be generated when a route-map update is checked. You can verify this situation in the output 
of the show align command.
Conditions: This symptom is observed on a Cisco 7600 series that is configured for BGP.
Workaround: There is no workaround.