Our network switches have STP enabled, and I see that my APs have an option to enable STP as well. The purpose of STP is to prevent network path loops, but the AP only has one connection back to the switch, and only one connection to each client. Why would I want to enable STP on an AP, or would enabling it be moot?
In which situation one should enable the bridge_stp for the host bridge when using KVM? Is it worth keeping it disabled when not needed?
I make heavy use of Linux Bridges (brctl) as I have a Xen environment. At the minute, only one physical NIC is connected to the bridge (There are many virtual NICs for the Xen VMs though). In order to get some redundancy working, what steps would I need to take to add another physical NIC to the bridge? This second NIC will be connected to a different switch. Do I need to run a cable between the 2 switches and enable STP?
Please note that the NIC do not have IP assigned to them (however the bridges do).
I do know the commands to add NICs to bridges; my question related to the redundancy aspect of it.
The topic covers a few topics, so I would try to break this down further as means to provide more information as well as gain a better understanding about the technology.
First some background - we are running a local LAN Party with a lot of attendees. Connected computers vary between 200 and 600 (could be more). We have Netgear FS726T managed switches, with gigabit links leading to a core gigabit switch. The network is setup at least a couple of hours before people come in and is used for 24-48 hours. On those Netgear switches, we've enabled 802.1d to avoid loops, but everything is left with default settings.
We have control over the following STP 802.1d settings (with their ranges):
- Bridge priority (0-65535)
- Bridge Max Age (6-20)
- Bridge Hello Time (1-10)
- Bridge Forward Delay (4-30)
Per port:
- Path cost (1-65535)
- Priority (0-255)
Here are some follow up questions:
- how can the 802.1d settings be tweaked to best suit this scenario?
- can these changes have impact on network performance (both lag and transfer speeds)?
These are the changes I've been considering along with reasons why - is my thinking correct?
- maximize age to avoid rebuilding the spanning tree calculations as much as possible (because the network won't change once it's established)
- maximize hello time to minimize chatter (similar reasons to above)
- minimize forward delay to start sending actual packets as quickly as possible
- increase path cost on standard ports to avoid connected machines from hijacking traffic
- decrease path cost on the link to the core switch to indicate preferable path
- increase priority on the link to the core (same as above)
Any information and partial answers would be appreciated. Information on where to find more information on the topic would also be appreciated.
Thank you
Someone please explain what Spanning Tree Protocol (STP) actually does in layman's terms. I know it can cause problems with some network gear, but that's the extent of my knowledge.