Wireless Access

 View Only
  • 1.  IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 01:53 AM
    Edited by Eby Feb 26, 2024 01:55 AM

    Instant AP clock gets reset to iap firmware version date after reboot and do not update current time from local NTP server(local server ip and timezone configured on IAP) and  I have option 42 configured on DHCP server.

    On webGUI, command - "AP Current Time" show correct NTP time on top but incorrect system clock. Due to this, Time Based Services are not running properly. Earlier we did not use any time based service. 

    *********************************************************************************************************
     2/26/2024 12:10:13 PM    Target: virtual-c    Command: show clock 
    *********************************************************************************************************
    Current Time     :2021-09-30 21:05:31

    debug

    show log iap-bootup

    starting DHCP
    Getting an IP address...
    172.16.6.65 255.255.254.0 172.16.6.1
    Starting Webserver
    NTP server 172.16.17.60 from configuration.
    Put ntpdate to the nannylist.
    shutting down watchdog process (nanny will restart it)...

    What are my options to resolve this issue ?.

    Thanks,



  • 2.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 04:06 AM

    please give more context, like what firmware version you upgrade to?

    is NTP server reachable? and finally what's the output of "show ntp status"



    ------------------------------
    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.
    ------------------------------



  • 3.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 05:20 AM

    IAP running firmware 8.3.0.17.

    NTP server is reachable from VC.

    There are no ntp related commands.

    # sh n?
    network             Network
    network-summary     




  • 4.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 05:43 AM

    8.3.x is very old, I think it has reached its end of support date. Yo  can fnd the details of EoS at HPE Network support Portal

    Depending on what IAP models you have  I suggest to use something newer.



    ------------------------------
    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.
    ------------------------------



  • 5.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 07:08 AM

    The question is, would upgrading firmware to 8.4.x fix this issue ?.

    Hardware upgrade is not planned at all, for the time being. 




  • 6.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 26, 2024 08:20 AM

    What model of AP?  More than likely you can upgrade to 8.6.  For instant, "show ntp" was added with 8.5.



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 7.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 28, 2024 08:46 AM

    Is this(IAP not setting clock using NTP) known problem/bug/hardware limitation ?.  Would this issue be resolved by upgrading to specific firmware ?.

    Couple of very old 200 and 300 series, 8.3 itself feels slow compared to 6..5.4.x. We upgraded to 8.3.x only for "multi zone" feature.

    Thanks,




  • 8.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 28, 2024 09:52 AM

    I wasn't able to find anything in my brief search, but 8.6 is likely the last version supported by your combination of hardware and would be the recommended firmware to be running.



    ------------------------------
    Carson Hulcher, ACEX#110
    ------------------------------



  • 9.  RE: IAP clock not getting updated from local NTP server.

    Posted Feb 29, 2024 10:13 AM

    Thanks, I'm hesitant to run later code on these ancient devices. due to stability issues and bugs that are said to be fixed aren't really fixed at all.

    e.g. 

    1, 8.3.x release note, resolved issues related to clock confirm "System clock is too far ahead of NTP sync result" is fixed. Yet, system clock not getting updated using NTP on  200/300 series devices running 8.3.x .

    https://www.arubanetworks.com/techdocs/Instant_8.x_RN_WebHelp/Content/8.3/00/resolved-issues-8300.htm?Highlight=clock

    2, firmware command say NTP required for "time-range" command to work, but rely on system clock for time range functions. Time based SSID only get activated when the system clock reach the scheduled time.

    virtual-c (SSID Profile "Ldevices") # ?
    a-basic-rates                          
    .......<command list ommitted>
    time-range                             NTP needs to work for this feature to work correctly
    .......<command list ommitted>
    zone                                   
    virtual-c (SSID Profile "Ldevices") #