Specifications

1123
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S2
IP Routing Protocols
• CSCea59206
Symptoms: When you configure the distribute-list router configuration command under the
address-family ipv4 vrf vrf name router configuration command, the distribute-list router
configuration command may appear under the main routing process as may be displayed in the
output of the show running-config EXEC command.
Conditions: This symptom is observed in either a Routing Information Protocol version 2 (RIPv2)
or a Border Gateway Protocol (BGP) configuration when you specify the interface-type and
interface-number arguments of the distribute-list {access-list-number | access-list-name} {in |
out} [interface-type interface-number] router configuration command.
The symptom does not occur when you do not define the interface-type and interface-number
arguments and only enter the distribute-list {access-list-number | access-list-name} {in | out}
router configuration command.
Workaround: There is no workaround.
• CSCec22723
Symptoms: A router may unexpectedly reload because of a watchdog timeout or bus error in OSPF.
Conditions: This symptom is observed when iSPF is configured under OSPF.
Workaround: Remove the iSPF configuration from OSPF by entering the no ispf command.
• CSCed93804
Symptoms: EIGRP may incorrectly remove a connected route from a topology.
Conditions: This symptom is observed when you change the router network commands and there are
overlapping networks. For example, if the following is configured:
int loopback1
ip addr 10.1.2.2 255.255.255.0
router eigrp 1
net 10.0.0.0 0.3.255.255
and you change the network command to:
router(config-router)# net 10.0.0.0
router(config-router)# no net 10.0.0.0 0.3.255.255
the connected route will be removed when it should be retained.
Workaround: Remove the old network command first before adding the new one, for example:
router(config-router)# no net 10.0.0.0 0.3.255.255
router(config-router)# net 10.0.0.0
• CSCee28148
Symptoms: After a switchover on a router, one or more obsolete LSAs from a neighboring router
may still be present in the topology. This is improper behavior: the LSAs should no longer be present
in the topology.
Conditions: This symptom is observed when a switchover occur on a Cisco router that runs OSPF
NSF and when a neighboring router flushes one or more of its self-originated LSAs.
Note that the LSAs automatically age out within an hour, unless the link that connects the router and
the neighboring router is a demand circuit or has OSPF “flood-reduction” configured.