There are only good reasons for enabling it on L2 links. STP is required to avoid bridging loops on L2 networks. The bad idea is to disable it, especially if you're planning to hand out redundant links.
If you want to avoid incidents like creative customer attaching a switch to the network or advertising a superior root ID, enable RootGuard and BPDUGuard on the customer facing ports. This will disable the offending ports which has much less impact than having a L2 loop or continous STP instability in your network. Best regards, Andras On Tue, Jan 18, 2011 at 9:07 PM, Jay Nakamura <[email protected]> wrote: > Is there any good reason to turn on STP on a switch port to a > customer? It seems like it could cause more trouble than preventing a > loop. What's your common practice? What if you hand off two > connection for redundancy? > > I am in the middle of converting to MSTP from a network that didn't > really have any STP design or goals. > _______________________________________________ > 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/
