VSX solution topology overview

  • Active gateway support: Active gateways can be configured for active-active routing. VRRP can be used, as an alternative, for active-standby routing.

  • ISL links assigned to higher bandwidth: An ISL link has a higher bandwidth compared to VSX links. When planning the topology, consider sizing the ISL link according to the traffic volume required for the east-west traffic of a single-homed VSX during a failover scenario.

  • Increasing resiliency: When creating a LAG with multiple ports on each chassis-based switch, it is a best practice to create the LAG with members from multiple line cards. This technique increases the points of resiliency.

  • Same VLAN configurations: Both VSX switches have the same VLAN configurations. Make sure that no topology loop is formed because an ISL is added as a member to all the VLANs by default. You can make configuration synchronization automatic between the VSX switches by enabling VSX synchronization.

  • Upstream device from VSX switches: Connections to the upstream device from the VSX switches have sufficient bandwidth to handle traffic from all VSXs.


Core-1 and Core-2, shown in the following figure, can be third-party devices, as long as they support LACP for downstream connectivity to the VSX LAG. VSX Synchronization syncs from the primary switch (shown as Agg-1 in the following diagram) to the secondary switch (shown as Agg-2 in the following diagram).

To configure Core-1 and Core-2 with ArubaOS-CX, see Configuring core 1 and core 2 for VSX.

To configure the aggregate 1 and aggregate 2, see Configuring the two aggregate VSX switches.

To configure the access switch, see Configuring an ArubaOS-CX switch as an access switch.

After setting up the VSX topology, enable VSX synchronization for a feature. VSX synchronization can be enabled globally for some features, and VSX synchronization can be enabled at the context level for other features.

Sample VSX solution topologySample VSX solution topology