Cisco Cisco IOS Software Release 12.4(23)
831
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(3)
•
CSCeg07725
Symptoms: A router may continue to redistribute an eBGP route into EIGRP after the eBGP route
is deleted or EIGRP may not redistribute an eBGP route after the eBGP route has been installed.
is deleted or EIGRP may not redistribute an eBGP route after the eBGP route has been installed.
Conditions: This symptom is observed on a Cisco router that redistributes eBGP routes into EIGRP
when the router functions in a multihoming environment.
when the router functions in a multihoming environment.
The symptom occurs in a configuration with two PE routers that advertise routes via eBGP and a
border router that is configured with a higher local preference than the PE routers when the eBGP
route of the primary path is withdrawn and the route of the secondary path is installed.
border router that is configured with a higher local preference than the PE routers when the eBGP
route of the primary path is withdrawn and the route of the secondary path is installed.
Workaround: If a route is still redistributed into EIGRP after the eBGP route is deleted, clear the
BGP peer from which the eBGP route used to be learned so EIGRP stops advertising the route.
BGP peer from which the eBGP route used to be learned so EIGRP stops advertising the route.
If a route is not redistributed into EIGRP after an eBGP route is installed, clear the route so EIGRP
starts advertising it. Another workaround is to enter the bgp redistribute-internal command to
cause EIGRP to redistribute iBGP routes and to prevent EIGRP from failing to redistribute an
updated BGP route.
starts advertising it. Another workaround is to enter the bgp redistribute-internal command to
cause EIGRP to redistribute iBGP routes and to prevent EIGRP from failing to redistribute an
updated BGP route.
•
CSCeg51291
Symptoms: A VRF ping fails to reach an OSPF neighbor interface.
Conditions: This symptom is observed when the platform on which the ping originates and the OSPF
neighbor interface are connected via an OSPF sham link that is used for interconnecting traffic
between two VPN sites.
neighbor interface are connected via an OSPF sham link that is used for interconnecting traffic
between two VPN sites.
Workaround: There is no workaround.
•
CSCeg58039
Symptoms: Border Gateway Protocol (BGP) may crash.
Conditions: This symptom is observed when the number argument of the maximum-paths number
command is modified.
command is modified.
Workaround: There is no workaround.
•
CSCeg89700
Symptoms: A Cisco router does not recognize an end-of-RIB message from a third-party vendor
router and continues to show the “Neighbor is currently in NSF mode” message although the restart
procedure of the third-party vendor router is complete.
router and continues to show the “Neighbor is currently in NSF mode” message although the restart
procedure of the third-party vendor router is complete.
Conditions: This symptom is observed on a Cisco router that is configured for IPv6 BGP peering
and NSF. Note that the symptom does not occur when IPv4 BGP peering is configured.
and NSF. Note that the symptom does not occur when IPv4 BGP peering is configured.
Workaround: There is no workaround.
•
CSCeh07809
Symptoms: When BGP nexthop information for a prefix changes because of topology changes, BGP
properly updates its path information and IP routing table entry but CEF may not update the
corresponding CEF entry, causing a stale entry. This inconsistency between BGP and CEF may
cause a connectivity problem.
properly updates its path information and IP routing table entry but CEF may not update the
corresponding CEF entry, causing a stale entry. This inconsistency between BGP and CEF may
cause a connectivity problem.
Conditions: This symptom is observed when the nexthop information changes to an existing prefix
entry in the BGP routing table. Typically, this occurs when the interface through which the prefix is
learned goes down.
entry in the BGP routing table. Typically, this occurs when the interface through which the prefix is
learned goes down.
Workaround: Flush out the stale CEF entry by entering the clear ip bgp command or withdraw and
readvertise the prefix by the source router, which enables the affected router to refresh the CEF
entry.
readvertise the prefix by the source router, which enables the affected router to refresh the CEF
entry.