Controllerless Networks

Frequent Contributor I

Instant Time is incorrect

After we downgraded from 3.4 to 3.3 due to some client issues we were having - we noticed that the time on the VCs were now at the year 2000.


We added an NTP. No change.


We manually set the clock in the CLI and the time is always off by five hous. We have the correct timezone set, but no matter what we do the time is always off.


This is occurring in all the VCs we dongraded.


I've checked other site that have 3.3 code and they are fine. No issues with the clock.


Anybody else seeing this?


Re: Instant Time is incorrect

Please open a case for this.  Also, did you open a case for the 3.4 client issues?

Seth R. Fiermonti
Consulting Systems Engineer - ACCX, ACDX, ACMX
If you found my post helpful, please give kudos
Frequent Contributor I

Re: Instant Time is incorrect

Opening a ticket now.

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