C9800 compatibility with Aironet 1560 seires

[DhanushS]

Is it possible to connect Aironet AP 1560 series to C9800 WLAN controller for centralized management.

[Karsten Iwen · Accepted solution]

Yes: https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#c9800-ctr-ap_support

[DhanushS]

Thank you for the reply. But for this AIR-AP1562D-x-K9 Outdoor model the supported version is Cisco IOS XE Gibraltar 16.10.1. In this case i also have one C9124AXI AP. can i able to manage both in c9800 controller

[Karsten Iwen]

That was the first release to support the 1560. If you are still running that release, you can't use the 9124 on the same controller. You need to upgrade to a newer version to operate both models on the same controller.

[DhanushS]

Thank you Sir, Does Catalyst 9800 controller requires IOS-XE 17.x or later for CAPWAP communication.

[Karsten Iwen]

All controllers use CAPWAP to communicate with the controller. There is no dependency on the version. The only dependency is that not all versions support all APs. For your use case, the minimum suggested version is 17.9.6. If you are running any version below, I would look if and how you can upgrade to that version as both mentioned APs are supported on that release.

[Leo Laohoo]

Only the 9800-M/H1/H2 require a minimum of 17.15.2.

[marce1000]

- @Leo Laohoo   I can't see the connection with the subject of the post Leo ; also these controllers are 
                           supported  already from 17.14.1  
                           E.g. : https://software.cisco.com/download/home/286330374/type/282046477/release/IOSXE-17.14.1

  M.

[Rich R]

Hi @DhanushS 
The 2 documents you should be referring to are the Compatibility Matrix (link below) and the TAC Recommended code versions (link below).

The Compatibility Matrix shows you the minimum required code version, and if the AP is end of support also the last code version, to support the AP.
The TAC recommended code tells you what version you should aim to be running to keep up to date with current features, fixes and supportability.

A good starting point for you would be 17.12.4 with all available SMUs and APSPs installed.  That supports the 1562D and the 9124AXI.  You should always refer to the release notes for the planned release which also lists the supported APs:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps

[Karsten Iwen]

OMG ... For the first time I have to disagree with @Rich R, which typically would mean that I am wrong ...

I would not recommend updating to 17.12.x when only limited experience with the controller is given. IMO, the likelihood that something is going wrong is less likely if you go to 17.9.6, which is also a recommended version.

[Rich R]

Ha ha, yes they are both recommended releases, but 17.9 is already End of Software Maintenance now (since 30 March 2025), meaning no more bug fixes, which is my main reason for preferring 17.12.  We moved from 17.9 to 17.12 for a number of fixes which Cisco had already decided not to fix in 17.9 some time ago.  Any new bugs found in 17.9 TAC will automatically recommend upgrade.  Yes, 17.12 is not perfect (no release is), but it is now very widely used and fairly stable for most people, so it's a matter of choice to consider.  Now that 17.9 is end of software maintenance TAC are likely to update the recommendation to 17.12 and 17.15 in the next few months - probably if/when 17.15.3 is released and has been stable for a month or two.

PS: Note that with 17.9.6 you'll need APSP3 installed too.
Note that 17.9.7 (probably the last bug fix release for 17.9) was released recently so TAC are likely to update from 17.9.6 to 17.9.7 in due course before moving away from 17.9 completely later in the year.

[Karsten Iwen]

Oh, I missed this milestone. Yes, with that, 17.9 is really no target release for upgrades any more. Perhaps I would upgrade directly to 17.12.5 in that case.

[Leo Laohoo]

Two (out of six) of our 9800-80 have now encountered CSCwm80596.  The other three controllers will also encounter this bug soon. 

All our six 9800-80 have the following in common: 

1.  17.12.4 APSP4
2.  <3000 APs per controller
3.  <10k daily wireless client
4.  Uptime:  <4 months
5.  DNAC

We found out about this bug after one controller started spatting out TMPFS exceeding 41%.  A few weeks later, the 2nd WLC is doing the same thing.  I have checked the other controllers and they will soon be hitting this bug. 

Now that I've mentioned the good news, here is the bad news:  I challenge anyone (including DNAC) to proactively monitor TMPFS going above 50% because DNAC will not flag this and other NMS do not monitor the TMPFS OID properly. 

We caught this with our syslog "catcher".  

Use the following command to check: 

sh platform software mount | include tmpfs.*tmp

All TMPFS should be <11%.  Any TMPFS >12% means trouble.  When TMPFS reaches 100%, the controller, switch or router will crash.  

There are several ways to fix this: 

1.  TAC loves to tell people to reboot the controller

2.  And TAC also likes to recommend people to upgrade the firmware

3.  But TAC hates it when they go into shell and "poke" (or delete) the files associated to the ballooning TMPFS.  

Anyone who encounter this bug may want to consider option #3 because it is non-disruptive.  Meaning, option #3 does not reboot the controller.  

NOTE:  

1.  CSCwm80596 talks about two processes:  pubd & wncd

2.  WNCD is "wireless network controller daemon", aka "load-balancer".  Read all about what the WNCD does here:  Cisco Catalyst 9800 Series Configuration Best Practices

3.  PubD is "publication daemon" it is part-and-parcel to DNAC.  Cisco Bug ID authors substitute "DNAC" with "pubd" as not to insult clients.  "telemetry" is another euphemism for DNAC.  

[Rich R]

Note that CSCwm80596 affects both 17.9 and 17.12 so the problem applies equally to both recommended releases 17.12.4 and 17.9.6.
According to bug tool it's fixed in 17.9.7 and 17.12.5 (and 17.15.2)

[DhanushS]

Is there any software License needs for aironet Ap to join controller