12-16-2023 03:44 AM
Hi Everyone
Details : I have found the cpu process is not normally. This device uses very high CPU resources about 65-70%.
---------------------------------- System CPU Process ---------------------------------
Current Time:Sat Dec 16 18:13:01 2023 - System UP Time:481 days 1 hrs 22 mins 32 secs (Time: 41562645 Secs)
ReaperTick: 4139737 ReaperWatcherTick: 1385246 ReaperTrigger:0 ReaperState:1 reaperExitTick:4139737
Last Reaper Tick :2023-12-16 11:12:52.987482 Last Reaper Watcher Tick :2023-12-16 11:13:00.715490
Name PID Priority CPU Use (usr/sys)% hwm CPU Reaper
<SNIP>
emWeb 5503 ( 71/ 71) 0 ( 0/ 0)% 99 1 T 300
<SNIP>
bcastReceiveTask 5419 ( 71/ 71) 99 ( 6/ 93)% 99 7
<SNIP>
spamApTask6 5259 ( 71/ 71) 98 ( 5/ 93)% 99 5
spamApTask4 5257 ( 71/ 71) 98 ( 5/ 93)% 99 9
spamApTask5 5258 ( 71/ 71) 99 ( 5/ 93)% 99 6
spamApTask7 5260 ( 71/ 71) 98 ( 5/ 93)% 99 8
spamApTask3 5256 ( 71/ 71) 98 ( 7/ 90)% 99 3
spamApTask2 5255 ( 71/ 71) 0 ( 0/ 0)% 80 5
spamApTask1 5254 ( 71/ 71) 99 ( 7/ 91)% 99 1
I have disabled Broadcast Forwarding and mDNS service already but It didn't help anything, the cpu process still is very high. Now, I do not any idea for will fix this issue. Therefore, please give me some advice.
Solved! Go to Solution.
12-17-2023 08:19 AM
1. Upgrade your WLC as per the link Marce supplied. Remember to check the compatibility matrix (link below) to make sure your APs will be supported by 8.10. If not then at least upgrade to 8.5.182.11 (link below).
2. Check your WLC config using the Config Analyzer (link below).
If still not resolved then open a TAC case as Scott suggested.
12-16-2023 08:36 AM
I remember someone saying that this was okay as long as it's not pinned over 95%. I also noticed you are using SSO, so have you tried to fail over and see what the other controller is showing and then fail it back?
12-16-2023 08:42 AM
I also just looked at a few of ours and it's not very high at all but we are on a different code version. Why not just open a TAC case and see what they have to say.
12-16-2023 08:57 AM
- Checkout https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html
Use latest advisory , https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.190.0
check if that can help ,
M.
12-17-2023 08:19 AM
1. Upgrade your WLC as per the link Marce supplied. Remember to check the compatibility matrix (link below) to make sure your APs will be supported by 8.10. If not then at least upgrade to 8.5.182.11 (link below).
2. Check your WLC config using the Config Analyzer (link below).
If still not resolved then open a TAC case as Scott suggested.
12-18-2023 08:46 AM
Hi All,
Thanks you for your reply.
I can't open TAC because this device is end of support HW already. Therefore, I am informing to end customer to upgrade first and monitor continues.
Best Regard,
Many Thanks.
12-18-2023 09:01 AM
5520 is not end of support yet:
https://www.cisco.com/c/en/us/products/collateral/wireless/5520-wireless-controller/eos-eol-notice-c51-744430.html
12-18-2023 09:29 AM
My customer uses 5508 Model. I might written the wrong topic.
I apologize for misunderstanding.
12-18-2023 02:19 PM
Then they should upgrade to 8.5.182.11 (link below) and check the WLC config with Config Analyzer.
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