[j-nsp] How to upgrade M20 RE's with least downtime

[Harry Reynolds]

*If* this is within a major version, I have heard that you can get great
results by:

1. Enable Graceful restart to minimize/eliminate forwarding plane
disruption

2. Upgrade backup RE

3. Manually switch (here is where graceful restart comes in)

4. Upgrade primary RE

5. If step 3 worked well, switch back


HTHs. Please note Juniper does not claim support for hitless upgrades,
but this procedure has been known to result in pretty much that. All
bets are off if you are crossing major JUNOS software revisions. You
also need to enable graceful restart on peer nodes for it to buy you
anything.

 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Bill Petrisko
> Sent: Friday, November 12, 2004 2:18 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] How to upgrade M20 RE's with least downtime
> 
> I need to upgrade the junos on an M20 with redundant RE's.
> 
> What is the practical method of doing this, in order to have 
> the least amount of downtime?  Are there any issues with 
> upgrading one RE at a time, and performing a manual 
> switchover between upgrades so that the router is not down 
> for the full install process?
> 
> I am thinking either...
> 
> a) Upgrade (backup) RE1, reboot it, etc
> b) Force switchover to RE1
> c) Upgrade RE0
> d) Let it run on RE1 
> 
> Or...
> 
> a) Force switchover to (backup) RE1
> b) Upgrade RE0, reboot it, etc
> c) Force switchover to RE0
> d) Upgrade RE1, reboot it, etc
> 
> I just want to make sure that one of the above is an 
> acceptable or a customary way of doing it -- also that 
> nothing bad will happen if I have two RE's running at 
> different version levels for a brief time.  
> 
> bill
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>