APs do not preserve a new profile upon restart

[Tiago_Juliano_F]

Hello! I need to migrate APs from one native Vlan to another (from VLAN 1 to 10). I make the settings for Wing 5.8 by creating a new profile (ap-7532-new) and setting the VLAN settings. Everything seems to work, the AP adopts the correct IP but when it restarts it goes back to the previous profile (default-ap3572).

I make sure I commit and save but still do not maintain the new Profile settings.

Procedures:

- I created the new profile in Configuration-Profiles
- I set Ethernet Ports and Virtual Lan for my scenario
- In the specific Device I set the Profile

Did I forget something?

[ckelly]

As far as I can see here, the AP should be getting a DHCP lease on VLAN-911.

So....if the AP is able to use VLAN-911 to MiNT connect to the controller using VLAN-911, then there shouldn't be a problem. This would mean that VLAN-911 is able to pass MiNT UDP port 24576 traffic all the way back to the controller (and back again in the other direction).

To continue testing, what would be the MOST helpful here is if you can connect to the AP remotely while it's connected. (SSH)
Are you able to find the IP address of the AP when it gets into the condition where it has lost its adoption? If so, we can verify a lot things and figure out where the breakdown is.

[Tiago_Juliano_F]

Keep the same settings as the previous profile, setting only the interfaces

[Tiago_Juliano_F]

Here the new profile settings:

profile ap7532 default-ap7532new
ip name-server 200.XXXXXX
ip name-server 200.XXXXXX
autoinstall configuration
autoinstall firmware
load-balancing balance-channel-loads 2.4ghz
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

interface radio2
description Radio2
beacon dtim-period 1
antenna-gain 15.0
max-clients 100
interface ge1
description "Uplink Radios"
switchport mode trunk
switchport trunk native vlan 20
no switchport trunk native tagged
switchport trunk allowed vlan 1,10,20
interface vlan20
ip address dhcp
ip address zeroconf secondary
ip dhcp client request options all
interface pppoe1
use firewall-policy default
ip dns-server-forward
logging on
logging host XXX
controller host XXX pool 1 level 1
controller host XXX pool 1 level 1
no lldp med-tlv-select power-management
no configuration-persistence
no auto-learn staging-config
service pm sys-restart
router ospf

[ckelly]

It sounds like the new Profile is successfully being pushed out to the APs, but then when the APs attempt to use the new Profile and realize that they can no longer re-adopt to the controller, they are automatically reverting back to their previous configuration. This is expected behavior.
You have some sort of problem with the new Profile/config that is preventing the APs from being able to re-adopt.