Specifications

1154
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S1
3. The summary LSA IDs for the intra-area routes above, when ORed with the host bits of the
corresponding masks, yield identical LSA IDs.
For example, 10.10.10.128/25 and 10.10.10.0/24 yield identical LSA IDs when the network
address is logically ORed with the host bits; i.e.,
10.10.10.128 | 0.0.0.127 = 10.10.10.255
10.10.10.0 | 0.0.0.255 = 10.10.10.255
Workaround: Perform the clear ip ospf proc command on all ABRs containing the obsolete LSAs.
• CSCee36721
Symptoms: An OSPF Designated Router (DR) may fail to regenerate the network LSA when you
reload the router.
Conditions: This symptom is observed on a Cisco router that functions as a DR for an OSPF
interface when another interface with the same interface address is present in the area but is in a shut
down state.
Workaround: Remove the duplicate interface address and enter the clear ip ospf process command.
• CSCee40207
Symptoms: The BGP Open processes may hold more and more memory, may cause a memory leak,
may finally run out of memory, and may cause a Malloc Failure error.
Conditions: This symptom is observed when there are BGP neighbors stuck in the active state (that
is, a BGP neighbor is configured but the peer address is not reachable) and when some NSF/SSO
RP switchovers occur and the standby becomes active.
Workaround: Shut down the neighbors that are not used.
Further Problem Description: When the memory leak occurs, 1 Kb of memory leaks every two
minutes for each BGP neighbor that is not up.
• CSCee41172
Symptoms: The maximum-paths import number-of-paths command enables a VRF to import
additional paths in addition to the bestpath. If the original path of the import path is withdrawn,
wrong import paths may be purged. This situation may cause traffic disruption up to 15 seconds.
Conditions: This symptom is observed when the original path of the best import path is withdrawn
and the import path is at the end of the path list (that is, the one learned the very first). In this
situation, all import paths that are derived from other paths may be purged as well. If the imported
net has only import paths, the net may not be reachable until other paths are reimported.
Workaround: Ensure that the import path is at the top of the path list or use the same route descriptor
(RD) for all import paths.
• CSCee42285
Symptoms: Non-EIGRP originated routes are not supported. Furthermore, when a route is injected
into mp-BGP from a connected, static, or any other IGP on the remote PE router where the same
prefix is also learned via EIGRP (when a backdoor exists for that site), the route may constantly flap
between EIGRP and BGP.
Conditions: These symptoms are observed when the EIGRP MPLS VPN PE-CE SoO feature is
configured.
Workaround: Only inject EIGRP routes into mp-BGP for sites with a backdoor.
• CSCee43166
Symptoms: The BGP inbound update processing becomes slow and a high CPU utilization occurs
for a long time.