2500 WLC Primary DHCP Server
Hello,
If I set a primary DHCP server in the interface configuration, or if I override DHCP in the WLAN Configuration.
Which interface does the WLC use to try and connect to the DHCP on behalf of the wireless clients?
IF
A) The dhcp server is not on any of the configured subnets.
B) The DHCP server is on a different interface's subnet.
Sent from Cisco Technical Support iPad App
Hello Stuart,
As per your query i can propose the following solution-
The interface will be Management interface
IF
A) The dhcp server is not on any of the configured subnets.
B) The DHCP server is on a different interface's subnet.
For more information you can go through the link-
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml
Hope this will work.
Similar Messages
-
Using one controller as primary DHCP server for 2 or more controllers
Here's my setup
2 - 5508 controllers (40 APs per controller) running 6.0.196.0 (100 user license per controller)
about 80 mixed - 1142 and 1252 APs, trying to put 40 APs on each controller
One subnet connects two controllers together on the management interface on port 1 on both controllers. 10.x.x.x addresses.
Port 2 on each controller (LAG not used) connects to a DMZ via dynamic interfaces for user traffic, 172.x.x.x addresses.
I want to use one controller for all clients to get their DHCP addresses from (no matter what controller their AP is on)
as a primary DHCP server (controller A as primary), then i'd like to point the clients to the other controller (controller B) to be used as a backup DHCP server in case Controller A fails. Also, the APs are setup to have the correct primary and secondary controllers under their high availability setting as well as the mobility group information.
I want to avoid splitting my DHCP scopes between controllers, and I don't have a DHCP server dedicated to this project, so the 5508s should be able to do the job. Or at least I thought.
When configuring the controllers with the proper DHCP scopes, this only seems to work for clients connecting to controller A. Clients on controller B don't get an address from controller A when pointing to that controller, in fact, the wierd thing is that debugging shows DHCP requests going out of port 2 (DMZ traffic) instead of port 1 (management) on controller B. Shouldn't they be going out of the interface that is specified with the DHCP configuration in the dynamic interface? And I don't have "override" turned on in the WLAN configuration so the DHCP server should be taken from the dynamic interface that the user resides on.
Mobility groups are configured correctly between the two controllers and both the control and data paths are up between the two controllers. Another wierd thing, both controllers management interfaces are on the same subnet, no acls or filters, when the mobility groups are configured, controller A can ping controller B, but controller B cannot ping A. The status still shows as UP/UP in the mobility members windows, but they use mPing which seems to work fine. Remove the mobility group configuration and ping works just fine between the boxes. I don't know if this is related to my DHCP issues, but it would seem that if I put the controller A's management address in the dynamic interface configuration for DHCP on controller B, my clients on B should get an address from A's DHCP pool. Controller A's dynamic interfaces all point to controller A's management interface and they work just fine.
I'm trying to load ballance my AP distribution between two boxes, and I'm also trying to have some controller redundancy.
Controller A works just fine, it's in production. Trying to add another controller B to talk A for DHCP is the issue.
Anyone have any clues?
-BlairI guess i was under the impression that when mobility groups were cofigured, the lease time, along with other client information (mac address, IP address and such), would replicated from one controller to the other controller over the EoIP tunnel. If that's not the case, then obviously I'll have to look elsewhere.
Also, does this mean that it will not work, or just that it's not recommended. If it does work and I have to fix something, at least I can move on with my testing, all while pursuing a DHCP server. It doesn't sound like using an AP as a DHCP server is any better than using the controllers for that same purpose.
Thank you for the quick response. -
Hi
My 5508 WLC which runs version 7.4.100.60 is configured as a DHCP server for the AP management and here's my problem:
Client can not get the address,I am in location at 1F of AP, obtain an IP address and associated to this AP, but I got to address is the address section 2F instead of 1F address above. In this WLC the AP, power and channel have not been optimized, the adjacent channels are AP 1, the power display is 1.
Last night I test, disconnect reconnect several times, I was able to get to the same network to a different IP address.My AP is 1602I. LoaderVersion 15.2<2> JAX . This is why ?Cisco Controller) >show interface summ
Number of Interfaces.......................... 17
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
management LAG 421 10.217.147.45 Static Yes No
redundancy-management LAG 421 0.0.0.0 Static No No
redundancy-port - untagged 0.0.0.0 Static No No
service-port N/A N/A 10.215.29.165 Static No No
t2-2f LAG 608 10.215.69.125 Dynamic No No
t2-1f LAG 609 10.215.68.253 Dynamic No No -
5500 Series WLC internal DHCP Server - Exclusion?
Hi there,
We're using the internal DHCP server on our 5500 Series WLC which works fine.
However on one WLAN we ran out of addresses so changed the subnet from a /25 to a /24.
The problem is that the router/gateway is still in the middle (124/125/126) and not easily changed.
I've moved the WLC interface to the top of the subnet (251) but the router is more difficult as its externally managed/controlled.
So is there a way we can create a DHCP pool of .1 through 250 on a /24 mask but exclude 124/125/126?
Thanks
Mike
PS - Router subnet masks were changed so can see whole subnet.Mike,
The WLC isn't a fully functional DHCP server, it only allows you to define what is in scope, not what is out of scope. Now if you have a cisco router/switch, you could use that for the DHCP server and specifically exclude the necessary addresses.
HTH,
Steve -
WLC CT2504: Interface IP can not be used as internal DHCP server IP
Hello all,
I've got a new CT2504 controller with software version 7.0.220.0
Regarding to
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml
I've tried to configure the internal DHCP on a dynamic-interface, but this is not possible:
(Cisco Controller) >config interface dhcp dynamic-interface vlan401 primary 172.16.x.3
vlan401 Interface IP can not be used as internal DHCP server IP
It works, if I use another IP (aka DHCP server) in the same subnet or in another subnet. It works also for the management interface.
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... d0:c2:82:xx:xx:xx
IP Address....................................... 10.2.x.135
IP Netmask....................................... 255.255.255.240
IP Gateway....................................... 10.2.x.129
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 400
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 10.2.x.135
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Disabled
Scopes are defined and Proxy is enabled.
(Cisco Controller) >show dhcp summary
Scope Name Enabled Address Range
ap Yes 10.2.x.137 -> 10.2.x.140
intern Yes 172.16.x.20 -> 172.16.x.30
(Cisco Controller) >show dhcp proxy
DHCP Proxy Behaviour: enabled
Has somebody an explanation for this issue?
Thanks in advance,
Regard,
RobertYou can use the internal dhcp, but you need to set the primary dhcp as the management ip. So in your dynamic interface, your primary dhcp is configure with the wlc management ip address. Dhcp proxy also needs to be enabled and is enabled by default.
Thanks,
Scott Fella
Sent from my iPhone -
WLC 5508 Internal DHCP server issues
Hi,
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
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 Vlan 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.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS + LDPE
(Cisco Controller) >show interface summary
Interface Name Port Vlan Id IP Address Type Ap Mgr Gu
est
guest 1 301 10.255.255.30 Dynamic No No
management 1 100 172.17.1.30 Static Yes No
service-port N/A N/A 192.168.0.1 Static No No
virtual N/A N/A 10.0.0.1 Static No No
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 4
WLAN ID WLAN Profile Name / SSID Status Interface Name
1 LAN Enabled management
2 Internet Enabled management
3 Managment Assets Enabled management
4 Guest Enabled guest
(Cisco Controller) >show dhcp detailed guest
Scope: guest
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... e8:b7:48:9b:84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.30.50.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show interface detailed guest
Interface Name................................... guest
MAC Address...................................... e8:b7:48:9b:84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show dhcp leases
MAC IP Lease Time Remaining
00:21:6a:9c:03:04 10.255.255.46 23 hours 52 minutes 42 seconds <<<<<<< lease remains even when the client is disconnected.
*********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
(Cisco Controller) >show client detail 00:21:6a:9c:03:04
Client MAC Address............................... 00:21:6a:9c:03:04
Client Username ................................. N/A
AP MAC Address................................... a0:cf:5b:00:49:c0
AP Name.......................................... mel
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 2 <<<<<<<< 'Internet' SSID
BSSID............................................ a0:cf:5b:00:49:ce
Connected For ................................... 319 secs
Channel.......................................... 36
IP Address....................................... 10.255.255.46 <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 1800
Client CCX version............................... 4
Client E2E version............................... 1
QoS Level........................................ Silver
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
Power Save....................................... OFF
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Policy Manager Rule Created...................... Yes
ACL Name......................................... none
ACL Applied Status............................... Unavailable
Policy Type...................................... N/A
Encryption Cipher................................ None
Management Frame Protection...................... No
EAP Type......................................... Unknown
H-REAP Data Switching............................ Central <<<<<<<<<
H-REAP Authentication............................ Central <<<<<<<<<<
Interface........................................ management
VLAN............................................. 100 <<<<<<<<<<< right Vlan
Quarantine VLAN.................................. 0
Access VLAN...................................... 100Hi All,
I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
Thanks,
Raj Sandhu -
WLC Dropping DHCP Discover Packets
Hello
I have following setup:
[Notebook]----wired connection----[Cisco Lynksys wlan ethernet bridge] )))))) wirelessConnection ((((( [AP]-----[switch]-----[Router]-----[WLC]
I use a seperat DHCP Server. so on the WLC the DHCP Proxy is disabled.
what i know is - the WLC should receive and forrward he DHCP Discover to the layer3 interface on the router, where the ip-Helper is configured. From there it should go to the DHCP Server.
BUT - here comes the problem -
The WLC Dropps the DHCP Discover.
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP received op BOOTREQUEST (1) (len 308,vlan 253, port 13, encap 0xec03)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: hostname = Test (len 4)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: 55 (len 13) - skipping
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP options end, len 72, actual 64
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
Can anyone tell me why this happens?HI Chris,
First enable DHCP Proxy on WLC.
(Cisco Controller) >config dhcp proxy enable
and make sure that For DHCP proxy to work, a primary DHCP server must be configured on each controller interface that requires DHCP services.
To kow more about DHCO on WLC:
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html#Internal-DHCP
Regards
Dont forget to rate helpful posts -
DHCP Failover / Migrate DHCP Server to another Machine
We have DHCP Server Installed in Domain Controller with Windows Server 2008 R2 Based OS.
I have Checked that there is no way to make the DHCP Failover in Server 2008 R2.
Can anyone help me to get some level of Failover in DHCP?
or
If I want to migrate the DHCP to Server 2012 what is the Best Practice?Hello,
There is no big challenge for configuring DHCP failover in Windows 2008 platform. Kindly go through with this link for configuring DHCP failover. I am sure it will help you to completing your task.
1> Step-by-Step: Configure DHCP for Failover
http://technet.microsoft.com/en-us/library/hh831385.aspx
2> DHCP Step-by-Step Guide: Demonstrate DHCP Failover – Clustering in a Test Lab
http://technet.microsoft.com/en-us/library/ee405263(v=ws.10).aspx
Process of Migration DHCP Server 2008R2 to Windows 2012
• Firstly, you can disable the DHCP role in Windows Server 2008 R2. However, if the Windows Server 2012 is down, the clients cannot renew their IP lease duration and obtain IP address.
Therefore, it is recommended to leave the DHCP role in Windows Server 2008 R2 and deploy high availability. Windows Server 2012 brings the new feature: DHCP failover. However it requires both DHCP Servers are Windows Server 2012. Consider another Server
is Windows Server 2008 R2, we have to choose one of the following:
>> DHCP in a Windows failover cluster. This option places the DHCP server in a cluster with an additional server configured with the DHCP service that assumes the load if the primary DHCP server fails. The clustering deployment option uses
a single shared storage. This makes the storage a single point of failure, and requires additional investment in redundancy for storage. In addition, clustering involves relatively complex setup and maintenance.
>> Split scope DHCP. Split scope DHCP uses two independent DHCP servers that share responsibility for a scope. Typically 70% of the addresses in the scope are assigned to the primary server and the remaining 30% are assigned to the backup server.
If clients cannot reach the primary server then they can get an IP configuration from the secondary server. Split scope deployment does not provide IP address continuity and is unusable in scenarios where the scope is already running at high utilization of
address space, which is very common with Internet Protocol version 4 (IPv4).
More references:
Step-by-Step: Configure DHCP for Failover (Windows
Server 2012)
How
to configure split-scope using wizard
DHCP
Step-by-Step Guide: Demonstrate DHCP Split Scope with Delay on a Secondary Server in a Test Lab
DHCP
Step-by-Step Guide: Demonstrate DHCP Failover – Clustering in a Test Lab
If you need snap shot of migration then follow these links.
http://blogs.technet.com/b/canitpro/archive/2013/04/29/step-by-step-migration-of-dhcp-from-windows-server-2003-to-windows-server-2012.aspx
http://www.mehrban.net/migrating-dhcp-from-windows-2008-to-windows-2012
Deepak Kotian.
MCP, MCTS, MCITP Exchange 2010 Ent. Administrator
Disclaimer:
Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!
All the opinions expressed here is mine. This posting is provided "AS IS" with no
warranties or guarantees and confers no rights. -
Can I use ASA to be a DHCP Server use in WLC wireless Client
I want to use ASA to be a DHCP Server for Wireless Client not it can't.
I check the debug log in WLC, I confirm the WLC have send the request to ASA.
In the ASA, it don't have any hits in the rule when the WLC send the DHCP relay request.
I have try don't use dhcp relay in WLC but don't success. Anybody have the same case with me? And Is the ASA can't support DHCP relay agent to request to get the IP Addr.
P.S. In the Network Design limitation so I can't use WLC to be DHCP Server.
Equipment:
ASA5510
WLC4402
How can I fix it.
Thank you very muchThe issue is that the ASA doesn't accept DHCP requests from a relay agent, only broadcast DHCP requests. In the 4.2 version for the controllers there is now an option so you can change the way the controller forwards DHCP requests so that it is sent as a broadcast and not from a relay agent.
-
WLC 5508, vlan select, reserved address in external DHCP server
Hi guys,
I have a deploy with a WLC 5508 version 7.0.116.0, APs mode local and vlan select feature enable. The issue is that the reserved IP address in external DHCP server not work. The DHCP contains a reserved IP address associates with mac address, but the assignement of IP is not match with de policies in DHCP. All others services operate normally.
This reserved assignment operate previusly to modificate the WLAN to vlan select feature. Help me to improve this situation.
Thanks.-
Best regardsHello Abhishek, thanks for you quick answer....
the link was a document used for the deploy, but not especifict nothing about the reserved IP address for particular host. In other words, the reserved IP address (through MAC address) in external DHCP server not work when "vlan select" its enable. -
WLC 7.0.230.0 - Incorrect DHCP addresses being allocated by internal DHCP server
Background:
Initially there were 3 SSIDs configured but all of them were assigned a single interface and this interface was configured with the controller management IP address as DHCP server so that the WLC could assign IP addresses to wireless clients, guns and printers etc.
Issue:
As part of PCI initiative, we decided to segment the traffic in multiple subnets based on type of wireless clients; so now there are 3 interfaces configured and each SSID is assigned a specific dynamic interface and each interface is configured to use the controller management IP address as DHCP server.
There are 3 scopes configured for each of the dynamic interfaces/SSIDs and DHCP proxy is enabled but wirelss clients are still being allocated IP addresses from the original DHCP scope that was associated with the dynamic interface originally assigned to all 3 SSIDs.
What am I missing here?
I verified the following:
1. Each SSID is assigned a different dynamic interface (Users, Voice and Handhelds)
2. Each dynamic interface is configured to use controllers management IP address as DHCP server
3. DHCP scopes configured with correct network information for each dynamic interface and enabledAs mentioned in my first post, I am using the management interface IP address of the controller as the DHCP server in the configuration of all the dynamic interfaces.
I have not configured the override DHCP option in the WLAN configuration becuase I have specified the internal DHCP address in the dynamic interface.
But I did check the AP group configuration and there I found that the SSID is not assigned to the correct dynamic interface even if the WLAN configuration is correct.
I will change the AP group configuration to correct this. Thanks! -
WLC 5760 with internal DHCP server, clients no get IP address
Hi all,
I have 2 Cisco 5760 WLC (active-standby) IOS-Xe 03.03.03SE with one WLAN.
sh wlan summary
Number of WLANs: 1
WLAN Profile Name SSID VLAN Status
1 Invitados_ADSL Guest 905 UP
sh vlan
VLAN Name Status Ports
1 default active Te1/0/3, Te1/0/4, Te1/0/5, Te1/0/6, Te2/0/3
Te2/0/4, Te2/0/5, Te2/0/6
100 VLAN0100 active Te1/0/1, Te2/0/1
101 Planta_1 active
905 Internet active Te1/0/2, Te2/0/2
The DHCP server is internal.
Sometimes the clients no get IP address and the DHCP pool has IP addresses available.
The workaround done by me to solve the issue is “clear ip dhcp binding *”.
Some days later the problem appears again.
I see this bug with a similar problem:
NGWC blocks DHCP traffic if wireless broadcast disabled
CSCun88928
Description
Symptom:
Some clients set the BROADCAST flag on the DHCP Discover packet. This requires the DHCP server to reply with a broadcast.
In that case and if you are not using DHCP snooping on the 5760/3850, then the controller will block the return traffic unless you enable "wireless broadcast" which enables broadcast globally (and is thus not always desirable)
Conditions:
Seen on 3.3.2 IOS-XE
Workaround:
Use DHCP snooping with the "ip dhcp snooping wireless bootp-broadcast command"
OR
Enable "wireless broadcast" globally
My DHCP configuration is:
ip dhcp relay information trust-all
ip dhcp snooping vlan 905
ip dhcp snooping
ip dhcp excluded-address 172.16.0.1 172.16.0.19
ip dhcp excluded-address 172.16.1.250 172.16.1.254
ip dhcp pool Invitados
network 172.16.0.0 255.255.254.0
default-router 172.16.0.1
dns-server 212.66.160.2 212.49.128.65
lease 0 8
I see in Cisco documentation (http://www.cisco.com/en/US/docs/wireless/technology/5760_deploy/CT5760_Centralized_Configuration_eg.html) this configuration:
DHCP Snooping and Trust Configuration on CT5760
ip dhcp snooping vlan 100, 200
ip dhcp snooping wireless bootp-broadcast enable
ip dhcp snooping
interface TenGigabitEthernet1/0/1
description Connection to Core Switch
switchport trunk allowed vlan 100, 200
switchport mode trunk
ip dhcp relay information trusted ip dhcp snooping trust
interface Vlan100
description Client Vlan
ip dhcp relay information trusted
My question is,Do I have to add the command "ip dhcp snooping wireless bootp-broadcast enable" to solve the issue?
Thanks in advance.
Regards.
DYes, test it with the command you mentioned
ip dhcp snooping wireless bootp-broadcast enable
HTH
Rasika
**** Pls rate all useful responses ***** -
5508 WLC + 3702I APs /w a Windows 2012 DHCP Server
All,
I am in the process of a new WLC install with five 3702I APs. The configuration was gone well up till now..... I am having issues with DHCP pulling IPs from the correct scope. The WLC is in a different VLAN (10) than the APs (142). What am I missing in the configuration? We have multiple autonomous 1252s that pull the correct scope. Any suggestions would be greatly appreciated.
DaveAre you having issues with client getting IP when they connect to 3702 ? or AP itself not taking IP ?
Either case I would check switch SVI is configured with "ip helper-address x.x.x.x" pointing to your DHCP server.
Also for dynamic interface configuration of WLC I would check all interfaces correctly configured with DHCP server address.
You can run " debug client <mac_address>" on WLC CLI for a single client & post that output if you still facing the issue
HTH
Rasika
**** Pls rate all useful responses **** -
Configuring the 3750G WLC to use the Internal DHCP Server
I want to use the Internal DHCP Server on a 3750G WLC to hand out IP's to gueat users. I'm having issues getting the DHCP server to hand out addresses for the guest network - any suggestions would be a great help.
Configuration Details are attached.Configuring DHCP
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52wlan.html#wp1293808 -
Hi,
i have a test setup with a WLC-526, a few AIR-LAP521 and a 2621 with an ios 12.2.31 . I' not abel to associate the 521 to the WLC. I have configured an DHCP server on the Router with option 43 ascii "ap-managent-address" of the WLC. The DHCP server packet debug looks like :
DHCPD: DHCPDISCOVER from
DHCPD: Sending DHCPOFFER to
DHCPD: broadcasting BOOTREPLY to
DHCPD: DHCPDREQUEST received
DHCPD: Sending DHCPACK to
DHCPD: broadcasting BOOTREPLY to
and about 20 sec later :
DHCPD: DHCDPRELEASE message received
Has someone an idea how to configure a dhcp server for a 521 correctly. ?
Thankx
J?rgHi Carl
It's the real address. And if you are using secondary IP's it's still the primary real address.
Simon
Maybe you are looking for
-
I am new to this. My question is as per the header line.
-
Cannot compile java beans in my jsp page
Hi all I have created jsp pages which contains java beans. Now its working fine on my machine(XP OS) but when i put it on windows 2000 server it gives the following error: type Exception report message description The server encountered an internal e
-
Back and sharing solution for Macbook Pro - Synology or Time Capsule?
Hi Hi, My plan is to have a complete new efficient and flexible set up. I have decided to buy the new Macbook 13inch Pro with 16MB Ram and 3.1 Ghz i7 processor with 256GB glash drive. I want an external solution for my storage and sharing needs. Mini
-
I get a message that I have exceeded my 5 computers that I am allowed to have 2 of those computers no longer exsist How do I correct this?
-
need to create object to calculate age of an employee when he employed using two columns i.e. date of employment and dob, both columns are in different table. how to do that? let me know if you need more info thanks & regards