Cisco ESW Cards and Multicast Issues

[keith]

One of our military guys had this to say about Cisco ESW Cards:

A few years ago the Army had a lot of problems with the ESW line of switch modules in the ISR routers. Most of the issues were related to Multicast; there were some CPU utilization issues as well. Apparently Cisco has not fixed the problem; even though they said that they have. They also provided a work around – turn igmp snooping off; which doesn’t always work either.

Please let us know your experiences with ES or ESW cards.

[jeremycorkery]

On IOS 12.4 (15)T3 when using a 16-ESW-NM switchport module to dot1q trunk to a downstream switch with multiple VLANs, one of which had WAVE clients in, we could not get WAVE to work consistently. Multicast seem to be intermittent, but most of the time actually broken. We did away with this config and did inter-vlan routing from the switch into the fastethernet (non-switchport) port of the router. WAVE worked fine after that.

I have also experienced CPU and memory problems with the switchport, although it was when enabling IP PIM Sparse-dense-mode in a vlan on the switchport which connected to my out-of-band management, which connected to other WAVe routers. So not really a fault of the card.

[keith]

Thanks for the feedback!

[kumar]

Hi I am facing problem in multicasting. I am receiving unwanted multicast stream. Can some on eplease help.


sh ip mroute count
IP Multicast Statistics
4 routes using 2500 bytes of memory
3 groups, 0.33 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 239.1.1.1, Source count: 1, Packets forwarded: 9938, Packets received: 12328
RP-tree: Forwarding: 0/0/0/0, Other: 472/0/472
Source: 172.16.0.57/32, Forwarding: 9938/2/247/0, Other: 11856/0/1918

Group: 224.0.1.40, Source count: 0, Packets forwarded: 0, Packets received: 0

Group: 239.255.255.250, Source count: 0, Packets forwarded: 0, Packets received: 0



239.1.1.1 is unwanted stream which i am receiving.

[lconley]

Hello, Kumar. My name is Larry and I will try to help you.

Can you tell me a bit more about your setup? Are you using a standard WAVE client or does this issue involve a custom application that you've built using the Java or .NET SDK?

How Many Media servers, if any, are involved in your scenario?

What is your networking environment? Are all your clients and Media Servers on a single subnet or are multiple subnets involved?

What zone usage, if any, are you using? If you are using zones, what is the mixture of multicast and unicast zones?

Also, what version of WAVE are you using?

Larry

[kcarpenter]

Kumar,

In addition to Larry's questions I have a couple more items I'd like to clarify.

What is generating traffic from 239.1.1.1 on your network and why do you wish to block it?

Why is the router subscribed to that group if you don't want the traffic to get there?

What is that traffic in the first place? Is this a WAVE standard channel by chance?

Can you please post a copy of your router config? If you would like to keep it private please submit it to support@twistpair.com

The easiest but not so efficient method would be to create an ACL that prevents the multicast group from coming into the router at the interface level. Something to think about is layer 2 switches will broadcast multicast out each port so the router may be receiving it for that reason. Another cause would be maybe the dial-peer for your radios has that address in which case the router is subscribed to that group and will receive that traffic, naturally.

Thank you,
Kenneth