Internal DHCP in controller

dear
i wanna to configer internal dhcp in WISM
how can i
i need the pool start from 10.30.101.50 t0 200 /24 (255.255.255.0)
the network 10.30.101.0
netmask 255.255.255.0
the defoult router must be the WISM-A ip address
10.30.101.2
also i configured the DNS
and put in the ap-manager interface the primary DHCP server the ip 10.30.101.2
and i changet to 10.30.101.1
and its not work whats the mistake and what i shoul do ?i tried to use external dhcp server for ap 1020 and configure dns , optoin 43 but the ap didnt took any ip address
wism-a management 10.30.101.2
ap manager 10.30.101.3
vlan id 101
subnet 255.255.255.0
the client vlan is 202 ip 10.30.202.3
and all port access to this vlan in the edge switch
please advice

ip dhcp excluded-address 10.30.101.50 10.30.101.200, network 10.30.101.0, default-router 10.30.101.2

Similar Messages

Controller 4400 Internal DHCP

Hy, I have a wireless controller 4400 and I am using internal DHCP.I am unable to receive a IP address from the switch connected to the controller.
Thr debug messages are:
DHCP Op: BOOTREQUEST(1), IP len: 300, switchport: 1, encap: 0xec00
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option len, including the magic cookie = 64
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: received DHCP DISCOVER msg
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: skipping option 116, len 1
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: skipping option 61, len 7
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: requested ip = 10.0.10.30
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: skipping option 12, len 4
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: vendor class id = MSFT 5.0 (len 8)
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcp option: skipping option 55, len 11
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcpParseOptions: options end, len 64, actual 64
Tue Sep 5 08:07:31 2006: 00:01:03:8d:43:5f dhcpProxy: Dropping packet (no mscb) from STA 00:01:03:8d:43:5f, giaddr:0.0.0.0, udpSrcPort:68, op:1
Tue Sep 5 08:07:39 2006: 00:01:03:8d:43:5f dhcpProxy: Received packet: Client 00:01:03:8d:43:5f
someboby can help me???
Thanks

hi ,
you have to create a scope for that vlan and on management interace for dhcp server give management ip address ;
so a sample cli to create scope is :
config dhcp create-scope 53
config dhcp address-pool 53 10.50.53.100 10.50.53.200
config dhcp default-router 53 10.50.53.1
config dhcp dns-servers 53 10.50.1.21
config dhcp domain 53 blr.airesace.com
config dhcp lease 53 120
config dhcp netbios-name-server 53 10.50.1.21
config dhcp network 53 10.50.53.0 255.255.255.0
config dhcp proxy enable
config dhcp enable 53
let me know if you face any problem ; send me the screen shot of the error
regards
seema

Can i use Internal DHCP on WLC Guest Anchor (5508) with Foreign HA 5508

DHCP Proxy is required in order to use local WLC DHCP Pool (Guest Anchor), however reading Wireless Q&A (http://www.cisco.com/image/gif/paws/107458/wga-faq.pdf) states that both foreign and guest anchors must have :
In a Wireless guest access setup, the DHCP proxy setting in the Guest Anchor controllers
and the internal controller must match. Else, DHCP request from clients are dropped and you
see this error message on the internal controller......
However if you have N+1 you cannot use internal DHCP, does this also "grey" out the DHCP Proxy global setting? If so will the Guest Anchor still work with a internal DHCP pool even though foreign and guest controllers have a mismatch in DHCP Proxy (global) setting?
Many Thanks
Kam

Well it should still work... dhcp proxy is required on the WLC that has a dhcp scope. With the newer code versions, you can enable dhcp proxy on a per interface do this doens't have to be global.

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,
Robert

You 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 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 enabled

As 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 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...................................... 100

Hi 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

WLCs 5508, HA enabled and Internal DHCP

Hi:
Designing a new project for a customer in which a pair of WLC-5508 and a bunch of AP-3602I will be deployed.
Controllers running 7.4 image, and I'd also like to use them as internal DHCP servers for clients in different WLANs
As for the redundancy mechanism I'd go for activating HA (AP-SSO) but I know HA and internal DHCP server can't coexist.
So, my question is: does anyone know if Cisco is thinking of implementing both features in any new version to come? The goal would be the Active controller handing over all leases database in case of active to standby switchover.
Thx!
Juan.

As you already know that HA and DHCP both cannot coexist on WLC. Till now there is no plan of cisco to implement this.

5508 internal DHCP server

Hi,
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 ServerThe 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)?
Thanks.

