Cisco Cisco IOS Software Release 12.2(15)ZL

Page de 20
 
15
Release Notes for Cisco 3200 Series Mobile Access Routers for Cisco IOS Release 12.2(15)ZL
OL-3424-01
Caveats
When the Sony Ericsson handset connected to the serial interface of the Cisco 3200 router is 
idle for a day, the Cisco 3200 router will no longer be able to communicate with the handset.
Workaround
The communication can be restored either by disconnecting and then reconnecting the handset 
end of the serial cable, or by power-cycling the handset.
When the antenna of the Siemens M35 modem connected to the serial interface of the 
Cisco 3200 router is detached, the Cisco 3200 router will maintain PPP connection although IP 
traffic cannot be send or received.
Workaround
Configure the register lifetime <x> command under ip mobile router. Set x to a lesser value 
if the modem has to be disconnected.
CSCeb06521—Two mobile tunnels may be created pointing to different home agents.
When the Priority HA feature is configured and connectivity to registered HA is lost, a 
CCoA-registered mobile router may not delete its Mobile IP tunnel to that HA after that HA 
registration is deleted. This may cause problems for traffic passing though the mobile router when 
it subsequently registers with another HA.
Workaround
None.
CSCeb06827—Europe Vodafone wireless does not work on Mobile IP.
Vodafone uses Network Address Translation (NAT)/Port Address Translation (PAT) in its network, 
which causes problems for Mobile IP, because Mobile IP uses either generic routing encapsulation 
(GRE) or IP encapsulation that lacks a port to translate.
Workaround
None.
CSCdy79531—Layer 3 QoS features will not work on switched virtual interfaces.
Workaround
None.
Resolved Caveats - Release 12.2(15)ZL
This section describes possibly unexpected behavior by Cisco IOS Release 12.2(15)ZL. This section 
includes severity 1 through 3 caveats.
CSCdu53656
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a 
Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by 
default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the 
malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject 
a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this 
advisory, available at 
.