Wireless Access

 View Only

  • 1.  Failed in device due to invalid url format

    Posted yesterday
      |   view attached

    Hi,

    We are experiencing a firmware upgrade on our AP-615 when we add them to our clusters. Our clusters firmware version is 8.13.0.1_93317.

    The new AP 615 firmware version is 8.11.2.0_87947 and it's in a separate cluster but it does not upgrade its firmware.

    The option Manage firmware compliance is on.

    We are using Aruba Central to manage our APs.



  • 2.  RE: Failed in device due to invalid url format

    Posted yesterday

    Please access the AP console / CLI and check the logs using the following commands. 

    show log upgrade
show upgrade
show image > please check of both partitions have a valid image.


    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------



  • 3.  RE: Failed in device due to invalid url format

    Posted 10 hours ago
      |   view attached

    Hi,

    Thanks for your reply.

    Support Aruba says that the firmware version 8.13.0.1_93317 is no longer available in their repository.

    I am wandering if Aruba support can provide the the firmware file to upgrade the AP firmware manually from the AP GUI.

    Please see the attached image.


    Original Message


  • 4.  RE: Failed in device due to invalid url format

    Posted 9 hours ago

    Hello Mario,

    I believe you're using Aruba Central Classic.

    Could you try creating a new group without Firmware Compliance enabled and then move the AP to that group. After that, try upgrading it to the desired firmware version.

    If it works, you can simply move the AP back to its original group.




  • 5.  RE: Failed in device due to invalid url format

    Posted 9 hours ago

    I just checked and can confirm there is no 8.13.0.1 image posted for the AP-615. I don't know the reason for this.

    8.13.1.x is available for the AP-615. 



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 6.  RE: Failed in device due to invalid url format

    Posted 6 hours ago

    @Mario12 Turned out that the software was not correctly published to the support portal and Central. The team has fixed this. You should now be able to download the software and start the update from Central



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------

    Original Message


  • 7.  RE: Failed in device due to invalid url format

    Posted 3 hours ago
      |   view attached

    Hi Willem,

    The new APs are now successfully updating to the cluster firmware version as expected. Thank you very much for your assistance.

    However, while troubleshooting this issue, we upgraded one AP to a newer firmware version than the rest of the cluster.

    Could you please advise on the best way to downgrade this AP so that it can join its original cluster?

    Please see the attached image for reference.

    Thank you for your help.


    Original Message


  • 8.  RE: Failed in device due to invalid url format

    Posted 3 hours ago
    Just simply ‘upgrade’ the AP to a lower version

    ---------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ---------------------------------



    Original Message


  • 9.  RE: Failed in device due to invalid url format

    Posted 2 hours ago

    Hi,

    On the AC it does not recommend any version and I have invalid url format.

    I removed the AP from AC and accessed it on GUI. I can only upgrade it to 8.13.2.0.

    I don't see how I can upgrade it to 8.13.0.1.

    Aruba support sent me the link to download the firmware file: ArubaInstant_Norma_8.13.0.1_93317

    But when tried to upgrade a standalone AP-615 with the downloaded file ArubaInstant_Norma_8.13.0.1_93317, I got image_upgrade_invalid_image error.

    Is this file for AP-615?

    Any idea on how to fix this issue?


    Original Message


Related Content