I have been thinking about doing he same thing on our customer access networks.
I would be curious what others features you are enabling as well good topic!
Sent from my iPhone
On Feb 9, 2014, at 6:34 PM, Mike mike-cisconspl...@tiedyenetworks.com wrote:
Hello,
I am looking at
Hi,
Hello,
I am looking at tightening up my subscriber access network and, if
I understand the documentation correctly, 'switchport block unicast'
will prevent a cisco switch (3560g in this case) from flooding unicast
frames out any port so configured, unless the destination mac address
hey,
I am looking at tightening up my subscriber access network and, if
I understand the documentation correctly, 'switchport block unicast'
will prevent a cisco switch (3560g in this case) from flooding unicast
frames out any port so configured, unless the destination mac address
was
Hi,
Let's not forget STP topology change notifications (TCNs) because they'll
cause the MAC address entries to age out in forward-delay (15 sec) or even
immediately with Rapid-STP. A STP topology change is observed (and TCN
generated) when a non-edge (non-portfast) port goes either from
hey,
Let's not forget STP topology change notifications (TCNs) because they'll
cause the MAC address entries to age out in forward-delay (15 sec) or even
immediately with Rapid-STP.
TCN will also screw up IGMP snooping and will cause multicast flooding
for N * general-query-timeout. As a
You pose an interesting question wrt what the default should be.
I don't have that answer. On the same token, unknown unicast flooding is
required for certain topologies to work - campus networks come to mind.
...Your network, you decide based on your topology what to leave-enabled and
what to
