Specifications
1298
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(27)S3
• 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.
• CSCee59315
Symptoms: A BGP VPNv4 table may contain paths that may be imported from deleted BGP table
entries or from table entries that have a different prefix from the importing prefix.
An example of a path from a deleted BGP table entry is as follows:
Router# sh ip bgp v v vpn2 192.168.0.0
BGP routing table entry for 200:2:192.168.0.0/32, version 52
Paths: (1 available, best #1, table vpn2)
Advertised to non peer-group peers:
10.4.1.2
2 100, imported path from 2829:2829:185404173:11.13.11.13/-53
10.1.1.2 from 10.1.1.2 (10.1.1.2)
Origin IGP, localpref 100, valid, external, best
Extended Community: RT:1:3
The entry that this path is imported from has been removed from the table and its memory contents
contain an incorrect pattern. When the incorrect pattern is displayed as a prefix, it appear as
“2829:2829:185404173:11.13.11.13/-53”.
A mismatched prefix appears as follows:
Router# sh ip bgp v v vpn2 192.168.0.0