Wired Intelligent Edge

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

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

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

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

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

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

Don't use LACP with vSS ! it is not needed !

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

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

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

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

What is the configuration on the vSwitch side regarding distribution of traffic to the various NICs (teaming and failover policy)? Are they all "active" or do you have an active/standby setup? What is the load balancing algo you selected? Do you see the MAC addresses of the VMs not reachable in the MC-LAG interface?

Be aware that depending on the load balancing you configure you need or you dont need any special config on the physical switch. Please refer to VMware's documentation for further details. 

Regards, 
Thomas

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

All NICs are in Active mode. Load balancing algo is "Route based on IP hash". All 4 NICs are up and are in static bundle. When I ping vmWare host from Core switch primary, host is responding and when I ping vmWare host from Core switch secondary, host is not responding. However ARP is getting resolved on both switches on interface LAG50 with same MAC address.

What is the configuration on the vSwitch side regarding distribution of traffic to the various NICs (teaming and failover policy)? Are they all "active" or do you have an active/standby setup? What is the load balancing algo you selected? Do you see the MAC addresses of the VMs not reachable in the MC-LAG interface?

Be aware that depending on the load balancing you configure you need or you dont need any special config on the physical switch. Please refer to VMware's documentation for further details. 

Regards, 
Thomas

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

For vsphere standard vswitch (i.e. no LACP), the best approach I would recommend is to not configure LAG at all and have each vmnic being connected to the switches as a standalone NIC, with just regular VLAN trunking. This should give best outcome. 

All NICs are in Active mode. Load balancing algo is "Route based on IP hash". All 4 NICs are up and are in static bundle. When I ping vmWare host from Core switch primary, host is responding and when I ping vmWare host from Core switch secondary, host is not responding. However ARP is getting resolved on both switches on interface LAG50 with same MAC address.

What is the configuration on the vSwitch side regarding distribution of traffic to the various NICs (teaming and failover policy)? Are they all "active" or do you have an active/standby setup? What is the load balancing algo you selected? Do you see the MAC addresses of the VMs not reachable in the MC-LAG interface?

Be aware that depending on the load balancing you configure you need or you dont need any special config on the physical switch. Please refer to VMware's documentation for further details. 

Regards, 
Thomas

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

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.

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

Hi, thanks for your response. kindly find the requested cmds output.

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.

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

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!

Hi, thanks for your response. kindly find the requested cmds output.

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.

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.

Don't use LACP with vSS ! it is not needed !

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

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

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

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

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

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

Sorry, you have to uselize vSphere Distributed Switch for LACP

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

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

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

Hi, we are not using LACP. We configured static bundle and that supports in standard vSphere.

Original Message:
Sent: Apr 18, 2024 04:55 AM
From: Steinar Grande
Subject: Static LAG in VSX Aruba 6400 CX OS for vSphere Standard vSwitches

Sorry, you have to uselize vSphere Distributed Switch for LACP

------------------------------
Steinar

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

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

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