Aruba CX - VSX - VSX split optimization, if a server connection to both members uses no lacp
=========================================================================

- on secondary member you can use command "shutdown-on-split"
L2 or L3 Pyhsical port which is not member of VSX lag (mlag)
- 8325-2(config)# interface 1/1/37
8325-2(config-if)# vsx
shutdown-on-split Configure to shutdown the interface on VSX split
8325-2(config-if)# vsx shutdown-on-split

hints:
-- VSX split and uptime optimization by avoiding connectivity through VSX secondary during split. This command has no effect on the VSX primary switch during a VSX split.
-- In most cases, this feature is not needed. In very specific cases, for single-homed active connection:
---- Identify the port that must be torn down during VSX split or linkup-delay phase after reboot.

documenation:
- VSX Configuration Best Practices, Revision 2.0 – June 2025, page 43

#####################################################################################
# When connecting a server using non-LACP (Static/Active-Backup or Active-Active with manual configuration) to an Aruba CX VSX pair,
# special consideration is needed for VSX split scenarios to avoid traffic loops and blackholes.
# Because the server does not run LACP, the switches cannot signal that the other peer is down, making proper configuration of VSX
# split-recovery and port-shutdown policies critical.
#
# Key Optimization Strategies (No LACP)
# Implement vsx-shutdown-on-split: When the Inter-Switch Link (ISL) fails, the secondary switch must shut down its member ports
# of the server-connected LAG. Without LACP, the server cannot detect that its connection to one switch is invalid.
# Using vsx-shutdown-on-split on the server-facing interfaces or LAGs prevents the secondary switch from creating a traffic blackhole.
#
#####################################################################################

computer2know :: thank you for your visit :: have a nice day :: © 2026