DHCP service on an elected AP7622 Virtual Controller

[theciscokid99]

We are currently working with a customer that has an AP7522 network with a virtual controller (on an access point). The VC is running a DHCP server for the WLAN clients. We decided to enable the "Elected" Virtual Controller for high availability. After we moved to the "elected" VC and configured an additional static IP address, we cannot get the VC to hand out DHCP addresses. The DHCP server is configured and enable at the AP profile. I've been able to recreate this same issue on my access points.

My customer is on 5.9.2.5
My system is on version 5.9.3.1

Relevant configuration below

dhcp-server-policy Blackhole
dhcp-pool POOL1
network 10.10.10.0/24
dhcp-server activation-criteria rf-domain-manager
!
profile ap7522 default-ap7522
use enterprise-ui
no autoinstall configuration
no autoinstall firmware
load-balancing balance-band-loads
crypto ikev1 policy ikev1-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ikev2 policy ikev2-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
crypto ikev1 remote-vpn
crypto ikev2 remote-vpn
crypto auto-ipsec-secure
crypto load-management
crypto remote-vpn-client
interface radio1
wlan bss 1 primary
wlan " bss 2 primary
interface radio2
wlan ConnorCompany bss 1 primary
interface ge1
interface vlan1
ip address dhcp
ip address zeroconf secondary
ip dhcp client request options all
interface pppoe1
use event-system-policy default
use dhcp-server-policy Blackhole
use firewall-policy default
use client-identity-group default
virtual-controller auto
virtual-controller management-interface ip address 192.168.100.16/23
rf-domain-manager capable
logging on
ip nat inside source list BROADCAST-MULTICAST-CONTROL precedence 1 interface vlan1 overload
service pm sys-restart
router ospf
adoption-mode controller
!
rf-domain default
timezone CST6CDT
country-code us
use smart-rf-policy default
!
ap7522 84-24-8D-17-78-B4
use profile default-ap7522
use rf-domain default
hostname ap7522-1778B4
interface vlan1
ip address 192.168.101.15/23
no use dhcp-server-policy
rf-domain-manager capable
no adoption-mode

[zlinuxboy]

Because the VC will migrated between APs, So every AP should config a static SVI ip manually or  device override, is that right?

Any possible to config multiple SVI static IP on profile and migrate them accompany with the VC role migration?

For example, when AP-A was VC and act as dhcp server, have been lease some IPs to clients, when AP-A down, and AP-B was elected as the new VC, any possible to migrate the AP-A’s SVI IP and dhcp lease db to AP-B automatically?

[theciscokid99]

Static IP's on the SVI's did solve the problem. I had another error on my DHCP config that was causing an issue.

[theciscokid99]

I did have a static IP on the SVI of the original VC but not the other AP's. I added static IP's to the other AP's and still no change. Wireless client associate and come up with a 169.x.x.x address. If I connect the AP's to a network with DHCP available, the wireless clients will associate pull IP's from that DHCP server.

[Daren_E · Accepted solution]

DHCP service will not work without assigning a static IP address to SVI of the desired AP.
Example:
interface VLAN 10
ip address 10.10.10.1/24