Shows the current status of the cluster, whether operating as L2 or L3. Clusters should ALWAYS be operating in L2 for normal operations. If the cluster is operating in L3 mode, then the most likely culprit is a lack of visibility on one or more VLANs. Always add VLANs at the switch side first, making sure to span the VLAN to all necessary ports/switches so that all cluster members have access. Then add the VLAN to the cluster members, preferably at a group level so that all cluster members get the exact same configuration.
When cluster VLAN probe is failing on a VLAN, the status can be checked to figure out which VLAN is failing. This will only show one failing VLAN at a time so you could potentially have to check multiple times if there are multiple VLANs with issues. Best option is to check this at each cluster node.
At a bare minimum you probably need to exclude VLAN 1 from the VLAN probes. All VLANs not used for client connectivity should be excluded from the probes.
The bucketmap determines the mapping of client MAC address to UAC. Technically the decision for that mapping is done well before the client is connected, and gets updated based on cluster membership.
Original Message:
Sent: May 10, 2024 01:12 PM
From: alexb
Subject: Random clients not getting DHCP address
A missing client VLAN in the switch trunk port on one of the controllers in the cluster was the Root Cause.
If clients connect to the controllers with correct vlans, they work.
If clients connect to the controller with the missing vlan, DHCP fails.
It looks like once the client mac is added to the user table, it is permanently mapped to a host controller.
But because we can randomize the mac-address for Windows and mobile devices, we can get it to work.
As for Macbooks, once it fails we could not get it to work and no workaround.
Does anyone know where I can find documentation on Controller clustering or AP/Client Tunnels if there is any?
Thanks,
Original Message:
Sent: May 06, 2024 08:31 AM
From: alexb
Subject: Random clients not getting DHCP address
Hey Matt,
We see the issue on different devices. There's workarounds for Mobile devices and Windows clients, but our main problem now are Macbooks. If I take any of the problematic device to another floor with the old wireless they work just fine. Once I bring them back to where the new Aruba wireless has been migrated they don't work. Opened a case with TAC now and trying to capture E2E traffic to where bootp is failing.
Original Message:
Sent: May 03, 2024 09:51 AM
From: Matt_C
Subject: Random clients not getting DHCP address
Alex, what devices did you have to do that on? We are getting the exact same thing on our 6300M and 6200 switches at one of our schools. We run almost entirely Apple equipment which in this case are Ipads, tv's and a few Macbooks.
Original Message:
Sent: May 02, 2024 07:56 AM
From: alexb
Subject: Random clients not getting DHCP address
We figured it out.
For some reason some devices need 'Random Mac addressing' feature enabled.
Not sure why this is the case but as soon as we enable it, clients are able to obtain IP address.
Original Message:
Sent: Apr 25, 2024 07:20 AM
From: alexb
Subject: Random clients not getting DHCP address
Hi Carson,
Everything is working and we have hundreds of APs and thousands of clients.
The issue is that we are slowly migrating wireless from another vendor to Aruba.
Majority of devices work after the migration, but a handful of devices just wont get DHCP with Aruba.
If I move the device to the old wireless network, those same devices work just fine.
I will open a TAC case and get them involved.
Thanks!
Original Message:
Sent: Apr 24, 2024 02:39 PM
From: chulcher
Subject: Random clients not getting DHCP address
Have you opened a case with TAC?
Are the APs connecting to a cluster? How many nodes? How long have the nodes been online?
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Apr 24, 2024 11:11 AM
From: alexb
Subject: Random clients not getting DHCP address

Original Message:
Sent: Apr 17, 2024 12:36 PM
From: alexb
Subject: Random clients not getting DHCP address
Hello all,
We are running 8.10.0.10.
I have a few devices, Macbooks/Windows laptops that pass authentication but wont get DHCP.
These devices work with other non-Aruba wireless but not sure why DHCP fails when connecting to Aruba.
So far, the issue looks isolated since we have thousands other clients that work just fine.
I tried 'sudo ifconfig en0 ether <random mac>' on Macbook but failed so I couldnt verify if issue is tied to specific Mac address.
Anyone else seen this or have a workaround?
Thanks,
Alex