Cisco Cisco IOS Software Release 12.0 S

Seite von 678
397
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
  Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S5
SLOT 4:02:04:44: %EE192-3-LINKBUNDLE: Cannot create hw link_bundle -Traceback= 
40030EE8 4068CAC8 405AF138 413B6CCC 413D7464 413D7FA0 413BB2F4 413BB580 413BB88C 
413BC780
Workaround: Reload the linecard. 
CSCtc72808
Symptoms: In situations where an enhanced SFC module would experience problems with the clock 
module, a recovery feature that was introduced in previous releases would try to recover switch 
fabric system indefinitely:
%FABRIC-3-ERR_HANDLE: Reconfigure all fabric cards due to SUSHI REGISTER RESET ERROR 
error from slot <..>
And that would lead to linecard resets in the chassis.
Conditions: This behavior is observed when a enhanced SFC module experiences hardware/clock 
module problems.
Workaround: Disable the faulty module in configuration mode:
hw-module slot <slot> shutdown 
CSCtc76700
Symptoms: An E5 T1E1 SPA loses all configurations when the image is loaded.
Conditions: This symptom is observed when the latest Cisco IOS Release 12.0 (33)S6 image is 
loaded.
Workaround: There is no workaround.
CSCtd15620
Symptoms: An interface on a ChOC12 linecard remains down after a shut/no shut is performed.
Conditions: This symptom is observed when a shut/no shut is performed on a serial interface.
Workaround: Perform a shut/no shut on the SONET controller.
Resolved Caveats—Cisco IOS Release 12.0(33)S5
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(33)S5. This section 
describes only severity 1, severity 2, and select severity 3 caveats.
CSCsx70889
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service 
(DoS) attack if configured for IP tunnels and Cisco Express Forwarding. Cisco has released free 
software updates that address this vulnerability. This advisory is posted at
.
CSCsz55293
Symptoms: A remote third-party device is resetting the IPv6 BGP session with a Cisco 12000 router.
Conditions: BGP is exchanging only IPv6 capability with the remote EBGP peer, but IPv4 capability 
will be enabled by default. The remote EBGP peer is sending only IPv6 capability, and we should 
advertise only IPv6 prefixes because that is the capability negotiated. We are wrongly marking IPv4 
capability as negotiated and advertising IPv4 prefixes, and the remote neighbor is resetting the 
session because IPv4 capability is not negotiated at the peer end.
Workaround: Configure a route map to deny all IPv4 prefixes, and apply it as follows:
Route-map deny-ipv4 deny 10