Cisco Cisco IOS Software Release 12.4(4)T
1323
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(4)T2
•
CSCek10384
Symptoms: A Cisco 7200 router that is performing NAT could drop IPSec packets.
Conditions: This symptom is observed on a Cisco 7200 router that is performing NAT functionality
for IPSec transit packets. The router will NAT and forward the Inside to Outside IPSec (ESP)
packets, but might drop the return IPSec packets from Outside to Inside.
for IPSec transit packets. The router will NAT and forward the Inside to Outside IPSec (ESP)
packets, but might drop the return IPSec packets from Outside to Inside.
Workaround: Disable NAT for IPSec.
•
CSCsb09852
Symptoms: The number of networks in the BGP table and the number of attributes increases, and a
slower convergence may occur for members of a BGP update group.
slower convergence may occur for members of a BGP update group.
Conditions: This symptom is observed on a Cisco router when the members of a BGP update group
go out of synchronization with each other in such a way that they have different table versions,
preventing the BGP Scanner from freeing networks that do not have a path.
go out of synchronization with each other in such a way that they have different table versions,
preventing the BGP Scanner from freeing networks that do not have a path.
To check if the members of the BGP update group are in synchronization with each other, enter the
show ip bgp update-group summary command and look at the table version for each member. If
they have the same table version, they are in synchronization with each other; if they do not, they
are out of synchronization with each other.
show ip bgp update-group summary command and look at the table version for each member. If
they have the same table version, they are in synchronization with each other; if they do not, they
are out of synchronization with each other.
Workaround: To enable the members of the BGP update group to synchronize with each other, enter
the clear ip bgp * soft out command. Doing so does not bounce the sessions but forces BGP to
re-advertise all prefixes to each member.
the clear ip bgp * soft out command. Doing so does not bounce the sessions but forces BGP to
re-advertise all prefixes to each member.
•
CSCsb50606
Symptoms: Memory utilization in the "Dead" process grows gradually until the memory is
exhausted. The output of the show memory dead command shows that many "TCP CBs" re
allocated. Analysis shows that these are TCP descriptors for non-existing active BGP connections.
exhausted. The output of the show memory dead command shows that many "TCP CBs" re
allocated. Analysis shows that these are TCP descriptors for non-existing active BGP connections.
Conditions: This symptom is observed on a Cisco 7200 series that runs Cisco IOS Release 12.3(13),
that has an NPE-G1, and that functions as a PE router with many BGP neighbors. The symptom may
not be platform-specific.
that has an NPE-G1, and that functions as a PE router with many BGP neighbors. The symptom may
not be platform-specific.
Workaround: Reload the router. I this is not an option, there is no workaround.
•
CSCsb74588
Symptoms: A router that is configured for OSPFv3 may crash because of memory corruption or a
CPUHOG condition.
CPUHOG condition.
Conditions: This symptom is observed rarely in a configuration with a large LSA with 64 parallel
links that have OSPFv3 enabled in broadcast mode when all adjacencies with a peer router flap.
links that have OSPFv3 enabled in broadcast mode when all adjacencies with a peer router flap.
Workaround: There is no workaround.
•
CSCsb79749
Symptoms: The output of the show memory summary command may contain garbled characters in
the "What" column.
the "What" column.
Conditions: This symptom is observed when you configure OSPF with at least one network, and then
unconfigure it.
unconfigure it.
Workaround: There is no workaround.
•
CSCsc10494
Symptoms: When an inter-area, external, or Not-So-Stubby Area (NSSA) route is learned via a link
state update that follows the initial database synchronization, the route may not be added to the
routing table by a partial shortest path first (SPF) computation even though the LSA is installed in
the link state database. A subsequent full SPF computation causes the route to be added.
state update that follows the initial database synchronization, the route may not be added to the
routing table by a partial shortest path first (SPF) computation even though the LSA is installed in
the link state database. A subsequent full SPF computation causes the route to be added.