Cisco Cisco IOS Software Release 12.4(23) Notas de publicación
930
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(1a)
Resolved Caveats—Cisco IOS Release 12.4(1a)
Cisco IOS Release 12.4(1a) is a rebuild release for Cisco IOS Release 12.4(1). The caveats in this
section are resolved in Cisco IOS Release 12.4(1a) but may be open in previous Cisco IOS releases.
section are resolved in Cisco IOS Release 12.4(1a) but may be open in previous Cisco IOS releases.
IP Routing Protocols
•
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.
•
CSCeg58039
Symptoms: Border Gateway Protocol (BGP) could crash.
Conditions: This symptom occurs when the max-paths value is modified.
Workaround: There is no workaround.
•
CSCeh33504
Symptoms: A router terminates 102,000 VPNv4 routes but route reflectors (RRs) report only a a
subset of the total.
subset of the total.
Conditions: This symptom is observed on a Cisco MGX RPM-XF that runs Cisco IOS
Release 12.3(11)T4 when 204 routes are configured per VRF over 496 VPNs (one VPN has about
1000 routes). However, Cisco MGX RPM-PRs that function as RRs show that only 76245 routes are
terminated on the Cisco MGX RPM-XF. The symptom may be platform-independent.
Release 12.3(11)T4 when 204 routes are configured per VRF over 496 VPNs (one VPN has about
1000 routes). However, Cisco MGX RPM-PRs that function as RRs show that only 76245 routes are
terminated on the Cisco MGX RPM-XF. The symptom may be platform-independent.
Workaround: There is no workaround.
•
CSCeh47763
Symptoms: A Cisco router may erroneously send ACK packets in response to RST packets for
non-local TCP sessions. This can cause high CPU utilization on the router.
non-local TCP sessions. This can cause high CPU utilization on the router.
Conditions: This symptom occurs when using Port Address Translation (PAT).
Workaround: Use the clear ip nat translation * command.
•
CSCsa54937
Symptoms: An LNS with a VRF configuration does not send an echo reply when it receives a ping
to loopback interface 0.
to loopback interface 0.
Conditions: This symptom is observed on a Cisco 7200 series that is configured with an NPE-300,
a Cisco 7200 series that is configured with an NPE-400, and a Cisco 7400 series.
a Cisco 7200 series that is configured with an NPE-400, and a Cisco 7400 series.