Cisco Cisco IOS Software Release 12.4(4)T
1058
Caveats for Cisco IOS Release 12.4T
OL-8003-09 Rev. Z0
Resolved Caveats—Cisco IOS Release 12.4(11)T
Further Problem Description: Use the show ip nhrp command to look for NHRP mapping entries
that are covered by an NHRP network mapping entry in the table.
that are covered by an NHRP network mapping entry in the table.
Example:
Network mapping:
192.168.13.0/24 via 10.0.0.13, Tunnel0 created 00:02:51, expire 00:07:08
Type: dynamic, Flags: router nat
NBMA address: 172.16.3.1
Incomplete mapping covered by above network mapping
192.168.13.70/32, Tunnel0 created 00:02:51, expire 00:00:13
Type: incomplete, Flags: negative
Cache hits: 61
192.168.13.72/32, Tunnel0 created 00:02:51, expire 00:00:13
Type: incomplete, Flags: negative
Cache hits: 16
If this example indicates the symptom is present. Clearing the incomplete
mappings clears the symptom, but it can easily come back.
Example:
clear ip nhrp 192.168.13.70
•
CSCsf11980
Symptoms: On Cisco IOS interim Release 12.4(9.16)T when running a DMVPN configuration with
dual hub routers and with OSPF as the IGP, the router may experience a crash as NHRP attempts to
send a NHRP resolution request.
dual hub routers and with OSPF as the IGP, the router may experience a crash as NHRP attempts to
send a NHRP resolution request.
Conditions: This symptom has been observed on routers with Cisco IOS interim Release
12.4(9.16)T when running a DMVPN configuration with dual hub routers and with OSPF as the IGP.
12.4(9.16)T when running a DMVPN configuration with dual hub routers and with OSPF as the IGP.
Workaround: There is no workaround.
•
CSCsg22426
Symptoms: A router running Cisco IOS may unexpectedly reload. The crashes can be very different
in nature, but the crashinfo should show the IP Input process as the currently running process:
in nature, but the crashinfo should show the IP Input process as the currently running process:
---- Partial decode of process block ----
Pid 84: Process "IP Input" stack 0x46C3C080 savedsp 0x46758540
Conditions: This is seen when the router is configured for NAT and receives a fragmented skinny
packet that it needs to reassemble and translate.
packet that it needs to reassemble and translate.
Workaround: Prevent the router from receiving a fragmented skinny packet by ensuring the path
MTU between the call manager server and the router is large enough. Usually skinny packets aren’t
larger than 800 bytes.
MTU between the call manager server and the router is large enough. Usually skinny packets aren’t
larger than 800 bytes.
Miscellaneous
•
CSCei39688
Symptoms: When a CEF initialization failure occurs, an ATM PVC that is configured for OAM may
not pass traffic even though the PVC link status is up:
not pass traffic even though the PVC link status is up:
Router#show ip interface brief | include ATM
ATM3/0/0 unassigned YES manual up up