Network Management

last person joined: yesterday 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Back to discussions
Expand all | Collapse all

After upgrading IAP's, Error config version - how to fix

This thread has been viewed 3 times

  • 1.  After upgrading IAP's, Error config version - how to fix

    Posted Oct 16, 2017 04:00 PM
      |   view attached

    After the news for KRACK Attack, we upgraded all devices for customers trhough our Airwave..

     

    Unfortunately all groups are mismatched.. it says:

    ' Error--- config version[6.5.4.0-6.5.4] not found in command model list '

     

    We run Airwave version 8.2.4.1

     

    How can we fix the Mismatches?



  • 2.  RE: After upgrading IAP's, Error config version - how to fix

    Posted Oct 16, 2017 09:20 PM
    Are you instant GUI in airwave?

    Get Outlook for iOS


  • 3.  RE: After upgrading IAP's, Error config version - how to fix

    Posted Oct 17, 2017 04:49 AM
      |   view attached

    Yes we manage instant VC complete from Airwave - and Instant GUI is enabled for all groups - see screenshot



  • 4.  RE: After upgrading IAP's, Error config version - how to fix

    Posted Oct 18, 2017 02:34 PM

    have you heard anything on this? I am having the exact same issue and using the exact same codes on Airwave and IAP. 



  • 5.  RE: After upgrading IAP's, Error config version - how to fix

    Posted Oct 19, 2017 02:47 AM

    Nope unfortunately no feedback or help back yet from the community..

     

    I am trying to upgrade AMP from 8.2.4.1 to 8.2.5 (maybe a solution) but upgrade is in progress so not sure this will solve the problem



  • 6.  RE: After upgrading IAP's, Error config version - how to fix
    Best Answer

    Posted Oct 20, 2017 06:11 AM

    I upgraded Airwave to 8.2.5 and now all mismatches are fixed.. good news.



  • 7.  RE: After upgrading IAP's, Error config version - how to fix

    EMPLOYEE
    Posted Oct 20, 2017 10:28 AM

    IAP 6.5.4.0 firmware support was added in 8.2.5 release.  This explains the error since the config template didn't exist in 8.2.4.1.