Interfaces on the same VLAN receive IP multicast's from other streamers on the same VLAN. This doesn't scale well and it is not a proper setup for each streamer to automatically receive one another's multicast.
Problem description detail:
Streamer 1 and 2 are both apart of vlan 967. Streamer 2 receives all multicast streams from streamer 1 without any requests. Conversely, streamer 1 receives all of streamer 2's multicasts! I need to prevent the streamers traffic from hitting one another.
no ip igmp snooping
Source VLAN with backfeed problem:
description Modulus Encoders
ip address 10.1xx.yy.65 255.255.255.0
ip pim sparse-dense-mode (same result with just ip pim)
If I remove PIM from the source vlan then the 6500 does not seem to recognize the multicast coming in from the streamers. The mroute doesn't show up but the traffic counters in the Ethernet interface continue to increment:
It would make sense to have IGMP snooping on for the streamer vlan but the Cisco does not seem to accept the command (after issuing the command it does not show up in the vlan interface configuration).
Other info about the network that is a requirement and working fine with the current setup:
Most of my interfaces require me to send the multicast's without any igmp requests. This is easy to do with the ip igmp static-group command such as in this destination VLAN:
ip address 10.1xx.zz.65 255.255.255.0
ip pim dense-mode
ip igmp static-group 126.96.36.199
ip igmp static-group 188.8.131.52
ip igmp static-group 184.108.40.206
ip igmp static-group 220.127.116.11
ip igmp static-group 18.104.22.168
ip igmp static-group 22.214.171.124
ip igmp static-group 126.96.36.199
ip igmp static-group 188.8.131.52
Of course I also have periodic testing that requires me to make an IGMP request from another vlan and request multicast streams from the source vlan 967. For instance, if I'm plugged in as a client to a port apart of vlan 943 I can make an IGMP request and pull the multicast from 967 no prob.
PIM being enabled on the interface is what sends out the IGMP queries. Without it there will be no igmp queries and so no igmp responses.
if you only needed to have multicast on vlan 967 then you can turn off PIM on the interface and enable the "igmp snooping querier" function on the 6500. The IGMP querier function then sends out IGMP queries.
Something has to query for members to report.
That explains your PIM/no PIM issue.
However it looks like you want to access that group from other vlans so you do need PIM on the interface.
But you also need IGMP snooping or else it will flood to all ports as said before.
I need to lab something up so i'll get back to you.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...