Juniper SRX5600, Hardware Manual

Page: 277 / 483

NOTE: Ensure that you use the correct node number for the destination node.
e. In the destination node, use the ls –la command to verify that all files from the
/var/db/certs/common/key-pair folder of the source node are copied.
f. Repeat Step b through Step e for the /var/db/certs/common/local and
/var/db/certs/common/certification-authority folders.
Low Impact Hardware Upgrade for SCB3 and IOC3
If your device is part of a chassis cluster, you can upgrade SRX5K-SCBE (SCB2) to SRX5K-SCB3 (SCB3)
and SRX5K-MPC (IOC2) to IOC3 (SRX5K-MPC3-100G10G or SRX5K-MPC3-40G10G) using the low-impact
hardware upgrade (LICU) procedure, with minimum downtime. You can also follow this procedure to
upgrade SCB1 to SCB2, and RE1 to RE2.
Before you begin the LICU procedure, verify that both services gateways in the cluster are running the
same Junos OS release.
NOTE: You can perform the hardware upgrade using the LICU process only.
You must perform the hardware upgrade at the same time as the software upgrade from Junos
OS Release 12.3X48-D10 to 15.1X49-D10.
In the chassis cluster, the primary device is depicted as node 0 and the secondary device as node 1.
Follow these steps to perform the LICU.
1. Ensure that the secondary node does not have an impact on network traffic by isolating it from the
network when LICU is in progress. For this, disable the physical interfaces (RETH child interfaces) on
the secondary node.
For SRX5400 Services Gateways
admin@cluster#set interfaces xe-5/0/0 disable
admin@cluster#set interfaces xe-5/1/0 disable
For SRX5600 Services Gateways
admin@cluster#set interfaces xe-9/0/0 disable
280