cancel
Showing results for 
Search instead for 
Did you mean: 

Time on my F5 device doesn't matched with the real time on my desktop

Ren_Alcala
Cirrus
Cirrus

Hi Sir/Ma'am,

 

Does anyone know how to fix the time of my F5 Devices that doesn't matched the real-time?? Please see the screenshot below.

 

0691T00000Co12fQAB.png 

 

Thanks,

Renato

1 ACCEPTED SOLUTION

AlexBCT
MVP
MVP

Hi Renato,

 

Has this F5 already been rebooted after the timezone has changed? I've noticed that this time display doesn't always update when it has been changed and a reboot normally sorts it out.

If that doesn't fix it, have a look at the NTP configuration (via Linux CLI: ntpq -p) to see if it has any connections to upstream time servers). If there are none, it is likely that the F5 gets the time from the hypervisor, so then you will have to have a look how the time is configured on the hypervisor.

 

Seen that the time is 3 hours and 10 minutes out of sync compared to the Windows system, I suspect that either the F5 or the hypervisor cannot synchronize its time.

 

Hope this helps.

View solution in original post

3 REPLIES 3

AlexBCT
MVP
MVP

Hi Renato,

 

Has this F5 already been rebooted after the timezone has changed? I've noticed that this time display doesn't always update when it has been changed and a reboot normally sorts it out.

If that doesn't fix it, have a look at the NTP configuration (via Linux CLI: ntpq -p) to see if it has any connections to upstream time servers). If there are none, it is likely that the F5 gets the time from the hypervisor, so then you will have to have a look how the time is configured on the hypervisor.

 

Seen that the time is 3 hours and 10 minutes out of sync compared to the Windows system, I suspect that either the F5 or the hypervisor cannot synchronize its time.

 

Hope this helps.

Hi  ,

 

It is now back to normal sir :). I just did what you have told me to reboot the devices. Thank 🙂

 

Regards,

Renato

Ha, brilliant - Glad to hear 🙂

To be honest, the time in the device itself does normally have the correct information (type "date" via command line), but this time on the GUI often indeed doesn't update immediately.

Either way, glad to hear it's sorted!