Ap 310i does not get ip address while in AP adoption discovery process.

[Ahmed_101]

Hi all. 
I have a deployment where there are AP310i version 7.7.0.0 and NX5500 running WING 7.9.6.1. 
the 1. problem is that when the AP boots its stuck at  "AP adoption discovery process in progress... To cancel and boot in Standalone mode, type (s): " 
and it does not getsadopted and does not get management ip address. 
when i press "s" and it switches to standalone it works fine and get ip address and being adopted to the controller.
the second problem is that some times the AP does offline in the controller and after some time it coming online again.
what is the problem here ? 

[arichter]

Hello Ahmed, 

did you enable "enforce version-adoption none" on your NX device profile? This would enable the Controller to adopt an AP of different FW. Else, please double check on the Ethernetsettings of the Switch and AP. Seems, that there is something odd (Tagged vs. Untagged) , etc. Are NX & AP in same Layer 2 domain ? Thanks for some more details.

[Ahmed_101]

Hi, 
i yes i enabled enforce version-adoption none on the nx device, the edge switches that the APs is connected to is ERS 3650 switch 
so i used this configs in the switch : 
vlan members add 118,113 48 (113 is the management vlan and 118 is the user vlan, 48 is the port that the AP is connected to the switch)
vlan port 48 pvid 113
vlan port 48 tagging untagpvid only
and in the AP310 profile in NX i configured the ethernet port as tagged and allowed the vlans 113,118 and the native vlan is 113 (not tagged) when i tried to set the native vlan to 1 the AP does not gets ip address at all so i configured the native vlan as 113 
and in the profile i created the vlan 113 and 118 and configured the ip option of the vlan 113 as dhcp.
is there a problem with this setup ? 
Thanks.