Specifications

1041
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
2. The ABRs are generating summary LSAs, on behalf of the Area X’s two or more intra-area
routes, into the backbone area and other areas. The two intra-area routes must be advertised as
stub links from two different routers; i.e., one from ABR X, and the other from another router
belonging to Area X.
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, it will be a consistent 1k leak for each
neighbor that is not up every 2 minutes.
• 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.
Conditions: This symptom is observed when a large number of VRFs (more than 200) and prefixes
(more than 220,000) are configured.
Workaround: There is no workaround.
• CSCee49764
Symptoms: The redistribute maximum-prefix command may not take effect.