On 31 May 2018 at 18:04, Chris Adams <c...@cmadams.net> wrote: > I had an MX80 crash (insert sad face here) - worse problem was that it > did a crash dump and then did NOT reboot. I have out-of-band serial > access to the console, so I could see that, after the dump completed, it > just printed: > > watchdog: scheduling fairness gone for 240 seconds now. > > every 20 seconds (with the seconds count increasing). I had to open a > remote-hands ticket to get it power cycled. > > Is there any way to for a reboot at that point? Like, on old Sun > servers, sending a BREAK followed by certain other keys could get to the > firmware and hard-reboot the system, even with the OS was fubar. Is > there anything like that on a Juniper?
Some network devices don't even have console ports or OOB IP MGMT ports etc. so for this reasons we deploy PDUs with remote power cycling. We can hard power cycle a crashed device. I strongly recommend this. Cheers, James. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
