Cloud Managed Networks

 View Only

  • 1.  AP Provision to Central - NTP Unresponsive error.

    Posted Mar 03, 2026 11:23 AM

    Hello everyone,

    I have an AP-635 factory reset connected to a lab switch in Manila Ph.  It booted up through the process connected to a backup controller in the US.  I see the AP on that controller in the US in the default AP-Group.   I want to connect this to Central.  In old Central I create an AP group managed by new central.  I also set it to do a firmware enforcement to get the AP to AOS 10.8.  I am watching a 3 year old video on YT that said to run some commands like:

    ap convert pre-validate all-aps
    show ap convert-status

    I get the below status which shows an NTP unreachable message?  My question is how do I fix this?  The controller is AOS 8.10.x and has NTP configure.  The time on the controller is correct.  The AP is in campus mode.  And we do not allow external NTP

    (xxxxx) [MDC] *#show ap convert-status
     
    AP Conversion Parameters
    ------------------------
    Item                             Value
    ----                             -----
    Status                           Active
    Mode                             All APs
    Image Source                     None
    Max Simultaneous Converting      1000
    Current Simultaneous Converting  0
    Auto Reboot                      True
    Start Time                       2026-03-03 10:46:45
    Current Status                   Pre-Validating
     
    AP Image Conversion AP Status Summary
    -------------------------------------
    AP Image Conversion State  Count
    -------------------------  -----
    Pre Validate Failed        1
    TOTAL                      1
     
    AP Image Conversion Status
    --------------------------
    AP Name            AP Group  AP Mac             AP Serial #  AP IP         AP Type  Upgrade State        Start Time           End Time             Failure Count  Failure Reason   Central url  Central Group
    -------            --------  ------             -----------  -----         -------  -------------        ----------           --------             -------------  --------------   -----------  -------------
    ec:1b:5f:c2:ea:bb  default   ec:1b:5f:c2:ea:bb  PHSZKYJ38F   10.214.1.179  635      Pre Validate Failed  2026-03-03 10:46:45  2026-03-03 10:48:09  1              NTP unreachable   

    (xxxxx) [MDC] *#show ntp servers 
     
    NTP version is ntp-4.2.8p15.
     
    NTP Server Table Entries
    ------------------------
     
    Flags:     * Selected for synchronization
               + Included in the final selection set
               # Selected for synchronization but distance exceeds maximum
               - Discarded by the clustering algorithmn
               = mode is client
     
      remote                                  local                                    st   poll   reach    delay     offset      disp
     
    =========================================================================================================================================
     
    *xxxxx                              xxxx                            2   64     377    0.04326    +0.002194    0.06834
     
    Upstream NTP Server(s) are reachable.
    Time synchronization is with configured upstream NTP server.


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


  • 2.  RE: AP Provision to Central - NTP Unresponsive error.
    Best Answer

    Posted Mar 03, 2026 04:59 PM

    this is the current migration steps from AOS8 to AOS10 
    check the section "Migrating controller managed APs to AOS 10"

    Lastly ensure the associated gateway/AP should be running AOS 8.10.0.12, 8.12.0.1, or a later release



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------

    Original Message


  • 3.  RE: AP Provision to Central - NTP Unresponsive error.

    Posted 24 days ago

    Just as a reference if you have UAP or IAP that is CAP. You can use the command "ap redeploy controller-less". It will basically force the AP to load form the other boot bank and come up as an IAP. There are some other factors that come into play when using redeploy vs convert. The AP would not care about NTP, nor would it care about being registered in central.  There is also a "ap deploy-profile" that you can ignore subnets for a UAP converting to CAP. 

    I do think the "ap convert" command is a safer use as if you go form AOS 8 to AOS 10. There is no adp (discovery) that would cause the AP to phone back to controller/gateway. The "ap convert" will upgrade both boot banks and you can go right to the destination version you want to use. 

    I did have some issues on 8.10 version where the AP's kept failing with "ap convert", I believe it had something to do with the size of the draco image. I didn't pay much attention as I just used another method. 

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

    Original Message


Related Content