DNA Assurance - DNA Center and network device time has drifted

[Eoin.Quinn]

Hi Guys

We're receiving the "Device time has Drifted" error constantly from all catalysts on our network in DNA Assurance but can't find a reason why.

All equipment is using the same NTP server and all are synchronised. It doesn't seem to be happening with the WLCs (Same NTP server again). When you check the clock times they're always identical but after resolving the issue it usually appears multiple times a day.

Our software versions are v1.3.3.3(1) on DNAC, 16.11.1 on 9500s and  16.9.3 on 9300s. This has only started appearing since DNAC 1.3.3 from what I can recall.

Has anyone else encountered similar?

Thanks!

Eoin

[grabonlee]

I noticed same alarm as soon as I upgraded to version 1.3.3. Since my DNAC is primarily for Wireless, I have removed the switches for now.

[Preston Chilcote]

I think 1.3.3.3 has the fix for CSCvr46035 (Cisco DNA Center Assurance reports timeskew when timezone is configured on device) already, so it's probably not that one.

Can you confirm that the time isn't really out of sync (compare "show clock" on network device with "date" on Cisco DNA's maglev shell). If so, it's probably CSCvt13305 (Excessive time drift reported on Cisco DNA Center even when the device is NTP synced), which will be fixed in the next major release late this month or early next.

If you have a timezone (other than UTC) configured on your Cisco DNA appliance, removing it might be a workaround. Let us know if that helps.

[StevieC666]

Having the same here. Running 1.3.3.1 and 16.9.5, when I look I see that the clock time is 1hour behind DNAC time. I assumed that it was because we hadn't yet set a time zone/daylight savings on the switching and therefore depsite being in sync they're in sync with UTC and not being corrected for BST?

It's on the long list of things to log with TAC at some point.

[Arne Bier]

Hi 

any joy with TAC - we have the same issue - DNAC 1.3.3.5 - DNAC is set to UTC, but correct timezone - the wall clock in DNAC GUI is correct - so it's calculating the correct offset. IOS-XE devices set to AEDT and also in sync with NTP. I think DNAC is getting itself confused.

I have not raised a TAC case yet - wondering if anyone can spare me that agony ...

[Arne Bier]

This looks like the culprit

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr46035/?rfs=iqvred