...
- Link Aggregation + Spanning Tree → Possible and practical.
- Link Aggregation + Stacking → Possible and practical. Not possible
- Link Aggregation + Loop Protection → Possible and practical.
...
- Spanning Tree is always configured on ports to other network devices (e.g. a router or a switch).
- STP is deprecated and should not be used anymore.
- In most scenarios it makes sense to use RSTP. There is one instance for the whole network. In contrast to STP topology changes happen much faster with RSTP, thus minimizing downtimes.
- In some scenarios it can be useful to use MSTP. It is used for a VLAN group (a group with only one VLAN is also possible) and forms an instance for each group.
- On GS-23xx and GS-3xxx switches Spanning Tree has to be activated separately for Link Aggregation:
- GS-23xx: In the menu Configuration → Spanning Tree → CIST Ports the option STP Enabled has to be activated under CIST Aggregated Port Configuration.
- GS-3xxx: In the menu Spanning Tree → MSTI Configuration the instance CIST has to be edited under the MSTI Mapping. Afterwards make sure that the option STP Enabled under CIST Aggregated Port Configuration is active (default setting).
Interoperability to other features:
- Spanning Tree + Link Aggregation → Possible and practical.
- Spanning Tree + Stacking → Possible and practical. Not possible
- Spanning Tree + Loop Protection → Possible, but impractical, as both features deactivate ports. Can lead to network problems.
...
- Stacking + Spanning Tree → Possible, but impractical, as path monitoring is already included in Stacking.
- Stacking + Link Aggregation → Possible, but impractical, as Stack ports can be bundled.Not possible
- Stacking + Loop Protection → Possible, but impractical, as a loop is already prevented by Stacking.
...