Wireless Access

last person joined: yesterday 

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

AP-365 stuck at boot

  • 1.  AP-365 stuck at boot

    Posted Jan 30, 2018 12:09 PM

    We are deploying 5 AP-365 units connected to 72xx controllers running 6.5.4.3.

     

    Most of them get stuck here:

     

    APBoot 2.1.4.7 (build 57679)
    Built: 2016-12-08 at 15:43:35

    Model: AP-36x
    DRAM: 512 MiB
    Flash: Detected W25Q32FV_SPI: total 4 MiB
    NAND: 128 MiB

     

    After a few minutes, they reboot and do the same. The switch shows link and power, but clearly the AP is not booting.

     

    Two of them I was able to upgrade code to the latest but then they won't talk to the controller because of

     

    SAPD: Rebooting after setting cert_cap=1. Need to open a secure channel(IPSEC)

     

    and also showing as certified-hold-factory-cert. I've changed it to approved but they go back to this mode no matter what.

     

    Another one I am able to boot and factory reset, but after it attempts to convert to a campus AP, it gets stuck on boot like the other ones or gives me an error like this:

     

    APBoot 2.1.4.7 (build 57679)
    Built: 2016-12-08 at 15:43:35

    Model: AP-36x
    DRAM:  512 MiB
    Flash: Detected W25Q32FV_SPI: total 4 MiB
    NAND:  128 MiB
    Power: POE
    ## Error inserting "filesize" variable, errno=12

    ## Error inserting "filesize" variable, errno=12

    ## Error inserting "filesize" variable, errno=12

    ## Error inserting "filesize" variable, errno=12

    ...

     

    Is it a bad batch? I don't think it's a power issue. We've tried two different models of Cisco switches (one 802.11af and one 802.11at) and a PoE+ injector with the same results.

     

    TAC issued an RMA for just two units. Any clues?



  • 2.  RE: AP-365 stuck at boot

    Posted Jan 31, 2018 11:35 AM

    We got one of the replacements. This one worked perfectly fine straight out of the box, however this one shipped with APBoot 2.1.4.13 and AOS 6.5.3.0

     

    Wondering if the older APBoot has an issue. Can this be updated?

     

    I asked to RMA all other 5 APs but makes me wonder what would have happened if I had hundred's of them. We will probably be adding 100+ 303H and concerned something like this may happen.