#DHCP proxy needs to be enabled to use internal dhcp on WLC. WLC uses virtual ip for dhcp and they're unicast. So keeping the AP on L3 doesn't work with internal dhcp. dhcp for wireless client works due to the packets are sent to WLC via capwap.
#The DHCP required state can cause traffic to not be forwarded properly if a client is deauthenticated or removed. To overcome this problem, ensure that the DHCP required state is always disabled.
Ans: it is expected behavior irrespective of dhcp being internal or external, it is a feature and not disadvantage.
Cons:-
#can't have dhcp reservations.
#can't have option 43 or any other dhcp options.
#DHCP service can't be restarted, WLC reboot is required if needed to so.
#If Multiple WLCs used, need to create non overlapping scope on other WLCs as well.
#Wired clients cannot get ip from internal dhcp. So need to maintain separate network & dhcp server for wired network, and this require routing.
#From WLC GUI, Can't remove the client, need to use cli.
#WLC reboot may clear the dhcp lease, though not sure 100%

Internal dhcp with anchor and foreign

Greetings,
trying to get dhcp going for guest clients.
I can see dhcp requests coming through and getting dropped at the foreign controller.
*DHCP Socket Task: Aug 10 16:19:54.075: 58:94:6b:1d:xx:yy DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 13, encap 0xec03)
*DHCP Socket Task: Aug 10 16:19:54.075: 58:94:6b:1d:xx:yy DHCP dropping packet
Could someone tell me;
1. why would the DHCP requests processed by the foreign controller instead of the anchor ?
2. do i need to configure dhcp server under the guest WLAN interface on foreign?
I thought all L3 and security stuff is forwarded over eoip to anchor and therefore no need to configure the DHCP server under foreign.
I'm trying to utilise the internal DHCP server (firmware 7.0.220) but so far its not going well.
Thanks,
silva

Hi All,
Steve you got me thinking and thanks to the debugs you provided, I managed to fix the issue.The problem was caused by local EoIP tunnel that was configured on the foreign and thus traffic was not getting forwarded.Strange thing I can't remember configuring that as it was not required.Anyway after I removed it, all worked as expected. I'm using internal DHCP and so far it is is working fine as well.
With the ACLs, for guest WLAN, do we neded to configure for both foreign and anchors so that the WLAN configs are identical?
Does not make any sense to me to configure the ACLS on the foreign but can someone confirm?
Silva

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

Internal DHCP on WiSM

Hi all!
Tell me, please.
Can I use internal DHCP server for my APs ?
I have next syslog message from Wism :
"DHCP-6-MSGTAG094: Dropping packet from 10.77.114.250 (unable to match to adhcp scope)"
10.77.114.250 it is inerface DHCP Relay.
The debug show next:
>Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcpProxy: Received packet: Client 00:0a:b8:3b:0b:02
DHCP Op: BOOTREQUEST(1), IP len: 576, switchport: 29, encap: 0xec00
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option len, including the magic cookie = 340
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: received DHCP DISCOVER msg
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: skipping option 57, len 2
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: skipping option 61, len 7
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: skipping option 12, len 16
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: skipping option 55, len 8
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcp option: vendor class id = Cisco AP c1200 (len 14)
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 dhcpParseOptions: options end, len 340, actual 65
Tue Nov 13 17:01:32 2007: 00:0a:b8:3b:0b:02 Received a DHCP Request from Gateway 10.77.98.62 for STA 00:0a:b8:3b:0b:02
-- bouncing to local DHCP server.
Tue Nov 13 17:01:32 2007: dhcpd: sending 301 bytes raw 10.77.114.250:67 -> 10.77.97.51:1067
Tue Nov 13 17:01:32 2007: dhcpd: Received 301 byte dhcp packet from 0x0a4d72fa 10.77.114.250:67
Any idea ?
Thanks in advance,
Basil

The design in principle is correct, you will need to ensure that there is a way of delivering the controller IP addresses to the access point, either by dns, DHCP option 43 (not support on the internal DHCP server)or by pre staging the APs prior to deployment.
You can use the internal DHCP server for wireless clients by defining itself as the DHCP server address under interface.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809d5097.shtml
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
Hope this helps

Using internal DHCP in WLC 4112

