Usage Guidelines

Use the monitor event-trace command to control what, when, and how event trace data is collected. Use this command after you have configured the event trace functionality on the networking device using the monitor event-trace command in global configuration mode.

Note	The amount of data collected from the trace depends on the trace message size configured using the monitor event-trace command in global configuration mode for each instance of a trace.

The Cisco IOS software allows for the subsystem components to define whether support for event tracing is enabled or disabled at boot time. You can enable or disable event tracing in two ways: using the monitor event-trace command in privileged EXEC mode or using the monitor event-trace command in global configuration mode. To disable event tracing, you would enter either of these commands with the disable keyword. To enable event tracing again, you would enter either of these commands with the enable keyword.

To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ? command to get a list of software components that support event tracing. To determine whether event tracing is enabled by default for the subsystem, use the show monitor event-trace command to display trace messages.

Use the show monitor event-trace command to display trace messages. Use the monitor event-trace component dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace component dump pretty command.

To write the trace messages for all events currently enabled on a networking device to a file, enter the monitor event-trace dump command.

To configure the file where you want to save trace information, use the monitor event-trace command in global configuration mode. The trace messages are saved in a binary format.

Usage Guidelines

Use the monitor event-trace command to enable or disable event tracing and to configure event trace parameters for Cisco IOS software subsystem components.

Note

Event tracing is intended for use as a software diagnostic tool and should be configured only under the direction of a Technical Assistance Center (TAC) representative. In Cisco IOS software images that do not provide subsystem support for the event trace function, the monitor event-trace command is not available.

The Cisco IOS software allows the subsystem components to define whether support for event tracing is enabled or disabled by default. The command interface for event tracing allows you to change the default two ways: using the monitor event-trace command in privileged EXEC mode or using the monitor event-trace command in global configuration mode.

Additionally, default settings do not show up in the configuration file. If the subsystem software enables event tracing by default, the monitor event-trace componentenable command will not show up in the configuration file of the networking device; however, disabling event tracing that has been enabled by default by the subsystem will create a command entry in the configuration file.

Note	The amount of data collected from the trace depends on the trace message size configured using the monitor event-trace command for each instance of a trace.

To determine whether you can enable event tracing on a subsystem, use the monitor event-trace ? command to get a list of software components that support event tracing.

To determine whether event tracing is enabled by default for the subsystem, use the show monitor event-trace command to display trace messages.

To specify the trace call stack at tracepoints, you must first clear the trace buffer.

Usage Guidelines

Use the monitor event-trace crypto pki command to control what, when, and how event trace data is collected. Use the monitor event-trace component dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace component dump pretty command. To write the trace messages for all events currently enabled on a networking device to a file, enter the monitor event-trace dump command.

Usage Guidelines

Use the monitor event-trace crypto ipsec command to control what, when, and how event trace data is collected. Use the monitor event-trace component dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace component dump pretty command. To write the trace messages for all events currently enabled on a networking device to a file, enter the monitor event-trace dump command.

Usage Guidelines

Use the monitor event-trace crypto ikev2 command to control what, when, and how event trace data is collected. Use the monitor event-trace component dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace component dump pretty command. To write the trace messages for all events currently enabled on a networking device to a file, enter the monitor event-trace dump command.

Usage Guidelines

Use the monitor event-trace dump-traces command to save trace message information for all event traces currently enabled on a networking device. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace dump-traces pretty command.

To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC) command.

To configure the file where you want to save messages, use the monitor event-trace (global) command.

Usage Guidelines

Use the monitor event-trace dump-traces command to save trace message information for all event traces currently enabled on a networking device. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace dump-traces pretty command.

To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC) command.

To configure the file where you want to save messages, use the monitor event-trace (global) command.

Usage Guidelines

Use the monitor event-trace dump-traces command to save trace message information for all event traces currently enabled on a networking device. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace dump-traces pretty command.

To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC) command.

To configure the file where you want to save messages, use the monitor event-trace (global) command.

Usage Guidelines

Use the monitor event-trace dump-traces command to save trace message information for all event traces currently enabled on a networking device. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace dump-traces pretty command.

