Unable to view the APs from the secureweb (https) browser page. APs powered up, controller configured (pingable), ip addrs, dhcp relay (svr pingable), WLAN I/F (not recognized within https web monitor), ideas?
Thanks for your reply. Understood re: no http service running on WAPs. Issue is communication between WLC and WAPs. WLC GUI does not see any WAPs physically connected to it. LWAPP Transport mode is layer 3 (layer 2 is not available in drop down box). A DHCP server has been configured and reachable however I do not know if WAPs are receieving the IP address needed to receive their config from WLC... Never configured 113x WAPs or WLC before so may be something very obvious to yourself. What are the steps needed to config WLC and a WAP so they can communicate? Thx -W
if you console in one of the ap's and you see it going through the discovery and then rebooting, then the ap's are not finding the WLC. Try to configure the switch port where the ap's is connected to, to the same vlan as the management interface of the controller. The ap will discover the WLC and then keep that information. You then can configure the switch ort to what ever vlan you want the ap to be in and then do a shut and no shut so the ap will boot right away. Once the ap reboots it should find the WLC since the WLC ip address was previously learned. hope this helps.
Try to connect the ap's to the switch. I have never tired to use the crossover. One thing to do also is to reset the AP if its a demo. The ap probably has the information from the previous borrower. Then try the crossover cable.
Versions before 3.2.116 of the controller OS do not load 1130s properly. What version of the firmware is your 2006 running?
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
