About the command of 'config ap primary-base xxx xxx xxx'

[Lucas Woo]

Hello,

As the title suggests, I changed the setting of Primary Controller of 'AIR-CAP3702I-Q-K9' on WLC (C9800), but result of show command didn`t seem to be changed.

Commands and results are as below.

--------
【AIR-CAP3702I-Q-K9】

# config ap primary-base [name of WLC] [name of AP] 172.20.130.251

# show capwap ip config
Primary Controller 172.20.130.250
------------

Also, after rebooting AP, AP tried to join in old WLC(172.20.130.250).

Which commands are prioritized 'config ap primary-base xxx xxx xxx' or 'capwap ap primary-base xxx xxx xxx'

Thank you.

[marce1000]

     >....Which commands are prioritized 'config ap primary-base xxx xxx xxx' or 'capwap ap primary-base xxx xxx xxx'
  - The latter commands are probably unrelated to what you want to do because they are applicable only when an ap has already joined a controller (prioritizing controllers). You need to make the AP discover the intended controller such as DHCP option 43 (e.g.)

 M.

[Leo Laohoo]

If the command is entered on the WLC, the command is "config ap primary-base <WLC_NAME > <AP_NAME> <WLC_IP_ADDRESS>". 

If the command is entered on the AP, the command is "capwap ap primary-base <WLC_NAME > <WLC_IP_ADDRESS>".

[Scott Fella]

If you are trying to move an ap from AireOS to a 9800, if the ap is joined to the 5508, you just need to change the high availability from the GUI.CLI of the 5508.  The ap will then attempt to join the 9800.  If it fails, then you need to look at other things.  Is the code on the 9800 support the ap you want to join?  Look at the output from the console to see what error(s) you see.  If you don't have any ap's joined to the 9800, you might have a configuration issue in which you might of configured something wrong or you are missing something.

You didn't provide what controller the ap is joined to, what code version on the AireOS and the 9800, is the controllers on the same subnet and are you also using option 43, DNS or are the ap's in the same L2 subnet.

[Rich R]

As already highlighted you seem to be mixing WLC and AP CLI commands!
Having set the AP config you can view the result by: show ap config general <apname>
Get a console on the AP and watch the logs from power-on.  You'll see exactly what the AP is using to decide which WLC to join and they always remember WLCs they've joined before (and try them) even if they're not configured in the pri/sec/tertiary HA.

Presume you've checked the AP flash as per https://www.cisco.com/c/en/us/support/docs/field-notices/703/fn70330.html and https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/213317-understanding-various-ap-ios-flash-corru.html ?