Hi Brian, Active Gateway concept on ArubaOS-CX has nothing to do with a well formed (working) VSX LAG. A VSX LAG (you can call it Multi-Chassis LAG but the current nomenclature should be VSX LAG despite the command is for "multi-chassis") is a logical interface containing physical interfaces on each VSX node.
Let me suppose this scenario (here I imply that a VSX is already well formed):
VSX Node 1 (Primary role) has the VSX LAG lag1 (active = LACP) made of interface 1/1/1
VSX Node 2 (Secondary role) has the VSX LAG lag1 (active = LACP) made of interface 1/1/1
Then a peer device (say a Switch, as example) can be concurrently connected to interface 1/1/1 on VSX Node 1 and 1/1/1 VSX Node 2 by using a normal Link Aggregation made of two matching physical interfaces (the LAG should be configured with LACP, to match the LACP configuration on the VSX side).
In this way you have a peer device (Host, Switch, etc.) which is concurrently connected to two separate physical entities (VSX Node 1 and VSX Node 2) as it would be connected to a single logical entity (the magic is done by the VSX), which is an essential requirement for LAG (static or LACP) to work.
------------------------------
Davide Poletto
------------------------------
Original Message:
Sent: Dec 07, 2021 03:32 PM
From: Brian Moebius
Subject: Aruba 8320 LAG config for Server 2019
It is a very simple setup, there isn't much else to the config. I guess coming from 2920's this seems almost greek to me.
interface 1/1/51 no shutdown lag 128interface 1/1/54 no shutdown lag 128interface 1/1/33 no shutdown lag 8
I also saw some tech articles where an active gateway was configured but I was not sure the need.
What does mclag-interfaces do? I will dig to see in the mean time.
------------------------------
Brian Moebius
Original Message:
Sent: Dec 07, 2021 02:57 PM
From: Dustin Burns
Subject: Aruba 8320 LAG config for Server 2019
Can you share the full config for those links? You have your multi-chassis lag config there, but what about the port level config?
I would also suggest you add mclag-interfaces to your vsx-sync: "vsx-sync mclag-interfaces copp-policy dns snmp static-routes time"
------------------------------
Dustin Burns
Lead Mobility Engineer @WEI
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2021
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Dec 07, 2021 10:31 AM
From: Brian Moebius
Subject: Aruba 8320 LAG config for Server 2019
Hello, I have been having a hard time trying to get our new Aruba switches configured. I have two switches setup in a vsx stack.
I would like to have them setup with a LAG back to our 5406 using an MC lag.
I would like to have the servers I connect to the stack spread across the two switches.
The server in question is a 2019 Server setup with a nic LACP team using Dynamic load balancing. This was working on our older switch stack. Should the server be setup to switch independent instead of load balancing?
When I connect the server to the 8320's connectivity is iffy.
The new CLI has thrown me for a loop, not to mention Aruba Central wiping out my config once I connected the devices....
Here is the config for the related devices:
interface lag 1 multi-chassis no shutdown description 'MC Lag to 5406 Core' no routing vlan trunk native 1 vlan trunk allowed all lacp mode activeinterface lag 8 multi-chassis no shutdown description veeamproxy no routing vlan trunk native 32 vlan trunk allowed all lacp mode activeinterface lag 128 no shutdown description VSX-Link no routing vlan trunk native 1 tag vlan trunk allowed all lacp mode activeinterface 1/1/1 no shutdown description hearbeat-link ip address 192.168.255.1/24 ipv6 address link-localvsx inter-switch-link lag 128 role primary keepalive peer 192.168.255.2 source 192.168.255.1 vsx-sync copp-policy dns snmp static-routes timeip route 0.0.0.0/0 vlan1 10.3.1.1
------------------------------
Brian Moebius
------------------------------