> -----Original Message----- > From: [email protected] [mailto:juniper-nsp- > [email protected]] On Behalf Of Mark Menzies > Sent: Friday, March 08, 2013 1:03 PM > To: Andy Litzinger > Cc: [email protected] > Subject: Re: [j-nsp] SRX upgrade procedure -ready for enterprise? > > The best approach, which does NOT include minimal downtime is to > upgrade > both nodes and then reboot them both at the same time. Its less > complicated, less prone to error but it does mean that the services > are > down for the time it takes for the boxes to boot and bring up all > interfaces.
I've thought about this a lot lately. At what point do the two nodes start communicating with each other after a reboot? What I'm getting at is, could you upgrade both, reboot one node, then right before it comes back online fully, reboot the other one? This way, you're not waiting around a full reboot cycle for service to return. -evt _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
