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 disable.
./Randy >________________________________ > From: Mike <[email protected]> >To: "[email protected]" <[email protected]> >Sent: Sunday, February 9, 2014 4:34 PM >Subject: [c-nsp] wisdom of switchport block ... > > >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 was learned from >that port. Is there any reason on earth why I would NOT want to have this as a >standard default option? Arp would still work, as would dhcp and pppoe... >trying to fathom how this could be bad? Would appreciate any insights! > >Thank you. > >Mike- > >_______________________________________________ >cisco-nsp mailing list [email protected] >https://puck.nether.net/mailman/listinfo/cisco-nsp >archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
