02-20-2009 12:07 PM - edited 07-03-2021 05:12 PM
See attached file for details
02-20-2009 12:21 PM
Well one thing to try id you are not useing option 43 or DNS to help the LAP join the WLC is to place the AP in the VLAN 30 subnet and let the ap join. Then tag the port for vlan 50 and reboot the LAP. That should work for you unless the vlan from the switch the ap is connected to isn't forwarding to the core.
02-22-2009 03:33 AM
which port to tag ?
ap-manager or management interface
02-20-2009 07:50 PM
Does the AP have an IP Address? If yes, can the AP ping the management interface of the WLC? If yes, then type this command from the AP:
lwapp ap controller ip add
Hope this helps.
02-22-2009 03:31 AM
When we are typing this command on AP it is showing that command is disabled, so how can we enable command writing mode in lightweight AP.
Thanks
02-22-2009 03:10 PM
The command should be enabled in priviledge mode (not in configuration/global).
02-22-2009 07:16 PM
configure a username and password from the wlc cli:
config ap username
config ap username
02-23-2009 08:50 AM
I have joined the VLAN 50 AP to controller with this command and have connect the wireless client, but the wireless client of VLAN 50 (static IP's)not ping the gateway address i.e. 10.0.50.1, what should I do now ? whereas the wireless clients of VLAN 30 (DHCP based IP's)are working perfectly.
Thanks
02-23-2009 08:58 AM
Double check that your dhcp scope is active and that the switches are forwarding the vlan 50 to the L3 switch/router. Post your show run-config if you are still having issues.
02-22-2009 10:00 PM
we are typing this command in privilege mode but it is showing the error that command is disabled, so what to do?
Thanks
02-23-2009 10:38 AM
Have you got the possibility to send a screen dump of the console when the LAP is coming up after a reboot? which method are you using to discover your LAPs?
02-23-2009 01:26 PM
Whoopsie! The command is indeed disable if the IOS you are running is NOT the RCV image. Can you boot into the RCV image and run the command?
02-24-2009 10:43 PM
OK, I have done this, there was some VLAN segmentation problem.
Thanks for your input
02-24-2009 10:42 PM
OK, I have done this, there was some VLAN segmentation problem.
Thanks for your input
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide