Wireless Access

 View Only

  • 1.  AP-315 image upgrade failed (AOS6 to 8)

    Posted Nov 21, 2023 11:21 AM

    Hi community,

    I am running a mobility conductor environment with WLC7220 on AOS8 and still have some old AP-315 left from good old AOS6 times.

    These AP-315 have never been connected to controllers ...so when I am connecting them to the current setup (8.10.0.7) they all fail to upgrade to the current image:

    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  lms 136.230.84.239 file ipq806x.ari part 1 strap 0 preload 0 size 14947384
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  vm.min_free_kbytes = 10
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  mem free 356488 minimum 21895 (memmin 14897)
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  /aruba/bin
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Running /aruba/bin/ncftpget  -V -g 1 -u *** -p *** -t 5,5,5  -B 8192 136.230.84.239 . ipq806x.ari
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ERROR: File size exceeded 14680064 bytes
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Local write failed: Success.
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ncftpget ipq806x.ari: no space.
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  FTP Failed: 3. Trying FTP again
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Running /aruba/bin/ncftpget  -V -g 1 -u *** -p *** -t 5,5,5  -B 8192 136.230.84.239 . ipq806x.ari
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ERROR: File size exceeded 14680064 bytes
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Local write failed: Success.
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ncftpget ipq806x.ari: no space.
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  FTP Failed: 3. Trying TFTP.
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Running /aruba/bin/sap-tftp -g -r ipq806x.ari -l ipq806x.ari -P 1 136.230.84.239
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ERROR: File size exceeded 14680064 bytes
    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Flash Image upgrade failed: Result code 255
    Nov 15 08:02:05 2023  sapd[2205]: <311002> <WARN> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  Rebooting: SAPD: Reboot after image upgrade failed: 65280
    Nov 15 08:02:05 2023  nanny[2152]: <303086> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 nanny| Process Manager (nanny) shutting down - AP will reboot!
    Nov 15 08:02:14 2023  nanny[2152]: <303022> <WARN> |AP 80:8d:b7:ce:e2:b2@136.230.36.47 nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:01:32 PST 1969; SAPD: Reboot after image upgrade failed: 65280
    Nov 15 08:02:19 2023  sapd[2323]: <311013> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd| Image upgrade failed; details follow.
    Nov 15 08:02:19 2023  sapd[2323]: <311014> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd|  lms 136.230.84.239 file ipq806x.ari part 1 strap 0 preload 0 size 14947384
    Nov 15 08:02:19 2023  sapd[2323]: <311014> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd|  vm.min_free_kbytes = 10
    Nov 15 08:02:19 2023  sapd[2323]: <311014> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd|  mem free 381500 minimum 21895 (memmin 14897)
    Nov 15 08:02:19 2023  sapd[2323]: <311014> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd|  /aruba/bin
    Nov 15 08:02:19 2023  sapd[2323]: <311014> <ERRS> |AP 00:4e:35:c3:35:3e@136.230.36.64 sapd|  Running /aruba/bin/ncftpget  -V -g 1 -u *** -p *** -t 5,5,5  -B 8192 136.230.84.239 . ipq806x.ari

    Am I doing something wrong or is it normal that they cannot be updated directly to this firmware? I don't know which firmware the APs have...could be that they are very early APs with 6.4.x.x

    Thanks and best regards,

    Michael



  • 2.  RE: AP-315 image upgrade failed (AOS6 to 8)

    Posted Nov 21, 2023 11:30 AM

    I believe this applies to the 315 as well:  https://asp.arubanetworks.com/notifications/Tm90aWZpY2F0aW9uOjEzMDM3;notificationCategory=Product



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: AP-315 image upgrade failed (AOS6 to 8)

    Posted Nov 23, 2023 01:39 AM

    Thank you,

    will try that tomorrow.

    Best regards,

    Michael


    Original Message


  • 4.  RE: AP-315 image upgrade failed (AOS6 to 8)

    Posted Dec 07, 2023 05:12 AM
    Edited by MK-bb8a89 Dec 07, 2023 05:24 AM

    Hi,

    I had exact the same issue. Customer runs AOS8.10.07 and had a bunch AP-315 with 6.x code the lay down in the warehouse for a couple of years.

    Solved it removing the backup partition from the CLI, becasuse the Aruba solutions didnt work for me).

    apboot> clear cache
    Erasing flash sector @ 0x3a0000...OK
     
    Device 0: nand0... is now current device
    Erasing UBIFS ...OK
    Remove UBI volume ubifs (id 0)
    Creating dynamic volume ubifs of size 63234048
    Device 1: nand1... is now current device
    apboot> clear os 1
    512 bytes written to volume aos1
    apboot> safe
    Unknown command 'safe' - try 'help'
    apboot> s
      saveenv setenv
    apboot> saveenv
    Saving Environment to Flash...
    Erasing flash...
    Writing to flash... ...............done
    apboot> boot



    ------------------------------
    Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
    ------------------------------



  • 5.  RE: AP-315 image upgrade failed (AOS6 to 8)

    Posted Dec 08, 2023 04:00 AM

    To add a bit of detail, there are AP images that have an image file size limit. If these units are upgraded to a newer version with a larger image, one should see this error message in the log:

    Nov 15 08:02:04 2023  sapd[2205]: <311014> <ERRS> |AP 80:8d:b7:ce:de:96@136.230.36.56 sapd|  ERROR: File size exceeded 14680064 bytes

    The alternative to the process outlined is to upgrade the second (recovery) partition to a more modern version that can handle the larger image files. (partition 1 is used during AOS upgrades), which does not require AP console access.

    If the AP is connected to an Aruba controller, "show ap image version" will show the active image, and the contents of both partitions.

    a) if the unit is UAP, convert or factory default (which uses the 2nd partition) and perform an IAP upgrade twice - the 1st will overwrite partition 0, the 2nd will overwrite

    partition 1

    b) Attach the AP to an Aruba controller with an older version, and forcibly upgrade the 2nd partition to a more modern version, but still small enough for the 

    AP to accept. When this newer more modern version is installed, we can then upgrade to newer versions which have larger images.

    The ASP site notifications offer this bulletin which provides more detail:

    ARUBA-SA-20220922-PLVL02 :: Older AP-320 Series Access Points ArubaOS Upgrade and AP Firmware File Size Limitation (Rev-1)
    Sep 23, 2022
    If these AP-315s can be connected as Campus APs,  first upgrade to one of the following ArubaOS versions:
    ArubaOS 6.5.4.23  or higher
    ArubaOS 8.6.0.17  or higher 
    ArubaOS 8.7.1.9    or higher 
    ArubaOS 8.9.0.3    or higher 
    ArubaOS 8.10.0.0  or higher 


    ------------------------------
    Shawn Adams
    ------------------------------

    Original Message


Related Content