I think I got it! After some testing, I've made some changes. I put the center 4 cores as MC-LAG and the outer cores as normal lags with lacp mode active. So far all redundancy is working. When I did all cores as MC-LAG they wouldn't communicate at all. Let me know what y'all think, honestly lol. I'm pretty new at this so bare with me!
Original Message:
Sent: Aug 28, 2023 09:17 AM
From: MoJoPBS
Subject: 8325 True Redundancy
Of course! I haven't been able to get back out into the field (my off network sandbox) to pull the configurations. Below and attached see a quick drawing of how I lagged it. I haven't used MC-LAGs, when I did LACP kept blocking all of the ports. I'll be going out later today and finish testing. The current configuration is working, but it did begin to loop when I was testing the redundancy. Appreciate the advise!
Original Message:
Sent: Aug 25, 2023 04:46 AM
From: parnassus
Subject: 8325 True Redundancy
Please show us sanitized running configurations of (at least) two VSX (and, at least, the part relevant to involved VSX LAGs on both VSX ends). Help us to help you.
Original Message:
Sent: Aug 24, 2023 11:50 AM
From: MoJoPBS
Subject: 8325 True Redundancy
I have! I keep running into the issue, I configure the ports as VSX LAG, however it keeps saying LACP BLOCK. I know I'm missing something somewhere!! Appreciate the help!
I made a normal lag and it does work, but when pinging the other set of 8325s, I get DUP! in the pings every now and then.
Original Message:
Sent: Aug 23, 2023 06:09 PM
From: parnassus
Subject: 8325 True Redundancy
As said, I don't see any evident loop between those four VSX deployments...and, in any case (as a best practice), a design employing one pair (or more pairs) of switches deployed as a VSX...it should also use a VSX LAG approach (Multi-Chassis LAG or MC-LAG, abbreviated) to fully benefit of the VSX features...and that either when you consider interlinking two VSX together or when you consider connecting any other peer device (server, switch, etc.) to a VSX.
Have you read the VSX Best Practice guide?
Original Message:
Sent: 8/23/2023 5:47:00 PM
From: MoJoPBS
Subject: RE: 8325 True Redundancy
Hmm, I see, any advice on configuring? I'm having a hard time understanding if i'll do MCLAG or how i'll go about not causing a loop.
Original Message:
Sent: Aug 23, 2023 05:42 PM
From: parnassus
Subject: 8325 True Redundancy
Hi! your scenario is totally possible (what I recognize are: 4 VSX interconnected without loops).
Layout: the top left VSX has two downstream central VSX on the bottom, of these two central VSX the top one is the connected upstream to the top right VSX (while the bottom VSX is not).
Original Message:
Sent: 8/23/2023 5:10:00 PM
From: MoJoPBS
Subject: 8325 True Redundancy
It's a pretty rough drawing, but I'm looking to have true redundancy for our network. I could use a little advice on how I should go about doing this, and if it's even possible. An aruba engineer said it could be done, but so far I'm scratching my head. Any advice?
