Network Management

Hi,
I will configure a pair of  Aruba 8360 with VSX as core level.
1) Do I need to enable on both of them spanning-tree ?
2) Do I need to run only on the main switch spanning tree instance and share this one between such two switches via Global synchronization?
3) If I will use only layer3 point-to-point links for WAN uplinks and "multichassis lag" for connection of layer2 switches to such Aruba 8360 with VSX as core level, do I need to run spanning-tree at all or all links will be not blocked / without layer2 loops ?!

Hi Avy,

I would say:

1. No (see 2)
2. Yes (VSX synchronization option: vsx-sync stp-global)
3. Running Spanning-Tree in a loop-free network topology is perfectly fine because is a mechanism able to save your topology from loops (LAGs - VSX LAGs, also known as Multi-Chassis LAGs, or just standard ones, LACP or static - are seen by Spanning Tree as single interfaces and so it doesn't kick in with respect to LAGs' physical member interfaces that, indeed, are not seen forming any loop).

For sure there is good documentation about implementing Spanning Tree on a VSX Cluster.
Original Message:
Sent: Jul 27, 2022 05:11 AM
From: Andriy -
Subject: spanning-tree for VSX

Hi,
I will configure a pair of  Aruba 8360 with VSX as core level.
1) Do I need to enable on both of them spanning-tree ?
2) Do I need to run only on the main switch spanning tree instance and share this one between such two switches via Global synchronization?
3) If I will use only layer3 point-to-point links for WAN uplinks and "multichassis lag" for connection of layer2 switches to such Aruba 8360 with VSX as core level, do I need to run spanning-tree at all or all links will be not blocked / without layer2 loops ?!