Cisco Wireless :: WLC 5508 - Lightweight AP Client Getting Wrong IP Address From DHCP Server
Mar 29, 2012
I have 2 units Cisco WLC 5508 running software version 7.0.220 with 70 over units Cisco AP 1262N and 1242AG. Some of wireless clients having problem to get the correct IP address from the DHCP server. There are 2 units of Microsoft DHCP. Both DHCP server ip have been configured on the Interface at the WLC. The core switch also being configured with ip helper. I've attached the debug output of one of the wireless client during the problem.
DHCP enabled with default settings. Dynamic IP range from 192.168.0.100 - 192.168.0.199.Router shows laptop with 192.168.0.199 however when I check the IP on laptop I have 192.168.100.10 and both laptops are connected on my SSID with 90% signal strenght.
My 5508 WLC which runs version 7.4 is configured as a DHCP server for the AP management and here's my problem: My AP can get to the address, and can ping the address of the WLC management，But my AP prompts the following log： [code]
In the switch dhcp we can use to do the WLC option43 specified address, but in this case how the address specified WLC, the AP can be registered up?
I have Cisco 1131 & 1300 Light Weight Acces Points and I have 5508 WLAN controller. If i enable the wlan controller internal DHCP Server can this access points will work with this internal DHCP server or do i need to configure DHCP option 43 for these access points? Can these access points works with LWAPP or do i need to configure CAPWAP?
I have a 5508 controller, just upgraded from 6.0.182 to 7.0.98.0. Also LAG was switched off directly after upgrade.
Since the upgrade none of the 1142 LAPs are associating with the controller. I can see they are being issued IPs by the internal DHCP but putting a console cable and watching I am getting:
Not in Bound state. *May 4 11:41:17.759: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !! *May 4 11:41:17.759: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
One Ap prior to the upgrade was on a static IP and that connected through without any problem, (it was an 1131 though, but I dont think that is the issue...)
I have setup the WLC to authenticate to a MS Server2008 NPS for a WPA2/AES SSID. The connection is successful, but client authentication fails for wrong EAP-type. I believe this indicates a Windows7 client issue. What is the required client setup to satisfy the MS NPS?
I have a RV042 router. The problem that I am having with it is that the DHCP is giving out the wrong Default Gateway and DNS Server. There is no option to change the DHCP server IP on any of the settings pages on the router. I am begining to think that there might not be a way to do it. I see that there is an option for the DNS under the DHCP page but the Public IP that is being handed out is not the one on that page. I also have 2 WAN connections hooked up as well a DSL link and a Cable link (the cable link is the primary one).
The following information is provided in an effort to resolve this issue: IP of Router 10.0.0.2 IP of DHCP Server (the one that is being handed out):10.0.0.1 IP of DNS (the one that is being handed out): 10.0.0.11
What I want to it be. IP of Router: 10.0.0.2 IP of DHCP 10.0.0.2 IP of DNS 10.0.0.2
User is connecting to 5508, running 7.0.116.0. Previously worked on another AP. TV (client) is set to use dhcp. As other posts have mentioned, "DHCP Addr. Assignment" checkbox is not checked for this wlan, but I also switched it to Required for this wlan but it did not make any difference. Seems to be a problem with just this client as many other clients are on this AP with no problems.
Users have to register their MAC to get on our wireless system, but there is no encyption or security enabled once the device has been registered.
I am using 2 anchor controllers 5508 as DHCP server. Anchor controller A is primary and anchor controller B is secondary. From time to time, client will complain "duplicate IP address error" when they try to connect guest wireless.First question: both anchor controller should have a recorder of IP address which is assigned to each PC, right?Second question: is there any way this type of issue can be avoided?
Currently we're providing DHCP to wireless clients from a dhcp pool on a cisco 6500. Due to new requirements we need to move to windows 2008 dhcp and when I test this on an unused WLC (7.0.235.0) the client doesn't get an address.
When I do a packet capture on the client I see it requesting dhcp but not getting any response from the server. When I do a dhcp debug on the client I see the same (see attached file).
This seems to me to be a server issue but the same server is supplying addresses to wired clients.
The wireless client can't get the DHCP address when I enable the On-MAC-Filter-failure, MAC Filtering and Web Auth. Client can get the DHCP address when I only enable the Web Auth in the same WLAN SSID. The WiSM verion is v7.0.235.0. [code]
I have Internal DHCP Server configured on the Cisco WLC 5508 and all is working fine. DHCP Range is 192.168.1.100 to 192.168.1.245. Now I created another SSID but I want clients connecting to this SSID get specific IP's or from a specific range. WLC has no option to bind a DHCP pool to a specific IP so what I did I checked the option to "Override DHCP" and added the IP of my firewall WLC is connected to and setup a DHCP Pool on that firewall as 192.168.1.89 to 192.168.1.94 (192.168.1.88/29).
Client can connect to the second SSID but can't grab and IP address, what am I missing ?
Recently I came across a wireless design whcih I ws not able to understand.The design is:
1. Two wireless LAN Controllers 5508, each with 25 AP license. AP load (5APs per Contorller) shared between the WLCs and congured with Backup Controller option.
2. The design has a Data Center Switch 3560x series, on which the two WLCs, Cisco Prime Infrastructure and Cisco MSE were connected. I've attached the design here.
3. The Data Center Switch is configured with DHCP pool for the wireless clients. The IP Address of the Data Center Switch is : 10.xx.xx.2 and Default Gateway is: 10.xx.xx.1
4. On the WLC, the Management Interface is configured with the IP Address: 10.xx.xx.21 for Controller 1 adnd 10.xx.xx.22 for Controller 2. But, their DHCP Server is configured with IP Address: 10.xx.xx.1 but not with 10.xx.xx.2 .
This means, all the DHCP requests are pointing towards the Gateway of the Data Center Switch.Is this the correct configuration?I have seen the Wireless Clients getting the IPs allocated from the DHCP Pool, even though the Management Interface's DHCP server configured with Gateway IP address 10.xx.xx.1 .
The DHCP configuration for the Data Center Switch is:
ip dhcp pool xxxxxx network 10.164.220.0 255.255.254.0 default-router 10.164.220.1
The Management Interface configuration on the WLC is:
Interface Configuration Interface Name................................... management MAC Address...................................... 2c:54:2d:72:b5:40 IP Address....................................... 10.164.220.21 IP Netmask....................................... 255.255.254.0 IP Gateway....................................... 10.164.220.1 External NAT IP State............................ Disabled
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. The setup is as follows:
- I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching. - I have an LWAP connected to the WLC in HREAP mode. - WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server. - Only one scope for Guest Interface is setup on the WLC.
Problems: 1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine. 2. DHCP does not release the ip addresses assigned to clients even after they are logged out. 3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the V LAN configured on the management interface.
************Output from the Controller******************** (Cisco Controller) >show sysinfo Manufacturer's Name............. Cisco Systems Inc.Product Name................ Cisco Controller Product Version................. 7.0.116.0Bootloader Version................ 1.0.1Field Recovery Image Version..................... 6.0.182.0Firmware Version..... FPGA 1.3, Env 1.6, USB console 1.27Build Type.......... DATA + WPS + LDPE [code]...
A client wants us to use the internal DHCP server on a 5508 instead of Windows DHCP. They will have 15 APs initially and upto 25 later. The docs on the 7.2 WLC make it sound like this is discouraged: Internal DHCP Server.
The controllers contain an internal DHCP server. This server is typically used in branch offices that do not already have a DHCP server. The wireless network generally contains 10 access points or fewer, with the access points on the same IP subnet as the controller.
In this case, the APs will not be in the same subnet as the Managment Internet.Is it a mistake to use the internal DHCP with upto 25 APs (3 WLANs)?
In our test set up, we have two WLC 5508 Controllers connected via Checkpoint UTM-1 firewall Inside and DMZ Interfaces. Both the WLC controllers are connected to the firewall via Cisco 3750 switch. On the Local (Inside) Controller, guest SSID is enabled and attached to the wireless management Interface. On the remote anchor controller, guest SSID is enabled and attached to the Management Interface as well. The following configs are replicated on both the Controllers.
SSID Name - guest Interface - Management ( VLAN 10 on Local and VLAN 20 on remote) - Mobility Group: Same configs at both ends SSID Anchor : Anchor SSID on local and local SSID on Anchor. AP: CAPWAP 3502 Management Subnet
[code]....
Is there any thing missing in the wireless configs and or the firewall rules as i could not see DHCP request back from the Anchor Controller. Also, after DHCP is obtained, the web authentication request will be redirected to an Amigopod device for authentication. In this case is the redirect URL congiguration to be performed only on the Anchor Controller or is this to be replicated on both the Local and Anchor Controllers.
We have a 5508 controller authenticates with WPA2-enterprise to 3 possible AAA servers. Today I tried migrating our DHCP server from a Windows 2003 machine to Windows 2008 R2. Migration went smoothly and all wired clients could get IP's. Reservations intact, scopes intact, etc.. you name it. I though it was a great success.
Fast forward about an hour when people started coming into work for the day. Calls started coming in about their laptops not able to connect to the network. I double checked with a spare laptop in our IT department and also my iPhone. Same issue. Seems the only thing I changed today was the DHCP server (from 10.1.1.1 to 10.1.1.2).
After racking my head on it for awhile, I re-enabled the "old" dhcp server (10.1.1.1) and disabled it on the new (10.1.1.2). Instantly wireless clients were able to connect.
Am I missing some configuration step in the 5508 controller when moving DHCP servers? I do plan on running 2 DHCP servers (10.1.1.2 and 10.1.1.10) for redundancy once I get the primary one moved over and working correctly.
I want to decommision the older 2003 server. Its time to raise the domain functional level.
i have 5508 WLC and 1242 LAP . i 5508 connects to core switch and LAP connects to access switch, and there is L3 link from core swtich to access switch , so i have to use HREAP to let my WLC to control my APs.in my access switch i set ip helper-address to my WLC in the client vlam, then all the wireless clients cannot get ip address from the WLC.but if i set ip helper-address to another DHCP server , the wireless clients can get ip address .so i dont know why WLC cannot be the DHCP server of the wireless client?
The 5508 is running code 7.0.116.0. I have created a group interface for 3 subnets and assigned the group to the WLAN. Clients are getting IP addresses in a round robin fashion. The issue or downside to this is if the lease has not expired before the next time the station connects to the WLAN it consumes an address on another subnet instead of grabbing the unexpired lease IP address on it's previous VLAN. It seems that the WLC determines the VLAN in the interface group before the DHCP request from the client in case the client already received a DHCP address that has not expired. This can be problematic since we have seen some iPhones requesting an address every 20 minutes thus consuming an address on every subnet in the interface group. Other than setting a lease time extremely low what can be done to address this?
I am using a WLC 5508 and its internal DHCP server. I cant find anywhere I can setup option 43. However, the access points are connected in just fine. Do I need to worry about setting up a seperate DHCP server to get option 43 setup properly?
Is it problem with iPads or LAP1141n?WLC 4404 and many 1142 and 1141, so other devices laptops, iphones, androind phone works as well.But iPad authorized, but can't get an ip address from dhcp server (dhcp not local on wlc, on windows machine) with coverage lap1141, but it get ip with coverage lap1142, and when i got it i roaming to lap1141 and it stays, if i off/on iPads can't get it again from lap1141.
I have a 1250 AP connected to an Switch Cisco 3750. We have a SSID(v lan 1 - native) which get an IP Address from our DHCP Server(located in a Windows 2003 server). I added a new SSID in VLAN 2 and I would like no to use the DHCP Server but to make the AP get an IP Address from the pool I created in the own AP (ip dhcp pool Guest) but every time I try to connect the new v lan, it doesn't get an ip address.
Follow the settings of the AP.
version 12.4 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption [Code]...
I would like to share one problem with WLC 5508 . we added a new virtual interface on the WLC. One new SSID is associated with this interface.
We created a ACL for this interface to restrict the access via WIFI to certian services. It´s not correct that everything works fine because the change were not applied. [code]
The changes of the ACL are applied on the fly, but for reason we don´t know, the clients don´t get a DHCP IP-Address (after changing the ACL) until the Controller is rebooted.
I have DHCP server running in windows 2003. Presently its unable to provide Ip address for VPN clients who connect remotely. What I should do / reconfigure in DHCP, so that the DHCP server provides address for VPN clients.
A Windows Server 2008 r2 with 2 internet ports. One (IP: 10.0.96.132) connected to company intranet and one (192.168.10.1) as DHCP server connect to several PCs (192.168.10.**) through a switch.The problem is the PCs (192.168.10.**) can ping the DHCP server (192.168.10.1) , while DHCP server (192.168.10.1) can not ping (192.168.10.**).How to configure the server so that all these PCs can access the intranet?
Can I have two asa firewall between dhcp client and dhcp server. if yes what solution i have to have to get dhcp leases. should i have to configure dhcp relay on both the asa.
I keep getting some additional IP addresses logging onto my home network that have an address outside what should be allowed by the router. The server is running at 192.168.2.1 and is set to only allow clients from 192.168.2.2 - 192.168.2.10 so a total of 9 clients should be allowed on.The problem is that something keeps logging in with an address of 192.168.169.2 or 3 etc. Sometimes more than one device at a time.I have assumed that it is some automated or virtual client as I'm pretty certain my network has not been breached. I have a 9 character password with a relatively random alphanumeric combination, although I haven't tried changing the password (I live in a share house with with a bunch of devices using wireless, so I haven't yet bothered). What I don't understand is how it has connected with the xx.xx.169.xx range at all. I have a Belkin 'Share' Wireless N Modem Router and at some stage there was a 'guest' network but that has since been disabled and I still am seeing the extra address. I have attached a screen shot of the DHCP client list on the router.The following is a list of devices that may be on the network at times, I'm thinking one of these may be responsible for the problem:
Windows Vista Desktop - Only LAN device PS3 Macbook Epson wireless printer Android HTC Desire Mobile Phone Laptops running various Windows versions (XP, Vista and 7)
A few thoughts I had:
- the android phone is capable of running a wireless hotspot, may have to look into it to see if if has been operating as an access point into the Belkin router, but assumed this wouldn't bring up clients connected to the phone on the home router.
- The desktop has PS3 Media server installed to stream video to the PS3 over the network (not that I have ever managed to get it to work), however this is not ever open on the desktop.
How do i get the 12.4 code to assign a dhcp address to my ethernet interface from my server? I deleted the default config on the 1141 and searching has not turned up anything useful.
We have 3 5508 WLCs (A, B, & C) and several LAPs (1140, 3500, 3600). The APs learn the controllers IP addresses through DHCP Option 43. When we setup a new site we put the IP address of the controller we want the AP to join first. Lately, I've noticed that regardless of which WLC IP I put first when I setup Option 43 the LAPs are always joining a particular controller.
We have two WLC's 5508. Following are its interfaces & details:mgmt 10.49.5.251 on wlc1 & .252 on wlc2 access p 10.49.6.251 on wlc1 & .252 on wlc2 there is no AP manager interface seen on both wlc's nor configured. both wlc1 & wlc2 are connected each to two switch ports, configured as normal trunk link each.LAG is enabled on both WLC's.
