Wired Intelligent Edge (Campus Switching and Routing)

Reply
New Contributor

Re: Aruba 2530 NTP issues

Here is some information that you requested.
NTP config:

1.PNG2.PNG

Show running-config:

3.PNG

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. 

New Contributor

Re: Aruba 2530 NTP issues

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

New Contributor

Re: Aruba 2530 NTP issues

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

New Contributor

Re: Aruba 2530 NTP issues

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.

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: