Trying to connect LAP to an WLC - packet tracer

[Naji.AbdelRahman]

so I have been trying to add a new LAP (lightweight ACCESS POINT) to my packet tracer assignment network topology, the network is connected via a multilayer switch that connects WLC with the gateway and the access points, there are already 2 LAP that are connected previously and the CAPWAP status is connected, but when I try to connect another LAP it gives it an ip and its recognized by the WLC in the AP join section that requests is being sent but it doesn't show that its connected, I have tried to connect a console cable to the access, point to troubleshoot it but it doesn't work, anyone have an idea of how to troubleshoot that?

[Flavio Miranda]

Attached your pkt file and we can take a look.  Dont forget to zip it.

[Naji.AbdelRahman]

Sure, thank you in advance for helping!

[Flavio Miranda]

I couldn´t access the L3 switch. I can´t find the  user/pass but take a look in the interface  GigabitEthernet1/0/2.  It seems to me that have not vlan on it.

 I´d like to take a look on  Switch2 if you provide user and pass. I think there might be the answer.

[Naji.AbdelRahman]

in the switch2 you can enter the config field and tap on any gigabitE interface and then go back to the CLI you will automatically be in the privilege mode, the assignment came with secured switch i really don't know why but here you go. 

[Flavio Miranda · Accepted solution]

Got  that.

Well, then I found the problem. The interface of AP 3 was in trunk mode. I just had to change it to access and put it in vlan 100 and the AP joined the WLC. 

Just do it and you´ll be good with that.

[Naji.AbdelRahman]

Thank you soooo much! Appreciated a lot, I saw the other LAPs use trunk port thats why I doubted it, do you know why do we have to use VLAN 100?

[Rich R]

Well as a general rule (on a real network which packet tracer is NOT) the port would need to be an access port on the management VLAN the AP uses to connect to the WLC or a trunk port with native vlan configured to the management VLAN.  Either way allows the CAPWAP connection on untagged VLAN which is what the AP needs.  Did you have native vlan set to 100 on the trunk port?