We just finished deploying 2 cisco SG300-28 switches in our network. We're building a voLANte video distribution network, so all ports were enabled to have multicasting support.
The problem we face is that our Crestron AV2 doesn't support Multicasting. Do any of you know how to disable multicasting on a single port?
Here's the running config if it matters
no spanning-tree
interface port-channel 1
description Default
exit
bridge multicast filtering
vlan database
default-vlan vlan 999
exit
vlan database
vlan 1
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
interface range gi25-28
channel-group 1 mode on
exit
ip igmp snooping
ip igmp snooping vlan 999
ip igmp snooping vlan 999 mrouter interface Po1
interface vlan 999
ip igmp query-interval 30
ip igmp last-member-query-interval 100
exit
interface range gi1-28
bridge multicast unregistered filtering
exit
ip igmp snooping vlan 999 querier
ip igmp snooping vlan 999 querier address 192.168.1.254
interface vlan 999
ip address 10.10.10.2 255.255.255.0
exit
ip default-gateway 10.10.10.1
interface vlan 999
no ip address dhcp
exit
no boot host auto-config
no bonjour enable
hostname switchb18a77
no snmp-server server
It appears to me as though this would be called "Unicast and Multicast Flood Blocking"
For future reference, I think the option you are looking for may be 'Unregistered Multicast' filtering on the SG300s. (I tried the previous answer's suggestion but that wasn't enough to help in itself for me)
I just had a Meraki router which was for some reason, subscribing to our Symantec Ghost Multicast sessions, not ideal! Setting Unregistered Multicast to Filtering for the port it was connected to sorted the issue and allowed us to get better Ghost performance too.
Based on this link, on page 252, here are the necessary steps to disable multicast flooding on a specific port.