Hi Guys,
I want to make my wireless place into different network. So i define the 3 internal dhcp scope inside WLC. My WLC LWAPP set to layer 2. My problem is, the clients are not able to get the IP address into WLC dhcp scope. Please help me what to do
thanks,
Jong

hi jong,
as far as I know the WLC isn't a router but I think you have a router somethere in your network(layer3 switch for example) where you need a virtual interface for each VLAN and the ip of this interface is your default-router for the corresponding clients.All ports of the WLC are Trunkports but you can also use one as an access port for an specified vlan. I would recommend to configure the controller as follows,
ap-manager and management interface same vlan but different ip addresses, dynamic interfaces for each WLAN with different vlan ID's, map all interfaces to a physical port of the WLC, make sure the switch where the WLC is connected is configured as trunk with the needed VLAN's, make sure you have each VLAN also configured in your network infrastructure,
hope this will help you.
regards,
Rocco

Will the 2504 WLC internal DHCP give IP addresses to clients?

Is there a way to configure the 2504 WLC so that its internal DHCP only services the LAPs?
I don't want the controller to give out IP addressed to wireless clients.
Thanks

No.
DHCP on the WLC is never intended to offer DHCP services to any "wired" side devices, which includes your APs. These DHCP pools are specifically to hand addresses out to wireless clients attached to WLANs of the specific WLC it is configured on. Even then, unless you absolutely cannot offer DHCP somewhere else, DHCP on the WLC is not a suggested practice.
DHCP Pool Configuration and Restrictions.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_01000110.html

Cisco 1702i WAP: how to get an interface in a non-native bridge group/ VLAN to be recognized by the internal DHCP server

Does anyone know how the internal DHCP server in these access points connects to virtual interfaces and bridges in the unit?
Is there some sort of default connection that connects the DHCP server to the native bridge group or VLAN?
In a test case, with an SSID in the native VLAN and bridge group, the 1702i serves an IP address to a wireless client no problem. But with a second SSID in a non native VLAN and bridge group, no IP gets served. My only guess is that since the bvi1 defaults to the native bridge group and VLAN, sub-interfaces also in this group are assumed to be in the same subnet as bvi1, or in this case:
interface bvi1
ip address 192.168.1.205 255.255.255.0
no ip route-cache
exit
It would be the ..1. subnet.
Since the dhcp pool is set as:
ip dhcp pool GeneralWiFi
network 192.168.1.0 255.255.255.0
lease 1
default-router 192.168.1.1
dns-server 8.8.8.8
exit
There may be an assumption that anything bvi1 can talk to is in the ..1. subnet, so the above pool gets activated on a request coming through bvi1.
Is the DHCP server just hanging out waiting for a request from an "area" that is assumed to be on the same subnet as the given pool?
Do I need to somehow show the device what subnet the 2nd SSID/ subinterfaces are in so the internal DHCP server can decide it needs to go to work, or is there some sort of bridging between the DHCP server and the interfaces that needs to be done? I am trying to use the same DHCP pool for the second subnet at this point, since I assume I will need another router to service an additional subnet and DHCP pool.

Keep in mind that DHCP is a broadcast packet to start. So the AP can only listen in the subnet that it has an IP address for.
Now, for any other subnet you can use the AP for DHCP but you have to have an IP helper address on your L3 pointing back to the AP.
That being said, I wouldn't use the DHCP server on the AP as it is limited. You'd be better off using a Microsoft server or some other device that is designed for DHCP.
HTH,
Steve

VirtualBox 4.0.2 internal DHCP problem in Host-only mode?

Hi,
dos anyone have experience problems with VirtualBox 4.0.2 internal DHCP not working when running Oracle Linux and a Host-Only adapter.
More detailed described my problem is that Oracle Linux don't get a ip from the internal DHCP server om my system. My host is Win 7 (64 bit) and Guest Oracle Linux (64 bit). I have read that there are several ohers who experienced the same problem with the open source version, but that patching the Guest Tools to 4.0.3 helped them. Sadly this is not the case for me. Any suggestions are welcome and thanks in advance.

Thanks for your reply - my problem is that the build in dhcp server is not working for some reason and i dont't gen any ip address assigned. I can see from the VBoxManager that it is running, but i can't get i contact with it from the linux guest.

Internal DHCP in controller

Similar Messages

Maybe you are looking for