Deployment model: APs and controller are remote to each other and not in the same broadcast domain.
- The APs in the profile on the controllers are configured as DHCP clients, but the parameter to allow them to obtain gateway/DNS information is missing so when the AP comes in, is adopted and and pulls the config, it will then disconnect due to missing default gateway information, lose connection to the controller and not be able to ping it. At point the AP will reboot into the last know good configuration in an attempt to reestablish the connection to the controller.
- The AP will be able to ping the gateway since the latter is in the same broadcast domain, but no traffic will be allowed through.
- Make sure that the setting to allow the APs to pull gateway and DNS information is configured in the AP profile on the controller, as such:
- From WebUI:
- From the Configuration tab go to Profiles >> Select profile >> Click Edit >> Expand Interface from the menu tree >> Virtual Interfaces >> Select the Native VLAN and Edit >> IPV4 tab >> IPV4 Addresses >> Use DHCP to obtain Gateway/DNS Servers >> Check the box
- From CLI
- SSH into the controller and run the following commands:
Enter configuration commands, one per line. End with CNTL/Z.
#profile <ap-model> <profile-name>
#ip dhcp client request options all