Cisco ASR 1000 Series Aggregation Services Routers Operations and Maintenance Guide

Performing File System Cleanups

---

This chapter describes the various file system cleanups performed on the Cisco ASR 1000 Series Aggregation Services Router.

This chapter includes the following sections:

• Performing Core File and Trace File Cleanups
• Performing Crashinfo File Cleanups
• Performing Sub-Package File Cleanups
• For More Information

Performing Core File and Trace File Cleanups

Core and trace files are automatically created and saved to the core and tracelogs directories on the
harddisk: file system on all Cisco ASR 1000 Series Routers except the Cisco ASR 1001 Router, Cisco ASR 1002 Router and Cisco ASR 1002-F Router, which store core and trace files in the bootflash: file system.

Trace files are automatically created during normal operation of the router and are stored in the tracelogs directory. Normally, the router automatically purges the old tracelogs to provide space for new files.

In case of a process failure, core files may be generated in the core directory. If any core files are detected, contact Cisco TAC for assistance. Normally, the router will automatically purge the old core files to make space for new files.

The user has the option to delete unneeded core and tracelog files to make space for other content. However, such a removal may impact the debuggability of the system.

Note On an Cisco ASR 1001 Router equipped with the HDD IDC option, the ROMMON cannot see the hard disk and therefore the ROMMON has no access to the data stored on the HDD IDC. Though you can copy the Image to a harddisk on Cisco ASR 1001-HDD Router, you cannot boot from the hardisk. The ASR1001 HDD can be used for general storage but cannot be considered a complete filesystem (like bootflash or USB0:) and is only accessible when the box is running IOS. The true intent of the HDD is to support applications that require a harddisk. Therefore the HDD IDC on Cisco ASR 1001 Router should be used for application services such as call manager, etc.

To clean up the contents of the core and tracelogs directories, perform the following steps:

Step 1 Log in to the Cisco ASR 1000 Series Router using a Telnet or Secure Shell (SSH) connection.

Note The core and tracelogs directories can contain large volumes of output. Be sure to use a Telnet or SSH connection instead of the console port to avoid monopolizing the console port.

Step 2 Change to the core or tracelogs directory using the cd command.

Step 3 Display the contents of the core or tracelogs directory using the dir command.

Step 4 Remove files from the core or tracelogs directory using the delete command. Delete files based on their creation date; that is, delete older files first.

Step 5 Repeat Step 2 through Step 4 for all the core and tracelogs directories on the router as follows:

• For Cisco ASR 1006 Routers, perform the file cleanup on the harddisk: file system on both RPs.
• For Cisco ASR 1004 Routers, perform the file cleanup on the harddisk: file system on the single RP.
• For Cisco ASR 1002 Routers and Cisco ASR 1002-F Routers, perform the file cleanup on the bootflash: file system. (The harddisk: file system is not available.)

Performing Crashinfo File Cleanups

Crashinfo files are automatically created and saved to the bootflash: or harddisk: file systems on all Cisco ASR 1000 Series Routers. Delete unneeded crashinfo files at least once a week to maintain optimal router operation.

To delete crashinfo files, perform the following steps:

Step 1 Log in to the Cisco ASR 1000 Series Router using a Telnet or Secure Shell (SSH) connection.

Note Crashinfo files may generate large volumes of output. Be sure to use a Telnet or SSH connection instead of the console port to avoid monopolizing the console port.

Step 2 Change to the bootflash: or harddisk: directory using the cd command.

Step 3 Display the contents of the directory using the dir command.

Step 4 Delete crashinfo files using the delete command.

Step 5 Repeat Step 2 through Step 4 for the other file system.
For Cisco ASR 1006 Routers, purge the crashinfo files on both RPs.

Performing Sub-Package File Cleanups

A consolidated package file can be stored in the bootflash: file system, on a USB Flash disk, or on any TFTP or other network server. Individual sub-package files and provisioning files must be stored in the bootflash: file system.

A sub-package file is no longer in use when it is no longer referenced by the booted or specified provisioning manager. Remove sub-package files and provisioning files that are no longer in use to maintain optimal router operation.

To delete sub-package files and provisioning files that are no longer in use, use the request platform software package clean command. This command checks to see which sub-package files and provisioning files are in use and deletes only those files that are not in use.

Example: Deleting All Unused Sub-Package Files and Provisioning Files From a Boot Directory

The following example shows how to delete all unused sub-package files and provisioning files from a boot directory:

The following example shows all sub-package files and provisioning files in a boot directory. If they are in use, they cannot be deleted:

Example: Deleting a Specific Sub-Package File from a Boot Directory

The following example shows how to delete a specific sub-package file from a boot directory:

The following example shows that a specific sub-package file cannot be deleted if it is in use:

Example: Deleting a Duplicate Sub-Package File on Different Media

The following example shows how to delete a sub-package file that was copied and has the same name as the file that was used to boot, but the duplicate file is on different media:

For More Information

For more information about the topics discussed in this chapter, see the following documents: