CSCwj93906 - 9120|| Sending Msg:2 in mode:2 to hostapd failed

[hhitalani]

Hi there,

i have the same problem.

Installation 9800CL 17.9.4a and 17.6.4 , APs 9120.

there is no software version or APSP available to download from Cisco.

what should i do?

Thanks

[marce1000]

 -          17.12.4    is being mentioned as a fixed release

 M.

[hhitalani]

Hi Marce 1000,

Thanks for your reply.

Actually I dont want to upgrade the software version completely, its too difficult at the moment.

I just want to have a fixed APSP in version 17.9.4a and 17.6.4, which was already mentioned in the bug fix.

But the APSPs are not available for download.

[marce1000]

  - I myself can't find any APSP(s) mentioned in the bug report , the right column (Known Fixed Releases) are 'effective complete IOS-XE releases'.   Please correct me if I am wrong and or provide screenshot (e.g.)

 M.

[hhitalani]

I may be wrong.

What the support means with AP-17.9.6.28 and AP-17.6.8.2. I thought it is an ASPS's in the release.

As I understand from you, it is a software release, but it is also not available for download.

Thanks

[marce1000 · Accepted solution]

  - I can't find it anywhere either (correction) , personally I consider the global upgrade to 17.12.4 better , it is also simpler then working with APSP's  , however check https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
                                                       for AP compatibility with a new or target release when upgrading

  M.

[Leo Laohoo]

Regularly reboot the AP is the best Workaround because there is no guarantee upgrading will fix anything (or introduce more bugs).

[hhitalani]

Hi Leo,

thanks for your replay.

that is the main reason, why i dont want to upgrade.

the Problem is the APs restart resolve the problem for just to week. I support 160 Branch

Thanks

[marce1000]

              >...that is the main reason, why i dont want to upgrade.
    Read my remarks on the 'age of inevitable bugs' it can not be considered a showstopper when a specific
                      fix is announced for a  a specific problem  , 

 M.

[marce1000]

   @Leo Laohoo   - I beg to differ , for this problem 17.12.4 was mentioned as fixed ; it was a specific topic for the customer
                              As far as bugs  : in the enormous complexity of the modern IT age ,there will always be bugs
                                        a moderate path is to go for fixes when confronting with a specific problem, and it being mentioned
                                       as fixed in a subsequent release
  =>  Not everybody stumbles on the same bug(s)

 M.

[Leo Laohoo]

Hi @marce1000, 

In my humble opinion, I can think of more terrible bugs that have been re-introduced in 17.12.4 like, for example, CSCvx56223.  

Currently, the only problem @hhitalani can easily be fixed by regularly (daily or weekly) reboot of the APs.  Easy enough fix with an EEM.  CSCvx56223, for example, has a workaround of bouncing the 2.4 Ghz/5.0 Ghz.  And that is worse than bouncing the APs.  

[marce1000 · Accepted solution]

  @hhitalani : You may further deliberate  the two viewpoints (Leo's and mine) on dealing with bugs ; but my position is clear ; if there is  an effective fix in a bug report then I don't hesitate ===> Upgrade , 

 M.