Controller Based WLANs

Why does my AP act like a DHCP server after an upgrade to ArubaOS 5.0.0.0?

Aruba Employee

Product and Software: This article applies to an Aruba access point that is connected through its second Ethernet port Enet1 as its uplink and ArubaOS 5.0.0.0 build 23711.

 

Issue
After software has been upgraded to ArubaOS version 5.0.0.0 build 23711, an access point (AP) that is connected through its second Ethernet port Enet1 is unable to successfully terminate on the controller and fails to come online. Instead the AP begins to function as a DHCP server and hands out IP addresses to the wired devices connected to the same network segment as itself.

 

Symptoms
After the upgrade to Aruba OS 5.0.0.0:

  • The AP does not bring up its radios and appears to be in a down state on the controller.
  • Wired devices on the same network segment as the AP receive IP addresses in the subnet 192.168.11.0/24 with a default gateway of 192.168.11.1.

 

Workaround
These workarounds are available to prevent this issue before or after the upgrade to ArubaOS 5.0.0.0 and bring the AP online.

  • Before you upgrade to ArubaOS 5.0.0.0 build 23711:

o Reconnect the AP through its Enet0 port.

OR

o If the AP uses DHCP option 43 or ADP to discover the master controller IP address, reprovision it with the master controller's IP address statically.

  • After you upgrade to ArubaOS 5.0.0.0 build 23711, the only workaround is to reconnect the affected AP through its Enet0 port.

 

Notes

  • A fix for this issue is currently in the works and is expected to be integrated into ArubaOS 5.0.0.1.
  • This issue is not experienced in ArubaOS versions prior to 5.0.0.0 OR if the AP is connected through Enet0 port as its uplink.
Version history
Revision #:
1 of 1
Last update:
‎07-05-2014 03:49 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.