FMC virtual Time different in Gui versus in Shell

[evan.chadwick1]

Hi, 

Virtual FMC running 6.2.2

The time in the Gui is different to on the cli.

Both are set to use the same NTP server.

can anyone explain the difference? It seems that FMC can pull its time from configuration within the product package (connection events are correctly timestamped). 

Where does linux time come into the solution. 

As a fix shall I just manually match the time up and ntp will take care of the rest?

PS I noticed this after upgrading from 6.1.0.3 to 6.2.2

[Flavio Miranda]

Hi,

I´d take a look here. Very handy commands for NTP troubleshooting.

https://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/118626-technote-firesight-00.html

-If I helped you somehow, please, rate it as useful.-

[evan.chadwick1 · Accepted solution]

Thanks. 

To be clear, this is about time being different on the FMC cli versus its time in the Gui.

i'm going to manually help it catch up and ntp should keep it in check from there. 

[Flavio Miranda · Accepted solution]

Looks like CLI uses UTC default. Maybe this can explain.

[Flavio Miranda]

Thanks for rating and changing the status to solved. This helps make this forum better.

-If I helped you somehow, please, rate it as useful.-

[evan.chadwick1]

FYI - looks like one is not supposed to manually change it either. 

Looks like there is alot of discussion about Firepower Sensors time. But i'm interested in the linux output for FMC from a 'date' command. 

i'm part way through my upgrades, and its improved from when I first raised this POST. 

Its gone from over 24 hours out, to now probably the Default UTC, about 12 - 13 hours. 

I can probably live with this if I have to.