Wireless Access

Dear all

  i have to deploy Aruba VMC on VMware Esxi 5.5. the vmware host have 2 Physical NIC connect to L3 Switch via Trunk interface of both.

In the vSwitch0 security configuration "Promiscuous Mode:Accept, MAC Address Changes:Accept, Forged Transmits:Accept" and NIC teaming "NIC1 and NIC2 : Active"  

device can connected ssid but can't get dhcp but

when we disconnect NIC2 everting working fine.

Please guide me to fix problem. 

thank you.

Additional information.

we just implement Aruba Virtual Controller version 8.3.0.4 VMWare ESXi 5.5,

from the Switch we connected 2 network cables to ESX server NIC1 and NIC2,

On switch side, we configured trunk port allowed all VLAN on both ports.

VMWare Host side, we configured Standard vSwitch allow all VLAN 4095, assign this port group to Aruba vitual controller VM. set NIC Teaming following the Aruba document.

our symptom is when we try to connect wireless SSID with 2 NIC network connected. the client cannot get the dhcp and cannot to wireless.

and when to disconnect on NIC network interface on VMWare.

This time we can connect to Wireless successfully.

please advise, what is the cause, and how to resolve this.

if you need more information, please let me know.

Thank you.

Please check the Hashing alogrithm of the Vswitch. It is only working with "Route based on Orginating PortID" or with "Explicit Failover" (which is does only failover and no loadbalancing) . Please check also, if 

ReversePathFwdCheckPromisc’ is enabled on the ESXI Host. See also the installation guide of the controller and the VMWare l2 Security Guide. In my cases, changing the algorithm, and setting the reversepathcheck helped.

Attachment(s)

VMWare L2 Security Settings Requirements.pdf   992 KB 1 version

In addition to choosing the right hashing algo, I'd like to point out that setting ReversePathFwdCheckPromisc=1 is mandatory if you use

a)  active / active NIC team with no link aggregation

b)  active / standby NIC team

In fact setting ReversePathFwdCheckPromisc=1 will not harm the situation where there is link aggregation (or trunk/static port channel etc.), so best to just enable it anyways.

With that said, here's a possibly related question - what kind of NIC do you have in the VM server (specific model).