Cisco Cisco IOS Software Release 12.4(23) Notas de publicación
907
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(1b)
Further Problem Description: We do not recommend process-switching in combination with
software payload compression because it is not possible to provide latency guarantees.
software payload compression because it is not possible to provide latency guarantees.
•
CSCin88048
Symptoms: The protocol does not come up when channelized T3 is changed to unchannelized.
Conditions: This symptom has been observed when a channelized T3 is changed to the
unchannelized mode.
unchannelized mode.
Workaround: Reconfigure or reboot the router.
IP Routing Protocols
•
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.
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.
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.
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.
•
CSCeh15639
Symptoms: A Cisco router may crash when it is reloaded with PIM traffic on the network.
Conditions: This symptom is observed on a Cisco 7200 series router with multicast enabled but is
not platform dependent. Bootup is the most likely place where this will happen, but the router may
crash anytime if an interface flap happens at the right time while receiving PIM traffic.
not platform dependent. Bootup is the most likely place where this will happen, but the router may
crash anytime if an interface flap happens at the right time while receiving PIM traffic.
Workaround: There is no workaround.
•
CSCei06089
Symptoms: Conditional advertisement of the default route via a route map does not work when you
enter the neighbor default-originate command.
enter the neighbor default-originate command.
Conditions: This symptom is observed on a Cisco router that is configured for BGP.
Workaround: Disable the route map entirely. If this is not an option, there is no workaround.
•
CSCei26899
Symptoms: When you reset a BGP peer, some prefixes are missing.
Conditions: This symptom is observed on a Cisco MGX8850 RPM-XF that runs Cisco IOS
Release 12.3(11)T. However, the symptom is platform-independent and may also occur in other
releases.
Release 12.3(11)T. However, the symptom is platform-independent and may also occur in other
releases.
Workaround: There is no workaround.
•
CSCsa65155
Symptoms: IS-IS may not update redistributed BGP network changes.