[j-nsp] Procedure for upgrade routing engines.
Mark Tinka
mark.tinka at seacom.mu
Wed Jan 8 08:15:21 EST 2014
On Wednesday, January 08, 2014 03:05:12 PM Daniel Roesen
wrote:
> I have no idea what to make out of this fuzzy comment.
> "one minute or so" is not a reasonable time frame for
> any upgrade action as this is not enough time to boot it
> up, wait for it to settle, perform health checks, switch
> over to it, let the dust settle down and replace the
> formely active, old RE too.
>
> Perhaps some JNPR folks can chime in with actual
> technical facts and details?
A technical dude that spoke the truth, but didn't run it by
his PLM to handle the practical side of it :-).
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20140108/b35de9cd/attachment.sig>
More information about the juniper-nsp
mailing list