Option 43 and WLC redundancy

[r.roudi]

I am planning to split AP's between 2 WLC's. Also need to configure DHCP option 43, since the Management and AP-Manager interfaces will be on a different VLAN than APs.

Is Option 43 going to overwrite the primary/secondary controller configuration on AP's?

Thanks for replies.

[Scott Fella]

Option 43 provides information to a new LAP what WLC's are out on the network. As long as you have all the management ip addresses configured. The primary, secondary and or tertiary is not overwritten by option 43. When mobility is working between the WLC's and AP Fallback is enabled, then whatever you configure as primary, secondary and or tertiary will take priority over what the LAP learned from option 43.

[r.roudi]

Thanks for quick reply and good info.

[ericgarnel]

in ISC dhcp you can do the following:

# DHCP Server Configuration file.

# see /usr/share/doc/dhcp*/dhcpd.conf.sample

#

authoritative;

ddns-update-style none;

ignore client-updates;

allow unknown-clients;

option space cisco-lwapp;

option cisco-lwapp.lwapp-controllers code 241 = array of ip-address;

option cisco-lwapp-encap code 43 = encapsulate cisco-lwapp;

#### WIFI Mgmt Subnet 192.168.10.0 ######

subnet 192.168.10.0 netmask 255.255.255.0 {

option routers 192.168.10.1;

option subnet-mask 255.255.254.0;

option domain-name-servers 192.168.10.10, 192.168.10.9;

option domain-name "toecheese.com";

option cisco-lwapp.lwapp-controllers 192.168.11.26, 192.168.11.27, 192.168.11.22, 192.168.11.23;

default-lease-time 432000;

option log-servers 172.20.1.203;

max-lease-time 442000;

# range dynamic-bootp 192.168.10.30 172.20.3.254;

pool {