Here's ours... we use option 43 and we set the 'campus' code later in the
config so that we can pass different controllers based on different parts of
the campus. The link in the comments will take you to the cisco doc for their
LWAPs.
option campus code 180 = string;
option controllers code 43 = string;
class "wireless_controller" {
match hardware;
default-lease-time 604800; # 7 days.
max-lease-time 1209600; # 14 days.
min-lease-time 604800; # 7 days.
#
http://www.cisco.com/univercd/cc/td/doc/product/wireless/airo1130/1130hig5/113h_g.htm#wp1007971
#
# The hex string is assembled by concatenating the TLV values shown
below:
# Type + Length + Value
#
# Type is always f1(hex). Length is the number of controller management
IP addresses
# times 4 in hex. Value is the IP address of the controller listed
sequentially in hex.
#
# For example, suppose that there are two controllers with management
interface IP addresses,
# 10.126.126.2 and 10.127.127.2. The type is f1(hex). The length is 2
* 4 = 8 = 08 (hex).
# The IP addresses translate to 0a7e7e02 and 0a7f7f02. Assembling the
string then yields
# f1080a7e7e020a7f7f02. The resulting Cisco IOS command added to the
DHCP scope is listed below:
#
# option 43 hex f1080a7e7e020a7f7f02
if config-option campus = "north" {
log(error, "wireless controller - north");
# North
# 10.3.240.2 == 0A.03.F0.02
# 10.3.240.4 == 0A.03.F0.04
option controllers f1:08:0a:03:f0:02:0a:03:f0:04;
} elsif config-option campus = "south" {
log(error, "wireless controller - south");
# South
# 10.3.241.2 == 0A.03.F1.02
# 10.3.241.4 == 0A.03.F1.04
option controllers f1:08:0a:03:f1:02:0a:03:f1:04;
} else {
log(error, "wireless controller - no campus");
log(error, "handing off no controllers!");
}
}
-----------------------------------
Robert G Colantuoni
Senior Programmer Analyst
CIT - Network and Classroom Services
SUNY Buffalo
[email protected]
716.645.3552
> -----Original Message-----
> From: The EDUCAUSE Wireless Issues Constituent Group Listserv
> [mailto:[email protected]] On Behalf Of Danner, Mearl
> Sent: Thursday, June 02, 2011 11:37 AM
> To: [email protected]
> Subject: Re: [WIRELESS-LAN] option 43 for finding master controller
>
> 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/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
