Okay...so what’s happened is that the AP received the config….but then as part of the new config, it was no longer able to stay adopted to the controller….so it reverted back to the previous config (which is likely just an empty default config). So the question now is, why can’t the AP remain adopted with the new config? Looks like a VLAN config issue.
Look at the AP’s Profile on the controller - in the VLAN1 section. There’s nothing.
So when the AP receives this profile after being adopted, it’s NOT being instructed to behave like a DHCP client.
Even if it DID have an IP address, it can no longer discover the controller using layer-2 because the controller is then on a different subnet, so it then also needs a controller host entry. The easiest way to do this would be to add the entry to the AP’s Profile...so we’ll take care of both of these issues.
Enter these commands and add these three lines *in BOLD* to the AP Profile
login to CLI on controller
enable
config
profile ap4600 ap4600_Hof
interface vlan 1
ip address dhcp
ip dhcp client request options all
exit
controller host 10.216.0.199
commit write
The Profile will then look like this:
profile ap4600 ap4600_Hof
no autoinstall configuration
no autoinstall firmware
crypto ikev1 policy ikev1-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ikev2 policy ikev2-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
crypto ikev1 remote-vpn
crypto ikev2 remote-vpn
crypto auto-ipsec-secure
crypto load-management
crypto remote-vpn-client
interface radio1
wlan hof bss 1 primary
interface radio2
wlan S-Inet bss 1 primary
interface ge1
ip dhcp trust
qos trust dscp
qos trust 802.1p
interface vlan1
ip address dhcp ← Will be under ‘interface vlan 1’
ip dhcp client request options all ← Will be under ‘interface vlan 1’
interface pppoe1 use firewall-policy default
controller host 10.216.0.199 ← Will appear *somewhere* in this AP profile. Look for it
service pm sys-restart
!
Now again, delete the AP from the system as before and then reboot the AP.
This time, the AP should then get an IP address and will know how to reach the controller using layer 3.
