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 188.8.131.52 build 23711.
After software has been upgraded to ArubaOS version 184.108.40.206 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.
After the upgrade to Aruba OS 220.127.116.11:
- 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.
These workarounds are available to prevent this issue before or after the upgrade to ArubaOS 18.104.22.168 and bring the AP online.
- Before you upgrade to ArubaOS 22.214.171.124 build 23711:
o Reconnect the AP through its Enet0 port.
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 126.96.36.199 build 23711, the only workaround is to reconnect the affected AP through its Enet0 port.
- A fix for this issue is currently in the works and is expected to be integrated into ArubaOS 188.8.131.52.
- This issue is not experienced in ArubaOS versions prior to 184.108.40.206 OR if the AP is connected through Enet0 port as its uplink.