Upgrade ASR920
Upgrade ASR920
This chapter describes how to update software on the Cisco ASR 920 Series Router.
• Upgrading Field Programmable Hardware Devices, on page 1
• File Systems on the Cisco ASR 920 Series Router, on page 1
• Restrictions, on page 2
• System Requirements, on page 2
• Autogenerated Files and Directories, on page 3
• Upgrading the Router Software, on page 4
• Verifying the Upgrade, on page 7
• Software Upgrade Example, on page 8
nvram: Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.
system: The system memory file system, which includes the running configuration.
usb[0-1]: The Universal Serial Bus (USB) flash drive file systems.
If you see a file system not listed in the table above, enter the ? help option or see the copy command reference
for additional information on that file system.
Restrictions
When you migrate to Cisco IOS-XE Release 3.18 SP, HOFPGA upgrade is mandatory and not optional. The
router works for few minutes after the first reboot is complete and starts a second reboot without a notice.
System Requirements
The following sections describe the system requirements for the Cisco ASR 920 Series Router software:
Memory Recommendations
These are the recommendation for the routers for the Cisco IOS XE 3S images and packages:
• DRAM Memory—4 GB
• Software Image—asr920-universalk9_npe.bin—270 MB (ASR 920-24SZ-IM)
• Software Image—asr920-universalk9_npe.bin—300 MB (ASR 920-12SZ-IM)
Note If you try to copy or archive upgrade beyond the bootflash memory capacity, the action aborts.
You can use the show version privileged EXEC command to see the software version that is running on your
router. The second line of the display shows the version.
You can also use the dir bootflash: privileged EXEC command to see the names of other software images
that you might have stored in bootflash.
3.13.0S 15.4(3)S
3.14.0S 15.5(1)S
The Cisco ASR 920 Series Router does not support IOS XE versions prior to 3.13.0S.
Caution Do not alter any autogenerated file in the bootflash: directory should not be deleted, renamed, moved, or
altered in any way unless directed by customer support; altering these files can have unpredictable consequences
for system performance.
crashinfo files A crashinfo file may appear in the bootflash: file system.
Crashinfo files are useful for tuning and troubleshooting, but are not related to router
operations: you can erase them without impacting the router’s performance.
core files The bootflash/core directory is the storage area for .core files.
Caution Do not erase or move the core directory.
lost+found directory This directory is created on bootup if a system check is performed. Its appearance is
completely normal and does not indicate any issues with the router.
Caution Ensure that you have chosen an upgrade image that is supported by your current software version.
Note Before upgrading from Cisco IOS XE 3.13.0S to 3.14.0S, we recommend that you disable the following CLI
on router: platform trace runtime slot 0 bay 0 process iomd module all-modules level info
The routers are shipped with the latest software image installed. Follow the instructions in this section if you
need to reinstall or upgrade the software image.
Before installing your router software, make sure that you have archived copies of the current Cisco IOS XE
release and the Cisco IOS XE release to which you are upgrading. You should keep these archived images
until you have upgraded all devices in the network to the new Cisco IOS XE image and until you have verified
that the new Cisco IOS XE image works properly in your network.
Cisco routinely removes old Cisco IOS XE versions from [Link]. See End of Sale and End of Life Products
at this URL: [Link]
You can copy the software image file on the bootflash memory to the appropriate TFTP directory on a host
by using the copy bootflash: tftp: privileged EXEC command. You can also configure the router as a TFTP
server to copy files from one router to another without using an external TFTP server by using the tftp-server
global configuration command. For more information about the tftp-server command, see the “Basic File
Transfer Services Commands” section of the Cisco IOS Configuration Fundamentals Command Reference
at this URL: [Link]
This procedure is for copying the combined bin file to the router. You copy the file to the router from a TFTP
server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Procedure
Step 2 Download the image to a TFTP server and make sure that the server is properly configured.
Step 3 Log into the router through the console port or a Telnet session.
Step 4 If Gigabit Ethernet (GE) port 0 is used as management interface, check the connectivity to TFTP server using
the following CLI:
Router# ping vrf Mgmt-intf tftp-server-address
For more information about assigning an IP address and default gateway to the router, refer to the software
configuration guide for this release.
Step 5 Download the image file from the TFTP server to the router by entering this privileged EXEC command:
Router# copy t[Link] bootflash:
This example shows how to download an image from a TFTP server at [Link] and to overwrite the image
on the router:
Router# copy t[Link] bootflash:
The installation process extracts the bin file with all the files and the IOS XE image, and sets the BOOT
directory to the created directory in bootflash memory. The process takes approximately 5 to 10 minutes, and
at some stages might appear to have stopped.
Step 6 Set the image path in the boot variables and configure the router to autoboot as follows:
Router# configure terminal
Router(config)# config-register 0x2102 (! 0x2102 sets the router for autoboot)
Router(config)# boot system bootflash:[Link] (! sets the image to be loaded in the
next reload)
Step 7 Verify the boot variables set on the router using the following CLI:
Router# show bootvar
BOOT variable = bootflash:asr920-universalk9_npe.bin ,12;
CONFIG_FILE variable does not exist
After the installation, the router is running the universal image. To install a purchased license with increased
capabilities, see Software Activation Configuration Guide. To purchase a license, contact Cisco.
Caution To avoid actions that might make your system unable to boot, read this entire section before starting the
upgrade.
Procedure
Step 1 Check the router bootup ROMMON region (ROM0 or ROM1). The example, shows the router boots up from
ROM0 region.
Example:
1966080+0 records in
3840+0 records out
Upgrade image MD5 signature is 712184b6ef336f40263222175255f475
Burning upgrade partition...
1966080+0 records in
1966080+0 records out
CChecking upgrade partition...
1966080+0 records in
1966080+0 records out
Upgrade flash partition MD5 signature is 712184b6ef336f40263222175255f475
ROMMON upgrade complete.
To make the new ROMMON permanent, you must restart the RP.
Step 5 Reload the router again to confirm bootup from upgraded ROMMON region ROM1.
Example:
Router# reload
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]
Jul 24 09:56:34.510: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload
[Link] 24 15:27:03.205 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: process
exit with reload chassis code
System Bootstrap, Version 12.2(20140211:085836) [pbalakan-sb_romver_16 130], DEVELOPMENT
SOFTWARE
Copyright (c) 1994-2012 by cisco Systems, Inc.
Compiled Fri 28-Mar-14 18:57 by pbalakan-sb_romver_16
Boot ROM1
Last reset cause: RSP-Board
Step 6 Repeat Step 3 to Step 5 to update the other region on the RSP (ROM0) region in this procedure).
Note We recommend that both region ROM0 a.ndROM1 are upgraded.
Use the show rom-monitor r0 command to check the rommon version on the router.
of memory.
Processor board ID CAT1748U1GQ
12 Gigabit Ethernet interfaces
2 Ten Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
2097152K bytes of physical memory.
1328927K bytes of SD flash at bootflash:.
Configuration register is 0x2102