Wireless Access

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

please do let us know

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
------------------------------

Original Message:
Sent: Apr 11, 2021 09:52 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

Have you ruled out it is not an issue with the DHCP server by seeing if the issue persists on the wired side? What does a pcap show on both the client and the firewall? Do you have any broadcast/multicast controls configured under your WLAN Profile?

------------------------------
Craig Syme
------------------------------

Original Message:
Sent: Apr 11, 2021 10:56 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

please do let us know

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 11, 2021 09:52 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

@ariyap - No difference after the firmware downgrade to 8.7.1.3

@Craig Syme - Hi Craig, appreciate the response. We did have a client plugged in on the wired side, but for Wireshark pcap. (There's a lot of data to sift through, but couldn't find anything relating to the problem during the pcap)

The issue occurs on both the Guest and Staff SSID's, and the staff SSID uses Windows DHCP as opposed to the Fortigate DHCP for the Guest. We also swapped in Windows DHCP for the Guest SSID and still experienced the issues, not to mention that we have had Cisco and Ubiquiti AP's running successfully before the Aruba's came in. Pretty confident it's not the DHCP server causing the problems.

The Broadcast/Multicast settings are just the defaults, see attached screenshot. Anything particular on this end we should be looking out for?
​​
Original Message:
Sent: Apr 12, 2021 05:11 AM
From: Craig Syme
Subject: Aruba Central + AP515's = DHCP Timeouts

Have you ruled out it is not an issue with the DHCP server by seeing if the issue persists on the wired side? What does a pcap show on both the client and the firewall? Do you have any broadcast/multicast controls configured under your WLAN Profile?

------------------------------
Craig Syme

Original Message:
Sent: Apr 11, 2021 10:56 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

please do let us know

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 11, 2021 09:52 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

Hi Everyone,

We also have this issue, some clients don´t get their IP address, we have 34 AP515 and the DHCP server is on a Sophos XG Firewall

Does anybody have seen this issue and know a solution? @ST69 - Did you solve this?

Any help will be much appreciated, thanks​

------------------------------
Samy Masihy
------------------------------

Original Message:
Sent: Apr 15, 2021 07:50 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

@ariyap - No difference after the firmware downgrade to 8.7.1.3

@Craig Syme - Hi Craig, appreciate the response. We did have a client plugged in on the wired side, but for Wireshark pcap. (There's a lot of data to sift through, but couldn't find anything relating to the problem during the pcap)

The issue occurs on both the Guest and Staff SSID's, and the staff SSID uses Windows DHCP as opposed to the Fortigate DHCP for the Guest. We also swapped in Windows DHCP for the Guest SSID and still experienced the issues, not to mention that we have had Cisco and Ubiquiti AP's running successfully before the Aruba's came in. Pretty confident it's not the DHCP server causing the problems.

The Broadcast/Multicast settings are just the defaults, see attached screenshot. Anything particular on this end we should be looking out for?
​​
Original Message:
Sent: Apr 12, 2021 05:11 AM
From: Craig Syme
Subject: Aruba Central + AP515's = DHCP Timeouts

Have you ruled out it is not an issue with the DHCP server by seeing if the issue persists on the wired side? What does a pcap show on both the client and the firewall? Do you have any broadcast/multicast controls configured under your WLAN Profile?

------------------------------
Craig Syme

Original Message:
Sent: Apr 11, 2021 10:56 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

please do let us know

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 11, 2021 09:52 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?

@wintechie

Still working on the issue, no real solution at this point.

The ​issue being sporadic has really made it an absolute pain to troubleshoot.
Means we can't just turn on logging and replicate the issue at will​.
Original Message:
Sent: Jun 17, 2021 02:02 PM
From: Samy Masihy
Subject: Aruba Central + AP515's = DHCP Timeouts

Hi Everyone,

We also have this issue, some clients don´t get their IP address, we have 34 AP515 and the DHCP server is on a Sophos XG Firewall

Does anybody have seen this issue and know a solution? @ST69 - Did you solve this?

Any help will be much appreciated, thanks​

------------------------------
Samy Masihy

Original Message:
Sent: Apr 15, 2021 07:50 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

@ariyap - No difference after the firmware downgrade to 8.7.1.3

@Craig Syme - Hi Craig, appreciate the response. We did have a client plugged in on the wired side, but for Wireshark pcap. (There's a lot of data to sift through, but couldn't find anything relating to the problem during the pcap)

The issue occurs on both the Guest and Staff SSID's, and the staff SSID uses Windows DHCP as opposed to the Fortigate DHCP for the Guest. We also swapped in Windows DHCP for the Guest SSID and still experienced the issues, not to mention that we have had Cisco and Ubiquiti AP's running successfully before the Aruba's came in. Pretty confident it's not the DHCP server causing the problems.

The Broadcast/Multicast settings are just the defaults, see attached screenshot. Anything particular on this end we should be looking out for?
​​
Original Message:
Sent: Apr 12, 2021 05:11 AM
From: Craig Syme
Subject: Aruba Central + AP515's = DHCP Timeouts

Have you ruled out it is not an issue with the DHCP server by seeing if the issue persists on the wired side? What does a pcap show on both the client and the firewall? Do you have any broadcast/multicast controls configured under your WLAN Profile?

------------------------------
Craig Syme

Original Message:
Sent: Apr 11, 2021 10:56 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

please do let us know

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 11, 2021 09:52 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

Have already tested some AP's on their own isolated VLAN; issues persisted.
We've already downgraded firmware previously and found no difference, but it's little effort so will downgrade to 8.7.1.3 to see what happens.


Original Message:
Sent: Apr 10, 2021 06:43 PM
From: Ariya Parsamanesh
Subject: Aruba Central + AP515's = DHCP Timeouts

it is always recommended for the IAPs to have their own mgmt VLAN.
Also i would suggest to run the AP-515s on either 8.6.0.9 or 8.7.1.3 as a starting point.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.

Original Message:
Sent: Apr 07, 2021 11:28 PM
From: Steven Tonkin
Subject: Aruba Central + AP515's = DHCP Timeouts

So we've recently rolled out 16 x Aruba AP-515's, configured via Aruba Central.

It all seemed to work fine at first, but it quickly became apparent that there are sporadic DHCP Discover, and Offer timeout errors.
There are also reports of poor performance, frequent disconnections and DOT1X errors in the Aruba Central logs (these could just be certificate or credential mismatches)

Our Environment:

- Aruba CX 6405 switch; AP's are directly connected to this.
- Fortigate 200D cluster; handles the DHCP for the Guest SSID.
- Two Windows 2016 DC's that handle the DHCP for the Staff SSID. They also do RADIUS for the Staff SSID.
- Aruba Central as the controller.
- Other sites are still running Cisco AP's.

The Aruba AP's replaced Cisco Aironet AP's which worked without issue. 

Some troubleshooting steps taken:

- Installed the Aruba AP's in another office to take the CX 6405 switch out of the equation.
- Went back to WPA2 instead of WPA3.
- Turned off Fast Roaming, Wi-Fi Multimedia Power Save (U-APSD), Management Frame Protection.
- Turned off LACP mode on each AP.
- Turned off Enforce DHCP, 80MHz support.
- Setup a different DHCP server.
- Created completely separate VLAN's for the Aruba's to make sure the Cisco controller and AP's weren't interfering.
- Updated the firmware on the AP's to 8.8.0.0_79697; previously on 8.6.0.4 and 8.6.0.8.

All these changes have made no difference, and working with Aruba Support has led us nowhere.
Has anyone encountered this issue before and have any ideas on how to continue troubleshooting?