[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 831
  • Last Modified:

Can a Cisco 4402 WLC use a Windows DHCP scope to hand out leases?

We have ~150 remote offices and are looking for methods to inexpensively deploy more computers. One consideration is wireless. The remote desktops already receive their DHCP addresses via a Cisco forwarder address in GRE tunnel of a 1700 series router. Some sites already have 11/12/1300-series aironet on-site where the aironet 172.16.x.x route goes through the GRE tunnel back to the 4402 controller, where the aironets pickup their DHCP address scope. What I'd like to know is, in the interest of managing all of the DHCP from a single GUI, can the 4402 some how lookup/use the DHCP scope on the Windows server which the desktops are using to obtain their DHCP?
0
JimMueller
Asked:
JimMueller
  • 4
  • 3
1 Solution
 
wingateslCommented:
Definitely, you just need to set option 43 on the dhcp scope as you would on the WLC
0
 
JimMuellerAuthor Commented:
We already have option 43 configured in DHCP. Each site has their own DHCP scope...

Let's say remote site "1234" has network 10.12.34.0/26 and remote site "5678" has network 10.56.78.0/26. The DHCP range for both is .50-.62. Our WLC is on 192.168.0.0/24. Right now a remote wireless client will pull a 192.168.3.0/24 address from our WLC regardless if they are at site 1234 or at site 5678. I want to know how we get the remote wireless client to have a 10.12.34.0/26 DHCP address when at site 1234, but a 10.56.78.0/26 DHCP address when at site 5678, etc.

When the wired clients lookup their DHCP address, it finds the router DHCP option which matches the inside LAN default gateway. I guess I'm hoping that there's a way for the WLC to also look at the same information to find the matching scope. Hopefully that clarifies my question.
0
 
wingateslCommented:
Ahh, you will need different vlans for that to happen. Or a separate controller for each location. The vlan gets trunked back to the controller. If you set a new vlan and new ssid for each location you can get the effect youwant.
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
JimMuellerAuthor Commented:
The separate controller per site isn't an option. Where would we need to add the vlans? I seem to recall the Cisco 1711/1721 were using at the remote sites only allows a single vlan (which is already in use).
0
 
wingateslCommented:
The VLAN is at the HQ where the WLC exists. The SSID is trunked to the Controller, so your VLAN's endpoints would be whereever the controller is. Without the additional controllers there is no way to get the VLAN to terminate at the branch.
0
 
JimMuellerAuthor Commented:
OK, although I had hoped the solution would be simpler, the points are yours :)
0
 
JimMuellerAuthor Commented:
Thank you for taking the time to answer my question!
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now