Not in the way you draw those downlinks (uplinks).
The point is: interlinking two VSX(s) together doesn't create a VSX of VSX(s) (a cluster of clusters), you just have two VSX(s) interconnected together (on each VSX you will have to setup MC-LAGs, one on each VSX member of that particular VSX cluster hosted on that particular site, these two MC-LAGs of the VSX on the left site will form the LAG that will be used to connect to the corresponding LAG formed on the VSX on the right side (again, in that side the VSX will have its MC-LAGs, one per VSX member, to connect to the left side).
Given the above you have just interconnected the left VSX with the right VSX. If you have other devices those ones need to connect (and terminate their links) to each VSX and only there...you can't go from, example, CC2 and VSX on the left with one downlink and VSX on the right with the other downlink (as pictured)...but you can go from CC2 to VSX on the left (or on the right) with both of its downlinks spreading into VSX members of the same VSX (say one CC2 downlink to left VSX top member and the other downlink to the left VSX bottom member).
Technically - having a lot of links between the sites - you can also create other downlinks to the right VSX...but...doing so you will form a loop (CC2 <-> Left VSX <-> Right VSX <-> CC2) and I don't believe that is something you want architecturally speaking.
So, to recap, if from CC2 you have a LAG, its downlinks to VSX clusters (on Left and Right sites) can go from:
- CC2 to, respectively, concurrently Left VSX Top and Bottom members <- OK
- CC2 to, respectively, any Left VSX member AND any Right VSX member <- Not OK
The same is valid for CC3 and CC4, always speaking about a LAG (and its member links) going to your two sites.
A side note: you can connect CC2 via standalone downlinks (non LAGged) to - say - one member of Left VSX and one member of Right VSX but expect that one of the two downlinks will be blocked (since that's a loop)...so, in the end, you will have a CC2 connected and forwarding to only one site at time (forwarding will not happen concurrently)...this if STP is working correctly (remember that I assumed that, for this particular case, you are not dealing with a LAG from CC2...).
Original Message:
Sent: Feb 01, 2023 05:18 AM
From: Julio
Subject: How can i connect 4x8325? VSF and VSX
So if I want to use a LAG between them towards other wiring centers, would it be possible?

Original Message:
Sent: Jan 31, 2023 11:47 AM
From: parnassus
Subject: How can i connect 4x8325? VSF and VSX
Hi, why three VSX Stacks? you have to create two VSX (on each site the VSX shall be made by 2 Aruba 8325) and interconnect them "back-to-back" (using Multi-Chassis LAGs as known as VSX LAGs).
Have a look at VSX Best Practices Guide, at the end there is an example where two VSX, each one operating in a specific site, are interconnected via four physical links through VSX LAGs.
Original Message:
Sent: Jan 31, 2023 11:24 AM
From: Julio
Subject: How can i connect 4x8325? VSF and VSX
But then i have to create three vsx stack?
I am reading that VSX only can on two devices
Original Message:
Sent: Jan 31, 2023 11:16 AM
From: jkupski
Subject: How can i connect 4x8325? VSF and VSX
The 8325 does not support VSF. Your correct configuration here would be two VSX clusters.
Original Message:
Sent: Jan 31, 2023 07:56 AM
From: Julio
Subject: How can i connect 4x8325? VSF and VSX
Hi.
I have to build a core with 4 8325s, 2 in one location and the other two in another location. Is it possible to make a Stack between 2 using VSF? Thus we would only have 2 logical units with which VSX could be mounted.
In the figure below you can see what I mean.