To me it doesn't look like an issue at (VSXI) static LAG level...since both lag50 are up (although when set to static there are less informative output coming from the typical show lacp interfaces command). If vSS side (virtual Standard Switch) side all setting are OK matching those of the VSX LAGs the issue should be at an higher level (routing?).
Original Message:
Sent: Apr 17, 2024 11:16 AM
From: jdjackson@confergeone.com
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
One other thing to check on the VMware side is to make sure the port group is set to "Routed Based On IP Hash" as well. Can you post a screenshot of the VLAN 51 port group?
Typically the port group is set to inherit from the vswitch but just double check, also if it is set to inherit, manually set it to "Routed Based On IP Hash" and see if that fixes the issue. I have run into this issue a few times!
Original Message:
Sent: Apr 16, 2024 08:44 AM
From: it.services@medanta.org
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
Hi, thanks for your response. kindly find the requested cmds output.
Core-Switch(config)# show vsx lacp aggregates lag50
Local-peer Remote-peer
-------------------------------------------------------------------------------
Aggregate name : lag50 (multi-chassis) lag50 (multi-chassis)
Interfaces : 1/3/21 1/3/3 1/3/3 1/3/7
Peer interfaces : 1/3/7 1/3/3 1/3/21 1/3/3
Heartbeat rate : N/A N/A
Hash : l3-src-dst l3-src-dst
Aggregate mode : Off Off
Core-Switch(config)# exit
Core-Switch# show lacp interfaces | in lag50
Actor details of all interfaces:
1/3/3 lag50(mc) up
1/3/21 lag50(mc) up
Partner details of all interfaces:
1/3/3 lag50(mc)
1/3/21 lag50(mc)
Original Message:
Sent: Apr 15, 2024 11:10 AM
From: parnassus
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
Hi! could you paste the output of the CLI commands:
- show vsx lacp aggregates lag50 (executed on both VSX members)
- show lacp interfaces (no matter we are dealing with a static VSX LAG)
Out of curiosity: shouldn't be better to have both the LAGs lag50 (the static VSX LAG lag50 as defined on the VSX Primary and the corresponding static VSX LAG lag50 defined on the VSX Secondary) to use the same "set of member interfaces" (I mean, say lag50: 1/3/3 + 1/3/21 or lag50: 1/3/3 + 1/3/7 on both VSX members instead of, as it is now, VSX Primary lag50: 1/3/3+1/3/21 and VSX Secondary lag50: 1/3/3+1/3/7)? it is not an essential requirement, just a good practice to ease the troubleshooting.
Original Message:
Sent: Apr 15, 2024 07:03 AM
From: it.services@medanta.org
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
Hi, We are not configuring LACP. Doing static aggregation as vmWare vSS doesn't support LACP. Some users are able to ping the vmWare host and some are not. vmWare host has total 4 nics. 2 are connected on primary core switch and 2 are on secondary core switch. both core are connected with VSX. All users get ping reply when we disable 3 nic and leave 1 nic enable on switch.
Original Message:
Sent: Apr 15, 2024 06:48 AM
From: alagoutte
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
Don't use LACP with vSS ! it is not needed !
------------------------------
PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...
PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)
PowerArubaCL: Powershell Module to use Aruba Central
PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..
ACEP / ACMX #107 / ACDX #1281
Original Message:
Sent: Apr 12, 2024 06:31 AM
From: it.services@medanta.org
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches
Hi,
We have 2 Aruba 6405 CX OS switches in VSX. Recently we precured vmWare with standard licenses. We know that LACP does support in this licenses. We configured static McLAG in our Aruba switches and "Routed Based On IP Hash" in vmWare. But after this configuration, vmWare host becomes unreachable. Getting ping response on some random systems. Some users are able to ping and some are not. Even ping reply from vmWare host is coming on primary VSX switch but not on secondary switch however ARP is available on both Cores. These 6405 VSX switches are L3 for users VLAN and Server VLAN.
I checked vmWare documents and found document with sample configuration for Cisco, HP and Dell switches but no document available for Aruba CS OX switches.
Below is switches configuration:
Primary Switch
CORE-SWH-PRI# sh running-config interface lag50
interface lag 50 multi-chassis static
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed 51
exit
CORE-SWH-PRI# sh lag 50
System-ID : d4:e0:53:b1:07:00
System-priority : 65534
Aggregate lag50 is up
Admin state is up
Description :
Type : multi-chassis
Lacp Fallback : Disabled
MAC Address : 02:02:00:00:01:00
Aggregated-interfaces : 1/3/3 1/3/21
Aggregation-key : 50
Aggregate mode : static
Hash : l3-src-dst
LACP rate : n/a
Speed : 20000 Mb/s
Mode : trunk
CORE-SWH-PRI# sh running-config interface 1/3/3
interface 1/3/3
description vmWare
no shutdown
lag 50
exit
CORE-SWH-PRI# sh running-config interface 1/3/21
interface 1/3/21
description vmWare
no shutdown
lag 50
exit
Secondary Switch
CORE-SWH-SEC# sh running-config interface lag50
interface lag 50 multi-chassis static
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed 51
exit
CORE-SWH-SEC# sh lag 50
System-ID : d4:e0:53:b1:87:00
System-priority : 65534
Aggregate lag50 is up
Admin state is up
Description :
Type : multi-chassis
Lacp Fallback : Disabled
MAC Address : 02:02:00:00:01:00
Aggregated-interfaces : 1/3/3 1/3/7
Aggregation-key : 50
Aggregate mode : static
Hash : l3-src-dst
LACP rate : n/a
Speed : 20000 Mb/s
Mode : trunk
CORE-SWH-SEC# sh running-config interface 1/3/3
interface 1/3/3
description vmWare
no shutdown
lag 50
exit
CORE-SWH-SEC# sh running-config interface 1/3/7
interface 1/3/7
description vmWare
no shutdown
lag 50
exit
Also attaching screenshots of vmWare setting.
Kindly correct me if I have done some wrong config or share any reference document if you have.
Thanks