Wired Intelligent Edge

Hi all,

looking for some guidance. 

have configured a pair fo 2530s to talk NTP to windows server and the status is showing config , insane and the ntp server is not ever going into sync. 

show ntp status

NTP Status Information

NTP Status : Enabled NTP Mode : Unicast
Synchronization Status : Not Synced Peer Dispersion : 0.00000 sec
Stratum Number : 16 Leap Direction : 0
Reference Assoc ID : 0 Clock Offset : 0.00000 sec
Reference ID : 0.0.0.0 Root Delay : 0.00000 sec
Precision : 2**-18 Root Dispersion : 0.08570 sec
NTP Up Time : 0d 1h 35m Time Resolution : 1270 nsec
Drift : 0.00000 sec/sec

System Time : Mon May 15 15:44:22 2017
Reference Time : Mon Jan 1 11:00:00 1990

IP Address : 10.10.4.10 Peer Mode : Server
Status : Config,Insane Peer Poll Intvl : 6
Stratum : 1 Root Delay : 0.00000 sec
Ref Assoc ID : 1 Root Dispersion : 10.54242 sec
Assoc Name : NTP Association 1 Reach : 37777777777
Reference ID : 76.79.67.76 Delay : 0.00603 sec
Our Mode : Client Offset : -10.05123 sec
Our Poll Intvl : 6 Precision : 2**-23
Dispersion : 0.02230 sec
Association In Packets : 74
Association Out Packets : 74
Association Error Packets : 0
Origin Time : Mon May 15 15:44:14 2017
Receive Time : Mon May 15 15:44:24 2017
Transmit Time : Mon May 15 15:44:24 2017

-------------------------------------------------------------------------
Filter Delay = 0.0064 0.0084 0.0111 0.0068 0.0094 0.0060 0.0116 0.8501
Filter Offset = -10.0358 -10.0384 -10.0430 -10.0452 -10.0481 -10.0512
-10.0524 -9.6364

IP Address : 10.10.5.10 Peer Mode : Server
Status : Config,Insane Peer Poll Intvl : 6
Stratum : 2 Root Delay : 0.00175 sec
Ref Assoc ID : 2 Root Dispersion : 10.56506 sec
Assoc Name : NTP Association 2 Reach : 37777777777
Reference ID : 10.10.4.10 Delay : 0.00579 sec
Our Mode : Client Offset : -10.05795 sec
Our Poll Intvl : 6 Precision : 2**-23
Dispersion : 0.03462 sec
Association In Packets : 74
Association Out Packets : 74
Association Error Packets : 0
Origin Time : Mon May 15 15:43:34 2017
Receive Time : Mon May 15 15:43:44 2017
Transmit Time : Mon May 15 15:43:44 2017

-------------------------------------------------------------------------
Filter Delay = 0.0065 0.0065 0.0136 0.0063 0.0063 0.0059 0.0086 0.0058
Filter Offset = -10.0372 -10.0401 -10.0399 -10.0456 -10.0486 -10.0515
-10.0550 -10.0579

Here is my config:

timesync ntp
no sntp
ntp unicast
ntp server 10.10.4.10 iburst
ntp server 10.10.5.10 iburst
ntp enable
time daylight-time-rule user-defined begin-date 10/01 end-date 04/01
time timezone 600

NTP Server is windows DC. 

Any ideas?

Scott

Hi Scott,

Can you provide some more details on the NTP server? What version of windows are you using maybe add even output of following command  w32tm /query /configuration when it's standalone NTP server.

Thanks in advance!

Hi Dobias, 

Its Win 2016 Server. Unfortunately i had to move on and no longer have access to the environment. The switches have been configured to talk to an external NTP server now. 

When i get some time i'll try and lab this up again. 

Scott

Hi Scott,

No problem and let me know whenever I can support you.

Regards, Dobias

Hi Dobias!

Maby you can help me? Thnx.

I can at leat try 8-)

Can you forward me the NTP configuration of the switch and if possible add IP information and some details of NTP server?

Hi,

