Navigation
Related Documentation
- SRX Series
- Upgrading ICU Using a Build Available Locally on a Primary Node in a Chassis Cluster
- Upgrading ICU Using a Build Available on an FTP Server
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
Upgrading Both Devices in a Chassis Cluster Using ICU
Devices in a chassis cluster can be upgraded with a minimal service disruption of approximately 30 seconds using in-band cluster upgrade (ICU) with the no-sync option. The chassis cluster ICU feature allows both devices in a cluster to be upgraded from supported Junos OS versions.
The impact on traffic is as follows:
- Drop in traffic (30 seconds approximately)
- Loss of security flow sessions
 | Note: ICU is supported only on SRX100, SRX210, SRX220, SRX240, SRX550, and SRX650 Services Gateways. |
Before you begin, note the following:
- ICU is available with the no-sync option only.
- This feature is available only on Junos OS Releases 11.2 R2 and later.
- Before starting ICU, you should ensure that sufficient disk space is available. See Upgrading ICU Using a Build Available Locally on a Primary Node in a Chassis Cluster and Upgrading ICU Using a Build Available on an FTP Server.
- This feature cannot be used to downgrade to a build earlier than Junos OS 11.2 R2.
The upgrade is initiated with the Junos OS build locally available on the primary node of the device or on an FTP server.
| Note:
|
Related Documentation
- SRX Series
- Upgrading ICU Using a Build Available Locally on a Primary Node in a Chassis Cluster
- Upgrading ICU Using a Build Available on an FTP Server
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
Published: 2014-06-19
Related Documentation
- SRX Series
- Upgrading ICU Using a Build Available Locally on a Primary Node in a Chassis Cluster
- Upgrading ICU Using a Build Available on an FTP Server
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
