Here's ours - at the top of dhcpd.conf. We got it from:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml
option space Cisco_LWAPP_AP;
option Cisco_LWAPP_AP.server-address code 241 = string;
class "Cisco AP c1130" {
match if option vendor-class-identifier = "Cisco AP c1130";
option vendor-class-identifier "Cisco AP c1130";
vendor-option-space Cisco_LWAPP_AP;
option Cisco_LWAPP_AP.server-address
ac:1e:00:0d:ac:1e:00:96:ac:1e:00:97:ac:1e:00:98:ac:1e:00:99;
}
My assumption would be to declare the class definitions at the top and move the
option line to the scope.
Can't remember why we hex encoded the controller addresses.
-----Original Message-----
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[email protected]] On Behalf Of Ken Connell
Sent: Thursday, June 02, 2011 10:11 AM
To: [email protected]
Subject: Re: [WIRELESS-LAN] option 43 for finding master controller
The following is at the top of my dhcpd.conf:
option serverip code 43 = ip-address;
class "vendor-class" {
match option vendor-class-identifier;
}
.
.
.
Scope is as follows:
subnet 10.16.0.0 netmask 255.255.254.0
{
option broadcast-address 10.16.1.255;
option domain-name "rbb.ryerson.ca";
option domain-name-servers 141.117.100.1, 141.117.100.4;
option routers 10.16.0.1;
range 10.16.0.5 10.16.0.9;
default-lease-time infinite;
max-lease-time infinite;
subclass "vendor-class" "ArubaAP" {
option vendor-class-identifier "ArubaAP";
#
# option serverip <loopback-IP-address-of-master-controller>
#
option serverip 10.10.10.1;
}
}
Ken Connell
Intermediate Network Engineer
Computer & Communication Services
Ryerson University
350 Victoria St
RM AB50
Toronto, Ont
M5B 2K3
416-979-5000 x6709
----- Original Message -----
From: "Danner, Mearl" <[email protected]>
Date: Thursday, June 2, 2011 9:48 am
Subject: Re: [WIRELESS-LAN] option 43 for finding master controller
To: [email protected]
> We use it globally for our Cisco LWAPPs, but not per scope. The ISC
> server is a bit ticky about using class declarations. I worried with
> it (not pertaining to LWAPPS) several years ago. The manner of
> declaring and using them is not intuitive.
>
> Could you show us relevant areas of your dhcpd.conf (obfuscated if
> necessary)? Might bring back an unfond memory of the struggle.
>
> -----Original Message-----
> From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> [mailto:[email protected]] On Behalf Of Ken Connell
> Sent: Thursday, June 02, 2011 7:42 AM
> To: [email protected]
> Subject: [WIRELESS-LAN] option 43 for finding master controller
>
> Is any one using this on a per-scope basis with an ISC DHCP server ?
>
> We're an Aruba shop an currently find our masters via dns, but are
> also exploring giving the master controller address via DHCP option
> 43.
>
> We currently have this working on a limited basis and have it defined
> in a particular scope, but have found that its seems to be working as
> a global option.
>
> So, and AP that gets DHCP from this server via a different subnet and
> therefore a different scope that does not have the subclass details
> for the master controller defined, in the end still gets the IP
> address as defined in a different scope.....
>
> I wondering if this is just how it works ? or can a define different
> master controllers on a per-scope basis ?
>
>
> Ken Connell
> Intermediate Network Engineer
> Computer & Communication Services
> Ryerson University
> 350 Victoria St
> RM AB50
> Toronto, Ont
> M5B 2K3
> 416-979-5000 x6709
>
> **********
> Participation and subscription information for this EDUCAUSE
> Constituent Group discussion list can be found at
> http://www.educause.edu/groups/.
>
> **********
> Participation and subscription information for this EDUCAUSE
> Constituent Group discussion list can be found at
> http://www.educause.edu/groups/.
>
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
