Wireless Access

 View Only
Back to discussions
Expand all | Collapse all

Aruba AP-515 can't be provisioned

This thread has been viewed 7 times

  • 1.  Aruba AP-515 can't be provisioned

    Posted 6 days ago

    Good Day All,

    Im trying to recover some AP that turn on but can't be provisioned in the MM dashboard

    I've used the AP-CBL-SERU cable to see what was going on during the boot.

    I've tried 2 way, one is the manual factory reset with serial cable:

    factory_reset
clear os
osinfo
dhcp
setenv serverip <TFTP IP>
upgrade os <Aruba OS Filename>
osinfo
setenv os_partition 0
save
reset

    and the other was the official factory reset trough the button behind the AP.

    my environment is the following:


    1 cluster with 2 controllers, version: AOS-8 (MODEL: ArubaMM-VA), Version 8.13.1.2 LSR

    Im going to attach the two output for the two way.

    From what I can see, it seems the AP is unable to communicate with controllers somehow, like the certificate can't be generated, at the end of the auto factory reset I read:

    no rsa host key is available
no ecdsa host key is available
generating ssh rsa host key..

        <<<<<       Welcome to the Access Point     >>>>>

~ # generating ssh ecdsa host key..

~ #
~ #

    I have checked also from MM if the AP was allowed:


    (XX-XX-XXX) [mynode] #show allowlist-db cpsec | include cc:88:c7:c9:6a:08
cc:88:c7:c9:6a:08                     Enabled  certified-factory-cert       factory-cert                            Mon May 18 14:48:11 2026
(XX-XX-XXX) [mynode] #

    Any suggestions?

    Thank You,

    regards



    -------------------------------------------

    Attachment(s)

    txt
    AP-515-LOG_button_factory_reset.txt   8 KB 1 version
    txt
    AP-515-LOG_Manual_update.txt   10 KB 1 version


Related Content