
703
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Workaround: There is no workaround.
• CSCsk80552
Symptoms: Delay seen in forming of Protocol Independent Multicast (PIM) auto-RP mapping.
Whenever a link flaps, the graft messages are sent for faster convergence and since these get dropped
over the multicast distribution tree (MDT) tunnel, there is a delay in convergence.
Conditions: Occurs in networks with mVPN deployment and PIM-DM in the core. An interface flap
on the PE/CE router may cause delay in forming PIM auto-RP mapping. The issue causes traffic
black holing and affects the sources and receivers in the network, if the following conditions hold
TRUE:
a. If the network has a mVPN deployment, and the path between source and receiver has to traverse
through the mVPN cloud.
b. If traffic is processed by at least one Cisco 6500 or Cisco 7600 series router in the mVPN
deployment. The occurs when Cisco 6500 and Cisco 7600 series routers are used to decapsulate
traffic,
Workaround: Migrate to PIM-SM. No functionality is affected and the fix for the same is available
in Cisco IOS Release 12.2SXF.
Further Problem Description: The PIM-DM graft messages, unlike other PIM-DM control packets,
are unicast packets. These packets when sent over the MDT tunnel, are encapsulated with multicast
MAC address and a unicast IP address (destination IP of the tunnel). Such packets are not replicated
and are dropped .
• CSCsk81396
Symptoms: Bus Error Exception at "sock_tcp_directwakeup."
Conditions: Occurs on a Cisco WS-C6513 running Cisco IOS Release 12.2(18)SXF8.
Workaround: There is no workaround.
• CSCsk83683
Symptoms: After reload or switchover, when an initial request is made for a rsvd_vlan, VLAN
allocation is not ready at that time.
Conditions: Occurs when route-map contains is configured with VPN routing/forwarding (VRF) on
an interface. The issue creates a synchronization problem between Active & Standby, causing traffic
to be punted to RP after reload or SSO.
Workaround: Remove the VRF and route-map, then apply it again to the interface.
• CSCsk84925
Symptoms: Platforms, such as the Cisco Catalyst 6500, are capable of dropping multicast traffic in
hardware. However, in order to do so, they require that mroute entries be created by software. In the
case of SSM mroutes on a first-hop router, software does not always create such entries and so this
traffic cannot be dropped in hardware, resulting in high CPU utilization on the route-processor.
Conditions: This symptom will be encountered in the following scenario:
1. There are no receivers present for a given SSM (S,G) flow 2. (S1,G) has already been created 3.
A directly-connected source (S2,G) starts sending traffic
That is, the first flow (S1,G) will be created and will be properly dropped in hardware if no receivers
for that flow are present. Subsequent flows to the same group G will not be created and will impact
the route-processor CPU.
Workaround: There are several possible workarounds to this issue:
Comentarios a estos manuales