To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC) command.

To configure the file where you want to save messages, use the monitor event-trace (global) command.

Usage Guidelines

Use the monitor event-trace crypto pki command to control what, when, and how event trace data is collected. Use the monitor event-trace component dump command to save trace message information for a single event. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace component dump pretty command. To write the trace messages for all events currently enabled on a networking device to a file, enter the monitor event-trace dump command.

Usage Guidelines

Use the monitor event-trace dump-traces command to save trace message information for all event traces currently enabled on a networking device. By default, trace information is saved in binary format. If you want to save trace messages in ASCII format, possibly for additional application processing, use the monitor event-trace dump-traces pretty command.

To write the trace messages for an individual trace event to a file, enter the monitor event-trace (EXEC) command.

To configure the file where you want to save messages, use the monitor event-trace (global) command.

Usage Guidelines

You can use the monitor pcm-tracer capture-destination command to specify a location to save the PCM trace information. When Cisco IOS software saves the data to network file systems, such as TFTP and FTP, it assumes the location is valid and has write access.

After the PCM capture is complete, the router automatically copies the captured contents to the specified location. The filename format at the destination location is as follows:

<Configured name>_tx_<DS0 slot>_<DS0 unit>_<DS0 channel>--For TX
<Configured name>_rx_<DS0 slot>_<DS0 unit>_<DS0 channel>--For RX

You can identify the dial feature card (DFC) channel from where the PCM is traced using the filename format.

Consider the following example:

Router(config)# monitor pcm-tracer capture-destination tftp: ://223.255.254.254/benzeer/cap/cap_data

In this example, two files are created for the data corresponding to each DS0s, one for each direction (transmitter and receiver). When the debug pcmtracer command is enabled, the trace data is copied into the following files:

• cap_data_tx_6_1_22 and cap_data_rx_6_1_22 --This corresponds to the traffic flowing through DS0 6/1:22.

• cap_data_tx_6_1_22 and cap_data_rx_6_1_22 --cap_data_tx_6_1_2 2 is the data in the transmit direction (from the DFC to the system backplane) and cap_data_rx_6_1_22 is the data in the receiver direction (to the DFC from the system backplane).

Usage Guidelines

You must create at least one user profile under the channels that need to be traced. You can create the following profile operations:

• Create a user profile identified by a profile number.

• Add one or more profiles. A user profile consists of capture groups in which the channels that are to be traced are specified.

• Configure one or more capture groups under a profile.

Usage Guidelines

To prevent accidental configuration of ports as destinations, you can create a permit list of the ports that are valid for use as destinations. With a destination port permit list configured, you can only configure the ports in the permit list as destinations.

When you enter multiple instances of interface interface-type slot/port-fastport , you must enter a space before and after the comma. For example, interface interface-type slot/port-fastport , interface-type slot/port-fastport , interface-type slot/port-fastport .

Usage Guidelines

Note	Prior to Cisco IOS Release 12.2(33)SXH and the introduction of this feature, the operating mode was centralized and could not be changed.

Centralized egress span monitoring redirects traffic to the supervisor engine for egress monitoring.

Distributed egress span monitoring is performed in the ingress module. Distributed replication for Switched Port Analyzer (SPAN), Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN) increases the total throughput at the span destination.

Note	Distributed egress span (DES) mode is applied to ASIC-based sessions only.

Usage Guidelines

Release 12.2(18)SXE and later releases support ERSPAN with the Supervisor Engine 720, hardware revision 3.2 or higher. Enter the show module version | include WS-SUP720-BASE command to display the hardware revision.

ERSPAN traffic is GRE-encapsulated SPAN traffic that can only be processed by an ERSPAN destination session.

This command is not supported on Catalyst 6500 series switches that are configured with a Supervisor Engine 2.

All ERSPAN source sessions on a switch must use the same source IP address. You enter the origin ip address command to configure the IP address for the ERSPAN source sessions.

