Wireless Access

 View Only
last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

This thread has been viewed 24 times

  • 1.  AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 09, 2019 09:03 AM

    Hello!

     

    I have migrated a master controller from 6.5.4.6 to 8.4.0.5 with the AOS 8.4.x migration tool in MCM mode.
    After the migration the controller came up and the AP's pulled the new firmware and the config.

     

    But the GUI is not fully working.
    In the monitor dashbord is literally nothing to see.
    The first hurdle was, that the licensing feature bits are not visible.
    So - RF Protect and PEF NG must be enabled via CLI.

     

    Apart from that, everything is working fine (AAA, SSID's, etc...).

     

    Now, this topic say's that the controller need to be reconfigured from factory defaults (recomendation from TAC) to recover the GUI functionality.
    Does anybody faced this issue before? Is it enough, to reset the controller to factory defaults and to reimport the config?
    Or is it neccessary to create the configuration from scratch?

     

    Thank you!

     



  • 2.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 09, 2019 09:21 AM

    Hi

     

    Please try with different browsers, if possible from different systems.

     

    If it still not working, could be a cosmetic issue in the 8.4.0.5.

    I understand it is a headache, I would suggest you to raise a ticket with TAC.

     

    They will ask you to collect the Browser Console logs to analyze.

     

    -Jeeva Selvakumar



  • 3.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 09, 2019 09:38 AM

    Hello!

     

    It is no cosmetic error.
    And it is a standard process to try multiple browsers, from multiple machines under use of multiple versions.

    No, it is definitly no browser issue.

     

    I linked a topic which describe the output from TAC, the migration from 6.5.x to 8.4.x with the migration tool breaks the functionality of GUI.

     

    So my question is: Do I have to build the configuration from scratch or does anybody tested what will happen if I reimport the migrated configuration in a factory defaulted 8.4.0.5 controller.

    My question adresses users who have experience with the AOS migration tool.

     

    Thank you!

     



  • 4.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 09, 2019 11:33 AM

    Hi Matthias,

     

    I knew it is not a browser or system issue, but I needed to confirm that we had tried it already.

     

    I gone through the link, please note it is not a recommendation from the TAC, maybe for the time being they might have re-configured the controller. But No Worries ;) we can still fix the issue if we are lucky with another method.

     

    There were issue sometimes while migrating from 6.x to 8.4 using 8.4 migration tool and there was a particular case where the internal captive portal wasn't working in the ArubaOS 8.4.x code, the page wasn't loading for the guest users.

     

    Since both are HTTP module related issue in the Aruba OS, please try the below steps:

    - show switchinfo --> Check if there is any crash info

    If crash available follow the next step, if not skip the "tar"ring step below,

    -tar crash --> tar the crash file and transfer to the tftp server

    - show process monitor statistics | include http --> check if the http module has crashed/rebooted (kindy, confirm the http process module name from the output, it's been months, so I am not sure!!)

    - process restart "httpd" --> this should fix the issue in most cases

     

    If not, please follow the other Link you have shared! .

    But before starting that paining process, have a check with TAC, since it's been four months that post had been made, they might have came up with a way around to fix the issue or they will help you to resolve the issue and fix/document it for the future.

     

    Best of Luck!!

     

    - Jeeva Selvakumar



  • 5.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 10, 2019 03:38 AM

    Hi!

    Thank you for that input.
    I will check that, and give you an update.

     



  • 6.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Dec 16, 2019 03:17 AM

    Hi!

     

    Sorry for the delay, I was not able to access the device until today.

     

    show switchinfo:
    Configuration unchanged since last save
    No AP crash information available.
    No controller crash information available.

     

    show process monitor statistics | include http:

    Returns no chrashinfo.

     

    After process restart "httpd", GUI is not fixed.

     

    I think the only way to resolve this issue, will be a reset of the controller.
    But to come back to my initial question, does anybody know if it's enough to reimport the config after a factory reset?

     

    Thank you!

     

     

     

     



  • 7.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted Jun 04, 2020 03:54 PM

    Hello!

     

    I want to give a short update to this subject, maybe this will help someone with the same problem.

     

    We decided for an update to 8.6.0.4 code.
    I thought there is a little chance to fix the GUI if we go on to the next version.

    But with the update to 8.6.0.4 from 8.4 which was migrated from 6.5 with the migration tool, we broke the database.

     

    The controller came back up again, but the accesspoints does not.
    The logs where full of postgres errors at migration state during the update.

     

    We had to boot up with the 8.4 code again.

     

    As next step, we will set the controller to factory defaults and update it to 8.6.0.4.
    Because I'm curious, we will try to import the 8.4.x config to 8.6.0.4...

     



  • 8.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x
    Best Answer

    Posted May 11, 2021 07:53 AM

    Hello!

    I finaly found the couse of the broken GUI after a Master/Standby upgrade with the migration tool.

    If you migrate from 6.5.x to 8.4.x with the migration tool V 3.3.2 (AOS 8.4.x), the migrated controller will end up in a master deployment mode, even if you choose the "Standalone" deployment mode at the deployment mode step in the migration wizzard.

    To migrate the controller, use the migration tool version 3.2.3 (AOS 8.3.x) instead.

    Under use of MigrationTool_V3.2.3 and upgrading to AOS 8.3.x, the controller will be migrated to standalone mode and the GUI will work as expected.

    You can upgrade the controller afterwards directly to your targed version, for example 8.7.x.

    I used this migration path to upgrade a customers 7210 AOS 6.5.16 master/standby deployment:

    • MigrationTool_V3.2.3.ova
    • move master role to backup controller
    • deactivate VRRP on master controller
    • migrate master controller to 8.3.0.16
    • enable VRRP, move VRRP VIP back to master controller
    • migrate backup controller to 8.3.0.16
    • ensure correct master redundancy function (db sync)
    • update backup controller to 8.7.1.3
    • update master controller to 8.7.1.3

    choose the migration and deployment mode
    choose the origin and target version images for migration
    enter the credentials and start the migration




    ------------------------------
    Best regards, mom
    ------------------------------

    Original Message


  • 9.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    MVP EXPERT
    Posted May 12, 2021 02:42 AM
    Note that ArubaOS 8.6.0.9 is the new conservative (most stable) release since last week.

    ------------------------------
    Marcel Koedijk | MVP Guru 2021 | ACMP | ACCP | ACDA | Ekahau ECSE | Not an HPE Employee | Opionions are my own
    ------------------------------

    Original Message


  • 10.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted May 12, 2021 02:55 AM

    Hi!

    So, you mean we should prefere 8.6.0.9 to 8.7.1.3? 



    ------------------------------
    Best regards, mom
    ------------------------------

    Original Message


  • 11.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    MVP EXPERT
    Posted May 12, 2021 03:03 AM
    Hi Mom,

    Yes thats correct. 

    • The conservative releases are longer tested en more stable and recommended for production environments.
    • The standard releases i will only use when there is need for it, example for new feature or hardware (ap) support.
    https://www.arubanetworks.com/support-services/end-of-life/arubaos-software-release/

    ------------------------------
    Marcel Koedijk | MVP Guru 2021 | ACMP | ACCP | ACDA | Ekahau ECSE | Not an HPE Employee | Opionions are my own
    ------------------------------

    Original Message


  • 12.  RE: AOS 8.4.x GUI not fully functional after MCM migration from 6.5.x

    Posted May 12, 2021 03:18 AM

    Hi!

    Ok, that's clear.

    Since I have big deployments with 56x and 57x, I have to use 8.7.x...


    One more thing to mention, the CR/SR list is linked to support.arubanetworks.com.

    Even with my partner account, I have no access to this source any more.

    Can you trigger a update of this?



    ------------------------------
    Best regards, mom
    ------------------------------

    Original Message