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

[Mark Menzies]

Yes the upgrade process is not the best.

The link above puts names on tasks to do do effectively "split" the cluster
in such a way that you can reconnect it without loss of connectivity.

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.

Its something that I hope Juniper are looking at.


On 8 March 2013 17:50, 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
>