The likely issue is the CMOS battery is weak and not able to maintain the date when it loses power. The date is changing when there is a power loss or the box is rebooting.
To verify take one such device that is exhibiting the problem and do the below checks.
- First set the date to the current date (2022)
- Then do "sudo hwclock --systohc" from shell
- Perform "sudo reboot."
- Remove the power to the box when it is booting and return the power and restart the device.
Check if the date is still 2022. If it is not then it is a CMOS issue. Please reach out to Hardware Vendor, if its CSG device open support case to help assist further
Here are some commands you can run before and after the reboot. The hwclock command pulls time from the system onboard clock.
If that is not correct then it means the system is not able to retain the clock when it loses power.
admin@versa-flexvnf:~$ date
Tue Jan 3 14:05:23 PST 2022
admin@versa-flexvnf:~$ sudo hwclock --utc
Tue 03 Jan 2022 02:05:31 PM PST -0.906678 seconds
admin@versa-flexvnf:~$ sudo hwclock --localtime
Tue 03 Jan 2022 02:05:35 PM PST -0.406725 seconds
Tue Jan 3 14:05:23 PST 2022
admin@versa-flexvnf:~$ sudo hwclock --utc
Tue 03 Jan 2022 02:05:31 PM PST -0.906678 seconds
admin@versa-flexvnf:~$ sudo hwclock --localtime
Tue 03 Jan 2022 02:05:35 PM PST -0.406725 seconds
NOTE: If NTP is configured on cpe and reachable, it will help sync time back once CPE is up and running..