[j-nsp] SRX upgrade procedure -ready for enterprise?

[Clay Haynes]

I've had really good luck with the ICU Upgrade for branch series. You
upload the software package to the active SRX, run the commands, and it
handles copying the package to the backup unit and all reboots. There is
still a drop in traffic for up to 30 seconds, but for the most part it's
much safer than upgrading/rebooting both units simultaneously and praying
they come up properly. Again, ICU is supported on branch-series only, and
you have run 11.2r2 or later for it to be available.

http://www.juniper.net/techpubs/en_US/junos12.1/topics/task/operational/cha
ssis-cluster-upgrading-and-aborting-backup-and-primary-device-with-icu.html



I haven't had great luck on ISSU, but then again I don't have many
datacenter-series boxes to play with (300+ SRX650 and below, about 10
SRX1400 and above). I would follow this URL, and if you're running any of
these services in the respective code do not proceed with the ISSU:

http://kb.juniper.net/InfoCenter/index?page=content&id=KB17946&actp=RSS



- Clay




On 3/8/13 12:50 PM, "Andy Litzinger" <Andy.Litzinger at theplatform.com>
wrote:

>We're evaluating SRX clusters as replacements for our aging ASAs FO pairs
>in various places in our network including the Datacenter Edge.  I  was
>reading the upgrade procedure KB:
>http://kb.juniper.net/InfoCenter/index?page=content&id=KB17947  and
>started to have some heart palpitations.  It seems a complicated
>procedure fraught with peril.  Anyone out there have any thoughts
>(positive/negative) on their experience on upgrading an SRX cluster with
>minimal downtime?
>
>thanks!
>-andy
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp