Controller don't discovery the APs

[Eng.AD27]

Hello Dear 

i have controller 9800-40 dont discover APs 9176 ? 

anyone here faced same problem  ? 

[Leo Laohoo]

What firmware is the controller on?

Console into the AP and bounce the AP.  Post the entire bootup process.

[Eng.AD27]

C9800 Software (C9800_IOSXE-K9), Version 17.14.1, R 

<Meraki>

Global Use AP ships with Meraki OS as the primary image and with default no
country domain configured. Depending on the DHCP/DNS configurations and Cloud
connectivity AP will either stay in Meraki or Catalyst mode to reach WLCs. To
get more details on the procedure please look at online documentation.

We have currently detected the Access Point is in Day 0 mode. i.e doesn't have
a persona yet. AP will proceed for offline migration shortly. Offline
migration procedure will check if a Catalyst WLC is present in the network and
automatically migrate to Catalyst if a valid one is detected (>= IOS XE 17.15)

Offline migration can take up to 15 minutes to take a decision. To get logs
and details on the current state of offline migration procedure, please type
'offline-migration-info' command after <Meraki> console prompt.

If the intent for the Access Point is to be connected via Meraki mode, resolve
the Cloud connectivity and follow the Dashboard procedure to claim the device
on the network.

[Leo Laohoo]

9176 requires the WLC to be on 17.15.2 minimum.  

The AP is running Meraki OS so it will not join a 9800 with IOS-XE.

[Mark Elsen]

  - @Leo Laohoo   Your remarks about 17.15.2  being needed at least are correct; but note from initial post
                             >... Offline migration procedure will check if a Catalyst WLC is present
                                   in the network and  automatically migrate to Catalyst if a valid one is detected

   I am not exactly sure on this , but I thought these generation of APs could migrate from meraki to Catalyst (CAPWAP) 
  automatically (?)

 M.

[Mark Elsen]

  - @Eng.AD27    Check software version on the controller  , make sure that it is compatible
                           with the use AP model(s) according to : https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

                          + Validate the configuration of your 9800-40 controller with the CLI command
                            show tech wireless and feed  the output from that into Wireless Config Analyzer
                                  (Use the full command outlined , it does not work with show tech-support !)

                         +  Use commands from : https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin
                             for advanced troubleshooting

  M.

[Mark Elsen · Accepted solution]

  - @Eng.AD27      I have noticed that you are running 17.14.1 , these APs need at least 
                             Cisco IOS XE 17.15.2  for starters!

 M.
                           

[Rich R]

As the others have already highlighted you need to be running a WLC software version which supports that model of AP. Refer to the compatibility matrix (link below) and the TAC recommended code versions (link below).

Regarding auto-conversion - that's the day 0 (factory default) behaviour but if suitable WLC is not found and AP is able to reach Meraki cloud then it will boot and continue thereafter in cloud mode.  After that it must either be converted from Meraki cloud dashboard or by resetting to factory default (day 0).

This is all documented in https://www.cisco.com/c/en/us/td/docs/wireless/access_point/technical-reference/global-use-ap-dg.html including new DHCP option 43 configuration which can be used to accelerate day 0 conversion to WLC (CAPWAP) mode.

@Eng.AD27 IOS-XE versions 17.7/8, 17.10/11, 17.13/14, 17.16/17 are short-lived limited support releases which never get any bug fixes or security updates.  They are purely for features which you may need in those releases and should only be used until the next Extended Support release (17.12, 17.15, 17.18 etc) is available so you should not be using 17.14 at all now.
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-14-x-eol.html
Migrate to a recommended 17.15 release - currently 17.15.3 + SMUs + APSP3
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/214749-tac-recommended-ios-xe-builds-for-wirele.html#toc-hId--434755423

[Haydn Andrews]

Heard someone doing same thing and they said

DHCP option 43 needs to be used, and it has to point to the WLC not DNAC
also the APs need to be able to view the sky

They also take like 15min first boot as they will initially try and hit Meraki cloud

[Eng.AD27 · Accepted solution]

Thank you all dears 
i upgraded to17.17.1 and worked normally 

[Rich R]

> i upgraded to17.17.1 
@Eng.AD27 I suspect you did not read my previous reply!
You should not be using 17.17.1 - it's a short-lived limited support release (no bug fixes, no security updates)!
If you want to use latest then go for 17.18.1
If you want minimum recommended release then see TAC Recommended link below - that would currently be 17.15.3 + SMUs + APSP3

[Eng.AD27]

i added new APs and same issue and the WLC assign the ips but the AP didn't receive IPs 

WLC01#sh ip dhcp binding
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type State Interface
Hardware address/
User name
172.18.250.12 0063.6973.636f.2d33. Infinite Automatic Active Vlan190
3861.612e.3039.3065.
2e61.6266.662d.566c.
3139.30
172.18.250.16 38aa.090e.abff Infinite Automatic Active Vlan190
172.18.250.17 cc6e.2a53.4580 Infinite Automatic Active Vlan190

but the APs logs 

| [2025-09-29 07:51:23.495] [offline-migration] migration decision
| [2025-09-29 07:51:23.495] [offline-migration][v4] no WLC IP in DHCP option 43
| [2025-09-29 07:51:23.495] [offline-migration][v4] missing DNS config (server and/or domain)
| [2025-09-29 07:51:23.496] [offline-migration][v6] no WLC IP in DHCP option 52
| [2025-09-29 07:51:23.496] [offline-migration][v6] missing DNS config (server and/or domain)
| [2025-09-29 07:51:28.517] [offline-migration][v4][capwap-l2] 0 WLC(s) detected (unsupported)
| [2025-09-29 07:51:33.538] [offline-migration][v6][capwap-l2] 0 WLC(s) detected (unsupported)

[Mark Elsen]

  - @Eng.AD27                 >...[offline-migration][v4] no WLC IP in DHCP option 43
                                  It looks like the DHCP option 43 and offline/online migration options are not configured
                                 correctly on the DHCP server.

  M.

[Eng.AD27]

ip dhcp-server 172.18.250.200
ip dhcp use subscriber-id client-id
ip dhcp subscriber-id interface-name
ip dhcp pool AA
network 172.18.250.0 255.255.255.0
dns-server 10.10.10.44
default-router 172.18.250.1
option 43 hex f104.ac10.fac8
lease infinite

[Mark Elsen]

  - @Eng.AD27    I am not sure if those options offline/online migration are mandatory for these APs in
                           the DHCP server option settings. Check below example from :
                           https://www.cisco.com/c/en/us/td/docs/wireless/access_point/technical-reference/global-use-ap-dg.html
                           Implement it on your DHCP server , and check if that  makes a difference:
                           (Of course that's  an example , WLC ip address must be changed accoringly)

>...    

Fast Offline Migration

1)     DHCPv4

The option 43 string for DHCPv4 Fast offline migration is as follows:

•        F3 <size> <IP array> Mode=<1|2>, where Mode = 1 -> Meraki and 2 -> Catalyst

where size is Number of WLCs *4 +1 (For one WLC – the size is 05 and two WLCs – the size is 09 and so on)

•        Example String for one WLC.

o    f305ac10011802 (“normal” option 43 “f104ac100118” becomes “f305ac10011802”)

•   Change type from f1 to f3
•   Change length from 04 to 05
•   Add the sub option at the end; 01 for Meraki, 02 for Catalyst
•        IOS/IOS-XE configuration example for WLC discovery using DHCPv4:

ip dhcp pool vlan192

  network 192.168.200.0 255.255.255.0

  default-router 192.168.200.1

  option 43 hex f305.ac10.0118.02

•        Windows server configuration screenshot: