The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Logging to Local Nonvolatile Storage feature enables system logging messages to be saved on an advanced technology attachment flash disk. Messages saved on bootflash or a harddisk persist after a router is rebooted.
For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Logging to Local Nonvolatile Storage" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
•Prerequisites for Logging to Local Nonvolatile Storage
•Restrictions for Logging to Local Nonvolatile Storage
•Information About Logging to Local Nonvolatile Storage
•How to Configure Logging to Local Nonvolatile Storage
•Configuration Examples for Logging to Local Nonvolatile Storage
•Feature Information for Logging to Local Nonvolatile Storage
The logging buffered Command Must Be Enabled
Before the Logging to Local Nonvolatile Storage feature can be enabled with the logging persistent command, you must enable the logging of messages to an internal buffer with the logging buffered command. For additional information, refer to the "Writing Logging Messages to Bootflash or a Harddisk" section, and to the "Related Documents" section.
Available bootflash or harddisk Space Constrains the Size and Number of Stored Log Files
The amount of bootflash or harddisk space allocated to system logging messages constrains the number of logging files that can be stored. When the allocation threshold is passed, the oldest log file in the directory is deleted to make room for new system logging messages. To permanently store system logging messages, you must archive them to an external device. For more information, refer to the "Copying Logging Messages to an External Disk" section.
Note Logging to Local Nonvolatile Storage can use up to 2 GB of storage space.
The Logging to Local Nonvolatile Storage feature adds a router's bootflash or harddisk as a storage destination for logging messages. When using this feature, be sure to understand the following concepts:
•How to Configure Logging to Local Nonvolatile Storage
System logging messages include error and debug messages generated by application programming interfaces (APIs) on the router. Typically, logging messages are stored in a router's memory buffer; when the buffer is full, older messages are overwritten by new messages. All logging messages are erased from the memory buffer when the router reboots.
This section contains the following procedures:
•Writing Logging Messages to Bootflash or a Harddisk (required)
•Copying Logging Messages to an External Disk (optional)
Perform this task to enable the Logging to Local Nonvolatile Storage feature and write logging messages to bootflash or a harddisk:
1. enable
2. configure terminal
3. logging buffered [buffer-size | severity-level]
4. logging persistent [url {harddisk:/directory | harddisk:/directory}] [size filesystem-size]
[filesize logging-file-size]
Perform this task to copy logging messages from the bootflash or a harddisk to an external disk.
1. enable
2. copy source-url destination-url
This section provides the following configuration examples:
•Writing Logging Messages to bootflash or a Harddisk: Example
•Copying Logging Messages to an External Disk: Example
The following example shows how to write up to 134217728 bytes (128 MB) of logging messages to the syslog directory of disk 0, specifying a file size of 16384 bytes:
Router(config)# logging buffered
Router(config)# logging persistent url harddisk:/syslog size 134217728 filesize 16384
The following example shows how to copy logging messages from the router's bootflash or harddisk to an external disk:
Router# copy harddisk:/syslog ftp://myuser/mypass@192.168.1.129/syslog
The following sections provide references related to the Logging to Local Nonvolatile Storage feature.
|
|
---|---|
copy command |
|
Network Management commands (including logging commands): complete command syntax, defaults, command mode, command history, usage guidelines, and examples |
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS XE software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.