Hi, On Wed, May 23, 2012 at 01:15:16PM -0500, Chris Gotstein wrote: > It's probably not going to address the overrun issue, but from a best > practices stand point, it should not be enabled on interfaces that > connected to other connected devices, ie a router or switch.
Uh, so it should only be turned on for switchports that connect to...
"no device"?
Anyway: right for "to switch", dead wrong for "to router". It should be
turned on for any connection that is known to not go to a switch or hub,
and doubly so if rapid-pvstp is used (due to TCNs being sent on a link
flap otherwise, possibly causing stalls elsewhere).
As far as a switch is concerned, a "router" is the same thing as "a host" -
it doesn't forward layer2 things, so can't cause a routing loop.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpNbw4ZR3f9l.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
