02-22-2009 10:50 PM - edited 07-03-2021 05:12 PM
i am facing in AP Association with the controller.
i have added option 60 and option 43 on cisco IOS DHCP server.
option 60 ascii "Cisco AP c1250"
option 43 hex f104c0a80ab1
and it is correct config coz i m getting controller ip address and info on AP.
but getting one error that is "Did not get log server settings from DHCP."
any one has knowledge about it?
if any please help me.
here is the AP output.
Translating "CISCO-LWAPP-CONTROLLER"...domain server (4.2.2.2) [OK]
%LWAPP-3-CLIENTEVENTLOG: Controller address 192.168.10.177 obtained through DHCP
%LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
%LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER
%LWAPP-3-CLIENTEVENTLOG: Controller address 10.32.32.19 obtained through DNS
02-23-2009 03:31 AM
now i am getting new problem and here is the output
%LWAPP-5-CHANGED: LWAPP changed state to JOIN
%LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join response (controller -
WLC_4402)
%LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP manager IP addresses
remain
%LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join response (controller -
WLC_4402)
%LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP manager IP addresses
remain
%SYS-4-PUPDATECLOCK: Periodic Clock update with ROMMON failed, because size left
in ROMMON (4294967295), size needed (29), error code (-1)
%SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN
RESPONSE.
%LWAPP-5-CHANGED: LWAPP changed state to DOWN
IOS Bootloader - Starting system.
Xmodem file system is available.
and AP restarts again & again
plz help me.
02-23-2009 01:30 PM
Join Timer: did not recieve join response (controller - WLC_4402) <--- How many AP's can your controller handle and how many have joined?
Set Transport Address: no more AP manager IP addresses remain < --- Please check your DHCP scope
What is the model of your AP?
What is the IOS your AP is running?
What is the firmware of your WLC4402?
02-26-2009 12:41 PM
I just had a similar issue with a COMPLETELY different resolution. Usually when you get errors regarding 'No more AP Manager IP addresses remain' or 'Did not get join response' it means things like:
1. Not allowing SSC
2. Improperly configured AP Policies
3. Wrong time on controller
4. Active interface on ap-manager set to 0 instead of 1 or 2
5. and many others...
Here was my situation: I am setting up a small network with a 4402-25. I wanted to collapse all of my 'wireless' devices onto the same subnet. Without thinking it through, the APs and the wireless clients being on the same subnet resulted in the following layer 3 error:
'Discovery request received on wrong VLAN '253' on interface '1', management VLAN = '0' - in L3 mode, dropping the packet.'
So in my case, you can't have your infrastructure APs on the same subnet as clients on an interface configured on the controller that is not a dynamic ap management interface. IOW, this would not apply to having APs and the ap-manager on the same subnet. It isn't recommended to have the APs and ap-manager on the same subnet, but it is valid.
Hope this helps.
Regards,
Scott
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