All ERSPAN destination sessions on a switch must use the same IP address. You enter the ip address command to configure the IP address for the ERSPAN destination sessions. If the ERSPAN destination IP address is not a Supervisor Engine 720 (for example, it is a network sniffer), the traffic arrives with the GRE and RSPAN headers/encapsulation intact.

The ERSPAN source session destination IP address, which must be configured on an interface on the destination switch, is the source of traffic that an ERSPAN destination session sends to the destination ports. You configure the same address in both the source and destination sessions with the ip address command.

The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from different ERSPAN source sessions.

The local ERSPAN session limits are as follows:

• Total sessions--66

• Source sessions--2 (ingress or egress or both)

• Destination sessions--23

The monitor session type command creates a new ERSPAN session or allows you to enter the ERSPAN session configuration mode. ERSPAN uses separate source and destination sessions. You configure the source and destination sessions on different switches. The ERSPAN session configuration mode prompts are as follows:

• Router(config-mon-erspan-src)--Indicates the ERSPAN source session configuration mode.

• Router(config-mon-erspan-src-dst)--Indicates the ERSPAN source session destination configuration mode.

• Router(config-mon-erspan-dst)--Indicates the ERSPAN destination session configuration mode.

• Router(config-mon-erspan-dst-src)--Indicates the ERSPAN destination session source configuration mode

The table below lists the ERSPAN destination session configuration mode syntaxes.

The table below lists the ERSPAN source session configuration mode syntaxes.

When you configure the monitor sessions, follow these syntax guidelines:

• erspan-destination-span-session-number can range from 1 to 66.

• single-interface is interface type slot /port ; type is fastethernet , gigabitethernet , or tengigabitethernet .

• interface-list is single-interface , single-interface , single-interface ...

Note	In lists, you must enter a space before and after the comma. In ranges, you must enter a space before and after the dash.

• interface-range is interface type slot /first-port - last-port .

• mixed-interface-list is, in any order, single-interface , interface-range , ...

• erspan-flow-id can range from 1 to 1023.

When you clear the monitor sessions, follow these syntax guidelines:

• The no monitor session session-number command entered with no other parameters clears the session session-number .

• session-range is first-session-number -last-session-number.

Note	When you enter the no monitor session range command, do not enter spaces before or after the dash. If you enter multiple ranges, do not enter spaces before or after the commas.

Use the monitor session type local command to configure ingress, egress, or both ingress and egress SPAN sessions.

Use the monitor session type local-tx command to configure egress-only SPAN sessions.

When you enter the local or the local egress-only SPAN session configuration mode, the prompt changes accordingly to Router(config-mon-local)# or Router(config-mon-local-tx)#, and the following commands are available:

• description -- Describes the properties for this session using this syntax:

The description can be up to 240 characters and cannot contain special characters or spaces.

• destination -- Specifies the destination and the destination properties using this syntax:

• exit -- Exits from configuration session mode.

• filter vlan vlan-id -- Limits the SPAN source traffic to specific VLANs; valid values are from 1 to 4096.

• no -- Negates a command or sets its defaults.

• shutdown -- Shuts down this session

• source -- Specifies the SPAN source interface or VLAN using the following syntax:

The local SPAN session limits are as follows:

• Total sessions--80

• Source sessions--2 (ingress or egress or both)

• Egress only--14

If you enter the filter keyword on a monitored trunk interface, only traffic on the set of specified VLANs is monitored.

Only one destination per SPAN session is supported. If you attempt to add another destination interface to a session that already has a destination interface configured, you get an error. You must first remove a SPAN destination interface before changing the SPAN destination to a different interface.

You can configure up to 64 SPAN destination interfaces, but you can have one egress SPAN source interface and up to 128 ingress source interfaces only.

A SPAN session can either monitor VLANs or monitor individual interfaces, but it cannot monitor both specific interfaces and specific VLANs. Configuring a SPAN session with a source interface and then trying to add a source VLAN to the same SPAN session causes an error. Configuring a SPAN session with a source VLAN and then trying to add a source interface to that session also causes an error. You must first clear any sources for a SPAN session before switching to another type of source.

Port channel interfaces display in the list of interface options if you have them configured. VLAN interfaces are not supported. However, you can span a particular VLAN by entering the monitor session session source vlan vlan-id command.

