The router can be
booted using any of the following:
single software image containing a full collection of software packages. This
mode provides a simplified installation and can be stored in the bootflash, a
TFTP server, or a network server.
or more sub-images extracted from the consolidated image. This mode provides
optimized memory usage and requires that you store files in the bootflash
NCS 4200 Series Software Packages
Table 1 Individual Sub-Packages
Route Switch Processor (RSP) operating system
Control plane processes between IOS process and the rest of the
Handles security features including Secure Socket Layer (SSL)
and Secure Shell (SSH)
Cisco IOS kernel, which is where IOS features are stored and
Each consolidated image has a unique RPIOS package.
Controls interface module daemons.
Provisioning files manage the boot process
when the router is configured to boot in sub-packages. The provisioning file manages the
bootup of each individual sub-package. Provisioning files are extracted automatically
when individual sub-package files are extracted from a consolidated package.
Provisioning files are not necessary for running the router using the complete
File Systems on the
Table 2 File Systems
flash memory file system on the active RSP.
Networking Services file directory.
You can copy the startup configuration to NVRAM or from NVRAM.
flash memory file system on the standby RSP.
The hard disk
file system on the standby RSP.
Serial Bus (USB) flash drive file systems on the standby RSP.
stby-usb1: is an internal port.
memory file system, which includes the running configuration.
system files file system.
Serial Bus (USB) flash drive file systems on the active RSP.
usb1: is an internal port.
If you see a file
system not listed in the above table, enter the
? help option
or see the
reference for additional information on that file system.
Table 3 Memory Recommendations for the NCS 4200
RSP3 Module - Consolidated Package Image
NCS 4200 RSP3 Module
Cisco NCS 4200 Series RSP3 UNIVERSAL W/O
NCS 4200 RSP3 Module
Cisco NCS 4200 Series RSP3 UNIVERSAL NPE
Determining the Software Version
You can use the showversioninstalledcommand to list the installed sub-packages on the router.
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.
Table 4 Autogenerated
file may appear in the bootflash: file system.
files are useful for tuning and troubleshooting, but are not related to router
operations: you can erase them without impacting the router’s performance.
bootflash/core directory is the storage area for .core files.
Do not erase or move the core directory.
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.
area for trace files is bootflash/tracelogs.
are useful for troubleshooting; you can access trace files using diagnostic
mode to gather information related to the IOS failure.
Do not erase or move the tracelog directory.
Creating a Service
Before creating a new
Service Upgrade directory, verify if that directory already exists in the
bootflash of the active and standby RSPs.
If the SU directory
exists, skip to Deleting an Existing packages.conf File.
If the directory does
not exist in the bootflash, create the directory by running the following
Router# mkdir su
Create directory filename [su]?
Created dir bootflash:/su
Deleting an Existing
Before loading the new
image to bootflash:su/, you must delete the existing packages.conf file. This
step is required only if the bootflash:su/ directory already existed in the
bootflash and contains an expanded image with a packages.conf file.
Remove all other
unused images (.bin, or expanded image with .conf and .pkg as file extensions)
from the existing SU directory.
The system boot
statement points to the packages.conf. This ensures that the systems boots
using the packages.conf file.
Router#show running-config | section boot
boot system bootflash:su/packages.conf
If the system boot
statement points to a different file, delete that file and point the boot
statement to the correct file by running the following commands:
Router# configure terminal
Router(config)# no boot system
Router(config)# boot system bootflash:su/packages.conf
Router(config)# do copy running-config startup-config
A system reload affects all services on the system.
Upgrading the Cisco
NCS4200 Series Chassis
The following sections describe:
Upgrading a single-RSP chassis
with boot in sub-package mode
Upgrading a redundant-RSP chassis with boot in sub-package mode
If IGP and MPLS are configured on the chassis, it is recommended that
NSR or NSF configuration are enabled for IGP and MPLS. These configuration
reduce the loss of traffic during RSP switchover during the upgrade process.
Before upgrading a
redundant-RSP chassis, verify if the
redundancy and mode sso are set.
Router# show running-config | section redundancy
If the above values
are missing, run the following commands to configure the chassis for SSO
Router(config-red)# mode sso
Router# show redundancy states | include peer
peer state = 8 -STANDBY HOT
The standby RSP should be in 'STANDBY HOT' state.
Consolidated Image on the Active and Standby RSPs and Reloading to the New
No new or modified standards are supported, and support for existing standards has not been modified.
No new or modified MIBs are supported, and support for existing MIBs has not been modified.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
No new or modified RFCs are supported, and support for existing RFCs has not been modified.
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.