11-07-2024 11:01 AM
Man, there has to be another solution other than upgrading to iOS 17.12.3 .. We can't use that IOS because we still have 900 2702's on our controllers. We have 1500 9130's and 2800 3802's.
I really wish Cisco would escalate this issue and get a patch put out. We are screwed if our 9130's continue to drop and no longer permit client connections. Wish we knew this was a problem before we migrated 4 months ago off of our old 8540's. Not to mention, these 9800 WLC's have crashed 4 times in 4 months and the 8540's would go years without crashing. Not happy with Cisco right now
11-07-2024 11:05 AM
- The older IOS COS AP's are supported in and up to 17.12.x verify using :
https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
M.
11-07-2024 11:44 AM
Interesting. The Cisco tech from the TAC case gave me a screen shot of 17.12.3 showing supported AP's, and the 2702 is not listed. He also told me that the 2702 wasn't supported. And the link that you provided takes me to a place that shows the 2702 is supported. So the question is, what document is correct
Does anyone out there have 2702's running on the 9800-80 WLC running Dublin 17.12.3(ED) or 17.12.4(MD) ?
Thx Marc1000 for your document reference. You gave me hope, something I didn't have when I posted my original post..
11-07-2024 12:01 PM
>...So the question is, what document is correct
- Well I can tell you from 'first hand' what is correct : I have a mini lab setup with a 9800-cl running in vmware workstation on windows 10 , version installed = 17.12.4 and a 2700 'aside it' in the living. It can connect to it perfectly. Use the setup also for community support and when I need to check things out sometimes
1) It is supported
2) The compatibility matrix is correct
M.
11-08-2024 05:19 AM
Excellent. Thank you for your input on this. You have been most helpful.
11-10-2024 10:16 AM - edited 03-03-2025 01:56 PM
You can also refer to the release notes. The Wave 1 APs are definitely supported on 17.12
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps
These days you'll often find you know more than the TAC engineer you're dealing with. You have to double check and verify anything they tell you. I can't count the number of times they've told me to run commands that don't even exist, or just don't work, because they've got them from a document for some other platform or version (never actually tried the commands themselves).
11-07-2024 12:31 PM
I can also confirm that the 2700, 3700, and 1570 series APs are working on 17.12.4 on 9800-80s.
11-08-2024 05:20 AM
Wonderful. Good to hear. Thank you for the confirmation.
11-07-2024 04:52 PM - edited 11-07-2024 04:54 PM
The Bug ID might say "but is not seen in 17.12.3 or above" but you may want to make it a point to reboot the APs regularly (daily or weekly) because there are about a dozen Bug IDs where the x800/1560 and all Catalyst 9k APs would stop passing traffic.
The "workaround" is to reboot the APs very regularly.
energywise domain [HAKUNA MATATA] security shared-secret [PASSWORD]
energywise importance 60
! Interface
interface range
energywise level 10 recurrence importance 70 time-range POWER_ON
energywise level 0 recurrence importance 70 time-range TURN_OFF
energywise importance 60
! Time Range Power ON
time-range POWER_ON
absolute start 00:00 01 January 2024
periodic weekdays 8:00 to 20:00
! Time Range Power OFF
time-range TURN_OFF
absolute start 00:00 01 January 2024
periodic weekdays 20:00 to 23:59
periodic weekdays 0:00 to 8:00
11-08-2024 05:21 AM
Wow. Good to know. An thank you for the config snippets.
11-10-2024 10:22 AM
The latest version of this bug which we're dealing with on 17.12.4 is https://bst.cisco.com/bugsearch/bug/CSCwk12169
It's supposed to be fixed in 17.12.4 APSP4 which was released a few days ago.
We're rolling it out this coming week and hoping it will resolve the issue...
11-14-2024 01:14 AM - edited 11-29-2024 03:57 AM
And I can now confirm that CSCwk12169 does not fix the issue for 9105 APs! TAC getting back to developers ...
Update 27-11-2024: dev who wrote CSCwk12169 fix now making noises about maybe it doesn't fix the issue on 9105 on 17.12.4 APSP4 after all ... Meanwhile TAC have opened a new bug https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwn27877 which has a different dev assigned and we've got off to a great start (not) with them misunderstanding the RA traces (claiming it's working fine and it's the clients which are at fault) and not believing the OTA captures which prove the AP doesn't respond! So we have a dev who doesn't really understand AP/9800/wireless and doesn't believe OTA - what could possibly go wrong? Maybe they were having a bad day and will see sense in the fresh light of a new day...
Update: 29-11-2024: debug session with dev team completed after they saw sense and realised there is definitely something wrong with the AP. They could see that the 5GHz radio Rx queue gets stuck (but no idea why). They've collected lots of debugs and will be talking to Broadcom next week ...
11-14-2024 05:51 AM
Rich, Couple questions.
1.) in regards to upgrading from 17.9.5 on our 9800-80 WLC's to 17.12.x, which should we upgrade to? The Early Deployment is starred and the newer 17.12.4 is the main deployment..
17.12.3(ED)* or 17.12.4(MD)
2. In regards to CSCwk48338, has Cisco found anything yet are they still looking?
Thank you
Brannon
11-14-2024 06:24 AM
brannonsweet@cox.net Consider 17.12.4 as being mature enough and to be preferred over 17.12.3 ,
M.
11-22-2024 08:47 AM
Rich, wondering if you might have a opinion on this. We are updating our 9800'-80's from 17.9.5 to 17.12.4 this weekend. I was looking over the SMU's and had a question about one of them:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide