Software Package and Architecture

This section covers these topics.

Consolidated packages

A consolidated package is a single image composed of individual software subpackage files that

  • enables the Cisco Catalyst 8500 Series Edge Platforms to boot and operate using a single, bootable package file,

  • includes a provisioning file within the consolidated package which can be used to boot the router with the complete consolidated package.

  • uses the provisioning file for booting when subpackages are extracted or optional subpackages are selected, and

  • simplifies software management by combining all necessary components into one file.

Individual software subpackages within a consolidated package

Individual subpackages are not available for separate download from Cisco.com. Users must download a consolidated package and extract the needed subpackages from it by using the command-line interface. If the router operates with individual subpackages instead of a complete consolidated package, it must be booted using a provisioning file. Every consolidated package contains a provisioning file, which is extracted along with the individual subpackages during the extraction process.

  • RPBase: Provides the operating system software for the Route Processor.

  • RPControl: Controls the control plane processes that interface between the IOS process and the rest of the platform.

  • RPAccess: Exports processing of restricted components, such as Secure Socket Layer (SSL), Secure Shell (SSH), and other security features.

  • RPIOS: Provides the Cisco IOS kernel, which is where IOS features are stored and run. Each consolidated package has a different RPIOS.

  • ESPBase: Provides the ESP operating system and control processes, and the ESP software.

Provisioning files

Provisioning files manage the boot process when the Cisco Catalyst 8500 Series Edge Platforms is configured to run using individual subpackages or optional subpackages (such as the package for the Cisco WebEx Node Cisco Catalyst 8500 Series Edge Platforms Series).

When individual subpackages are being used to run the Cisco Catalyst 8500 Series Edge Platforms, the router has to be configured to boot the provisioning file. The provisioning file manages the bootup of each individual subpackage and the Cisco Catalyst 8500 Series Edge Platform assumes normal operation.

Provisioning files are extracted automatically when individual subpackage files are extracted from a consolidated package.

Provisioning files are not necessary for running the router using the complete consolidated package; if you want to run the router using the complete consolidated package, simply boot the router using the consolidated package file.

You must use the provisioning files to manage the boot process if you need to install optional subpackages. The provisioning file and individual subpackage files must be kept in the same directory. The provisioning filename can be renamed; the individual subpackage filenames cannot be renamed. After placing the provisioning file and the individual subpackage files in a directory and booting the router, it is highly advisable not to rename, delete, or alter any of these files. Renaming, deleting, or altering the files can lead to unpredictable router problems and behaviors

Upgrade field programmable hardware devices

Starting in Cisco IOS XE Release 17.3.2, a hardware programmable package file used to upgrade field programmable hardware devices is released as needed . A package file is provided for the field programmable device to customers in cases where a field upgrade is required.

If the Cisco Catalyst 8500 Series Edge Platforms contains an incompatible version of the hardware programmable firmware, then that firmware may need to be upgraded.

Generally an upgrade is only necessary in cases where a system message indicates one of the field programmable devices on the Cisco Catalyst 8500 Series Edge Platforms needs an upgrade or a Cisco technical support representative suggests an upgrade.

Processes overview

Cisco IOS XE has numerous components that run entirely as separate processes on the Cisco Catalyst 8500 Series Edge Platforms. This modular architecture increases network resiliency by distributing operating responsibility among separate processes rather than relying on Cisco IOS software for all operations.

IOS as a process

In almost all previous Cisco router platforms, an overwhelming majority of the internal software processes are run using Cisco IOS memory.

The Cisco Catalyst 8500 Series Edge Platforms introduce a distributed software architecture that moves many operating system responsibilities out of the IOS process. In this architecture, IOS, which previously was responsible for almost all of the internal software processes, now runs as one of many Linux processes while allowing other Linux processes to share responsibility for running the router. This architecture allows for better allocation of memory so the router can run more efficiently.

Dual IOS processes

The Cisco Catalyst 8500 Series Edge Platforms introduces a dual IOS process model that allows for increased high availability at all times. In the event of an active IOS failure, the second IOS process immediately becomes the active IOS process with little to no service disruption

On Cisco Catalyst 8500 Series Edge Platforms configured with dual Route Processors, the second IOS process runs on the standby Route Processor.

The state of these dual IOS processes can be checked by entering the show platform command.

File systems

The table provides a list of file systems that can be seen on the Cisco Catalyst 8500 Series Edge Platforms.

Table 1. File Systems

File System

Description

bootflash:

The boot flash memory file system on the active RP.

cns:

The Cisco Networking Services file directory.

harddisk:

The hard disk file system on the active RP.

nvram:

Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.

obfl:

The file system for Onboard Failure Logging files.

system:

The system memory file system, which includes the running configuration.

tar:

The archive file system.

tmpsys:

The temporary system files file system.

usb[0-1]:

The Universal Serial Bus (USB) flash drive file systems on the active RP.


Note

If you run into a file system not listed in the above table, enter the? help option or see the copy command reference for additional information on that file system.

Autogenerated file directories and files

Any autogenerated file on the bootflash: directory should remain unchanged unless you receive explicit instructions from customer support. Changing these files may impact system performance in unpredictable ways.

The table provides a list and descriptions of autogenerated files on the Cisco Catalyst 8500 Series Edge Platforms.

Table 2. Autogenerated Files

File or Directory

Description

crashinfo files

A crashinfo file may appear in the bootflash: or harddisk: file system.

These files provide descriptive information about a crash. They may be useful for tuning or troubleshooting purposes, but they are not part of router operations and can be erased without impacting router functioning

core directory

The storage area for.core files.

If this directory is erased, it will automatically regenerate itself at bootup. The .core files in this directory can be erased without impacting any router functionality, but the directory itself should not be erased.

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.

tracelogs directory

The storage area for trace files.

Trace files are useful for troubleshooting, but they are not part of router operations and can be erased without impacting the router’s performance.

Crashinfo, core, and trace files can be deleted. However, do not remove the core and tracelog directories, which are an automatic part of the harddisk: file system.