Disadvantages command Block Unicast and multicast
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2015 10:55 AM - edited 03-07-2019 11:28 PM
what are the disadvantages of using the command block unicast and multicast ? You can generate problems with communication?7
Command :
switchport block unicast
switchport block multicast
BestRegards
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2015 11:15 AM
It should not cause any problem as it is designed to block unknown flooding of unicast and multicast traffic:
Occasionally, unknown unicast or multicast traffic is flooded to a switch port because a MAC address has timed out or has not been learned by the switch. (This condition is especially undesirable for a private VLAN isolated port.) To guarantee that no unicast and multicast traffic is flooded to the port, use the switchport block unicast and switchport block multicast commands to enable fl
ood blocking on the switch.
link:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/31sg/configuration/guide/conf/uniflood.html
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2015 11:45 AM
Thank you Sharifi for your comment.
What happens when a mac address is still not learned by the switch. It is taken as unknown unicast?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2015 11:51 AM
If the mac address is not known to the switch then it is a unicast flood and if you have blocked that on a port the end device won't receive the traffic even if it is meant for it.
Once the end device communicates with the switch then it knows the mac address so it will receive traffic.
I have never used that command but my understanding is that you are relying on the fact that most end devices are fairly chatty and so the mac address is always known on the switch.
Of course you would most definitely want portfast enabled on end device ports because otherwise you could see a large number of TCNs which causes the switch to flush the entries of the mac address table of any non edge (ie. non portfast ) ports.
It really depends on what your requirements are and why you would want to block unicast flooding in the first place.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2022 03:16 PM
I have seen it cause outages. period.... full stop... no need for it... it is a badly conceived feature in the real world and protects nothing