When you configure the destination , use these guidelines:

• A single-interface is as follows:

  • interface type slot /port ; type is fastethernet , gigabitethernet , or tengigabitethernet .
  • interface port-channel number

Note	Destination port channel interfaces must be configured with the channel-group group-num mode on command and the no channel-protocol command.

• An interface-list is single-interface , single-interface , single-interface ...

Note	In lists, you must enter a space before and after the comma. In ranges, you must enter a space before and after the dash.

• An interface-range is interface type slot / first-port - last-port .

• A mixed-interface-list is, in any order, single-interface , interface-range , ...

• A single-vlan is the ID number of a single VLAN.

• A single-list is single-vlan , single-vlan , single-vlan ...

• A vlan-range is first-vlan-ID - last-vlan-ID .

• A mixed-vlan-list is, in any order, single-vlan , vlan-range , ...

When you clear the monitor sessions, follow these syntax guidelines:

• The no monitor session session-number command entered with no other parameters clears the session session-number .

• session-range is first-session-number -last-session-number.

Note	When you enter the no monitor session range command, do not enter spaces before or after the dash. If you enter multiple ranges, do not enter spaces before or after the commas.

Usage Guidelines

The sysid messages and request program messages use the identity information indicated by this command.

Usage Guidelines

By default, when the software sends a request that requires a response from a MOP boot server and the server does not respond, the message is re-sent after 4 seconds. If the MOP boot server and router are separated by a slow serial link, it might take longer than 4 seconds for the software to receive a response to its message. Therefore, you might want to configure the software to wait longer than 4 seconds before resending the message if you are using such a link.

Usage Guidelines

The more system:running-config command displays the same output as the show running-config command. The more nvram:startup-config command is recommended as a replacement for the show startup-config command and the show configuration command.

You can use the following commands to display configuration files:

• The more nvram:startup-config command displays the startup configuration file that is contained in NVRAM or specified by the CONFIG_FILE environment variable. The Cisco IOS software informs you whether the displayed configuration is a complete configuration or a distilled version. A distilled configuration is one that does not contain access lists.

• The more system:running-config command displays the running configuration.

These commands show the version number of the software used when you last changed the configuration file.

You can also display the contents of files on remote systems using the more command. For example, you could display a saved running configuration file on an FTP server using more ftp://username:password@ftp-host1/mydirectory/7200-basic-running-config . See the description of the copy command for more information on file-system prefixes available in the Cisco IOS CLI.

Options for filtering and redirecting the output of this command are available by appending a pipe character (|). See the Related Commands table for a list of more <url> command extensions.

Usage Guidelines

The regular-expression argument is case sensitive and allows for complex matching requirements.

You can specify a new search at every --More-- prompt.

To search the remaining output of the more command, use the following command at the --More-- prompt:

/ regular-expression

To filter the remaining output of the more command, use one of the following commands at the --More-- prompt:

- regular-expression

+ regular-expression

When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl -^ (Ctrl-Shift-6) or Ctrl -Z .

Note	Once you specify a filter for a more command, you cannot specify another filter at a --More-- prompt. The first specified filter remains until the more command output finishes or until you interrupt the output. The use of the keyword begin does not constitute a filter.

Because prior output is not saved, you cannot search or filter backward through prior output.

Usage Guidelines

The regular-expression argument is case sensitive and allows for complex matching requirements.

You can specify a new search at any --More-- prompt. To search the remaining output of the more command, use the following command at the --More-- prompt:

/ regular-expression

When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl -^ (Ctrl-Shift-6) or Ctrl -Z .

Because prior output is not saved, you cannot search or filter backward through prior output.

Usage Guidelines

The regular-expression argument is case sensitive and allows for complex matching requirements.

You can specify a new search at any --More-- prompt. To search the remaining output of the more command, use the following syntax at the --More-- prompt:

/ regular-expression

When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl -^ (Ctrl-Shift-6) or Ctrl -Z .

Because prior output is not saved, you cannot search or filter backward through prior output.

Usage Guidelines

