Re: Someone didn't get the leap second memo...

We manage a couple of these too, running an affected version. :( I've applied the suggested workaround, but not the recommended 24h in advance of the unexpected leap second. I'll find out tomorrow if that mattered. On Sat, 31 Dec 2016, Richard Hicks wrote: We had some ASR1001s routers

Re: Someone didn't get the leap second memo...

We had some ASR1001s routers reboot. Looks like we hit this bug: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb01730 On Sat, Dec 31, 2016 at 5:47 PM, Hugo Slabbert wrote: > Had a set of Cisco ASR1004s running 15.4(3)S1 (on IOS-XE 03.13.01.S) all > restart at around

Re: Someone didn't get the leap second memo...

Had a set of Cisco ASR1004s running 15.4(3)S1 (on IOS-XE 03.13.01.S) all restart at around midnight UTC, and all with `Last reload reason: Watchdog`, with those boxes being at separate DCs in different regions. I'm assuming when I call TAC I'll get a "whoops; sorry". -- Hugo Slabbert |

Someone didn't get the leap second memo...

[root@hayden ~]# ntpq -p remote refid st t when poll reach delay offset jitter == LOCAL(0).LOCL. 10 l 20d 6400.0000.000 0.000 -clock.xmission. 132.163.4.1032