Refer to the exhibit. An administrator noticed that after a change was made on R1, the timestamps on the system logs did not match the clock.
What is the reason for this error?
Refer to the exhibit. An administrator noticed that after a change was made on R1, the timestamps on the system logs did not match the clock.
What is the reason for this error?
The reason the timestamps on the system logs did not match the clock is that the keyword 'localtime' is not defined on the timestamp service command. By default, syslog and debug messages are stamped with UTC time regardless of the configured time zone on the device. Including the 'localtime' keyword in the timestamp service command aligns the logs with the local time configured on the system clock.
I think B is the correct https://community.cisco.com/t5/networking-documents/router-log-timestamp-entries-are-different-from-the-system-clock/ta-p/3132258
By default, syslog and debug messages are stamped by UTC, regardless of the time zone that device configured. You should append localtime key word to "service timestamp {log | debug} datetime msec" global command to change that behavior.
yes option B https://community.cisco.com/t5/networking-documents/router-log-timestamp-entries-are-different-from-the-system-clock/ta-p/3132258
B is the correct answer!
As in discussion
The answer is B. Even if the the time was synched with NTP the log and the clock would still show a difference because localtime was not included in the service timestamp command
the questionnis why logs and clock do not match and not if ntp is syncd or not
so it's B
B is correct.
Agree on B is the correct.
The difference in times between show clock and the logging timestamps is because logging messages are not set to use local time. (c) service timestamps log datetime localtime will fix the error If the output of show clock has an '*' it does indicate there is no synchronization between an NTP server. It doesn't necessarily mean that the time is incorrect or authentication error
* at start shows a clock error against ntp server
The given answer is B
It’s matching that they are showing you the #show clock command. But the NTP is not working properly due “recent changes” you can notice that with the “*” symbol.
The question is why the clock is having a different time than the actual logs generated. The question is not that the clock is having the incorrect time. Concluding, the answer to the question appears to be B
"*" symbol means time is not authoritative: the software clock is not in sync or has never been set.
B is correct
A is correct. An '*' preceding the datetime indicates that the local clock is not synced with a time source
It's B hands down