Preview Tool

Cisco Bug: CSCvu98011 - Unable to sync time with NTP after VM suspends.

Last Modified

Jul 29, 2020

Products (1)

  • Cisco IOS

Known Affected Releases


Description (partial)

Controllers: 19.2.2
CSRv1000 SDWAN: 16.12.2r

Same issue is seen on ISRv and CSRv running 17.2.1r on different setup with controllers on 20.1.1.

To me looks like "reference time is E28B639B.991688D0 (13:50:19.598 UTC Wed Jun 10 2020)" is not changing after VM suspend/resume.

If we remove NTP config and readd it, the NTP time is synced fine.

CSRv1000 running SDWAN image 17.2.1 unable to sync time with NTP after VM suspend/resume.

We have CSR1000v configured with NTP. It was time sync fine before we suspended VM on which CSRv1000 is running.

After resuming even after few hours NTP is not syncing with current time.

Logs collected at time 11th June 4:10am UTC time. The current time on Device should be 11th June 4:10am UTC but it is showing yesterday's time.

sdcsrv7# show clock
14:10:43.701 UTC Wed Jun 10 2020
sdcsrv7#show nt
sdcsrv7#show ntp as
sdcsrv7#show ntp associations

  address         ref clock       st   when   poll reach  delay  offset   disp
*~     2    177   1024   377 76.942 5028105  1.056
 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
sdcsrv7#show nt
sdcsrv7#show ntp st
sdcsrv7#show ntp status
Clock is synchronized, stratum 3, reference is
nominal freq is 250.0000 Hz, actual freq is 249.9999 Hz, precision is 2**10
ntp uptime is 7405600 (1/100 of seconds), resolution is 4016
reference time is E28B639B.991688D0 (13:50:19.598 UTC Wed Jun 10 2020)
clock offset is 50281058.4812 msec, root delay is 144.07 msec
root dispersion is 50281126.06 msec, peer dispersion is 1.05 msec
loopfilter state is 'SPIK' (Spike), drift is 0.000000209 s/s
system poll interval is 1024, last update was 1233 sec ago.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.