Thank you very much for this lesson. i have been wandering around like a headless chicken for the last 25 days unable to complete my academic project. thank you again.
Thank you very much for this lesson. I got the answers about my problems for the wireless technology in the packet tracer. You are doing an amazing job with your channels and I would kindly ask you to upload a similar lab with SVIs instead of ROAS which is presented in this lab.
Thanks my friend. this tutorial is of great help to me. Instead of setting DHCP server on the Router, I setup on the controller itself. - and it works.
Doesnt it only work on VLAN 0 (none) or VLAN 1 in this case because a L2 switch only has VLAN1? In the case we would want to use VLAN 99, we would need to use a L3 switch and add the VLAN 99?
You can use any native vlan, but in this case the only limitation of packet tracer is that the WLC can use only the VLAN 1, but on real life you can choose another vlan number on the WLC
Great explanation! One detail I'd like to have learned is: can we simulate roaming client? When client PC goes away from one AP and gets closer to another AP, does it maintain connection to its WLAN while switching AP association?
Thanks a lot for this. Very helpful. Would be good to include option 43 in the DHCP so that the clients automatically get the correct WLC IP. What I don't understand is why I need to use VLAN 1 in the WLC setup while actually I am using native VLAN (untagged) 99. I tested this in packet tracer and if I use ID 99 during the WLC setup I lose connectivity. According to the help tag, VLAN 0 should be the untagged VLAN (during WLC setup wizard).
Hello, thank you for all your support, the problem for now is that WLC on packet tracer will not support all functionality, will be little different like real WLC.
Hi Christian, thanks for the lab There is a thing you dont speak about: CAPWAP data encapsulation Where does CAPWAP take place in this lab ? I think in this lab CAPWAP tunnel is only carrying control messages between LWAP and WLC But data from client is not encapsulated in a CAPWAP tunnel When you ping PC0 from a laptop (in simulation mode), data does not reach the WLC; data goes to the router (GW for the laptop) and the router works like router on a stick I read that with WLC data is also encapsulated in CAPWAP tunnel, and not only control messages Could you clarify ? Regards
ping test verify connectivity between devices, the CAPWAP tunnel is working between LAPs and WLC anywhere the LAPs are, so you can´t use ping to test CAPWAP tunnel
@@romeroc24 Hi Christian, thanks for replying I am studying vlan configuration in WLC and your video is a great help, but as far as i know 1) tunnel CAPWAP is used for control messages between WLC and LWAP using UDP port 5246: OK i saw these messages 2) but data from and to wifi clients is also encapsulated in a similar CAPWAP tunnel using UDP ports 5247 That is to say: when a ping is sent from Laptop0 in vlan 10, the ICMP packet is tunneled directly from the AP to the WLC That is : it is included in a new IP packet build by the LWAP and send to the WLC IPs in the external packet are IPs of AP and WLC; IPs in the internal ICMP packet should be IP laptop0 for the src and the IP dest of the ICMP packet So the link between 3702i and the switch has not to be a trunk: it should only be an access link in vlan 99, because external IP packets between 3702i and WLC (and the opposite when returning) are in the network 172.16.99.0/24 and are carried by vlan 99 in layer 2 But when link between AP and switch is set "switchport access vlan 99", ping does not work anymore ! That is why something i think something has to be clarified In any case your video helps me, but your configuration is unclear for me Regards
I think there's an issue with Packet Tracer and CAPWAP tunnel for data. The link from the switch to LAP should be an access link but in packet tracer it won't work unless it's configured as a trunk.
Muchas gracias por el video, es de mucha ayuda,Consulta: es posible propagar algunos SSID específicos por cada AP, es decir no todos los SSIDs en todos los APs. Ejemplo solo Vlan10 en AP1, solo Vlan20 en AP2. Gracias.
adding dhcp pool in WLC is not working in my Packettracer :/ but this video was very helpful. But i have a question. The mGMG VLAN is 99, but why do we have to tell the WLC that the MGMT vlan is in 1?
Hello Augusto I have a question. In real world, with such topology what have you created in the video, WLC and AP trunk native VLAN would still be native 99 and sit in management? or trunk native would have been anything except 99-20-10? for instance from perspective of switch: To interface WLC: Switchport mode trunk, switchport native vlan 777, switchport trunk allowed vlans 10,20,99 Same to LWAP.... Such way would have been correct?
Not sure if it's Packet Tracer, but I set up this lab exactly as you have it and the laptops won't get the correct DHCP address from the pools on the router. It keeps getting an APIPA address. All my configurations are the same, everything looks good. When I do a simulation, the dhcp message stops at the access point and then disappears...Also the SSIDs aren't showing up on the laptops after adding the adapter and clicking refresh. Guessing it's Packet Tracer not working right maybe.
Please be careful where to use a trunk link or access ports on the switch, view the complete video, maybe something is missing about the WLC, please save and commit every time you make a modification to WLC
Hey one Question: the LWAP reffered to vlan 99 based to your topology. But in the switch configuration you set him to trunk and tell the lwap interface that the native vlan is 99.... there is no sw access vlan 99 entry. Is it because of the native and how would you configure it if native vlan is 1. Would you do the command sw mode access + sw access vlan 99 or sw mode trunk? and should the wlc always be in native vlan or is it just for this topology? pls help by awnsering.. i rlly need to understamd this xd btw u a great teacher but the native confused me a little
I tried creating a native vlan 99 and management vlan 88, I tried to manage the WLAN in the vlan 88, but did not work, the native vlan should be the same where you manage the WLAN and the link to the WLAN should be trunk because will Manage more than one VLAN, for the admin the port should be access because is managing only one VLAN
i read in the ccna pdf the whietlight access points should be linked with the switch on access mode not trunk but you did them in trunk why ? And thanks for this great video
How can I get this to work with an external dhcp server? I setup two different dhcp ip pools on a server in packet tracer, but it does not pull the correct IP's. It will only pull from the vlan 99 pool of IP's. I am using a Layer 3 switch for routing, so I have the ip helper-address configured on the different vlans pointing to my dhcp server.
Also on WLC configure the primary DHCP server with the IP address of external server, for each VLAN or WLAN. Also use ip helper address to reach the server
hello,thankyou so much for this video,i ve questions: should always the management vlan be the native one or we can leave the vlan 1 as native and configure the port connected to wlc as trunk????seconf question is,can be the LAP on mode access vlan 99,and they will receive the other vlan by the capwap tunnel.thank you and please answer me
Hi i have a question for you. In this situation all AP light connected with the switch acess should be not configured in ACESS mode (acess vlan 99) et only the port between WLC et switch in trunk mode ? thanks
VLAN 99 is the Management and Native, LAPs use the VLAN 99 to connect with the WLC, WLC use trunk port because it is managing various VLANs (10, 20 , 99)
Hello Christian, good video, thanks for uploading... situation: lets imagine, that You have this topology and You want add new set of APs which will run on example WLAN 100 and they will provide wlan 110 for users? dhcp for APs and Users will be on same WLC3504... thank You...
@@romeroc24 sure, but how to do that? I mean, how to configure that that new AP will be on VLAN100? I have read at the documentation, that mentioned VLAN must be connected to WLC via separate LAN cable e.g. to port 2 of WLC than the WLC will able to manage APs on the different VLAN connected... any ideas?
@@MrDome110 so you need to create another interface for another VLAN and use that new interface with new ip address on different subnet as the DHCP server
on real device you alright, but packet tracer has some limitations, like this on WLC use management with 1 also if you will use another number on the switch
On pakcet tracer only, if you modify the management vlan identifier in the WLC, will not work (packet tracer limits), on real lab you need to match the management vlan in the WLC with the management VLAN on the network
the WLC manage multiple VLANs, so is necessary a native VLAN to support those VLANs, also WLC has IP addresses for remote administration, you need to access those IP addresses using the Management VLAN that is the same of NAtive
@@romeroc24 Thank you for the quick response. Just another question, can we just allow the VLANs needed instead of setting up the mgmt VLAN as Native VLAN? For example, allowing the mgmt VLAN, SSID VLANs? I know that it's best practice to change the default Native VLAN but is there a special reason why the Native VLAN has to be the mgmt VLAN? Apologies for having too many questions.
@@rawlee205 i think the problem is with packet tracer. From the perspective of security i don't think it's good idea to use native vlan in allowed vlans/management vlan.
This is the best video i have ever watched on wlc configuration. Thank you sir for taking your time to explain everything on this video
Thank you for all your support, your motivation is very important for me
Thank you very much for this lesson. i have been wandering around like a headless chicken for the last 25 days unable to complete my academic project. thank you again.
Glad it helped! Thank you for all your support!
Nothing could be better explanation than this one.
Well done 👍 Mr Christian
Thank you for all your support, I appreciate it
Best wlc vlan setup vid i have seen. cleared up a lot of questions regarding dhcp THX
Glad it helped. I appreciate all your support!!!
Thanks Christian, very well explained. Cleared up all of my confusion with setting up a WLAN on packet tracer.
Thank you for all your support
Grazie! Mi hai veramente aiutato con questo video, ero bloccato da una giornata su un esercizio del genere
Grazie per tutto il vostro supporto, lo apprezzo davvero tanto!!
Always thank you for everything you do and remain outstanding in the networking field
I appreciate your comment, this motivate me to continue
Thank you sir. I had been spending quite a time on youtube looking similar config. Your video helped me a lot for my assessment
Glad it helped. I appreciate all your support and good comments.
Great video, thanks for taking the time to make this. Learned a lot!
Thank you very much for this lesson. I got the answers about my problems for the wireless technology in the packet tracer. You are doing an amazing job with your channels and I would kindly ask you to upload a similar lab with SVIs instead of ROAS which is presented in this lab.
Thank you very much, I will try to do it as soon as possible, by the way, you can review this th-cam.com/video/MMha3L2s5OE/w-d-xo.html
Thanks my friend. this tutorial is of great help to me. Instead of setting DHCP server on the Router, I setup on the controller itself. - and it works.
Glad it helped . thank you for all your support
You are a legend
I appreciate all your support my friend!!!
Great teaching ,thanks
Thank you for all your support
Thanks
thanks for info you shared in this video, i have learned a lot on wireless lan controller.
Glad it helped, thank you for all your support
Excellent - thanks mate.
Glad it helped, Thank you
Thank you very much!!!!
thank you for all your support
thank you for your great video. cheers
thank you for all your support
Thanks a lot for this! You are a legend. Liked and subscribed.
Thank you for all your support. Thanks for the sub!
Thank you for your amazing video! it really helped me out
You're very welcome! Thank you for all your kind support!
Doesnt it only work on VLAN 0 (none) or VLAN 1 in this case because a L2 switch only has VLAN1? In the case we would want to use VLAN 99, we would need to use a L3 switch and add the VLAN 99?
You can use any native vlan, but in this case the only limitation of packet tracer is that the WLC can use only the VLAN 1, but on real life you can choose another vlan number on the WLC
Great explanation!
One detail I'd like to have learned is: can we simulate roaming client? When client PC goes away from one AP and gets closer to another AP, does it maintain connection to its WLAN while switching AP association?
Brother, thanks. Sunday going to implement the same setup to one of our customer with the same WLC model with Rest the password
Glad it helped, thank you for all your support
Thanks a lot for this. Very helpful. Would be good to include option 43 in the DHCP so that the clients automatically get the correct WLC IP.
What I don't understand is why I need to use VLAN 1 in the WLC setup while actually I am using native VLAN (untagged) 99. I tested this in packet tracer and if I use ID 99 during the WLC setup I lose connectivity. According to the help tag, VLAN 0 should be the untagged VLAN (during WLC setup wizard).
Hello, thank you for all your support, the problem for now is that WLC on packet tracer will not support all functionality, will be little different like real WLC.
👍👍
thank you
Congrats !!!!
Thank you for all your support
Hi
this video was helpfull and thanks for your simple teaching way
Glad it was helpful! I appreciate it
Hi Christian, thanks for the lab
There is a thing you dont speak about: CAPWAP data encapsulation
Where does CAPWAP take place in this lab ? I think in this lab CAPWAP tunnel is only carrying control messages between LWAP and WLC
But data from client is not encapsulated in a CAPWAP tunnel
When you ping PC0 from a laptop (in simulation mode), data does not reach the WLC; data goes to the router (GW for the laptop) and the router works like router on a stick
I read that with WLC data is also encapsulated in CAPWAP tunnel, and not only control messages
Could you clarify ?
Regards
ping test verify connectivity between devices, the CAPWAP tunnel is working between LAPs and WLC anywhere the LAPs are, so you can´t use ping to test CAPWAP tunnel
thank you for all your support
@@romeroc24 Hi Christian, thanks for replying
I am studying vlan configuration in WLC and your video is a great help, but
as far as i know
1) tunnel CAPWAP is used for control messages between WLC and LWAP using UDP port 5246: OK i saw these messages
2) but data from and to wifi clients is also encapsulated in a similar CAPWAP tunnel using UDP ports 5247
That is to say: when a ping is sent from Laptop0 in vlan 10, the ICMP packet is tunneled directly from the AP to the WLC
That is : it is included in a new IP packet build by the LWAP and send to the WLC
IPs in the external packet are IPs of AP and WLC; IPs in the internal ICMP packet should be IP laptop0 for the src and the IP dest of the ICMP packet
So the link between 3702i and the switch has not to be a trunk: it should only be an access link in vlan 99, because external IP packets between 3702i and WLC (and the opposite when returning) are in the network 172.16.99.0/24 and are carried by vlan 99 in layer 2
But when link between AP and switch is set "switchport access vlan 99", ping does not work anymore !
That is why something i think something has to be clarified
In any case your video helps me, but your configuration is unclear for me
Regards
you need to use trunk because a lot of vlans will be used in the link
I think there's an issue with Packet Tracer and CAPWAP tunnel for data. The link from the switch to LAP should be an access link but in packet tracer it won't work unless it's configured as a trunk.
very useful, thanks
Thank you for all your support
Muchas gracias por el video, es de mucha ayuda,Consulta: es posible propagar algunos SSID específicos por cada AP, es decir no todos los SSIDs en todos los APs. Ejemplo solo Vlan10 en AP1, solo Vlan20 en AP2. Gracias.
Si, hay una forma de hacerlo por grupos de APs, eso lo pobré en el mismi packet tracer con este mismo WLC
adding dhcp pool in WLC is not working in my Packettracer :/ but this video was very helpful.
But i have a question. The mGMG VLAN is 99, but why do we have to tell the WLC that the MGMT vlan is in 1?
I can figure out, on real WLAN you will select 99 management vlan and will work, in packet tracer will not work, only if you select vlan 1
@@romeroc24 thanks your awnser helped me alot understanding it : )
@@DovaBro thanks to you
Hello Augusto
I have a question.
In real world, with such topology what have you created in the video, WLC and AP trunk native VLAN would still be native 99 and sit in management? or trunk native would have been anything except 99-20-10?
for instance from perspective of switch:
To interface WLC: Switchport mode trunk, switchport native vlan 777, switchport trunk allowed vlans 10,20,99
Same to LWAP....
Such way would have been correct?
Trunk should be the Management because Management needs to access APs and WLCs
Thanks
Thank you my friend
Thanks!
Thank you for all your support
Not sure if it's Packet Tracer, but I set up this lab exactly as you have it and the laptops won't get the correct DHCP address from the pools on the router. It keeps getting an APIPA address. All my configurations are the same, everything looks good. When I do a simulation, the dhcp message stops at the access point and then disappears...Also the SSIDs aren't showing up on the laptops after adding the adapter and clicking refresh. Guessing it's Packet Tracer not working right maybe.
Please be careful where to use a trunk link or access ports on the switch, view the complete video, maybe something is missing about the WLC, please save and commit every time you make a modification to WLC
Hey one Question:
the LWAP reffered to vlan 99 based to your topology.
But in the switch configuration you set him to trunk and tell the lwap interface that the native vlan is 99....
there is no sw access vlan 99 entry. Is it because of the native
and how would you configure it if native vlan is 1. Would you do the command sw mode access + sw access vlan 99 or sw mode trunk?
and should the wlc always be in native vlan or is it just for this topology?
pls help by awnsering.. i rlly need to understamd this xd btw u a great teacher but the native confused me a little
I tried creating a native vlan 99 and management vlan 88, I tried to manage the WLAN in the vlan 88, but did not work, the native vlan should be the same where you manage the WLAN and the link to the WLAN should be trunk because will Manage more than one VLAN, for the admin the port should be access because is managing only one VLAN
i read in the ccna pdf the whietlight access points should be linked with the switch on access mode not trunk but you did them in trunk why ?
And thanks for this great video
Thank you, the reason I used trunk is because that port will manage various vlans, not only one
How can I get this to work with an external dhcp server? I setup two different dhcp ip pools on a server in packet tracer, but it does not pull the correct IP's. It will only pull from the vlan 99 pool of IP's. I am using a Layer 3 switch for routing, so I have the ip helper-address configured on the different vlans pointing to my dhcp server.
Also on WLC configure the primary DHCP server with the IP address of external server, for each VLAN or WLAN. Also use ip helper address to reach the server
hello,thankyou so much for this video,i ve questions: should always the management vlan be the native one or we can leave the vlan 1 as native and configure the port connected to wlc as trunk????seconf question is,can be the LAP on mode access vlan 99,and they will receive the other vlan by the capwap tunnel.thank you and please answer me
On packet tracer. You need to use the management and native on the same vlan.
In real environments the link between the access points and the switch should be trunk or access …thank u
thank you for all your support
that was my question too,i think LAP should be on access mode,this is the most confusing stuff + the native vlan
why did you use 1 for the vlan identifier on the Management interface, when the Management VLAN is set to 99?
for packet tracer, use 1 and will work, on real life use 99 or the native number
Hello sir, I have same model but i am not getting wifi/hotspot mobile notifications when I enter in a premises. Please help for the same
please contact me using social media shown in 00:03 , so you will send me details
my laptops are all receiving ips on 99 network via dhcp after following all your steps. i wonder why and i have placed dhcp on routers as youve shown
please try again, the switch should use vlans to separate the networks
would you please explain to me how should be the relation between wlc and the switch(trunk or access),and between lap and the switch ,and why,thanks
the video shows you all but, the connections from WLC and LAP are trunks
Hi i have a question for you. In this situation all AP light connected with the switch acess should be not configured in ACESS mode (acess vlan 99) et only the port between WLC et switch in trunk mode ? thanks
VLAN 99 is the Management and Native, LAPs use the VLAN 99 to connect with the WLC, WLC use trunk port because it is managing various VLANs (10, 20 , 99)
no funciona la troncal entre el sw to wlc, si ese puerto lo pones como acceso si funciona, a que se debe ese problema?????
en este video el switch y el wlc son troncales, necesitaría algunoms detalles si deseas para resolver el problema
Hello Christian, good video, thanks for uploading...
situation: lets imagine, that You have this topology and You want add new set of APs which will run on example WLAN 100 and they will provide wlan 110 for users? dhcp for APs and Users will be on same WLC3504... thank You...
ON packet tracer will work using the DHCP server on the router, on real life you can use the DHCP server on the WLC
@@romeroc24 sure, but how to do that? I mean, how to configure that that new AP will be on VLAN100? I have read at the documentation, that mentioned VLAN must be connected to WLC via separate LAN cable e.g. to port 2 of WLC than the WLC will able to manage APs on the different VLAN connected... any ideas?
@@MrDome110 in the video, I created the DHCP pool for management VLAN, so is the same process to create a DHCP pool for another VLAN
@@romeroc24 I tried it, but in reality the WLC says that I cant use same IP as dhcp server and interface IP... but thanks for reply...
@@MrDome110 so you need to create another interface for another VLAN and use that new interface with new ip address on different subnet as the DHCP server
hi i have one question. Ur management is vlan 99 but why u set ur management vlan ID 1 (http)
on real device you alright, but packet tracer has some limitations, like this on WLC use management with 1 also if you will use another number on the switch
AMIGO porque pones la id de la vlan nativa como 1 en vez de 99 en el WLC?
porque es una limitación del WLC en packet tracer, debería usar la 99 pero sólo funciona con 1
why we make ap int trunk .....we can make it access to vlan mangment !!... bcs mangment vlan encapsulate other vlan inside capwap tunnel
yes but please try and let me know, for now I'm using trunk because there are various vlans on that place
May I know in 15:21, why we cannot use VLAN Identifier as 99?
On pakcet tracer only, if you modify the management vlan identifier in the WLC, will not work (packet tracer limits), on real lab you need to match the management vlan in the WLC with the management VLAN on the network
@@romeroc24Thank you so much for ur reply, appreciate it
Hello, may I know the reason why do you need to set the management VLAN and the Native VLAN as the same?
the WLC manage multiple VLANs, so is necessary a native VLAN to support those VLANs, also WLC has IP addresses for remote administration, you need to access those IP addresses using the Management VLAN that is the same of NAtive
@@romeroc24 Thank you for the quick response. Just another question, can we just allow the VLANs needed instead of setting up the mgmt VLAN as Native VLAN? For example, allowing the mgmt VLAN, SSID VLANs? I know that it's best practice to change the default Native VLAN but is there a special reason why the Native VLAN has to be the mgmt VLAN? Apologies for having too many questions.
@@rawlee205 i think the problem is with packet tracer. From the perspective of security i don't think it's good idea to use native vlan in allowed vlans/management vlan.
Bom dia Mano gostaria de saber se é possível um AP fornecer 2 redes ?
Não me refiro a controladora
Em um AP real você pode ter dois SSIDs, mas no packet tracer apenas um SSID
thx for the video :) what happend if native vlan default 1
Thank you my friend, on Packet Tracer change the native vlan to 1 and all will work, on real scenario change native vlan on switch and on WLC
dude i can't put ip addres in the interfaces when i put IP and then aply the ip does'nt change, can you help me?
maybe the ip is incorrect or is used by another device
can i create multiple controllers and still use one external dhcp server?
yes you can do it my friend
why did u use vlan 1
Yes, the default VLAN for switch and WLC
you did not isolate vlans though
vlans are isolated by default
why configure native vlan?
How about Roaming?
Just only add more LAPs, and configure the switch ports
Hy, do you help me?
yes, not problem