Hi, I am trying to reboot a AP-205 from 7030 Controller running ArubaOS 22.214.171.124. The AP-205 is keep showing Down state. I am not able to ping the AP-205.
Inspect the controller log we spot
Mar 14 15:08:15 stm: <305058> <WARN> |stm| AP DSG03AP08: Drop hello message from 10.8.2.21 with different MAC, old MAC 94:b4:0f:c1:7e:1a, new MAC 94:b4:0f:cb:2d:5c.
where the new MAC is the AP205 mac address while the old MAC is the MAC address belong to DSG03AP08.
The MAC 94:b4:0f:cb:2d:5c is belong to the AP-205 being boot.
Any insight to the problem? I have attached the controller log for your reference.
Are you using static ip addresses or DHCP for your devices?
We are using the DHCP for the devices.
Seems that is problem also exists for AP-225. I have attached the bootlog for AP-225.
Is there a NAT boundary between your access points and your controller? (a router?) The messages indicate that two devices are sharing the same source port, like if they are behind a NAT device.
Can you please open a TAC case and PM me the ticket#?
The issue seems to be ip conflict issue. The microsoft DHCP Server in our network reboot without notice. An AP reboot and request IP and server DHCP assigned an IP without knowing that it has been assigned prior to the reboot. As a result, AP boot failed. We need to reboot all the AP in our network.
I am just wonder if there are any recommendations from Aruba to prevent this siutation from happening again. Anyway that we can prevent AP reboot after the DHCP restart?
Unfortunately, there is no built-in protection for this. The Aruba access point depends on getting a valid ip address from your infrastructure. If it does not get an ip address, as you see, it cannot function.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.