4-7
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
OL-16506-10
Chapter 4 Software Upgrade Process
ISSU Upgrade for Redundant Platforms
Step 2
copy tftp: URL-to-target-location
copy source-file-system:filename
standby-destination-filesystem
Example:
Router# copy tftp bootflash:
Copy the consolidated package onto the active RP.
Step 3
copy source-file-system:filename
standby-destination-filesystem
Example:
Router# copy
bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.
XNA1.bin stby-bootflash:
Copy the consolidated package onto the standby RP.
Step 4
dir URL-to-target-location
dir URL-to-target-stby-location
Example:
Router# dir bootflash:
Router# dir stby-bootflash:
(Optional) Display the contents of the target
directories to confirm the successful copy of the file
package.
Step 5
issu loadversion rp upgrade-rp-number
standby-file-system:filename
Example:
Router# issu loadversion rp 1 file
stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.12
2-33.XNA1.bin
Load the target consolidated package onto the
standby RP.
After you receive the message indicating that the
terminal state has been reached, go on to
Step 6.
Step 6
issu runversion
Example:
Router# issu runversion
Run the consolidated package that was loaded in
Step 5.
Note If this command is entered before the
terminal state is reached, a “
peer is not
online
” or “Standby RP is not in
terminal state
” error message will be seen
and the issu runversion command will not
work. If the issu runversion command does
not run for these reasons, wait for the
“
terminal state is reached” message to
appear and retry the issu runversion
command. You can also monitor the terminal
state using the show platform command.
After ISSU runversion is completed, a switchover
will automatically occur and the standby RP will
become the active RP.
Command or Action Purpose
To Next Page
Loading...
Need help?
General
