DHCP option to define Controller IP for Access-Points (Airespace)

[jsteffensen]

Hi Everybody.

Does anyone have an idea of specifying the Controller by using DHCP options.

We are using :

- AIR-WLC4404-100-K9 Controller

- AP-1010 AP-5312 Access-poinst

- ISC DHCPd 3.0.1 dhcp-server

The logs on DCHP server states that the Access-points are getting the IP-Addresses, but the information about the controller is not "read" / "understood".

In productive environment the controllers will be redundant.

Until now we have not been sucsessful with eighter of these configurations:

I. Using VTL block:

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_quick_start09186a00805100f5.html#wp49287

subnet 10.50.107.0 netmask 255.255.255.0 {

option subnet-mask 255.255.255.0;

option routers 10.50.107.1;

option domain-name-servers 10.20.51.11, 10.20.51.12;

option vendor-class-identifier “Airespace 1200”;

option dhcp-client-identifier 0xf1, 8, 10.20.51.254, 10.20.51.249;

ddns-updates on;

ddns-rev-domainname "in-addr.arpa.";

ddns-domainname "xxyy.local.";

default-lease-time 28800;

range 10.50.107.101 10.50.107.200;

}

II. Using DHCP Next-Server option:

subnet 10.50.107.0 netmask 255.255.255.0 {

option subnet-mask 255.255.255.0;

option routers 10.50.107.1;

option domain-name-servers 10.20.51.11, 10.20.51.12;

next-server 10.20.51.254;

III. Using Header Information Option 43 as described in DHCP manual:

option wlan-apc code 60 = text;

option wlan-controller code 43 = ip-address;

subnet 10.50.107.0 netmask 255.255.255.0 {

option subnet-mask 255.255.255.0;

option routers 10.50.107.1;

option domain-name-servers 10.20.51.11, 10.20.51.12;

option wlan-apc "Airespace.AP1200";

option wlan-controller 10.20.51.254;

IV. Using header Information in DHCP Server:

class "vendor-classes" {

match option vendor-class-identifier; }

subclass "vendor-classes" "Airespace.AP1200" {

next-server 10.20.51.254;

}

Does anyone have a working configuration (using ISC ?) or any hints?

Best Regards

Jarle Steffensen

[jsteffensen]

Hi Everyone

So far this seems to be the solution for us:

Configured on the DHCP'server:

option controller code 43 = text;

option controller "";

=========================

option controller code 43 = text;

option controller "10.20.51.254,10.20.51.249";

Greetings

Jarle Steffensen

[lldemeyer]

I have a similar problem,my AP1000 is receiving a DHCP ip address but there seems to be a problem in obtaining the WLC's mgmt ip address via DHCP option 43 . I am using a Win2003 DHCP server and have configured the VCI string "Airespace 1200" as shown in a Cisco Application Note

In there they say that the Airespace(Cisco1000) uses a string format whereas the Cisco AP's use TLV format. Any idea how to enter a string format in Win2003 DHCP servers ?

Thanks,

Luc De Meyer

[mkakhovsky]

Hi,

We're also running a WLC4402 with AP-1010 access points. Here's a ISC DHCPd config that works for us:

--cut--

ddns-update-style interim;

option wlan-controller code 43 = text;

subnet 10.10.10.0 netmask 255.255.255.0 {

default-lease-time 600;

range 10.10.10.50 10.10.10.200;

option subnet-mask 255.255.255.0;

option routers 10.10.10.1;

option domain-name-servers 10.10.5.60, 10.10.3.110 ;

class "vendor-classes" {

match option vendor-class-identifier; }

subclass "vendor-classes" "Airespace.AP1200" {

option wlan-controller "10.10.5.200";

}

}

--cut--

Like the documentation says, option 43 should be in string format for 1000 series APs. Note that the VID string should be "Airespace.AP1200", not "Airespace 1200" as stated in the documentation!

I still can't get the same configuration to work with Windows 2003 DHCP services. I see the server send proper option 43 in the DHCP offer, but the APs seem to ignore it and never associate with the WLC.

Does anyone have Windows 2003 DHCP working with 1000 series APs?

Thanks

Max

[bsigmund]

Jarle,

Don't know if this helps, but I have it working on Red Hat Linux with Cisco 4400 controllers and 1510 series LWAPPs. It should be the same for the 1200 series LWAPPs. My dhcpd.conf is below.

# wireless

ddns-update-style ad-hoc;

option wlan-lwap code 60 = text;

option wlan-controller code 43 = ip-address;

subnet 10.90.23.0 netmask 255.255.255.0 {

option domain-name "nodomain.com";

option domain-name-servers

10.90.23.100;

option routers 10.90.23.254;

option wlan-lwap "Cisco AP.LAP1510";

option wlan-controller 10.90.23.51;

authoritative;

allow client-updates;

allow unknown-clients;

ddns-update-style ad-hoc;

pool {

range 10.90.23.20 10.90.23.50;

}

[dal]

I too have tried to set this up on a Windows 2003 server, but no luck.

I have used this guide: http://www.ciscosystems.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp125304

together with Airespace.AP1200 as VCI string.

When I make a similar scope on my C3550 it works like a charm. This is how it looks on the C3550:

ip dhcp pool APTest

network 10.10.71.0 255.255.255.0

default-router 10.10.71.1

dns-server 10.10.10.70

option 60 ascii "Airespace.AP1200"

option 43 ascii "10.37.0.11"

lease 0 0 5

If anyone could tell me what's missing to make it work on Win2003, it would be much appreciated.

Thanks

[dagyb]

It won't work on a Win 2003 DHCP server, I hooked up a sniffer and watched the whole conversation, the AP announces it's self, the server returns the controller address, and a debug DHCP on the AP confirms that the AP received the address but just wouldn't use it.

But when you set it up on an IOS device it works fine.

I even opened a TAC case and they too thought it should work, but it doesn't, bottom line don't waste a lot of time on it.

[dal]

Not the answer I was hoping for, but a good answer nevertheless :)

Only one thing left to try then, I saw service pack 2 for Win2003 is released now, so will try that one before I give up.

I'll let you know how it goes.

[dal]

Have upgraded to Service Pack on the Windows 2003 server now, but still no luck :(

Anyone out there got this to work?

[dal · Accepted solution]

Yessss, finally got this to work.

I simply followed this guide:

http://www.cisco.com/univercd/cc/td/doc/product/wireless/control/c44/dep.pdf

and it worked at first attempt :)