Specifications

1131
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S2
Workaround: Configure the static ARP entries for the nexthop router that is configured in the static
recursive routes.
CSCef25917
Symptoms: A 4GE-SFP-LC line card may reload unexpectedly when it processes QoS traffic in a
configuration with a VLAN on a VCG that is configured with an ingress CoS.
Conditions: This symptom is observed on a Cisco 12000 series that runs Cisco IOS
Release 12.0(26)S or a later release when the resolved ARPs are deleted, for example, when routers
flap, when BGP peers do not respond, or when you enter the clear arp command. Note that the
symptom may also occur on releases earlier than Release 12.0(26)S.
The ingress CoS includes a set command for the matched class: either a police command with a set
command or a simple set command and either a set-mpls command or a set-dscp command.
Possible Workaround: Configure static ARPs.
CSCef26053
Symptoms: Load-balancing does not work over a BGP multipath. Some of the traffic may be
forwarded correctly while other traffic may be forwarded unlabeled into the MPLS core.
Conditions: This symptom is observed on a Cisco router that functions as a PE router when the
following conditions are present:
The affected route is in a VRF.
One of the paths is learned from a CE router via an eBGP multihop session.
The eBGP multihop peer (that is, the CE router) is reachable through the MPLS core and the
BGP session does not involve a label exchange.
Workaround: Avoid a multihop eBGP session in which the CE router is reachable through the MPLS
core. For example, instead of a configuration in which the CE router connects to the PE router across
the MPLS core, configure the CE peer to connect to a local PE router that redistributes the routes it
has learned from the CE peer to other PE routers. (The local PE router may need to be configured
for eiBGP multipath.)
CSCef26543
Symptoms: A Cisco 12000 series line card may rate-limit process-switched packets to the GRP. This
situation causes a ping to be lost when you perform a ping test to the local interface of the router.
Conditions: This symptom is observed when the interface is configured for HDLC, when the
interface has a hard loop, and when the IP address of the interface is the destination of the ping.
Because the interface is in the up/up state (looped) and functional, there should be no packet loss
when you ping the interface at its own IP address.
Workaround: There is no workaround.
CSCef29467
Symptoms: When you enter commands in various configuration modes such as address-family,
PVC, service-policy, and so on, an invalid input error message may be returned even though the
command was accepted and entered into the running configuration. The following is an example:
Router(config-router-af)#redistribute connected
address-family ipv4 vrf atmTrk
^
Invalid input detected at “^” marker.