If you are a remote Telnet user performing the Flash upgrade without a console connection, this command allows you to retrieve console output when your Telnet connection has terminated due to the switch to the ROM image. The output indicates what happened during the download, and is particularly useful if the download fails.

This command is a form of the more command. See the more command for more information.

Usage Guidelines

This command determines whether the router will display the MOTD banner when an EXEC session is created on the specified line or lines. The MOTD banner is defined with the banner motd global configuration command. By default, the MOTD banner is enabled on all lines. Disable the MOTD banner on specific lines using the no motd-banner line configuration command.

The MOTD banners can also be disabled by the no exec-banner line configuration command, which disables both MOTD banners and EXEC banners on a line. If the no exec-banner command is configured on a line, the MOTD banner will be disabled regardless of whether the motd-banner command is enabled or disabled. The table below summarizes the effects of the exec-banner command and the motd-banner command.

For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner command or no motd-banner command is configured. The table below summarizes the effects of the exec-banner command and the motd-banner command for reverse Telnet connections.

Usage Guidelines

This command can be useful for keeping track of multiple connections.

You are prompted for the connection number and name to assign. The where command displays a list of the assigned logical connection names.

Usage Guidelines

Configuring the nmsp enable command enables NMSP features on the switch. However, configuring the nmsp stong-cipher command before enabling the NMSP features ensures that all NMSP connections use strong ciphers.

Usage Guidelines

The nmsp strong-cipher command enables strong ciphers for new Network Mobility Service Protocol (NMSP) connections.

Note	The existing NMSP connections will use the default cipher.

Usage Guidelines

Use this command to remove any menu commands for a particular menu from the configuration file.

As with all global configuration commands, this command will only effect the startup configuration file when you save the running configuration using the copy running-config startup-config EXEC command.

Usage Guidelines

This command sets a line to inform a user that has multiple, concurrent Telnet connections when output is pending on a connection other than the current one.

Usage Guidelines

Enable the notify syslog command if you use the syslog to monitor your device. Syslog monitoring prevents the need to gather configuration log information manually.

Note

When a system message contains lengthy descriptive information, the message text can sometimes exceed the syslog buffer. In releases earlier than Cisco IOS Release 12.2(33)SXF2, the overrun message is truncated to the buffer size and any additional text is lost. In Cisco IOS Release 12.2(33)SXF2 and later releases, a long message can be split into multiple messages, with truncation and continuation indicators at each section. The end of an incomplete syslog message section will be tagged with the string "**MSG XXXXX TRUNCATED**", where XXXXX is a count of overrun messages since the last system reload. The continuation of the message will begin with "**MSG XXXXX CONTINUATION #YY", where YY represents the part number. A message can be divided into a maximum of 99 parts. When truncation occurs, the following message is sent after the truncated message: %Log packet overrun, PC [hex], format: [chars]

Usage Guidelines

Use this command when the attached device is an old terminal that requires padding after certain characters (such as ones that scrolled or moved the carriage). See the “ASCII Character Set and Hex Values” appendix for a list of ASCII characters.

Usage Guidelines

Communication protocols provided by devices such as terminals and modems sometimes require a specific parity bit setting. Refer to the documentation for your device to determine required parity settings.

If you use this command to set parity on Cisco AS5350 and Cisco AS5400 NextPort lines, do not also set parity by means of S-register settings in a modemcap. (A modemcap is a series of parameter settings that are sent to your modem to configure it to interact with a Cisco device in a specified way. Cisco IOS software defines modemcaps that have been found to properly initialize most modems so that they function properly with Cisco routers and access servers.)

Usage Guidelines

The Parser Cache feature optimizes the parsing (translation and execution) of Cisco software configuration command lines by remembering how to parse recently encountered command lines, decreasing the time required to process large configuration files.

The parser cache is enabled by default. However, if you wish to disable the parser cache, you may do so using the no parser cache command in global configuration mode. To reenable the parser cache after it has been disabled, use the parser cache command.

When the no parser cache is issued, the command line appears in the running configuration file. However, if the parser cache is reenabled, no command line appears in the running configuration file.

Usage Guidelines

