Cisco Cisco IOS Software Release 12.4(4)T 發佈版本通知
1426
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(2)T1
Conditions: This symptom is observed on a Cisco 3800 series that runs Cisco IOS
Release 12.3(11)T5 or an earlier release or Release 12.3(14)T1 or an earlier release and that has
subinterfaces that are configured for HSRP. The symptom may also occur on Release 12.4T.
Release 12.3(11)T5 or an earlier release or Release 12.3(14)T1 or an earlier release and that has
subinterfaces that are configured for HSRP. The symptom may also occur on Release 12.4T.
Workaround: Enter the standby use-bia command on the main interface.
•
CSCsb08428
Symptoms: A router may crash when a VPN tunnel is established.
Conditions: This symptom is observed on a Cisco router when an interface has both IPSec and the
ip verify unicast reachable-via command enabled and when a hardware encryption engine is used
for IPSec.
ip verify unicast reachable-via command enabled and when a hardware encryption engine is used
for IPSec.
Workaround: Remove the ip verify unicast reachable-via command from the interface.
•
CSCsb14481
Symptoms: Active voice and fax calls may stop unexpectedly on a gateway, that is, either the call
may drop or two-way audio may stop.
may drop or two-way audio may stop.
Conditions: This symptom is observed when a DSP recovery algorithm on the gateway is started in
response to a DSMP-3-DSP_TIMEOUT error condition. The timeout may occur on one of the
channels of the DSP, but the reset algorithm impacts other calls on other channels that are active on
the same DSP.
response to a DSMP-3-DSP_TIMEOUT error condition. The timeout may occur on one of the
channels of the DSP, but the reset algorithm impacts other calls on other channels that are active on
the same DSP.
Network modules with 549 and 5421 DSPs such as the NM-HDV and AIM-VOICE network
modules are reset when this timeout occurs, causing other active voice and fax calls on other
channels of the same DSP to be reset. Network modules that use 5510 DSPs such as the NM-HDV2
network module do not seem to be reset when this timeout occurs during statistics collection.
modules are reset when this timeout occurs, causing other active voice and fax calls on other
channels of the same DSP to be reset. Network modules that use 5510 DSPs such as the NM-HDV2
network module do not seem to be reset when this timeout occurs during statistics collection.
To verify which DSP is currently in use on a gateway, enter the show voice dsp EXEC command.
Workaround: Disable the DSP recovery algorithm by entering the test dsp recovery disable
command. However, use this command with caution because disabling the auto-recovery
mechanism prevents voice and fax calls from functioning properly when a DSP enters a valid
non-responding state.
command. However, use this command with caution because disabling the auto-recovery
mechanism prevents voice and fax calls from functioning properly when a DSP enters a valid
non-responding state.
Further Problem Description: This fix for this caveat suppresses the resetting of the DSP when the
timeout occurs under a statistics collection state as shown in the sample output below where the state
is equal to S_DSMP_COLLECTING_STATS:
timeout occurs under a statistics collection state as shown in the sample output below where the state
is equal to S_DSMP_COLLECTING_STATS:
%DSMP-3-DSP_TIMEOUT: DSP timeout on DSP 1/5:4: event 0x6, DSMP timed out, while waiting
for statistics from the DSP. DSMP State = S_DSMP_COLLECTING_STATS
for statistics from the DSP. DSMP State = S_DSMP_COLLECTING_STATS
The timeout may occur when an internal software error causes some invalid statistics to be polled,
leading to the timeout. As an example, see caveat CSCsa72951.
leading to the timeout. As an example, see caveat CSCsa72951.
•
CSCsb43655
Symptoms: Some incoming packets that are larger than 1400 bytes are incorrectly counted as “input
errors” on an ATM interface. An ATM error debug reports an “ATM0: AAL5 rx errors (status =
0C100000)” message, which suggests congestion occurs while cells pass through the ATM
interface.
errors” on an ATM interface. An ATM error debug reports an “ATM0: AAL5 rx errors (status =
0C100000)” message, which suggests congestion occurs while cells pass through the ATM
interface.
Conditions: This symptom is observed on a Cisco 870 that is configured as an PPPoE client or for
RFC1483 bridging. Note that the symptom does not occur on a Cisco 836.
RFC1483 bridging. Note that the symptom does not occur on a Cisco 836.
Workaround: There is no workaround.