Application Data Upgrade On The Standby Srp Module - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SERVICE AVAILABILITY CONFIGURATION GUIDE 2010-10-08 Configuration Manual

Software for e series broadband services routers service availability configuration guide
Table of Contents

Advertisement

Application Data Upgrade on the Standby SRP Module

Copyright © 2010, Juniper Networks, Inc.
NOTE: We recommend that you issue the show issu command before
beginning the unified in-service software upgrade. The output of the command
lists any necessary conditions that are not currently met on the router. You
can therefore correct these failures before entering into the upgrade. You
can issue the show issu command at any time.
NOTE: On E120 and E320 routers, you can hot swap an IOA during the
initialization phase without affecting the in-service software upgrade.
However, we strongly recommend that you perform any necessary hot swaps
before you issue the issu initialize command.
If the standby SRP module reloads during the initialization phase, unified ISSU is halted.
You must begin again by issuing the issu initialize command.
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 unified 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 unified in-service software upgrade is completed.
Chapter 5: Configuring a Unified In-Service Software Upgrade
109

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents