Cluster software upgrade SRX1500

rack 104

rack 202

https://kb.juniper.net/InfoCenter/index?page=content&id=KB17947&actp=METADATA

The goal of this article is to provide information and the procedure for upgrading SRX chassis clusters with minimal downtime as an alternative to ISSU/ICU.

https://kb.juniper.net/InfoCenter/index?page=content&id=KB17947&actp=METADATA

Not using ISSU or ( ICU for branch )

NOTE: During this type of chassis cluster upgrade, a service disruption of about 3 to 5 minutes occurs.

https://www.juniper.net/documentation/en_US/junos/topics/task/operational/chassis-cluster-separate-device-upgrading.html

1- Download file to SRX1500 ( RE)

2- Copy the tgz file to the other SRX

3- pre-

4- Upgrade the SRX one after the other

5- Post-

Copy from Node1 to Node0

file copy "/var/tmp/image-18.2R2-S1.3.tgz" node0:"/var/tmp/image-18.2R2-S1.3.tgz"

3- Check and Add the file to BOTH SRX1500 ( RE)

request system software validate "/var/tmp/image-18.2R2-S1.3.tgz"

request system software add "/var/tmp/image-18.2R2-S1.3.tgz"

4- Reboot both SRX1500

request system reboot

request routing-engine login node 1

(on High End: rlogin -T node1)


	node0 Expand source root@SRX1500-2> show interfaces terse Interface Admin Link Proto Local Remote dsc up up em0 up up em0.0 up up inet 129.16.0.1/2 tnp 0x1100001 em1 up up em1.32768 up up inet 192.168.1.2/24 em2 up up fxp0 up up fxp0.0 up up inet 172.30.95.206/25 172.30.95.207/25 gre up up ipip up up lo0 up up lo0.16385 up up lsi up up mtun up up pimd up up pime up up tap up up

Juniper Security