Cisco Cisco IOS Software Release 12.0 S

Seite von 678
425
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
  Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S2
Resolved Caveats—Cisco IOS Release 12.0(33)S2
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(33)S2. This section 
describes only severity 1, severity 2, and select severity 3 caveats.
CSCeb54456
Symptoms: A Data-link switching plus (DLSw+) circuit may not function when a TCP connection 
gets stuck. After about 90 seconds, the TCP connection is closed by DLSw+, and a new TCP 
connection is built for DLSw+. Once the new TCP connection is up, the DLSw+ circuit starts 
functioning again.
Conditions: This symptom is observed on a Cisco router that is configured with both a DLSw+ 
interface and an ATM interface.
Possible Workaround: If this is an option, remove the ATM interface from the router. When you 
configure the DLSw+ interface and the ATM interface on different routers, the symptom does not 
occur. 
CSCek79311
Symptoms: Under stress conditions, an L2TP multihop node may crash.
Conditions: This symptom is observed when a session is being disconnected.
Workaround: There is no workaround. 
CSCse05292
Symptoms: A static map configuration for an ATM PVC that uses the protocol ip ip-address 
command is rejected, giving an ambiguous command error.
Conditions: This symptom is observed when you configure a static map on an ATM PVC using the 
protocol ip ip- address command.
Workaround: Explicitly configure the [broadcast | no broadcast] option:
Router(config-if-atm-vc)# protocol ip 10.10.100.2 broadcast 
Router(config-if-atm-vc)# protocol ip 10.10.100.2 ? 
broadcast Pseudo-broadcast 
no Prevent Pseudo-broadcast on this connection 
<cr>
Router(config-if-atm-vc)# protocol ip 10.10.100.2 no broadcast 
Router(config-if-atm-vc)# 
CSCsi68795
Symptoms: A PE that is part of a confederation and that has received a VPNv4 prefix from an 
internal and an external confederation peer, may assign a local label to the prefix despite the fact 
that the prefix is not local to this PE and that the PE is not changing the BGP next-hop.
Conditions: The symptoms are observed when receiving the prefix via two paths from confederation 
peers.
Workaround: There is no workaround.
Further Problem Description: Whether or not the PE will chose to allocate a local label depends on 
the order that the multiple paths for this VPNv4 prefix are learned. The immediate impact is that the 
local label allocated takes up memory in the router as the router will populate the LFIB with the 
labels. 
CSCsi77983
Symptoms: The NetFlow cache runs out of space for new flow entry when customer uses heavy 
traffic.