Synchronized modules can become unsynchronized because you can change the router configuration at any time until you issue the issu start command. When the verification process is completed, unified ISSU starts up the stateful SRP switchover process to maintain synchronization between the active SRP module and the standby SRP module during the SRP module upgrade phase.
 |
Note: An SRP switchover from the active SRP module to the standby SRP module at this point in the in-service software upgrade causes a cold restart of the router because the SRP modules are running two different releases. The current release is on the active SRP module and the upgrade release is on the standby SRP module. |
The application and configuration data that has been mirrored to the standby SRP module is upgraded as required by the new software release. The CLI displays the progress of the SRP module upgrade.
While data on the standby SRP module is upgraded, any new changes that are mirrored from the primary SRP module to the standby SRP module are also upgraded to the version required by the armed release.
|
Note: This process consumes significant CPU resources on the redundant SRP module and can take a considerable amount of time to complete. Performance of the active SRP module might be affected during the SRP module upgrade. |
When the upgrade release has been synchronized to the standby SRP module, stateful SRP switchover is disabled until the in-service software upgrade is completed.
If you configure an application that does not support unified ISSU during the initialization phase, the initialization phase completes, but the issu start command subsequently fails.
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |