Cisco Cisco IOS Software Release 12.4(4)T
1097
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(9)T4
–
There is an inconsistency between the NHRP cache and the Adjacency for the problematic
spoke.
spoke.
Conditions: These symptoms have been observed with DMVPN set up.
Workaround: Disable CEF on the hub.
•
CSCsi09698
Symptoms: In Cisco IOS software that is running the Border Gateway Protocol (BGP), BGP may
advertise a connected prefix that has been removed from the routing table, and cause using that
prefix to get dropped. The advertisement may happen during a reload if IP Event Dampening is
configured on the interface and suppresses the interface because of flapping during the reload. The
problem may continue until the interface is unsuppressed, which depends on the nature of the
flapping that occurs and on the parameters used to configure the dampening. In some releases, the
problem may be corrected by a BGP scan. An outage of about one minute is not unreasonable.
advertise a connected prefix that has been removed from the routing table, and cause using that
prefix to get dropped. The advertisement may happen during a reload if IP Event Dampening is
configured on the interface and suppresses the interface because of flapping during the reload. The
problem may continue until the interface is unsuppressed, which depends on the nature of the
flapping that occurs and on the parameters used to configure the dampening. In some releases, the
problem may be corrected by a BGP scan. An outage of about one minute is not unreasonable.
Conditions: The symptom may happen if the BGP configuration includes a network command for
the connected prefix. It requires an unlikely timing of events which is more likely to be observed
with large configurations, and when the interface is configured to use small carrier delay timer. The
symptom was observed in a configuration with about 1100 lines and with the carrier-delay msec 0
command configured on the interface in question.
the connected prefix. It requires an unlikely timing of events which is more likely to be observed
with large configurations, and when the interface is configured to use small carrier delay timer. The
symptom was observed in a configuration with about 1100 lines and with the carrier-delay msec 0
command configured on the interface in question.
Workaround: If the interface can be configured to filter out link outages during the restart then the
IP Event Dampening suppression can be avoided. Configuring the carrier-delay msec 100
command on the interface may achieve this in some cases.
IP Event Dampening suppression can be avoided. Configuring the carrier-delay msec 100
command on the interface may achieve this in some cases.
•
CSCsi62559
Symptoms: OSPF packets with IP Precedence 0 are classified by SPD as priority. This is an error
because only IP Precedence 6 packets should be classified as priority packets by SPD.
because only IP Precedence 6 packets should be classified as priority packets by SPD.
Conditions: This symptom has been observed on a Cisco router running Cisco IOS Release 12.2(18)
and later.
and later.
Workaround: Use ACLs to block invalid IP Control packets from reaching the control plane.
Miscellaneous
•
CSCej42879
Symptoms: A traceback may be generated when packets are transmitted over a basic IPSec
connection between two peers in transmission mode and tunnel mode using multilink interfaces.
connection between two peers in transmission mode and tunnel mode using multilink interfaces.
Conditions: This symptom is observed on a Cisco 3845 router that runs Cisco IOS Release 12.4(5).
Workaround: There is no workaround.
•
CSCsd43903
Symptoms: A Cisco router may experience memory leaks in the Crypto IKMP process when using
certificates for Internet Security Association and Key Management Protocol (ISAKMP) for peer
authentication.
certificates for Internet Security Association and Key Management Protocol (ISAKMP) for peer
authentication.
Conditions: This symptom has been observed on Cisco IOS Release 12.2(18)SXE5 and
Release 12.4(9)T2. This symptom is platform independent.
Release 12.4(9)T2. This symptom is platform independent.
Workaround: There is no workaround to prevent the leak and the only way to recover is to reboot
the device.
the device.