Specifications

1039
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
– Enter the ip proxy-arp command on the remote side of the Fast Ethernet link.
– Use an OSPF route instead of a default static route.
• CSCed57403
Symptoms: When a Cisco router is a midpoint of a TE tunnel and the tunnel headend is a third- party
vendor router, the Cisco router may crash.
Conditions: This symptom is observed during a period of network instability and may occur when
a TE tunnel does not contain an EXPLICIT ROUTE object and when the tunnel is dynamically
routed by using OSPF cost only.
Workaround: Use an EXPLICIT ROUTE object or ensure that there are no alternate paths in the
network.
• CSCed59978
Symptoms: A router may crash and reload due to a bus error, and the following error message may
appear:
Unexpected exception, CPU signal 10
Conditions: This symptom is observed on a Cisco router that is running OSPF and that is configured
for incremental SPF.
Workaround: Remove incremental SPF from the router by entering the router ospf process-id
command followed by the no ospf command.
• CSCed60800
Symptoms: The withdraw message of a multipath (not bestpath) from a BGP neighbor deletes the
path from the BGP table but it does not uninstall the route from the IP routing table.
Conditions: This symptom is observed when the maximum-paths eibgp command or
maximum-paths ibgp command is configured.
Workaround: Enter the clear ip bgp * or disable the maximum-paths eibgp command or
maximum-paths ibgp command.
Alternate Workaround: if the number of possible BGP paths is less or equal to 2 then the problem is
transient and not obviously noticeable.
• CSCed62479
Symptoms: The neighbor next-hop-unchanged command may not keep the next hop unchanged
for internal paths.
Conditions: This symptom is observed when an internal route is learnt via a confederation eBGP
peer.
Workaround: There is no workaround.
• CSCed93630
Symptoms: A Cisco router running Cisco IOS Release 12.0 S, 12.2 S, or 12.3 T can reload
unexpectedly.
Conditions: The problem can occur only if a bgp debug command is enabled.
Workaround: There is no workaround.
• CSCee10426
Symptoms: A BGP prefix may receive or advertise incorrect label information.
Conditions: This symptom is observed on an MPeBGP session between ASBRs when there is more
than one MPeBGP session configured.