Cisco Cisco IOS Software Release 12.4(23)

Page de 610
830
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
  Resolved Caveats—Cisco IOS Release 12.4(3)
Workaround: There is no workaround. 
CSCsa87986
Symptoms: A router may intermittently transmit corrupt PPP packets. When you enter the debug 
ppp nego
 and debug ppp errors commands, it appears that “protocol reject” packets are received 
from the remote end.
Conditions: This symptom is observed on a Cisco 7500 series that has only one OC3 POS port 
adaptor per VIP and that is configured for PPP encapsulation.
Workaround: There is no workaround. 
IP Routing Protocols
CSCee94020
Symptoms: The timer command to configure SPF and LSA may not be available.
Conditions: This symptom is observed when the OSPF VRF process is configured.
Workaround: There is no workaround. 
CSCef21601
Symptoms: Calls may not complete because ResvConfirm messages are dropped. You can enter the 
debug ip rsvp messages command to track RSVP messages as they traverse routers.
Conditions: This symptom is observed when RSVP is configured for call admission control in a 
network with routers that do not have RSVP and a proxy ARP enabled. The symptom occurs because 
the RSVP-capable hop that sends the ResvConfirm messages uses the next RSVP-capable hop as the 
next IP hop for the packets and does not have the MAC address that is needed to encapsulate the IP 
packets for this next IP hop.
Workaround: Configure a static ARP entry that enables the router to properly encapsulate the packet 
by entering the arp ip-address hardware-address arpa command. The ip-address argument is the 
address of the next hop (that is visible via the RSVP debugs) for the ResvConfirm messages and the 
hardware-address argument is the MAC address of the interface of the next IP hop through which 
the ResvConfirm messages should be routed. 
CSCef86518
Symptoms: A router may generate a series of error messages similar to the following and eventually 
pauses indefinitely because of a software-forced crash:
%SYS-3-CPUHOG: Task is running for (2003)msecs, more than (2000)msecs (2/1),process 
= HSRP (Standby).
Conditions: This symptom is observed on a Cisco router that is configured for secure NAT (SNAT), 
NAT Stateful Failover, and HSRP.
Workaround: Disable NAT Stateful Failover.
Further Problem Description: In order for SNAT, NAT Stateful Failover, and HSRP to function 
together, enter the following commands:
Enter the protocol udp as part of the SNAT configuration.
Enter the standby delay minimum min-delay reload reload-delay for the SNAT-tied HSRP 
group.
Enter the standby [group-numberpreempt [delay {minimum delay | reload delay | sync 
delay}] command for the SNAT-tied HSRP group.