Hey all - I have a weird one for you - hope somebody has seen this before. Thanks in advance!
I found myself logged into a WS-C3560G (12.2(44)SE6) today and when I issue a 'reload in 10', the system informs me it will be reloading but not in 10 minutes as desired - rather 3 weeks and 8 hours and change into the future. I've included the commands issued, system response and relevant config.
I issue a 'sh clock' immediately before issuing 'reload in 10' to provide the current time to compare with the system's response to the reload command.
hostname# sh clock 15:53:45.383 CST Wed Feb 7 2018
hostname# reload in 10 Reload scheduled for 23:10:44 CST Wed Feb 28 2018 (in 511 hours and 16 minutes) by redacted on vty0 (ip.ip.ip.ip) Proceed with reload? [confirm] hostname# reload cancel hostname#
I have the clock and ntp configs and below we see that ntp is synched
hostname# sh run | i clock clock timezone CST -6 clock summer-time CDT recurring 3 Sun Mar 2:00 2 Sun Nov 2:00
hostname# sh run | i ntp ntp source VlanBB ntp server ip.ip.ip.ip prefer ntp server ip.ip.ip.ip ntp server ip.ip.ip.ip
hostname# sh ntp stat Clock is synchronized, stratum 2, reference is ip.ip.ip.ip. nominal freq is 119.2092 Hz, actual freq is 119.2079 Hz, precision is 2**18 reference time is DE25F281.95274A75 (15:57:26.582 CST Wed Feb 7 2018) clock offset is 9.4973 msec, root delay is 85.33 msec root dispersion is 41.31 msec, peer dispersion is 31.33 msec
No comments:
Post a Comment