Re: [j-nsp] Update to 9.4R1.8 gone bad

are or does the documented procedure usu- ally work? Cheers, sven03 Tommy Perniciaro wrote: > RTFM > > - Original Message - > From: juniper-nsp-boun...@puck.nether.net > > To: juniper-nsp@puck.nether.net > Cc: Stacy W. Smith > Sent: Wed Feb 18 23:48:5

Re: [j-nsp] Update to 9.4R1.8 gone bad

RTFM - Original Message - From: juniper-nsp-boun...@puck.nether.net To: juniper-nsp@puck.nether.net Cc: Stacy W. Smith Sent: Wed Feb 18 23:48:50 2009 Subject: Re: [j-nsp] Update to 9.4R1.8 gone bad -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, they asked me to do a 're

Re: [j-nsp] Update to 9.4R1.8 gone bad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, they asked me to do a 'request system snapshot' and miraculously the box is now able to boot from flash. Care to clue me in on what happened here? Thanks, sven03 Stacy W. Smith wrote: > Sven, > > Can you provide me with your JTAC case

Re: [j-nsp] Update to 9.4R1.8 gone bad

ther.net] On Behalf Of Sven Juergensen > (KielNET) > Sent: 18 February 2009 08:35 > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] Update to 9.4R1.8 gone bad > > Hi list, > > I recently updated one MX router from 9.3 t

Re: [j-nsp] Update to 9.4R1.8 gone bad

] Update to 9.4R1.8 gone bad -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, I recently updated one MX router from 9.3 to 9.4. What shows up after that is - -- Alarm time Class Description 2009-02-18 07:46:34 UTC Minor Host 0 Boot from alternate media - -- and after logging

[j-nsp] Update to 9.4R1.8 gone bad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, I recently updated one MX router from 9.3 to 9.4. What shows up after that is - -- Alarm time Class Description 2009-02-18 07:46:34 UTC Minor Host 0 Boot from alternate media - -- and after logging in to that RE - -- - ---