If you span the LAG between VSX members you need to use multi-chasis keyword.
https://www.arubanetworks.com/techdocs/AOS-CX/AOSCX-CLI-Bank/cli_10000/Content/VSX_cmds/int-lag-mul-cha-10.htm
Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Guru 2024
------------------------------
Original Message:
Sent: Aug 23, 2024 05:26 AM
From: barisben
Subject: Aruba AOS-CX 8320 LACP Blocked Issue
Hey! I have a topology as follows; There is HA between FortiGates and there is Aggregate that contains VLANs on port5-port6 and no problem with the config for sure. And Kat-1-L2, Kat-2-L2, Kat-3-L2, Kat-1-2-L2 switches has all vlans and trunks configured well. So no problem with them. SW-L3-A-1 has vsx between SW-L3-A-2. If I don't start SW-L3-A-2 there is no problem, every switch can access each other but if I start it then all lacp ports blocking and nothing works. I have no idea why. L3-A-1 and L3-A-2 configs in the below. (LAG256 was working very well when only Fortigates and SW-L3-A-1, SW-L3-A-2 works. When I start L2 Switches then it stopped)
This is what "sh lacp int" says when I start A-2;