Hi guys,
I had a similar issue with my 2530 and its NTP configuration.
I was looking how to add my 2530 to Central and one of the key prerequisites for this was NTP and it didn't work.
My firmware version:
YA.16.05.0008.
NTP used to work fine with one of the previous versions but I can't recall when exactly it stopped working - having wrong time on this switch didn't affect its main function :)
The NTP server is a Win2016 server and my IAP, desktop and other VMs used it for time synchronisation with no issues and still do.
This is the configuration I had on the switch:
timesync ntp
ntp unicast
ntp server 192.168.1.10 iburst
ntp enable
time daylight-time-rule southern-hemisphere
time timezone 600
NTP was in constantly in Not Synced state.
In logs it was not reachable:
I 08/28/18 21:21:09 04911 ntp: The NTP Server 192.168.1.10 is unreachable.
Even if it was reachable being in the same subnet with the server:
ping 192.168.1.10
192.168.1.10 is alive, time = 2 ms
After some time spent on troubleshooting the issue I decided to wipe its NTP configuration and switch to SNTP and... drums... it worked out:
I 08/29/18 19:27:04 00413 SNTP: Updated time by 35 seconds from server at 192.168.1.10. Previous time was Wed Aug 29 19:26:29 2018. Current time is Wed Aug 29 19:27:04 2018.
I can't see if my previous config was incorrect but switching to SNTP has resolved the issue. Maybe there is something wrong with the base NTP client.
My current time settings:
timesync sntp
sntp unicast
sntp 30
sntp server priority 1 192.168.1.10
time daylight-time-rule southern-hemisphere
time timezone 600
After that I applied "activate provision force" and my switch popped up in Central.
Also:
If your switch is manufactured before 2017 it's likely it's not in the database so you need to contact TAC to get it added (so did I).
Let's see how it goes with the cloud management... But it's a different story.
Thanks to Vikram from Aruba TAC who helped me in my jorney to Central.