Cisco 200 Series

Hierarchical Navigation

System Files

System files are files that contain configuration information, firmware images or boot code.

Various actions can be performed with these files, such as: selecting the firmware file from which the device boots, copying various types of configuration files internally on the device, or copying files to or from an external device, such as an external server.

The possible methods of file transfer are:

  • Internal copy.
  • HTTP/HTTPS that uses the facilities that the browser provides.
  • TFTF/SCP client, requiring a TFTP/SCP server.

Configuration files on the device are defined by their type, and contain the settings and parameter values for the device.

When a configuration is referenced on the device, it is referenced by its configuration file type (such as Startup Configuration or Running Configuration), as opposed to a file name that can be modified by the user.

Content can be copied from one configuration file type to another, but the names of the file types cannot be changed by the user.

Other files on the device include firmware, boot code, and log files, and are referred to as operational files.

The configuration files are text files and can be edited in a text editor, such as Notepad after they are copied to an external device, such as a PC.

Files and File Types

The following types of configuration and operational files are found on the device:

  • Running Configuration—Contains the parameters currently being used by the device to operate. This is the only file type that is modified when you change parameter values on the device.
  • If the device is rebooted, the Running Configuration is lost. The Startup Configuration, stored in Flash, overwrites the Running Configuration, stored in RAM.

    To preserve any changes you made to the device, you must save the Running Configuration to the Startup Configuration, or another file type.

  • Startup Configuration—The parameter values that were saved by copying another configuration (usually the Running Configuration) to the Startup Configuration.
  • The Startup Configuration is retained in Flash and is preserved when the device is rebooted. At this time, the Startup Configuration is copied to RAM and identified as the Running Configuration.

  • Mirror Configuration—A copy of the Startup Configuration, created by the device when the following conditions exist:
    • The device has been operating continuously for 24 hours.
    • No configuration changes have been made to the Running Configuration in the previous 24 hours.
    • The Startup Configuration is identical to the Running Configuration.

    Only the system can copy the Startup Configuration to the Mirror Configuration. However, you can copy from the Mirror Configuration to other file types or to another device.

    The option of automatically copying the Running Configuration to the mirror configuration can be disabled in the Configuration Files Properties page.

  • Backup Configuration—A manual copy of a configuration file used for protection against system shutdown or for the maintenance of a specific operating state. You can copy the Mirror Configuration, Startup Configuration, or Running Configuration to a Backup Configuration file. The Backup Configuration exists in Flash and is preserved if the device is rebooted.
  • Firmware—The program that controls the operations and functionality of the device. More commonly referred to as the image.
  • Boot Code—Controls the basic system startup and launches the firmware image.
  • Language File—The dictionary that enables the web-based configuration utility windows to be displayed in the selected language.
  • Flash Log—SYSLOG messages stored in Flash memory.

File Actions

The following actions can be performed to manage firmware and configuration files:

This section covers the following topics: