Cisco 5508 WLC v.8.5.161.0 doesn´t work via GUI but does work via SSH

[SerFer9]

Cisco 5508 WLC v.8.5.161.0 doesn´t work via GUI but does work via SSH. It used to work and then it stopped working. The web mode option is enabled. Any help or a similar case?

[MHM Cisco World]

Clarity what!!?? 

Http use ssl cipher to connect if there is mismatch then http (gui) is failed

MHM

[marce1000]

 @MHM Cisco World That is true , but in that case you get already other errors then a simple 'no connection possible'

 M.

[marce1000]

  - Could there be any intranet firewalling or local firewalling on your device preventing this (full) access ?
    + Could you also check the controller's logs after trying , is there anything related reported ?

 M.

[SerFer9]

no, there is no firewall blocking anything.

[marce1000]

                >....no, there is no firewall blocking anything.
  -  And do you see anything in the controller's logs when trying to access the GUI ?

 M.

[SerFer9]

Jun 23 11:58:31.545: [WARNING] ewmain.c 5364: EmWeb: Handle table overflow @5364
*apfMsConnTask_3: Jun 23 11:58:31.358: %APF-4-INVALID_ACTION_CATEGORY: [PA]apf_wme_utils.c:6743 Could not process 802.11 Action. Received Action frame with invalid category field(not supported by controller) from client. Mobile:8C:F8:C5:96:A6:EF, Category

--More or (q)uit current module or <ctrl-z> to abort
*osapiBsnTimer: Jun 23 11:58:30.824: %RMGR-3-RED_SWITCH_CASE_NOT_HANDLED: [PA]rmgr_main.c:813 rmgrMsgRetryTmoHandler: The switch case 0x1 not handled
Previous message occurred 3 times.

Is the last message

[marce1000]

         >...APF-4-INVALID_ACTION_CATEGORY
  - This one seems to be a bug : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCto64291
     but it's not related to GUI access.

         >...RMGR-3-RED_SWITCH_CASE_NOT_HANDLED
       - You can look that one up in https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-0MR1/message/guide/SysMsgGuide_7-0MR1/rfid_rrm_sim_7-0MR1_msgs21.html
          but it seems to be a debug  message and also not related

   - Since you say that GUI (access)  used to work , could it be possible to reboot the controller at some time
                      and check if that makes a difference ?

 M,

[SerFer9]

that's the problem, it can't be rebooted because it's in production with almost 300 ap's.

[marce1000]

     >...that's the problem, it can't be rebooted because it's in production with almost 300 ap's.
  - It then depends on how urgent GUI access is currently because many things can also be done
    with config statements in the CLI

 M.

[marce1000]

            >...that's the problem, it can't be rebooted because it's in production with almost 300 ap's.
  - Another possibility I have been thinking about is to try to restart the web services on the controller with
    the following commands (sequence) :
                                 config network secureweb disable
                                     config network webmode  disable
                                     config network webmode   enable
                                     config network secureweb enable

          Hoping that this would restart the webservices on the controller completely (e.g.)
           In that context if there is no response for https , you may also try simple http access

 M
                                 

[SerFer9]

Hi @marce1000 

It was the first thing to be tested.

Best regards

[simolor78]

Any news about this problem ? I am in the same situation

[jagan.chowdam]

Is there a CPU ACL configured to protect access to the WLC? Also, are you logging in with a local admin account?

Jagan Chowdam