09-02-2011 03:14 AM - edited 07-03-2021 08:39 PM
Hi there
I have a problem with our WLC 2100 series (2125). Basycally internal DHCP server configured on WLC is not working. I have one AP connected to port no 7 (PoE) to bypass and eliminate problem with other equipment.
Port no 7 details:
IP Address: 192.168.30.10
Netmask: 255.255.255.0
Default router: 192.168.30.1
DHCP Server: 192.168.1.250
Managment Port details:
IP Address: 192.168.1.250
Netmask: 192.168.1.1
Default Router: 192.168.1.1
DHCP Server: 192.168.1.250
I have created new scope: 192.168.30.20 - 192.168.30.40
I have tried enable DHCP proxy but still the same.
I have upgraded the firmware on the Controller and no luck.
On the AP:
%CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
Thanks for any help
09-02-2011 05:28 AM
If you connect the AP to the ports on the back of the 21xx, which I don't recommend if you can help it, it has to get an address that matches the subnet of the AP-manager interface.
Sent from Cisco Technical Support iPad App
09-02-2011 06:40 AM
Hi there
I have reconfigured the Controller and now the AP is getting the IP Address but client who is trying to connect to the AP can not get one.
Manager Port
192.168.1.250
255.255.255.0
192.168.1.1
AP-Manager Port
192.168.10.10
255.255.255.0
192.168.10.1
DHCP Scope
192.168.10.20 - 192.168.10.40
Any suggestions??
I forgot to add that the blue light is on the AP and Ethernet as well as Radio light is flashing green
Also on the Controller I am getting some error messages:
WIPS Alert: Reason "NoProfile" detected on AP MAC: 00:24:98:9b:85:e0, AP Name: THIRD2
09-02-2011 09:21 AM
What version are you running on your 2125? If you are on 7.0.98.0 you may be hitting bug CSCth68708.
I assume these clients' WLAN is mapped to the management interface, so do you have the management interface primary DHCP server defined as itself? (192.168.1.250).
09-02-2011 09:25 AM
The client isn't going to get an address from the AP-manager subnet. Whatever interface you point the WLAN at, is the scope you need to configure on the WLC. And yes you could hit that defect,
Sent from Cisco Technical Support iPad App
09-02-2011 09:30 AM
Exactly. So, assuming you are going to map this WLAN to the management interface, you would want your scope to be more along the lines of...
192.168.1.20 - 192.168.1.40
as the client will be placed on the management interface network
But still, be sure your management interface primary DHCP is pointed to itself (192.168.1.250), or any other interface you are binding to WLANs, assuming you are defining that scope "internal" to the WLC.
09-02-2011 11:02 AM
So the setting should be as follow:
Manager Interface
IP: 192.168.1.250
Mask: 255.255.255.0
DG: 192.168.1.1
Primary DHCP: 192.168.1.250
AP-Manager Interface
IP: 192.168.10.10
Mask: 255.255.255.0
DG: 192.168.10.1
Primary DHCP: 192.168.1.250
DHCP Scopes
192.168.1.50 -192.168.1.100 - for Clients
192.168.10.50 - 192.168.10.100 - for APs
Nad that should work I believe? what about DHCP proxy?? enabled or disabled?
Also I have changed via WLC ap mode of one of the APs from local to bridge and now AP does not conect to the WLC. How do I change it back if AP can not get IP address again (Flashing Orange)
Thanks
09-02-2011 11:11 AM
If you are offering "internal" DHCP, you "must" enable DHCP proxy on the WLC.
For your AP you set to bridge mode, I would just factory reset it. Hold down your reset button while powering on for 7-10 seconds and let it reset to defaults. It should then perform a normal discovery/join and arrive as a "local" mode AP.
Also, I don't think you ever revealed what version you are running on your WLC, please let us know.
09-02-2011 12:38 PM
Thanks David for you quick reply
Today I have upgraded the IOS on WLC from ver 5... to version 6.0.202.
I have tried to factory reset the AP by holding mode button (there is no reset button) but it looks that the AP is still in bridge mode. How can I check what is the current mode of AP??
I have noticed that when the AP was in local mode the ip address has been assigned to Fa0/1 interface, now the ip address is being assigned to BVI interface.
09-02-2011 04:01 PM
What model of AP are you using?
09-03-2011 12:03 AM
Cisco Aironet 1240
09-03-2011 07:06 AM
Here is a link to reset the 1240 AP:
http://www.cisco.com/en/US/docs/wireless/access_point/1240/quick/guide/ap1240qs.html#wp30482
09-03-2011 08:54 AM
Thanks Scott
Will try that on Monday and let you know.
09-04-2011 02:13 AM
Hi Guys
I have upgraded IOS on the controller to 7.0.116.0 version. I have reconfigured it again. I am also using PeE 8 port switch (no VLANs).
Controller is connected on port 3 to the PoE switch.
Port 3 is my AP-MAnager port with the config as follow:
192.168.10.10
255.255.255.0
192.168.10.1
DHCP: 192.168.1.250
Port 1 is my Manager port with config as follow:
192.168.1.250
255.255.255.0
192.168.1.1
DHCP: 192.168.1.250
I have configured 2 x DHCP Scopes
Clients: 192.168.1.50 - 192.168.1.100
APs: 192.168.10.50 - 192.168.10.100
And my APs connected to the PoE switch still are not getting IP addresses from the controller... Why??
Please help
It something wrong with the controller/DHCP configuration as if I connect our Juniper Firewall with another DHCP server to one of the ports of PoE switch the AP will get one of the IP Addresses from that DHCP.
Where Managment interface should be plugged into??
If I plug managment interface into the PoE switch I am getting IP address assigned to the AP from 192.168.1.0 subnet. I am getting confused now which port should be connected where...
09-05-2011 03:42 AM
I have managed to fix that finally.
Maybe it is not the usuall set up but it works.
Thanks for ur help guys
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