Wired Intelligent Edge

Hello
I have a really simple scenario
I got 2 8320
The config of the two 8320 is really simple:  Vlans, Trunks, and in one interface VLAN the management VLAN, that's it, they do not take routing decisions.   The routing decisions are taken by the upstream Layer 3 switch.   For now, it will stay like this.

We got a few switches connected  to 1 8320  and others to the other 8320
We also have some servers connected to 1 8320 and others to the other 8320

We would like to configure VSX for redundancy 

This way we can configure a link aggregation from the other access switches connected to it, and if one of the 8320 fails the access switch will still have a connection to the network.   The same will happen with the L3 switch which is routing now, we will build an LACP to those 8320s in VSX so that if one fails everything keeps working.

As for the server part, I'm not sure about that because I don't know too much about it.   But I believe they can build their own LACP ( is this correct?)

In summary  that's what we would like to achieve 

I have been reading some  and I think you have to:

1-Build the ISL between the 8320s 
2-Configure the keep-alive
3-Configure the VSX and assign a primary and a secondary.

Anyone can help with an example of a config?

I'll keep reading to see if I can post a draft of the config,  but if someone posts it before that would be great too.

As a note, all the other switches around these 8320 are NOT Aruba HPE they are other brands.

Take a look at the VSX Guide
https://www.arubanetworks.com/techdocs/AOS-CX/10.10/PDF/vsx.pdf
"Setting up the VSX environment" has sample configs

------------------------------
DWan
------------------------------

Hi!

Have a look at this Aruba VSX Configuration Best Practices for Aruba CX 6400, 8320, 8325, 8360 and 8400 Technical Whitepaper (Edition 1.3 December 2020). I believe that reading it you will be able to find answers to most (if not all) of your questions.

And for your doubt: "As for the server part, I'm not sure about that because I don't know too much about it. But I believe they can build their own LACP ( is this correct?)" Yes, it's correct...any peer LACP capable peer device (a Switch, a Server, etc.) should connect to the VSX by means of a LACP-controlled Links Aggregation logical interface (So a LAG with at least one physical link terminating into VSX Primary and one other physical link terminating into VSX Secondary).

Thanks, you all, let me check the links
Original Message:
Sent: Oct 15, 2022 08:51 AM
From: Davide Poletto
Subject: VSX Config example

Hi!

Have a look at this Aruba VSX Configuration Best Practices for Aruba CX 6400, 8320, 8325, 8360 and 8400 Technical Whitepaper (Edition 1.3 December 2020). I believe that reading it you will be able to find answers to most (if not all) of your questions.

And for your doubt: "As for the server part, I'm not sure about that because I don't know too much about it. But I believe they can build their own LACP ( is this correct?)" Yes, it's correct...any peer LACP capable peer device (a Switch, a Server, etc.) should connect to the VSX by means of a LACP-controlled Links Aggregation logical interface (So a LAG with at least one physical link terminating into VSX Primary and one other physical link terminating into VSX Secondary).