Asr 5000 System Administration Guide, Staros Release 21.1 - Cisco ASR 5000 Administration Manual

On-Line Software Upgrade
Note the "Available" blocks in the last line of the display. After displaying the directory information, it again returns to
the root and the following prompt appears:
host_name
[local]
Step 2
View the boot stack entries and note the name and location (local device) of the CLI configuration file for the first entry
(highest priority) by entering the following command:
host_name
[local]
Step 3 Verify that there are less than 10 boot stack entries in the boot.sys file and that a higher priority in the boot stack is
available (minimally there is no priority 1 entry in the boot stack). Refer to Configuring the Boot Stack for more
information.
The system will automatically create a new boot stack entry for this software, using the <N-1> method, wherein the new
entry will have a priority of one less than the previous entry (currently used).
Step 4 Using either an FTP client or the copy command, transfer the new operating system software image file to the location
(network server or local device from where it will be loaded by the system).
For information on how to use the copy command, please reference the Copying Files and Directories section.
When transferring an operating system software image file via file transfer protocol (FTP), the FTP client must be
configured to transfer the file using binary mode. Failure to use binary transfer mode will render the transferred operating
system image file unusable. In release 20.0 and higher Trusted StarOS builds, FTP is not supported.
Step 5 Back up the current CLI configuration file by entering the following command:
host_name
[local]
For information on using the copy command, please see the Copying Files and Directories section.
The following command example creates a backup copy of a file called general.cfg located on the /flash device to a file
called general_3652.cfg:
host_name
[local]
Step 6 Synchronize the local file systems on the management cards by entering the following command:
host_name
[local]
Step 7
Enter the Global Configuration mode by entering the following command:
configure
The following prompt appears:
host_name
[local]
Step 8
For PDSN and HA services, configure an overload policy for each service that redirects new session requests to other
devices or rejects them as given procedure below.
Note that there is no explicit overload policy configuration for Closed R-P. The default overload behavior for Closed
R-P is to reject calls.
a) Enter the Context Configuration mode by entering the following command:
host_name
[local]
The following prompt appears:
context_name
[
b) Enter the Service Configuration mode for the service to be configured by entering the following command:
context_name
[
The following prompt appears:
context_name
[

ASR 5000 System Administration Guide, StarOS Release 21.1

138
#
show boot
#
copy from_url to_url [ -noconfirm ]
#
copy /flash/general.cfg /flash/general_3652.cfg
#
filesystem synchronize all
#
(config)#
context context_name
(config)#
host_name
] (config-ctx)#
host_name
] (config-ctx)#
host_name service_type
] (config-
{ pdsn-service | ha-service } service_name
-service)#
Software Management Operations