Cisco Cisco IOS Software Release 12.4(4)T
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
1326
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(4)T2
•
CSCej10160
Symptoms: A spurious memory access is generated on a Cisco 3700 series, causing IPMC voice
traffic to be dropped temporarily.
traffic to be dropped temporarily.
Conditions: This symptom is observed on a Cisco 3700 series that has DSP-related features enabled
and that has Cisco Land Mobile Radio (LMR) features configured on the voice ports.
and that has Cisco Land Mobile Radio (LMR) features configured on the voice ports.
Workaround: There is no workaround.
•
CSCej13460
Symptoms: The packets are not switched correctly using the Fast Switching with IPSec tunnel
protection feature.
protection feature.
Condition: This symptom has been observed in Cisco IOS Release 12.4(1b) when tunnel protection
IPSec is configured and tunnel source interface has Fast- switching (but not CEF) configured.
IPSec is configured and tunnel source interface has Fast- switching (but not CEF) configured.
Workaround: Use CEF switching.
•
CSCej22954
Symptoms: The show event manager history events [detailed] [maximum number] command
may crash when the history queue has looped.
may crash when the history queue has looped.
Conditions: The default size of the Embedded Event Manager (EEM) history events queue is 10. If
11 events come in, then the number] argument with a value less than 10 will cause the issue. This
symptom only affects routers using the EEM and with the show event manager history events
command using the maximum keyword.
11 events come in, then the number] argument with a value less than 10 will cause the issue. This
symptom only affects routers using the EEM and with the show event manager history events
command using the maximum keyword.
Workaround: Do not use the maximum keyword.
•
CSCej42804
Symptoms: A Cisco Gateway that is running Session Initiation Protocol (SIP) calls might run out of
processor memory due to hung SIP calls.
processor memory due to hung SIP calls.
Conditions: Active and hung calls can be seen using the show sip-ua calls command. The following
specific scenario will result in a hung call:
specific scenario will result in a hung call:
1.
The gateway initiates an INVITE.
2.
The gateway receives a 100/180 response.
3.
The gateway sends a CANCEL.
4.
The gateway receives the 200ok for the CANCEL.
5.
The gateway receives an invalid final response for the INVITE (or no final response) and drops
the message.
the message.
Each hung call will use a little more memory, and eventually the gateway will run out of memory.
Workaround: Downgrade to Cisco IOS Release 12.3(14)T3, Release 12.3(11)T6,
Release 12.4(2)T1, or Release 12.4(1a).
Release 12.4(2)T1, or Release 12.4(1a).
•
CSCej42935
Symptoms: Data corruption may occur on a disk when directory entries are read by more than one
process simultaneously.
process simultaneously.
Conditions: This symptom is observed on a Cisco platform that has an ATA file system when, for
example, the dir disk0: command is entered on one vty connection and simultaneously, and for the
same disk, the copy disk0: command is entered on another vty connection.
example, the dir disk0: command is entered on one vty connection and simultaneously, and for the
same disk, the copy disk0: command is entered on another vty connection.
Workaround: There is no workaround.