WLC 9800 Process iosd Eror

[RoeyF]

hello,

i'm running wlc9800-40 17.6.4 version and i'v got this error

Severity	Process Name	Message
Critical	iosd	Apr 10 23:47:04.326: %IOSXE_QFP-2-LOAD_RECOVER: Slot: 0, QFP:0, Load 45% recovered. 5 secs traffic rate on QFP: Total Input: 13034 pps (13.0 kpps), 27199160 bps (27.2 mbps), Total Output: 3040723 pps (3040.7 kpps), 5885627216 bps (5885.6 mbps).
Critical	iosd	Apr 10 23:46:54.326: %IOSXE_QFP-2-LOAD_EXCEED: Slot: 0, QFP:0, Load 86% exceeds the setting threshold 80%. 5 secs traffic rate on QFP: Total Input: 25640 pps (25.6 kpps), 65863984 bps (65.9 mbps), Total Output: 4369691 pps (4369.7 kpps), 8469788640 bps (8469.8 mbps).
Critical	iosd	Apr  9 23:47:13.298: %IOSXE_QFP-2-LOAD_RECOVER: Slot: 0, QFP:0, Load 13% recovered. 5 secs traffic rate on QFP: Total Input: 7612 pps (7.6 kpps), 39925576 bps (39.9 mbps), Total Output: 684281 pps (684.3 kpps), 1350940856 bps (1350.9 mbps).

and many more columns

[marce1000]

 - The output from those commands requested are the most imported ones ; the values reported are normal , for the current controller state. If those QFP messages would appear again. Then also run the commands again.

        Reminder and important :  - Have a checkup of the 9800 WLC configuration with the CLI command show tech wireless and feed the output from that inti : Wireless Config Analyzer

 M.

[marce1000]

 - Added reply : as far as Leo's remarks concerning pubd have a look at : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwb15629
                   Following the bug report advising to upgrade to 17.9.5 if problems persist.

 M.

[Leo Laohoo]

Add this to your list: CSCwi59993, CSCwi62915

[marce1000]

                            - Last one giving me : This bug is not available for viewing at this time.
    Anyways all releases included new ones will have (new) bugs (an inherit property of the enormous complexity of the it-age we live in ; which is often underestimated) , useful for customer to know these too then  (indeed) ; customer has a potential show stopping problem with 17.6.x which is getting older too  and should proceed to 17.9.5 (in my humble opinion)

 M.

[Leo Laohoo]

---

@marce1000 wrote:
which is getting older

---

That's not an excuse to upgrade the firmware. 

All I want is a stable firmware to use.  If I crash a switch, that is going to affect only 48 ports, however, a WLC with a buggy firmware will affect tens of thousands of fully p*ssed off wireless clients.  

If the WLC is stable at 17.6.6 then stay there.  Jumping from one buggy firmware version to another buggy firmware version is a very exhausting process.  

[marce1000]

                         >...If the WLC is stable at 17.6.6 then stay there. 
  - Leo because of the customer's pubd problem , for that customer , 17.6.6 is currently not stable enough , for another it very well may be....(as I said , it's not as simple as that).I will; abort here ; to not overwhelm customer with 'spam'...  One final example on 'then stay here' : Yesterday I gave the example to someone that 17.13.x now has extra provisioning and checks to prevent AP Image download corruption over WAN links and other.  Well tomorrow someone comes along which gets bitten by that a lot and goes for 17.13.x to remediate that (aborting 'then stay here') to remediate a specific issue (as for this customer).  To let have customer his breakfast (LOL!) further discussions may be done in a private context.

 M.

[Leo Laohoo]

---

@marce1000 wrote:
Leo because of the customer's pubd problem , for that customer , 17.6.6 is currently not stable enough , for another it very well may be

---

This is subject to debate but, personally, no.  If "pubd" is the only cause of the issue, then there is an easy fix.  However, as a "whole", 17.6.6 is not as terrible as APs randomly dropping packets.  

[marce1000]

              >...then there is an easy fix. 
 - There is only an easy fix if you explain the fix Leo (smile!)

 M.

[Leo Laohoo]

---

@marce1000 wrote:
There is only an easy fix if you explain the fix

---

Memory leak due to "pubd" is due to DNAC.  

Remove the DNAC hooks is the fix.