It seems not be documented by juniper - atleast i couldnt find any (MX related) info. However its a basic linux procedure, see: https://en.wikipedia.org/wiki/Magic_SysRq_key
Juniper only has some info regarding SysRQ & the IDP series at: https://kb.juniper.net/InfoCenter/index?page=content&id=KB6660&actp=MET ADATA -Jonas Am Donnerstag, den 05.04.2018, 09:34 -0500 schrieb Aaron Gould: > Thanks Rob, Is a break followed by c within 5 seconds a documented > way to > crash a RE-S-X6-64G ? > > Btw, Jtac couldn't find the dump > > Rma'ing RE ... said bad SSD on RE > > -Aaron > > -----Original Message----- > From: Rob Foehl [mailto:r...@loonybin.net] > Sent: Wednesday, April 4, 2018 2:11 PM > To: Aaron Gould > Cc: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] mx960 crashed > > On Wed, 4 Apr 2018, Aaron Gould wrote: > > > > > Any idea why this happened and how do I tshoot cause ? > > > > login: root > > > > Password:SysRq : Trigger a crash > Looks like you're running a RE-S-X6-64G, and somehow sent it SysRq c > -- > which is a break followed by c within 5 seconds on a serial console > -- and > the hypervisor dutifully crashed and wrote out a dump. Can't really > blame > it for doing what it's told. > > -Rob > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp
signature.asc
Description: This is a digitally signed message part
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