The Parser Concurrency and Locking Improvements feature ensures that exclusive access is granted only to a requested process and prevents other users from concurrently accessing the Cisco IOS configuration. That is, it prevents simultaneous execution of two or more commands. Use the parser command serializer command to configure the Parser Concurrency and Locking Improvements feature.

Usage Guidelines

Enable the parser config cache interface command to reduce the execution time required for running configuration management commands such as the show running-configuration , write terminal , and copy system:running-configuration commands. Information for these configuration management commands is supplied by nonvolatile generation (NVGEN) processes that query the system for configuration details. The parser config cache interface command is especially useful for managing large system configurations that contain numerous interface configurations.

Once enabled, the command provides faster execution of the NVGEN commands that process the running system configuration by caching interface configurations in system memory, and by retrieving only configuration information that has changed. For this reason, the device on which this command is enabled must have enough memory available to store the interface configuration. For example, if the interface configurations take up 15 KB of memory, using this command would require having an additional 15 KB of memory space available.

The first time you display the configuration file, you will not see much evidence of improvement in performance because the interface cache will be filled up. However, you will notice performance improvements when you enter subsequent NVGEN-type commands such as the show running-configuration EXEC command.

Each time the interface configuration is changed, the interface cache is flushed. Entering an NVGEN-type command after modifying the interface configuration will once again not show any performance improvement until the next NVGEN-type command is entered.

Usage Guidelines

This command controls (enables or disables) the Configuration Partitioning feature.

Note	This command is not related to disk partitions or disk partitioning.

To display the list of commands that make up the current running configuration for a specific part (“partition”) of the system’s global running configuration, use the show running-config partition command in privileged Exec mode.

The Configuration Partitioning feature uses a small amount of system resources. The no parser config partition command allows you to disable this feature if the feature is not needed on your system.

Note	Only the no form of this command appears in configuration files. To determine if config partitioning is supported on your system and whether it is enabled, use the show running-config parser ? command.

Usage Guidelines

The Parser Maximum feature provides a workaround in the event of a problem with the coding of a protocol, allowing the error to be bypassed untill it can be corrected.

Usage Guidelines

For the Cisco 1600 series and Cisco 3600 series routers, to undo partitioning, use the partition flash-filesystem :1 or no partition flash-filesystem : command. For other Class B platforms, use either the partition flash 1 or no partition flash command. If there are files in a partition other than the first, you must use the erase flash-filesystem:partition-number command to erase the partition before reverting to a single partition.

When creating two partitions, you must not truncate a file or cause a file to spill over into the second partition.

Note	The partition command will only create 3MB or larger partitions and may not be used if the device memory contains logging persistent files.

Usage Guidelines

When this command is entered, an archive file of the running configuration is saved when the archive config , write-memory , or copy running-config startup-config command is entered.

URLs are commonly used to specify files or location on the World Wide Web. On Cisco devices, URLs can be used to specify the location of a file or directory on a device or a remote file server. The path command uses a URL to specify the location and filename prefix for the Cisco configuration archive.

The locations or file systems that you can specify in the url argument are as follows:

• If your platform has disk0--disk0:, disk1:, ftp:, pram:, rcp:, slavedisk0:, slavedisk1:, or tftp:

• If your platform does not have disk0--ftp:, http:, pram:, rcp:, or tftp:

The colon is required in the location format.

The filename of the first archive file is the filename specified in the url argument followed by -1. The filename of the second archive file is the filename specified in the url argument followed by -2 and so on.

Because some file systems are incapable of storing the date and time that a file was written, the filename of the archive file can contain the date, time, and device hostname. To include the device hostname in the archive file filename, enter the characters $h (for example, disk0:$h). To include the date and time in the archive file filename, enter the characters $t.

When a configuration archive operation is attempted on a local file system, the file system is tested to determine if it is writable and if it has sufficient space to save an archive file. If the file system is read-only or if there is not enough space to save an archive file, an error message is displayed.

If you specify the tftp: file server as the location with the path command, you need to create the configuration file on the TFTP file server and change the file’s privileges before the archive config command works properly.