Just an update after we managed network traces of a working and none working one yesterday. Unfortunately the LAN and DHCP server is managed by a 3rd party, but I've looked at the config of both and see nothing obvious.
#TROUBLESHOOTING DHCP FORTIGATE CODE#
I've tried different versions of code without resolution.
Looking at LLDP on the switch shows the APs as present. The APs then get caught in the reboot cycle, as they do when they can't locate a controller. Looking at a Wireshark trace of the AP port is seems that the AP gets a DHCP offer which contains the correct option 43 controller address, but it never attempts to connect to the controller (ARP, or unicast), instead seeming to ignore the DHCP resoponse and proceeding to ADP then DNS for 'aruba-master'. With the ones that find the controller, it's then hit and miss as to whether they find their way back after provisioning, although they may also find their way back in future days. Then on subsequent days some of the others start to find their way also, generally around the same time on each day. Now here's the problem some of the APs find the controller and some don't. We are therefore using DHCP option 43/60 in order for the APs to locate the contoller. We are experiencing a weird problem in a number of our new sites and was wondering if anyone had experienced similar.īasically we have a controller based deployment with 225 and 205 APs/ AMs with the controller and APs 元 separated on the LAN.
0 kommentar(er)