Did anyone ever resolve this issue?

I have the same problem on my Aruba 2530, im running my WatchGuard Router as the NTP Server, all other devices can use the WatchGuard as the NTP server except the Aruba.

I can see network traffic passing through from the switch to the router, i can ping it etc... i just get a returned error in the logging of the Aruba saying it was unreachable.

As a test are you able to confirm an external NTP server on the switch, does this work? Have you tried manually sync'ing the clock to the same time/date on the NTP and then tried configuring the NTP server again? I've seen issues where if the difference is too great between the device and the NTP server it will not sync? Also, don't forget to check the NTP versions you have configured.

Here is some information that you requested.
NTP config:

Show running-config:

NTP server is Windows Server 2008R2.

I think that main part of this issue that Switch tryies to sync by management vlan, but vlan that NTP server located is not in mgt vlan. And there is no feature to point wich vlan use for NTP syncronization. 

Hello,

Same problem here with 2930F:

Time on switch:

Thu Aug  9 11:59:26 2018

Config:

timesync ntp
ntp unicast
ntp server 10.10.10.10 iburst
ntp enable
time timezone 120

Status:

NTP Status Information

  NTP Status             : Enabled         NTP Mode        : Unicast
  Synchronization Status : Not Synced      Peer Dispersion : 0.00000 sec
  Stratum Number         : 16              Leap Direction  : 0
  Reference Assoc ID     : 0               Clock Offset    : 0.00000 sec
  Reference ID           : 0.0.0.0         Root Delay      : 0.00000 sec
  Precision              : 2**-18          Root Dispersion : 0.00755 sec
  NTP Up Time            : 0d 0h 8m        Time Resolution : 819 nsec
  Drift                  : 0.00000 sec/sec

  System Time            : Thu Aug  9 11:58:50 2018
  Reference Time         : Mon Jan  1 02:00:00 1990

Debug:

0001:00:12:39.91 NTP  eNtpTask:Sent NTP Packet of 48 bytes to 10.10.10.10
0001:00:12:39.99 NTP  eNtpTask:NTP Packet of 48 bytes received from 10.10.10.10
0001:00:12:40.07 NTP  eNtpTask:Chimelist:
0001:00:12:40.12 NTP  eNtpTask:Clock Select algorithm selected 0 peers

Any ideas ?

Thanks.

Jean

Well, changing NTP server from windows to network switch, it is now working:

Aruba-VSF-2930F(vlan-1)# sho ntp status

 NTP Status Information

  NTP Status             : Enabled         NTP Mode        : Unicast

  Synchronization Status : Synchronized    Peer Dispersion : 0.00000 sec

  Stratum Number         : 4               Leap Direction  : 0

  Reference Assoc ID     : 0               Clock Offset    : 0.00135 sec

  Reference ID           : 10.105.216.2    Root Delay      : 0.04532 sec

  Precision              : 2**-18          Root Dispersion : 1.26328 sec

  NTP Up Time            : 0d 3h 46m       Time Resolution : 820 nsec

  Drift                  : 0.00001 sec/sec

  System Time            : Thu Aug  9 15:38:43 2018

  Reference Time         : Thu Aug  9 15:27:11 2018

Logs:

I 08/09/18 15:36:13 04910 ntp: ST1-CMDR: All the NTP server associations reset.

I 08/09/18 15:36:13 04909 ntp: ST1-CMDR: The NTP Stratum was changed from 16 to 4.

I 08/09/18 15:36:13 04908 ntp: ST1-CMDR: The system clock time was changed by

            123 sec 201227240 nsec.      The new time is Thu Aug  9 15:36:13 2018

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.

Hello! Did you resolve this issue? Because I have the same problem, with my Aruba 3800 switch. So it's not synchronize with my NTP server. When I listed syslog, it shows this: " ntp: ST1-CMDR: The NTP Server *ip_address* is unreachable." But ping is working greate. Other HPE switches in network synchronize with this NTP server without problem.

unfortunately i had to move on before being able to troubleshoot any further.